On a fresh new install the package is giving me errors unless I remove all the /dev/shm/FTL-*
files and restart the service:
-- Journal begins at Sat 2021-02-27 08:25:46 UTC, ends at Sun 2021-02-28 21:25:47 UTC. --
Feb 28 21:25:19 instance systemd[1]: Starting Pi-hole FTLDNS engine...
Feb 28 21:25:19 instance systemd[1]: Started Pi-hole FTLDNS engine.
Feb 28 21:25:19 instance systemd[1]: Stopping Pi-hole FTLDNS engine...
Feb 28 21:25:19 instance systemd[1]: pihole-FTL.service: Succeeded.
Feb 28 21:25:19 instance systemd[1]: Stopped Pi-hole FTLDNS engine.
Feb 28 21:25:19 instance systemd[1]: Starting Pi-hole FTLDNS engine...
Feb 28 21:25:19 instance systemd[1]: Started Pi-hole FTLDNS engine.
Feb 28 21:25:19 instance pihole-FTL[28554]: [2021-02-28 21:25:19.091 28554M] Using log file /run/log/pihole-ftl/pihole-FTL.log
Feb 28 21:25:19 instance pihole-FTL[28554]: [2021-02-28 21:25:19.091 28554M] ########## FTL started! ##########
Feb 28 21:25:19 instance pihole-FTL[28554]: [2021-02-28 21:25:19.091 28554M] FTL branch: master
Feb 28 21:25:19 instance pihole-FTL[28554]: [2021-02-28 21:25:19.091 28554M] FTL version: v5.7
Feb 28 21:25:19 instance pihole-FTL[28554]: [2021-02-28 21:25:19.091 28554M] FTL commit: builtfromreleasetarball
Feb 28 21:25:19 instance pihole-FTL[28554]: [2021-02-28 21:25:19.091 28554M] FTL date: 2021-02-16
Feb 28 21:25:19 instance pihole-FTL[28554]: [2021-02-28 21:25:19.091 28554M] FTL user: pihole
Feb 28 21:25:19 instance pihole-FTL[28554]: [2021-02-28 21:25:19.091 28554M] Compiled for x86_64 (compiled locally) using cc (GCC) 10.2.0
Feb 28 21:25:19 instance pihole-FTL[28554]: [2021-02-28 21:25:19.091 28554M] FATAL: create_shm(): Failed to create shared memory object "FTL-lock": File exists
Feb 28 21:25:19 instance pihole-FTL[28554]: [2021-02-28 21:25:19.091 28554M] Initialization of shared memory failed.
Feb 28 21:25:19 instance systemd[1]: pihole-FTL.service: Main process exited, code=exited, status=1/FAILURE
Feb 28 21:25:19 instance systemd[1]: pihole-FTL.service: Failed with result 'exit-code'.
Feb 28 21:25:19 instance systemd[1]: pihole-FTL.service: Scheduled restart job, restart counter is at 1.
Could this be because the package is setup to automatically enable the service upon install? Something else?
Also, is there any reason why (a very old) pi-hole-ftl.db
is included with this package? Wouldn't pihole set that up automatically on its first run?
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.