@max.bra - I wonder if there is some race condition. I find that pihole-FTL fails to start about 1:3 times. In journalctl, the reason is dnsmasq[105]: failed to create listening socket for port 53: Address already in use
... here is a complete section of the log when it fails:
May 19 05:36:22 pihole pihole-FTL[333]: dnsmasq: failed to create listening socket for port 53: Address already in use
May 19 05:36:22 pihole pihole-FTL[333]: [2019-05-19 05:36:22.198 333] Using log file /run/log/pihole-ftl/pihole-FTL.log
May 19 05:36:22 pihole pihole-FTL[333]: [2019-05-19 05:36:22.198 333] ########## FTL started! ##########
May 19 05:36:22 pihole pihole-FTL[333]: [2019-05-19 05:36:22.198 333] FTL branch: master
May 19 05:36:22 pihole pihole-FTL[333]: [2019-05-19 05:36:22.199 333] FTL version: v4.3
May 19 05:36:22 pihole pihole-FTL[333]: [2019-05-19 05:36:22.199 333] FTL commit: 61c1f2a
May 19 05:36:22 pihole pihole-FTL[333]: [2019-05-19 05:36:22.199 333] FTL date: 2019-05-19
May 19 05:36:22 pihole pihole-FTL[333]: [2019-05-19 05:36:22.199 333] FTL user: root
May 19 05:36:22 pihole pihole-FTL[333]: [2019-05-19 05:36:22.199 333] Starting config file parsing (/etc/pihole/pihole-FTL.conf)
May 19 05:36:22 pihole pihole-FTL[333]: [2019-05-19 05:36:22.199 333] SOCKET_LISTENING: only local
May 19 05:36:22 pihole pihole-FTL[333]: [2019-05-19 05:36:22.199 333] AAAA_QUERY_ANALYSIS: Hide AAAA queries
May 19 05:36:22 pihole pihole-FTL[333]: [2019-05-19 05:36:22.199 333] MAXDBDAYS: max age for stored queries is 365 days
May 19 05:36:22 pihole pihole-FTL[333]: [2019-05-19 05:36:22.199 333] RESOLVE_IPV6: Don't resolve IPv6 addresses
May 19 05:36:22 pihole pihole-FTL[333]: [2019-05-19 05:36:22.199 333] RESOLVE_IPV4: Resolve IPv4 addresses
May 19 05:36:22 pihole pihole-FTL[333]: [2019-05-19 05:36:22.199 333] DBINTERVAL: saving to DB file every 10800 seconds
May 19 05:36:22 pihole pihole-FTL[333]: [2019-05-19 05:36:22.199 333] DBFILE: Using /etc/pihole/pihole-FTL.db
May 19 05:36:22 pihole pihole-FTL[333]: [2019-05-19 05:36:22.199 333] MAXLOGAGE: Importing up to 24.0 hours of log data
May 19 05:36:22 pihole pihole-FTL[333]: [2019-05-19 05:36:22.200 333] PRIVACYLEVEL: Set to 0
May 19 05:36:22 pihole pihole-FTL[333]: [2019-05-19 05:36:22.200 333] IGNORE_LOCALHOST: Show queries from localhost
May 19 05:36:22 pihole pihole-FTL[333]: [2019-05-19 05:36:22.200 333] BLOCKINGMODE: Null IPs for blocked domains
May 19 05:36:22 pihole pihole-FTL[333]: [2019-05-19 05:36:22.200 333] ANALYZE_ONLY_A_AND_AAAA: Disabled. Analyzing all queri>
May 19 05:36:22 pihole pihole-FTL[333]: [2019-05-19 05:36:22.200 333] DBIMPORT: Importing history from database
May 19 05:36:22 pihole pihole-FTL[333]: [2019-05-19 05:36:22.200 333] PIDFILE: Using /run/pihole-ftl/pihole-FTL.pid
May 19 05:36:22 pihole pihole-FTL[333]: [2019-05-19 05:36:22.200 333] PORTFILE: Using /run/pihole-ftl/pihole-FTL.port
May 19 05:36:22 pihole pihole-FTL[333]: [2019-05-19 05:36:22.200 333] SOCKETFILE: Using /run/pihole-ftl/FTL.sock
May 19 05:36:22 pihole pihole-FTL[333]: [2019-05-19 05:36:22.200 333] WHITELISTFILE: Using /etc/pihole/whitelist.txt
May 19 05:36:22 pihole pihole-FTL[333]: [2019-05-19 05:36:22.200 333] BLACKLISTFILE: Using /etc/pihole/black.list
May 19 05:36:22 pihole pihole-FTL[333]: [2019-05-19 05:36:22.200 333] GRAVITYFILE: Using /etc/pihole/gravity.list
May 19 05:36:22 pihole pihole-FTL[333]: [2019-05-19 05:36:22.201 333] REGEXLISTFILE: Using /etc/pihole/regex.list
May 19 05:36:22 pihole dnsmasq[333]: failed to create listening socket for port 53: Address already in use
May 19 05:36:22 pihole systemd[1]: pihole-FTL.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Pinned Comments
max.bra commented on 2018-02-09 16:46 (UTC) (edited on 2019-10-18 23:13 (UTC) by max.bra)
ArchLinux Pi-hole is not officially supported by Pi-hole project. In case of bugs and malfunctions please DO NOT file a report upstream.
First of all check if the wiki (https://wiki.archlinux.org/index.php/Pi-hole) can help then ask here for assistance and tips.
When it will be excluded that the problem does not depend on ArchLinux we will file a bug upstream.