search

espressif / esp-idf

Espressif IoT Development Framework. Official development framework for Espressif SoCs.
Apache License 2.0
13.91k stars 7.33k forks source link

TCP & ICMP Fail, UDP and WiFi still connected (IDFGH-3916) #5810

Closed gadget-man closed 3 years ago

gadget-man commented 4 years ago

Problem Description: I have approx. 200 devices deployed in production, all with identical (custom) PCB using the Wrover-IB module. Of these, 5-8 devices consistently have an issue where they very regularly disconnect from MQTT / TCP connections - usually at a pretty regular interval. The other 190ish devices are very stable and disconnect once every 2-3 days (probably due to the local environment)

What is particularly strange about the problem is that when the device disconnects, I continue to be able to see full logging over UDP (including the ESP_LOG wifi: debug logging). However ICMP ping to the local router or a DNS server starts to timeout, and shortly thereafter an MQTT ping also fails. The only way to recover is to force a reboot of the device (via an MQTT watchdog timer), and on reboot the device will immediately reconnect.

Here is an example output from a graphical dashboard showing the frequency of disconnects for this particular device:

Screenshot 2020-08-29 at 20 52 21

Here is an output from the log showing the disconnect event until my timeout eventually forces a reboot - note there are no wifi: debugs logs shown here, but I know the wifi: logging is working as at 19:08 I can see a wifi:obss scan is disabled in my logs. https://pastebin.com/qUGqta5a

What could be causing my device to drop ICMP and TCP connection even though UDP is still active (it's a remote device so my only way to get the logs is via remote UDP logging)?

Alvin1Zhang commented 4 years ago

Thanks for reporting, and sorry for the inconvenience, we will look into.

david-cermak commented 4 years ago

Hi @gadget-man

What I can see from the logs is that the UDP packets are delivered inside the local network, but the ICMP to 8.8.8.8 timeouts and resolving of a AWS host name fails, which just seems like the connection to your local network works okay, but fails to route any further. I think you can easily track the packets from ESP32 on the 192.168.1.254 (your local gateway I assume) to see if the pings to 8.8.8.8 get delivered to your local network at lease and if ICMP replies to those packet are available (the same for DNS queries)

gadget-man commented 4 years ago

Thanks. As a test, I also tried changing the ping from 8.8.8.8 to the IP address of the local gateway, the same issue occurs, so the ping will also fail when trying to ping the local router.

david-cermak commented 4 years ago

Ah, okay. In that case, could you please check for the packets and the replies on the local network? And at the same time check if the replies are delivered to the ESP32. You can enable IP and ICMP debugging in the lwip by setting:

#define IP_DEBUG                        LWIP_DBG_ON
#define ICMP_DEBUG                      LWIP_DBG_ON

You could see the logs similar to the below:

ip_input: iphdr->dest 0x100000a netif->ip_addr 0x100000a (0xa, 0xa, 0x1000000)0a-00-00-02-0a-00-00-01-08-00-f7-fd-00-01-00-01
ip4_input: packet accepted on interface st
ip4_input:
IP header:
+-------------------------------+
| 4 | 5 |  0x00 |        28     | (v, hl, tos, len)
+-------------------------------+
|        0      |000|       0   | (id, flags, offset)
+-------------------------------+
|  255  |    1  |    0xa7de     | (ttl, proto, chksum)
+-------------------------------+
|   10  |    0  |    0  |    2  | (src)
+-------------------------------+
|   10  |    0  |    0  |    1  | (dest)
+-------------------------------+
ip4_input: p->len 28 p->tot_len 28
icmp_input: ping

Which might help indicate on which level the packet was dropped (if received)

The only guess at this point on what might cause dropping some packets while processing others (plain UDP) would be shortage of heap? Could you please check for that as well?

Also could you please share the version of IDF you use, the v3.4-r5 is not a recognized version.

gadget-man commented 4 years ago

OK thanks. I'll try and turn on the additional debugging and also do some logging of available heap to see if it gives any clues.

Regards the IDF - I'm using mongoose-os which uses a seperate fork of the ESP-IDF here: https://github.com/cesanta/esp-idf. Last commit was https://github.com/cesanta/esp-idf/commit/fb7ba1baa068a2267ef54b7105cf3c8a004fe4eb

gadget-man commented 4 years ago

Question - bearing in mind I'm using Wrover-IB with 4mb SPIRAM, should I be reporting on any particular memory capability (e.g. does the ICMP call use only internal ram?)

david-cermak commented 4 years ago

should I be reporting on any particular memory capability

This depends on the configuration. You can quickly look at components/lwip/lwip/src/core/mem.c for a definition of mem_malloc(), this depends on config values such as CONFIG_WIFI_LWIP_ALLOCATION_FROM_SPIRAM_FIRST (may be called differently in different idf versions)

gadget-man commented 4 years ago

Thanks. I am indeed using CONFIG_WIFI_LWIP_ALLOCATION_FROM_SPIRAM_FIRST. I'll report on both MALLOC_CAP_INTERNAL and MALLOC_CAP_SPIRAM whenever I get a ICMP ping timeout and see whether it gives any clues.

gadget-man commented 4 years ago

I've had clarification from the team at mongoose-os, they are using https://github.com/mongoose-os/esp-idf/commits/3.3-r6 - it's based on espressif/esp-idf@bf02206 with patches on top

gadget-man commented 4 years ago

@david-cermak I haven't yet managed to get the ICMP debug turned on as it causes a crash loop when the mongoose-os UDP logging starts up before wifi is connected, however I have managed to check the heap when the ping timeout starts:

`[Sep 11 09:18:57.889] iParcelBox-30AEA4C6F1C8 3091 12260.507 2 2|pn_ping.c:44 PING From 8.8.8.8 icmp_seq=1226 timeout [Sep 11 09:18:57.900] iParcelBox-30AEA4C6F1C8 3092 12260.525 2 2|pn_ping.c:47 MemReport: intenal_free: 157784, internal_min_free: 129112, internal_free_block: 49544, psram_free: 4157328, psram_min_free: 4126476, psram_free_block: 4124560

[Sep 11 09:19:05.949] iParcelBox-30AEA4C6F1C8 3093 12268.516 2 3|mg_mqtt.c:192 Send PINGREQ [Sep 11 09:19:07.871] iParcelBox-30AEA4C6F1C8 3094 12270.507 2 2|pn_ping.c:44 PING From 8.8.8.8 icmp_seq=1227 timeout [Sep 11 09:19:07.884] iParcelBox-30AEA4C6F1C8 3095 12270.525 2 2|pn_ping.c:47 MemReport: intenal_free: 157784, internal_min_free: 129112, internal_free_block: 49544, psram_free: 4155764, psram_min_free: 4126476, psram_free_block: 4124560`

I'm capturing both MALLOC_CAP_INTERNAL and MALLOC_CAP_SPIRAM. To me, this looks as though it isn't a heap problem?

david-cermak commented 4 years ago

@gadget-man Agree, that it looks like this is not a heap problem.

gadget-man commented 4 years ago

@david-cermak is there anything else we can do to try to get to the bottom of this problem - it is now occurring on further devices as more customers connect their products to the network.

gadget-man commented 4 years ago

Here's a further log from another device - log captured remotely over UDP, showing similar behaviour:

gadget-man commented 4 years ago

[Oct 17 08:46:44.790] iParcelBox-30AEA4C6F1C8 1557 705.332 2 2|pn_ping.c:36 PING 64 bytes from 192.168.0.1 icmp_seq=69 ttl=64 time=1 ms [Oct 17 08:46:51.780] iParcelBox-30AEA4C6F1C8 1558 712.327 2 3|mg_mqtt.c:192 Send PINGREQ [Oct 17 08:46:51.780] iParcelBox-30AEA4C6F1C8 1559 712.366 2 3|mg_mqtt.c:174 Recv PINGRESP [Oct 17 08:46:51.780] iParcelBox-30AEA4C6F1C8 1560 712.372 2 3|mgos_mqtt_conn.c:219 MQTT0 event: 213 [Oct 17 08:46:54.751] iParcelBox-30AEA4C6F1C8 1561 715.332 2 2|pn_ping.c:36 PING 64 bytes from 192.168.0.1 icmp_seq=70 ttl=64 time=2 ms [Oct 17 08:47:04.783] iParcelBox-30AEA4C6F1C8 1562 725.334 2 2|pn_ping.c:36 PING 64 bytes from 192.168.0.1 icmp_seq=71 ttl=64 time=4 ms [Oct 17 08:47:06.016] iParcelBox-30AEA4C6F1C8 1563 726.297 2 2|D (726452) wifi:obss scan is disabled [Oct 17 08:47:06.016] iParcelBox-30AEA4C6F1C8 1564 726.302 2 2|D (726452) wifi:start obss scan: obss scan is stopped [Oct 17 08:47:14.818] iParcelBox-30AEA4C6F1C8 1565 735.333 2 2|pn_ping.c:36 PING 64 bytes from 192.168.0.1 icmp_seq=72 ttl=64 time=3 ms [Oct 17 08:47:25.774] iParcelBox-30AEA4C6F1C8 1566 746.327 2 2|pn_ping.c:45 PING From 192.168.0.1 icmp_seq=73 timeout [Oct 17 08:47:25.774] iParcelBox-30AEA4C6F1C8 1567 746.346 2 2|pn_ping.c:48 MemReport: intenal_free: 150056, internal_min_free: 115312, internal_free_block: 38100, psram_free: 4156540, psram_min_free: 4126236, psram_free_block: 4127996 [Oct 17 08:47:35.718] iParcelBox-30AEA4C6F1C8 1568 756.327 2 2|pn_ping.c:45 PING From 192.168.0.1 icmp_seq=74 timeout [Oct 17 08:47:35.735] iParcelBox-30AEA4C6F1C8 1569 756.345 2 2|pn_ping.c:48 MemReport: intenal_free: 150056, internal_min_free: 115312, internal_free_block: 38100, psram_free: 4156540, psram_min_free: 4126236, psram_free_block: 4127996 [Oct 17 08:47:45.847] iParcelBox-30AEA4C6F1C8 1570 766.327 2 2|pn_ping.c:45 PING From 192.168.0.1 icmp_seq=75 timeout [Oct 17 08:47:45.847] iParcelBox-30AEA4C6F1C8 1571 766.346 2 2|pn_ping.c:48 MemReport: intenal_free: 150056, internal_min_free: 115312, internal_free_block: 38100, psram_free: 4156540, psram_min_free: 4126236, psram_free_block: 4127996 [Oct 17 08:47:51.784] iParcelBox-30AEA4C6F1C8 1572 772.337 2 3|mg_mqtt.c:192 Send PINGREQ [Oct 17 08:47:55.780] iParcelBox-30AEA4C6F1C8 1573 776.327 2 2|pn_ping.c:45 PING From 192.168.0.1 icmp_seq=76 timeout [Oct 17 08:47:55.780] iParcelBox-30AEA4C6F1C8 1574 776.346 2 2|pn_ping.c:48 MemReport: intenal_free: 150056, internal_min_free: 115312, internal_free_block: 38100, psram_free: 4154980, psram_min_free: 4126236, psram_free_block: 4127996 [Oct 17 08:48:05.814] iParcelBox-30AEA4C6F1C8 1575 786.327 2 2|pn_ping.c:45 PING From 192.168.0.1 icmp_seq=77 timeout [Oct 17 08:48:05.814] iParcelBox-30AEA4C6F1C8 1576 786.346 2 2|pn_ping.c:48 MemReport: intenal_free: 150056, internal_min_free: 115312, internal_free_block: 38100, psram_free: 4154980, psram_min_free: 4126236, psram_free_block: 4127996 [Oct 17 08:48:15.721] iParcelBox-30AEA4C6F1C8 1577 796.327 2 2|pn_ping.c:45 PING From 192.168.0.1 icmp_seq=78 timeout [Oct 17 08:48:15.736] iParcelBox-30AEA4C6F1C8 1578 796.345 2 2|pn_ping.c:48 MemReport: intenal_free: 150056, internal_min_free: 115312, internal_free_block: 38100, psram_free: 4154980, psram_min_free: 4126236, psram_free_block: 4127996 [Oct 17 08:48:25.785] iParcelBox-30AEA4C6F1C8 1579 806.327 2 2|pn_ping.c:45 PING From 192.168.0.1 icmp_seq=79 timeout [Oct 17 08:48:25.986] iParcelBox-30AEA4C6F1C8 1580 806.347 2 2|pn_ping.c:48 MemReport: intenal_free: 150056, internal_min_free: 115312, internal_free_block: 38100, psram_free: 4154980, psram_min_free: 4126236, psram_free_block: 4127996 [Oct 17 08:48:35.816] iParcelBox-30AEA4C6F1C8 1581 816.327 2 2|pn_ping.c:45 PING From 192.168.0.1 icmp_seq=80 timeout [Oct 17 08:48:35.817] iParcelBox-30AEA4C6F1C8 1582 816.346 2 2|pn_ping.c:48 MemReport: intenal_free: 150056, internal_min_free: 115312, internal_free_block: 38100, psram_free: 4154980, psram_min_free: 4126236, psram_free_block: 4127996 [Oct 17 08:48:45.750] iParcelBox-30AEA4C6F1C8 1583 826.327 2 2|pn_ping.c:45 PING From 192.168.0.1 icmp_seq=81 timeout [Oct 17 08:48:45.750] iParcelBox-30AEA4C6F1C8 1584 826.346 2 2|pn_ping.c:48 MemReport: intenal_free: 150056, internal_min_free: 115312, internal_free_block: 38100, psram_free: 4154980, psram_min_free: 4126236, psram_free_block: 4127996 [Oct 17 08:48:52.103] iParcelBox-30AEA4C6F1C8 1585 832.612 2 0|mg_ssl_if_mbedtls.c:30 0x3ffe7b44 mbedtls_ssl_flush_output() returned -78 (-0x004e) [Oct 17 08:48:52.103] iParcelBox-30AEA4C6F1C8 1586 832.621 2 0|mg_ssl_if_mbedtls.c:30 0x3ffe7b44 mbedtls_ssl_write_record() returned -78 (-0x004e) [Oct 17 08:48:52.103] iParcelBox-30AEA4C6F1C8 1587 832.630 2 0|mg_ssl_if_mbedtls.c:30 0x3ffe7b44 mbedtls_ssl_send_alert_message() returned -78 (-0x004e) [Oct 17 08:48:52.104] iParcelBox-30AEA4C6F1C8 1588 832.635 2 2|mgos_mqtt_conn.c:253 MQTT0 Disconnect [Oct 17 08:48:52.104] iParcelBox-30AEA4C6F1C8 1589 832.641 2 3|mgos_event.c:135 ev MOS5 triggered 1 handlers [Oct 17 08:48:52.104] iParcelBox-30AEA4C6F1C8 1590 832.647 2 3|mgos_event.c:135 ev MOS5 triggered 1 handlers [Oct 17 08:48:52.104] iParcelBox-30AEA4C6F1C8 1591 832.662 2 2|init.js:468 MQTT Disconnect [Oct 17 08:48:52.104] iParcelBox-30AEA4C6F1C8 1592 832.685 2 2|init.js:476 Starting MQTT Disconnect Timer: 1073642440 [Oct 17 08:48:52.104] iParcelBox-30AEA4C6F1C8 1593 832.691 2 2|mgos_mqtt_conn.c:546 MQTT0 connecting after 2191 ms [Oct 17 08:48:54.297] iParcelBox-30AEA4C6F1C8 1594 834.893 2 2|mgos_mqtt_conn.c:468 MQTT0 connecting to a24buxh69lukw9-ats.iot.eu-west-1.amazonaws.com:8883 [Oct 17 08:48:54.297] iParcelBox-30AEA4C6F1C8 1595 834.899 2 3|mgos_event.c:135 ev MOS6 triggered 1 handlers [Oct 17 08:48:54.303] iParcelBox-30AEA4C6F1C8 1596 834.914 2 3|mg_net.c:910 0x3ffe7b44 a24buxh69lukw9-ats.iot.eu-west-1.amazonaws.com:8883 aws-iParcelBox-30AEA.crt.pem,aws-iParcelBox-30AEA.key.pem,ca.pem [Oct 17 08:48:54.443] iParcelBox-30AEA4C6F1C8 1597 834.926 2 3|mgos_vfs.c:283 aws-iParcelBox-30AEA.crt.pem -> /aws-iParcelBox-30AEA.crt.pem pl 1 -> 1 0x3ffc00b4 (refs 1) [Oct 17 08:48:54.443] iParcelBox-30AEA4C6F1C8 1598 834.936 2 3|mgos_vfs_fs_spiffs.:838 aws-iParcelBox-30AEA.crt.pem -> 2UtgX+f6kfNlUiJgeGwWuDYbbagygbxrqr4IyOJ76Zg= [Oct 17 08:48:54.443] iParcelBox-30AEA4C6F1C8 1599 834.952 2 3|mgos_vfs.c:377 open aws-iParcelBox-30AEA.crt.pem 0x0 0x1b6 => 0x3ffc00b4 aws-iParcelBox-30AEA.crt.pem 1 => 257 (refs 1) [Oct 17 08:48:54.443] iParcelBox-30AEA4C6F1C8 1600 834.959 2 3|mgos_vfs.c:536 fstat 257 => 0x3ffc00b4:1 => 0 (size 1162) [Oct 17 08:48:54.443] iParcelBox-30AEA4C6F1C8 1601 834.967 2 3|mgos_vfs.c:536 fstat 257 => 0x3ffc00b4:1 => 0 (size 1162) [Oct 17 08:48:54.443] iParcelBox-30AEA4C6F1C8 1602 834.973 2 3|mgos_vfs.c:564 lseek 257 0 1 => 0x3ffc00b4:1 => 0 [Oct 17 08:48:54.443] iParcelBox-30AEA4C6F1C8 1603 834.980 2 3|mgos_vfs.c:564 lseek 257 1024 0 => 0x3ffc00b4:1 => 1024 [Oct 17 08:48:54.443] iParcelBox-30AEA4C6F1C8 1604 834.989 2 3|mgos_vfs.c:564 lseek 257 1024 0 => 0x3ffc00b4:1 => 1024 [Oct 17 08:48:54.443] iParcelBox-30AEA4C6F1C8 1605 834.996 2 3|mgos_vfs.c:564 lseek 257 0 2 => 0x3ffc00b4:1 => 1162 [Oct 17 08:48:54.444] iParcelBox-30AEA4C6F1C8 1606 835.002 2 3|mgos_vfs.c:564 lseek 257 0 0 => 0x3ffc00b4:1 => 0 [Oct 17 08:48:54.444] iParcelBox-30AEA4C6F1C8 1607 835.016 2 3|mgos_vfs.c:410 close 257 => 0x3ffc00b4:1 => 0 (refs 0) [Oct 17 08:48:54.444] iParcelBox-30AEA4C6F1C8 1608 835.030 2 3|mgos_vfs.c:283 aws-iParcelBox-30AEA.key.pem -> /aws-iParcelBox-30AEA.key.pem pl 1 -> 1 0x3ffc00b4 (refs 1) [Oct 17 08:48:54.444] iParcelBox-30AEA4C6F1C8 1609 835.041 2 3|mgos_vfs_fs_spiffs.:838 aws-iParcelBox-30AEA.key.pem -> 2UtgX+f6kfNlUiJgeGwWuLO8pzQZpHNITStcmv0ViCA= [Oct 17 08:48:54.452] iParcelBox-30AEA4C6F1C8 1610 835.058 2 3|mgos_vfs.c:377 open aws-iParcelBox-30AEA.key.pem 0x0 0x1b6 => 0x3ffc00b4 aws-iParcelBox-30AEA.key.pem 1 => 257 (refs 1) [Oct 17 08:48:54.455] iParcelBox-30AEA4C6F1C8 1611 835.065 2 3|mgos_vfs.c:536 fstat 257 => 0x3ffc00b4:1 => 0 (size 227) [Oct 17 08:48:54.462] iParcelBox-30AEA4C6F1C8 1612 835.073 2 3|mgos_vfs.c:536 fstat 257 => 0x3ffc00b4:1 => 0 (size 227) [Oct 17 08:48:54.470] iParcelBox-30AEA4C6F1C8 1613 835.079 2 3|mgos_vfs.c:564 lseek 257 0 1 => 0x3ffc00b4:1 => 0 [Oct 17 08:48:54.476] iParcelBox-30AEA4C6F1C8 1614 835.086 2 3|mgos_vfs.c:564 lseek 257 0 0 => 0x3ffc00b4:1 => 0 [Oct 17 08:48:54.482] iParcelBox-30AEA4C6F1C8 1615 835.093 2 3|mgos_vfs.c:564 lseek 257 0 0 => 0x3ffc00b4:1 => 0 [Oct 17 08:48:54.624] iParcelBox-30AEA4C6F1C8 1616 835.100 2 3|mgos_vfs.c:564 lseek 257 0 2 => 0x3ffc00b4:1 => 227 [Oct 17 08:48:54.624] iParcelBox-30AEA4C6F1C8 1617 835.106 2 3|mgos_vfs.c:564 lseek 257 0 0 => 0x3ffc00b4:1 => 0 [Oct 17 08:48:54.624] iParcelBox-30AEA4C6F1C8 1618 835.115 2 3|mgos_vfs.c:410 close 257 => 0x3ffc00b4:1 => 0 (refs 0) [Oct 17 08:48:54.624] iParcelBox-30AEA4C6F1C8 1619 835.124 2 3|mgos_vfs.c:283 ca.pem -> /ca.pem pl 1 -> 1 0x3ffc00b4 (refs 1) [Oct 17 08:48:54.624] iParcelBox-30AEA4C6F1C8 1620 835.133 2 3|mgos_vfs_fs_spiffs.:838 ca.pem -> p0Wg4sKNHIna7YDEpP5CSLltTIGAQkR5MEdzJvfF22o= [Oct 17 08:48:54.624] iParcelBox-30AEA4C6F1C8 1621 835.145 2 3|mgos_vfs.c:377 open ca.pem 0x0 0x1b6 => 0x3ffc00b4 ca.pem 1 => 257 (refs 1) [Oct 17 08:48:54.625] iParcelBox-30AEA4C6F1C8 1622 835.152 2 3|mgos_vfs.c:410 close 257 => 0x3ffc00b4:1 => 0 (refs 0) [Oct 17 08:48:54.625] iParcelBox-30AEA4C6F1C8 1623 835.160 2 3|mg_net.c:910 0x3ffef4a8 udp://192.168.0.1:53 -,-,- [Oct 17 08:48:54.625] iParcelBox-30AEA4C6F1C8 1624 835.166 2 3|mg_net.c:778 0x3ffef4a8 udp://192.168.0.1:53 [Oct 17 08:48:54.625] iParcelBox-30AEA4C6F1C8 1625 835.174 2 3|mg_net.c:793 0x3ffef4a8 udp://192.168.0.1:53 -> 0 [Oct 17 08:48:55.788] iParcelBox-30AEA4C6F1C8 1626 836.327 2 2|pn_ping.c:45 PING From 192.168.0.1 icmp_seq=82 timeout [Oct 17 08:48:55.788] iParcelBox-30AEA4C6F1C8 1627 836.346 2 2|pn_ping.c:48 MemReport: intenal_free: 146528, internal_min_free: 115312, internal_free_block: 38100, psram_free: 4156668, psram_min_free: 4126236, psram_free_block: 4127996 [Oct 17 08:49:05.821] iParcelBox-30AEA4C6F1C8 1628 846.333 2 2|pn_ping.c:45 PING From 192.168.0.1 icmp_seq=83 timeout [Oct 17 08:49:05.821] iParcelBox-30AEA4C6F1C8 1629 846.352 2 2|pn_ping.c:48 MemReport: intenal_free: 151816, internal_min_free: 115312, internal_free_block: 38100, psram_free: 4156760, psram_min_free: 4126236, psram_free_block: 4127996 [Oct 17 08:49:09.585] iParcelBox-30AEA4C6F1C8 1630 850.159 2 2|mgos_mqtt_conn.c:468 MQTT0 connecting to a24buxh69lukw9-ats.iot.eu-west-1.amazonaws.com:8883 [Oct 17 08:49:09.585] iParcelBox-30AEA4C6F1C8 1631 850.166 2 3|mgos_event.c:135 ev MOS6 triggered 1 handlers [Oct 17 08:49:09.585] iParcelBox-30AEA4C6F1C8 1632 850.181 2 3|mg_net.c:910 0x3ffe7b44 a24buxh69lukw9-ats.iot.eu-west-1.amazonaws.com:8883 aws-iParcelBox-30AEA.crt.pem,aws-iParcelBox-30AEA.key.pem,ca.pem [Oct 17 08:49:09.585] iParcelBox-30AEA4C6F1C8 1633 850.193 2 3|mgos_vfs.c:283 aws-iParcelBox-30AEA.crt.pem -> /aws-iParcelBox-30AEA.crt.pem pl 1 -> 1 0x3ffc00b4 (refs 1) [Oct 17 08:49:09.594] iParcelBox-30AEA4C6F1C8 1634 850.203 2 3|mgos_vfs_fs_spiffs.:838 aws-iParcelBox-30AEA.crt.pem -> 2UtgX+f6kfNlUiJgeGwWuDYbbagygbxrqr4IyOJ76Zg= [Oct 17 08:49:09.609] iParcelBox-30AEA4C6F1C8 1635 850.219 2 3|mgos_vfs.c:377 open aws-iParcelBox-30AEA.crt.pem 0x0 0x1b6 => 0x3ffc00b4 aws-iParcelBox-30AEA.crt.pem 1 => 257 (refs 1) [Oct 17 08:49:09.616] iParcelBox-30AEA4C6F1C8 1636 850.226 2 3|mgos_vfs.c:536 fstat 257 => 0x3ffc00b4:1 => 0 (size 1162) [Oct 17 08:49:09.624] iParcelBox-30AEA4C6F1C8 1637 850.234 2 3|mgos_vfs.c:536 fstat 257 => 0x3ffc00b4:1 => 0 (size 1162) [Oct 17 08:49:09.630] iParcelBox-30AEA4C6F1C8 1638 850.240 2 3|mgos_vfs.c:564 lseek 257 0 1 => 0x3ffc00b4:1 => 0 [Oct 17 08:49:09.637] iParcelBox-30AEA4C6F1C8 1639 850.247 2 3|mgos_vfs.c:564 lseek 257 1024 0 => 0x3ffc00b4:1 => 1024 [Oct 17 08:49:09.645] iParcelBox-30AEA4C6F1C8 1640 850.255 2 3|mgos_vfs.c:564 lseek 257 1024 0 => 0x3ffc00b4:1 => 1024 [Oct 17 08:49:09.659] iParcelBox-30AEA4C6F1C8 1641 850.262 2 3|mgos_vfs.c:564 lseek 257 0 2 => 0x3ffc00b4:1 => 1162 [Oct 17 08:49:09.659] iParcelBox-30AEA4C6F1C8 1642 850.269 2 3|mgos_vfs.c:564 lseek 257 0 0 => 0x3ffc00b4:1 => 0 [Oct 17 08:49:09.671] iParcelBox-30AEA4C6F1C8 1643 850.282 2 3|mgos_vfs.c:410 close 257 => 0x3ffc00b4:1 => 0 (refs 0) [Oct 17 08:49:09.689] iParcelBox-30AEA4C6F1C8 1644 850.297 2 3|mgos_vfs.c:283 aws-iParcelBox-30AEA.key.pem -> /aws-iParcelBox-30AEA.key.pem pl 1 -> 1 0x3ffc00b4 (refs 1) [Oct 17 08:49:09.696] iParcelBox-30AEA4C6F1C8 1645 850.307 2 3|mgos_vfs_fs_spiffs.:838 aws-iParcelBox-30AEA.key.pem -> 2UtgX+f6kfNlUiJgeGwWuLO8pzQZpHNITStcmv0ViCA= [Oct 17 08:49:09.713] iParcelBox-30AEA4C6F1C8 1646 850.324 2 3|mgos_vfs.c:377 open aws-iParcelBox-30AEA.key.pem 0x0 0x1b6 => 0x3ffc00b4 aws-iParcelBox-30AEA.key.pem 1 => 257 (refs 1) [Oct 17 08:49:09.721] iParcelBox-30AEA4C6F1C8 1647 850.332 2 3|mgos_vfs.c:536 fstat 257 => 0x3ffc00b4:1 => 0 (size 227) [Oct 17 08:49:09.728] iParcelBox-30AEA4C6F1C8 1648 850.339 2 3|mgos_vfs.c:536 fstat 257 => 0x3ffc00b4:1 => 0 (size 227) [Oct 17 08:49:09.737] iParcelBox-30AEA4C6F1C8 1649 850.346 2 3|mgos_vfs.c:564 lseek 257 0 1 => 0x3ffc00b4:1 => 0 [Oct 17 08:49:09.741] iParcelBox-30AEA4C6F1C8 1650 850.352 2 3|mgos_vfs.c:564 lseek 257 0 0 => 0x3ffc00b4:1 => 0 [Oct 17 08:49:09.751] iParcelBox-30AEA4C6F1C8 1651 850.360 2 3|mgos_vfs.c:564 lseek 257 0 0 => 0x3ffc00b4:1 => 0 [Oct 17 08:49:09.755] iParcelBox-30AEA4C6F1C8 1652 850.367 2 3|mgos_vfs.c:564 lseek 257 0 2 => 0x3ffc00b4:1 => 227 [Oct 17 08:49:09.766] iParcelBox-30AEA4C6F1C8 1653 850.374 2 3|mgos_vfs.c:564 lseek 257 0 0 => 0x3ffc00b4:1 => 0 [Oct 17 08:49:09.774] iParcelBox-30AEA4C6F1C8 1654 850.382 2 3|mgos_vfs.c:410 close 257 => 0x3ffc00b4:1 => 0 (refs 0) [Oct 17 08:49:09.780] iParcelBox-30AEA4C6F1C8 1655 850.392 2 3|mgos_vfs.c:283 ca.pem -> /ca.pem pl 1 -> 1 0x3ffc00b4 (refs 1) [Oct 17 08:49:09.793] iParcelBox-30AEA4C6F1C8 1656 850.400 2 3|mgos_vfs_fs_spiffs.:838 ca.pem -> p0Wg4sKNHIna7YDEpP5CSLltTIGAQkR5MEdzJvfF22o= [Oct 17 08:49:09.800] iParcelBox-30AEA4C6F1C8 1657 850.413 2 3|mgos_vfs.c:377 open ca.pem 0x0 0x1b6 => 0x3ffc00b4 ca.pem 1 => 257 (refs 1) [Oct 17 08:49:09.812] iParcelBox-30AEA4C6F1C8 1658 850.420 2 3|mgos_vfs.c:410 close 257 => 0x3ffc00b4:1 => 0 (refs 0) [Oct 17 08:49:09.822] iParcelBox-30AEA4C6F1C8 1659 850.428 2 3|mg_net.c:910 0x3ffef4a8 udp://192.168.0.1:53 -,-,- [Oct 17 08:49:09.822] iParcelBox-30AEA4C6F1C8 1660 850.434 2 3|mg_net.c:778 0x3ffef4a8 udp://192.168.0.1:53 [Oct 17 08:49:09.837] iParcelBox-30AEA4C6F1C8 1661 850.441 2 3|mg_net.c:793 0x3ffef4a8 udp://192.168.0.1:53 -> 0 [Oct 17 08:49:15.753] iParcelBox-30AEA4C6F1C8 1662 856.327 2 2|pn_ping.c:45 PING From 192.168.0.1 icmp_seq=84 timeout [Oct 17 08:49:15.753] iParcelBox-30AEA4C6F1C8 1663 856.345 2 2|pn_ping.c:48 MemReport: intenal_free: 146528, internal_min_free: 115312, internal_free_block: 38100, psram_free: 4156668, psram_min_free: 4126236, psram_free_block: 4127996 [Oct 17 08:49:20.746] iParcelBox-30AEA4C6F1C8 1664 861.331 2 0|mg_resolv.c:208 Failed to resolve 'a24buxh69lukw9-ats.iot.eu-west-1.amazonaws.com', server 192.168.0.1 [Oct 17 08:49:20.746] iParcelBox-30AEA4C6F1C8 1665 861.337 2 2|mgos_mqtt_conn.c:227 MQTT0 TCP connect error (-1) [Oct 17 08:49:20.746] iParcelBox-30AEA4C6F1C8 1666 861.342 2 2|mgos_mqtt_conn.c:253 MQTT0 Disconnect [Oct 17 08:49:20.746] iParcelBox-30AEA4C6F1C8 1667 861.348 2 3|mgos_event.c:135 ev MOS5 triggered 1 handlers [Oct 17 08:49:20.758] iParcelBox-30AEA4C6F1C8 1668 861.365 2 2|init.js:468 MQTT Disconnect [Oct 17 08:49:20.761] iParcelBox-30AEA4C6F1C8 1669 861.373 2 2|mgos_mqtt_conn.c:546 MQTT0 connecting after 8608 ms [Oct 17 08:49:20.772] iParcelBox-30AEA4C6F1C8 1670 861.378 2 3|mg_net.c:149 0x3ffe7b44 0x10 1 [Oct 17 08:49:25.787] iParcelBox-30AEA4C6F1C8 1671 866.327 2 2|pn_ping.c:45 PING From 192.168.0.1 icmp_seq=85 timeout [Oct 17 08:49:25.787] iParcelBox-30AEA4C6F1C8 1672 866.346 2 2|pn_ping.c:48 MemReport: intenal_free: 151816, internal_min_free: 115312, internal_free_block: 38100, psram_free: 4156760, psram_min_free: 4126236, psram_free_block: 4127996 [Oct 17 08:49:29.581] iParcelBox-30AEA4C6F1C8 1673 869.991 2 2|mgos_mqtt_conn.c:468 MQTT0 connecting to a24buxh69lukw9-ats.iot.eu-west-1.amazonaws.com:8883 [Oct 17 08:49:29.582] iParcelBox-30AEA4C6F1C8 1674 869.997 2 3|mgos_event.c:135 ev MOS6 triggered 1 handlers [Oct 17 08:49:29.582] iParcelBox-30AEA4C6F1C8 1675 870.012 2 3|mg_net.c:910 0x3ffe7b44 a24buxh69lukw9-ats.iot.eu-west-1.amazonaws.com:8883 aws-iParcelBox-30AEA.crt.pem,aws-iParcelBox-30AEA.key.pem,ca.pem [Oct 17 08:49:29.582] iParcelBox-30AEA4C6F1C8 1676 870.023 2 3|mgos_vfs.c:283 aws-iParcelBox-30AEA.crt.pem -> /aws-iParcelBox-30AEA.crt.pem pl 1 -> 1 0x3ffc00b4 (refs 1) [Oct 17 08:49:29.582] iParcelBox-30AEA4C6F1C8 1677 870.033 2 3|mgos_vfs_fs_spiffs.:838 aws-iParcelBox-30AEA.crt.pem -> 2UtgX+f6kfNlUiJgeGwWuDYbbagygbxrqr4IyOJ76Zg= [Oct 17 08:49:29.582] iParcelBox-30AEA4C6F1C8 1678 870.049 2 3|mgos_vfs.c:377 open aws-iParcelBox-30AEA.crt.pem 0x0 0x1b6 => 0x3ffc00b4 aws-iParcelBox-30AEA.crt.pem 1 => 257 (refs 1) [Oct 17 08:49:29.582] iParcelBox-30AEA4C6F1C8 1679 870.056 2 3|mgos_vfs.c:536 fstat 257 => 0x3ffc00b4:1 => 0 (size 1162) [Oct 17 08:49:29.582] iParcelBox-30AEA4C6F1C8 1680 870.063 2 3|mgos_vfs.c:536 fstat 257 => 0x3ffc00b4:1 => 0 (size 1162) [Oct 17 08:49:29.582] iParcelBox-30AEA4C6F1C8 1681 870.070 2 3|mgos_vfs.c:564 lseek 257 0 1 => 0x3ffc00b4:1 => 0 [Oct 17 08:49:29.582] iParcelBox-30AEA4C6F1C8 1682 870.077 2 3|mgos_vfs.c:564 lseek 257 1024 0 => 0x3ffc00b4:1 => 1024 [Oct 17 08:49:29.582] iParcelBox-30AEA4C6F1C8 1683 870.085 2 3|mgos_vfs.c:564 lseek 257 1024 0 => 0x3ffc00b4:1 => 1024 [Oct 17 08:49:29.582] iParcelBox-30AEA4C6F1C8 1684 870.091 2 3|mgos_vfs.c:564 lseek 257 0 2 => 0x3ffc00b4:1 => 1162 [Oct 17 08:49:29.582] iParcelBox-30AEA4C6F1C8 1685 870.098 2 3|mgos_vfs.c:564 lseek 257 0 0 => 0x3ffc00b4:1 => 0 [Oct 17 08:49:29.582] iParcelBox-30AEA4C6F1C8 1686 870.111 2 3|mgos_vfs.c:410 close 257 => 0x3ffc00b4:1 => 0 (refs 0) [Oct 17 08:49:29.582] iParcelBox-30AEA4C6F1C8 1687 870.126 2 3|mgos_vfs.c:283 aws-iParcelBox-30AEA.key.pem -> /aws-iParcelBox-30AEA.key.pem pl 1 -> 1 0x3ffc00b4 (refs 1) [Oct 17 08:49:29.582] iParcelBox-30AEA4C6F1C8 1688 870.137 2 3|mgos_vfs_fs_spiffs.:838 aws-iParcelBox-30AEA.key.pem -> 2UtgX+f6kfNlUiJgeGwWuLO8pzQZpHNITStcmv0ViCA= [Oct 17 08:49:29.583] iParcelBox-30AEA4C6F1C8 1689 870.154 2 3|mgos_vfs.c:377 open aws-iParcelBox-30AEA.key.pem 0x0 0x1b6 => 0x3ffc00b4 aws-iParcelBox-30AEA.key.pem 1 => 257 (refs 1) [Oct 17 08:49:29.584] iParcelBox-30AEA4C6F1C8 1690 870.161 2 3|mgos_vfs.c:536 fstat 257 => 0x3ffc00b4:1 => 0 (size 227) [Oct 17 08:49:29.584] iParcelBox-30AEA4C6F1C8 1691 870.168 2 3|mgos_vfs.c:536 fstat 257 => 0x3ffc00b4:1 => 0 (size 227) [Oct 17 08:49:29.584] iParcelBox-30AEA4C6F1C8 1692 870.175 2 3|mgos_vfs.c:564 lseek 257 0 1 => 0x3ffc00b4:1 => 0 [Oct 17 08:49:29.584] iParcelBox-30AEA4C6F1C8 1693 870.181 2 3|mgos_vfs.c:564 lseek 257 0 0 => 0x3ffc00b4:1 => 0 [Oct 17 08:49:29.584] iParcelBox-30AEA4C6F1C8 1694 870.189 2 3|mgos_vfs.c:564 lseek 257 0 0 => 0x3ffc00b4:1 => 0 [Oct 17 08:49:29.588] iParcelBox-30AEA4C6F1C8 1695 870.196 2 3|mgos_vfs.c:564 lseek 257 0 2 => 0x3ffc00b4:1 => 227 [Oct 17 08:49:29.590] iParcelBox-30AEA4C6F1C8 1696 870.202 2 3|mgos_vfs.c:564 lseek 257 0 0 => 0x3ffc00b4:1 => 0 [Oct 17 08:49:29.598] iParcelBox-30AEA4C6F1C8 1697 870.210 2 3|mgos_vfs.c:410 close 257 => 0x3ffc00b4:1 => 0 (refs 0) [Oct 17 08:49:29.609] iParcelBox-30AEA4C6F1C8 1698 870.220 2 3|mgos_vfs.c:283 ca.pem -> /ca.pem pl 1 -> 1 0x3ffc00b4 (refs 1) [Oct 17 08:49:29.617] iParcelBox-30AEA4C6F1C8 1699 870.229 2 3|mgos_vfs_fs_spiffs.:838 ca.pem -> p0Wg4sKNHIna7YDEpP5CSLltTIGAQkR5MEdzJvfF22o= [Oct 17 08:49:29.630] iParcelBox-30AEA4C6F1C8 1700 870.241 2 3|mgos_vfs.c:377 open ca.pem 0x0 0x1b6 => 0x3ffc00b4 ca.pem 1 => 257 (refs 1) [Oct 17 08:49:29.637] iParcelBox-30AEA4C6F1C8 1701 870.249 2 3|mgos_vfs.c:410 close 257 => 0x3ffc00b4:1 => 0 (refs 0) [Oct 17 08:49:29.645] iParcelBox-30AEA4C6F1C8 1702 870.257 2 3|mg_net.c:910 0x3ffef4a8 udp://192.168.0.1:53 -,-,- [Oct 17 08:49:29.658] iParcelBox-30AEA4C6F1C8 1703 870.263 2 3|mg_net.c:778 0x3ffef4a8 udp://192.168.0.1:53 [Oct 17 08:49:29.658] iParcelBox-30AEA4C6F1C8 1704 870.271 2 3|mg_net.c:793 0x3ffef4a8 udp://192.168.0.1:53 -> 0 [Oct 17 08:49:35.823] iParcelBox-30AEA4C6F1C8 1705 876.327 2 2|pn_ping.c:45 PING From 192.168.0.1 icmp_seq=86 timeout [Oct 17 08:49:35.823] iParcelBox-30AEA4C6F1C8 1706 876.345 2 2|pn_ping.c:48 MemReport: intenal_free: 146528, internal_min_free: 115312, internal_free_block: 38100, psram_free: 4156668, psram_min_free: 4126236, psram_free_block: 4127996 [Oct 17 08:49:40.740] iParcelBox-30AEA4C6F1C8 1707 881.331 2 0|mg_resolv.c:208 Failed to resolve 'a24buxh69lukw9-ats.iot.eu-west-1.amazonaws.com', server 192.168.0.1 [Oct 17 08:49:40.741] iParcelBox-30AEA4C6F1C8 1708 881.337 2 2|mgos_mqtt_conn.c:227 MQTT0 TCP connect error (-1) [Oct 17 08:49:40.741] iParcelBox-30AEA4C6F1C8 1709 881.342 2 2|mgos_mqtt_conn.c:253 MQTT0 Disconnect [Oct 17 08:49:40.741] iParcelBox-30AEA4C6F1C8 1710 881.348 2 3|mgos_event.c:135 ev MOS5 triggered 1 handlers [Oct 17 08:49:40.753] iParcelBox-30AEA4C6F1C8 1711 881.363 2 2|init.js:468 MQTT Disconnect [Oct 17 08:49:40.758] iParcelBox-30AEA4C6F1C8 1712 881.371 2 2|mgos_mqtt_conn.c:546 MQTT0 connecting after 16101 ms [Oct 17 08:49:40.765] iParcelBox-30AEA4C6F1C8 1713 881.376 2 3|mg_net.c:149 0x3ffe7b44 0x10 1 [Oct 17 08:49:45.717] iParcelBox-30AEA4C6F1C8 1714 886.327 2 2|pn_ping.c:45 PING From 192.168.0.1 icmp_seq=87 timeout [Oct 17 08:49:45.780] iParcelBox-30AEA4C6F1C8 1715 886.345 2 2|pn_ping.c:48 MemReport: intenal_free: 151816, internal_min_free: 115312, internal_free_block: 38100, psram_free: 4156760, psram_min_free: 4126236, psram_free_block: 4127996 [Oct 17 08:49:55.792] iParcelBox-30AEA4C6F1C8 1716 896.327 2 2|pn_ping.c:45 PING From 192.168.0.1 icmp_seq=88 timeout [Oct 17 08:49:55.792] iParcelBox-30AEA4C6F1C8 1717 896.345 2 2|pn_ping.c:48 MemReport: intenal_free: 151816, internal_min_free: 115312, internal_free_block: 38100, psram_free: 4156760, psram_min_free: 4126236, psram_free_block: 4127996 [Oct 17 08:49:56.920] iParcelBox-30AEA4C6F1C8 1718 897.482 2 2|mgos_mqtt_conn.c:468 MQTT0 connecting to a24buxh69lukw9-ats.iot.eu-west-1.amazonaws.com:8883 [Oct 17 08:49:56.920] iParcelBox-30AEA4C6F1C8 1719 897.488 2 3|mgos_event.c:135 ev MOS6 triggered 1 handlers [Oct 17 08:49:56.920] iParcelBox-30AEA4C6F1C8 1720 897.503 2 3|mg_net.c:910 0x3ffe7b44 a24buxh69lukw9-ats.iot.eu-west-1.amazonaws.com:8883 aws-iParcelBox-30AEA.crt.pem,aws-iParcelBox-30AEA.key.pem,ca.pem [Oct 17 08:49:56.920] iParcelBox-30AEA4C6F1C8 1721 897.515 2 3|mgos_vfs.c:283 aws-iParcelBox-30AEA.crt.pem -> /aws-iParcelBox-30AEA.crt.pem pl 1 -> 1 0x3ffc00b4 (refs 1) [Oct 17 08:49:56.920] iParcelBox-30AEA4C6F1C8 1722 897.525 2 3|mgos_vfs_fs_spiffs.:838 aws-iParcelBox-30AEA.crt.pem -> 2UtgX+f6kfNlUiJgeGwWuDYbbagygbxrqr4IyOJ76Zg= [Oct 17 08:49:56.929] iParcelBox-30AEA4C6F1C8 1723 897.541 2 3|mgos_vfs.c:377 open aws-iParcelBox-30AEA.crt.pem 0x0 0x1b6 => 0x3ffc00b4 aws-iParcelBox-30AEA.crt.pem 1 => 257 (refs 1) [Oct 17 08:49:56.937] iParcelBox-30AEA4C6F1C8 1724 897.549 2 3|mgos_vfs.c:536 fstat 257 => 0x3ffc00b4:1 => 0 (size 1162) [Oct 17 08:49:56.943] iParcelBox-30AEA4C6F1C8 1725 897.556 2 3|mgos_vfs.c:536 fstat 257 => 0x3ffc00b4:1 => 0 (size 1162) [Oct 17 08:49:56.950] iParcelBox-30AEA4C6F1C8 1726 897.563 2 3|mgos_vfs.c:564 lseek 257 0 1 => 0x3ffc00b4:1 => 0 [Oct 17 08:49:56.957] iParcelBox-30AEA4C6F1C8 1727 897.570 2 3|mgos_vfs.c:564 lseek 257 1024 0 => 0x3ffc00b4:1 => 1024 [Oct 17 08:49:56.987] iParcelBox-30AEA4C6F1C8 1728 897.578 2 3|mgos_vfs.c:564 lseek 257 1024 0 => 0x3ffc00b4:1 => 1024 [Oct 17 08:49:56.987] iParcelBox-30AEA4C6F1C8 1729 897.585 2 3|mgos_vfs.c:564 lseek 257 0 2 => 0x3ffc00b4:1 => 1162 [Oct 17 08:49:56.987] iParcelBox-30AEA4C6F1C8 1730 897.591 2 3|mgos_vfs.c:564 lseek 257 0 0 => 0x3ffc00b4:1 => 0 [Oct 17 08:49:56.991] iParcelBox-30AEA4C6F1C8 1731 897.603 2 3|mgos_vfs.c:410 close 257 => 0x3ffc00b4:1 => 0 (refs 0) [Oct 17 08:49:57.010] iParcelBox-30AEA4C6F1C8 1732 897.618 2 3|mgos_vfs.c:283 aws-iParcelBox-30AEA.key.pem -> /aws-iParcelBox-30AEA.key.pem pl 1 -> 1 0x3ffc00b4 (refs 1) [Oct 17 08:49:57.024] iParcelBox-30AEA4C6F1C8 1733 897.628 2 3|mgos_vfs_fs_spiffs.:838 aws-iParcelBox-30AEA.key.pem -> 2UtgX+f6kfNlUiJgeGwWuLO8pzQZpHNITStcmv0ViCA= [Oct 17 08:49:57.033] iParcelBox-30AEA4C6F1C8 1734 897.645 2 3|mgos_vfs.c:377 open aws-iParcelBox-30AEA.key.pem 0x0 0x1b6 => 0x3ffc00b4 aws-iParcelBox-30AEA.key.pem 1 => 257 (refs 1) [Oct 17 08:49:57.040] iParcelBox-30AEA4C6F1C8 1735 897.653 2 3|mgos_vfs.c:536 fstat 257 => 0x3ffc00b4:1 => 0 (size 227) [Oct 17 08:49:57.048] iParcelBox-30AEA4C6F1C8 1736 897.660 2 3|mgos_vfs.c:536 fstat 257 => 0x3ffc00b4:1 => 0 (size 227) [Oct 17 08:49:57.063] iParcelBox-30AEA4C6F1C8 1737 897.666 2 3|mgos_vfs.c:564 lseek 257 0 1 => 0x3ffc00b4:1 => 0 [Oct 17 08:49:57.080] iParcelBox-30AEA4C6F1C8 1738 897.673 2 3|mgos_vfs.c:564 lseek 257 0 0 => 0x3ffc00b4:1 => 0 [Oct 17 08:49:57.084] iParcelBox-30AEA4C6F1C8 1739 897.680 2 3|mgos_vfs.c:564 lseek 257 0 0 => 0x3ffc00b4:1 => 0 [Oct 17 08:49:57.084] iParcelBox-30AEA4C6F1C8 1740 897.686 2 3|mgos_vfs.c:564 lseek 257 0 2 => 0x3ffc00b4:1 => 227 [Oct 17 08:49:57.084] iParcelBox-30AEA4C6F1C8 1741 897.692 2 3|mgos_vfs.c:564 lseek 257 0 0 => 0x3ffc00b4:1 => 0 [Oct 17 08:49:57.093] iParcelBox-30AEA4C6F1C8 1742 897.701 2 3|mgos_vfs.c:410 close 257 => 0x3ffc00b4:1 => 0 (refs 0) [Oct 17 08:49:57.099] iParcelBox-30AEA4C6F1C8 1743 897.710 2 3|mgos_vfs.c:283 ca.pem -> /ca.pem pl 1 -> 1 0x3ffc00b4 (refs 1) [Oct 17 08:49:57.107] iParcelBox-30AEA4C6F1C8 1744 897.719 2 3|mgos_vfs_fs_spiffs.:838 ca.pem -> p0Wg4sKNHIna7YDEpP5CSLltTIGAQkR5MEdzJvfF22o= [Oct 17 08:49:57.121] iParcelBox-30AEA4C6F1C8 1745 897.731 2 3|mgos_vfs.c:377 open ca.pem 0x0 0x1b6 => 0x3ffc00b4 ca.pem 1 => 257 (refs 1) [Oct 17 08:49:57.126] iParcelBox-30AEA4C6F1C8 1746 897.738 2 3|mgos_vfs.c:410 close 257 => 0x3ffc00b4:1 => 0 (refs 0) [Oct 17 08:49:57.134] iParcelBox-30AEA4C6F1C8 1747 897.746 2 3|mg_net.c:910 0x3ffef4a8 udp://192.168.0.1:53 -,-,- [Oct 17 08:49:57.140] iParcelBox-30AEA4C6F1C8 1748 897.753 2 3|mg_net.c:778 0x3ffef4a8 udp://192.168.0.1:53 [Oct 17 08:49:57.155] iParcelBox-30AEA4C6F1C8 1749 897.760 2 3|mg_net.c:793 0x3ffef4a8 udp://192.168.0.1:53 -> 0 [Oct 17 08:50:05.828] iParcelBox-30AEA4C6F1C8 1750 906.327 2 2|pn_ping.c:45 PING From 192.168.0.1 icmp_seq=89 timeout [Oct 17 08:50:05.828] iParcelBox-30AEA4C6F1C8 1751 906.345 2 2|pn_ping.c:48 MemReport: intenal_free: 146528, internal_min_free: 115312, internal_free_block: 38100, psram_free: 4156668, psram_min_free: 4126236, psram_free_block: 4127996 [Oct 17 08:50:08.796] iParcelBox-30AEA4C6F1C8 1752 909.331 2 0|mg_resolv.c:208 Failed to resolve 'a24buxh69lukw9-ats.iot.eu-west-1.amazonaws.com', server 192.168.0.1 [Oct 17 08:50:08.796] iParcelBox-30AEA4C6F1C8 1753 909.337 2 2|mgos_mqtt_conn.c:227 MQTT0 TCP connect error (-1) [Oct 17 08:50:08.796] iParcelBox-30AEA4C6F1C8 1754 909.342 2 2|mgos_mqtt_conn.c:253 MQTT0 Disconnect

gadget-man commented 4 years ago

So it looks as though it's set off soon after wifi:obss scan is disabled

david-cermak commented 3 years ago

@gadget-man I'm sorry for not responding. Is there any update to this issue? Thanks for posting the new log, but this only shows what you've shared previously. It would be really helpful to provide some more detailed info with lwip debugging on, as requested above.

So it looks as though it's set off soon after wifi:obss scan is disabled

I think this is unrelated, but will check with the wifi team.

gadget-man commented 3 years ago

We are still seeing this issue on a small number of devices. Interesting, in nearly every case the customer also has an LG TV connected to their same network, either via WiFi or an ethernet connection. To date we haven't been able to find a customer who is technical enough to be able to capture Wireshark updates. I'll try again to see if I can turn on lip debugging.

xueyunfei998 commented 3 years ago

hi @gadget-man

Do you mean that if there is an LG TV device in the network, the Ping Service will fail?

If it is a problem with the LG device, you can remove the LG device from the network to see if the problem can be reproduced？

You can build a testing environment and capture packets with Wireshark to reproduce this problem.

gadget-man commented 3 years ago

We aren't certain it's the cause, but nearly every customer who has experienced intermittent disconnections on ESP also has an LG television. Turning the power off to the TV stops the connection issues. It is only ICMP Ping and TCP that is affected - even on a 'disconnected' device I am still able to receive logging info via UDP. Rebooting the devices causes it to immediately reconnect.

xueyunfei998 commented 3 years ago

hi @gadget-man Because this problem requires packet capture analysis, but the current conditions do not allow it, can you upgrade the IDF version to 4.1 to see if this problem can be solved?

xueyunfei998 commented 3 years ago

hi @gadget-man

Provide the models of LG TV and router, and we purchase an environment test internally

In addition, you can do such a test. When something goes wrong, connect the router with your mobile phone to see if the communication is normal.

gadget-man commented 3 years ago

It looks as though this issue may have been resolved after an upgrade to IDF4.1. One of my most 'reliable' devices with this issue has now been stable for almost a week following the upgrade. I'll keep you posted!

Alvin1Zhang commented 3 years ago

@gadget-man Thanks for reporting and sharing the updates, feel free to reopen if the issue happens again.