I have a DSGW-210 and from time to time I loose connection to it. I am not able to find it on the network, the severs (default server and Node-Red) does not respond on the browser, and also I don’t see it on the network.
Power cycling (unplug and plug it back) the device always brings it back to life. Any suggestions would be appreciated.
I extracted part of the syslog, where I can see where it got restarted 19:11:35, but from the logs it looks like it was working without any issues before that.
/var/log/syslog
Feb 13 19:10:38 DUSUN Node-RED[1076188]: [2025-02-13T18:10:38.285Z +24ms] #033[32minfo#033[39m CLIENT:2.2.0/c5a17743> Status response
Feb 13 19:10:41 DUSUN Node-RED[1076188]: [2025-02-13T18:10:41.220Z +3s] #033[32minfo#033[39m CLIENT:2.2.0/00ef85b0> Status request
Feb 13 19:10:41 DUSUN Node-RED[1076188]: [2025-02-13T18:10:41.224Z +4ms] #033[32minfo#033[39m CLIENT:2.2.0/c5a17743> Status request
Feb 13 19:10:41 DUSUN Node-RED[1076188]: [2025-02-13T18:10:41.240Z +16ms] #033[32minfo#033[39m CLIENT:2.2.0/00ef85b0> Status response
Feb 13 19:10:41 DUSUN Node-RED[1076188]: [2025-02-13T18:10:41.243Z +3ms] #033[32minfo#033[39m CLIENT:2.2.0/c5a17743> Status response
Feb 13 19:10:43 DUSUN /usr/bin/dsdaemon: Ping GW OK!
Feb 13 19:10:43 DUSUN /usr/bin/dsdaemon: Network cable connected
Feb 13 19:10:44 DUSUN Node-RED[1076188]: [2025-02-13T18:10:44.222Z +3s] #033[32minfo#033[39m CLIENT:2.2.0/00ef85b0> Status request
Feb 13 19:10:44 DUSUN Node-RED[1076188]: [2025-02-13T18:10:44.225Z +3ms] #033[32minfo#033[39m CLIENT:2.2.0/c5a17743> Status request
Feb 13 19:10:44 DUSUN Node-RED[1076188]: [2025-02-13T18:10:44.261Z +36ms] #033[32minfo#033[39m CLIENT:2.2.0/c5a17743> Status response
Feb 13 19:10:44 DUSUN Node-RED[1076188]: [2025-02-13T18:10:44.270Z +9ms] #033[32minfo#033[39m CLIENT:2.2.0/00ef85b0> Status response
Feb 13 19:10:47 DUSUN Node-RED[1076188]: [2025-02-13T18:10:47.223Z +3s] #033[32minfo#033[39m CLIENT:2.2.0/00ef85b0> Status request
Feb 13 19:10:47 DUSUN Node-RED[1076188]: [2025-02-13T18:10:47.227Z +4ms] #033[32minfo#033[39m CLIENT:2.2.0/c5a17743> Status request
Feb 13 19:10:47 DUSUN Node-RED[1076188]: [2025-02-13T18:10:47.257Z +30ms] #033[32minfo#033[39m CLIENT:2.2.0/c5a17743> Status response
Feb 13 19:10:47 DUSUN Node-RED[1076188]: [2025-02-13T18:10:47.264Z +8ms] #033[32minfo#033[39m CLIENT:2.2.0/00ef85b0> Status response
Feb 13 19:10:48 DUSUN /usr/bin/dsdaemon: Ping GW OK!
Feb 13 19:10:48 DUSUN /usr/bin/dsdaemon: Network cable connected
Feb 13 19:10:50 DUSUN Node-RED[1076188]: [2025-02-13T18:10:50.225Z +3s] #033[32minfo#033[39m CLIENT:2.2.0/00ef85b0> Status request
Feb 13 19:10:50 DUSUN Node-RED[1076188]: [2025-02-13T18:10:50.228Z +4ms] #033[32minfo#033[39m CLIENT:2.2.0/c5a17743> Status request
Feb 13 19:10:50 DUSUN Node-RED[1076188]: [2025-02-13T18:10:50.245Z +16ms] #033[32minfo#033[39m CLIENT:2.2.0/00ef85b0> Status response
Feb 13 19:10:50 DUSUN Node-RED[1076188]: [2025-02-13T18:10:50.249Z +4ms] #033[32minfo#033[39m CLIENT:2.2.0/c5a17743> Status response
Feb 13 19:10:53 DUSUN Node-RED[1076188]: [2025-02-13T18:10:53.228Z +3s] #033[32minfo#033[39m CLIENT:2.2.0/00ef85b0> Status request
Feb 13 19:10:53 DUSUN Node-RED[1076188]: [2025-02-13T18:10:53.231Z +3ms] #033[32minfo#033[39m CLIENT:2.2.0/c5a17743> Status request
Feb 13 19:10:53 DUSUN Node-RED[1076188]: [2025-02-13T18:10:53.277Z +46ms] #033[3Feb 13 19:11:35 DUSUN systemd-random-seed[216]: Kernel entropy pool is not initialized yet, waiting until it
is.
Feb 13 19:11:35 DUSUN systemd[1]: Starting Flush Journal to Persistent Storage...
Feb 13 19:11:35 DUSUN systemd[1]: Finished Flush Journal to Persistent Storage.
Feb 13 19:11:35 DUSUN systemd[1]: Starting Create Volatile Files and Directories...
Feb 13 19:11:35 DUSUN systemd[1]: Started Rule-based Manager for Device Events and Files.
Feb 13 19:11:35 DUSUN systemd[1]: Finished Create Volatile Files and Directories.
Feb 13 19:11:35 DUSUN systemd[1]: Starting Update UTMP about System Boot/Shutdown...
Feb 13 19:11:35 DUSUN systemd[1]: Finished Update UTMP about System Boot/Shutdown.
Feb 13 19:11:35 DUSUN systemd[1]: Reached target System Initialization.
Feb 13 19:11:35 DUSUN systemd[1]: Started Daily apt download activities.
Feb 13 19:11:35 DUSUN systemd[1]: Started Daily apt upgrade and clean activities.
Feb 13 19:11:35 DUSUN systemd[1]: Started Periodic ext4 Online Metadata Check for All Filesystems.
Feb 13 19:11:35 DUSUN systemd[1]: Started Discard unused blocks once a week.
Feb 13 19:11:35 DUSUN systemd[1]: Started Daily rotation of log files.
Feb 13 19:11:35 DUSUN systemd[1]: Started Run system activity accounting tool every 10 minutes.
Feb 13 19:11:35 DUSUN systemd[1]: Started Generate summary of yesterday's process accounting.
Feb 13 19:11:35 DUSUN systemd[1]: Started Daily Cleanup of Temporary Directories.
Feb 13 19:11:35 DUSUN systemd[1]: Reached target Timers.
Feb 13 19:11:35 DUSUN systemd[1]: Listening on Avahi mDNS/DNS-SD Stack Activation Socket.
Feb 13 19:11:35 DUSUN systemd[1]: Listening on D-Bus System Message Bus Socket.
Feb 13 19:11:35 DUSUN systemd[1]: Starting Docker Socket for the API.
Feb 13 19:11:35 DUSUN systemd[1]: Listening on Docker Socket for the API.
Feb 13 19:11:35 DUSUN systemd[1]: Reached target Sockets.