http request fails if server takes at least 3 seconds to start responding

RE: http request fails if server takes at least 3 seconds to start responding

Alex Fickle — Mon, 24 Apr 2023 16:44:16 GMT

Thanks, I'll get a trace next time it starts to fail.

In the meantime I've verified that http timeouts do not work with Zephyr's HTTP library due to lack of support for zsock_shutdown(). This combined with the lack of TCP keepalive support make me think that the connection is getting dropped by the network causing the test application to block forever on what it thinks is a working connection.

Adding the below snippet prevents this.

timeval timeoutVal;
timeoutVal.tv_sec = timeoutSeconds;
timeoutVal.tv_usec = 0;
const int ret = zsock_setsockopt(sock, SOL_SOCKET, SO_RCVTIMEO, &timeoutVal, sizeof(timeoutVal));

RE: http request fails if server takes at least 3 seconds to start responding

Hakon — Mon, 24 Apr 2023 11:35:10 GMT

Modem team;

%XMODEMTRACE AT command should be used to set traces:

AT%XMODEMTRACE=0
AT%XMODEMTRACE=1,2
AT+CFUN=0

Then we need modem trace file started from socket connection to data transfer failure.

RE: http request fails if server takes at least 3 seconds to start responding

Hakon — Thu, 13 Apr 2023 11:46:57 GMT

I will ask the modem team if there is anything that can be done to achieve this.

RE: http request fails if server takes at least 3 seconds to start responding

Alex Fickle — Tue, 11 Apr 2023 18:53:59 GMT

I've attached a trace file from a successful run with a 5 second delay. The modem is currently in a run of operating as expected after not working for three days. Let me know if I should change any build options to enable more trace output, I did not see any options from this besides CONFIG_NRF_MODEM_LIB_TRACE_LEVEL_FULL which seems to be defaulting as enabled.

devzone.nordicsemi.com/.../trace_2D00_2023_2D00_04_2D00_11T18_2D00_44_2D00_00.399Z.bin

RE: http request fails if server takes at least 3 seconds to start responding

Hakon — Tue, 11 Apr 2023 13:48:30 GMT

Here is the response from the modem team;

I don't see any problem with modem's operation in attached modem trace file. Maybe more trace groups should be activated and then take new log with socket open and connect and then data transfer.

From attached modem trace file I can find only two TCP ACK DL packets form server to UE, no other data transmissions.

RE: http request fails if server takes at least 3 seconds to start responding

Hakon — Wed, 05 Apr 2023 11:48:54 GMT

Thanks. I have notified the modem team.

RE: http request fails if server takes at least 3 seconds to start responding

Alex Fickle — Mon, 03 Apr 2023 21:38:34 GMT

It just started failing again, I am attaching a trace.devzone.nordicsemi.com/.../trace_2D00_2023_2D00_04_2D00_03T21_2D00_35_2D00_52.556Z.bin

RE: http request fails if server takes at least 3 seconds to start responding

Alex Fickle — Tue, 21 Mar 2023 20:59:00 GMT

It might be a day or so before I am able to replicate again, but I'll get another trace when I can. The device has started to go on a run of working well which it does occasionally. No idea what causes this. It started working when I let it sit in a failure loop overnight when there was no one near it. Since then it has been working all day even when I reprogram it.

RE: http request fails if server takes at least 3 seconds to start responding

Hakon — Tue, 21 Mar 2023 16:00:32 GMT

I tried to decode the trace, and it's almost empty. Could you try to do another trace?

RE: http request fails if server takes at least 3 seconds to start responding

Alex Fickle — Tue, 21 Mar 2023 14:55:31 GMT

Here is a trace with it failing.

devzone.nordicsemi.com/.../3465.failure_2D00_trace.bin

RE: http request fails if server takes at least 3 seconds to start responding

Hakon — Tue, 21 Mar 2023 10:06:25 GMT

I tried with HTTP_DELAY 3, and I still get a successful HTTP GET. Can you try to do a modem trace when it is not working?

RE: http request fails if server takes at least 3 seconds to start responding

Hakon — Mon, 20 Mar 2023 14:52:45 GMT

Hello,

I'm taking over for Jonathan. I will try to reproduce this.

RE: http request fails if server takes at least 3 seconds to start responding

Alex Fickle — Wed, 15 Mar 2023 15:41:34 GMT

Minor update, there was a bug in the output of the cell signal strength in the above logs. The real signal strength was -77 dBm for the failure case and -74 dBm for the success case. Should not change much as these are both excellent values.

RE: http request fails if server takes at least 3 seconds to start responding

JONATHAN LL — Mon, 13 Mar 2023 16:43:20 GMT

Hi,

Will look in to this and get back to you.

Note: If you put all the files in a compressed folder like zip file then it will be accepted.

Regards,
Jonathan

RE: http request fails if server takes at least 3 seconds to start responding

Alex Fickle — Sat, 11 Mar 2023 05:41:20 GMT

devzone.nordicsemi.com/.../failure_2D00_trace.bin devzone.nordicsemi.com/.../failure_2D00_log.txt devzone.nordicsemi.com/.../success_2D00_trace.bin devzone.nordicsemi.com/.../success_2D00_log.txt

RE: http request fails if server takes at least 3 seconds to start responding

Alex Fickle — Sat, 11 Mar 2023 05:40:42 GMT

Looks like attaching the prg.conf is what caused creating the post to fail, inserting the as code snippets instead.

prj.conf:

# bootloader
CONFIG_BOOTLOADER_MCUBOOT=y

# C++
CONFIG_CPLUSPLUS=y
CONFIG_STD_CPP17=y
CONFIG_LIB_CPLUSPLUS=y

# libc
CONFIG_NEWLIB_LIBC=y
CONFIG_NEWLIB_LIBC_FLOAT_PRINTF=y
CONFIG_NEWLIB_LIBC_NANO=n

# logging
CONFIG_LOG=y
CONFIG_LOG_MODE_DEFERRED=y
CONFIG_LOG_BUFFER_SIZE=16384
CONFIG_NRF_MODEM_LOG=y
CONFIG_NRF_MODEM_LIB_LOG_LEVEL_DBG=y
CONFIG_LTE_LINK_CONTROL_LOG_LEVEL_DBG=y
CONFIG_PDN_LOG_LEVEL_DBG=y
CONFIG_DATE_TIME_LOG_LEVEL_DBG=y
CONFIG_MODEM_KEY_MGMT_LOG_LEVEL_DBG=y
CONFIG_NET_LOG=y
CONFIG_NET_HTTP_LOG_LEVEL_DBG=y

# trace
CONFIG_NRF_MODEM_LIB_TRACE=y
CONFIG_NRF_MODEM_LIB_TRACE_BACKEND_UART_SYNC=y

# networking
CONFIG_NETWORKING=y
CONFIG_NET_SOCKETS=y
CONFIG_NET_SOCKETS_POSIX_NAMES=y
CONFIG_NET_NATIVE=n
CONFIG_MODEM_KEY_MGMT=y
CONFIG_NRF_MODEM_LIB=y
CONFIG_LTE_LINK_CONTROL=y
CONFIG_LTE_NETWORK_MODE_LTE_M=y
CONFIG_LTE_NETWORK_USE_FALLBACK=n
CONFIG_PDN=y
CONFIG_PDN_DEFAULTS_OVERRIDE=y
CONFIG_PDN_DEFAULT_AUTH_CHAP=y
CONFIG_PDN_DEFAULT_APN="pelion"
CONFIG_PDN_DEFAULT_USERNAME="default"
CONFIG_PDN_DEFAULT_PASSWORD="void"

# network auto connecting
CONFIG_NRF_MODEM_LIB_SYS_INIT=y
# TODO: test if below is needed in latest SDK version, was needed in v2.0.0
CONFIG_PDN_INIT_PRIORITY=89
CONFIG_LTE_AUTO_INIT_AND_CONNECT=n

# date time library
CONFIG_DATE_TIME=y
CONFIG_DATE_TIME_NTP=n
CONFIG_DATE_TIME_MODEM=y
CONFIG_DATE_TIME_AUTO_UPDATE=y

# modem info library
CONFIG_MODEM_INFO=y
CONFIG_MODEM_INFO_ADD_SIM=n
CONFIG_MODEM_INFO_ADD_DEVICE=y
CONFIG_MODEM_INFO_ADD_DATE_TIME=n
CONFIG_MODEM_INFO_ADD_NETWORK=y

# http
CONFIG_HTTP_CLIENT=y

# main thread
CONFIG_MAIN_THREAD_PRIORITY=3
CONFIG_MAIN_STACK_SIZE=4096

# debug options
CONFIG_DEBUG=n
CONFIG_DEBUG_COREDUMP=y
CONFIG_DEBUG_COREDUMP_BACKEND_LOGGING=y
CONFIG_DEBUG_COREDUMP_MEMORY_DUMP_MIN=n

CONFIG_RESET_ON_FATAL_ERROR=n
CONFIG_REBOOT=y

devzone.nordicsemi.com/.../3463.main.cpp devzone.nordicsemi.com/.../2476.CMakeLists.txt