getaddrinfo, error -2

[Capt. Flatus O'Flaherty]

Error:

*** Booting Zephyr OS build v3.3.99-ncs1 ***
*** Booting Zephyr OS build v3.3.99-ncs1 ***
I: The AWS IoT sample started, version: v1.0.0
+CEREG: 2,"E03C","0012FE1E",7
I: LTE cell changed: Cell ID: 1244702, Tracking area: 57404
+CSCON: 1
I: RRC mode: Connected
%XTIME: ,"32609251520440","01"
+CEREG: 5,"E03C","0012FE1E",7,,,"11100000","11100000"
I: Network registration status: Connected - roaming
I: Date I: PSM parameter update: TAU: 6480, Active time: -1
time obtained
I: Next connection retry in 30 seconds
I: AWS_IOT_EVT_CONNECTING
E: getaddrinfo, error -2
E: client_broker_init, error: -10
I: AWS_IOT_EVT_CONNECTING

From: ncs/v2.4.0/nrf/samples/nrf9160/aws_iot

The first error is: "getaddrinfo, error -2"

Please advise how I can fix this !!!

Thank you.

[Øyvind]

O'hoi captain! 

Could you please provide more details on what SIM card you are using? Have you changed anything in the AWS IoT sample from your side? 

Have you ensured that your AWS account is properly configured, and that you are using correct AWS policy as described in the documentation? 

Kind regards;
Øyvind

[Capt. Flatus O'Flaherty]

Thanks @Øyvind for your reply.

I am using a Soracom SIM, not changed anything in the AWS IOT sample files and the AWS side of things seems to be working due to python test being successful, as above.

A 'Policy' file was generated by 'start.sh' and it contains the AWS address info.

I did try using the Nordic MQQT page, but it would not recognise the IMEI and serial no. of my device.

I also tried the 'CellularMoitor' app and it worked for a few minutes then the serial port droppped out:

08:10:38.925	Using nrf-monitor-lib-js version 0.8.0-pre3
08:10:38.926	Using nrf-monitor-lib version 0.13.1
08:10:38.928	Using nrf-device-lib-js version: 0.6.12
08:10:38.928	Using nrf-device-lib version: 0.15.3
08:10:38.928	Using nrfjprog DLL version: 10.19.1
08:10:38.928	Using JLink version: JLink_V7.88i
08:10:39.014	Installed JLink version does not match the provided version (V7.80c)
08:10:39.747	Getting serialport options from persistent store 000960072311.pc-nrfconnect-cellularmonitor
08:10:47.948	Selected device with s/n 000960072311
08:10:47.986	Opened port with options: {"path":"/dev/ttyACM0","baudRate":115200}
08:10:48.002	Device is in line mode.
08:10:52.861	Detected trace database version 1.3.3
08:10:52.883	Started tracefile
08:11:21.073	Error when creating trace: port closed: Resource temporarily unavailable plugin path: /home/flatus/.nrfconnect-apps/node_modules/pc-nrfconnect-cellularmonitor/node_modules/@nordicsemiconductor/nrf-monitor-lib-js/Release/linux-x64/nrfml-insight-source.nrfml
08:11:47.998	Deselected device
08:11:47.999	Closing device
08:12:20.326	Getting serialport options from persistent store 000960072311.pc-nrfconnect-cellularmonitor
08:12:20.335	Getting serialport options from persistent store 000960072311.pc-nrfconnect-cellularmonitor
08:12:27.435	Selected device with s/n 000960072311
08:12:27.465	Opened port with options: {"path":"/dev/ttyACM0","baudRate":115200}
08:12:27.469	Device is in line mode.
08:12:30.649	Detected trace database version 1.3.3
08:12:30.670	Started tracefile
08:15:54.372	Error when creating trace: port closed: Resource temporarily unavailable plugin path: /home/flatus/.nrfconnect-apps/node_modules/pc-nrfconnect-cellularmonitor/node_modules/@nordicsemiconductor/nrf-monitor-lib-js/Release/linux-x64/nrfml-insight-source.nrfml

[Capt. Flatus O'Flaherty]

I just created a second device on AWS to check I'd followed instructions properly. All good, except there's no mention of where to put the certificates and policy, but presumably they need to go in the certs folder: ~/ncs/v2.4.0/nrf/samples/nrf9160/aws_iot/certs    ????