FTL crash after clean install #2250
Labels
Comments
|
Can you please post some lines from above the !!!!!!!!! header from |
|
Sorry got an emergency. |
|
After reading this article I've stopped and disabled lighttpd for the moment (have to check if it was needed by some other service). Following the suggestion in #5948 I've also set |
|
I've got same isssue |
|
It would be extremely helpful if you could follow the steps on https://docs.pi-hole.net/ftldns/gdb/ and provide the |
|
I tried following the guide, but the command Do I need to restart, use the command and then try to add/delete a CNAME to make it crash? Edit: After some tests looks like there is problem with the |
|
@DL6ER I restarted the pi and with everything running I started the debugger and followed the guide. This is the output of This is the output of the Tell me if something else is needed. |
FTL/src/webserver/civetweb/civetweb.c Lines 20679 to 20684 in ac500d5 This comment somehow feels fishy here... If you can reproduce this (and the crash happens again at the same location), what is the output of ? |
|
I restarted and re-run all previous commands: Then output of |
|
Sorry for the delay in replying ... Could you please try if the issue is resolved by running ? |
|
Not solved. Output of |
|
Too bad, okay, let's dive deeper into this. I'm trying to see where Do you see log lines like in your |
|
This is the content of a clean The only reference to ports I can find is the port 53 (DNS?), nothing else. Two thing I did not specify before:
I did not report this before because the previous version of pihole was working fine with those settings. |
|
Ah, I did just spot in your log. This is about what I assumed:
just with the twist that it doesn't even try to bind anything. What is the output of ? |
|
|
|
Thank you. It seems the CivetWeb server crashes if all optional ports are already occupied, I did just report this upstream: civetweb/civetweb#1327 Please try if that fixes the issue for you. You should still set other ports so your Pi-hole can offer the API when there is already a webserver on the same host. |
|
|
You (or me) may have been too fast and the binary may have not been created. I did just check and everything is there now, please try again. |
5 tasks
|
Should I change something else? Switching branch did not solve the problem. This is the content of |
|
Please try again in ~ 5 minutes. I have a proposed fix which I will also send upstream to the CivetWeb project |
|
Ok, I'll restart it in 10 min to be sure. In the meanwhile, can you clarify what you meant by
What should I do? |
|
The
Please first if the crash is gone after running the |
|
@DL6ER which branch should I checkout? |
|
@DaitiDay Yes, exactly as before. |
|
I switched branch and launched After a reboot there seems to be no more crashes. I'll update tomorrow in case something happens, otherwise I'll close the issue if you agree @DL6ER |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Versions
Platform
Expected behavior
Can add/delete CNAME.
Actual behavior / bug
After the clean installation of the latest version of pihole, whenever I try to add/delete a CNAME, the FTL crashes.
Steps to reproduce
Steps to reproduce the behavior:
Debug Token
Additional context
During an update I got a DNS resolution problem related to a setting I did not change after a router reset. I quitted the update and got prompted to uninstall pihole and remove al unnecessary packages. I did that, and then reinstalled pihole following method 2 on the official site. Installation was fine, but I couldn't access the web interface, launching
pihole statusreported[✗] DNS service is NOT running, so I rebooted and everything was working.As soon as I added the first CNAME (which worked), every subsequent try I encoutered an error, and refreshing the page resulted in the same inaccessible web interface as before. Same output from
pihole status. Rebooting fixes the problem, but adding/deleting a CNAME results in FTL crash (checked in FTL.log).The text was updated successfully, but these errors were encountered: