I'm running a simple weather monitor (just temperature) on a Raspbeery Pi 3B (Raspbian Linux 4.14.98-v7+). It has a 3G modem that sends out simple packets to my server at home.
On june 5th I lost remote access to the device. Since it is located somewhere difficult to physically access, I couldn't manually reboot it.
To my surprise, on June 10th it got back to life. It has not registered a reboot! Here's the weird excerpt from the log at /var/log/messages:
Jun 5 17:54:28 raspberrypi NetworkManager[345]: <info> [1559768068.0169] policy: set 'VIVO ZAP' (wwan0) as default for IPv4 routing and DNS
Jun 5 17:54:28 raspberrypi NetworkManager[345]: <info> [1559768068.0174] dns-mgr: Writing DNS information to /sbin/resolvconf
Jun 5 17:54:28 raspberrypi NetworkManager[345]: <info> [1559768068.1295] device (ttyUSB2): Activation: successful, device activated.
Jun 10 23:14:33 raspberrypi NetworkManager[345]: <info> [1560219273.9397] (mon0): using nl80211 for WiFi device control
Jun 10 23:14:33 raspberrypi NetworkManager[345]: <info> [1560219273.9622] devices added (path: /sys/devices/platform/soc/3f300000.mmc/mmc_host/mmc1/mmc1:0001/mmc1:0001:1/net/mon0, iface: mon0)
Jun 10 23:14:33 raspberrypi NetworkManager[345]: <info> [1560219273.9623] device added (path: /sys/devices/platform/soc/3f300000.mmc/mmc_host/mmc1/mmc1:0001/mmc1:0001:1/net/mon0, iface: mon0): no ifupdown configuration found.
It's as if the operating system froze for some reason and suddenly got back working 5 days later! Absolutely no reboot registered.
It's practically impossible to know what happened without being there. It's possible it froze. Usually when things freeze we reboot, but maybe leaving a computer alone for 5 days does the trick also, impossible to tell without having seen what happened.
Maybe the network cut off, or the programming glitched out.