MR3020 V1 with GW1000 Lots of logger restarts

[galfert]

This is something new. Before Nov 7 build things ran smoothly without logger restarts. I've not made any changes to any Meteobridge settings in a long time. There is a recent GW1000 firmware 1.5.3 available (came out about a week ago) but I've not upgraded. I'm still running GW1000 firmware 1.5.2 that I've had for months. So nothing has changed with my GW1000 either.

Platform: TL-MR3020 (no USB hub)
RAM: 29364 kB total, 1776 kB free (93% used)
SW Version: Meteobridge 4.2 (Nov 7 2019, build 13265), FW 1.4
Uptime: 4 days, 20 hours, 41 minutes Buffer: 3 items (0%)

system (11.11.2019 12:19:37): start of logging process initiated.
wnetd (11.11.2019 12:19:37): process started.
logger (11.11.2019 12:19:38): historical data loaded (29 records).
logger (11.11.2019 12:19:38): data logger (version 5.1b, build 13265) started.
logger (11.11.2019 12:19:39): connect station 0 (GW1000 via TCP/IP).
logger (11.11.2019 12:19:42): waiting for sensors (wind0, rain0, th0, thb0) to provide data.
logger (11.11.2019 12:19:42): services paused.
logger (11.11.2019 12:19:44): sensors are now providing data.
logger (11.11.2019 12:19:44): services started.
logger (12.11.2019 12:32:40): parent process received termination signal (15).
logger (12.11.2019 12:32:40): child process received termination signal (15).
logger (12.11.2019 12:32:40): disconnect station 0 (GW1000): exit
logger (12.11.2019 12:32:46): data logger stopped.
test5m (12.11.2019 17:35:39): logger stalled, will be restarted now.
system (12.11.2019 17:35:39): stop of logging process initiated.
system (12.11.2019 17:35:40): start of logging process initiated.
logger (12.11.2019 12:35:40): historical data loaded (29 records).
logger (12.11.2019 12:35:40): data logger (version 5.1b, build 13265) started.
logger (12.11.2019 12:35:41): connect station 0 (GW1000 via TCP/IP).
logger (12.11.2019 12:35:44): sensors are now providing data.
logger (12.11.2019 12:35:44): services started.
logger (13.11.2019 03:03:36): unexpected 0 bytes.
logger (13.11.2019 03:03:36): disconnect station 0 (GW1000): response without data
logger (13.11.2019 03:04:06): connect station 0 (GW1000 via TCP/IP).
logger (14.11.2019 02:30:10): child process received termination signal (15).
logger (14.11.2019 02:30:10): parent process received termination signal (15).
logger (14.11.2019 02:30:10): disconnect station 0 (GW1000): exit
logger (14.11.2019 02:30:11): data logger stopped.
test5m (14.11.2019 07:30:41): logger stalled, will be restarted now.
system (14.11.2019 07:30:41): stop of logging process initiated.
system (14.11.2019 07:30:41): start of logging process initiated.
logger (14.11.2019 02:30:41): historical data loaded (29 records).
logger (14.11.2019 02:30:41): data logger (version 5.1b, build 13265) started.
logger (14.11.2019 02:30:42): connect station 0 (GW1000 via TCP/IP).
logger (14.11.2019 02:30:46): sensors are now providing data.
logger (14.11.2019 02:30:46): services started.
logger (14.11.2019 09:31:28): child process received termination signal (15).
logger (14.11.2019 09:31:28): disconnect station 0 (GW1000): exit
logger (14.11.2019 09:31:28): parent process received termination signal (15).
logger (14.11.2019 09:31:30): data logger stopped.
test5m (14.11.2019 14:35:52): logger stalled, will be restarted now.
system (14.11.2019 14:35:52): stop of logging process initiated.
system (14.11.2019 14:35:52): start of logging process initiated.
logger (14.11.2019 09:35:53): historical data loaded (29 records).
logger (14.11.2019 09:35:53): data logger (version 5.1b, build 13265) started.
logger (14.11.2019 09:35:54): connect station 0 (GW1000 via TCP/IP).
logger (14.11.2019 09:35:57): sensors are now providing data.
logger (14.11.2019 09:35:57): services started.
logger (14.11.2019 10:06:06): child process received termination signal (15).
logger (14.11.2019 10:06:07): parent process received termination signal (15).
logger (14.11.2019 10:06:09): disconnect station 0 (GW1000): exit
logger (14.11.2019 10:06:10): data logger stopped.
test5m (14.11.2019 15:06:26): logger stalled, will be restarted now.
system (14.11.2019 15:06:26): stop of logging process initiated.
system (14.11.2019 15:06:26): start of logging process initiated.
logger (14.11.2019 10:06:27): historical data loaded (29 records).
logger (14.11.2019 10:06:27): data logger (version 5.1b, build 13265) started.
logger (14.11.2019 10:06:28): connect station 0 (GW1000 via TCP/IP).
logger (14.11.2019 10:06:31): sensors are now providing data.
logger (14.11.2019 10:06:31): services started.
logger (14.11.2019 15:57:14): child process received termination signal (15).
logger (14.11.2019 15:57:15): parent process received termination signal (15).
logger (14.11.2019 15:57:15): disconnect station 0 (GW1000): exit
logger (14.11.2019 15:57:16): data logger stopped.
test5m (14.11.2019 21:00:58): logger stalled, will be restarted now.
system (14.11.2019 21:00:58): stop of logging process initiated.
system (14.11.2019 21:00:58): start of logging process initiated.
logger (14.11.2019 16:00:59): historical data loaded (29 records).
logger (14.11.2019 16:00:59): data logger (version 5.1b, build 13265) started.
logger (14.11.2019 16:01:01): connect station 0 (GW1000 via TCP/IP).
logger (14.11.2019 16:01:04): sensors are now providing data.
logger (14.11.2019 16:01:04): services started.
logger (14.11.2019 18:31:18): child process received termination signal (15).
logger (14.11.2019 18:31:18): parent process received termination signal (15).
logger (14.11.2019 18:31:18): disconnect station 0 (GW1000): exit
logger (14.11.2019 18:31:19): data logger stopped.
test5m (14.11.2019 23:36:24): logger stalled, will be restarted now.
system (14.11.2019 23:36:25): stop of logging process initiated.
system (14.11.2019 23:36:25): start of logging process initiated.
logger (14.11.2019 18:36:25): historical data loaded (29 records).
logger (14.11.2019 18:36:25): data logger (version 5.1b, build 13265) started.
logger (14.11.2019 18:36:26): connect station 0 (GW1000 via TCP/IP).
logger (14.11.2019 18:36:30): sensors are now providing data.
logger (14.11.2019 18:36:30): services started.
logger (15.11.2019 12:18:29): child process received termination signal (15).
logger (15.11.2019 12:18:30): parent process received termination signal (15).
logger (15.11.2019 12:18:30): disconnect station 0 (GW1000): exit
logger (15.11.2019 12:18:35): data logger stopped.
test5m (15.11.2019 17:21:27): logger stalled, will be restarted now.
system (15.11.2019 17:21:27): stop of logging process initiated.
system (15.11.2019 17:21:27): start of logging process initiated.
logger (15.11.2019 12:21:28): historical data loaded (29 records).
logger (15.11.2019 12:21:28): data logger (version 5.1b, build 13265) started.
logger (15.11.2019 12:21:29): connect station 0 (GW1000 via TCP/IP).
logger (15.11.2019 12:21:32): sensors are now providing data.
logger (15.11.2019 12:21:32): services started.
logger (15.11.2019 14:21:52): child process received termination signal (15).
logger (15.11.2019 14:21:52): parent process received termination signal (15).
logger (15.11.2019 14:21:52): disconnect station 0 (GW1000): exit
logger (15.11.2019 14:21:56): data logger stopped.
test5m (15.11.2019 19:25:27): logger stalled, will be restarted now.
system (15.11.2019 19:25:27): stop of logging process initiated.
system (15.11.2019 19:25:27): start of logging process initiated.
logger (15.11.2019 14:25:28): historical data loaded (29 records).
logger (15.11.2019 14:25:28): data logger (version 5.1b, build 13265) started.
logger (15.11.2019 14:25:29): connect station 0 (GW1000 via TCP/IP).
logger (15.11.2019 14:25:32): sensors are now providing data.
logger (15.11.2019 14:25:32): services started.
logger (15.11.2019 16:15:48): child process received termination signal (15).
logger (15.11.2019 16:15:48): parent process received termination signal (15).
logger (15.11.2019 16:15:48): disconnect station 0 (GW1000): exit
logger (15.11.2019 16:15:49): data logger stopped.
test5m (15.11.2019 21:21:38): logger stalled, will be restarted now.
system (15.11.2019 21:21:38): stop of logging process initiated.
system (15.11.2019 21:21:39): start of logging process initiated.
logger (15.11.2019 16:21:39): historical data loaded (29 records).
logger (15.11.2019 16:21:39): data logger (version 5.1b, build 13265) started.
logger (15.11.2019 16:21:40): connect station 0 (GW1000 via TCP/IP).
logger (15.11.2019 16:21:44): sensors are now providing data.
logger (15.11.2019 16:21:44): services started.
logger (16.11.2019 08:53:46): child process received termination signal (15).
logger (16.11.2019 08:53:47): parent process received termination signal (15).
logger (16.11.2019 08:53:47): disconnect station 0 (GW1000): exit
logger (16.11.2019 08:53:49): data logger stopped.
test5m (16.11.2019 13:55:38): logger stalled, will be restarted now.
system (16.11.2019 13:55:39): stop of logging process initiated.
system (16.11.2019 13:55:39): start of logging process initiated.
logger (16.11.2019 08:55:39): historical data loaded (29 records).
logger (16.11.2019 08:55:39): data logger (version 5.1b, build 13265) started.
logger (16.11.2019 08:55:41): connect station 0 (GW1000 via TCP/IP).
logger (16.11.2019 08:55:44): sensors are now providing data.
logger (16.11.2019 08:55:44): services started.

[admin]

Is your GW1000 on a fixed IP?

[galfert]

My GW1000 is on a Reserved DHCP IP Address from the router. The GW1000 doesn't have a way to actually set a true static IP address on the device.

[admin]

when you provide me a remote login, I can have a closer look.

[galfert]

PM sent. I guess you don't save remote logins

[galfert]

Strange that the problem seems to have stopped without a Meteobridge reboot. Still running same version and log shows no issues in over 24 hours.

Platform: TL-MR3020 (no USB hub)
RAM: 29364 kB total, 1680 kB free (94% used)
SW Version: Meteobridge 4.2 (Nov 7 2019, build 13265), FW 1.4
Uptime: 6 days, 19 hours, 1 minutes Buffer: 1 items (0%)

Could it be that some online service was giving problems and causing this and now they are fixed?

My network router uptime is: 5 days 4 hours 20 minute(s) 55 seconds
I have it set to reboot automatically every Wednesday.

I've not had any network problems while this was occurring and as you can see the router is still on the same instance and hasn't been rebooted yet since the logger restart issue.

[admin]

Please trigger me, when problems show up again.

[galfert]

Looks like it started doing it again. Meteobridge still has not been rebooted and uptime is now 8 days. It only didn't show logger restarts on Nov 17th it seems. I don't think it is a coincidence that I rebooted my camera system on the 17th.

I think I have a suspicion on what it is causing the problem. I think it has to do with the weather camera image acquisition. This is something I noticed stopped working. I noticed that my camera's login is constantly showing "Account Locked" and I think people are trying to hack the camera and then on wrong password attempt it get locked for like 30 minutes. But 30 minutes later I think they continue attempt to hack its login and then it gets locked again. I think the Meteobridge is failing to acquire the image and then causing the problems for the logger needing to restart. Perhaps there is nothing you can do as the problem is originating at the camera not letting the Meteobridge log in. I can't log into the camera from a computer either unless I power cycle the camera. There must be some new exploit. I've had my camera with firewall port forwarded to allow me to remotely log in and it has never been an issue. This is something new I'm having to deal with my camera system. I think I'll have to set up a VPN or something and close the camera system port forwarding for remote access to cameras.

Unless......the Meteobridge has started polling the camera system too often or in a wrong way and then the camera system is locking the account out. Meaning that something the Meteobridge is doing differently is causing the lockout on the camera system. It would be nice to be able to change the frequency that the camera is polled for an image by the Meteobridge. I don't see that as an option on the Meteobridge, unless the Meteobridge goes by the Weather Network tab and whatever services and frequency is set there for camera upload to WU and Meteobridge.com.

From the Weather Station tab I see this message:
System Message

Code: Select all

Error: Camera URL not providing data: https://admin:<mypassword>@192.168.1.220/cgi-bin/snapshot.cgi?channel=8&loginuse=admin&loginpas=admin

Platform: TL-MR3020 (no USB hub)
RAM: 29364 kB total, 1900 kB free (93% used)
SW Version: Meteobridge 4.2 (Nov 7 2019, build 13265), FW 1.4
Uptime: 8 days, 4 hours, 35 minutes Buffer: 1 items (0%)

Additional log messages since last time:
logger (18.11.2019 07:29:05): child process received termination signal (15).
logger (18.11.2019 07:29:05): disconnect station 0 (GW1000): exit
logger (18.11.2019 07:29:05): parent process received termination signal (15).
logger (18.11.2019 07:29:08): data logger stopped.
test5m (18.11.2019 12:31:14): logger stalled, will be restarted now.
system (18.11.2019 12:31:14): stop of logging process initiated.
system (18.11.2019 12:31:14): start of logging process initiated.
logger (18.11.2019 07:31:15): historical data loaded (29 records).
logger (18.11.2019 07:31:15): data logger (version 5.1b, build 13265) started.
logger (18.11.2019 07:31:16): connect station 0 (GW1000 via TCP/IP).
logger (18.11.2019 07:31:19): sensors are now providing data.
logger (18.11.2019 07:31:19): services started.
logger (18.11.2019 09:51:41): child process received termination signal (15).
logger (18.11.2019 09:51:41): parent process received termination signal (15).
logger (18.11.2019 09:51:41): disconnect station 0 (GW1000): exit
logger (18.11.2019 09:51:45): data logger stopped.
test5m (18.11.2019 14:55:17): logger stalled, will be restarted now.
system (18.11.2019 14:55:17): stop of logging process initiated.
system (18.11.2019 14:55:17): start of logging process initiated.
logger (18.11.2019 09:55:18): historical data loaded (29 records).
logger (18.11.2019 09:55:18): data logger (version 5.1b, build 13265) started.
logger (18.11.2019 09:55:19): connect station 0 (GW1000 via TCP/IP).
logger (18.11.2019 09:55:23): sensors are now providing data.
logger (18.11.2019 09:55:23): services started.
logger (18.11.2019 10:15:34): child process received termination signal (15).
logger (18.11.2019 10:15:34): parent process received termination signal (15).
logger (18.11.2019 10:15:34): disconnect station 0 (GW1000): exit
logger (18.11.2019 10:15:38): data logger stopped.
test5m (18.11.2019 15:16:02): logger stalled, will be restarted now.
system (18.11.2019 15:16:03): stop of logging process initiated.
system (18.11.2019 15:16:03): start of logging process initiated.
logger (18.11.2019 10:16:03): historical data loaded (29 records).
logger (18.11.2019 10:16:03): data logger (version 5.1b, build 13265) started.
logger (18.11.2019 10:16:04): connect station 0 (GW1000 via TCP/IP).
logger (18.11.2019 10:16:08): sensors are now providing data.
logger (18.11.2019 10:16:08): services started.
logger (19.11.2019 11:38:57): child process received termination signal (15).
logger (19.11.2019 11:38:57): parent process received termination signal (15).
logger (19.11.2019 11:38:57): disconnect station 0 (GW1000): exit
logger (19.11.2019 11:39:06): data logger stopped.
test5m (19.11.2019 16:41:18): logger stalled, will be restarted now.
system (19.11.2019 16:41:18): stop of logging process initiated.
system (19.11.2019 16:41:18): start of logging process initiated.
logger (19.11.2019 11:41:19): historical data loaded (29 records).
logger (19.11.2019 11:41:19): data logger (version 5.1b, build 13265) started.
logger (19.11.2019 11:41:20): connect station 0 (GW1000 via TCP/IP).
logger (19.11.2019 11:41:23): sensors are now providing data.
logger (19.11.2019 11:41:23): services started.
logger (19.11.2019 11:51:32): child process received termination signal (15).
logger (19.11.2019 11:51:33): parent process received termination signal (15).
logger (19.11.2019 11:51:33): disconnect station 0 (GW1000): exit
logger (19.11.2019 11:51:37): data logger stopped.
test5m (19.11.2019 16:56:10): logger stalled, will be restarted now.
system (19.11.2019 16:56:10): stop of logging process initiated.
system (19.11.2019 16:56:10): start of logging process initiated.
logger (19.11.2019 11:56:11): historical data loaded (29 records).
logger (19.11.2019 11:56:11): data logger (version 5.1b, build 13265) started.
logger (19.11.2019 11:56:12): connect station 0 (GW1000 via TCP/IP).
logger (19.11.2019 11:56:15): sensors are now providing data.
logger (19.11.2019 11:56:15): services started.