mqtt_connect error no 22 appearing after several successful connections.

RE: mqtt_connect error no 22 appearing after several successful connections.

dejans — Wed, 01 Mar 2023 12:39:27 GMT

Hi,

In order to have better insight into the problem, please provide modem trace.

Best regards,
Dejan

RE: mqtt_connect error no 22 appearing after several successful connections.

Jstone40649 — Tue, 28 Feb 2023 21:27:38 GMT

Sure, I'll get working on that though it's a very non-deterministic problem so it might take a while. These devices often run for months on end without encountering issues. I can add that configuration and setup more devices, but it's not something that's occurring often though when it does occur it appears to latch.

In the meantime is it possible to look into possible causes for EINVAL responses out of aws_iot_connect()?

I've been looking through myself and it seems that most of the time that function returns EINVAL when there's some incorrect configuration information. If that's consistent it would mean that some part of our configuration is being corrupted during runtime which we can look into.

If there's other situations where an EINVAL could originate from we could do debugging on that.

If at all possible I'd like to have some idea of where I could start looking for these sort of things, while I wait for more data from the devices themselves.

RE: mqtt_connect error no 22 appearing after several successful connections.

dejans — Tue, 28 Feb 2023 10:08:23 GMT

Hi,

Could you provide application log after you enable CONFIG_NET_LOG and CONFIG_MQTT_LOG_LEVEL_DBG configuration options in your prj.conf file?

Best regards,
Dejan

RE: mqtt_connect error no 22 appearing after several successful connections.

Jstone40649 — Mon, 27 Feb 2023 13:22:19 GMT

Sure, I'm not sure what specifically might be important. I'll cover what I can, but if you've got a more specific question let me know.

We have a custom board with an NRF9160 being used to post data to AWS. The application's purpose is to generally sit idle, waiting for an external 'Post' command. That trigger causes the modem to connect, if the modem connects it triggers AWS to connect, if AWS connects it triggers a publish; then we format a JSON message and attempt to publishes that to AWS.

The general purpose of the app is post data to the cloud periodically, every hour or so, otherwise it sits 'idle/sleeping'.
Code-wise it's largely based off the Asset Tracker example, and uses the application event structure. Once fully provisioned the devices will be booted once, and then expected to run 'forever'. Before running into this "EINVAL" issue, the device has happily posted dozens, if not hundreds of times. This error also appears to be latching, as the device will never post again, unless we re-boot via power cycle.

RE: mqtt_connect error no 22 appearing after several successful connections.

dejans — Fri, 24 Feb 2023 13:43:15 GMT

Hi,

The error you see is EINVAL 22 Invalid Argument error.

Could you provide more information about your application?

Best regards,
Dejan