Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pi-hole ftl is dying #48

Closed
3 tasks done
Bernd-Osterhage opened this issue May 13, 2017 · 3 comments
Closed
3 tasks done

pi-hole ftl is dying #48

Bernd-Osterhage opened this issue May 13, 2017 · 3 comments

Comments

@Bernd-Osterhage
Copy link

In raising this issue, I confirm the following (please check boxes, eg [X]) Failure to fill the template will close your issue:

  • I have read and understood the contributors guide.
  • The issue I am reporting can be replicated
  • The issue I am reporting isn't a duplicate

How familiar are you with the codebase?:

1

[BUG | ISSUE] Expected Behaviour:
ftl runs forever

[BUG | ISSUE] Actual Behaviour:
ftl is dying

[BUG | ISSUE] Steps to reproduce:
run pi-hole for a long time.
web interface shows ftl not running.

output from debug:

a lot of:
[New Thread 0x7ffff57e8700 (LWP 25440)]
[Thread 0x7ffff57e8700 (LWP 25440) exited]

and then:

Thread 48123 "client-4" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffff4fe7700 (LWP 11257)]
strlen () at ../sysdeps/x86_64/strlen.S:106
106 ../sysdeps/x86_64/strlen.S: Datei oder Verzeichnis nicht gefunden.

Device specifics

Hardware Type: rPi, VPS, etc
OS:
linux debian stretch

This template was created based on the work of udemy-dl.

@DL6ER
Copy link
Member

DL6ER commented May 13, 2017

Do you use the latest version of FTL? We released an update only yesterday.

If you use the latest version, please provide a backtrace as described here:
https://github.com/pi-hole/FTL#simplified-debugging-instructions-when-ftl-is-running

@Bernd-Osterhage
Copy link
Author

The last release runs by now for 24 hours. Looks very good. I will let it run further in debugging mode.
Thanks for the immediate answer.

@DL6ER
Copy link
Member

DL6ER commented May 15, 2017

Okay, we pushed a number of small code improvements over the last few days, hoping to harden the code. The most recent version is v2.7.3 by now.

Feel free to re-open this issue or open a new one if you need further assistance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants