aws_iot: getaddrinfo, error -11 AssetTrackerV2

[Paul Oberauer]

Hello, I am using the Asset TrackerV2 application (SDK 1.7.1) with the modem firmware (mfw_nrf9160_1.3.1). Recently the following error <err> aws_iot: getaddrinfo, error -11 and <err> aws_iot: client_broker_init, error: -10 is displayed. What could be the problem here?
Previously there was never a problem and I was able to send the data to AWS.

I use the sim card from ibasis and there is enough data. Also lte-m is available at my location. I also tried to configure the modem manually via lte-link monitor, with the same result.

Thanks in advance

2022-03-31T05:40:24.826Z INFO Application data folder: C:\Users\pauli\AppData\Roaming\nrfconnect\pc-nrfconnect-linkmonitor
2022-03-31T05:40:24.984Z DEBUG App pc-nrfconnect-linkmonitor v2.0.0 official
2022-03-31T05:40:24.984Z DEBUG App path: C:\Users\pauli\.nrfconnect-apps\node_modules\pc-nrfconnect-linkmonitor
2022-03-31T05:40:24.984Z DEBUG nRFConnect 3.10.0, required by the app is (^3.8.0)
2022-03-31T05:40:24.984Z DEBUG nRFConnect path: C:\Users\pauli\AppData\Local\Programs\nrfconnect\resources\app.asar
2022-03-31T05:40:24.985Z DEBUG HomeDir: C:\Users\pauli
2022-03-31T05:40:24.985Z DEBUG TmpDir: C:\Users\pauli\AppData\Local\Temp
2022-03-31T05:40:28.505Z INFO Modem port is opened
2022-03-31T05:40:28.520Z DEBUG modem >> AT+CFUN?
2022-03-31T05:40:28.531Z DEBUG modem << +CFUN: 1
2022-03-31T05:40:28.536Z DEBUG modem << OK
2022-03-31T05:40:28.572Z DEBUG modem >> AT+CGSN=1
2022-03-31T05:40:28.581Z DEBUG modem << +CGSN: "352656101082595"
2022-03-31T05:40:28.585Z DEBUG modem << OK
2022-03-31T05:40:28.590Z DEBUG modem >> AT+CGMI
2022-03-31T05:40:28.600Z DEBUG modem << Nordic Semiconductor ASA
2022-03-31T05:40:28.605Z DEBUG modem << OK
2022-03-31T05:40:28.611Z DEBUG modem >> AT+CGMM
2022-03-31T05:40:28.619Z DEBUG modem << nRF9160-SICA
2022-03-31T05:40:28.621Z DEBUG modem << OK
2022-03-31T05:40:28.626Z DEBUG modem >> AT+CGMR
2022-03-31T05:40:28.634Z DEBUG modem << mfw_nrf9160_1.3.1
2022-03-31T05:40:28.637Z DEBUG modem << OK
2022-03-31T05:40:28.640Z INFO Nordic Semiconductor ASA nRF9160-SICA [mfw_nrf9160_1.3.1] SerNr: 352656101082595
2022-03-31T05:40:28.641Z DEBUG modem >> AT+CEMODE?
2022-03-31T05:40:28.650Z DEBUG modem << +CEMODE: 2
2022-03-31T05:40:28.654Z DEBUG modem << OK
2022-03-31T05:40:28.668Z DEBUG modem >> AT%XCBAND=?
2022-03-31T05:40:28.680Z DEBUG modem << %XCBAND: (1,2,3,4,5,8,12,13,18,19,20,25,26,28,66)
2022-03-31T05:40:28.683Z DEBUG modem << OK
2022-03-31T05:40:28.707Z DEBUG modem >> AT+CMEE?
2022-03-31T05:40:28.715Z DEBUG modem << +CMEE: 0
2022-03-31T05:40:28.717Z DEBUG modem << OK
2022-03-31T05:40:28.720Z DEBUG modem >> AT+CMEE=1
2022-03-31T05:40:28.728Z DEBUG modem << OK
2022-03-31T05:40:28.733Z DEBUG modem >> AT+CNEC?
2022-03-31T05:40:28.740Z DEBUG modem << +CNEC: 0
2022-03-31T05:40:28.743Z DEBUG modem << OK
2022-03-31T05:40:28.751Z DEBUG modem >> AT+CNEC=24
2022-03-31T05:40:28.758Z DEBUG modem << OK
2022-03-31T05:40:28.761Z DEBUG modem >> AT+CGEREP?
2022-03-31T05:40:28.770Z DEBUG modem << +CGEREP: 0,0
2022-03-31T05:40:28.772Z DEBUG modem << OK
2022-03-31T05:40:28.775Z DEBUG modem >> AT+CGDCONT?
2022-03-31T05:40:28.782Z DEBUG modem << OK
2022-03-31T05:40:28.786Z DEBUG modem >> AT+CGACT?
2022-03-31T05:40:28.796Z DEBUG modem << OK
2022-03-31T05:40:28.802Z DEBUG modem >> AT+CGEREP=1
2022-03-31T05:40:28.814Z DEBUG modem << OK
2022-03-31T05:40:28.818Z DEBUG modem >> AT+CIND=1,1,1
2022-03-31T05:40:28.830Z DEBUG modem << OK
2022-03-31T05:40:28.842Z DEBUG modem >> AT+CEREG=5
2022-03-31T05:40:28.850Z DEBUG modem << OK
2022-03-31T05:40:28.856Z DEBUG modem >> AT+CEREG?
2022-03-31T05:40:28.864Z DEBUG modem << +CEREG: 5,4
2022-03-31T05:40:28.866Z DEBUG modem << OK
2022-03-31T05:40:28.880Z DEBUG modem >> AT%CESQ=1
2022-03-31T05:40:28.887Z DEBUG modem << OK
2022-03-31T05:40:28.892Z DEBUG modem >> AT+CESQ
2022-03-31T05:40:28.902Z DEBUG modem << +CESQ: 99,99,255,255,255,255
2022-03-31T05:40:28.905Z DEBUG modem << OK
2022-03-31T05:40:28.921Z DEBUG modem >> AT%XSIM=1
2022-03-31T05:40:28.929Z DEBUG modem << OK
2022-03-31T05:40:28.933Z DEBUG modem >> AT%XSIM?
2022-03-31T05:40:28.941Z DEBUG modem << %XSIM: 1
2022-03-31T05:40:28.943Z DEBUG modem << OK
2022-03-31T05:40:28.962Z DEBUG modem >> AT+CPIN?
2022-03-31T05:40:28.969Z DEBUG modem << +CPIN: READY
2022-03-31T05:40:28.970Z DEBUG modem << OK
2022-03-31T05:40:28.981Z DEBUG modem >> AT+CPINR="SIM PIN"
2022-03-31T05:40:28.996Z DEBUG modem << +CPINR: "SIM PIN",3
2022-03-31T05:40:28.999Z DEBUG modem << OK
2022-03-31T05:40:29.016Z DEBUG modem >> AT+CIMI
2022-03-31T05:40:29.026Z DEBUG modem << 204080813563652
2022-03-31T05:40:29.028Z DEBUG modem << OK
2022-03-31T05:40:29.030Z INFO IMSIdentity: 204080813563652
2022-03-31T05:40:50.815Z DEBUG modem << %CESQ: 22,1,1,0
2022-03-31T05:40:50.839Z DEBUG modem << +CEREG: 2,"36D9","00A4F129",7
2022-03-31T05:40:50.850Z DEBUG modem << [00:01:11.988,555] [0m<inf> event_manager: MODEM_EVT_LTE_DISCONNECTED[0m
2022-03-31T05:40:50.852Z DEBUG modem << [00:01:11.995,758] [0m<inf> event_manager: MODEM_EVT_LTE_CELL_UPDATE[0m
2022-03-31T05:40:51.070Z DEBUG modem << +CSCON: 1
2022-03-31T05:40:53.725Z DEBUG modem << +CGEV: ME PDN ACT 0,0
2022-03-31T05:40:53.745Z DEBUG modem << +CNEC_ESM: 50,0
2022-03-31T05:40:53.763Z DEBUG modem >> AT+CGDCONT?
2022-03-31T05:40:53.766Z DEBUG modem << +CEREG: 5,"36D9","00A4F129",7,,,"00001010","00100001"
2022-03-31T05:40:53.769Z DEBUG modem << [00:01:14.871,185] [0m<inf> event_manager: MODEM_EVT_LTE_CONNECTED[0m
2022-03-31T05:40:53.771Z DEBUG modem << [00:01:14.878,143] [0m<inf> event_manager: MODEM_EVT_LTE_PSM_UPDATE[0m
2022-03-31T05:40:53.773Z DEBUG modem << +CIND: "service",1
2022-03-31T05:40:53.774Z DEBUG modem << +CIND: "roam",1
2022-03-31T05:40:53.775Z DEBUG modem << [00:01:14.888,671] [1;33m<wrn> cloud_module: Cloud connection establishment in progress[0m
2022-03-31T05:40:53.776Z DEBUG modem << [00:01:14.896,728] [1;33m<wrn> cloud_module: New connection attempt in 32 seconds if not successful[0m
2022-03-31T05:40:53.777Z DEBUG modem << [00:01:14.906,036] [0m<inf> event_manager: CLOUD_EVT_CONNECTING[0m
2022-03-31T05:40:53.788Z DEBUG modem << +CGDCONT: 0,"IP","IBASIS.IOT","10.160.51.3",0,0
2022-03-31T05:40:53.790Z DEBUG modem << OK
2022-03-31T05:40:53.798Z DEBUG modem >> AT+CGACT?
2022-03-31T05:40:53.809Z DEBUG modem << +CGACT: 0,1
2022-03-31T05:40:53.811Z DEBUG modem << OK
2022-03-31T05:40:56.980Z DEBUG modem << %CESQ: 24,1,6,0
2022-03-31T05:41:17.436Z DEBUG modem << +CEREG: 5,"36D9","003E392B",7,,,"00001010","00100001"
2022-03-31T05:41:17.471Z DEBUG modem >> AT+COPS=3,2
2022-03-31T05:41:17.477Z DEBUG modem << [00:01:38.617,126] [0m<inf> event_manager: MODEM_EVT_LTE_CELL_UPDATE[0m
2022-03-31T05:41:17.481Z DEBUG modem << OK
2022-03-31T05:41:17.485Z DEBUG modem >> AT+COPS?
2022-03-31T05:41:17.495Z DEBUG modem << +COPS: 0,2,"23203",7
2022-03-31T05:41:17.497Z DEBUG modem << OK
2022-03-31T05:41:17.504Z DEBUG modem >> AT%XCBAND
2022-03-31T05:41:17.511Z DEBUG modem << %XCBAND: 8
2022-03-31T05:41:17.513Z DEBUG modem << OK
2022-03-31T05:41:17.532Z DEBUG modem >> AT+CGDCONT?
2022-03-31T05:41:17.543Z DEBUG modem << +CGDCONT: 0,"IP","IBASIS.IOT","10.160.51.3",0,0
2022-03-31T05:41:17.544Z DEBUG modem << OK
2022-03-31T05:41:17.551Z DEBUG modem >> AT+CGACT?
2022-03-31T05:41:17.559Z DEBUG modem << +CGACT: 0,1
2022-03-31T05:41:17.560Z DEBUG modem << OK
2022-03-31T05:41:23.747Z DEBUG modem << [00:01:44.915,496] [1;31m<err> aws_iot: getaddrinfo, error -11[0m
2022-03-31T05:41:23.751Z DEBUG modem << [00:01:44.921,447] [1;31m<err> aws_iot: client_broker_init, error: -10[0m
2022-03-31T05:41:23.754Z DEBUG modem << [00:01:44.928,192] [0m<inf> event_manager: CLOUD_EVT_CONNECTING[0m
2022-03-31T05:41:25.748Z DEBUG modem << [00:01:46.906,066] [0m<inf> event_manager: CLOUD_EVT_CONNECTION_TIMEOUT[0m
2022-03-31T05:41:25.752Z DEBUG modem << [00:01:46.913,177] [1;33m<wrn> cloud_module: Cloud connection establishment in progress[0m
2022-03-31T05:41:25.756Z DEBUG modem << [00:01:46.921,234] [1;33m<wrn> cloud_module: New connection attempt in 64 seconds if not successful[0m
2022-03-31T05:41:25.767Z DEBUG modem << [00:01:46.930,541] [0m<inf> event_manager: CLOUD_EVT_CONNECTING[0m
2022-03-31T05:41:39.090Z DEBUG modem << [00:02:00.258,331] [0m<inf> event_manager: APP_EVT_DATA_GET_ALL[0m
2022-03-31T05:41:39.098Z DEBUG modem << [00:02:00.264,984] [0m<inf> event_manager: APP_EVT_DATA_GET - Requested data types (MOD_DYN, BAT, ENV, NEIGHBOR_CELLS, GNSS, MOD_STAT)[0m
2022-03-31T05:41:39.125Z DEBUG modem << [00:02:00.284,942] [0m<inf> event_manager: GPS_EVT_ACTIVE[0m
2022-03-31T05:41:39.128Z DEBUG modem << [00:02:00.291,046] [0m<inf> event_manager: GPS_EVT_AGPS_NEEDED[0m
2022-03-31T05:41:39.130Z DEBUG modem << [00:02:00.301,116] [0m<inf> event_manager: SENSOR_EVT_ENVIRONMENTAL_DATA_READY[0m
2022-03-31T05:41:39.193Z DEBUG modem << [00:02:00.374,786] [0m<inf> event_manager: MODEM_EVT_MODEM_STATIC_DATA_READY[0m
2022-03-31T05:41:39.210Z DEBUG modem << [00:02:00.386,535] [0m<inf> event_manager: DATA_EVT_AGPS_REQUEST_DATA_SEND[0m
2022-03-31T05:41:39.247Z DEBUG modem << [00:02:00.428,802] [0m<inf> event_manager: MODEM_EVT_MODEM_DYNAMIC_DATA_READY[0m
2022-03-31T05:41:39.289Z DEBUG modem << [00:02:00.471,221] [0m<inf> event_manager: MODEM_EVT_BATTERY_DATA_READY[0m
2022-03-31T05:41:39.310Z DEBUG modem << %NCELLMEAS: 0,"003E392B","23203","36D9",143,3475,359,27,14,120273,3475,0,21,2,0,3475,151,20,-1,0,119655
2022-03-31T05:41:39.314Z DEBUG modem << [00:02:00.489,837] [0m<inf> event_manager: MODEM_EVT_NEIGHBOR_CELLS_DATA_READY[0m
2022-03-31T05:41:40.299Z DEBUG modem << %CESQ: 21,1,1,0
2022-03-31T05:41:55.769Z DEBUG modem << [00:02:16.939,086] [1;31m<err> aws_iot: getaddrinfo, error -11[0m
2022-03-31T05:41:55.772Z DEBUG modem << [00:02:16.944,976] [1;31m<err> aws_iot: client_broker_init, error: -10[0m
2022-03-31T05:41:55.774Z DEBUG modem << [00:02:16.951,721] [0m<inf> event_manager: CLOUD_EVT_CONNECTING[0m
2022-03-31T05:42:03.525Z DEBUG modem << +CSCON: 0
2022-03-31T05:42:24.550Z DEBUG modem << %CESQ: 255,0,255,0
2022-03-31T05:42:29.773Z DEBUG modem << [00:02:50.930,572] [0m<inf> event_manager: CLOUD_EVT_CONNECTION_TIMEOUT[0m
2022-03-31T05:42:29.777Z DEBUG modem << [00:02:50.937,683] [1;33m<wrn> cloud_module: Cloud connection establishment in progress[0m
2022-03-31T05:42:29.780Z DEBUG modem << [00:02:50.945,739] [1;33m<wrn> cloud_module: New connection attempt in 128 seconds if not successful[0m
2022-03-31T05:42:29.783Z DEBUG modem << [00:02:50.955,139] [0m<inf> event_manager: CLOUD_EVT_CONNECTING[0m
2022-03-31T05:42:29.865Z DEBUG modem << %CESQ: 23,1,6,0
2022-03-31T05:42:30.656Z DEBUG modem << +CSCON: 1
2022-03-31T05:42:30.660Z DEBUG modem << %CESQ: 19,0,0,0
2022-03-31T05:42:54.113Z DEBUG modem << [00:03:15.297,943] [0m<inf> event_manager: DATA_EVT_DATA_READY[0m
2022-03-31T05:42:59.795Z DEBUG modem << [00:03:20.965,606] [1;31m<err> aws_iot: getaddrinfo, error -11[0m
2022-03-31T05:42:59.798Z DEBUG modem << [00:03:20.971,496] [1;31m<err> aws_iot: client_broker_init, error: -10[0m
2022-03-31T05:42:59.801Z DEBUG modem << [00:03:20.978,302] [0m<inf> event_manager: CLOUD_EVT_CONNECTING[0m
2022-03-31T05:43:07.922Z DEBUG modem << +CSCON: 0
2022-03-31T05:43:08.086Z DEBUG modem << %CESQ: 21,1,5,0
2022-03-31T05:43:09.372Z DEBUG modem << %CESQ: 17,0,0,0

[Markus Tacker (he/him)]

Please double check that the SIM card you are using has enough data, we see this typically when this is not the case.

[Waqar Ahmed]

I am facing issue,
Suddenly the device giving the same error. after month change  also the sim have enough data package. Even i reboot the devices.in our fleet two of the device got this problem from 1 April.

[Markus Tacker (he/him)]

This shouldn't happen. Please create a new private DevZone case and provide the ICCID of your SIMs so our support can investigate.

[Waqar Ahmed]

Thanks,
I am not using i basis sim. Although i change the sim now it is connecting and working.

but the sim give this problem is not working still I have enough data.
Thanks

  

[Markus Tacker (he/him)]

Ok, in that case please contact the vendor of your SIM.