Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Segmentation fault SEGV_MAPERR when trying to access web interface #2288

Open
3 of 6 tasks
mbirth opened this issue Feb 26, 2025 · 1 comment
Open
3 of 6 tasks

Segmentation fault SEGV_MAPERR when trying to access web interface #2288

mbirth opened this issue Feb 26, 2025 · 1 comment
Labels
Fixed in next release

Comments

@mbirth
Copy link

mbirth commented Feb 26, 2025 •
edited
Loading

This is a: Bug

Details

After updating environment variables, PiHole comes up fine and serves DNS requests. Accessing non-existing pages on the web server also works and gives and error page. However, the moment I try to access /admin/, it crashes with a SEGV_MAPERR.

Related Issues

  • I have searched this repository/Pi-hole forums for existing issues and pull requests that look similar

#2281
#2279 - probably?

How to reproduce the issue

  1. Environment data
  • Operating System: Synology DSM 7.1
  • Hardware: Synology DS415+
  • Kernel Architecture: x64
  • Docker Install Info and version:
    • Software source:
    • Supplimentary Software:
  • Hardware architecture:
  1. docker-compose.yml contents, docker run shell command, or paste a screenshot of any UI based configuration of containers here
version: "3.8"

services:
  pihole:
    image: pihole/pihole:latest
    container_name: Pi-Hole
    restart: unless-stopped
    # Disable healthcheck due to Synology memory leak
    # https://community.synology.com/enu/forum/1/post/148437?page=5&sort=oldest
    healthcheck:
      disable: true
    environment:
      TZ: Europe/London
      FTLCONF_webserver_api_password: pihole
      FTLCONF_dns_listeningMode: 'all'
      DNSMASQ_USER: root
    volumes:
      - type: bind
        source: /volume1/docker/pihole/etc-pihole
        target: /etc/pihole
      - type: bind
        source: /volume1/docker/pihole/etc-dnsmasq.d
        target: /etc/dnsmasq.d
    ports:
      - 443:443/tcp
      - 53:53/tcp
      - 53:53/udp
      - 67:67/udp
      - 80:80/tcp
    networks:
      bridged_lan:
        ipv4_address: 172.16.16.16
    cap_add:
        - NET_ADMIN
        - NET_RAW
        - NET_BIND_SERVICE
        - CHOWN
        - SYS_NICE

networks:
  bridged_lan:
    name: bridged_lan
    driver: macvlan
    driver_opts:
      parent: eth0
    ipam:
      driver: default
      config:
        - subnet: 172.16.0.0/16
          ip_range: 172.16.16.1/24
          gateway: 172.16.254.254
  1. any additional info to help reproduce
  [i] Setting up user & group for the pihole user
  [i] PIHOLE_UID not set in environment, using default (1000)
  [i] PIHOLE_GID not set in environment, using default (1000)
  [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] Existing gravity database found - schema will be upgraded if necessary
     
  [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
Failed to set capabilities on file '/usr/bin/pihole-FTL': Not supported
  [i] Starting pihole-FTL (no-daemon) as root
  [i] Version info:
      Core version is v6.0.4 (Latest: null)
      Web version is v6.0.1 (Latest: null)
      FTL version is v6.0.2 (Latest: null)
2025-02-26 04:36:04.430 GMT [56M] INFO: ########## FTL started on f46b60fc9ae4! ##########
2025-02-26 04:36:04.430 GMT [56M] INFO: FTL branch: master
2025-02-26 04:36:04.430 GMT [56M] INFO: FTL version: v6.0.2
2025-02-26 04:36:04.430 GMT [56M] INFO: FTL commit: ac500d5f
2025-02-26 04:36:04.430 GMT [56M] INFO: FTL date: 2025-02-21 21:48:20 +0000
2025-02-26 04:36:04.430 GMT [56M] INFO: FTL user: root
2025-02-26 04:36:04.430 GMT [56M] INFO: Compiled for linux/amd64 (compiled on CI) using cc (Alpine 14.2.0) 14.2.0
2025-02-26 04:36:04.434 GMT [56M] ERROR: getrandom() failed in create_password()
2025-02-26 04:36:04.434 GMT [56M] INFO: 2 FTLCONF environment variables found (2 used, 0 invalid, 0 ignored)
2025-02-26 04:36:04.434 GMT [56M] INFO:    [✓] FTLCONF_dns_listeningMode is used
2025-02-26 04:36:04.434 GMT [56M] INFO:    [✓] FTLCONF_webserver_api_password is used
2025-02-26 04:36:04.436 GMT [56M] ERROR: Trying to compare a NULL (L) string in writeFTLtoml() (/app/src/config/toml_writer.c:105)
2025-02-26 04:36:04.436 GMT [56M] INFO: Wrote config file:
2025-02-26 04:36:04.436 GMT [56M] INFO:  - 152 total entries
2025-02-26 04:36:04.437 GMT [56M] INFO:  - 140 entries are default
2025-02-26 04:36:04.437 GMT [56M] INFO:  - 12 entries are modified
2025-02-26 04:36:04.437 GMT [56M] INFO:  - 1 entry is forced through environment
2025-02-26 04:36:04.441 GMT [56M] INFO: Parsed config file /etc/pihole/pihole.toml successfully
2025-02-26 04:36:04.441 GMT [56M] INFO: PID file does not exist or not readable
2025-02-26 04:36:04.441 GMT [56M] INFO: No other running FTL process found.
2025-02-26 04:36:04.444 GMT [56M] WARNING: Starting pihole-FTL as user root is not recommended
2025-02-26 04:36:04.445 GMT [56M] INFO: PID of FTL process: 56
2025-02-26 04:36:04.445 GMT [56M] INFO: listening on 0.0.0.0 port 53
2025-02-26 04:36:04.446 GMT [56M] INFO: listening on :: port 53
2025-02-26 04:36:04.985 GMT [56M] INFO: PID of FTL process: 56
2025-02-26 04:36:04.986 GMT [56M] INFO: Database version is 21
2025-02-26 04:36:04.987 GMT [56M] INFO: Database successfully initialized
2025-02-26 04:36:08.803 GMT [56M] INFO: Imported 98997 queries from the on-disk database (it has 11223617 rows)
2025-02-26 04:36:08.969 GMT [56M] INFO: Parsing queries in database
2025-02-26 04:36:09.081 GMT [56M] INFO:   10000 queries parsed...
2025-02-26 04:36:09.177 GMT [56M] INFO:   20000 queries parsed...
2025-02-26 04:36:09.272 GMT [56M] INFO:   30000 queries parsed...
2025-02-26 04:36:09.392 GMT [56M] INFO:   40000 queries parsed...
2025-02-26 04:36:09.489 GMT [56M] INFO:   50000 queries parsed...
2025-02-26 04:36:09.589 GMT [56M] INFO:   60000 queries parsed...
2025-02-26 04:36:09.688 GMT [56M] INFO:   70000 queries parsed...
2025-02-26 04:36:09.798 GMT [56M] INFO:   80000 queries parsed...
2025-02-26 04:36:09.901 GMT [56M] INFO:   90000 queries parsed...
2025-02-26 04:36:09.989 GMT [56M] INFO: Imported 98997 queries from the long-term database
2025-02-26 04:36:09.989 GMT [56M] INFO:  -> Total DNS queries: 98997
2025-02-26 04:36:09.989 GMT [56M] INFO:  -> Cached DNS queries: 69141
2025-02-26 04:36:09.989 GMT [56M] INFO:  -> Forwarded DNS queries: 25418
2025-02-26 04:36:09.989 GMT [56M] INFO:  -> Blocked DNS queries: 3693
2025-02-26 04:36:09.990 GMT [56M] INFO:  -> Unknown DNS queries: 109
2025-02-26 04:36:09.990 GMT [56M] INFO:  -> Unique domains: 2146
2025-02-26 04:36:09.990 GMT [56M] INFO:  -> Unique clients: 24
2025-02-26 04:36:09.990 GMT [56M] INFO:  -> DNS cache records: 267
2025-02-26 04:36:09.990 GMT [56M] INFO:  -> Known forward destinations: 4
2025-02-26 04:36:11.231 GMT [56M] WARNING: Insufficient permissions to set system time (CAP_SYS_TIME required), NTP client not available
2025-02-26 04:36:11.232 GMT [56/T170] INFO: NTP server listening on :::123 (IPv6)
2025-02-26 04:36:11.232 GMT [56M] INFO: FTL is running as root
2025-02-26 04:36:11.232 GMT [56/T172] WARNING: Long-term load (15min avg) larger than number of processors: 5.4 > 4
2025-02-26 04:36:11.232 GMT [56M] INFO: Reading certificate from /etc/pihole/tls.pem ...
2025-02-26 04:36:11.232 GMT [56M] INFO: Using SSL/TLS certificate file /etc/pihole/tls.pem
2025-02-26 04:36:11.233 GMT [56/T169] INFO: NTP server listening on 0.0.0.0:123 (IPv4)
2025-02-26 04:36:11.233 GMT [56M] INFO: Web server ports:
2025-02-26 04:36:11.233 GMT [56M] INFO:   - 80 (HTTP, IPv4, optional)
2025-02-26 04:36:11.233 GMT [56M] INFO:   - 443 (HTTPS, IPv4, optional)
2025-02-26 04:36:11.234 GMT [56M] INFO: Restored 0 API sessions from the database
2025-02-26 04:36:11.441 GMT [56M] ERROR: getrandom() failed in generate_password()
2025-02-26 04:36:11.441 GMT [56M] ERROR: Failed to generate CLI password hash!
2025-02-26 04:36:11.444 GMT [56M] INFO: Blocking status is enabled
2025-02-26 04:36:11.558 GMT [56/T177] INFO: Local URI: "/admin/"
2025-02-26 04:36:11.559 GMT [56/T177] INFO: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
2025-02-26 04:36:11.559 GMT [56/T177] INFO: ---------------------------->  FTL crashed!  <----------------------------
2025-02-26 04:36:11.559 GMT [56/T177] INFO: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
2025-02-26 04:36:11.559 GMT [56/T177] INFO: Please report a bug at https://github.com/pi-hole/FTL/issues
2025-02-26 04:36:11.559 GMT [56/T177] INFO: and include in your report already the following details:
2025-02-26 04:36:11.559 GMT [56/T177] INFO: FTL has been running for 7 seconds
2025-02-26 04:36:11.559 GMT [56/T177] INFO: FTL branch: master
2025-02-26 04:36:11.559 GMT [56/T177] INFO: FTL version: v6.0.2
2025-02-26 04:36:11.559 GMT [56/T177] INFO: FTL commit: ac500d5f
2025-02-26 04:36:11.559 GMT [56/T177] INFO: FTL date: 2025-02-21 21:48:20 +0000
2025-02-26 04:36:11.560 GMT [56/T177] INFO: FTL user: started as root, ended as root
2025-02-26 04:36:11.560 GMT [56/T177] INFO: Compiled for linux/amd64 (compiled on CI) using cc (Alpine 14.2.0) 14.2.0
2025-02-26 04:36:11.560 GMT [56/T177] INFO: Process details: MID: 56
2025-02-26 04:36:11.560 GMT [56/T177] INFO:                  PID: 56
2025-02-26 04:36:11.560 GMT [56/T177] INFO:                  TID: 177
2025-02-26 04:36:11.560 GMT [56/T177] INFO:                  Name: civetweb-worker
2025-02-26 04:36:11.560 GMT [56/T177] INFO: Received signal: Segmentation fault
2025-02-26 04:36:11.560 GMT [56/T177] INFO:      at address: 0
2025-02-26 04:36:11.560 GMT [56/T177] INFO:      with code:  SEGV_MAPERR (Address not mapped to object)
2025-02-26 04:36:11.560 GMT [56/T177] INFO: !!! INFO: pihole-FTL has not been compiled with glibc/backtrace support, not generating one !!!
2025-02-26 04:36:11.561 GMT [56/T177] INFO: ------ Listing content of directory /dev/shm ------
2025-02-26 04:36:11.561 GMT [56/T177] INFO: File Mode User:Group      Size  Filename
2025-02-26 04:36:11.561 GMT [56/T177] INFO: rwxrwxrwx root:root       360   .
2025-02-26 04:36:11.561 GMT [56/T177] INFO: rwxr-xr-x root:root       340   ..
2025-02-26 04:36:11.561 GMT [56/T177] INFO: rw------- root:root       786K  FTL-56-recycler
2025-02-26 04:36:11.561 GMT [56/T177] INFO: rw------- root:root         4K  FTL-56-dns-cache-lookup
2025-02-26 04:36:11.561 GMT [56/T177] INFO: rw------- root:root        20K  FTL-56-domains-lookup
2025-02-26 04:36:11.562 GMT [56/T177] INFO: rw------- root:root         4K  FTL-56-clients-lookup
2025-02-26 04:36:11.562 GMT [56/T177] INFO: rw------- root:root       569K  FTL-56-fifo-log
2025-02-26 04:36:11.562 GMT [56/T177] INFO: rw------- root:root         4K  FTL-56-per-client-regex
2025-02-26 04:36:11.562 GMT [56/T177] INFO: rw------- root:root        20K  FTL-56-dns-cache
2025-02-26 04:36:11.562 GMT [56/T177] INFO: rw------- root:root         8K  FTL-56-overTime
2025-02-26 04:36:11.562 GMT [56/T177] INFO: rw------- root:root         7M  FTL-56-queries
2025-02-26 04:36:11.562 GMT [56/T177] INFO: rw------- root:root        29K  FTL-56-upstreams
2025-02-26 04:36:11.563 GMT [56/T177] INFO: rw------- root:root       348K  FTL-56-clients
2025-02-26 04:36:11.563 GMT [56/T177] INFO: rw------- root:root        70K  FTL-56-domains
2025-02-26 04:36:11.563 GMT [56/T177] INFO: rw------- root:root       123K  FTL-56-strings
2025-02-26 04:36:11.563 GMT [56/T177] INFO: rw------- root:root       144   FTL-56-settings
2025-02-26 04:36:11.563 GMT [56/T177] INFO: rw------- root:root       328   FTL-56-counters
2025-02-26 04:36:11.563 GMT [56/T177] INFO: rw------- root:root        88   FTL-56-lock
2025-02-26 04:36:11.564 GMT [56/T177] INFO: ---------------------------------------------------
2025-02-26 04:36:11.564 GMT [56/T177] INFO: Please also include some lines from above the !!!!!!!!! header.
2025-02-26 04:36:11.564 GMT [56/T177] INFO: Thank you for helping us to improve our FTL engine!
2025-02-26 04:36:11.564 GMT [56/T177] INFO: Waiting for threads to join
2025-02-26 04:36:11.639 GMT [56/T171] INFO: Compiled 2 allow and 11 deny regex for 24 clients in 92.6 msec
2025-02-26 04:36:11.639 GMT [56/T171] INFO: Terminating database thread
2025-02-26 04:36:11.639 GMT [56/T177] INFO: Thread housekeeper (1) is idle, terminating it.
2025-02-26 04:36:11.640 GMT [56/T177] INFO: Thread dns-client (2) is idle, terminating it.
2025-02-26 04:36:11.640 GMT [56/T177] INFO: Thread timer (3) is idle, terminating it.
2025-02-26 04:36:11.640 GMT [56/T177] INFO: All threads joined
2025-02-26 04:36:11.654 GMT [56/T177] INFO: PID file emptied
2025-02-26 04:36:11.655 GMT [56/T177] INFO: Stored 0 API sessions in the database
/bin/bash: line 1:    56 Segmentation fault      (core dumped) /usr/bin/pihole-FTL no-daemon > /dev/null
2025-02-26 04:36:12.572 GMT [56M] INFO: Finished final database update
2025-02-26 04:36:13.253 GMT [56M] INFO: Waiting for threads to join
2025-02-26 04:36:13.253 GMT [56M] INFO: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
2025-02-26 04:36:13.253 GMT [56M] INFO: ---------------------------->  FTL crashed!  <----------------------------
2025-02-26 04:36:13.253 GMT [56M] INFO: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
2025-02-26 04:36:13.254 GMT [56M] INFO: Please report a bug at https://github.com/pi-hole/FTL/issues
2025-02-26 04:36:13.254 GMT [56M] INFO: and include in your report already the following details:
2025-02-26 04:36:13.254 GMT [56M] INFO: FTL has been running for 9 seconds
2025-02-26 04:36:13.254 GMT [56M] INFO: FTL branch: master
2025-02-26 04:36:13.254 GMT [56M] INFO: FTL version: v6.0.2
2025-02-26 04:36:13.254 GMT [56M] INFO: FTL commit: ac500d5f
2025-02-26 04:36:13.254 GMT [56M] INFO: FTL date: 2025-02-21 21:48:20 +0000
2025-02-26 04:36:13.254 GMT [56M] INFO: FTL user: started as root, ended as root
2025-02-26 04:36:13.254 GMT [56M] INFO: Compiled for linux/amd64 (compiled on CI) using cc (Alpine 14.2.0) 14.2.0
2025-02-26 04:36:13.254 GMT [56M] INFO: Process details: MID: 56
2025-02-26 04:36:13.254 GMT [56M] INFO:                  PID: 56
2025-02-26 04:36:13.254 GMT [56M] INFO:                  TID: 56
2025-02-26 04:36:13.254 GMT [56M] INFO:                  Name: pihole-FTL
2025-02-26 04:36:13.254 GMT [56M] INFO: Received signal: Segmentation fault
2025-02-26 04:36:13.254 GMT [56M] INFO:      at address: 0x7f3179f41b70
2025-02-26 04:36:13.254 GMT [56M] INFO:      with code:  SEGV_MAPERR (Address not mapped to object)
2025-02-26 04:36:13.255 GMT [56M] INFO: !!! INFO: pihole-FTL has not been compiled with glibc/backtrace support, not generating one !!!
2025-02-26 04:36:13.255 GMT [56M] INFO: ------ Listing content of directory /dev/shm ------
2025-02-26 04:36:13.255 GMT [56M] INFO: File Mode User:Group      Size  Filename
2025-02-26 04:36:13.255 GMT [56M] INFO: rwxrwxrwx root:root       360   .
2025-02-26 04:36:13.255 GMT [56M] INFO: rwxr-xr-x root:root       340   ..
2025-02-26 04:36:13.255 GMT [56M] INFO: rw------- root:root       786K  FTL-56-recycler
2025-02-26 04:36:13.255 GMT [56M] INFO: rw------- root:root         4K  FTL-56-dns-cache-lookup
2025-02-26 04:36:13.255 GMT [56M] INFO: rw------- root:root        20K  FTL-56-domains-lookup
2025-02-26 04:36:13.255 GMT [56M] INFO: rw------- root:root         4K  FTL-56-clients-lookup
2025-02-26 04:36:13.256 GMT [56M] INFO: rw------- root:root       569K  FTL-56-fifo-log
2025-02-26 04:36:13.256 GMT [56M] INFO: rw------- root:root         4K  FTL-56-per-client-regex
2025-02-26 04:36:13.256 GMT [56M] INFO: rw------- root:root        20K  FTL-56-dns-cache
2025-02-26 04:36:13.256 GMT [56M] INFO: rw------- root:root         8K  FTL-56-overTime
2025-02-26 04:36:13.256 GMT [56M] INFO: rw------- root:root         7M  FTL-56-queries
2025-02-26 04:36:13.256 GMT [56M] INFO: rw------- root:root        29K  FTL-56-upstreams
2025-02-26 04:36:13.256 GMT [56M] INFO: rw------- root:root       348K  FTL-56-clients
2025-02-26 04:36:13.256 GMT [56M] INFO: rw------- root:root        70K  FTL-56-domains
2025-02-26 04:36:13.257 GMT [56M] INFO: rw------- root:root       123K  FTL-56-strings
2025-02-26 04:36:13.257 GMT [56M] INFO: rw------- root:root       144   FTL-56-settings
2025-02-26 04:36:13.257 GMT [56M] INFO: rw------- root:root       328   FTL-56-counters
2025-02-26 04:36:13.257 GMT [56M] INFO: rw------- root:root        88   FTL-56-lock
2025-02-26 04:36:13.257 GMT [56M] INFO: ---------------------------------------------------
2025-02-26 04:36:13.257 GMT [56M] INFO: Please also include some lines from above the !!!!!!!!! header.
2025-02-26 04:36:13.257 GMT [56M] INFO: Thank you for helping us to improve our FTL engine!
2025-02-26 04:36:13.257 GMT [56M] INFO: Waiting for threads to join
  [i] pihole-FTL exited with status 139
  [i] Container will now stop or restart depending on your restart policy
      https://docs.docker.com/engine/containers/start-containers-automatically/#use-a-restart-policy

These common fixes didn't work for my issue

  • I have tried removing/destroying my container, and re-creating a new container
  • I have tried fresh volume data by backing up and moving/removing the old volume data
  • I have tried running the stock docker run example(s) in the readme (removing any customizations I added)
  • I have tried a newer or older version of Docker Pi-hole (depending what version the issue started in for me)

Same issue with 2025.2.5 and 2025.2.4

  • I have tried running without my volume data mounts to eliminate volumes as the cause

If the above debugging / fixes revealed any new information note it here.
Add any other debugging steps you've taken or theories on root cause that may help.
@yubiuser yubiuser transferred this issue from pi-hole/docker-pi-hole Feb 26, 2025
@yubiuser
Copy link
Member

Thanks for your report. This will be fixed by #2240

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Fixed in next release
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mbirth @yubiuser