Pi-Hole v6 Docker logs

Pi-Hole v6 Docker logs on OCI Ampere aarch64 VM.
 avatar
unknown
plain_text
3 days ago
39 kB
17
No Index
❯ docker container logs pihole
  [i] Setting up user & group for the pihole user
  [i] Changing ID for user: pihole (1000 => 1002)
  [i] Changing ID for group: pihole (1000 => 1002)

  [i] Starting FTL configuration
  [i] Assigning password defined by Environment Variable
  [i] Starting crond for scheduled scripts. Randomizing times for gravity and update checker

  [i] Ensuring logrotate script exists in /etc/pihole

  [i] Gravity migration checks
  [i] No adlist file found, creating one with a default blocklist
  [i] /etc/pihole/gravity.db does not exist (Likely due to a fresh volume). This is a required file for Pi-hole to operate.
  [i] Gravity will now be run to create the database
  [✓] DNS resolution is available

  [✗] Migrating the list's cache directory to new location
  [i] Creating new gravity database
  [i] Migrating content of /etc/pihole/adlists.list into new database
  [i] Neutrino emissions detected...

  [✓] Preparing new gravity database
  [✓] Creating new gravity databases
  [✓] Pulling blocklist source list into range
  [i] Using libz compression

  [i] Target: https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts
  [✓] Status: Retrieval successful
  [✓] Parsed 230047 exact domains and 0 ABP-style domains (blocking, ignored 1 non-domain entries)
      Sample of non-domain entries:
        - fe80::1%lo0

  [✓] Building tree
  [i] Number of gravity domains: 230047 (230047 unique domains)
  [i] Number of exact denied domains: 0
  [i] Number of regex denied filters: 0
  [i] Number of exact allowed domains: 0
  [i] Number of regex allowed filters: 0
  [✓] Optimizing database
  [✓] Swapping databases
  [✓] The old database remains available
  [✓] Cleaning up stray matter

  [✓] Done.

  [i] pihole-FTL pre-start checks
  [i] Setting capabilities on pihole-FTL where possible
  [i] Applying the following caps to pihole-FTL:
        * CAP_CHOWN
        * CAP_NET_BIND_SERVICE
        * CAP_NET_RAW
        * CAP_NET_ADMIN
        * CAP_SYS_NICE
        * CAP_SYS_TIME

chmod: cannot access '/etc/pihole/versions': No such file or directory
  [i] Starting pihole-FTL (no-daemon) as pihole

  [i] Version info:
      Core version is v6.1.4 (Latest: v6.1.4)
      Web version is v6.2.1 (Latest: v6.2.1)
      FTL version is v6.2.3 (Latest: v6.2.3)

2025-08-18 17:06:43.326 UTC [171M] INFO: ########## FTL started on cloud1! ##########
2025-08-18 17:06:43.326 UTC [171M] INFO: FTL branch: master
2025-08-18 17:06:43.326 UTC [171M] INFO: FTL version: v6.2.3
2025-08-18 17:06:43.326 UTC [171M] INFO: FTL commit: 88737f62
2025-08-18 17:06:43.326 UTC [171M] INFO: FTL date: 2025-06-10 20:44:58 +0200
2025-08-18 17:06:43.326 UTC [171M] INFO: FTL user: pihole
2025-08-18 17:06:43.326 UTC [171M] INFO: Compiled for linux/arm64/v8 (compiled on CI) using cc (Alpine 14.2.0) 14.2.0
2025-08-18 17:06:43.617 UTC [171M] INFO: 7 FTLCONF environment variables found (7 used, 0 invalid, 0 ignored)
2025-08-18 17:06:43.617 UTC [171M] INFO:    [✓] FTLCONF_dns_listeningMode is used
2025-08-18 17:06:43.617 UTC [171M] INFO:    [✓] FTLCONF_dns_domain is used
2025-08-18 17:06:43.617 UTC [171M] INFO:    [✓] FTLCONF_webserver_api_password is used
2025-08-18 17:06:43.617 UTC [171M] INFO:    [✓] FTLCONF_webserver_port is used
2025-08-18 17:06:43.617 UTC [171M] INFO:    [✓] FTLCONF_dns_upstreams is used
2025-08-18 17:06:43.617 UTC [171M] INFO:    [✓] FTLCONF_dhcp_active is used
2025-08-18 17:06:43.617 UTC [171M] INFO:    [✓] FTLCONF_misc_dnsmasq_lines is used
2025-08-18 17:06:43.618 UTC [171M] INFO: Wrote config file:
2025-08-18 17:06:43.618 UTC [171M] INFO:  - 155 total entries
2025-08-18 17:06:43.618 UTC [171M] INFO:  - 148 entries are default
2025-08-18 17:06:43.618 UTC [171M] INFO:  - 7 entries are modified
2025-08-18 17:06:43.618 UTC [171M] INFO:  - 5 entries are forced through environment
2025-08-18 17:06:43.619 UTC [171M] INFO: Config file written to /etc/pihole/pihole.toml
2025-08-18 17:06:43.619 UTC [171M] INFO: Parsed config file /etc/pihole/pihole.toml successfully
2025-08-18 17:06:43.619 UTC [171M] INFO: PID file does not exist or not readable
2025-08-18 17:06:43.619 UTC [171M] INFO: No other running FTL process found.
2025-08-18 17:06:43.621 UTC [171M] INFO: PID of FTL process: 171
2025-08-18 17:06:43.626 UTC [171M] INFO: listening on 0.0.0.0 port 53
2025-08-18 17:06:43.626 UTC [171M] INFO: listening on :: port 53
2025-08-18 17:06:43.626 UTC [171M] INFO: PID of FTL process: 171
2025-08-18 17:06:43.628 UTC [171M] WARNING: No database file found, creating new (empty) database
2025-08-18 17:06:43.646 UTC [171M] INFO: Database version is 1
2025-08-18 17:06:43.646 UTC [171M] INFO: Updating long-term database to version 2
2025-08-18 17:06:43.649 UTC [171M] INFO: Updating long-term database to version 3
2025-08-18 17:06:43.652 UTC [171M] INFO: Updating long-term database to version 4
2025-08-18 17:06:43.655 UTC [171M] INFO: Updating long-term database to version 5
2025-08-18 17:06:43.659 UTC [171M] INFO: Updating long-term database to version 6
2025-08-18 17:06:43.662 UTC [171M] INFO: Updating long-term database to version 7
2025-08-18 17:06:43.664 UTC [171M] INFO: Updating long-term database to version 8
2025-08-18 17:06:43.669 UTC [171M] INFO: Updating long-term database to version 9
2025-08-18 17:06:43.672 UTC [171M] INFO: Updating long-term database to version 10
2025-08-18 17:06:43.677 UTC [171M] INFO: Updating long-term database to version 11
2025-08-18 17:06:43.681 UTC [171M] INFO: Updating long-term database to version 12
2025-08-18 17:06:43.684 UTC [171M] INFO: Updating long-term database to version 13
2025-08-18 17:06:43.687 UTC [171M] INFO: Updating long-term database to version 14
2025-08-18 17:06:43.690 UTC [171M] INFO: Updating long-term database to version 15
2025-08-18 17:06:43.694 UTC [171M] INFO: Updating long-term database to version 16
2025-08-18 17:06:43.697 UTC [171M] INFO: Updating long-term database to version 17
2025-08-18 17:06:43.700 UTC [171M] INFO: Updating long-term database to version 18
2025-08-18 17:06:43.703 UTC [171M] INFO: Updating long-term database to version 19
2025-08-18 17:06:43.706 UTC [171M] INFO: Updating long-term database to version 20
2025-08-18 17:06:43.712 UTC [171M] INFO: Updating long-term database to version 21
2025-08-18 17:06:43.715 UTC [171M] INFO: Database successfully initialized
2025-08-18 17:06:43.720 UTC [171M] INFO: Imported 0 queries from the on-disk database (it has 0 rows)
2025-08-18 17:06:43.720 UTC [171M] INFO: Parsing queries in database
2025-08-18 17:06:43.720 UTC [171M] INFO: Imported 0 queries from the long-term database
2025-08-18 17:06:43.720 UTC [171M] INFO:  -> Total DNS queries: 0
2025-08-18 17:06:43.720 UTC [171M] INFO:  -> Cached DNS queries: 0
2025-08-18 17:06:43.720 UTC [171M] INFO:  -> Forwarded DNS queries: 0
2025-08-18 17:06:43.720 UTC [171M] INFO:  -> Blocked DNS queries: 0
2025-08-18 17:06:43.720 UTC [171M] INFO:  -> Unknown DNS queries: 0
2025-08-18 17:06:43.720 UTC [171M] INFO:  -> Unique domains: 0
2025-08-18 17:06:43.720 UTC [171M] INFO:  -> Unique clients: 0
2025-08-18 17:06:43.720 UTC [171M] INFO:  -> DNS cache records: 0
2025-08-18 17:06:43.720 UTC [171M] INFO:  -> Known forward destinations: 0
2025-08-18 17:06:43.814 UTC [171M] INFO: FTL is running as user pihole (UID 1002)
2025-08-18 17:06:43.817 UTC [171M] INFO: Created SSL/TLS certificate for pi.hole at /etc/pihole/tls.pem
2025-08-18 17:06:43.817 UTC [171M] INFO: Reading certificate from /etc/pihole/tls.pem ...
2025-08-18 17:06:43.818 UTC [171M] INFO: Using SSL/TLS certificate file /etc/pihole/tls.pem
2025-08-18 17:06:43.819 UTC [171M] INFO: Web server ports:
2025-08-18 17:06:43.819 UTC [171M] INFO:   - 0.0.0.0:8080 (HTTP, IPv4, OK)
2025-08-18 17:06:43.819 UTC [171M] INFO:   - 0.0.0.0:8443 (HTTPS, IPv4, OK)
2025-08-18 17:06:43.819 UTC [171M] INFO: Restored 0 API sessions from the database
2025-08-18 17:06:43.821 UTC [171M] INFO: Blocking status is enabled
2025-08-18 17:06:43.915 UTC [171/T173] INFO: Compiled 0 allow and 0 deny regex for 8 clients in 0.1 msec
2025-08-18 17:06:48.378 UTC [171/T172] INFO: Received 8/8 valid NTP replies from pool.ntp.org
2025-08-18 17:06:48.378 UTC [171/T172] INFO: Time offset: -1.554489e-01 ms (excluded 1 outliers)
2025-08-18 17:06:48.378 UTC [171/T172] INFO: Round-trip delay: 6.598827e+01 ms (excluded 1 outliers)
2025-08-18 17:06:48.378 UTC [171/T276] INFO: NTP server listening on 0.0.0.0:123 (IPv4)
2025-08-18 17:06:48.378 UTC [171/T277] INFO: NTP server listening on :::123 (IPv6)
2025-08-18 17:06:50.944 UTC [171/T175] ERROR: Cannot receive UDP DNS reply: Timeout - no response from upstream DNS server
2025-08-18 17:06:50.944 UTC [171/T175] INFO: Tried to resolve PTR "16.169.60.187.in-addr.arpa" on 127.0.0.1#53 (UDP)
2025-08-18 17:07:13.951 UTC [171/T278] INFO: Wrote config file:
2025-08-18 17:07:13.951 UTC [171/T278] INFO:  - 155 total entries
2025-08-18 17:07:13.951 UTC [171/T278] INFO:  - 144 entries are default
2025-08-18 17:07:13.951 UTC [171/T278] INFO:  - 11 entries are modified
2025-08-18 17:07:13.951 UTC [171/T278] INFO:  - 5 entries are forced through environment
2025-08-18 17:07:13.952 UTC [171/T278] INFO: Config file written to /etc/pihole/pihole.toml
2025-08-18 17:07:13.953 UTC [171/T278] INFO: Restarting FTL: dnsmasq config changed
2025-08-18 17:07:13.953 UTC [171M] INFO: Asked to terminate by "/usr/bin/pihole-FTL no-daemon" (PID 171, user pihole UID 1002)
2025-08-18 17:07:14.047 UTC [171/T173] INFO: Terminating database thread
2025-08-18 17:07:14.050 UTC [171/T176] INFO: Terminating timer thread
2025-08-18 17:07:14.209 UTC [171M] INFO: Finished final database update
2025-08-18 17:07:14.209 UTC [171M] INFO: Waiting for threads to join
2025-08-18 17:07:14.209 UTC [171M] INFO: Thread housekeeper (1) is idle, terminating it.
2025-08-18 17:07:15.584 UTC [171/T175] ERROR: Cannot receive UDP DNS reply: Timeout - no response from upstream DNS server
2025-08-18 17:07:15.584 UTC [171/T175] INFO: Tried to resolve PTR "201.169.60.187.in-addr.arpa" on 127.0.0.1#53 (UDP)
2025-08-18 17:07:16.209 UTC [171M] INFO: Thread dns-client (2) is still busy, cancelling it.
2025-08-18 17:07:16.209 UTC [171M] INFO: Thread ntp-client (4) is idle, terminating it.
2025-08-18 17:07:16.209 UTC [171M] INFO: All threads joined
2025-08-18 17:07:16.216 UTC [171M] INFO: PID file emptied
2025-08-18 17:07:16.217 UTC [171M] INFO: Stored 1 API session in the database
2025-08-18 17:07:16.827 UTC [171M] INFO: ########## FTL terminated after 33s  (internal restart)! ##########
2025-08-18 17:07:16.835 UTC [171M] INFO: ########## FTL started on cloud1! ##########
2025-08-18 17:07:16.835 UTC [171M] INFO: FTL branch: master
2025-08-18 17:07:16.835 UTC [171M] INFO: FTL version: v6.2.3
2025-08-18 17:07:16.835 UTC [171M] INFO: FTL commit: 88737f62
2025-08-18 17:07:16.835 UTC [171M] INFO: FTL date: 2025-06-10 20:44:58 +0200
2025-08-18 17:07:16.835 UTC [171M] INFO: FTL user: pihole
2025-08-18 17:07:16.835 UTC [171M] INFO: Compiled for linux/arm64/v8 (compiled on CI) using cc (Alpine 14.2.0) 14.2.0
2025-08-18 17:07:16.981 UTC [171M] INFO: 7 FTLCONF environment variables found (7 used, 0 invalid, 0 ignored)
2025-08-18 17:07:16.981 UTC [171M] INFO:    [✓] FTLCONF_dns_listeningMode is used
2025-08-18 17:07:16.981 UTC [171M] INFO:    [✓] FTLCONF_dns_domain is used
2025-08-18 17:07:16.981 UTC [171M] INFO:    [✓] FTLCONF_webserver_api_password is used
2025-08-18 17:07:16.981 UTC [171M] INFO:    [✓] FTLCONF_webserver_port is used
2025-08-18 17:07:16.981 UTC [171M] INFO:    [✓] FTLCONF_dns_upstreams is used
2025-08-18 17:07:16.981 UTC [171M] INFO:    [✓] FTLCONF_dhcp_active is used
2025-08-18 17:07:16.981 UTC [171M] INFO:    [✓] FTLCONF_misc_dnsmasq_lines is used
2025-08-18 17:07:16.982 UTC [171M] INFO: Wrote config file:
2025-08-18 17:07:16.982 UTC [171M] INFO:  - 155 total entries
2025-08-18 17:07:16.982 UTC [171M] INFO:  - 144 entries are default
2025-08-18 17:07:16.982 UTC [171M] INFO:  - 11 entries are modified
2025-08-18 17:07:16.982 UTC [171M] INFO:  - 5 entries are forced through environment
2025-08-18 17:07:16.983 UTC [171M] INFO: Parsed config file /etc/pihole/pihole.toml successfully
2025-08-18 17:07:16.983 UTC [171M] INFO: PID file does not exist or not readable
2025-08-18 17:07:16.983 UTC [171M] INFO: No other running FTL process found.
2025-08-18 17:07:16.984 UTC [171M] INFO: PID of FTL process: 171
2025-08-18 17:07:16.989 UTC [171M] INFO: listening on 0.0.0.0 port 53
2025-08-18 17:07:16.989 UTC [171M] INFO: listening on :: port 53
2025-08-18 17:07:16.989 UTC [171M] INFO: PID of FTL process: 171
2025-08-18 17:07:16.990 UTC [171M] INFO: Database version is 21
2025-08-18 17:07:16.990 UTC [171M] INFO: Database successfully initialized
2025-08-18 17:07:16.995 UTC [171M] INFO: Imported 623 queries from the on-disk database (it has 623 rows)
2025-08-18 17:07:16.995 UTC [171M] INFO: Parsing queries in database
2025-08-18 17:07:17.143 UTC [171M] INFO: Imported 623 queries from the long-term database
2025-08-18 17:07:17.143 UTC [171M] INFO:  -> Total DNS queries: 623
2025-08-18 17:07:17.144 UTC [171M] INFO:  -> Cached DNS queries: 2
2025-08-18 17:07:17.144 UTC [171M] INFO:  -> Forwarded DNS queries: 553
2025-08-18 17:07:17.144 UTC [171M] INFO:  -> Blocked DNS queries: 0
2025-08-18 17:07:17.144 UTC [171M] INFO:  -> Unknown DNS queries: 0
2025-08-18 17:07:17.144 UTC [171M] INFO:  -> Unique domains: 95
2025-08-18 17:07:17.144 UTC [171M] INFO:  -> Unique clients: 483
2025-08-18 17:07:17.144 UTC [171M] INFO:  -> DNS cache records: 0
2025-08-18 17:07:17.144 UTC [171M] INFO:  -> Known forward destinations: 1
2025-08-18 17:07:17.239 UTC [171M] INFO: FTL is running as user pihole (UID 1002)
2025-08-18 17:07:17.239 UTC [171M] INFO: Reading certificate from /etc/pihole/tls.pem ...
2025-08-18 17:07:17.239 UTC [171M] INFO: Using SSL/TLS certificate file /etc/pihole/tls.pem
2025-08-18 17:07:17.239 UTC [171M] INFO: Web server ports:
2025-08-18 17:07:17.239 UTC [171M] INFO:   - 0.0.0.0:8080 (HTTP, IPv4, OK)
2025-08-18 17:07:17.239 UTC [171M] INFO:   - 0.0.0.0:8443 (HTTPS, IPv4, OK)
2025-08-18 17:07:17.239 UTC [171M] INFO: Restored 1 API session from the database
2025-08-18 17:07:17.242 UTC [171M] INFO: Blocking status is enabled
2025-08-18 17:07:17.340 UTC [171/T293] INFO: Compiled 0 allow and 0 deny regex for 490 clients in 0.1 msec
2025-08-18 17:07:25.632 UTC [171/T292] ERROR: Failed to receive data from NTP server pool.ntp.org (23.186.168.131): Timeout
2025-08-18 17:07:26.198 UTC [171/T292] INFO: Received 7/8 valid NTP replies from pool.ntp.org
2025-08-18 17:07:26.198 UTC [171/T292] INFO: Time offset: -1.522711e+00 ms (excluded 1 outliers)
2025-08-18 17:07:26.198 UTC [171/T292] INFO: Round-trip delay: 6.343113e+01 ms (excluded 1 outliers)
2025-08-18 17:07:39.328 UTC [171/T295] ERROR: Cannot receive UDP DNS reply: Timeout - no response from upstream DNS server
2025-08-18 17:07:39.328 UTC [171/T295] INFO: Tried to resolve PTR "88.169.60.187.in-addr.arpa" on 127.0.0.1#53 (UDP)
2025-08-18 17:07:57.026 UTC [171/T295] ERROR: DNS compression pointer out of bounds: 14465
2025-08-18 17:07:57.026 UTC [171/T295] WARNING: Trying to free NULL pointer in ngethostbyname() (/app/src/resolve.c:449)
2025-08-18 17:07:57.353 UTC [171/T295] ERROR: DNS compression pointer out of bounds: 5703
2025-08-18 17:07:57.353 UTC [171/T295] WARNING: Trying to free NULL pointer in ngethostbyname() (/app/src/resolve.c:449)
2025-08-18 17:08:06.109 UTC [171/T293] INFO: Compiled 0 allow and 0 deny regex for 1280 clients in 0.1 msec
2025-08-18 17:08:06.210 UTC [171/T293] INFO: Compiled 0 allow and 0 deny regex for 1284 clients in 0.1 msec
2025-08-18 17:08:26.705 UTC [171M] ERROR: get_client_groupids("170.78.204.9") - SQL error step: database is locked
2025-08-18 17:08:26.705 UTC [171M] ERROR: Gravity database not available (allowlist)
2025-08-18 17:08:26.706 UTC [171M] ERROR: get_client_groupids("170.78.204.9") - SQL error step: database is locked
2025-08-18 17:08:26.706 UTC [171M] ERROR: Gravity database not available (denylist)
2025-08-18 17:08:26.706 UTC [171M] ERROR: get_client_groupids("170.78.204.9") - SQL error step: database is locked
2025-08-18 17:08:26.706 UTC [171M] ERROR: Gravity database not available (antigravity)
2025-08-18 17:08:26.706 UTC [171M] ERROR: get_client_groupids("170.78.204.9") - SQL error step: database is locked
2025-08-18 17:08:26.706 UTC [171M] ERROR: Gravity database not available (gravity)
2025-08-18 17:08:26.707 UTC [171M] WARNING: domain_in_list("75.17.209.186.in-addr.arpa", 0xe2cba4cffa18, whitelist): Database is busy, assuming domain is NOT on list
2025-08-18 17:08:26.707 UTC [171M] WARNING: domain_in_list("75.17.209.186.in-addr.arpa", 0xe2cba4d00418, blacklist): Database is busy, assuming domain is NOT on list
2025-08-18 17:08:26.707 UTC [171M] WARNING: domain_in_list("75.17.209.186.in-addr.arpa", 0xe2cba4d00058, antigravity): Database is busy, assuming domain is NOT on list
2025-08-18 17:08:26.707 UTC [171M] WARNING: domain_in_list("75.17.209.186.in-addr.arpa", 0xe2cba4cffc98, gravity): Database is busy, assuming domain is NOT on list
2025-08-18 17:08:26.774 UTC [171M] ERROR: SQLite3: no such table: main.antigravity in "SELECT adlist_id from vw_antigravity WHERE domain = ? AND group_id IN (0);" (1)
2025-08-18 17:08:26.774 UTC [171M] ERROR: domain_in_list("125.17.209.186.in-addr.arpa", 0xe2cba4d00058, antigravity): Failed to perform step: SQL logic error
2025-08-18 17:08:26.774 UTC [171M] ERROR: SQLite3: no such table: main.gravity in "SELECT adlist_id from vw_gravity WHERE domain = ? AND group_id IN (0);" (1)
2025-08-18 17:08:26.774 UTC [171M] ERROR: domain_in_list("125.17.209.186.in-addr.arpa", 0xe2cba4cffc98, gravity): Failed to perform step: SQL logic error
2025-08-18 17:08:26.822 UTC [171M] ERROR: SQLite3: no such table: main.gravity in "SELECT adlist_id from vw_gravity WHERE domain = ? AND group_id IN (0);" (1)
2025-08-18 17:08:26.822 UTC [171M] ERROR: gravityDB_open("SELECT(... vw_gravity ...)") - SQL error prepare: SQL logic error
2025-08-18 17:08:26.828 UTC [171M] ERROR: Gravity database not available (allowlist)
2025-08-18 17:08:27.093 UTC [171/T293] INFO: Gravity database has been updated, reloading now
2025-08-18 17:08:27.094 UTC [171/T293] INFO: Compiled 0 allow and 0 deny regex for 1624 clients in 0.2 msec
2025-08-18 17:10:50.369 UTC [171/T295] ERROR: Cannot receive UDP DNS reply: Timeout - no response from upstream DNS server
2025-08-18 17:10:50.369 UTC [171/T295] INFO: Tried to resolve PTR "121.58.238.170.in-addr.arpa" on 127.0.0.1#53 (UDP)
2025-08-18 17:18:46.656 UTC [171/T295] ERROR: Cannot receive UDP DNS reply: Timeout - no response from upstream DNS server
2025-08-18 17:18:46.656 UTC [171/T295] INFO: Tried to resolve PTR "29.122.111.187.in-addr.arpa" on 127.0.0.1#53 (UDP)
2025-08-18 17:23:31.904 UTC [171/T295] ERROR: Cannot receive UDP DNS reply: Timeout - no response from upstream DNS server
2025-08-18 17:23:31.904 UTC [171/T295] INFO: Tried to resolve PTR "74.45.84.206.in-addr.arpa" on 127.0.0.1#53 (UDP)
2025-08-18 17:24:46.016 UTC [171/T295] ERROR: Cannot receive UDP DNS reply: Timeout - no response from upstream DNS server
2025-08-18 17:24:46.016 UTC [171/T295] INFO: Tried to resolve PTR "70.123.246.170.in-addr.arpa" on 127.0.0.1#53 (UDP)
2025-08-18 17:24:50.304 UTC [171/T295] ERROR: Cannot receive UDP DNS reply: Timeout - no response from upstream DNS server
2025-08-18 17:24:50.304 UTC [171/T295] INFO: Tried to resolve PTR "135.122.246.170.in-addr.arpa" on 127.0.0.1#53 (UDP)
2025-08-18 17:25:17.760 UTC [171/T295] ERROR: Cannot receive UDP DNS reply: Timeout - no response from upstream DNS server
2025-08-18 17:25:17.760 UTC [171/T295] INFO: Tried to resolve PTR "99.122.246.170.in-addr.arpa" on 127.0.0.1#53 (UDP)
2025-08-18 17:25:54.327 UTC [171M] INFO: Rate-limiting 127.0.0.1 for at least 23 seconds
2025-08-18 17:26:17.237 UTC [171/T294] INFO: Still rate-limiting 127.0.0.1 as it made additional 8467 queries
2025-08-18 17:27:17.241 UTC [171/T294] INFO: Ending rate-limitation of 127.0.0.1
2025-08-18 17:29:54.368 UTC [171/T295] ERROR: Cannot receive UDP DNS reply: Timeout - no response from upstream DNS server
2025-08-18 17:29:54.368 UTC [171/T295] INFO: Tried to resolve PTR "9.218.70.177.in-addr.arpa" on 127.0.0.1#53 (UDP)
2025-08-18 17:29:58.720 UTC [171/T295] ERROR: Cannot receive UDP DNS reply: Timeout - no response from upstream DNS server
2025-08-18 17:29:58.720 UTC [171/T295] INFO: Tried to resolve PTR "180.223.70.177.in-addr.arpa" on 127.0.0.1#53 (UDP)
2025-08-18 17:32:23.360 UTC [171/T295] ERROR: Cannot receive UDP DNS reply: Timeout - no response from upstream DNS server
2025-08-18 17:32:23.360 UTC [171/T295] INFO: Tried to resolve PTR "91.121.221.131.in-addr.arpa" on 127.0.0.1#53 (UDP)
2025-08-18 17:35:26.592 UTC [171/T295] ERROR: Cannot receive UDP DNS reply: Timeout - no response from upstream DNS server
2025-08-18 17:35:26.592 UTC [171/T295] INFO: Tried to resolve PTR "145.219.169.45.in-addr.arpa" on 127.0.0.1#53 (UDP)
2025-08-18 17:35:33.184 UTC [171/T295] ERROR: Cannot receive UDP DNS reply: Timeout - no response from upstream DNS server
2025-08-18 17:35:33.184 UTC [171/T295] INFO: Tried to resolve PTR "70.219.169.45.in-addr.arpa" on 127.0.0.1#53 (UDP)
2025-08-18 17:35:42.080 UTC [171/T295] ERROR: Cannot receive UDP DNS reply: Timeout - no response from upstream DNS server
2025-08-18 17:35:42.080 UTC [171/T295] INFO: Tried to resolve PTR "31.219.169.45.in-addr.arpa" on 127.0.0.1#53 (UDP)
2025-08-18 17:36:18.624 UTC [171/T295] ERROR: Cannot receive UDP DNS reply: Timeout - no response from upstream DNS server
2025-08-18 17:36:18.624 UTC [171/T295] INFO: Tried to resolve PTR "12.219.169.45.in-addr.arpa" on 127.0.0.1#53 (UDP)
2025-08-18 17:36:55.744 UTC [171/T295] ERROR: Cannot receive UDP DNS reply: Timeout - no response from upstream DNS server
2025-08-18 17:36:55.744 UTC [171/T295] INFO: Tried to resolve PTR "0.208.249.167.in-addr.arpa" on 127.0.0.1#53 (UDP)
2025-08-18 17:37:03.360 UTC [171/T295] ERROR: Cannot receive UDP DNS reply: Timeout - no response from upstream DNS server
2025-08-18 17:37:03.360 UTC [171/T295] INFO: Tried to resolve PTR "6.210.249.167.in-addr.arpa" on 127.0.0.1#53 (UDP)
2025-08-18 17:44:50.944 UTC [171/T295] ERROR: Cannot receive UDP DNS reply: Timeout - no response from upstream DNS server
2025-08-18 17:44:50.944 UTC [171/T295] INFO: Tried to resolve PTR "84.54.141.192.in-addr.arpa" on 127.0.0.1#53 (UDP)
2025-08-18 17:46:27.569 UTC [171/T295] ERROR: DNS compression pointer out of bounds: 2048
2025-08-18 17:46:27.569 UTC [171/T295] WARNING: Trying to free NULL pointer in ngethostbyname() (/app/src/resolve.c:449)
2025-08-18 17:46:56.654 UTC [171/T295] ERROR: DNS compression pointer out of bounds: 2048
2025-08-18 17:46:56.654 UTC [171/T295] WARNING: Trying to free NULL pointer in ngethostbyname() (/app/src/resolve.c:449)
2025-08-18 17:46:58.136 UTC [171/T295] ERROR: DNS compression pointer out of bounds: 2048
2025-08-18 17:46:58.136 UTC [171/T295] WARNING: Trying to free NULL pointer in ngethostbyname() (/app/src/resolve.c:449)
2025-08-18 17:46:59.806 UTC [171/T295] ERROR: DNS compression pointer out of bounds: 2048
2025-08-18 17:46:59.806 UTC [171/T295] WARNING: Trying to free NULL pointer in ngethostbyname() (/app/src/resolve.c:449)
2025-08-18 17:47:01.334 UTC [171/T295] ERROR: DNS compression pointer out of bounds: 2048
2025-08-18 17:47:01.334 UTC [171/T295] WARNING: Trying to free NULL pointer in ngethostbyname() (/app/src/resolve.c:449)
2025-08-18 17:47:07.964 UTC [171/T295] ERROR: DNS compression pointer out of bounds: 2048
2025-08-18 17:47:07.964 UTC [171/T295] WARNING: Trying to free NULL pointer in ngethostbyname() (/app/src/resolve.c:449)
2025-08-18 17:47:42.912 UTC [171/T295] WARNING: Could not recv() in ngethostbyname() (/app/src/resolve.c:382): Resource temporarily unavailable
2025-08-18 17:47:42.912 UTC [171/T295] ERROR: Cannot receive TCP DNS reply (1): Timeout - no response from upstream DNS server
2025-08-18 17:47:42.912 UTC [171/T295] INFO: Tried to resolve PTR "101.73.227.186.in-addr.arpa" on 127.0.0.1#53 (TCP)
2025-08-18 17:49:16.341 UTC [171M] INFO: Rate-limiting 127.0.0.1 for at least 1 second
2025-08-18 17:49:17.257 UTC [171/T294] INFO: Still rate-limiting 127.0.0.1 as it made additional 1025 queries
2025-08-18 17:50:17.256 UTC [171/T294] INFO: Still rate-limiting 127.0.0.1 as it made additional 10006 queries
2025-08-18 17:51:17.256 UTC [171/T294] INFO: Ending rate-limitation of 127.0.0.1
2025-08-18 17:57:38.009 UTC [1390/F171] INFO: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
2025-08-18 17:57:38.009 UTC [1390/F171] INFO: ---------------------------->  FTL crashed!  <----------------------------
2025-08-18 17:57:38.009 UTC [1390/F171] INFO: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
2025-08-18 17:57:38.009 UTC [1390/F171] INFO: Please report a bug at https://github.com/pi-hole/FTL/issues
2025-08-18 17:57:38.009 UTC [1390/F171] INFO: and include in your report already the following details:
2025-08-18 17:57:38.009 UTC [1390/F171] INFO: FTL has been running for 3022 seconds
2025-08-18 17:57:38.009 UTC [1390/F171] INFO: FTL branch: master
2025-08-18 17:57:38.009 UTC [1390/F171] INFO: FTL version: v6.2.3
2025-08-18 17:57:38.009 UTC [1390/F171] INFO: FTL commit: 88737f62
2025-08-18 17:57:38.009 UTC [1390/F171] INFO: FTL date: 2025-06-10 20:44:58 +0200
2025-08-18 17:57:38.010 UTC [1390/F171] INFO: FTL user: started as pihole, ended as pihole
2025-08-18 17:57:38.010 UTC [1390/F171] INFO: Compiled for linux/arm64/v8 (compiled on CI) using cc (Alpine 14.2.0) 14.2.0
2025-08-18 17:57:38.010 UTC [1390/F171] INFO: Process details: MID: 171
2025-08-18 17:57:38.010 UTC [1390/F171] INFO:                  PID: 1390
2025-08-18 17:57:38.010 UTC [1390/F171] INFO:                  TID: 1390
2025-08-18 17:57:38.010 UTC [1390/F171] INFO:                  Name: pihole-FTL
2025-08-18 17:57:38.010 UTC [1390/F171] INFO: Received signal: Segmentation fault
2025-08-18 17:57:38.010 UTC [1390/F171] INFO:      at address: 0
2025-08-18 17:57:38.010 UTC [1390/F171] INFO:      with code:  SEGV_MAPERR (Address not mapped to object)
2025-08-18 17:57:38.010 UTC [1390/F171] INFO: !!! INFO: pihole-FTL has not been compiled with glibc/backtrace support, not generating one !!!
2025-08-18 17:57:38.010 UTC [1390/F171] INFO: ------ Listing content of directory /dev/shm ------
2025-08-18 17:57:38.010 UTC [1390/F171] INFO: File Mode User:Group      Size  Filename
2025-08-18 17:57:38.010 UTC [1390/F171] INFO: rwxrwxrwx root:root       360   .
2025-08-18 17:57:38.010 UTC [1390/F171] INFO: rwxr-xr-x root:root       340   ..
2025-08-18 17:57:38.010 UTC [1390/F171] INFO: rw------- pihole:pihole   786K  FTL-171-recycler
2025-08-18 17:57:38.010 UTC [1390/F171] INFO: rw------- pihole:pihole   561K  FTL-171-dns-cache-lookup
2025-08-18 17:57:38.010 UTC [1390/F171] INFO: rw------- pihole:pihole   164K  FTL-171-domains-lookup
2025-08-18 17:57:38.010 UTC [1390/F171] INFO: rw------- pihole:pihole   360K  FTL-171-clients-lookup
2025-08-18 17:57:38.010 UTC [1390/F171] INFO: rw------- pihole:pihole   569K  FTL-171-fifo-log
2025-08-18 17:57:38.010 UTC [1390/F171] INFO: rw------- pihole:pihole     4K  FTL-171-per-client-regex
2025-08-18 17:57:38.010 UTC [1390/F171] INFO: rw------- pihole:pihole     3M  FTL-171-dns-cache
2025-08-18 17:57:38.010 UTC [1390/F171] INFO: rw------- pihole:pihole     8K  FTL-171-overTime
2025-08-18 17:57:38.010 UTC [1390/F171] INFO: rw------- pihole:pihole     5M  FTL-171-queries
2025-08-18 17:57:38.010 UTC [1390/F171] INFO: rw------- pihole:pihole    29K  FTL-171-upstreams
2025-08-18 17:57:38.010 UTC [1390/F171] INFO: rw------- pihole:pihole    31M  FTL-171-clients
2025-08-18 17:57:38.010 UTC [1390/F171] INFO: rw------- pihole:pihole   651K  FTL-171-domains
2025-08-18 17:57:38.010 UTC [1390/F171] INFO: rw------- pihole:pihole     2M  FTL-171-strings
2025-08-18 17:57:38.010 UTC [1390/F171] INFO: rw------- pihole:pihole   144   FTL-171-settings
2025-08-18 17:57:38.010 UTC [1390/F171] INFO: rw------- pihole:pihole   328   FTL-171-counters
2025-08-18 17:57:38.010 UTC [1390/F171] INFO: rw------- pihole:pihole    88   FTL-171-lock
2025-08-18 17:57:38.010 UTC [1390/F171] INFO: ---------------------------------------------------
2025-08-18 17:57:38.010 UTC [1390/F171] INFO: Please also include some lines from above the !!!!!!!!! header.
2025-08-18 17:57:38.010 UTC [1390/F171] INFO: Thank you for helping us to improve our FTL engine!
2025-08-18 17:57:38.010 UTC [1390/F171] INFO: Asking parent pihole-FTL (PID 171) to shut down
2025-08-18 17:57:38.010 UTC [1390/F171] INFO: FTL fork terminated!
2025-08-18 17:57:38.010 UTC [171M] INFO: Received: RT37 (37 -> 2)
2025-08-18 17:57:38.010 UTC [171M] INFO: Asked to terminate by "/usr/bin/pihole-FTL no-daemon" (PID 171, user pihole UID 1002)
2025-08-18 17:57:38.010 UTC [1428/F171] ERROR: Error when obtaining outer SHM lock: Previous owner died
2025-08-18 17:57:38.011 UTC [1428/F171] ERROR: Error when obtaining inner SHM lock: Previous owner died
2025-08-18 17:57:38.011 UTC [1428/F171] INFO: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
2025-08-18 17:57:38.011 UTC [1428/F171] INFO: ---------------------------->  FTL crashed!  <----------------------------
2025-08-18 17:57:38.011 UTC [1428/F171] INFO: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
2025-08-18 17:57:38.011 UTC [1428/F171] INFO: Please report a bug at https://github.com/pi-hole/FTL/issues
2025-08-18 17:57:38.011 UTC [1428/F171] INFO: and include in your report already the following details:
2025-08-18 17:57:38.011 UTC [1428/F171] INFO: FTL has been running for 3022 seconds
2025-08-18 17:57:38.011 UTC [1428/F171] INFO: FTL branch: master
2025-08-18 17:57:38.011 UTC [1428/F171] INFO: FTL version: v6.2.3
2025-08-18 17:57:38.011 UTC [1428/F171] INFO: FTL commit: 88737f62
2025-08-18 17:57:38.011 UTC [1428/F171] INFO: FTL date: 2025-06-10 20:44:58 +0200
2025-08-18 17:57:38.011 UTC [1428/F171] INFO: FTL user: started as pihole, ended as pihole
2025-08-18 17:57:38.011 UTC [1428/F171] INFO: Compiled for linux/arm64/v8 (compiled on CI) using cc (Alpine 14.2.0) 14.2.0
2025-08-18 17:57:38.011 UTC [1428/F171] INFO: Process details: MID: 171
2025-08-18 17:57:38.011 UTC [1428/F171] INFO:                  PID: 1428
2025-08-18 17:57:38.011 UTC [1428/F171] INFO:                  TID: 1428
2025-08-18 17:57:38.011 UTC [1428/F171] INFO:                  Name: pihole-FTL
2025-08-18 17:57:38.011 UTC [1428/F171] INFO: Received signal: Segmentation fault
2025-08-18 17:57:38.011 UTC [1428/F171] INFO:      at address: 0
2025-08-18 17:57:38.011 UTC [1428/F171] INFO:      with code:  SEGV_MAPERR (Address not mapped to object)
2025-08-18 17:57:38.011 UTC [1428/F171] INFO: !!! INFO: pihole-FTL has not been compiled with glibc/backtrace support, not generating one !!!
2025-08-18 17:57:38.011 UTC [1428/F171] INFO: ------ Listing content of directory /dev/shm ------
2025-08-18 17:57:38.011 UTC [1428/F171] INFO: File Mode User:Group      Size  Filename
2025-08-18 17:57:38.011 UTC [1428/F171] INFO: rwxrwxrwx root:root       360   .
2025-08-18 17:57:38.011 UTC [1428/F171] INFO: rwxr-xr-x root:root       340   ..
2025-08-18 17:57:38.011 UTC [1428/F171] INFO: rw------- pihole:pihole   786K  FTL-171-recycler
2025-08-18 17:57:38.011 UTC [1428/F171] INFO: rw------- pihole:pihole   561K  FTL-171-dns-cache-lookup
2025-08-18 17:57:38.011 UTC [1428/F171] INFO: rw------- pihole:pihole   164K  FTL-171-domains-lookup
2025-08-18 17:57:38.011 UTC [1428/F171] INFO: rw------- pihole:pihole   360K  FTL-171-clients-lookup
2025-08-18 17:57:38.011 UTC [1428/F171] INFO: rw------- pihole:pihole   569K  FTL-171-fifo-log
2025-08-18 17:57:38.011 UTC [1428/F171] INFO: rw------- pihole:pihole     4K  FTL-171-per-client-regex
2025-08-18 17:57:38.011 UTC [1428/F171] INFO: rw------- pihole:pihole     3M  FTL-171-dns-cache
2025-08-18 17:57:38.011 UTC [1428/F171] INFO: rw------- pihole:pihole     8K  FTL-171-overTime
2025-08-18 17:57:38.011 UTC [1428/F171] INFO: rw------- pihole:pihole     5M  FTL-171-queries
2025-08-18 17:57:38.012 UTC [1428/F171] INFO: rw------- pihole:pihole    29K  FTL-171-upstreams
2025-08-18 17:57:38.012 UTC [1428/F171] INFO: rw------- pihole:pihole    31M  FTL-171-clients
2025-08-18 17:57:38.012 UTC [1428/F171] INFO: rw------- pihole:pihole   651K  FTL-171-domains
2025-08-18 17:57:38.012 UTC [1428/F171] INFO: rw------- pihole:pihole     2M  FTL-171-strings
2025-08-18 17:57:38.012 UTC [1428/F171] INFO: rw------- pihole:pihole   144   FTL-171-settings
2025-08-18 17:57:38.012 UTC [1428/F171] INFO: rw------- pihole:pihole   328   FTL-171-counters
2025-08-18 17:57:38.012 UTC [1428/F171] INFO: rw------- pihole:pihole    88   FTL-171-lock
2025-08-18 17:57:38.012 UTC [1428/F171] INFO: ---------------------------------------------------
2025-08-18 17:57:38.012 UTC [1428/F171] INFO: Please also include some lines from above the !!!!!!!!! header.
2025-08-18 17:57:38.012 UTC [1428/F171] INFO: Thank you for helping us to improve our FTL engine!
2025-08-18 17:57:38.012 UTC [1428/F171] INFO: Asking parent pihole-FTL (PID 171) to shut down
2025-08-18 17:57:38.012 UTC [1428/F171] INFO: FTL fork terminated!
2025-08-18 17:57:38.012 UTC [171M] INFO: Received: RT37 (37 -> 2)
2025-08-18 17:57:38.012 UTC [171M] INFO: Asked to terminate by "/usr/bin/pihole-FTL no-daemon" (PID 171, user pihole UID 1002)
2025-08-18 17:57:38.012 UTC [1426/F171] ERROR: Error when obtaining outer SHM lock: Previous owner died
2025-08-18 17:57:38.012 UTC [1426/F171] ERROR: Error when obtaining inner SHM lock: Previous owner died
2025-08-18 17:57:38.012 UTC [1426/F171] INFO: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
2025-08-18 17:57:38.012 UTC [1426/F171] INFO: ---------------------------->  FTL crashed!  <----------------------------
2025-08-18 17:57:38.012 UTC [1426/F171] INFO: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
2025-08-18 17:57:38.012 UTC [1426/F171] INFO: Please report a bug at https://github.com/pi-hole/FTL/issues
2025-08-18 17:57:38.012 UTC [1426/F171] INFO: and include in your report already the following details:
2025-08-18 17:57:38.012 UTC [1426/F171] INFO: FTL has been running for 3022 seconds
2025-08-18 17:57:38.012 UTC [1426/F171] INFO: FTL branch: master
2025-08-18 17:57:38.012 UTC [1426/F171] INFO: FTL version: v6.2.3
2025-08-18 17:57:38.012 UTC [1426/F171] INFO: FTL commit: 88737f62
2025-08-18 17:57:38.012 UTC [1426/F171] INFO: FTL date: 2025-06-10 20:44:58 +0200
2025-08-18 17:57:38.012 UTC [1426/F171] INFO: FTL user: started as pihole, ended as pihole
2025-08-18 17:57:38.012 UTC [1426/F171] INFO: Compiled for linux/arm64/v8 (compiled on CI) using cc (Alpine 14.2.0) 14.2.0
2025-08-18 17:57:38.012 UTC [1426/F171] INFO: Process details: MID: 171
2025-08-18 17:57:38.012 UTC [1426/F171] INFO:                  PID: 1426
2025-08-18 17:57:38.012 UTC [1426/F171] INFO:                  TID: 1426
2025-08-18 17:57:38.012 UTC [1426/F171] INFO:                  Name: pihole-FTL
2025-08-18 17:57:38.012 UTC [1426/F171] INFO: Received signal: Segmentation fault
2025-08-18 17:57:38.012 UTC [1426/F171] INFO:      at address: 0
2025-08-18 17:57:38.012 UTC [1426/F171] INFO:      with code:  SEGV_MAPERR (Address not mapped to object)
2025-08-18 17:57:38.012 UTC [1426/F171] INFO: !!! INFO: pihole-FTL has not been compiled with glibc/backtrace support, not generating one !!!
2025-08-18 17:57:38.012 UTC [1426/F171] INFO: ------ Listing content of directory /dev/shm ------
2025-08-18 17:57:38.012 UTC [1426/F171] INFO: File Mode User:Group      Size  Filename
2025-08-18 17:57:38.013 UTC [1426/F171] INFO: rwxrwxrwx root:root       360   .
2025-08-18 17:57:38.013 UTC [1426/F171] INFO: rwxr-xr-x root:root       340   ..
2025-08-18 17:57:38.013 UTC [1426/F171] INFO: rw------- pihole:pihole   786K  FTL-171-recycler
2025-08-18 17:57:38.013 UTC [1426/F171] INFO: rw------- pihole:pihole   561K  FTL-171-dns-cache-lookup
2025-08-18 17:57:38.013 UTC [1426/F171] INFO: rw------- pihole:pihole   164K  FTL-171-domains-lookup
2025-08-18 17:57:38.013 UTC [1426/F171] INFO: rw------- pihole:pihole   360K  FTL-171-clients-lookup
2025-08-18 17:57:38.013 UTC [1426/F171] INFO: rw------- pihole:pihole   569K  FTL-171-fifo-log
2025-08-18 17:57:38.013 UTC [1426/F171] INFO: rw------- pihole:pihole     4K  FTL-171-per-client-regex
2025-08-18 17:57:38.013 UTC [1426/F171] INFO: rw------- pihole:pihole     3M  FTL-171-dns-cache
2025-08-18 17:57:38.013 UTC [1426/F171] INFO: rw------- pihole:pihole     8K  FTL-171-overTime
2025-08-18 17:57:38.013 UTC [1426/F171] INFO: rw------- pihole:pihole     5M  FTL-171-queries
2025-08-18 17:57:38.013 UTC [1426/F171] INFO: rw------- pihole:pihole    29K  FTL-171-upstreams
2025-08-18 17:57:38.013 UTC [1426/F171] INFO: rw------- pihole:pihole    31M  FTL-171-clients
2025-08-18 17:57:38.013 UTC [1426/F171] INFO: rw------- pihole:pihole   651K  FTL-171-domains
2025-08-18 17:57:38.013 UTC [1426/F171] INFO: rw------- pihole:pihole     2M  FTL-171-strings
2025-08-18 17:57:38.013 UTC [1426/F171] INFO: rw------- pihole:pihole   144   FTL-171-settings
2025-08-18 17:57:38.013 UTC [1426/F171] INFO: rw------- pihole:pihole   328   FTL-171-counters
2025-08-18 17:57:38.013 UTC [1426/F171] INFO: rw------- pihole:pihole    88   FTL-171-lock
2025-08-18 17:57:38.013 UTC [1426/F171] INFO: ---------------------------------------------------
2025-08-18 17:57:38.013 UTC [1426/F171] INFO: Please also include some lines from above the !!!!!!!!! header.
2025-08-18 17:57:38.013 UTC [1426/F171] INFO: Thank you for helping us to improve our FTL engine!
2025-08-18 17:57:38.013 UTC [1426/F171] INFO: Asking parent pihole-FTL (PID 171) to shut down
2025-08-18 17:57:38.013 UTC [1426/F171] INFO: FTL fork terminated!
2025-08-18 17:57:38.013 UTC [171M] INFO: Received: RT37 (37 -> 2)
2025-08-18 17:57:38.013 UTC [171M] INFO: Asked to terminate by "/usr/bin/pihole-FTL no-daemon" (PID 171, user pihole UID 1002)
2025-08-18 17:57:38.013 UTC [171M] ERROR: Error when obtaining outer SHM lock: Previous owner died
2025-08-18 17:57:38.013 UTC [171M] ERROR: Error when obtaining inner SHM lock: Previous owner died
Editor is loading...