Multi Station: data logger restarts on connectivity problems. **solved**

[thunderstorm]

This night my AirLink was powered off (forgot to reconfigure the outdoor power-outlet) which resulted in a series of continuous restarts of the data logger. Since such connectivity problems to a specific device are kind of common, I wondering whether it could be a problem to restart the logger for all stations over and over again.

Or would it be feasible to only restart the affected station ?

Thanks
Bernd

Code: Select all

logger (25.09.2020 05:15:49): station 2 (AirLink), no synchronization for 900 seconds, data logger will be restarted.
logger (25.09.2020 05:15:49): disconnect station 0 (Vantage): exit
logger (25.09.2020 05:15:49): disconnect station 1 (User-defined): exit
logger (25.09.2020 05:15:49): disconnect station 2 (AirLink): exit
logger (25.09.2020 05:15:49): disconnect station 9 (System Data): exit
logger (25.09.2020 05:15:50): data logger stopped.
logger (25.09.2020 05:15:50): databases disconnected.
logger (25.09.2020 05:15:50): parent process to be terminated.
logger (25.09.2020 05:15:50): databases connected. Update interval 3600 seconds.
logger (25.09.2020 05:15:50): data logger (version 5.1d, build 3369) started.
logger (25.09.2020 05:15:51): connect station 0 (Vantage via USB serial).
logger (25.09.2020 05:15:51): connect station 1 (User-defined via Plug-in).
logger (25.09.2020 05:15:51): connect station 2 (AirLink via SW Driver).
logger (25.09.2020 05:15:51): connect station 9 (System Data via Plug-in).
logger (25.09.2020 05:15:51): station 0 (Vantage), wakeup sent.
logger (25.09.2020 05:15:52): waiting for sensors (wind0, rain0, th0, thb0) to provide data.
logger (25.09.2020 05:15:52): services paused.
logger (25.09.2020 05:15:54): station 0 (Vantage), no need to update console date/time.
logger (25.09.2020 05:15:54): station 0 (Vantage), setup script executed.
logger (25.09.2020 05:15:55): station 0 (Vantage), internal logger activated.
logger (25.09.2020 05:15:55): station 0 (Vantage), syncing.
logger (25.09.2020 05:16:05): station 0 (Vantage), gettime request sent.
logger (25.09.2020 05:16:05): station 0 (Vantage), no Vantage time offset.
logger (25.09.2020 05:16:05): station 0 (Vantage), eeprom request sent.
logger (25.09.2020 05:16:05): station 0 (Vantage), rain collector size 0.01 inch per tick.
logger (25.09.2020 05:16:05): station 0 (Vantage), transmitter 1 active as station type #0 "ISS".
logger (25.09.2020 05:16:05): station 0 (Vantage), firmware version request sent.
logger (25.09.2020 05:16:05): station 0 (Vantage), firmware version 3.15 (supports LOOP2)
logger (25.09.2020 05:16:05): station 0 (Vantage), no reading of Vantage's internal logger.
logger (25.09.2020 05:16:09): sensors are now providing data.
logger (25.09.2020 05:16:09): services started.
logger (25.09.2020 05:30:50): station 2 (AirLink), no synchronization for 900 seconds, data logger will be restarted.

[admin]

There are some kinds of stations that need a complete un-powering of the USB ports to get back to live after a hang-up. This is the reason, why Meteobridge stops logging completely after having tried to restart connection to a certain device a few times without results.

[admin]

Newest release will have a switch where you can decide per station if a lacking of data should initiate a restart of the logger.

Meteobridge does anyway react on a connection break down to a certain station. When you use a user-defined plugin to deliver data, then terminating this plugin will force Meteobridge to start it again. Connections to other stations should not be impacted. Therefore, I recommend to have your scripts working in a way, that they terminate in case no data coming in from sensors for a certain time. Meteobridge will then restart this process again.

[thunderstorm]

Thanks and I just was curious why meteobridge is restarting the whole datalogger, not at all non-coolness of the logs (although it felt a bit spammy).
And I haven't experienced any issues with the complete restart.

[admin]

Next update will have the restart behaviour ("restart just impacted station" vs "restart all stations") selectable for every station.