-
-
Notifications
You must be signed in to change notification settings - Fork 230
Open
Labels
Description
Versions
- Pi-hole: Core version is v6.0.5 (Latest: v6.0.5)
- AdminLTE: Web version is v6.0.2 (Latest: v6.0.2)
- FTL: FTL version is v6.0.4 (Latest: v6.0.4)
Platform
- OS and version: Linux version 6.8.12-8-pve (build@proxmox) (gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) Update gravity-adv.sh pi-hole#1 SMP PREEMPT_DYNAMIC PMX 6.8.12-8 (2025-01-24T12:32Z)
- Platform: Proxmox LXC
Behavior
I use a dockerized nebula-sync to keep both my piholes in sync. However the 2nd pihole (the one receiving the replication) however often goes down and it seems like it takes 5 minutes to reboot the FTL which doesn't seem normal to me...
I also found this issue on nebula-sync's github but doesn't provide any solution: lovelaze/nebula-sync#69
snippet from the logs:
2025-03-29 15:35:06.496 CET [172M] INFO: NTP sync is disabled
2025-03-29 15:35:06.497 CET [172M] INFO: FTL is running as user pihole (UID 999)
2025-03-29 15:35:06.497 CET [172M] INFO: Reading certificate from /etc/pihole/tls.pem ...
2025-03-29 15:35:06.497 CET [172M] INFO: Using SSL/TLS certificate file /etc/pihole/tls.pem
2025-03-29 15:35:06.498 CET [172M] INFO: Web server ports:
2025-03-29 15:35:06.498 CET [172M] INFO: - 0.0.0.0:80 (HTTP, IPv4, optional, OK)
2025-03-29 15:35:06.498 CET [172M] INFO: - 0.0.0.0:443 (HTTPS, IPv4, optional, OK)
2025-03-29 15:35:06.498 CET [172M] INFO: - [::]:80 (HTTP, IPv6, optional, OK)
2025-03-29 15:35:06.498 CET [172M] INFO: - [::]:443 (HTTPS, IPv6, optional, OK)
2025-03-29 15:35:06.498 CET [172M] INFO: Restored 1 API session from the database
2025-03-29 15:35:06.501 CET [172M] INFO: Blocking status is enabled
2025-03-29 15:35:06.653 CET [172/T51934] INFO: Compiled 8 allow and 2 deny regex for 10 clients in 50.9 msec
2025-03-29 15:36:35.159 CET [51948/F172] WARNING: Connection error (127.0.0.1#5335): TCP connection failed while receiving payload length from upstream (Connection prematurely closed by remote server)
2025-03-29 15:36:35.172 CET [51949/F172] WARNING: Connection error (127.0.0.1#5335): TCP connection failed while receiving payload length from upstream (Connection prematurely closed by remote server)
2025-03-29 15:40:02.813 CET [172/T51940] INFO: Ignoring file etc/pihole/pihole.toml in Teleporter archive (not in import list)
2025-03-29 15:40:02.838 CET [172/T51940] INFO: Restarting FTL: Teleporter (ZIP) import
2025-03-29 15:40:02.838 CET [172M] INFO: Asked to terminate by "/usr/bin/pihole-FTL -f" (PID 172, user pihole UID 999)
2025-03-29 15:40:02.856 CET [172/T51955] INFO: No config changes detected
2025-03-29 15:40:02.894 CET [172/T51937] INFO: Terminating timer thread
2025-03-29 15:40:02.934 CET [172/T51934] INFO: Terminating database thread
2025-03-29 15:40:03.159 CET [172M] INFO: Finished final database update
2025-03-29 15:40:03.159 CET [172M] INFO: Waiting for threads to join
2025-03-29 15:40:03.159 CET [172M] INFO: Thread housekeeper (1) is idle, terminating it.
2025-03-29 15:40:03.159 CET [172M] INFO: Thread dns-client (2) is idle, terminating it.
2025-03-29 15:40:03.160 CET [172M] INFO: All threads joined
2025-03-29 15:40:03.167 CET [172M] INFO: PID file emptied
2025-03-29 15:40:03.168 CET [172M] INFO: Stored 1 API session in the database
2025-03-29 15:40:03.602 CET [172M] INFO: ########## FTL terminated after 4m 59s (internal restart)! ##########
2025-03-29 15:40:03.614 CET [172M] INFO: ########## FTL started on pi-hole2! ##########
2025-03-29 15:40:03.614 CET [172M] INFO: FTL branch: master
2025-03-29 15:40:03.614 CET [172M] INFO: FTL version: v6.0.4
2025-03-29 15:40:03.614 CET [172M] INFO: FTL commit: b7eb53bf
2025-03-29 15:40:03.614 CET [172M] INFO: FTL date: 2025-03-04 17:22:10 +0000
2025-03-29 15:40:03.614 CET [172M] INFO: FTL user: pihole
2025-03-29 15:40:03.614 CET [172M] INFO: Compiled for linux/amd64 (compiled on CI) using cc (Alpine 14.2.0) 14.2.0
2025-03-29 15:40:03.623 CET [172M] INFO: Wrote config file:
2025-03-29 15:40:03.623 CET [172M] INFO: - 153 total entries
2025-03-29 15:40:03.623 CET [172M] INFO: - 131 entries are default
2025-03-29 15:40:03.623 CET [172M] INFO: - 22 entries are modified
2025-03-29 15:40:03.623 CET [172M] INFO: - 0 entries are forced through environment
2025-03-29 15:40:03.626 CET [172M] INFO: Parsed config file /etc/pihole/pihole.toml successfully
2025-03-29 15:40:03.627 CET [172M] INFO: PID file does not exist or not readable
2025-03-29 15:40:03.627 CET [172M] INFO: No other running FTL process found.
2025-03-29 15:40:03.627 CET [172M] WARNING: Insufficient permissions to set process priority to -10 (CAP_SYS_NICE required), process priority remains at 0
2025-03-29 15:40:03.632 CET [172M] INFO: PID of FTL process: 172
2025-03-29 15:40:03.634 CET [172M] INFO: listening on 0.0.0.0 port 53
2025-03-29 15:40:03.634 CET [172M] INFO: listening on :: port 53
2025-03-29 15:40:03.636 CET [172M] INFO: PID of FTL process: 172
2025-03-29 15:40:03.638 CET [172M] INFO: Database version is 21
2025-03-29 15:40:03.639 CET [172M] INFO: Database successfully initialized
Debug Token
Thanks!
barstown