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.

Sign up for GitHub

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

Jump to bottom

Ftl crash #2316

Open
luisenlag opened this issue Mar 1, 2025 · 6 comments
Open

Ftl crash #2316

luisenlag opened this issue Mar 1, 2025 · 6 comments
Labels
crash

Comments

@luisenlag
Copy link

Versions

  • Pi-hole:
  • AdminLTE:
  • FTL:

Platform

  • Platform: LXC Ubuntu 24.04 on proxmox 8.

Find the attached file with the crash info.

Pihole.txt.txt
@streamdp
Copy link

streamdp commented Mar 2, 2025

I have the same issue, today.

Versions

  • Core: v6.0.4
  • Web: v6.0.1
  • FTL: v6.0.3

Platform

  • Platform: Ubuntu 22.04.5 LTS (GNU/Linux 5.15.0-133-generic x86_64)
2025-03-02 17:01:24.250 UTC [1215580/T1215715] INFO: Received 8/8 valid NTP replies from pool.ntp.org
2025-03-02 17:01:24.251 UTC [1215580/T1215715] INFO: Time offset: -3.306457e+00 ms (excluded 1 outliers)
2025-03-02 17:01:24.251 UTC [1215580/T1215715] INFO: Round-trip delay: 1.553535e+00 ms (excluded 1 outliers)
2025-03-02 17:29:00.190 UTC [1215580/T1215716] INFO: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
2025-03-02 17:29:00.190 UTC [1215580/T1215716] INFO: ---------------------------->  FTL crashed!  <----------------------------
2025-03-02 17:29:00.190 UTC [1215580/T1215716] INFO: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
2025-03-02 17:29:00.190 UTC [1215580/T1215716] INFO: Please report a bug at https://github.com/pi-hole/FTL/issues
2025-03-02 17:29:00.190 UTC [1215580/T1215716] INFO: and include in your report already the following details:
2025-03-02 17:29:00.190 UTC [1215580/T1215716] INFO: FTL has been running for 163670 seconds
2025-03-02 17:29:00.190 UTC [1215580/T1215716] INFO: FTL branch: master
2025-03-02 17:29:00.190 UTC [1215580/T1215716] INFO: FTL version: v6.0.3
2025-03-02 17:29:00.191 UTC [1215580/T1215716] INFO: FTL commit: 37f9a96e
2025-03-02 17:29:00.191 UTC [1215580/T1215716] INFO: FTL date: 2025-02-28 09:26:27 +0000
2025-03-02 17:29:00.191 UTC [1215580/T1215716] INFO: FTL user: started as pihole, ended as pihole
2025-03-02 17:29:00.191 UTC [1215580/T1215716] INFO: Compiled for linux/amd64 (compiled on CI) using cc (Alpine 14.2.0) 14.2.0
2025-03-02 17:29:00.191 UTC [1215580/T1215716] INFO: Process details: MID: 1215580
2025-03-02 17:29:00.191 UTC [1215580/T1215716] INFO:                  PID: 1215580
2025-03-02 17:29:00.191 UTC [1215580/T1215716] INFO:                  TID: 1215716
2025-03-02 17:29:00.191 UTC [1215580/T1215716] INFO:                  Name: database
2025-03-02 17:29:00.191 UTC [1215580/T1215716] INFO: Received signal: Segmentation fault
2025-03-02 17:29:00.191 UTC [1215580/T1215716] INFO:      at address: 0x28
2025-03-02 17:29:00.191 UTC [1215580/T1215716] INFO:      with code:  SEGV_MAPERR (Address not mapped to object)
2025-03-02 17:29:00.191 UTC [1215580/T1215716] INFO: !!! INFO: pihole-FTL has not been compiled with glibc/backtrace support, not generating one !!!
2025-03-02 17:29:00.191 UTC [1215580/T1215716] INFO: ------ Listing content of directory /dev/shm ------
2025-03-02 17:29:00.191 UTC [1215580/T1215716] INFO: File Mode User:Group      Size  Filename
2025-03-02 17:29:00.192 UTC [1215580/T1215716] INFO: rwxrwxrwx root:root       360   .
2025-03-02 17:29:00.192 UTC [1215580/T1215716] INFO: rwxr-xr-x root:root         4K  ..
2025-03-02 17:29:00.192 UTC [1215580/T1215716] INFO: rw------- pihole:pihole   786K  FTL-1215580-recycler
2025-03-02 17:29:00.192 UTC [1215580/T1215716] INFO: rw------- pihole:pihole    45K  FTL-1215580-dns-cache-lookup
2025-03-02 17:29:00.192 UTC [1215580/T1215716] INFO: rw------- pihole:pihole    29K  FTL-1215580-domains-lookup
2025-03-02 17:29:00.192 UTC [1215580/T1215716] INFO: rw------- pihole:pihole     8K  FTL-1215580-clients-lookup
2025-03-02 17:29:00.192 UTC [1215580/T1215716] INFO: rw------- pihole:pihole   569K  FTL-1215580-fifo-log
2025-03-02 17:29:00.192 UTC [1215580/T1215716] INFO: rw------- pihole:pihole    29K  FTL-1215580-per-client-regex
2025-03-02 17:29:00.192 UTC [1215580/T1215716] INFO: rw------- pihole:pihole   287K  FTL-1215580-dns-cache
2025-03-02 17:29:00.193 UTC [1215580/T1215716] INFO: rw------- pihole:pihole     8K  FTL-1215580-overTime
2025-03-02 17:29:00.193 UTC [1215580/T1215716] INFO: rw------- pihole:pihole     3M  FTL-1215580-queries
2025-03-02 17:29:00.193 UTC [1215580/T1215716] INFO: rw------- pihole:pihole    29K  FTL-1215580-upstreams
2025-03-02 17:29:00.193 UTC [1215580/T1215716] INFO: rw------- pihole:pihole     1M  FTL-1215580-clients
2025-03-02 17:29:00.193 UTC [1215580/T1215716] INFO: rw------- pihole:pihole   172K  FTL-1215580-domains
2025-03-02 17:29:00.193 UTC [1215580/T1215716] INFO: rw------- pihole:pihole   246K  FTL-1215580-strings
2025-03-02 17:29:00.194 UTC [1215580/T1215716] INFO: rw------- pihole:pihole   144   FTL-1215580-settings
2025-03-02 17:29:00.194 UTC [1215580/T1215716] INFO: rw------- pihole:pihole   328   FTL-1215580-counters
2025-03-02 17:29:00.194 UTC [1215580/T1215716] INFO: rw------- pihole:pihole    88   FTL-1215580-lock
2025-03-02 17:29:00.194 UTC [1215580/T1215716] INFO: ---------------------------------------------------
2025-03-02 17:29:00.194 UTC [1215580/T1215716] INFO: Please also include some lines from above the !!!!!!!!! header.
2025-03-02 17:29:00.194 UTC [1215580/T1215716] INFO: Thank you for helping us to improve our FTL engine!
2025-03-02 17:29:00.194 UTC [1215580/T1215716] INFO: Waiting for threads to join
2025-03-02 17:29:00.251 UTC [1215580/T1215719] INFO: Terminating timer thread
2025-03-02 17:29:01.006 UTC [1215580/T1215718] INFO: Terminating resolver thread
2025-03-02 17:29:01.190 UTC [1215580/T1215717] INFO: Terminating GC thread
2025-03-02 17:29:02.194 UTC [1215580/T1215716] INFO: Thread database (0) is still busy, cancelling it.
2025-03-02 17:29:08.750 UTC [1215580M] ERROR: Error when obtaining outer SHM lock: Previous owner died
2025-03-02 17:29:08.750 UTC [1215580M] ERROR: Error when obtaining inner SHM lock: Previous owner died
2025-03-02 17:29:10.004 UTC [1215580M] ERROR: export_queries_to_disk(): Failed to export queries: database is locked
2025-03-02 17:29:10.004 UTC [1215580M] INFO:     SQL query was: "INSERT INTO disk.query_storage SELECT * FROM query_storage WHERE id > ? AND timestamp < ?"

@streamdp streamdp mentioned this issue Mar 2, 2025
Open
@DL6ER
Copy link
Member

DL6ER commented Mar 2, 2025

Can you reproduce the crash (I guess so). If so, can you please follow the steps described on https://docs.pi-hole.net/ftldns/gdb/ and come back with the backtrace info? I will probably lead to the solution right away once we know where to look

@DL6ER DL6ER added the crash label Mar 2, 2025
@streamdp
Copy link

streamdp commented Mar 3, 2025 •
edited
Loading

@DL6ER I have connection problems all day yesterday with OpenDNS, and than pihole-FTL just crashed, I'm checked pihole.log and didn't see anything interesting, last several requests returned cached result for the google.com domain.

@streamdp
Copy link

streamdp commented Mar 3, 2025

@DL6ER I have two pihole instances: one works in the local network, second for the outside. Crashed the second instance. It's all I know for today about the problem =)

@streamdp
Copy link

streamdp commented Mar 3, 2025

@DL6ER I think in that case pihole-FTL should be restarted, but it's just stopped.

@DL6ER
Copy link
Member

DL6ER commented Mar 3, 2025

Yes, to my understanding this is also what should have happened:

Restart=on-failure
RestartSec=5s

https://github.com/pi-hole/pi-hole/blob/567bb724b18bf174f033d0b8b289cc44a5e9c8eb/advanced/Templates/pihole-FTL.systemd#L25-L26

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
crash
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@DL6ER @streamdp @luisenlag