Strange issue #17
Comments
|
This log is quite odd, e.g. Can you run |
|
unfortunately the following didnt work at all: FTL has been designed such that a debugger can be attached to an already running process to ease debugging. Use sudo gdb -p $(cat /var/run/pihole-FTL.pid) to attach to the already running pihole-FTL process. You can leave off sudo if you are running pihole-FTL with the current user. Once loading of the symbols has finished (the (gdb) input prompt is shown), run continue to continue operation of pihole-FTL inside the debugger. All debugger features are now available. When you want to detach the debugger from FTL without terminating the process, you can hit Ctrl+C and enter detach followed by quit what is working is the following: [2017-04-11 00:07:26.199] ########## FTL started! ########## I'm confused as the FTL service isnt starting anymore... sudo service pihole-FTL status and syslog is repeately complaining about: tail -f /var/log/syslog any hints? //edit: reboot solved FTL start but how should I continue as the debug does not seem to work? Thanks! |
|
What was causing the normal debug steps to not work? |
|
these steps should work to get you to the correct debug
|
|
Oh yes... The simplified debugging does not work when FTL crashes during or shortly after startup. Use the instructions @technicalpyro posted instead. There is a catch in They are now also included in the official |
|
/edited @DL6ER @technicalpyro thanks for sharing some pretty useful knowledge :) @DL6ER unfortunately restart didnt change a thing :/ |
|
@DL6ER taught it to me so i cannot take any credit |
|
finally it happened again: `[New Thread 0xb5b7a460 (LWP 28133)] a^[[2017-04-13 09:59:00.076] Running GC on data structure [2017-04-13 11:59:00.009] Running GC on data structure [2017-04-13 14:59:00.085] Running GC on data structure Program received signal SIGSEGV, Segmentation fault.
|
|
Okay, so this is still strange. Please try again with What operating system on which device are you running? |
|
ok, I'll update FTL and update this thread if it happens again Linux 4.4.50+ #970 Mon Feb 20 19:12:50 GMT 2017 armv6l GNU/Linux Could it have something to do that I've disabled swapping completely? //Edit: while upgradeing I get this at the end systemctl status pihole-FTL.service |
|
you must exit the FTL process that is running in the debug in order to have the new one being used if you have then im not sure on that error |
|
sorry, my bad |
|
ok f it still isnt updating use then run the update also can use |
|
its already 2.2 - thanks |
|
Yeah, according to your output the update went fine, but only the restarting hasn't worked, because, as @technicalpyro said, there was still a running process inside the debugger (which cannot be terminated from the outside of the debugger). Hmm, still it is strange that your system shows things like
? Is there swapping enabled by default? I'd guess no because that would almost certainly kill any SD card in a short time frame |
thats the reason I have disabled it indeed it is definetely enabled by default ! I had to manually disable it and additionally mounted some folders including /var/log/ into ramfs right now the debug is spamming me with this but ftl is running fine atm |
|
Interesting, my Raspberry Pi model B is now 5 years old and still running with the same SD card from the first day on in almost uninterrupted 24/7 operation. It has also been used as the daily Pi-hole device for the internal network for about one year. Still, I have never seen a problem with either the device itself or the SD card. It is now replaced by the (much better) NanoPi NEO which seems to be really the ideal device for Pi-hole. I disabled swap now as well, but according to The "spamming" is fine - it shows you that there is activity going on. In your case, it is most likely that this corresponds to requests from the web interface. Try to close all web interface instances and they should go away (only new log events, but no periodic messages). |
|
Ive disabled it just to be save. I dont know how long it takes to kill a SD with standard OS swapping |
|
It is very small and cheap (less than $10) while having about the same performance data as the current Raspberry Pi version 3. Also, it comes w/o a graphics card which is something I have never needed once on my Raspberry Pi devices (I don't even have a HDMI capable device at home). |
|
wow thats neat - Im thinking of getting one as I dont need a gpu as well //edit: |
|
Yeah, I have just been able to confirm this locally after flushing took place. I think that all issues that have been reported are due to illegal struct resizing after flushing. At least this cures the error flood you have seen. If there are still more issues with the data structure, my sophisticated memory access validator (whose output you have seen above) should be able to identify them and warn in a similar manner. Anyhow, it should be fixed in |
|
looks like its fixed - never had an issue until now thanks for your quick help @DL6ER & @technicalpyro |
|
Closing since the issue has been resolved. @strrrn Feel free to re-open if you experience the same issue again. Please file a new issue report for other issues. |
|
I'm having the same issue running Pi-hole Version v3.0.1 Web Interface Version v3.0.1 FTL Version v2.6.2 on a VM [2017-05-07 00:00:01.745] Reading from /var/log/pihole.log (rw-r--r--) |
|
Thanks for reporting this! However, as this is almost certainly another issue, could I ask you to file a new bug report? You can then also already include some more details which you can obtain by going into debug mode (see here for detailed instructions) |
@strrrn wrote:
mine is crashing with the following:
any updates on this?
The text was updated successfully, but these errors were encountered: