FTL crashed
SvenHerr opened this issue · comments
I only share it because it could help. Im going back to the current release now
Versions
Core
Version is 719ce80 (Latest: v5.17.2)
Branch is development-v6
Hash is 719ce801 (Latest: 719ce801)
Web
Version is 2889bb5 (Latest: v5.21)
Branch is development-v6
Hash is 2889bb5a (Latest: 2889bb5a)
FTL
Version is vDev-17a2038 (Latest: v5.23)
Branch is development-v6
Hash is 17a2038 (Latest: 8eef4d8)
- Pi-hole:
- AdminLTE:
- FTL:
Platform
- OS and version:
- Platform: Raspberry Pi 4
Expected behavior
Actual behavior / bug
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
2023-12-14 21:37:02.804 [1303/F167] INFO: ----------------------------> FTL crashed! <----------------------------
2023-12-14 21:37:02.804 [1303/F167] INFO: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
2023-12-14 21:37:02.804 [1303/F167] INFO: Please report a bug at https://github.com/pi-hole/FTL/issues
2023-12-14 21:37:02.804 [1303/F167] INFO: and include in your report already the following details:
2023-12-14 21:37:02.804 [1303/F167] INFO: FTL has been running for 3045 seconds
2023-12-14 21:37:02.804 [1303/F167] INFO: FTL branch: development-v6
2023-12-14 21:37:02.804 [1303/F167] INFO: FTL version: vDev-17a2038
2023-12-14 21:37:02.805 [1303/F167] INFO: FTL commit: 17a2038
2023-12-14 21:37:02.805 [1303/F167] INFO: FTL date: 2023-12-13 19:45:14 +0100
2023-12-14 21:37:02.805 [1303/F167] INFO: FTL user: started as pihole, ended as pihole
2023-12-14 21:37:02.805 [1303/F167] INFO: Compiled for linux/arm64/v8 (compiled on CI) using cc (Alpine 12.2.1_git20220924-r10) 12.2.1 20220924
2023-12-14 21:37:02.805 [1303/F167] INFO: Process details: MID: 167
2023-12-14 21:37:02.806 [1303/F167] INFO: PID: 1303
2023-12-14 21:37:02.806 [1303/F167] INFO: TID: 1303
2023-12-14 21:37:02.806 [1303/F167] INFO: Name: pihole-FTL
2023-12-14 21:37:02.806 [1303/F167] INFO: Received signal: Segmentation fault
2023-12-14 21:37:02.806 [1303/F167] INFO: at address: 0x10
2023-12-14 21:37:02.806 [1303/F167] INFO: with code: SEGV_MAPERR (Address not mapped to object)
2023-12-14 21:37:02.806 [1303/F167] INFO: !!! INFO: pihole-FTL has not been compiled with glibc/backtrace support, not generating one !!!
2023-12-14 21:37:02.806 [1303/F167] INFO: ------ Listing content of directory /dev/shm ------
2023-12-14 21:37:02.807 [1303/F167] INFO: File Mode User:Group Size Filename
2023-12-14 21:37:02.807 [1303/F167] INFO: rwxrwxrwx root:root 280 .
2023-12-14 21:37:02.807 [1303/F167] INFO: rwxr-xr-x root:root 320 ..
2023-12-14 21:37:02.808 [1303/F167] INFO: rw------- pihole:pihole 560K FTL-fifo-log
2023-12-14 21:37:02.808 [1303/F167] INFO: rw------- pihole:pihole 4K FTL-per-client-regex
2023-12-14 21:37:02.809 [1303/F167] INFO: rw------- pihole:pihole 25K FTL-dns-cache
2023-12-14 21:37:02.809 [1303/F167] INFO: rw------- pihole:pihole 8K FTL-overTime
2023-12-14 21:37:02.810 [1303/F167] INFO: rw------- pihole:pihole 786K FTL-queries
2023-12-14 21:37:02.810 [1303/F167] INFO: rw------- pihole:pihole 29K FTL-upstreams
2023-12-14 21:37:02.810 [1303/F167] INFO: rw------- pihole:pihole 86K FTL-clients
2023-12-14 21:37:02.811 [1303/F167] INFO: rw------- pihole:pihole 33K FTL-domains
2023-12-14 21:37:02.811 [1303/F167] INFO: rw------- pihole:pihole 82K FTL-strings
2023-12-14 21:37:02.812 [1303/F167] INFO: rw------- pihole:pihole 16 FTL-settings
2023-12-14 21:37:02.812 [1303/F167] INFO: rw------- pihole:pihole 292 FTL-counters
2023-12-14 21:37:02.813 [1303/F167] INFO: rw------- pihole:pihole 88 FTL-lock
2023-12-14 21:37:02.813 [1303/F167] INFO: ---------------------------------------------------
2023-12-14 21:37:02.813 [1303/F167] INFO: Please also include some lines from above the !!!!!!!!! header.
2023-12-14 21:37:02.813 [1303/F167] INFO: Thank you for helping us to improve our FTL engine!
2023-12-14 21:37:02.813 [1303/F167] INFO: Asking parent pihole-FTL (PID 167) to shut down
2023-12-14 21:37:02.813 [1303/F167] INFO: FTL fork terminated!
2023-12-14 21:37:02.814 [167M] INFO: Received: RT37 (37 -> 2)
2023-12-14 21:37:02.814 [167M] ERR: Error when obtaining outer SHM lock: Previous owner died
2023-12-14 21:37:02.814 [167M] ERR: Error when obtaining inner SHM lock: Previous owner died
2023-12-14 21:37:02.815 [167M] INFO: Shutting down... // exit code 1 // jmpret 0
2023-12-14 21:37:03.153 [167M] INFO: Finished final database update
2023-12-14 21:37:03.154 [167M] INFO: Waiting for threads to join
2023-12-14 21:37:03.154 [167M] INFO: Thread database (0) is idle, terminating it.
2023-12-14 21:37:03.154 [167M] INFO: Thread housekeeper (1) is idle, terminating it.
2023-12-14 21:37:03.155 [167M] INFO: Thread DNS client (2) is idle, terminating it.
2023-12-14 21:37:03.155 [167M] INFO: All threads joined
2023-12-14 21:37:03.174 [167M] INFO: Stored 1 API session in the database
2023-12-14 21:37:03.949 [167M] INFO: ########## FTL terminated after 50m 46s (code 1)! ##########
Steps to reproduce
Steps to reproduce the behavior:
- Go to '...'
- Click on '....'
- Scroll down to '....'
- See error
Debug Token
- URL:
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
Please, if possible also include some lines from above the !!!!!!!!! header.
Please, if possible also include some lines from above the
!!!!!!!!!header.
i dont have it anymore in my terminal but next time i will store it
This issue is stale because it has been open 30 days with no activity. Please comment or update this issue or it will be closed in 5 days.