nRF9160 thingy91 - AWS IOT (sample): Connect errors -11 and -10

[johnwest]

Hello All,

This is from an app I had working 1 1/2 months ago - when I've tried recently to get it connected again, I haven't been successful.

The latest asset tracker appears to work find and posts data to the nRF Cloud.

I've seen previous posts - DNS is working - or appears to be ok.

I'm getting the following:

===

+CSCON: 0

RRC mode: Idle

Next connection retry in 30 seconds

AWS_IOT_EVT_CONNECTING

+CSCON: 1

RRC mode: Connected

E: getaddrinfo, error -11

E: client_broker_init, error: -10

AWS_IOT_EVT_CONNECTING

+CSCON: 0

RRC mode: Idle

Next connection retry in 30 seconds

AWS_IOT_EVT_CONNECTING

+CSCON: 1

RRC mode: Connected

E: getaddrinfo, error -11

E: client_broker_init, error: -10

AWS_IOT_EVT_CONNECTING

+CSCON: 0

RRC mode: Idle

====

I can reload the asset tracker and it'll work fine.  I'm running the AWS_IOT sample code.

Thanks in advance as to what -11 and -10 mean - it would appear getting the address fails - I tried to find error codes that make sense but not sure and wanted to ask in case something has changed in the last 1 1/2 months.  This app used to run without issue.

Thanks!
jwest

[johnwest]

Didrik Rokhaug said:

Hi,

Thanks in advance as to what -11

The -11 comes from getaddrinfo, which has it's own error codes. You can find them here: https://github.com/nrfconnect/sdk-zephyr/blob/main/include/net/dns_resolve.h#L122

and -10 mean

This is a normal errno error number, you can find them here: https://github.com/zephyrproject-rtos/zephyr/blob/main/lib/libc/minimal/include/errno.h#L49

Remember to look at the right version of the file, as the numbers has changed over time.

This is from an app I had working 1 1/2 months ago

I'm running the AWS_IOT sample code.

Are you running an old build of the aws_iot sample, that used to work?

If so, what version is the build based on, and did you make any changes?

Or are you running a new build, of an old version of the sample?

Then, again, I would need to know what version of the sample you are using, and if you have made any changes to it, in addition, I would  like to know which toolchain version you used when building the sample.

Or, are you using a new version of the aws_iot sample which doesn't work, but earlier you used an older version which did work?

Then again, I have similar questions. Which SDK versions are involved, and have you made any modifications to either of the versions?

And, regardless of the above, which modem FW version are you using, and what SIM card are you using?

Is it possible that hte SIM card is out of data?

Best regards,

Didrik

Didrik,

Running what's in v1.7.1 - with latest firmware - 1.3.1.

Using 5.64 of toolchain.

AT&T Sim card.  I can switch back and forth to/from current assetTracker in v1.3.1 FW (10/20) - assetTracker posts fine to nrfCloud - after updating nRF Cloud certificate.

Does this answer all of your questions?

I guess a newbie mistake I made was to say "yes" to the Segger embedded studio where I had version 1.6 based AWS_IOT app running and 1.3.0 of modem firmware - I may have that hex file saved off.  That build failed and I moved to 5.64, 1.3.1. and 1.7.1.  The successful build made 1 1/2 months ago was 5.60 tools based.

Thanks,
johnwest

[johnwest]

Didrik,

Found the .hex file - and getting this:

SPM: NS image at 0x1c200

SPM: NS MSP at 0x2001f8b0

SPM: NS reset vector at 0x222c1

SPM: prepare to jump to Non-Secure image.

*** Booting Zephyr OS build v2.6.0-rc1-ncs1  ***

I: Modem library is not yet initialized, AT commands not sent

I: Configuration of MAGPIO and COEX0 is left to drivers

The AWS IoT sample started, version: v1.0.0A

LTE cell changed: Cell ID: 170924863, Tracking area: 35667

RRC mode: Connected

Network registration status: Connected - home network

Next connection retry in 30 seconds

PSM parameter update: TAU: -1, Active time: -1

AWS_IOT_EVT_CONNECTING

DATE_TIME_OBTAINED_NTP

AWS_IOT_EVT_DISCONNECTED

W: connection_poll_start failed, error: -119

So, -119 is there.

All 3 of the previous build files are returning -119 on the aws_iot_connect command:

aws_iot_connect, error: -119

Maybe that actually means the certificates are incorrect.(?)

Thanks,
johnwest