After running pihole -up I get this error
sudo pihole enable
/opt/pihole/api.sh: line 25: utilsfile: readonly variable
Communication error. Is FTL running?
I've rebooted multiple times - debug below
We had a recent report with that message, see Pihole FTL fails because of a segmentation fault, where a user is also able to trigger a segfault by just running pihole-FTL.
By chance, your debug log contains a part of such a crash:
-----tail of FTL.log------
2025-05-31 21:22:58.881 AEST [1978M] INFO: FTL user: started as pihole, ended as pihole
2025-05-31 21:22:58.881 AEST [1978M] INFO: Compiled for linux/arm64/v8 (compiled on CI) using cc (Alpine 14.2.0) 14.2.0
2025-05-31 21:22:58.881 AEST [1978M] INFO: Process details: MID: 1978
2025-05-31 21:22:58.881 AEST [1978M] INFO: PID: 1978
2025-05-31 21:22:58.881 AEST [1978M] INFO: TID: 1978
2025-05-31 21:22:58.881 AEST [1978M] INFO: Name: pihole-FTL
2025-05-31 21:22:58.881 AEST [1978M] INFO: Received signal: Segmentation fault
2025-05-31 21:22:58.881 AEST [1978M] INFO: at address: 0xffff9066e4bb
2025-05-31 21:22:58.881 AEST [1978M] INFO: with code: SEGV_MAPERR (Address not mapped to object)
2025-05-31 21:22:58.881 AEST [1978M] INFO: !!! INFO: pihole-FTL has not been compiled with glibc/backtrace support, not generating one !!!
2025-05-31 21:22:58.881 AEST [1978M] INFO: ------ Listing content of directory /dev/shm ------
2025-05-31 21:22:58.881 AEST [1978M] INFO: File Mode User:Group Size Filename
2025-05-31 21:22:58.881 AEST [1978M] INFO: rwxrwxrwx root:root 360 .
2025-05-31 21:22:58.881 AEST [1978M] INFO: rwxr-xr-x root:root 4K ..
2025-05-31 21:22:58.882 AEST [1978M] INFO: rw------- pihole:pihole 786K FTL-1978-recycler
2025-05-31 21:22:58.882 AEST [1978M] INFO: rw------- pihole:pihole 4K FTL-1978-dns-cache-lookup
2025-05-31 21:22:58.882 AEST [1978M] INFO: rw------- pihole:pihole 8K FTL-1978-domains-lookup
2025-05-31 21:22:58.882 AEST [1978M] INFO: rw------- pihole:pihole 4K FTL-1978-clients-lookup
2025-05-31 21:22:58.882 AEST [1978M] INFO: rw------- pihole:pihole 569K FTL-1978-fifo-log
2025-05-31 21:22:58.882 AEST [1978M] INFO: rw------- pihole:pihole 4K FTL-1978-per-client-regex
2025-05-31 21:22:58.882 AEST [1978M] INFO: rw------- pihole:pihole 20K FTL-1978-dns-cache
2025-05-31 21:22:58.883 AEST [1978M] INFO: rw------- pihole:pihole 8K FTL-1978-overTime
2025-05-31 21:22:58.883 AEST [1978M] INFO: rw------- pihole:pihole 885K FTL-1978-queries
2025-05-31 21:22:58.883 AEST [1978M] INFO: rw------- pihole:pihole 29K FTL-1978-upstreams
2025-05-31 21:22:58.883 AEST [1978M] INFO: rw------- pihole:pihole 348K FTL-1978-clients
2025-05-31 21:22:58.883 AEST [1978M] INFO: rw------- pihole:pihole 25K FTL-1978-domains
2025-05-31 21:22:58.883 AEST [1978M] INFO: rw------- pihole:pihole 82K FTL-1978-strings
2025-05-31 21:22:58.883 AEST [1978M] INFO: rw------- pihole:pihole 144 FTL-1978-settings
2025-05-31 21:22:58.883 AEST [1978M] INFO: rw------- pihole:pihole 328 FTL-1978-counters
2025-05-31 21:22:58.884 AEST [1978M] INFO: rw------- pihole:pihole 88 FTL-1978-lock
2025-05-31 21:22:58.884 AEST [1978M] INFO: ---------------------------------------------------
2025-05-31 21:22:58.884 AEST [1978M] INFO: Please also include some lines from above the !!!!!!!!! header.
2025-05-31 21:22:58.884 AEST [1978M] INFO: Thank you for helping us to improve our FTL engine!
2025-05-31 21:22:58.884 AEST [1978M] INFO: PID file emptied
2025-05-31 21:22:58.909 AEST [1978M] INFO: ########## FTL terminated after 1s 231ms (code 1)! ##########
Could you please extract the full crash log lines and share them here?
To help with that, the start of a crash can be found by running
sudo grep -n 'FTL crashed!' /var/log/pihole/FTL.log*
That should find any crash occurrences and list them with their file and line number.
/var/log/pihole/FTL.log.1:110:2025-05-31 19:45:26.676 AEST [1098797M] INFO: ----------------------------> FTL crashed! <----------------------------
/var/log/pihole/FTL.log.1:189:2025-05-31 19:45:33.456 AEST [1098938M] INFO: ----------------------------> FTL crashed! <----------------------------
/var/log/pihole/FTL.log.1:268:2025-05-31 19:45:40.193 AEST [1098995M] INFO: ----------------------------> FTL crashed! <----------------------------
/var/log/pihole/FTL.log.1:347:2025-05-31 19:45:46.907 AEST [1099080M] INFO: ----------------------------> FTL crashed! <----------------------------
/var/log/pihole/FTL.log.1:426:2025-05-31 19:45:53.745 AEST [1099132M] INFO: ----------------------------> FTL crashed! <----------------------------
/var/log/pihole/FTL.log.1:505:2025-05-31 19:59:46.920 AEST [1376M] INFO: ----------------------------> FTL crashed! <----------------------------
/var/log/pihole/FTL.log.1:584:2025-05-31 19:59:53.924 AEST [1744M] INFO: ----------------------------> FTL crashed! <----------------------------
/var/log/pihole/FTL.log.1:663:2025-05-31 20:00:00.737 AEST [1797M] INFO: ----------------------------> FTL crashed! <----------------------------
/var/log/pihole/FTL.log.1:742:2025-05-31 20:00:07.623 AEST [1886M] INFO: ----------------------------> FTL crashed! <----------------------------
/var/log/pihole/FTL.log.1:821:2025-05-31 20:00:14.576 AEST [1905M] INFO: ----------------------------> FTL crashed! <----------------------------
/var/log/pihole/FTL.log.1:900:2025-05-31 21:02:12.741 AEST [3619M] INFO: ----------------------------> FTL crashed! <----------------------------
/var/log/pihole/FTL.log.1:979:2025-05-31 21:02:19.338 AEST [3739M] INFO: ----------------------------> FTL crashed! <----------------------------
/var/log/pihole/FTL.log.1:1058:2025-05-31 21:02:26.104 AEST [3796M] INFO: ----------------------------> FTL crashed! <----------------------------
/var/log/pihole/FTL.log.1:1137:2025-05-31 21:02:32.830 AEST [3868M] INFO: ----------------------------> FTL crashed! <----------------------------
/var/log/pihole/FTL.log.1:1216:2025-05-31 21:02:39.577 AEST [3935M] INFO: ----------------------------> FTL crashed! <----------------------------
/var/log/pihole/FTL.log.1:1295:2025-05-31 21:07:06.221 AEST [4214M] INFO: ----------------------------> FTL crashed! <----------------------------
/var/log/pihole/FTL.log.1:1374:2025-05-31 21:07:13.016 AEST [4241M] INFO: ----------------------------> FTL crashed! <----------------------------
/var/log/pihole/FTL.log.1:1453:2025-05-31 21:07:19.628 AEST [4268M] INFO: ----------------------------> FTL crashed! <----------------------------
/var/log/pihole/FTL.log.1:1532:2025-05-31 21:07:26.545 AEST [4287M] INFO: ----------------------------> FTL crashed! <----------------------------
/var/log/pihole/FTL.log.1:1611:2025-05-31 21:07:33.549 AEST [4308M] INFO: ----------------------------> FTL crashed! <----------------------------
/var/log/pihole/FTL.log.1:1690:2025-05-31 21:22:31.952 AEST [1360M] INFO: ----------------------------> FTL crashed! <----------------------------
/var/log/pihole/FTL.log.1:1769:2025-05-31 21:22:38.745 AEST [1827M] INFO: ----------------------------> FTL crashed! <----------------------------
/var/log/pihole/FTL.log.1:1848:2025-05-31 21:22:45.504 AEST [1851M] INFO: ----------------------------> FTL crashed! <----------------------------
/var/log/pihole/FTL.log.1:1927:2025-05-31 21:22:52.133 AEST [1959M] INFO: ----------------------------> FTL crashed! <----------------------------
/var/log/pihole/FTL.log.1:2006:2025-05-31 21:22:58.880 AEST [1978M] INFO: ----------------------------> FTL crashed! <----------------------------
Thanks, but those are not full logs, only the result of the grep I've provided.
As explained, that is intended to help you find the start of a crash log, which you'd then could have used to extract the full log. 
But in the meantime, we've analysed crash logs from other posts like Pihole FTL fails because of a segmentation fault - #15 by DanSchaper, and Pi-hole's developers have been able to provide a fix.
Please try if updating your Pi-hole would also fix your issue.
updated and rebooted - repaired also same error
Core version is v6.1.1 (Latest: v6.1.1)
Web version is v6.2.1 (Latest: v6.2.1)
FTL version is v6.2.1 (Latest: v6.2.1)
orangepi@orangepizero2w:~$ sudo pihole enable
/opt/pihole/api.sh: line 25: utilsfile: readonly variable
Communication error. Is FTL running?
orangepi@orangepizero2w:~$
Ran fresh debug https://tricorder.pi-hole.net/jHXUpo7L/
Log details
sudo vi /var/log/pihole/FTL.log
2025-06-02 21:26:06.760 AEST [2969M] INFO: -> Cached DNS queries: 0
2025-06-02 21:26:06.760 AEST [2969M] INFO: -> Forwarded DNS queries: 0
2025-06-02 21:26:06.760 AEST [2969M] INFO: -> Blocked DNS queries: 0
2025-06-02 21:26:06.760 AEST [2969M] INFO: -> Unknown DNS queries: 0
2025-06-02 21:26:06.760 AEST [2969M] INFO: -> Unique domains: 0
2025-06-02 21:26:06.760 AEST [2969M] INFO: -> Unique clients: 0
2025-06-02 21:26:06.760 AEST [2969M] INFO: -> DNS cache records: 0
2025-06-02 21:26:06.760 AEST [2969M] INFO: -> Known forward destinations: 0
2025-06-02 21:26:07.125 AEST [2969M] INFO: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
2025-06-02 21:26:07.125 AEST [2969M] INFO: ----------------------------> FTL crashed! <----------------------------
2025-06-02 21:26:07.125 AEST [2969M] INFO: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
2025-06-02 21:26:07.125 AEST [2969M] INFO: Please report a bug at GitHub · Where software is built
2025-06-02 21:26:07.125 AEST [2969M] INFO: and include in your report already the following details:
2025-06-02 21:26:07.125 AEST [2969M] INFO: FTL has been running for 1 seconds
2025-06-02 21:26:07.125 AEST [2969M] INFO: FTL branch: master
2025-06-02 21:26:07.125 AEST [2969M] INFO: FTL version: v6.2.1
2025-06-02 21:26:07.125 AEST [2969M] INFO: FTL commit: d7ec012f
2025-06-02 21:26:07.125 AEST [2969M] INFO: FTL date: 2025-05-30 22:56:39 +0100
2025-06-02 21:26:07.125 AEST [2969M] INFO: FTL user: started as pihole, ended as pihole
2025-06-02 21:26:07.125 AEST [2969M] INFO: Compiled for linux/arm64/v8 (compiled on CI) using cc (Alpine 14.2.0) 14.2.0
2025-06-02 21:26:07.125 AEST [2969M] INFO: Process details: MID: 2969
2025-06-02 21:26:07.125 AEST [2969M] INFO: PID: 2969
2025-06-02 21:26:07.125 AEST [2969M] INFO: TID: 2969
2025-06-02 21:26:07.125 AEST [2969M] INFO: Name: pihole-FTL
2025-06-02 21:26:07.125 AEST [2969M] INFO: Received signal: Segmentation fault
2025-06-02 21:26:07.125 AEST [2969M] INFO: at address: 0xffffad23d4e3
2025-06-02 21:26:07.125 AEST [2969M] INFO: with code: SEGV_MAPERR (Address not mapped to object)
2025-06-02 21:26:07.125 AEST [2969M] INFO: !!! INFO: pihole-FTL has not been compiled with glibc/backtrace support, not generating one !!!
2025-06-02 21:26:07.125 AEST [2969M] INFO: ------ Listing content of directory /dev/shm ------
2025-06-02 21:26:07.126 AEST [2969M] INFO: File Mode User:Group Size Filename
2025-06-02 21:26:07.126 AEST [2969M] INFO: rwxrwxrwx root:root 360 .
2025-06-02 21:26:07.126 AEST [2969M] INFO: rwxr-xr-x root:root 4K ..
2025-06-02 21:26:07.126 AEST [2969M] INFO: rw------- pihole:pihole 786K FTL-2969-recycler
2025-06-02 21:26:07.126 AEST [2969M] INFO: rw------- pihole:pihole 4K FTL-2969-dns-cache-lookup
2025-06-02 21:26:07.126 AEST [2969M] INFO: rw------- pihole:pihole 4K FTL-2969-domains-lookup
2025-06-02 21:26:07.126 AEST [2969M] INFO: rw------- pihole:pihole 4K FTL-2969-clients-lookup
2025-06-02 21:26:07.127 AEST [2969M] INFO: rw------- pihole:pihole 569K FTL-2969-fifo-log
2025-06-02 21:26:07.127 AEST [2969M] INFO: rw------- pihole:pihole 4K FTL-2969-per-client-regex
2025-06-02 21:26:07.127 AEST [2969M] INFO: rw------- pihole:pihole 20K FTL-2969-dns-cache
2025-06-02 21:26:07.127 AEST [2969M] INFO: rw------- pihole:pihole 8K FTL-2969-overTime
2025-06-02 21:26:07.127 AEST [2969M] INFO: rw------- pihole:pihole 295K FTL-2969-queries
2025-06-02 21:26:07.127 AEST [2969M] INFO: rw------- pihole:pihole 29K FTL-2969-upstreams
2025-06-02 21:26:07.127 AEST [2969M] INFO: rw------- pihole:pihole 348K FTL-2969-clients
2025-06-02 21:26:07.128 AEST [2969M] INFO: rw------- pihole:pihole 4K FTL-2969-domains
2025-06-02 21:26:07.128 AEST [2969M] INFO: rw------- pihole:pihole 82K FTL-2969-strings
2025-06-02 21:26:07.128 AEST [2969M] INFO: rw------- pihole:pihole 144 FTL-2969-settings
2025-06-02 21:26:07.128 AEST [2969M] INFO: rw------- pihole:pihole 328 FTL-2969-counters
2025-06-02 21:26:07.128 AEST [2969M] INFO: rw------- pihole:pihole 88 FTL-2969-lock
2025-06-02 21:26:07.128 AEST [2969M] INFO: ---------------------------------------------------
2025-06-02 21:26:07.128 AEST [2969M] INFO: Please also include some lines from above the !!!!!!!!! header.
2025-06-02 21:26:07.128 AEST [2969M] INFO: Thank you for helping us to improve our FTL engine!
2025-06-02 21:26:07.128 AEST [2969M] INFO: PID file emptied
2025-06-02 21:26:07.158 AEST [2969M] INFO: ########## FTL terminated after 568ms (code 1)! ##########
hope I got it right 
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.