As far as I can see with netstat there is no flooding of sockets with CLOSE_WAIT state anymore. So this has been fixed.
However, there still is a problem that the logger process cannot generate new sockets. I added code to better understand this.
Lets see what it tells when it now runs into this problem.
Situation can be cured by restarting the logger process. Therefore, as a last option this can be triggered by the error message.
But this is more a work around than a solution. I still prefer to find a solution within the code.
MB keeps losing contact with Loggers.
Moderator: Mattk
Re: MB keeps losing contact with Loggers.
Quit just a bit ago.
Code: Select all
command: netstat -pa
-------------
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:5355 0.0.0.0:* LISTEN 2267/wsdd2
tcp 0 0 0.0.0.0:netbios-ssn 0.0.0.0:* LISTEN 1318/smbd
tcp 0 0 0.0.0.0:22222 0.0.0.0:* LISTEN 1762/loggerd
tcp 0 0 0.0.0.0:5551 0.0.0.0:* LISTEN 1762/loggerd
tcp 0 0 0.0.0.0:22223 0.0.0.0:* LISTEN 1762/loggerd
tcp 0 0 0.0.0.0:5552 0.0.0.0:* LISTEN 1762/loggerd
tcp 0 0 0.0.0.0:22224 0.0.0.0:* LISTEN 1762/loggerd
tcp 0 0 0.0.0.0:www 0.0.0.0:* LISTEN 699/uhttpd
tcp 0 0 0.0.0.0:5553 0.0.0.0:* LISTEN 1762/loggerd
tcp 0 0 0.0.0.0:5554 0.0.0.0:* LISTEN 1762/loggerd
tcp 0 0 0.0.0.0:5556 0.0.0.0:* LISTEN 1762/loggerd
tcp 0 0 0.0.0.0:5557 0.0.0.0:* LISTEN 1762/loggerd
tcp 0 0 192.168.2.59:domain 0.0.0.0:* LISTEN 495/dnsmasq
tcp 0 0 localhost:domain 0.0.0.0:* LISTEN 495/dnsmasq
tcp 0 0 0.0.0.0:3702 0.0.0.0:* LISTEN 2267/wsdd2
tcp 0 0 0.0.0.0:ssh 0.0.0.0:* LISTEN 536/dropbear
tcp 0 0 0.0.0.0:5559 0.0.0.0:* LISTEN 1762/loggerd
tcp 0 0 0.0.0.0:microsoft-ds 0.0.0.0:* LISTEN 1318/smbd
tcp 0 0 192.168.2.59:57166 gollum.meteobridge.com:www ESTABLISHED 2917/ssh
tcp 0 162 192.168.2.59:www 192.168.2.11:57817 ESTABLISHED 699/uhttpd
tcp 388 0 192.168.2.59:47212 192.168.2.90:22222 ESTABLISHED 1762/loggerd
tcp 0 0 192.168.2.59:www 192.168.2.11:57808 TIME_WAIT -
tcp 0 0 192.168.2.59:www 192.168.2.11:57807 TIME_WAIT -
tcp 1078 0 192.168.2.59:47402 192.168.2.58:22222 ESTABLISHED 1762/loggerd
tcp 0 0 192.168.2.59:www 192.168.2.11:57805 TIME_WAIT -
tcp 0 0 :::netbios-ssn :::* LISTEN 1318/smbd
tcp 0 0 :::5355 :::* LISTEN 2267/wsdd2
tcp 0 0 :::www :::* LISTEN 699/uhttpd
tcp 0 0 fe80::ba27:ebff:febe:2e39:domain :::* LISTEN 495/dnsmasq
tcp 0 0 localhost:domain :::* LISTEN 495/dnsmasq
tcp 0 0 :::ssh :::* LISTEN 536/dropbear
tcp 0 0 :::3702 :::* LISTEN 2267/wsdd2
tcp 0 0 :::microsoft-ds :::* LISTEN 1318/smbd
udp 0 0 192.168.2.59:domain 0.0.0.0:* 495/dnsmasq
udp 0 0 localhost:domain 0.0.0.0:* 495/dnsmasq
udp 0 0 0.0.0.0:3702 0.0.0.0:* 2267/wsdd2
udp 0 0 192.168.2.255:netbios-ns 0.0.0.0:* 1319/nmbd
udp 0 0 192.168.2.59:netbios-ns 0.0.0.0:* 1319/nmbd
udp 0 0 0.0.0.0:netbios-ns 0.0.0.0:* 1319/nmbd
udp 0 0 192.168.2.255:netbios-dgm 0.0.0.0:* 1319/nmbd
udp 0 0 192.168.2.59:netbios-dgm 0.0.0.0:* 1319/nmbd
udp 0 0 0.0.0.0:netbios-dgm 0.0.0.0:* 1319/nmbd
udp 0 0 0.0.0.0:mdns 0.0.0.0:* 746/avahi-daemon: r
udp 0 0 0.0.0.0:5355 0.0.0.0:* 2267/wsdd2
udp 0 0 fe80::ba27:ebff:febe:2e39:domain :::* 495/dnsmasq
udp 0 0 localhost:domain :::* 495/dnsmasq
udp 0 0 :::3702 :::* 2267/wsdd2
udp 0 0 :::mdns :::* 746/avahi-daemon: r
udp 0 0 :::5355 :::* 2267/wsdd2
Active UNIX domain sockets (servers and established)
Proto RefCnt Flags Type State I-Node PID/Program name Path
unix 2 [ ACC ] STREAM LISTENING 3345 746/avahi-daemon: r /var/run/avahi-daemon/socket
unix 2 [ ACC ] STREAM LISTENING 3103 222/ubusd /var/run/ubus.sock
unix 2 [ ] DGRAM 2667 1318/smbd /var/lock/msg.sock/1318
unix 13 [ ] DGRAM 3184 398/logd /dev/log
unix 2 [ ] DGRAM 2674 1458/smbd /var/lock/msg.sock/1458
unix 2 [ ] DGRAM 2419 604/wpa_supplicant /var/run/wpa_supplicant/global
unix 2 [ ] DGRAM 3497 1319/nmbd /var/lock/msg.sock/1319
unix 2 [ ACC ] STREAM LISTENING 3514 1319/nmbd /var/run/samba/nmbd/unexpected
unix 2 [ ] DGRAM 3524 1459/smbd /var/lock/msg.sock/1459
unix 2 [ ] DGRAM 3290 603/hostapd /var/run/hostapd/global
unix 2 [ ACC ] STREAM LISTENING 3320 722/dbus-daemon /var/run/dbus/system_bus_socket
unix 3 [ ] STREAM CONNECTED 3294 222/ubusd /var/run/ubus.sock
unix 3 [ ] STREAM CONNECTED 3293 603/hostapd
unix 2 [ ] DGRAM 3340 746/avahi-daemon: r
unix 3 [ ] STREAM CONNECTED 418 722/dbus-daemon /var/run/dbus/system_bus_socket
unix 3 [ ] STREAM CONNECTED 3347 746/avahi-daemon: r
unix 2 [ ] DGRAM 3105 222/ubusd
unix 3 [ ] STREAM CONNECTED 3186 398/logd
unix 3 [ ] STREAM CONNECTED 3187 222/ubusd /var/run/ubus.sock
unix 2 [ ] DGRAM 3287 603/hostapd
unix 2 [ ] DGRAM 3231 536/dropbear
unix 3 [ ] STREAM CONNECTED 414 722/dbus-daemon
unix 3 [ ] STREAM CONNECTED 413 722/dbus-daemon
unix 3 [ ] STREAM CONNECTED 3106 222/ubusd /var/run/ubus.sock
unix 3 [ ] STREAM CONNECTED 280 1/procd
unix 2 [ ] DGRAM 284 1/procd
unix 2 [ ] DGRAM 3494 1319/nmbd
unix 2 [ ] DGRAM 4626 495/dnsmasq
unix 3 [ ] STREAM CONNECTED 408 222/ubusd /var/run/ubus.sock
unix 2 [ ] DGRAM 12493 2267/wsdd2
unix 3 [ ] STREAM CONNECTED 4675 699/uhttpd
unix 3 [ ] STREAM CONNECTED 4622 495/dnsmasq
unix 3 [ ] STREAM CONNECTED 3216 222/ubusd /var/run/ubus.sock
unix 2 [ ] DGRAM 4623 495/dnsmasq
unix 2 [ ] DGRAM 2416 604/wpa_supplicant
unix 3 [ ] STREAM CONNECTED 3296 222/ubusd /var/run/ubus.sock
unix 3 [ ] STREAM CONNECTED 2422 604/wpa_supplicant
unix 3 [ ] STREAM CONNECTED 3302 222/ubusd /var/run/ubus.sock
unix 3 [ ] STREAM CONNECTED 2427 646/netifd
unix 2 [ ] DGRAM 2425 646/netifd
unix 3 [ ] STREAM CONNECTED 2371 430/rpcd
unix 3 [ ] STREAM CONNECTED 3194 222/ubusd /var/run/ubus.sock
unix 2 [ ] DGRAM 2501 646/netifd
unix 2 [ ] DGRAM 2657 1318/smbd
-------------Code: Select all
logger (19.04.2024 22:17:45): station 1 (Vantage), firmware version request sent.
logger (19.04.2024 22:17:45): station 0 (Vantage), firmware version 3.62 (supports LOOP2)
logger (19.04.2024 22:17:45): station 0 (Vantage), no reading of Vantage's internal logger.
logger (19.04.2024 22:17:45): station 1 (Vantage), firmware version 3.88 (supports LOOP2)
logger (19.04.2024 22:17:45): station 1 (Vantage), no reading of Vantage's internal logger.
logger (19.04.2024 22:17:48): station 2 (Vantage), gettime request sent.
logger (19.04.2024 22:17:48): station 2 (Vantage), no Vantage time offset.
logger (19.04.2024 22:17:48): station 2 (Vantage), eeprom request sent.
logger (19.04.2024 22:17:48): station 2 (Vantage), rain collector size 0.01 inch per tick.
logger (19.04.2024 22:17:48): station 2 (Vantage), transmitter 1 active as station type #3 "Temp/Hum" mapped to "th1".
logger (19.04.2024 22:17:48): station 2 (Vantage), transmitter 2 active as station type #4 "Wind".
logger (19.04.2024 22:17:48): station 2 (Vantage), transmitter 3 active as station type #0 "ISS".
logger (19.04.2024 22:17:48): station 2 (Vantage), firmware version request sent.
logger (19.04.2024 22:17:49): station 2 (Vantage), firmware version 3.80 (supports LOOP2)
logger (19.04.2024 22:17:49): station 2 (Vantage), no reading of Vantage's internal logger.
logger (19.04.2024 22:17:50): sensors are now providing data.
logger (19.04.2024 22:17:50): services started.
logger (20.04.2024 16:44:05): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (20.04.2024 16:45:07): message above repeats 22 times.
logger (20.04.2024 16:45:10): station 0 (Vantage), error make socket 192.168.2.46: port 22222: unknown (22)
logger (20.04.2024 16:45:10): disconnect station 0 (Vantage): socket reconnect failed
logger (20.04.2024 16:45:12): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (20.04.2024 16:45:38): message above repeats 11 times.
logger (20.04.2024 16:45:40): station 0 (Vantage), error make socket 192.168.2.46: port 22222: unknown (22)
logger (20.04.2024 16:45:43): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (20.04.2024 16:46:09): message above repeats 8 times.
logger (20.04.2024 16:46:10): station 0 (Vantage), error make socket 192.168.2.46: port 22222: unknown (22)
logger (20.04.2024 16:46:14): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (20.04.2024 16:46:39): message above repeats 10 times.
logger (20.04.2024 16:46:40): station 0 (Vantage), error make socket 192.168.2.46: port 22222: unknown (22)
logger (20.04.2024 16:46:42): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (20.04.2024 16:47:09): message above repeats 8 times.
logger (20.04.2024 16:47:10): station 0 (Vantage), error make socket 192.168.2.46: port 22222: unknown (22)
logger (20.04.2024 16:47:12): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (20.04.2024 16:47:40): message above repeats 11 times.
logger (20.04.2024 16:47:40): station 0 (Vantage), error make socket 192.168.2.46: port 22222: unknown (22)
logger (20.04.2024 16:47:44): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (20.04.2024 16:48:10): message above repeats 10 times.
logger (20.04.2024 16:48:10): station 0 (Vantage), error make socket 192.168.2.46: port 22222: unknown (22)
logger (20.04.2024 16:48:14): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (20.04.2024 16:48:39): message above repeats 12 times.
logger (20.04.2024 16:48:40): station 0 (Vantage), error make socket 192.168.2.46: port 22222: unknown (22)
logger (20.04.2024 16:48:41): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (20.04.2024 16:49:07): message above repeats 7 times.
logger (20.04.2024 16:49:10): station 0 (Vantage), error make socket 192.168.2.46: port 22222: unknown (22)
logger (20.04.2024 16:49:10): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (20.04.2024 16:49:34): message above repeats 10 times.
logger (20.04.2024 16:49:40): station 0 (Vantage), error make socket 192.168.2.46: port 22222: unknown (22)
logger (20.04.2024 16:49:40): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (20.04.2024 16:50:05): message above repeats 9 times.
logger (20.04.2024 16:50:10): station 0 (Vantage), error make socket 192.168.2.46: port 22222: unknown (22)
logger (20.04.2024 16:50:11): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (20.04.2024 16:50:38): message above repeats 12 times.
logger (20.04.2024 16:50:40): station 0 (Vantage), error make socket 192.168.2.46: port 22222: unknown (22)
logger (20.04.2024 16:50:41): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (20.04.2024 16:51:09): message above repeats 8 times.
logger (20.04.2024 16:51:10): station 0 (Vantage), error make socket 192.168.2.46: port 22222: unknown (22)
logger (20.04.2024 16:51:12): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (20.04.2024 16:51:39): message above repeats 11 times.
logger (20.04.2024 16:51:40): station 0 (Vantage), error make socket 192.168.2.46: port 22222: unknown (22)
logger (20.04.2024 16:51:42): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (20.04.2024 16:52:05): message above repeats 7 times.
logger (20.04.2024 16:52:10): station 0 (Vantage), error make socket 192.168.2.46: port 22222: unknown (22)
logger (20.04.2024 16:52:10): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (20.04.2024 16:52:37): message above repeats 11 times.
logger (20.04.2024 16:52:40): station 0 (Vantage), error make socket 192.168.2.46: port 22222: unknown (22)
logger (20.04.2024 16:52:42): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (20.04.2024 16:53:07): message above repeats 9 times.
logger (20.04.2024 16:53:10): station 0 (Vantage), error make socket 192.168.2.46: port 22222: unknown (22)
logger (20.04.2024 16:53:12): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (20.04.2024 16:53:39): message above repeats 13 times.
logger (20.04.2024 16:53:40): station 0 (Vantage), error make socket 192.168.2.46: port 22222: unknown (22)
logger (20.04.2024 16:53:43): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (20.04.2024 16:54:09): message above repeats 8 times.
logger (20.04.2024 16:54:10): station 0 (Vantage), error make socket 192.168.2.46: port 22222: unknown (22)
logger (20.04.2024 16:54:14): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (20.04.2024 16:54:39): message above repeats 11 times.
logger (20.04.2024 16:54:40): station 0 (Vantage), error make socket 192.168.2.46: port 22222: unknown (22)
logger (20.04.2024 16:54:44): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (20.04.2024 16:55:10): message above repeats 8 times.
logger (20.04.2024 16:55:10): station 0 (Vantage), error make socket 192.168.2.46: port 22222: unknown (22)
logger (20.04.2024 16:55:14): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (20.04.2024 16:55:36): message above repeats 9 times.
logger (20.04.2024 16:55:40): station 0 (Vantage), error make socket 192.168.2.46: port 22222: unknown (22)
logger (20.04.2024 16:55:42): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (20.04.2024 16:56:06): message above repeats 8 times.
logger (20.04.2024 16:56:10): station 0 (Vantage), error make socket 192.168.2.46: port 22222: unknown (22)
logger (20.04.2024 16:56:12): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (20.04.2024 16:56:36): message above repeats 10 times.
logger (20.04.2024 16:56:40): station 0 (Vantage), error make socket 192.168.2.46: port 22222: unknown (22)
logger (20.04.2024 16:56:42): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (20.04.2024 16:57:08): message above repeats 8 times.
logger (20.04.2024 16:57:10): station 0 (Vantage), error make socket 192.168.2.46: port 22222: unknown (22)
logger (20.04.2024 16:57:12): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (20.04.2024 16:57:40): message above repeats 10 times.
logger (20.04.2024 16:57:40): station 0 (Vantage), error make socket 192.168.2.46: port 22222: unknown (22)
logger (20.04.2024 16:57:44): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (20.04.2024 16:58:10): message above repeats 10 times.
logger (20.04.2024 16:58:10): station 0 (Vantage), error make socket 192.168.2.46: port 22222: unknown (22)
logger (20.04.2024 16:58:14): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (20.04.2024 16:58:40): message above repeats 12 times.
logger (20.04.2024 16:58:40): station 0 (Vantage), error make socket 192.168.2.46: port 22222: unknown (22)
logger (20.04.2024 16:58:44): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (20.04.2024 16:59:06): message above repeats 6 times.
logger (20.04.2024 16:59:10): station 0 (Vantage), error make socket 192.168.2.46: port 22222: unknown (22)
logger (20.04.2024 16:59:10): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (20.04.2024 16:59:36): message above repeats 10 times.
logger (20.04.2024 16:59:40): station 0 (Vantage), error make socket 192.168.2.46: port 22222: unknown (22)
logger (20.04.2024 16:59:40): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (20.04.2024 17:00:06): message above repeats 9 times.
logger (20.04.2024 17:00:10): station 0 (Vantage), error make socket 192.168.2.46: port 22222: unknown (22)
logger (20.04.2024 17:00:10): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (20.04.2024 17:00:40): message above repeats 12 times.
logger (20.04.2024 17:00:40): station 0 (Vantage), error make socket 192.168.2.46: port 22222: unknown (22)
logger (20.04.2024 17:00:44): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (20.04.2024 17:01:10): message above repeats 8 times.
logger (20.04.2024 17:01:10): station 0 (Vantage), error make socket 192.168.2.46: port 22222: unknown (22)
logger (20.04.2024 17:01:14): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (20.04.2024 17:01:34): message above repeats 8 times.
logger (20.04.2024 17:01:40): station 0 (Vantage), error make socket 192.168.2.46: port 22222: unknown (22)
logger (20.04.2024 17:01:40): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (20.04.2024 17:02:08): message above repeats 8 times.
logger (20.04.2024 17:02:10): station 0 (Vantage), error make socket 192.168.2.46: port 22222: unknown (22)
logger (20.04.2024 17:02:10): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (20.04.2024 17:02:40): message above repeats 10 times.
logger (20.04.2024 17:02:40): station 0 (Vantage), error make socket 192.168.2.46: port 22222: unknown (22)
logger (20.04.2024 17:02:42): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (20.04.2024 17:03:10): message above repeats 9 times.
logger (20.04.2024 17:03:10): station 0 (Vantage), error make socket 192.168.2.46: port 22222: unknown (22)
logger (20.04.2024 17:03:12): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (20.04.2024 17:03:40): message above repeats 12 times.
logger (20.04.2024 17:03:40): station 0 (Vantage), error make socket 192.168.2.46: port 22222: unknown (22)
logger (20.04.2024 17:03:42): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (20.04.2024 17:04:09): message above repeats 8 times.
logger (20.04.2024 17:04:10): station 0 (Vantage), error make socket 192.168.2.46: port 22222: unknown (22)
logger (20.04.2024 17:04:12): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (20.04.2024 17:04:40): message above repeats 10 times.
logger (20.04.2024 17:04:40): station 0 (Vantage), error make socket 192.168.2.46: port 22222: unknown (22)
logger (20.04.2024 17:04:42): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (20.04.2024 17:05:06): message above repeats 7 times.
logger (20.04.2024 17:05:10): station 0 (Vantage), error make socket 192.168.2.46: port 22222: unknown (22)
logger (20.04.2024 17:05:12): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (20.04.2024 17:05:38): message above repeats 10 times.
logger (20.04.2024 17:05:40): station 0 (Vantage), error make socket 192.168.2.46: port 22222: unknown (22)
logger (20.04.2024 17:05:42): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (20.04.2024 17:06:10): message above repeats 8 times.
logger (20.04.2024 17:06:10): station 0 (Vantage), error make socket 192.168.2.46: port 22222: unknown (22)
logger (20.04.2024 17:06:12): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (20.04.2024 17:06:36): message above repeats 9 times.
logger (20.04.2024 17:06:40): station 0 (Vantage), error make socket 192.168.2.46: port 22222: unknown (22)
logger (20.04.2024 17:06:40): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (20.04.2024 17:07:06): message above repeats 8 times.
logger (20.04.2024 17:07:10): station 0 (Vantage), error make socket 192.168.2.46: port 22222: unknown (22)
logger (20.04.2024 17:07:10): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (20.04.2024 17:07:36): message above repeats 10 times.
logger (20.04.2024 17:07:40): station 0 (Vantage), error make socket 192.168.2.46: port 22222: unknown (22)
logger (20.04.2024 17:07:42): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (20.04.2024 17:08:08): message above repeats 10 times.
logger (20.04.2024 17:08:10): station 0 (Vantage), error make socket 192.168.2.46: port 22222: unknown (22)
logger (20.04.2024 17:08:12): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (20.04.2024 17:08:34): message above repeats 11 times.
logger (20.04.2024 17:08:40): station 0 (Vantage), error make socket 192.168.2.46: port 22222: unknown (22)
logger (20.04.2024 17:08:40): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (20.04.2024 17:09:06): message above repeats 8 times.
logger (20.04.2024 17:09:10): station 0 (Vantage), error make socket 192.168.2.46: port 22222: unknown (22)
logger (20.04.2024 17:09:10): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (20.04.2024 17:09:40): message above repeats 10 times.
logger (20.04.2024 17:09:40): station 0 (Vantage), error make socket 192.168.2.46: port 22222: unknown (22)
logger (20.04.2024 17:09:42): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (20.04.2024 17:10:10): message above repeats 9 times.
logger (20.04.2024 17:10:10): station 0 (Vantage), error make socket 192.168.2.46: port 22222: unknown (22)
logger (20.04.2024 17:10:12): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (20.04.2024 17:10:40): message above repeats 11 times.
logger (20.04.2024 17:10:40): station 0 (Vantage), error make socket 192.168.2.46: port 22222: unknown (22)
logger (20.04.2024 17:10:42): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (20.04.2024 17:11:10): message above repeats 8 times.
logger (20.04.2024 17:11:10): station 0 (Vantage), error make socket 192.168.2.46: port 22222: unknown (22)
logger (20.04.2024 17:11:12): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (20.04.2024 17:11:40): message above repeats 10 times.
logger (20.04.2024 17:11:40): station 0 (Vantage), error make socket 192.168.2.46: port 22222: unknown (22)
logger (20.04.2024 17:11:42): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (20.04.2024 17:12:06): message above repeats 7 times.
logger (20.04.2024 17:12:10): station 0 (Vantage), error make socket 192.168.2.46: port 22222: unknown (22)
logger (20.04.2024 17:12:12): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (20.04.2024 17:12:36): message above repeats 10 times.
logger (20.04.2024 17:12:40): station 0 (Vantage), error make socket 192.168.2.46: port 22222: unknown (22)
logger (20.04.2024 17:12:42): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (20.04.2024 17:13:08): message above repeats 9 times.
logger (20.04.2024 17:13:10): station 0 (Vantage), error make socket 192.168.2.46: port 22222: unknown (22)
logger (20.04.2024 17:13:12): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (20.04.2024 17:13:38): message above repeats 12 times.
logger (20.04.2024 17:13:40): station 0 (Vantage), error make socket 192.168.2.46: port 22222: unknown (22)
logger (20.04.2024 17:13:42): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (20.04.2024 17:14:10): message above repeats 8 times.
logger (20.04.2024 17:14:10): station 0 (Vantage), error make socket 192.168.2.46: port 22222: unknown (22)
logger (20.04.2024 17:14:12): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (20.04.2024 17:14:38): message above repeats 9 times.
logger (20.04.2024 17:14:40): station 0 (Vantage), error make socket 192.168.2.46: port 22222: unknown (22)
logger (20.04.2024 17:14:42): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (20.04.2024 17:15:08): message above repeats 8 times.
logger (20.04.2024 17:15:10): station 0 (Vantage), error make socket 192.168.2.46: port 22222: unknown (22)
logger (20.04.2024 17:15:12): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (20.04.2024 17:15:39): message above repeats 10 times.
logger (20.04.2024 17:15:40): station 0 (Vantage), error make socket 192.168.2.46: port 22222: unknown (22)
logger (20.04.2024 17:15:44): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (20.04.2024 17:16:09): message above repeats 8 times.
logger (20.04.2024 17:16:10): station 0 (Vantage), error make socket 192.168.2.46: port 22222: unknown (22)
logger (20.04.2024 17:16:16): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (20.04.2024 17:16:36): message above repeats 9 times.
logger (20.04.2024 17:16:40): station 0 (Vantage), error make socket 192.168.2.46: port 22222: unknown (22)
logger (20.04.2024 17:16:41): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (20.04.2024 17:17:07): message above repeats 8 times.
logger (20.04.2024 17:17:10): station 0 (Vantage), error make socket 192.168.2.46: port 22222: unknown (22)
logger (20.04.2024 17:17:12): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (20.04.2024 17:17:38): message above repeats 10 times.
logger (20.04.2024 17:17:40): station 0 (Vantage), error make socket 192.168.2.46: port 22222: unknown (22)
logger (20.04.2024 17:17:43): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (20.04.2024 17:17:53): message above repeats 3 times.
logger (20.04.2024 17:17:55): error while doing accept on socket 5558 (22): Invalid argument
logger (20.04.2024 17:18:00): message above repeats 108 times.
logger (20.04.2024 17:18:01): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (20.04.2024 17:18:01): message above repeats 3 times.
logger (20.04.2024 17:18:02): error while doing accept on socket 5558 (22): Invalid argument
logger (20.04.2024 17:18:03): message above repeats 20 times.
Re: MB keeps losing contact with Loggers.
Keeps failing.
I'm about done with this MB. Cumulus on RPi Zero W doesn't do this.
May as well set up CMX now that I am on RPi anyway.
Can I give away my license to someone else?
I'm about done with this MB. Cumulus on RPi Zero W doesn't do this.
May as well set up CMX now that I am on RPi anyway.
Can I give away my license to someone else?
Re: MB keeps losing contact with Loggers.
Sorry that your unique issue could not be resolved and good luck on the Cumulus side.
Re: MB keeps losing contact with Loggers.
There's more to this than meets the eye.
I had a decent run after deleting the Station from MB that seemed to be at the root.
Taking a look at logger, it had an SD card installed that had intermittent data logs. Thinking the card that is total junk, nothing but 16GB printed on it but reports as a 32GB, is the issue, I set it up again and connect to MB.
Failed after 6 hours or so.
I now have 48 hours (--knock wood--) with no shutdown, with just the other two loggers.
Something about that particular piece of hardware, as it is on same FW, or MB not able to handle three Stations, or more than one WiFi Station.......
I had a decent run after deleting the Station from MB that seemed to be at the root.
Taking a look at logger, it had an SD card installed that had intermittent data logs. Thinking the card that is total junk, nothing but 16GB printed on it but reports as a 32GB, is the issue, I set it up again and connect to MB.
Failed after 6 hours or so.
I now have 48 hours (--knock wood--) with no shutdown, with just the other two loggers.
Something about that particular piece of hardware, as it is on same FW, or MB not able to handle three Stations, or more than one WiFi Station.......
Re: MB keeps losing contact with Loggers.
What is the make/model of that suspect SD card?davidmc36 wrote: ↑Wed May 01, 2024 12:30 pm .... Taking a look at logger, it had an SD card installed that had intermittent data logs. Thinking the card that is total junk, nothing but 16GB printed on it but reports as a 32GB, is the issue, I set it up again and connect to MB. Failed after 6 hours or so....
Re: MB keeps losing contact with Loggers.
As I said, the only thing printed on it is 16GB. Yet it reports as 32GB. No more comments on the quality of that card is reqd. lol I remember where it came from. A really crappy dash cam that failed.Mattk wrote: ↑Wed May 01, 2024 10:30 pmWhat is the make/model of that suspect SD card?davidmc36 wrote: ↑Wed May 01, 2024 12:30 pm .... Taking a look at logger, it had an SD card installed that had intermittent data logs. Thinking the card that is total junk, nothing but 16GB printed on it but reports as a 32GB, is the issue, I set it up again and connect to MB. Failed after 6 hours or so....
At any rate, the card is physically removed and the logger is not a Station connected to MB at this time.
Re: MB keeps losing contact with Loggers.
Removed and binned is the only place for itdavidmc36 wrote: ↑Thu May 02, 2024 6:38 amAs I said, the only thing printed on it is 16GB. Yet it reports as 32GB. No more comments on the quality of that card is reqd. lol I remember where it came from. A really crappy dash cam that failed.Mattk wrote: ↑Wed May 01, 2024 10:30 pmWhat is the make/model of that suspect SD card?davidmc36 wrote: ↑Wed May 01, 2024 12:30 pm .... Taking a look at logger, it had an SD card installed that had intermittent data logs. Thinking the card that is total junk, nothing but 16GB printed on it but reports as a 32GB, is the issue, I set it up again and connect to MB. Failed after 6 hours or so....
At any rate, the card is physically removed and the logger is not a Station connected to MB at this time.
Re: MB keeps losing contact with Loggers.
I'm going to try my spare logger later today. Then I have one more "tweak" to test.
Stay Tuned!
D
Stay Tuned!
D
Re: MB keeps losing contact with Loggers.
Finally found a spare minute to try a swap.
It seems to look like a hardware issue. With spare logger swapped in it seems solid (knock wood). Really needs a couple more days at least though.
If it remains good for a bit, I will upgrade Logger FW from current 2.41 to the 2.42 the other was running on. Then will set logger to Static IP and use the same IP as the offender.
That will duplicate every specific of the offender.
D
It seems to look like a hardware issue. With spare logger swapped in it seems solid (knock wood). Really needs a couple more days at least though.
If it remains good for a bit, I will upgrade Logger FW from current 2.41 to the 2.42 the other was running on. Then will set logger to Static IP and use the same IP as the offender.
That will duplicate every specific of the offender.
D
Re: MB keeps losing contact with Loggers.
Still working through different hardware combinations as no clear pattern has emerged yet.
Tests continue.
Tests continue.
Re: MB keeps losing contact with Loggers.
It seems to be emerging as related to the particular console. Had trouble with only two loggers.
Next to try that unit exclusively.
D
Next to try that unit exclusively.
D
Re: MB keeps losing contact with Loggers.
There has been no success in pinpointing any hardware as a culprit.
Will exhibit the same behavior with any combination of one or more of the four loggers attached to any of three consoles. Two consoles running 3.88 FW and one has 3.80 with the Ethernet Logger.
Keeps doing this, and eventually stops receiving Data.
The only thing I can think of at this point is have the RPi plugged into a WiFi controlled switch that has a schedule to shut down for one minute every hour or something.
I've left the MB on 5.9 as I read about some issue with 6.0
Will exhibit the same behavior with any combination of one or more of the four loggers attached to any of three consoles. Two consoles running 3.88 FW and one has 3.80 with the Ethernet Logger.
Keeps doing this, and eventually stops receiving Data.
The only thing I can think of at this point is have the RPi plugged into a WiFi controlled switch that has a schedule to shut down for one minute every hour or something.
I've left the MB on 5.9 as I read about some issue with 6.0
Code: Select all
logger (16.06.2024 17:02:33): station 0 (Vantage), eeprom request sent.
logger (16.06.2024 17:02:33): station 0 (Vantage), rain collector size 0.01 inch per tick.
logger (16.06.2024 17:02:33): station 0 (Vantage), transmitter 1 active as station type #0 "ISS".
logger (16.06.2024 17:02:33): station 0 (Vantage), transmitter 2 active as station type #4 "Wind".
logger (16.06.2024 17:02:33): station 0 (Vantage), firmware version request sent.
logger (16.06.2024 17:02:33): station 0 (Vantage), firmware version 3.88 (supports LOOP2)
logger (16.06.2024 17:02:33): station 0 (Vantage), no reading of Vantage's internal logger.
logger (16.06.2024 17:02:38): sensors are now providing data.
logger (16.06.2024 17:02:38): services started.
logger (16.06.2024 17:17:48): child process received termination signal (15).
logger (16.06.2024 17:17:48): parent process received termination signal (15).
logger (16.06.2024 17:17:48): disconnect station 0 (Vantage): exit
logger (16.06.2024 17:17:48): disconnect station 9 (System Data): exit
logger (16.06.2024 17:17:49): data logger stopped.
logger (16.06.2024 17:17:49): databases disconnected.
logger (16.06.2024 17:17:49): parent process to be terminated.
test5m (16.06.2024 17:20:43): logger stalled, will be restarted now.
system (16.06.2024 17:20:43): stop of logging process initiated.
system (16.06.2024 17:20:44): start of logging process initiated.
logger (16.06.2024 17:20:44): databases connected. Update interval 3600 seconds.
logger (16.06.2024 17:20:44): data logger started.
logger (16.06.2024 17:20:44): connect station 0 (Vantage via TCP/IP).
logger (16.06.2024 17:20:44): connect station 9 (System Data via Plug-in).
logger (16.06.2024 17:20:45): station 0 (Vantage), wakeup sent.
logger (16.06.2024 17:20:48): waiting for sensors (wind0, rain0, th0, thb0) to provide data.
logger (16.06.2024 17:20:48): services paused.
logger (16.06.2024 17:20:49): station 0 (Vantage), no need to update console date/time.
logger (16.06.2024 17:20:50): station 0 (Vantage), setup script executed.
logger (16.06.2024 17:20:50): station 0 (Vantage), internal logger activated.
logger (16.06.2024 17:20:50): station 0 (Vantage), syncing.
logger (16.06.2024 17:21:00): station 0 (Vantage), gettime request sent.
logger (16.06.2024 17:21:00): station 0 (Vantage), no Vantage time offset.
logger (16.06.2024 17:21:00): station 0 (Vantage), eeprom request sent.
logger (16.06.2024 17:21:00): station 0 (Vantage), rain collector size 0.01 inch per tick.
logger (16.06.2024 17:21:00): station 0 (Vantage), transmitter 1 active as station type #0 "ISS".
logger (16.06.2024 17:21:00): station 0 (Vantage), transmitter 2 active as station type #4 "Wind".
logger (16.06.2024 17:21:00): station 0 (Vantage), firmware version request sent.
logger (16.06.2024 17:21:00): station 0 (Vantage), firmware version 3.88 (supports LOOP2)
logger (16.06.2024 17:21:00): station 0 (Vantage), no reading of Vantage's internal logger.
logger (16.06.2024 17:21:05): sensors are now providing data.
logger (16.06.2024 17:21:05): services started.
logger (16.06.2024 17:21:12): child process received termination signal (15).
logger (16.06.2024 17:21:12): parent process received termination signal (15).
logger (16.06.2024 17:21:12): disconnect station 0 (Vantage): exit
logger (16.06.2024 17:21:12): disconnect station 9 (System Data): exit
logger (16.06.2024 17:21:13): data logger stopped.
logger (16.06.2024 17:21:13): databases disconnected.
logger (16.06.2024 17:21:13): parent process to be terminated.
test5m (16.06.2024 17:26:38): logger stalled, will be restarted now.
system (16.06.2024 17:26:38): stop of logging process initiated.
system (16.06.2024 17:26:39): start of logging process initiated.
logger (16.06.2024 17:26:39): databases connected. Update interval 3600 seconds.
logger (16.06.2024 17:26:39): data logger started.
logger (16.06.2024 17:26:39): connect station 0 (Vantage via TCP/IP).
logger (16.06.2024 17:26:39): connect station 9 (System Data via Plug-in).
logger (16.06.2024 17:26:40): station 0 (Vantage), wakeup sent.
logger (16.06.2024 17:26:43): waiting for sensors (wind0, rain0, th0, thb0) to provide data.
logger (16.06.2024 17:26:43): services paused.
logger (16.06.2024 17:26:52): station 0 (Vantage), execution of setup script failed (console is not responding).
logger (16.06.2024 17:26:52): station 0 (Vantage), internal logger activated.
logger (16.06.2024 17:26:52): station 0 (Vantage), syncing.
logger (16.06.2024 17:26:52): station 0 (Vantage), gettime request sent.
logger (16.06.2024 17:27:02): message above repeats 1 time.
logger (16.06.2024 17:27:02): station 0 (Vantage), no Vantage time offset.
logger (16.06.2024 17:27:02): station 0 (Vantage), eeprom request sent.
logger (16.06.2024 17:27:02): station 0 (Vantage), rain collector size 0.01 inch per tick.
logger (16.06.2024 17:27:02): station 0 (Vantage), transmitter 1 active as station type #0 "ISS".
logger (16.06.2024 17:27:02): station 0 (Vantage), transmitter 2 active as station type #4 "Wind".
logger (16.06.2024 17:27:02): station 0 (Vantage), firmware version request sent.
logger (16.06.2024 17:27:02): station 0 (Vantage), firmware version 3.88 (supports LOOP2)
logger (16.06.2024 17:27:02): station 0 (Vantage), no reading of Vantage's internal logger.
logger (16.06.2024 17:27:07): sensors are now providing data.
logger (16.06.2024 17:27:07): services started.
logger (16.06.2024 17:27:16): child process received termination signal (15).
logger (16.06.2024 17:27:16): parent process received termination signal (15).
logger (16.06.2024 17:27:16): disconnect station 0 (Vantage): exit
logger (16.06.2024 17:27:16): disconnect station 9 (System Data): exit
logger (16.06.2024 17:27:17): data logger stopped.
logger (16.06.2024 17:27:17): databases disconnected.
logger (16.06.2024 17:27:17): parent process to be terminated.
test5m (16.06.2024 17:30:18): logger stalled, will be restarted now.
system (16.06.2024 17:30:18): stop of logging process initiated.
system (16.06.2024 17:30:19): start of logging process initiated.
logger (16.06.2024 17:30:19): databases connected. Update interval 3600 seconds.
logger (16.06.2024 17:30:19): data logger started.
logger (16.06.2024 17:30:19): connect station 0 (Vantage via TCP/IP).
logger (16.06.2024 17:30:19): connect station 9 (System Data via Plug-in).
logger (16.06.2024 17:30:20): station 0 (Vantage), wakeup sent.
logger (16.06.2024 17:30:23): waiting for sensors (wind0, rain0, th0, thb0) to provide data.
logger (16.06.2024 17:30:23): services paused.
logger (16.06.2024 17:30:24): station 0 (Vantage), no need to update console date/time.
logger (16.06.2024 17:30:24): station 0 (Vantage), setup script executed.
logger (16.06.2024 17:30:25): station 0 (Vantage), internal logger activated.
logger (16.06.2024 17:30:25): station 0 (Vantage), syncing.
logger (16.06.2024 17:30:35): station 0 (Vantage), gettime request sent.
logger (16.06.2024 17:30:35): station 0 (Vantage), no Vantage time offset.
logger (16.06.2024 17:30:35): station 0 (Vantage), eeprom request sent.
logger (16.06.2024 17:30:35): station 0 (Vantage), rain collector size 0.01 inch per tick.
logger (16.06.2024 17:30:35): station 0 (Vantage), transmitter 1 active as station type #0 "ISS".
logger (16.06.2024 17:30:35): station 0 (Vantage), transmitter 2 active as station type #4 "Wind".
logger (16.06.2024 17:30:35): station 0 (Vantage), firmware version request sent.
logger (16.06.2024 17:30:35): station 0 (Vantage), firmware version 3.88 (supports LOOP2)
logger (16.06.2024 17:30:35): station 0 (Vantage), no reading of Vantage's internal logger.
logger (16.06.2024 17:30:39): sensors are now providing data.
logger (16.06.2024 17:30:39): services started.
logger (16.06.2024 17:30:46): child process received termination signal (15).
logger (16.06.2024 17:30:46): parent process received termination signal (15).
logger (16.06.2024 17:30:46): disconnect station 0 (Vantage): exit
logger (16.06.2024 17:30:46): disconnect station 9 (System Data): exit
logger (16.06.2024 17:30:47): data logger stopped.
logger (16.06.2024 17:30:47): databases disconnected.
logger (16.06.2024 17:30:47): parent process to be terminated.
test5m (16.06.2024 17:35:59): logger stalled, will be restarted now.
system (16.06.2024 17:35:59): stop of logging process initiated.
system (16.06.2024 17:36:00): start of logging process initiated.
logger (16.06.2024 17:36:00): databases connected. Update interval 3600 seconds.
logger (16.06.2024 17:36:00): data logger started.
logger (16.06.2024 17:36:00): connect station 0 (Vantage via TCP/IP).
logger (16.06.2024 17:36:00): connect station 9 (System Data via Plug-in).
logger (16.06.2024 17:36:01): station 0 (Vantage), wakeup sent.
logger (16.06.2024 17:36:04): waiting for sensors (wind0, rain0, th0, thb0) to provide data.
logger (16.06.2024 17:36:04): services paused.
logger (16.06.2024 17:36:05): station 0 (Vantage), no need to update console date/time.
logger (16.06.2024 17:36:06): station 0 (Vantage), setup script executed.
logger (16.06.2024 17:36:06): station 0 (Vantage), internal logger activated.
logger (16.06.2024 17:36:06): station 0 (Vantage), syncing.
logger (16.06.2024 17:36:16): station 0 (Vantage), gettime request sent.
logger (16.06.2024 17:36:16): station 0 (Vantage), no Vantage time offset.
logger (16.06.2024 17:36:16): station 0 (Vantage), eeprom request sent.
logger (16.06.2024 17:36:16): station 0 (Vantage), rain collector size 0.01 inch per tick.
logger (16.06.2024 17:36:16): station 0 (Vantage), transmitter 1 active as station type #0 "ISS".
logger (16.06.2024 17:36:16): station 0 (Vantage), transmitter 2 active as station type #4 "Wind".
logger (16.06.2024 17:36:16): station 0 (Vantage), firmware version request sent.
logger (16.06.2024 17:36:16): station 0 (Vantage), firmware version 3.88 (supports LOOP2)
logger (16.06.2024 17:36:16): station 0 (Vantage), no reading of Vantage's internal logger.
logger (16.06.2024 17:36:21): sensors are now providing data.
logger (16.06.2024 17:36:21): services started.
logger (16.06.2024 17:36:28): child process received termination signal (15).
logger (16.06.2024 17:36:28): parent process received termination signal (15).
logger (16.06.2024 17:36:28): disconnect station 0 (Vantage): exit
logger (16.06.2024 17:36:28): disconnect station 9 (System Data): exit
logger (16.06.2024 17:36:29): data logger stopped.
logger (16.06.2024 17:36:29): databases disconnected.
logger (16.06.2024 17:36:29): parent process to be terminated.
test5m (16.06.2024 17:40:27): logger stalled, will be restarted now.
system (16.06.2024 17:40:27): stop of logging process initiated.
system (16.06.2024 17:40:28): start of logging process initiated.
logger (16.06.2024 17:40:28): databases connected. Update interval 3600 seconds.
logger (16.06.2024 17:40:28): data logger started.
logger (16.06.2024 17:40:28): connect station 0 (Vantage via TCP/IP).
logger (16.06.2024 17:40:28): connect station 9 (System Data via Plug-in).
logger (16.06.2024 17:40:29): station 0 (Vantage), wakeup sent.
logger (16.06.2024 17:40:32): waiting for sensors (wind0, rain0, th0, thb0) to provide data.
logger (16.06.2024 17:40:32): services paused.
logger (16.06.2024 17:40:41): station 0 (Vantage), execution of setup script failed (console is not responding).
logger (16.06.2024 17:40:41): station 0 (Vantage), internal logger activated.
logger (16.06.2024 17:40:41): station 0 (Vantage), syncing.
logger (16.06.2024 17:40:41): station 0 (Vantage), gettime request sent.
logger (16.06.2024 17:40:41): station 0 (Vantage), no Vantage time offset.
logger (16.06.2024 17:40:41): station 0 (Vantage), eeprom request sent.
logger (16.06.2024 17:40:41): station 0 (Vantage), rain collector size 0.01 inch per tick.
logger (16.06.2024 17:40:41): station 0 (Vantage), transmitter 1 active as station type #0 "ISS".
logger (16.06.2024 17:40:41): station 0 (Vantage), transmitter 2 active as station type #4 "Wind".
logger (16.06.2024 17:40:41): station 0 (Vantage), firmware version request sent.
logger (16.06.2024 17:40:41): station 0 (Vantage), firmware version 3.88 (supports LOOP2)
logger (16.06.2024 17:40:41): station 0 (Vantage), no reading of Vantage's internal logger.
logger (16.06.2024 17:40:45): sensors are now providing data.
logger (16.06.2024 17:40:45): services started.
logger (16.06.2024 17:40:52): child process received termination signal (15).
logger (16.06.2024 17:40:52): parent process received termination signal (15).
logger (16.06.2024 17:40:52): disconnect station 0 (Vantage): exit
logger (16.06.2024 17:40:52): disconnect station 9 (System Data): exit
logger (16.06.2024 17:40:53): data logger stopped.
logger (16.06.2024 17:40:53): databases disconnected.
logger (16.06.2024 17:40:53): parent process to be terminated.
test5m (16.06.2024 17:46:11): logger stalled, will be restarted now.
system (16.06.2024 17:46:11): stop of logging process initiated.
system (16.06.2024 17:46:12): start of logging process initiated.
logger (16.06.2024 17:46:12): databases connected. Update interval 3600 seconds.
logger (16.06.2024 17:46:12): data logger started.
logger (16.06.2024 17:46:12): connect station 0 (Vantage via TCP/IP).
logger (16.06.2024 17:46:12): connect station 9 (System Data via Plug-in).
logger (16.06.2024 17:46:13): station 0 (Vantage), wakeup sent.
logger (16.06.2024 17:46:16): waiting for sensors (wind0, rain0, th0, thb0) to provide data.
logger (16.06.2024 17:46:16): services paused.
logger (16.06.2024 17:46:17): station 0 (Vantage), no need to update console date/time.
logger (16.06.2024 17:46:18): station 0 (Vantage), setup script executed.
logger (16.06.2024 17:46:18): station 0 (Vantage), internal logger activated.
logger (16.06.2024 17:46:18): station 0 (Vantage), syncing.
logger (16.06.2024 17:46:28): station 0 (Vantage), gettime request sent.
logger (16.06.2024 17:46:28): station 0 (Vantage), no Vantage time offset.
logger (16.06.2024 17:46:28): station 0 (Vantage), eeprom request sent.
logger (16.06.2024 17:46:28): station 0 (Vantage), rain collector size 0.01 inch per tick.
logger (16.06.2024 17:46:28): station 0 (Vantage), transmitter 1 active as station type #0 "ISS".
logger (16.06.2024 17:46:28): station 0 (Vantage), transmitter 2 active as station type #4 "Wind".
logger (16.06.2024 17:46:28): station 0 (Vantage), firmware version request sent.
logger (16.06.2024 17:46:28): station 0 (Vantage), firmware version 3.88 (supports LOOP2)
logger (16.06.2024 17:46:28): station 0 (Vantage), no reading of Vantage's internal logger.
logger (16.06.2024 17:46:33): sensors are now providing data.
logger (16.06.2024 17:46:33): services started.
Re: MB keeps losing contact with Loggers.
Seemed to go OK for about two hours..........then:
Code: Select all
logger (17.06.2024 00:01:27): station 0 (Vantage), transmitter 1 active as station type #0 "ISS".
logger (17.06.2024 00:01:27): station 0 (Vantage), transmitter 2 active as station type #4 "Wind".
logger (17.06.2024 00:01:27): station 0 (Vantage), firmware version request sent.
logger (17.06.2024 00:01:27): station 0 (Vantage), firmware version 3.88 (supports LOOP2)
logger (17.06.2024 00:01:27): station 0 (Vantage), no reading of Vantage's internal logger.
logger (17.06.2024 00:01:31): sensors are now providing data.
logger (17.06.2024 00:01:31): services started.
logger (17.06.2024 02:02:05): child process received termination signal (15).
logger (17.06.2024 02:02:05): parent process received termination signal (15).
logger (17.06.2024 02:02:05): disconnect station 0 (Vantage): exit
logger (17.06.2024 02:02:05): disconnect station 9 (System Data): exit
logger (17.06.2024 02:02:05): data logger stopped.
logger (17.06.2024 02:02:05): databases disconnected.
logger (17.06.2024 02:02:05): parent process to be terminated.
test5m (17.06.2024 02:05:07): logger stalled, will be restarted now.
system (17.06.2024 02:05:07): stop of logging process initiated.