Pihole segmentation fault with first DNS query

General Beta 5.0
1

Problem with Beta 5.0:
Fresh install on pihole zero W with defaults. Segmentaion fault with first query ie dig @localhost google.com

Have tried uninstalling and reinstalling again. (note the uninstall failed to remove the pihole group for both 4.3.2 and beta 5 so this had to be done manually before reinstalling)

/var/log/pihole-FTL.log:
[2020-01-29 11:37:20.694 18387] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[2020-01-29 11:37:20.695 18387] ----------------------------> FTL crashed! <----------------------------
[2020-01-29 11:37:20.695 18387] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[2020-01-29 11:37:20.695 18387] Please report a bug at GitHub · Where software is built
[2020-01-29 11:37:20.696 18387] and include in your report already the following details:
[2020-01-29 11:37:20.696 18387] FTL has been running for 35 seconds
[2020-01-29 11:37:20.696 18387] FTL branch: release/v5.0
[2020-01-29 11:37:20.697 18387] FTL version: vDev-44b772b
[2020-01-29 11:37:20.697 18387] FTL commit: 44b772b
[2020-01-29 11:37:20.697 18387] FTL date: 2020-01-28 19:22:34 +0100
[2020-01-29 11:37:20.697 18387] FTL user: started as pihole, ended as pihole
[2020-01-29 11:37:20.698 18387] Compiled for arm (compiled on CI) using arm-linux-gnueabihf-gcc (crosstool-NG crosstool-ng-1.22.0-88-g8460611) 4.9.3
[2020-01-29 11:37:20.698 18387] Received signal: Segmentation fault
[2020-01-29 11:37:20.698 18387] at address: 0x226
[2020-01-29 11:37:20.698 18387] with code: SEGV_MAPERR (Address not mapped to object)
[2020-01-29 11:37:20.698 18387] Backtrace:
[2020-01-29 11:37:20.699 18387] B[0000]: 0x4d1a54, /usr/bin/pihole-FTL(+0x2ba54) [0x4d1a54]
[2020-01-29 11:37:20.700 18387] B[0001]: 0xb6db4130, /lib/arm-linux-gnueabihf/libc.so.6(__default_rt_sa_restorer+0) [0xb6db4130]
[2020-01-29 11:37:20.700 18387] ------ Listing content of directory /dev/shm ------

Debug Token:
https://tricorder.pi-hole.net/rhjxct4eqo

1 Like
16

This is what I get with screen:

Thread 1 "pihole-FTL" received signal SIGSEGV, Segmentation fault.
0x00571590 in nettle_sha1_init ()
(gdb) backtrace
#0 0x00571590 in nettle_sha1_init ()
#1 0x0057158e in nettle_sha1_init ()
#2 0x0057158e in nettle_sha1_init ()
#3 0x0057158e in nettle_sha1_init ()
#4 0x0057158e in nettle_sha1_init ()
#5 0x0057158e in nettle_sha1_init ()
#6 0x0057158e in nettle_sha1_init ()

2 Likes
20

OK seems this report is what is happening with user richie510 in their post "Pihole update failure", also on a pi zero.

Would a backup/rollback option be worth considering for a pihole -up to easily get back to a workable version once the troubleshooting is done?

Keep up the good work. Thanks.

1 Like