Does Pi-hole self-reboot?

General
1

Ok, this is an odd question indeed.

I have a raspberry which run many services, including pi-hole. I've using it for a long, long time now. However, from time to time, my board just reboot.

At first I thought it was a power failure -> Changed the power source.
Afterwards, I start monitoring raspberry voltage -> Everything is ok.

I had this problem with ipv6 during two week, when I completely remove pi-hole. For my surprise, I got an uptime of 10 days.

I fixed the ipv6 problem, installed again, and there is a command for reboot.

Here is a piece of my syslog.
A first look points that everything start after:

/usr/local/bin/" pihole updatechecker local

Jul  2 19:22:43 rasp autossh[575]: timeout polling to accept read connection
Jul  2 19:22:43 rasp autossh[575]: port down, restarting ssh
Jul  2 19:22:43 rasp autossh[575]: starting ssh (count 1591)
Jul  2 19:22:43 rasp autossh[575]: ssh child pid is 11494
Jul  2 19:30:01 rasp CRON[14226]: (root) CMD (   PATH="$PATH:/usr/local/bin/" pihole updatechecker local)
Jul  2 19:30:46 rasp kernel: [969756.276119] Under-voltage detected! (0x00050005)
Jul  2 19:30:52 rasp kernel: [969762.516485] Voltage normalised (0x00000000)
Jul  2 19:32:40 rasp Node-RED[390]: 2 Jul 19:32:40 - [info] Stopping flows
Jul  2 19:32:40 rasp Node-RED[390]: 2 Jul 19:32:40 - [info] [mosca in:34c6e453.df2874] Unbinding mosca mqtt server from port: 1883
Jul  2 19:32:40 rasp Node-RED[390]: 2 Jul 19:32:40 - [info] serial port /dev/ttyACM0 closed
Jul  2 19:32:40 rasp Node-RED[390]: 2 Jul 19:32:40 - [info] [mqtt-broker:e1cd78d4.ca2998] Disconnected from broker: mqtt://localhost:1883
Jul  2 19:32:40 rasp Node-RED[390]: 2 Jul 19:32:40 - [info] serial port /dev/ttyUSB0 closed
Jul  2 19:32:43 rasp Node-RED[390]: 2 Jul 19:32:43 - [info] Stopped flows
Jul  2 19:32:43 rasp Node-RED[390]: 2 Jul 19:32:43 - [info] Starting flows
Jul  2 19:32:43 rasp Node-RED[390]: #033[32mTelegram Bot AiuroLarBot will be launched, environment is development#033[39m
Jul  2 19:32:43 rasp Node-RED[390]: #033[33mNo context provider specified for chatbot AiuroLarBot. Defaulting to "memory"#033[39m
Jul  2 19:32:45 rasp Node-RED[390]: 2 Jul 19:32:45 - [info] [python3-function:cbc944ac.a0e01] Python function '' running on PID 15240
Jul  2 19:32:45 rasp Node-RED[390]: 2 Jul 19:32:45 - [info] [mosca in:34c6e453.df2874] Binding mosca mqtt server on port: 1883
Jul  2 19:32:51 rasp Node-RED[390]: 2 Jul 19:32:51 - [info] Started flows
Jul  2 19:32:51 rasp Node-RED[390]: 2 Jul 19:32:51 - [error] serial port /dev/ttyACM0 error: Error: Error: No such file or directory, cannot open /dev/ttyACM0
Jul  2 19:32:51 rasp Node-RED[390]: 2 Jul 19:32:51 - [info] serial port /dev/ttyUSB0 opened at 9600 baud 8N1
Jul  2 19:32:52 rasp Node-RED[390]: 2 Jul 19:32:52 - [info] [mqtt-broker:e1cd78d4.ca2998] Connection failed to broker: mqtt://localhost:1883
Jul  2 19:32:55 rasp Node-RED[390]: 2 Jul 19:32:55 - [warn] [csv:ab4a3531.7f1e38] No columns template specified for object -> CSV.
Jul  2 19:32:58 rasp autossh[575]: timeout polling to accept read connection
Jul  2 19:32:58 rasp autossh[575]: port down, restarting ssh
Jul  2 19:32:58 rasp autossh[575]: starting ssh (count 1592)
Jul  2 19:32:58 rasp autossh[575]: ssh child pid is 15284
Jul  2 19:33:07 rasp Node-RED[390]: 2 Jul 19:33:07 - [info] [mqtt-broker:e1cd78d4.ca2998] Connected to broker: mqtt://localhost:1883
Jul  2 19:33:31 rasp systemd[1]: Started Session c33 of user thales.
Jul  2 19:34:08 rasp minissdpd[570]: device not found for removing : uuid:NFANDROID2-PRV-XIAOMIM12TRIAL-XIAOMMIBOX3-6728-FE23EBEE5C7120AEE92BDE4A046EF979DE70E9635AFC46415B6FEAB402D65818::upnp:rootdevice
Jul  2 19:34:08 rasp minissdpd[570]: device not found for removing : uuid:NFANDROID2-PRV-XIAOMIM12TRIAL-XIAOMMIBOX3-6728-FE23EBEE5C7120AEE92BDE4A046EF979DE70E9635AFC46415B6FEAB402D65818
Jul  2 19:34:08 rasp minissdpd[570]: device not found for removing : uuid:NFANDROID2-PRV-XIAOMIM12TRIAL-XIAOMMIBOX3-6728-FE23EBEE5C7120AEE92BDE4A046EF979DE70E9635AFC46415B6FEAB402D65818::urn:schemas-upnp-org:device:mdxdevice:1
Jul  2 19:34:08 rasp minissdpd[570]: device not found for removing : uuid:NFANDROID2-PRV-XIAOMIM12TRIAL-XIAOMMIBOX3-6728-FE23EBEE5C7120AEE92BDE4A046EF979DE70E9635AFC46415B6FEAB402D65818::urn:mdx-netflix-com:service:target:3
Jul  2 19:34:08 rasp minissdpd[570]: device not found for removing : uuid:NFANDROID2-PRV-XIAOMIM12TRIAL-XIAOMMIBOX3-6728-FE23EBEE5C7120AEE92BDE4A046EF979DE70E9635AFC46415B6FEAB402D65818::upnp:rootdevice
Jul  2 19:34:08 rasp minissdpd[570]: device not found for removing : uuid:NFANDROID2-PRV-XIAOMIM12TRIAL-XIAOMMIBOX3-6728-FE23EBEE5C7120AEE92BDE4A046EF979DE70E9635AFC46415B6FEAB402D65818
Jul  2 19:34:08 rasp minissdpd[570]: device not found for removing : uuid:NFANDROID2-PRV-XIAOMIM12TRIAL-XIAOMMIBOX3-6728-FE23EBEE5C7120AEE92BDE4A046EF979DE70E9635AFC46415B6FEAB402D65818::urn:schemas-upnp-org:device:mdxdevice:1
Jul  2 19:34:08 rasp minissdpd[570]: device not found for removing : uuid:NFANDROID2-PRV-XIAOMIM12TRIAL-XIAOMMIBOX3-6728-FE23EBEE5C7120AEE92BDE4A046EF979DE70E9635AFC46415B6FEAB402D65818::urn:mdx-netflix-com:service:target:3
Jul  2 19:34:16 rasp systemd[1]: Closed Load/Save RF Kill Switch Status /dev/rfkill Watch.
Jul  2 19:34:16 rasp systemd[1]: Stopped target RPC Port Mapper.
Jul  2 19:34:16 rasp systemd[1]: session-c22.scope: Killing process 31714 (pihole-FTL) with signal SIGTERM.
Jul  2 19:34:16 rasp systemd[1]: Stopping Session c22 of user pihole.
Jul  2 19:34:16 rasp systemd[1]: Stopped target Bluetooth.
Jul  2 19:34:16 rasp systemd[1]: Stopping Session c33 of user thales.
Jul  2 19:34:16 rasp systemd[1]: Stopped target Sound Card.
Jul  2 19:34:16 rasp systemd[1]: Stopping User Manager for UID 999...
Jul  2 19:34:16 rasp systemd[1]: session-c19.scope: Killing process 27625 (ipUpdate.pl) with signal SIGTERM.
Jul  2 19:34:16 rasp systemd[1]: Stopping Session c19 of user thales.
Jul  2 19:34:16 rasp systemd[1]: Stopping Save/Restore Sound Card State...
Jul  2 19:34:16 rasp systemd[1]: Stopped target Timers.
Jul  2 19:34:16 rasp systemd[1]: Stopped Daily apt upgrade and clean activities.
Jul  2 19:34:16 rasp systemd[1]: Stopped Daily apt download activities.
Jul  2 19:34:16 rasp systemd[1]: Stopped target Graphical Interface.
Jul  2 19:34:16 rasp systemd[1]: Stopped target Multi-User System.
Jul  2 19:34:16 rasp systemd[1]: Stopping triggerhappy global hotkey daemon...
Jul  2 19:34:16 rasp systemd[1]: Stopping Regular background program processing daemon...
Jul  2 19:34:16 rasp systemd[1]: Stopping LSB: pihole-FTL daemon...
Jul  2 19:34:16 rasp systemd[1]: Stopping Avahi mDNS/DNS-SD Stack...
Jul  2 19:34:16 rasp Node-RED[390]: 2 Jul 19:34:16 - [info] Stopping flows
Jul  2 19:34:16 rasp systemd[1]: Stopping uptime record daemon...
Jul  2 19:34:16 rasp systemd[1]: Stopping keep memory of all UPnP devices that announced themselves...
Jul  2 19:34:16 rasp systemd[1]: Stopping Node-RED graphical event wiring tool...
Jul  2 19:34:16 rasp systemd[1]: Stopping Configure Bluetooth Modems connected by UART...
2

That's a power supply issue.

That's the start of a graceful shutdown. Either the system is seeing a problem and shutting down (thermal issue, power issue) or something is calling for a shutdown of the system.

3

Pi-hole does not restart itself nor reboot the host OS.

4

I've been trying to find the source of this problem, but I can't find a clear reason for that. It's receiving, somehow, a shutdown signal.

Following your tip @DanSchaper, here is the thermal profile.

image
image925×422 40.1 KB

CPU load also has a spike, but nothing relevant.

image
image908×413 81.8 KB

And here is the memory. Time is wrong, but the event is correct.

image
image929×412 42.1 KB

It seams that pihole updatechecker trigger that.

This is my AndroidTV box. is this process minissdpd related to pihole. If so, things start to make sense.

My theory is that there is some memory allocations that are not getting clear. RAM overflow, temperature rise and it reboot.

5

Having to run autossh and seeing it frequently need to restart should also point you to system problems.