Hi, not to detract from existing issues, I've wanted to report another race condition for a while.
Perhaps this is just me, but if I restart pihole-FTL systemd service too fast, or sometimes even with an existing but killed service, files may be left in /dev/shm that cause a conflict to start the process.
pihole-FTL[15477]: ########## FTL started! ##########
pihole-FTL[15477]: FTL branch: master
pihole-FTL[15477]: FTL version: v5.8.1
pihole-FTL[15477]: FTL commit: builtfromreleasetarball
pihole-FTL[15477]: FTL date: 2021-04-21
pihole-FTL[15477]: FTL user: pihole
pihole-FTL[15477]: Compiled for armv7l (compiled locally) using cc (GCC) 10.2.0
pihole-FTL[15477]: FATAL: create_shm(): Failed to create shared memory object "FTL-lock": File exists
pihole-FTL[15477]: Initialization of shared memory failed.
systemd[1]: pihole-FTL.service: Main process exited, code=exited, status=1/FAILURE
systemd[1]: pihole-FTL.service: Failed with result 'exit-code'.
systemd[1]: pihole-FTL.service: Scheduled restart job, restart counter is at 3.
systemd[1]: Stopped Pi-hole FTLDNS engine.
systemd[1]: pihole-FTL.service: Start request repeated too quickly.
systemd[1]: pihole-FTL.service: Failed with result 'exit-code'.
systemd[1]: Failed to start Pi-hole FTLDNS engine.
I'm not sure if there's a way to wipe any /dev/shm/FTL* files before starting the process, I'm not entirely familiar with systemd service files.
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.