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

V6 on ASUSTOR NAS using Portainer and Docker #2210

Open
anmcleanRH opened this issue Feb 20, 2025 · 2 comments
Open

V6 on ASUSTOR NAS using Portainer and Docker #2210

anmcleanRH opened this issue Feb 20, 2025 · 2 comments

Comments

@anmcleanRH
Copy link

Versions

see logs below

Platform

see logs below

Expected behavior

Expect pi-hole to start

Actual behavior / bug

FTL crash and pi-hole does not start

Steps to reproduce

Steps to reproduce the behavior:

  1. Start Container
  2. it crashes
  3. look at log
  4. See error

Additional context

Logs:
[i] Starting pihole-FTL (no-daemon) as root
[i] Version info:
Core version is v6.0 (Latest: v6.0.1)
Web version is v6.0 (Latest: v6.0)
FTL version is v6.0 (Latest: v6.0)
2025-02-20 13:43:51.269 AEST [93M] INFO: ########## FTL started on HomeServer! ##########
2025-02-20 13:43:51.270 AEST [93M] INFO: FTL branch: master
2025-02-20 13:43:51.270 AEST [93M] INFO: FTL version: v6.0
2025-02-20 13:43:51.270 AEST [93M] INFO: FTL commit: eaa7dbb
2025-02-20 13:43:51.270 AEST [93M] INFO: FTL date: 2025-02-18 17:19:26 +0000
2025-02-20 13:43:51.270 AEST [93M] INFO: FTL user: root
2025-02-20 13:43:51.270 AEST [93M] INFO: Compiled for linux/arm64/v8 (compiled on CI) using cc (Alpine 14.2.0) 14.2.0
2025-02-20 13:43:51.275 AEST [93M] INFO: 1 FTLCONF environment variable found (1 used, 0 invalid, 0 ignored)
2025-02-20 13:43:51.275 AEST [93M] INFO: [✓] FTLCONF_dns_upstreams is used
2025-02-20 13:43:51.278 AEST [93M] INFO: Wrote config file:
2025-02-20 13:43:51.278 AEST [93M] INFO: - 152 total entries
2025-02-20 13:43:51.278 AEST [93M] INFO: - 149 entries are default
2025-02-20 13:43:51.278 AEST [93M] INFO: - 3 entries are modified
2025-02-20 13:43:51.278 AEST [93M] INFO: - 1 entry is forced through environment
2025-02-20 13:43:51.368 AEST [93M] INFO: Parsed config file /etc/pihole/pihole.toml successfully
2025-02-20 13:43:51.368 AEST [93M] INFO: PID file does not exist or not readable
2025-02-20 13:43:51.368 AEST [93M] INFO: No other running FTL process found.
2025-02-20 13:43:51.368 AEST [93M] WARNING: Insufficient permissions to set process priority to -10 (CAP_SYS_NICE required), process priority remains at 0
2025-02-20 13:43:51.372 AEST [93M] WARNING: Starting pihole-FTL as user root is not recommended
2025-02-20 13:43:51.373 AEST [93M] INFO: PID of FTL process: 93
2025-02-20 13:43:51.374 AEST [93M] INFO: listening on 0.0.0.0 port 53
2025-02-20 13:43:51.375 AEST [93M] INFO: listening on :: port 53
2025-02-20 13:43:51.385 AEST [93M] INFO: PID of FTL process: 93
2025-02-20 13:43:51.437 AEST [93M] ERROR: SQLite3: recovered 2 frames from WAL file /etc/pihole/pihole-FTL.db-wal (283)
2025-02-20 13:43:51.446 AEST [93M] INFO: Database version is 21
2025-02-20 13:43:51.541 AEST [93M] INFO: Database successfully initialized
2025-02-20 13:43:51.550 AEST [93M] INFO: Imported 15 queries from the on-disk database (it has 15 rows)
2025-02-20 13:43:51.551 AEST [93M] INFO: Parsing queries in database
2025-02-20 13:43:51.554 AEST [93M] INFO: Imported 15 queries from the long-term database
2025-02-20 13:43:51.555 AEST [93M] INFO: -> Total DNS queries: 15
2025-02-20 13:43:51.555 AEST [93M] INFO: -> Cached DNS queries: 10
2025-02-20 13:43:51.555 AEST [93M] INFO: -> Forwarded DNS queries: 5
2025-02-20 13:43:51.555 AEST [93M] INFO: -> Blocked DNS queries: 0
2025-02-20 13:43:51.555 AEST [93M] INFO: -> Unknown DNS queries: 0
2025-02-20 13:43:51.555 AEST [93M] INFO: -> Unique domains: 6
2025-02-20 13:43:51.555 AEST [93M] INFO: -> Unique clients: 2
2025-02-20 13:43:51.555 AEST [93M] INFO: -> DNS cache records: 0
2025-02-20 13:43:51.555 AEST [93M] INFO: -> Known forward destinations: 1
2025-02-20 13:43:52.047 AEST [93M] WARNING: Insufficient permissions to set system time (CAP_SYS_TIME required), NTP client not available
2025-02-20 13:43:52.047 AEST [93/T123] INFO: NTP server listening on 0.0.0.0:123 (IPv4)
2025-02-20 13:43:52.047 AEST [93/T124] INFO: NTP server listening on :::123 (IPv6)
2025-02-20 13:43:52.047 AEST [93M] INFO: FTL is running as root
2025-02-20 13:43:52.048 AEST [93M] INFO: Reading certificate from /etc/pihole/tls.pem ...
2025-02-20 13:43:52.049 AEST [93M] INFO: Using SSL/TLS certificate file /etc/pihole/tls.pem
2025-02-20 13:43:52.050 AEST [93M] WARNING: No web server ports configured!
2025-02-20 13:43:52.050 AEST [93/T130] INFO: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
2025-02-20 13:43:52.050 AEST [93/T130] INFO: ----------------------------> FTL crashed! <----------------------------
2025-02-20 13:43:52.050 AEST [93/T130] INFO: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
2025-02-20 13:43:52.050 AEST [93/T130] INFO: Please report a bug at https://github.com/pi-hole/FTL/issues
2025-02-20 13:43:52.050 AEST [93/T130] INFO: and include in your report already the following details:
2025-02-20 13:43:52.051 AEST [93M] INFO: Restored 0 API sessions from the database
2025-02-20 13:43:52.051 AEST [93/T130] INFO: FTL has been running for 1 seconds
2025-02-20 13:43:52.051 AEST [93/T130] INFO: FTL branch: master
2025-02-20 13:43:52.051 AEST [93/T130] INFO: FTL version: v6.0
2025-02-20 13:43:52.051 AEST [93/T130] INFO: FTL commit: eaa7dbb
2025-02-20 13:43:52.051 AEST [93/T130] INFO: FTL date: 2025-02-18 17:19:26 +0000
2025-02-20 13:43:52.051 AEST [93/T130] INFO: FTL user: started as root, ended as root
2025-02-20 13:43:52.051 AEST [93/T130] INFO: Compiled for linux/arm64/v8 (compiled on CI) using cc (Alpine 14.2.0) 14.2.0
2025-02-20 13:43:52.051 AEST [93/T130] INFO: Process details: MID: 93
2025-02-20 13:43:52.051 AEST [93/T130] INFO: PID: 93
2025-02-20 13:43:52.051 AEST [93/T130] INFO: TID: 130
2025-02-20 13:43:52.051 AEST [93/T130] INFO: Name: civetweb-master
2025-02-20 13:43:52.051 AEST [93/T130] INFO: Received signal: Segmentation fault
2025-02-20 13:43:52.051 AEST [93/T130] INFO: at address: 0
2025-02-20 13:43:52.051 AEST [93/T130] INFO: with code: SEGV_MAPERR (Address not mapped to object)
2025-02-20 13:43:52.051 AEST [93/T130] INFO: !!! INFO: pihole-FTL has not been compiled with glibc/backtrace support, not generating one !!!
2025-02-20 13:43:52.051 AEST [93/T130] INFO: ------ Listing content of directory /dev/shm ------
2025-02-20 13:43:52.052 AEST [93/T130] INFO: File Mode User:Group Size Filename
2025-02-20 13:43:52.052 AEST [93/T130] INFO: rwxrwxrwx root:root 360 .
2025-02-20 13:43:52.052 AEST [93/T130] INFO: rwxr-xr-x root:root 320 ..
2025-02-20 13:43:52.052 AEST [93/T130] INFO: rw------- root:root 786K FTL-93-recycler
2025-02-20 13:43:52.052 AEST [93/T130] INFO: rw------- root:root 4K FTL-93-dns-cache-lookup
2025-02-20 13:43:52.052 AEST [93/T130] INFO: rw------- root:root 4K FTL-93-domains-lookup
2025-02-20 13:43:52.052 AEST [93/T130] INFO: rw------- root:root 4K FTL-93-clients-lookup
2025-02-20 13:43:52.052 AEST [93/T130] INFO: rw------- root:root 569K FTL-93-fifo-log
2025-02-20 13:43:52.053 AEST [93/T130] INFO: rw------- root:root 4K FTL-93-per-client-regex
2025-02-20 13:43:52.053 AEST [93/T130] INFO: rw------- root:root 20K FTL-93-dns-cache
2025-02-20 13:43:52.053 AEST [93/T130] INFO: rw------- root:root 8K FTL-93-overTime
2025-02-20 13:43:52.053 AEST [93/T130] INFO: rw------- root:root 295K FTL-93-queries
2025-02-20 13:43:52.053 AEST [93/T130] INFO: rw------- root:root 29K FTL-93-upstreams
2025-02-20 13:43:52.053 AEST [93/T130] INFO: rw------- root:root 348K FTL-93-clients
2025-02-20 13:43:52.053 AEST [93/T130] INFO: rw------- root:root 4K FTL-93-domains
2025-02-20 13:43:52.053 AEST [93/T130] INFO: rw------- root:root 82K FTL-93-strings
2025-02-20 13:43:52.054 AEST [93/T130] INFO: rw------- root:root 144 FTL-93-settings
2025-02-20 13:43:52.054 AEST [93/T130] INFO: rw------- root:root 328 FTL-93-counters
2025-02-20 13:43:52.054 AEST [93/T130] INFO: rw------- root:root 88 FTL-93-lock
2025-02-20 13:43:52.054 AEST [93/T130] INFO: ---------------------------------------------------
2025-02-20 13:43:52.054 AEST [93/T130] INFO: Please also include some lines from above the !!!!!!!!! header.
2025-02-20 13:43:52.054 AEST [93/T130] INFO: Thank you for helping us to improve our FTL engine!
2025-02-20 13:43:52.054 AEST [93/T130] INFO: PID file emptied
2025-02-20 13:43:52.055 AEST [93/T130] INFO: Stored 0 API sessions in the database
2025-02-20 13:43:52.127 AEST [93M] INFO: Blocking status is enabled
2025-02-20 13:43:52.247 AEST [93/T125] INFO: Compiled 0 allow and 0 deny regex for 2 clients in 0.3 msec

@DL6ER
Copy link
Member

DL6ER commented Feb 21, 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
Copy link
Member

DL6ER commented Mar 1, 2025

Platform

see logs below

The question is more like: What is the hardware you are running Pi-hole on? The title has "ASUSTOR NAS" but this is not very precise. We are seeing similar issues on Synology devices, this bug will be fixed with the upcoming (not yet released) version of FTL.

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

No branches or pull requests

2 participants