I am using 'curl' on a Linux server in a script to generate REST API calls to each of the ESP32's every second just as an endurance test. I let these tests run simultaneously against each ESP32. I am sending requests to one ESP32 every second and the other every two seconds (half the rate).
The ESP32s respond fine to the REST API calls for a several hours (8 to 18) and then suddenly and simultaneously stop responding to any requests. Neither do they respond to 'ping'. I reset the ESP32s and they will start responding again with no changes to the client side (Linux test tool).
I finally did capture an error that appears on the console when the error occurs (IP stops responding):
Code: Select all
I (10605501) wifi:state: run -> init (ec0)
I (10605501) wifi:pm stop, total sleep time: 9582020957 us / 10604598223 us
I (10605501) wifi:new:<11,0>, old:<11,0>, ap:<255,255>, sta:<11,0>, prof:1
W (10605511) httpd_txrx: httpd_sock_err: error in recv : 113
Has anyone encountered this before? I've done a lot of searching and have found one or two similar problems, but they were occurring within 10 or 15 minutes. In that case the issue has something to do with NetBIOS. Since I have Windows clients on my network, some mysterious network activities may be occurring.