FTL crash "Received signal: Segmentation fault" v5 beta on Raspberry Pi (FTL version vDev-44b772b)

[tintim]

In raising this issue, I confirm the following (please check boxes, eg [X]) Failure to fill the template will close your issue:

• I have read and understood the contributors guide.
• The issue I am reporting can be replicated
• The issue I am reporting isn't a duplicate

How familiar are you with the codebase?:

2 - happy working with linux OS
Fairly new to Pi-hole
Strong networking and DNS experience

[BUG | ISSUE] Expected Behaviour:
Core / Web and FTL updated

[BUG | ISSUE] Actual Behaviour:
FTL crashes and fails

[✗] DNS resolution is currently unavailable
[✗] DNS resolution is not available
Unable to complete update, please contact Pi-hole Support

[BUG | ISSUE] Steps to reproduce:

• update pihole via command line (pihole -up)

I have two Pi-Hole running (+1 is on a FreeNAS VM, Ubuntu Server), this only affects the Pi-hole on Raspberry Pi. both are running the same beta version. Thanks

Log file output [if available]

-----tail of pihole-FTL.log------
[2020-01-29 08:48:00.784 453] ----------------------------> FTL crashed! <----------------------------
[2020-01-29 08:48:00.784 453] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[2020-01-29 08:48:00.784 453] Please report a bug at https://github.com/pi-hole/FTL/issues
[2020-01-29 08:48:00.785 453] and include in your report already the following details:
[2020-01-29 08:48:00.785 453] FTL has been running for 83 seconds
[2020-01-29 08:48:00.785 453] FTL branch: release/v5.0
[2020-01-29 08:48:00.785 453] FTL version: vDev-44b772b
[2020-01-29 08:48:00.786 453] FTL commit: 44b772b
[2020-01-29 08:48:00.786 453] FTL date: 2020-01-28 19:22:34 +0100
[2020-01-29 08:48:00.787 453] FTL user: started as pihole, ended as pihole
[2020-01-29 08:48:00.787 453] 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 08:48:00.787 453] Received signal: Segmentation fault
[2020-01-29 08:48:00.787 453] at address: 0x226
[2020-01-29 08:48:00.788 453] with code: SEGV_MAPERR (Address not mapped to object)
[2020-01-29 08:48:00.788 453] Backtrace:
[2020-01-29 08:48:00.789 453] B[0000]: 0x451a54, /usr/bin/pihole-FTL(+0x2ba54) [0x451a54]
[2020-01-29 08:48:00.790 453] B[0001]: 0xb6d5d130, /lib/arm-linux-gnueabihf/libc.so.6(__default_rt_sa_restorer+0) [0xb6d5d130]
[2020-01-29 08:48:00.790 453] ------ Listing content of directory /dev/shm ------
[2020-01-29 08:48:00.790 453] File Mode User:Group Filesize Filename
[2020-01-29 08:48:00.791 453] rwxrwxrwx root:root 260 .
[2020-01-29 08:48:00.792 453] rwxr-xr-x root:root 4K ..
[2020-01-29 08:48:00.793 453] rw------- pihole:pihole 4K FTL-per-client-regex
[2020-01-29 08:48:00.794 453] rw------- pihole:pihole 12K FTL-dns-cache
[2020-01-29 08:48:00.795 453] rw------- pihole:pihole 53K FTL-overTime
[2020-01-29 08:48:00.796 453] rw------- pihole:pihole 786K FTL-queries
[2020-01-29 08:48:00.797 453] rw------- pihole:pihole 20K FTL-forwarded
[2020-01-29 08:48:00.797 453] rw------- pihole:pihole 20K FTL-clients
[2020-01-29 08:48:00.798 453] rw------- pihole:pihole 66K FTL-domains
[2020-01-29 08:48:00.799 453] rw------- pihole:pihole 25K FTL-strings
[2020-01-29 08:48:00.800 453] rw------- pihole:pihole 12 FTL-settings
[2020-01-29 08:48:00.801 453] rw------- pihole:pihole 120 FTL-counters
[2020-01-29 08:48:00.802 453] rw------- pihole:pihole 28 FTL-lock
[2020-01-29 08:48:00.802 453] ---------------------------------------------------
[2020-01-29 08:48:00.802 453] Thank you for helping us to improve our FTL engine!
[2020-01-29 08:48:00.803 453] FTL terminated!

Device specifics

Hardware Type: rPi, VPS, etc
OS: rPi

This template was created based on the work of udemy-dl.

[DL6ER]

Thanks, we've seen some reports related to this and already have a good idea what might be causing the issue (newly built CI containers). We're looking at replacing the CI images with previous ones and report back.

Thanks for using the Pi-hole!

[DL6ER]

Fixed by #684 @tintim Please update your Pi-hole.

[tintim]

Thank you @DL6ER updated successfully following a minor edit to the /etc/resolv.conf