Can anyone explain what is happening here?

[BrandonBarometer]

Hello,
Getting the following about a few hours before my meteobridge pro red crashes and stops sending data, any clues people?

oled (17.09.2019 06:19:26): process started.
database (17.09.2019 07:21:09): process started.
database (17.09.2019 07:21:09): Content of RAM database restored.
wnetd (17.09.2019 07:21:12): process started.
system (17.09.2019 07:21:12): start of logging process initiated.
logger (17.09.2019 07:21:12): databases connected. Update interval 3600 seconds.
logger (17.09.2019 07:21:12): data logger (version 5.1b, build 13143) started.
logger (17.09.2019 07:21:14): connect station 0 (Meteostick Vantage via USB serial).
logger (17.09.2019 07:21:14): connect station 9 (System Data via Plug-in).
logger (17.09.2019 07:21:16): transmitter 1 registered as ISS
logger (17.09.2019 07:21:16): Meteostick Version 2.5.2
logger (17.09.2019 07:21:16): debug off
logger (17.09.2019 07:21:16): verbose off
logger (17.09.2019 07:21:16): output raw (8 bytes)
logger (17.09.2019 07:21:16): output raw (10 bytes)
logger (17.09.2019 07:21:16): filter on
logger (17.09.2019 07:21:16): rx threshold set to -90db
logger (17.09.2019 07:21:16): listening to transmitter 1
logger (17.09.2019 07:21:16): bandwidth normal
logger (17.09.2019 07:21:16): chip authentication ok: 14
logger (17.09.2019 07:21:16): frequency band 868MHz (EU)
logger (17.09.2019 07:21:17): waiting for sensors (wind0, rain0, th0, thb0) to provide data.
logger (17.09.2019 07:21:17): services paused.
database (17.09.2019 07:21:36): database sync done (40 tables, 121/1720 writes).
logger (17.09.2019 07:23:14): give up waiting for sensors after 120 secs.
logger (17.09.2019 07:23:14): services activated.
wnetd (17.09.2019 12:11:37): process received signal (11) and terminated: sendloop_LOOP_C < sendloop_LOOP_B < sendloop_LOOP_A < wnet_handle* < appendlog < wnet_handle <
logger (17.09.2019 12:12:06): open named pipe "/dev/meteobridge" failed: No such device or address
logger (17.09.2019 12:16:14): message above repeats 15 times.
test5m (17.09.2019 11:16:34): weathernet daemon stalled, will be restarted now.
wnetd (17.09.2019 12:16:34): process started.

[admin]

There was a "segmentation violation" error that crashes the process which sends out data to weather networks, etc.
No idea why, but Meteobridge recovers from that automatically as you can see in the log.

[Lespius]

I think I had the same experience. I had the same kind of message:

oled (26.12.2019 16:49:05): process started.
test5m (26.12.2019 16:50:52): weathernet daemon stalled, will be restarted now.
wnetd (26.12.2019 17:50:52): process started.
test5m (26.12.2019 16:50:52): logger stalled, will be restarted now.
system (26.12.2019 16:50:53): stop of logging process initiated.
database (26.12.2019 17:50:59): process started.

It lasted from 1 am this morning until I rebooted the meteohub at 17h50. So the data logger didn't restart successfully for the whole day.
During the time the logger was out of service, of course no data were sent to the several weathernetworks, and no data were recorded by meteohub.
Any idea ?