MB Nano SD restart every hour (also with build 3440)

[xray77]

Hello Boris,
With the newest version of Meteobridge firmware (MB NANO SD) a reboot is triggered every hour, is this intended? I never noticed that with earlier versions.
SW-Version: Meteobridge 4.4 (Oct 2 2020, build 3436), FW 1.4

logger (03.10.2020 13:00:28): child process received termination signal (11) in functions: termination_handler < find_persist < get_special_byname < get_special_byname_map < find_persist < get_persist_byname < get_persist_byname_map < find_persist < get_special_byname < get_special_byname_map < find_persist < get_persist_byname < get_persist_byname_map < find_persist < get_special_byname...

This log-entry repeated every full hour.
regards
Mike

[jasonmfarrow]

I'm on the same level of firmware. No reboots since the update at 15:40 yesterday.

[xray77]

Hello Jason,
have rebooted the device and the firmware is lifted to a new build: Meteobridge 4.4 (Oct 3 2020, build 3440), FW 1.4, will watch it and see if the reboot reappears..
Thanks for your advice,
regards
Mike

Edit: the reboots every full hour persist's..
logger (03.10.2020 16:00:42): child process received termination signal (11) in functions: termination_handler < find_persist < get_special_byname < get_special_byname_map < find_persist < get_persist_byname < get_persist_byname_map < find_persist < get_special_byname < get_special_byname_map < find_persist < get_persist_byname < get_persist_byname_map < find_persist < get_special_byname... [.....]

logger (03.10.2020 17:00:28): child process received termination signal (11) in functions: termination_handler < find_persist < get_special_byname < get_special_byname_map < find_persist < get_persist_byname < get_persist_byname_map < find_persist < get_special_byname < get_special_byname_map < find_persist < get_persist_byname < get_persist_byname_map < find_persist < get_special_byname...
logger (03.10.2020 17:00:28): disconnect station 0 (Vantage): exit
logger (03.10.2020 17:00:28): disconnect station 9 (System Data): exit
logger (03.10.2020 17:00:29): data logger stopped.
logger (03.10.2020 17:00:29): databases disconnected.
logger (03.10.2020 17:00:29): parent process to be terminated.
logger (03.10.2020 17:00:29): databases connected. Update interval 3600 seconds.
logger (03.10.2020 17:00:29): data logger (version 5.1d, build 3440) started.
logger (03.10.2020 17:00:29): connect station 0 (Vantage via serial).
logger (03.10.2020 17:00:29): connect station 9 (System Data via Plug-in).
logger (03.10.2020 17:00:30): station 0 (Vantage), wakeup sent.
logger (03.10.2020 17:00:33): waiting for sensors (wind0, rain0, th0, thb0) to provide data.
logger (03.10.2020 17:00:33): services paused.
logger (03.10.2020 17:00:33): station 0 (Vantage), no need to update console date/time.
logger (03.10.2020 17:00:34): station 0 (Vantage), setup script executed.
logger (03.10.2020 17:00:35): station 0 (Vantage), internal logger activated.
logger (03.10.2020 17:00:35): station 0 (Vantage), syncing.
logger (03.10.2020 17:00:46): station 0 (Vantage), gettime request sent.
logger (03.10.2020 17:00:46): station 0 (Vantage), no Vantage time offset.
logger (03.10.2020 17:00:46): station 0 (Vantage), eeprom request sent.
logger (03.10.2020 17:00:46): station 0 (Vantage), rain collector size 0.2 mm per tick.
logger (03.10.2020 17:00:46): station 0 (Vantage), transmitter 1 active as station type #0 "ISS".
logger (03.10.2020 17:00:46): station 0 (Vantage), transmitter 8 active as station type #7 "Soil".
logger (03.10.2020 17:00:46): station 0 (Vantage), firmware version request sent.
logger (03.10.2020 17:00:46): station 0 (Vantage), firmware version 3.80 (supports LOOP2)
logger (03.10.2020 17:00:46): station 0 (Vantage), no reading of Vantage's internal logger.
logger (03.10.2020 17:00:50): sensors are now providing data.
logger (03.10.2020 17:00:50): services started.



but i see nothing what would go wrong about this... Only my second ID (Soil-station) tooks some more time to recognize by the MB, it seems so..

[xray77]

..in the last two hours no restart triggered...
Maybe the restarts were only a temporary problem, i don't know.
regards
Mike

[jasonmfarrow]

One for Boris as only he would know the code that triggers those specific messages.

[admin]

There are no reboot triggers. Signal 11 is a segfault error, but this only causes a restart of the logger process "loggerd".

When you still see this signal 11 in the logs of the loggerd process, please provide me a remote login.
As it works fine on my NANOs, I currently cannot reproduce this here.

[xray77]

Good Morning Boris,
Thanks for your explanation,
Since yesterday, 18:00 no more signal 11 occured in the log. It seems so, the NANO SD has healed itself.. If it appears again, I will contact you here again.
best regards
Mike

[xray77]

Hello Boris,
The logger-termination Signal (11) is back after the automatic reboot (i let reboot the MB every 48 hr's):

logger (05.10.2020 21:01:08): child process received termination signal (11) in functions: termination_handler < find_persist < get_persist_byname < get_persist_byname_map < find_persist < get_persist_byname < get_persist_byname_map < find_persist < get_persist_byname < get_persist_byname_map < find_persist < get_persist_byname < get_persist_byname_map < find_persist < get_persist_byname...

logger (05.10.2020 22:00:28): child process received termination signal (11) in functions: termination_handler < find_persist < get_special_byname < get_special_byname_map < find_persist < get_persist_byname < get_persist_byname_map < find_persist < get_special_byname < get_special_byname_map < find_persist < get_persist_byname < get_persist_byname_map < find_persist < get_special_byname...
It appears every hour since reboot.


Another problem that might be related to this: my ground temperature station (station ID 8 -> Soil station) keeps now loosing contact often to the console where is MeteoBridge connected to. A second console, which is only a short distance away from the MB console, does not lose contact.

Will send you the remote login per PM and appreciate your time to look on it.

[admin]

I made some changes in the affected function. Please reboot and give it a try.

[xray77]

Boris,
this update don't run at my MB, all services send only empty templates an the graphics-function an MB don't work anymore... have sent you PM.. After a downgrade to Version 4.3 from July 2020, all services run's again..
regards
Mike

[admin]

should be fine again.

[xray77]

Hello Boris
Thanks, I installed the fixed update last night and read your statements. The logger-restart-issue is gone, I'm not sure if this is due to the update or my reduced services in the MB. ☺ So i think this thread can be marked as solved.

It was a wonderful idea to take it easy and put the many features on a stable basis. The MB can do almost everything by now, the only thing I would still need is a sunshine duration evaluation I know that the MB can do this, all necessary variables are already available. But to get into calmer waters first is the best idea. Thanks for your tireless work,
Best regards, Michael