DNS Resolution should not crash after 2-3 hours of normal operation
Actual Behaviour:
After 2-3 hours of normal operation I get the message from padd.sh that DNS is off and the webinterface is not responding anymore or very slow. Logging in via SSH always works. When I try to restart the DNS service I get the message
Job for pihole-FTL.service failed because the control process exited with error code.
thats awkward, I get Permission denied although I am logged in as root user. Sorry I am not that familiar with linux. Do I first need to permit myself?
Funny thing is I can cd into the directory.
EDIT: Opening it with nano worked. Please see the post below
Can you provide the corresponding log from /var/log/pihole.log?
The developers will ask you for more logs and steps to proceed when the had a look on this.
This looks like a genuine crash. You could try if the following command would result in some additional information (though I doubt it would be more detailed or verbose than what your log has provided already):
sudo systemctl status --full --no-pager pihole-FTL.service
I have alerted the developers, but it may take some time before they have the chance to take a look at it (different time zones and daytime jobs interfering).
You shouldn't have run the sudo ... line in the debugger ((gdb) prompt), however it should not have caused issues. We will find out when the crash happens and we either get or don't get meaningful data. Until then, we are eagerly expecting what will happen.
yea I noticed that too after entering the line
so meanwhile pihole crashed again but I don't see any output in the terminal.
As far as I understood the documentation I should see an output in the terminal, right?
Thats all I see. it is running since a few hours. Dunno when exactly the crash happened.
EDIT: When I "quit" it says "Debugging Session Active". Is the data being dumped to a file?
Hmm, so something went wrong. It may be that you had several forks of pihole-FTL running when attaching the debugger and, by chance, we picket the wrong one.
Next time, instead of
sudo gdb -p $(pidof pihole-FTL)
please use
sudo gdb -p 13813
where this 13813 is the number you get from the command
grep "PID of FTL process" /var/log/pihole-FTL.log | tail -n1 | sed "s/.*: //"
Sorry for that, however, it is not always as straightforward to debug a multi-parallel application (using threads and process-forks at the same time).
No, you terminated the debugging session by quitting.
just a little update. The last crash was this morning. Afterwards I rebooted and started the screening with gdb (thx DL6ER for your help). Funny thing is, since then it didn't crash. I will post the output of gdb once it crashes again.
ok it crashed a few minutes ago. but all I see is this:
[Thread 0x734ff460 (LWP 2701) exited]
[New Thread 0x734ff460 (LWP 2704)]
[Thread 0x734ff460 (LWP 2704) exited]
[Detaching after fork from child process 2765]
[Detaching after fork from child process 2766]
[Detaching after fork from child process 2767]
[Detaching after fork from child process 2768]
[Detaching after fork from child process 2769]
[Detaching after fork from child process 2770]
[Detaching after fork from child process 2771]
[Detaching after fork from child process 2772]
[Detaching after fork from child process 2773]
[Detaching after fork from child process 2774]
[Detaching after fork from child process 2775]
[Detaching after fork from child process 2776]
[Detaching after fork from child process 2777]
[Detaching after fork from child process 2778]
[Detaching after fork from child process 2779]
[Detaching after fork from child process 2780]
[Detaching after fork from child process 2781]
[Detaching after fork from child process 2782]
[Detaching after fork from child process 2783]
[Detaching after fork from child process 2784]
[Detaching after fork from child process 2785]
[Detaching after fork from child process 2786]
[Detaching after fork from child process 2787]
[Detaching after fork from child process 2788]
[Detaching after fork from child process 2789]
[Detaching after fork from child process 2790]
[Detaching after fork from child process 2791]
[Detaching after fork from child process 2792]
[Detaching after fork from child process 2800]
[New Thread 0x734ff460 (LWP 2826)]
[Thread 0x734ff460 (LWP 2826) exited]
[New Thread 0x734ff460 (LWP 2829)]
[Thread 0x734ff460 (LWP 2829) exited]
[New Thread 0x734ff460 (LWP 2860)]
[Thread 0x734ff460 (LWP 2860) exited]
[New Thread 0x734ff460 (LWP 2865)]
[Thread 0x734ff460 (LWP 2865) exited]
[New Thread 0x734ff460 (LWP 2870)]
[Thread 0x734ff460 (LWP 2870) exited]
[New Thread 0x734ff460 (LWP 2874)]
[Thread 0x734ff460 (LWP 2874) exited]
[Detaching after fork from child process 2941]
[New Thread 0x734ff460 (LWP 2966)]
[Thread 0x734ff460 (LWP 2966) exited]
[New Thread 0x734ff460 (LWP 2969)]
[Thread 0x734ff460 (LWP 2969) exited]
[New Thread 0x734ff460 (LWP 3000)]
[Thread 0x734ff460 (LWP 3000) exited]
[New Thread 0x734ff460 (LWP 3005)]
[Thread 0x734ff460 (LWP 3005) exited]
[New Thread 0x734ff460 (LWP 3010)]
[Thread 0x734ff460 (LWP 3010) exited]
[New Thread 0x734ff460 (LWP 3013)]
[Thread 0x734ff460 (LWP 3013) exited]
[Detaching after fork from child process 3079]
[New Thread 0x734ff460 (LWP 3104)]
[Thread 0x734ff460 (LWP 3104) exited]
[New Thread 0x734ff460 (LWP 3107)]
[Thread 0x734ff460 (LWP 3107) exited]
[New Thread 0x734ff460 (LWP 3138)]
[Thread 0x734ff460 (LWP 3138) exited]
[New Thread 0x734ff460 (LWP 3143)]
[Thread 0x734ff460 (LWP 3143) exited]
[New Thread 0x734ff460 (LWP 3148)]
[Thread 0x734ff460 (LWP 3148) exited]
[New Thread 0x734ff460 (LWP 3151)]
[Thread 0x734ff460 (LWP 3151) exited]
[Detaching after fork from child process 3217]
