Pihole Docker unhealthy [solved]

Help docker
1

HI,
I have a Pihole on docker with this docker-compose:

docker-compose.yml 
version: "3"

services:
  pihole:
    container_name: pihole
    image: pihole/pihole:latest
    ports:
      - "53:53/tcp"
      - "53:53/udp"
      - "80:80/tcp"
      - "443:443/tcp"
    environment:
      TZ: 'Europa/Rome'
      DNSMASQ_LISTENING: 'all'
      WEBPASSWORD: '***'
      WEB_PORT: 8088
    volumes:
      - '/home/user/Docker_Containers/pihole/pihole:/etc/pihole'
      - '/home/user/Docker_Containers/pihole/dnsmasq.d:/etc/dnsmasq.d'
    network_mode: 'host'
    restart: unless-stopped

after a few minutes the docker acquires the status of "unhealthy" and I can't even reach pihole via the web interface.

...
  [✓] FTL is listening on port 53
     [✓] UDP (IPv4)
     [✓] TCP (IPv4)
     [✓] UDP (IPv6)
     [✓] TCP (IPv6)
  [✓] Pi-hole blocking is enabled
  Pi-hole version is v5.17.2 (Latest: v5.17.2)
  web version is v5.20.2 (Latest: v5.20.2)
  FTL version is v5.23 (Latest: v5.23)
  Container tag is: 2023.10.0
Stopping pihole-FTL
pihole-FTL: no process found

in the web interface, this error message appears in the settings:

There was a problem applying your settings.
Debugging information:
PHP error (2): fsockopen(): unable to connect to 127.0.0.1:4711 (Connection refused) in /var/www/html/admin/scripts/pi-hole/php/FTL.php:47

This error message appears in the top left corner:

:red_circle: DNS service not running

but if I try to start the service again the error appears again

Furthermore, if it can be useful, I load a part of the FTL.log file present in the container:

/var/log/pihole/FTL.log 
[2023-11-18 14:58:27.510 2507M] Resizing "FTL-clients" from 21504000 to (32128 * 672) == 21590016 (/dev/shm: 27.1MB used, 67.1MB total, FTL uses 27.1MB)
[2023-11-18 14:58:32.802 2507M] Resizing "FTL-clients" from 21590016 to (32256 * 672) == 21676032 (/dev/shm: 27.2MB used, 67.1MB total, FTL uses 27.2MB)
[2023-11-18 14:58:36.564 2507M] Resizing "FTL-clients" from 21676032 to (32384 * 672) == 21762048 (/dev/shm: 27.3MB used, 67.1MB total, FTL uses 27.3MB)
[2023-11-18 14:58:42.112 2507M] Resizing "FTL-clients" from 21762048 to (32512 * 672) == 21848064 (/dev/shm: 27.4MB used, 67.1MB total, FTL uses 27.4MB)
[2023-11-18 14:58:44.309 2507M] Imported 81531 queries from the long-term database
[2023-11-18 14:58:44.311 2507M]  -> Total DNS queries: 81531
[2023-11-18 14:58:44.311 2507M]  -> Cached DNS queries: 28
[2023-11-18 14:58:44.311 2507M]  -> Forwarded DNS queries: 22989
[2023-11-18 14:58:44.311 2507M]  -> Blocked DNS queries: 136
[2023-11-18 14:58:44.311 2507M]  -> Unknown DNS queries: 0
[2023-11-18 14:58:44.311 2507M]  -> Unique domains: 3460
[2023-11-18 14:58:44.311 2507M]  -> Unique clients: 32464
[2023-11-18 14:58:44.311 2507M]  -> Known forward destinations: 2
[2023-11-18 14:58:44.311 2507M] Successfully accessed setupVars.conf
[2023-11-18 14:58:44.315 2507M] listening on 0.0.0.0 port 53
[2023-11-18 14:58:44.316 2507M] listening on :: port 53
[2023-11-18 14:58:44.318 2507M] PID of FTL process: 2507
[2023-11-18 14:58:44.318 2507M] Listening on port 4711 for incoming IPv4 telnet connections
[2023-11-18 14:58:44.319 2507M] Listening on port 4711 for incoming IPv6 telnet connections
[2023-11-18 14:58:44.321 2507M] Listening on port 4711 for incoming socket telnet connections
[2023-11-18 14:58:44.322 2507M] INFO: FTL is running as user pihole (UID 999)
[2023-11-18 14:58:44.323 2507M] Reloading DNS cache
[2023-11-18 14:58:44.440 2507/T2901] Compiled 0 whitelist and 0 blacklist regex filters for 32468 clients in 7.8 msec
[2023-11-18 14:58:44.441 2507/T2901] Blocking status is enabled
[2023-11-18 14:58:44.873 2507M] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[2023-11-18 14:58:44.873 2507M] ---------------------------->  FTL crashed!  <----------------------------
[2023-11-18 14:58:44.873 2507M] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[2023-11-18 14:58:44.873 2507M] Please report a bug at https://github.com/pi-hole/FTL/issues
[2023-11-18 14:58:44.873 2507M] and include in your report already the following details:
[2023-11-18 14:58:44.873 2507M] FTL has been running for 833 seconds
[2023-11-18 14:58:44.873 2507M] FTL branch: master
[2023-11-18 14:58:44.873 2507M] FTL version: v5.23
[2023-11-18 14:58:44.873 2507M] FTL commit: d201776e
[2023-11-18 14:58:44.873 2507M] FTL date: 2023-05-28 11:55:26 +0100
[2023-11-18 14:58:44.873 2507M] FTL user: started as pihole, ended as pihole
[2023-11-18 14:58:44.873 2507M] Compiled for aarch64 (compiled on CI) using aarch64-linux-gnu-gcc (Debian 8.3.0-2) 8.3.0
[2023-11-18 14:58:44.873 2507M] Process details: MID: 2507
[2023-11-18 14:58:44.874 2507M]                  PID: 2507
[2023-11-18 14:58:44.874 2507M]                  TID: 2507
[2023-11-18 14:58:44.874 2507M]                  Name: pihole-FTL
[2023-11-18 14:58:44.874 2507M] Received signal: Segmentation fault
[2023-11-18 14:58:44.874 2507M]      at address: 0xbebe5865b1be5865
[2023-11-18 14:58:44.874 2507M]      with code:  SEGV_MAPERR (Address not mapped to object)
[2023-11-18 14:58:44.880 2507M] Backtrace:
[2023-11-18 14:58:44.881 2507M] B[0000]: /usr/bin/pihole-FTL(generate_backtrace+0x38) [0x557a95b818]
[2023-11-18 14:58:45.144 2507M] L[0000]: /__w/FTL/FTL/src/signals.c:98
[2023-11-18 14:58:45.148 2507M] B[0001]: /usr/bin/pihole-FTL(+0x5bcec) [0x557a95bcec]
[2023-11-18 14:58:45.191 2507M] L[0001]: /__w/FTL/FTL/src/signals.c:242
[2023-11-18 14:58:45.196 2507M] B[0002]: linux-vdso.so.1(__kernel_rt_sigreturn+0) [0x7fbdfbd7a8]
[2023-11-18 14:58:45.196 2507M] B[0003]: /usr/bin/pihole-FTL(+0x125d78) [0x557aa25d78]
[2023-11-18 14:58:45.417 2507M] L[0003]: /__w/FTL/FTL/src/database/sqlite3.c:88298
[2023-11-18 14:58:45.438 2507M] B[0004]: /usr/bin/pihole-FTL(sqlite3_bind_text+0x30) [0x557aa3d718]
[2023-11-18 14:58:45.626 2507M] L[0004]: /__w/FTL/FTL/src/database/sqlite3.c:89760
[2023-11-18 14:58:45.646 2507M] B[0005]: /usr/bin/pihole-FTL(+0x64c24) [0x557a964c24]
[2023-11-18 14:58:45.677 2507M] L[0005]: /__w/FTL/FTL/src/database/gravity-db.c:1198
[2023-11-18 14:58:45.681 2507M] B[0006]: /usr/bin/pihole-FTL(+0x4a598) [0x557a94a598]
[2023-11-18 14:58:45.714 2507M] L[0006]: /__w/FTL/FTL/src/dnsmasq_interface.c:1429
[2023-11-18 14:58:45.717 2507M] B[0007]: /usr/bin/pihole-FTL(_FTL_new_query+0x98c) [0x557a94de7c]
[2023-11-18 14:58:45.750 2507M] L[0007]: /__w/FTL/FTL/src/dnsmasq_interface.c:683 (discriminator 1)
[2023-11-18 14:58:45.754 2507M] B[0008]: /usr/bin/pihole-FTL(receive_query+0x424) [0x557a98f874]
[2023-11-18 14:58:45.790 2507M] L[0008]: /__w/FTL/FTL/src/dnsmasq/forward.c:1770 (discriminator 4)
[2023-11-18 14:58:45.794 2507M] B[0009]: /usr/bin/pihole-FTL(+0x803d4) [0x557a9803d4]
[2023-11-18 14:58:45.829 2507M] L[0009]: /__w/FTL/FTL/src/dnsmasq/dnsmasq.c:1868
[2023-11-18 14:58:45.833 2507M] B[0010]: /usr/bin/pihole-FTL(main_dnsmasq+0xfc0) [0x557a981fd0]
[2023-11-18 14:58:45.868 2507M] L[0010]: /__w/FTL/FTL/src/dnsmasq/dnsmasq.c:1278
[2023-11-18 14:58:45.873 2507M] B[0011]: /usr/bin/pihole-FTL(main+0x100) [0x557a942180]
[2023-11-18 14:58:45.905 2507M] L[0011]: /__w/FTL/FTL/src/main.c:118
[2023-11-18 14:58:45.909 2507M] B[0012]: /lib/aarch64-linux-gnu/libc.so.6(__libc_start_main+0xe8) [0x7fbdd45e18]
[2023-11-18 14:58:45.909 2507M] B[0013]: /usr/bin/pihole-FTL(+0x42648) [0x557a942648]
[2023-11-18 14:58:45.958 2507M] L[0013]: ??:?
[2023-11-18 14:58:45.967 2507M] ------ Listing content of directory /dev/shm ------
[2023-11-18 14:58:45.967 2507M] File Mode User:Group      Size  Filename
[2023-11-18 14:58:45.968 2507M] rwxrwxrwx root:root       260  .
[2023-11-18 14:58:45.968 2507M] rwxr-xr-x root:root       320  ..
[2023-11-18 14:58:45.968 2507M] rw------- pihole:pihole     4K  FTL-per-client-regex
[2023-11-18 14:58:45.968 2507M] rw------- pihole:pihole     4K  FTL-dns-cache
[2023-11-18 14:58:45.968 2507M] rw------- pihole:pihole     8K  FTL-overTime
[2023-11-18 14:58:45.968 2507M] rw------- pihole:pihole     5M  FTL-queries
[2023-11-18 14:58:45.969 2507M] rw------- pihole:pihole   315K  FTL-upstreams
[2023-11-18 14:58:45.969 2507M] rw------- pihole:pihole    22M  FTL-clients
[2023-11-18 14:58:45.969 2507M] rw------- pihole:pihole    86K  FTL-domains
[2023-11-18 14:58:45.969 2507M] rw------- pihole:pihole   614K  FTL-strings
[2023-11-18 14:58:45.969 2507M] rw------- pihole:pihole    16  FTL-settings
[2023-11-18 14:58:45.969 2507M] rw------- pihole:pihole   248  FTL-counters
[2023-11-18 14:58:45.969 2507M] rw------- pihole:pihole   104  FTL-lock
[2023-11-18 14:58:45.969 2507M] ---------------------------------------------------
[2023-11-18 14:58:45.970 2507M] Please also include some lines from above the !!!!!!!!! header.
[2023-11-18 14:58:45.970 2507M] Thank you for helping us to improve our FTL engine!
[2023-11-18 14:58:45.970 2507M] Waiting for threads to join
[2023-11-18 14:58:45.970 2507M] Thread database (0) is idle, terminating it.
[2023-11-18 14:58:45.970 2507M] Thread housekeeper (1) is idle, terminating it.
[2023-11-18 14:58:45.970 2507M] Thread DNS client (2) is idle, terminating it.
[2023-11-18 14:58:45.970 2507M] All threads joined
[2023-11-18 14:58:45.970 2507M] Joining API worker thread 0
[2023-11-18 14:58:45.970 2507M] Joining API worker thread 1
[2023-11-18 14:58:45.971 2507M] Joining API worker thread 2
[2023-11-18 14:58:45.971 2507M] Joining API worker thread 3
[2023-11-18 14:58:45.971 2507M] Joining API worker thread 4
[2023-11-18 17:17:41.300 242M] Using log file /var/log/pihole/FTL.log
[2023-11-18 17:17:41.300 242M] ########## FTL started on raspberrypi! ##########
[2023-11-18 17:17:41.300 242M] FTL branch: master
[2023-11-18 17:17:41.300 242M] FTL version: v5.23
[2023-11-18 17:17:41.300 242M] FTL commit: d201776e
[2023-11-18 17:17:41.300 242M] FTL date: 2023-05-28 11:55:26 +0100
[2023-11-18 17:17:41.300 242M] FTL user: pihole
[2023-11-18 17:17:41.300 242M] Compiled for aarch64 (compiled on CI) using aarch64-linux-gnu-gcc (Debian 8.3.0-2) 8.3.0
[2023-11-18 17:17:41.301 242M] Starting config file parsing (/etc/pihole/pihole-FTL.conf)

then I tried to create the docker with the same docker-compose, but leaving out the creation of the volumes and everything works perfectly, but this means that every time I delete and recreate the docker I lose all the data.

2

I'm not sure what is causing the crash, but if you think it's related to volumes, you can try to use a different type of volume.

You are currently using bind mounts. You can try to use named volumes.

You can create the named volumes before running your compose file using the command docker volume create or you can create the named volume in the compose file (see the example).

Does it work with named volumes?

6

I created the 'pihole' volume which I now see located in: /var/lib/docker/volumes/pihole/_data/
I can't figure out how to modify my docker-compose:
How do I replace the volume section?

edit:
I try this configuration of compose created 2 volumes pihole and dnsmasq:

...
        # Volumes store your data between container upgrades [LOCAL PATH]:[DOCKER PATH]
    volumes:
      - 'pihole:/etc/pihole'
      - 'dnsmasq:/etc/dnsmasq.d'
    network_mode: 'host'
    restart: unless-stopped

volumes:
  pihole:
    external: true
  dnsmasq:
    external: true

but the docker is very slow

8

This is a crash deep down in the SQLite3 library where it is called with an apparently completely random (invalid) pointer. I have not seen this before nor have I seen similar reports anywhere.

As it seems to be reproducible, it may be worth trying to add

DEBUG_ALL=true

to the file /etc/pihole/pihole-FTL.conf (create if it does not exist) and restarting the container.

Next time the crash happens, please include again the crash report from /var/log/pihole/FTL.log with some extra lines of context above the !!!!!! header. This may help us getting a better picture of where/why exactly the issue happens.

9

this is the log file:
FTL.txt (92.7 KB)

this is first 1.000 lines of the log file.
the file is very big: 1.490.243 lines (I have rename the file before to restart the container :exploding_head:)
log file is 138MB

10

I know it can get pretty massive, but we are looking for lines immediately above lines like:

This is not included in the file you uploaded.

11

I find it in the previus file renamed by me:

TFL.log 
[2023-11-21 09:19:01.702 388M] Opening FTL database in getNameFromIP() (/__w/FTL/FTL/src/database/network-table.c:2011)
[2023-11-21 09:19:01.708 388M]  ---> not found
[2023-11-21 09:19:01.708 388M] Closing FTL database in getNameFromIP() (/__w/FTL/FTL/src/database/network-table.c:2137)
[2023-11-21 09:19:01.709 388M] --> No result.
[2023-11-21 09:19:01.709 388M] Querying gravity database for interface of 45.225.73.193...
[2023-11-21 09:19:01.709 388M] Opening FTL database in getIfaceFromIP() (/__w/FTL/FTL/src/database/network-table.c:2153)
[2023-11-21 09:19:01.709 388M] getDatabaseHostname(): "SELECT interface FROM network JOIN network_addresses ON network_addresses.network_id = network.id WHERE network_addr>
[2023-11-21 09:19:01.710 388M] Found database interface 45.225.73.193 -> eth0
[2023-11-21 09:19:01.710 388M] Closing FTL database in getIfaceFromIP() (/__w/FTL/FTL/src/database/network-table.c:2223)
[2023-11-21 09:19:01.710 388M] Querying client table for interface :eth0
[2023-11-21 09:19:01.710 388M] --> There is no record for interface :eth0 in the client table
[2023-11-21 09:19:01.710 388M] Gravity database: Client 45.225.73.193 not found. Using default group.

[2023-11-21 09:19:01.710 388M] Adding "0" (len 2) to buffer. next_str_pos is 217743
[2023-11-21 09:19:01.710 388M] gravityDB_open(): Preparing vw_whitelist statement for client 45.225.73.193
[2023-11-21 09:19:01.710 388M] get_client_querystr: SELECT id from vw_whitelist WHERE domain = ? AND group_id IN (0);
[2023-11-21 09:19:01.710 388M] Setting sqlite3_stmt** 0x7f740264f0[9441] <-- 0x559c2c9d68
[2023-11-21 09:19:01.710 388M] gravityDB_open(): Preparing vw_gravity statement for client 45.225.73.193
[2023-11-21 09:19:01.711 388M] get_client_querystr: SELECT domain from vw_gravity WHERE domain = ? AND group_id IN (0);
[2023-11-21 09:19:01.711 388M] Setting sqlite3_stmt** 0x7f74031ef0[9441] <-- 0x559c2c8fa8
[2023-11-21 09:19:01.711 388M] gravityDB_open(): Preparing vw_blacklist statement for client 45.225.73.193
[2023-11-21 09:19:01.711 388M] get_client_querystr: SELECT id from vw_blacklist WHERE domain = ? AND group_id IN (0);
[2023-11-21 09:19:01.711 388M] Setting sqlite3_stmt** 0x7f7402bb00[9441] <-- 0x559c2ca048
[2023-11-21 09:19:01.711 388M] Getting sqlite3_stmt** 0x7f740264f0[9441] --> 0x559c2c9d68
[2023-11-21 09:19:01.711 388M] domain_in_list("cisco.com", 0x559c2c9d68, whitelist): -1
[2023-11-21 09:19:01.711 388M] Getting sqlite3_stmt** 0x7f7402bb00[9441] --> 0x559c2ca048
[2023-11-21 09:19:01.711 388M] domain_in_list("cisco.com", 0x559c2ca048, blacklist): -1
[2023-11-21 09:19:01.711 388M] Getting sqlite3_stmt** 0x7f74031ef0[9441] --> 0x559c2c8fa8
[2023-11-21 09:19:01.712 388M] domain_in_list("cisco.com", 0x559c2c8fa8, gravity): -1
[2023-11-21 09:19:01.712 388M] Checking if "cisco.com" is in gravity: no
[2023-11-21 09:19:01.712 388M] DNS cache: 45.225.73.193/cisco.com is not blocked
[2023-11-21 09:19:01.712 388M] Removed lock in _FTL_new_query() (/__w/FTL/FTL/src/dnsmasq_interface.c:842)
[2023-11-21 09:19:01.712 388M] Waiting for SHM lock in FTL_query_in_progress() (/__w/FTL/FTL/src/dnsmasq_interface.c:3247)
[2023-11-21 09:19:01.712 388/T562] Obtained SHM lock for add_FTL_clients_to_network_table() (/__w/FTL/FTL/src/database/network-table.c:778)
[2023-11-21 09:19:01.712 388/T562] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[2023-11-21 09:19:01.712 388/T564]  ---> "45-165-143-20.v1bandalarga.com.br" (found externally)
[2023-11-21 09:19:01.712 388/T562] ---------------------------->  FTL crashed!  <----------------------------
[2023-11-21 09:19:01.712 388/T564] Waiting for SHM lock in resolveAndAddHostname() (/__w/FTL/FTL/src/resolve.c:364)
[2023-11-21 09:19:01.712 388/T562] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[2023-11-21 09:19:01.712 388/T562] Please report a bug at https://github.com/pi-hole/FTL/issues
[2023-11-21 09:19:01.712 388/T562] and include in your report already the following details:
[2023-11-21 09:19:01.712 388/T562] FTL has been running for 1058 seconds
[2023-11-21 09:19:01.712 388/T562] FTL branch: master
[2023-11-21 09:19:01.712 388/T562] FTL version: v5.23
[2023-11-21 09:19:01.712 388/T562] FTL commit: d201776e
[2023-11-21 09:19:01.712 388/T562] FTL date: 2023-05-28 11:55:26 +0100
[2023-11-21 09:19:01.713 388/T562] FTL user: started as pihole, ended as pihole
[2023-11-21 09:19:01.713 388/T562] Compiled for aarch64 (compiled on CI) using aarch64-linux-gnu-gcc (Debian 8.3.0-2) 8.3.0
[2023-11-21 09:19:01.713 388/T562] Process details: MID: 388
[2023-11-21 09:19:01.713 388/T562]                  PID: 388
[2023-11-21 09:19:01.713 388/T562]                  TID: 562
[2023-11-21 09:19:01.713 388/T562]                  Name: database
[2023-11-21 09:19:01.713 388/T562] Received signal: Segmentation fault
[2023-11-21 09:19:01.713 388/T562]      at address: 0x7f837ff000
[2023-11-21 09:19:01.713 388/T562]      with code:  SEGV_ACCERR (Invalid permissions for mapped object)

the file with more lines befor error:
FTL.txt (25.7 KB)

12

Okay, thanks. Now I am a bit confused:

is not the same time as in your uploaded file

where we have

[2023-11-21 09:32:37.860 246M] ########## FTL started on raspberrypi! ##########

The currently available information points to

but it isn't immediately clear where inhere it could crash.

Anyway, I also see

which is pretty good because it means we can add a debugger to FTL to precisely see where the crash is triggered. Please follow the instructions on gdb - Pi-hole documentation. Hopefully, the generated backtrace will show us everything we need for further debugging.

13

I have this error:

gbd error

root@raspberrypi:/# echo "handle SIGHUP nostop SIGPIPE nostop SIGTERM nostop SIG32 nostop SIG34 nostop SIG35 nostop" | sudo tee /root/.gdbinit
handle SIGHUP nostop SIGPIPE nostop SIGTERM nostop SIG32 nostop SIG34 nostop SIG35 nostop
root@raspberrypi:/# sudo gdb -p $(pidof pihole-FTL)
GNU gdb (Debian 10.1-1.7) 10.1.90.20210103-git
Copyright (C) 2021 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "aarch64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
https://www.gnu.org/software/gdb/bugs/.
Find the GDB manual and other documentation resources online at:
http://www.gnu.org/software/gdb/documentation/.

For help, type "help".
Type "apropos word" to search for commands related to "word".
Attaching to process 275
ptrace: Operation not permitted.
(gdb) continue
The program is not being run.
(gdb)

14

Sorry, the documentation does not take docker into account. You need to run gdb in the container, attaching the debugger from the outside isn't possible.

So something like:

# find your container ID
sudo docker ps
# list of your containers - let's say your container ID is 1234567890

docker exec -i -t 1234567890 /bin/bash

there you can run the commands from the documentation.

15

I run the istruction on the console of the docker from portainer:

Immagine 2023-11-21 124847
Immagine 2023-11-21 124847753×646 25.7 KB

and in the console of docker with

docker exec -i -t [DOKER_ID] /bin/bash

Immagine 2023-11-21 125306

16

Can you help me with this error? thank for all. :+1:

17

Sorry, life kept me busy so I haven't had time to check back on this.

Unfortunately, I am unfamiliar with portainer, but I did only see now the

prace: Operation not permitted

Please add this to my docker-compose.yml file:

cap_add:
    - SYS_PTRACE

Or include --cap-add=SYS_PTRACE in the docker command from the CLI.

It may also be that we need --security-opt seccomp=unconfined in addition but I didn't find a clear answer to this online. Lots of mentioning but nothing really precise about it.

18

don't worry! you give me a very big help!
I try with this...

19

Screenshot 2023-11-22 alle 22.08.33
Screenshot 2023-11-22 alle 22.08.331416×1040 122 KB

now it's running well?

20

Yes, this looks great! Now we wait.

21

Is this our problem?

Thread 17 "database" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7f5effd1e0 (LWP 293)]
0x0000005571e0a4b8 in add_FTL_clients_to_network_table (additional_entries=<synthetic pointer>, now=1700687717, client_status=<optimized out>, db=0x7f40033b38) at /__w/FTL/FTL/src/database/network-table.c:803
803     /__w/FTL/FTL/src/database/network-table.c: No such file or directory.```
22

Possibly, could you enter where and copy the result here?

23

for you:

result

#0 syscall () at ../sysdeps/unix/sysv/linux/aarch64/syscall.S:39
#1 0x0000005571de75f0 in FTL_gettid () at /__w/FTL/FTL/src/daemon.c:211
#2 0x0000005571dfb650 in is_our_lock () at /__w/FTL/FTL/src/shmem.c:465
#3 is_our_lock () at /__w/FTL/FTL/src/shmem.c:462
#4 _getDNSCache (cacheID=cacheID@entry=4825, checkMagic=checkMagic@entry=true, line=line@entry=1268, func=func@entry=0x557201bcd8 <FUNCTION.15060> "_FTL_check_blocking",
file=file@entry=0x557201be48 "/__w/FTL/FTL/src/dnsmasq_interface.c") at /__w/FTL/FTL/src/shmem.c:1148
#5 0x0000005571de8480 in _findCacheID (domainID=domainID@entry=0, clientID=clientID@entry=14391, query_type=TYPE_TXT, create_new=create_new@entry=true,
func=func@entry=0x557201bcd8 <FUNCTION.15060> "_FTL_check_blocking", line=line@entry=1268, file=file@entry=0x557201be48 "/__w/FTL/FTL/src/dnsmasq_interface.c") at /__w/FTL/FTL/src/datastructure.c:328
#6 0x0000005571dea380 in _FTL_check_blocking (queryID=queryID@entry=15408, domainID=domainID@entry=0, clientID=clientID@entry=14391, line=, file=)
at /__w/FTL/FTL/src/dnsmasq_interface.c:1268
#7 0x0000005571dede7c in _FTL_check_blocking (file=0x557201be48 "/__w/FTL/FTL/src/dnsmasq_interface.c", line=836, clientID=14391, domainID=0, queryID=15408) at /__w/FTL/FTL/src/dnsmasq_interface.c:683
#8 _FTL_new_query (flags=flags@entry=524296, name=, addr=addr@entry=0x7fc2f03218, arg=0x5572020690 "query", qtype=, id=, proto=proto@entry=UDP,
file=file@entry=0x557202ca30 "/__w/FTL/FTL/src/dnsmasq/forward.c", line=line@entry=1771) at /__w/FTL/FTL/src/dnsmasq_interface.c:836
#9 0x0000005571e2f874 in receive_query (listen=listen@entry=0x55b124c760, now=now@entry=1700688827) at /__w/FTL/FTL/src/dnsmasq/forward.c:1770
#10 0x0000005571e203d4 in check_dns_listeners (now=now@entry=1700688827) at /__w/FTL/FTL/src/dnsmasq/dnsmasq.c:1868
#11 0x0000005571e21fd0 in main_dnsmasq (argc=, argv=) at /__w/FTL/FTL/src/dnsmasq/dnsmasq.c:1275
#12 0x0000005571de2180 in main (argc=, argv=0x7fc2f036c8) at /__w/FTL/FTL/src/main.c:116

24

It seems this is the backtrace of an unrelated thread, please try

thread 17
where