Version 4.2 pihole service and lighttped keep crashing

#6

I already update FTL to lastet version still crash
Debug token id: vers0xvonm

[2019-02-09 16:36:29.796] B[0006]: /usr/bin/pihole-FTL(main_dnsmasq+0xfdc) [0x5570a809675c]
[2019-02-09 16:36:29.796] B[0007]: /usr/bin/pihole-FTL(main+0xbc) [0x5570a805d74c]
[2019-02-09 16:36:29.796] B[0008]: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xeb) [0x7fcf323d509b]
[2019-02-09 16:36:29.796] B[0009]: /usr/bin/pihole-FTL(_start+0x2a) [0x5570a805d87a]
[2019-02-09 16:36:29.796] Thank you for helping us to improve our FTL engine!
[2019-02-09 16:36:29.796] FTL terminated!
[2019-02-09 16:36:30.878] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[2019-02-09 16:36:30.878] ---------------------------->  FTL crashed!  <----------------------------
[2019-02-09 16:36:30.878] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[2019-02-09 16:36:30.878] Please report a bug at https://github.com/pi-hole/FTL/issues
[2019-02-09 16:36:30.878] and include in your report already the following details:

[2019-02-09 16:36:30.878] FTL has been running for 629 seconds
[2019-02-09 16:36:30.878] FTL branch: master
[2019-02-09 16:36:30.878] FTL version: v4.2.1
[2019-02-09 16:36:30.878] FTL commit: 5f98312
[2019-02-09 16:36:30.878] FTL date: 2019-02-06 18:36:55 -0800
[2019-02-09 16:36:30.878] FTL user: started as pihole, ended as pihole
[2019-02-09 16:36:30.879] Received signal: Segmentation fault
[2019-02-09 16:36:30.879]      at address: 0
[2019-02-09 16:36:30.879]      with code: Unknown (128),
[2019-02-09 16:36:30.879] Backtrace:
[2019-02-09 16:36:30.879] B[0000]: /usr/bin/pihole-FTL(+0x254a8) [0x5570a805f4a8]
[2019-02-09 16:36:30.879] B[0001]: /lib/x86_64-linux-gnu/libpthread.so.0(+0x126e0) [0x7fcf325846e0]
[2019-02-09 16:36:30.879] B[0002]: /usr/bin/pihole-FTL(findDomainID+0x95) [0x5570a805ef35]
[2019-02-09 16:36:30.879] B[0003]: /usr/bin/pihole-FTL(FTL_new_query+0x4ff) [0x5570a8068f6f]
[2019-02-09 16:36:30.879] B[0004]: /usr/bin/pihole-FTL(tcp_request+0x2d8) [0x5570a807dcb8]
[2019-02-09 16:36:30.879] B[0005]: /usr/bin/pihole-FTL(+0x5abf4) [0x5570a8094bf4]
[2019-02-09 16:36:30.879] B[0006]: /usr/bin/pihole-FTL(main_dnsmasq+0xfdc) [0x5570a809675c]
[2019-02-09 16:36:30.879] B[0007]: /usr/bin/pihole-FTL(main+0xbc) [0x5570a805d74c]
[2019-02-09 16:36:30.879] B[0008]: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xeb) [0x7fcf323d509b]
[2019-02-09 16:36:30.879] B[0009]: /usr/bin/pihole-FTL(_start+0x2a) [0x5570a805d87a]
[2019-02-09 16:36:30.879] Thank you for helping us to improve our FTL engine!
[2019-02-09 16:36:30.879] FTL terminated!
[2019-02-09 16:37:02.089] Using log file /var/log/pihole-FTL.log
[2019-02-09 16:37:02.089] ########## FTL started! ##########
[2019-02-09 16:37:02.089] FTL branch: master
[2019-02-09 16:37:02.089] FTL version: v4.2.1
[2019-02-09 16:37:02.089] FTL commit: 5f98312
[2019-02-09 16:37:02.089] FTL date: 2019-02-06 18:36:55 -0800
[2019-02-09 16:37:02.089] FTL user: pihole
[2019-02-09 16:37:02.089] Starting config file parsing (/etc/pihole/pihole-FTL.conf)
[2019-02-09 16:37:02.089]    SOCKET_LISTENING: only local
[2019-02-09 16:37:02.089]    AAAA_QUERY_ANALYSIS: Show AAAA queries
[2019-02-09 16:37:02.089]    MAXDBDAYS: --- (DB disabled)
[2019-02-09 16:37:02.089]    RESOLVE_IPV6: Resolve IPv6 addresses
[2019-02-09 16:37:02.089]    RESOLVE_IPV4: Resolve IPv4 addresses
[2019-02-09 16:37:02.089]    DBINTERVAL: saving to DB file every minute
[2019-02-09 16:37:02.089]    DBFILE: Using /etc/pihole/pihole-FTL.db
[2019-02-09 16:37:02.089]    MAXLOGAGE: Importing up to 24.0 hours of log data
[2019-02-09 16:37:02.089]    PRIVACYLEVEL: Set to 0
[2019-02-09 16:37:02.089]    IGNORE_LOCALHOST: Show queries from localhost
[2019-02-09 16:37:02.089]    BLOCKINGMODE: Null IPs for blocked domains
[2019-02-09 16:37:02.089]    REGEX_DEBUGMODE: Inactive
[2019-02-09 16:37:02.089]    ANALYZE_ONLY_A_AND_AAAA: Disabled. Analyzing all queries
[2019-02-09 16:37:02.089]    DBIMPORT: Importing history from database
[2019-02-09 16:37:02.089]    PIDFILE: Using /var/run/pihole-FTL.pid
[2019-02-09 16:37:02.089]    PORTFILE: Using /var/run/pihole-FTL.port
[2019-02-09 16:37:02.089]    SOCKETFILE: Using /var/run/pihole/FTL.sock
[2019-02-09 16:37:02.089]    WHITELISTFILE: Using /etc/pihole/whitelist.txt
[2019-02-09 16:37:02.089]    BLACKLISTFILE: Using /etc/pihole/black.list
[2019-02-09 16:37:02.089]    GRAVITYFILE: Using /etc/pihole/gravity.list
[2019-02-09 16:37:02.089]    REGEXLISTFILE: Using /etc/pihole/regex.list
[2019-02-09 16:37:02.089]    SETUPVARSFILE: Using /etc/pihole/setupVars.conf
[2019-02-09 16:37:02.089]    AUDITLISTFILE: Using /etc/pihole/auditlog.list
[2019-02-09 16:37:02.089] Finished config file parsing
[2019-02-09 16:37:02.089] Skipping commented out regex filter on line 1
[2019-02-09 16:37:02.089] Skipping commented out regex filter on line 2
[2019-02-09 16:37:02.089] Skipping commented out regex filter on line 3
[2019-02-09 16:37:02.089] Compiled 0 Regex filters and 976 whitelisted domains in 0.2 msec (0 errors)
[2019-02-09 16:37:02.089]  -> Total DNS queries: 0
[2019-02-09 16:37:02.089]  -> Cached DNS queries: 0
[2019-02-09 16:37:02.089]  -> Forwarded DNS queries: 0
[2019-02-09 16:37:02.089]  -> Exactly blocked DNS queries: 0
[2019-02-09 16:37:02.089]  -> Unknown DNS queries: 0
[2019-02-09 16:37:02.089]  -> Unique domains: 0
[2019-02-09 16:37:02.089]  -> Unique clients: 0
[2019-02-09 16:37:02.089]  -> Known forward destinations: 0
[2019-02-09 16:37:02.089] Successfully accessed setupVars.conf
[2019-02-09 16:37:02.101] PID of FTL process: 20805
[2019-02-09 16:37:02.101] Listening on port 4711 for incoming IPv4 telnet connections
[2019-02-09 16:37:02.101] Listening on port 4711 for incoming IPv6 telnet connections
[2019-02-09 16:37:02.101] Listening on Unix socket
[2019-02-09 16:37:02.101] Skipping commented out regex filter on line 1
[2019-02-09 16:37:02.101] Skipping commented out regex filter on line 2
[2019-02-09 16:37:02.101] Skipping commented out regex filter on line 3
[2019-02-09 16:37:02.102] Compiled 0 Regex filters and 976 whitelisted domains in 0.6 msec (0 errors)
[2019-02-09 16:37:02.102] /etc/pihole/black.list: parsed 246 domains (took 0.2 ms)
[2019-02-09 16:37:03.740] /etc/pihole/gravity.list: parsed 581813 domains (took 1637.9 ms)
[2019-02-09 16:37:03.740] FATAL ERROR: Trying to access queries[-1], but maximum is 4096
[2019-02-09 16:37:03.740]              found in findQueryID() (dnsmasq_interface.c:230)
[2019-02-09 16:37:03.740] FATAL ERROR: Trying to access queries[-1], but maximum is 4096
[2019-02-09 16:37:03.740]              found in findQueryID() (dnsmasq_interface.c:230)
[2019-02-09 16:37:03.740] FATAL ERROR: Trying to access queries[-1], but maximum is 4096
[2019-02-09 16:37:03.740]              found in findQueryID() (dnsmasq_interface.c:230)
[2019-02-09 16:37:03.740] FATAL ERROR: Trying to access queries[-1], but maximum is 4096
[2019-02-09 16:37:03.740]              found in findQueryID() (dnsmasq_interface.c:230)
[2019-02-09 16:37:03.741] FATAL ERROR: Trying to access queries[-1], but maximum is 4096
[2019-02-09 16:37:03.741]              found in findQueryID() (dnsmasq_interface.c:230)
[2019-02-09 16:37:03.741] FATAL ERROR: Trying to access queries[-1], but maximum is 4096
[2019-02-09 16:37:03.741]              found in findQueryID() (dnsmasq_interface.c:230)
[2019-02-09 16:37:03.741] FATAL ERROR: Trying to access queries[-1], but maximum is 4096
[2019-02-09 16:37:03.741]              found in findQueryID() (dnsmasq_interface.c:230)
[2019-02-09 16:37:03.750] New forward server: 2620:fe::fe (0/4096)
[2019-02-09 16:37:34.058] Resizing "/FTL-strings" from 4096 to 8192
[2019-02-09 16:37:48.198] Resizing "/FTL-strings" from 8192 to 12288
[2019-02-09 16:38:20.582] Resizing "/FTL-strings" from 12288 to 16384
[2019-02-09 16:38:52.661] Resizing "/FTL-strings" from 16384 to 20480
[2019-02-09 16:39:05.846] Resizing "/FTL-strings" from 20480 to 24576
[2019-02-09 16:39:20.623] Resizing "/FTL-strings" from 24576 to 28672
[2019-02-09 16:39:33.898] Resizing "/FTL-strings" from 28672 to 32768
[2019-02-09 16:39:43.834] Resizing "/FTL-strings" from 32768 to 36864
[2019-02-09 16:40:15.077] Resizing "/FTL-strings" from 36864 to 40960
[2019-02-09 16:40:48.266] Resizing "/FTL-strings" from 40960 to 45056
[2019-02-09 16:41:03.952] Resizing "/FTL-queries" from 294912 to 589824
[2019-02-09 16:41:05.597] Resizing "/FTL-strings" from 45056 to 49152
[2019-02-09 16:41:25.318] Resizing "/FTL-strings" from 49152 to 53248
[2019-02-09 16:41:40.031] Resizing "/FTL-strings" from 53248 to 57344
[2019-02-09 16:42:10.647] Resizing "/FTL-strings" from 57344 to 61440
[2019-02-09 16:42:42.766] Resizing "/FTL-strings" from 61440 to 65536
[2019-02-09 16:43:26.255] Resizing "/FTL-strings" from 65536 to 69632
[2019-02-09 16:43:54.653] Resizing "/FTL-strings" from 69632 to 73728
[2019-02-09 16:44:08.934] Resizing "/FTL-strings" from 73728 to 77824
[2019-02-09 16:44:21.201] Resizing "/FTL-queries" from 589824 to 884736
[2019-02-09 16:44:30.597] Resizing "/FTL-strings" from 77824 to 81920
[2019-02-09 16:44:45.023] Resizing "/FTL-strings" from 81920 to 86016
[2019-02-09 16:45:08.382] Resizing "/FTL-strings" from 86016 to 90112
[2019-02-09 16:45:51.929] Resizing "/FTL-strings" from 90112 to 94208
[2019-02-09 16:46:06.220] Resizing "/FTL-strings" from 94208 to 98304
[2019-02-09 16:46:20.846] Resizing "/FTL-strings" from 98304 to 102400
[2019-02-09 16:46:27.774] Resizing "/FTL-domains" from 131072 to 262144
[2019-02-09 16:46:48.864] Resizing "/FTL-strings" from 102400 to 106496
[2019-02-09 16:47:21.856] Resizing "/FTL-strings" from 106496 to 110592
[2019-02-09 16:47:34.584] Resizing "/FTL-queries" from 884736 to 1179648
[2019-02-09 16:47:40.095] Resizing "/FTL-strings" from 110592 to 114688
[2019-02-09 16:47:54.550] Resizing "/FTL-strings" from 114688 to 118784
[2019-02-09 16:48:11.588] Resizing "/FTL-strings" from 118784 to 122880
0 Likes

#7

Can you share the rest of the first error in the log you shared? It does not appear in your debug log.

1 Like

#10

Hi,

My debug token is: x6ifos9x0g

0 Likes

#14

We’re testing some fixes for issues seen on v4.2.1, it would be helpful to know if you still experience these issues on this branch:

pihole checkout ftl tweak/overhaul_overTime
0 Likes

#15

Ok, Will try for 1 day and let you know

0 Likes

#16

Hi,

Unfortunately, no crash, but the FTL service become not responding. If I dig google.com, It return SERVFAIL.
My debug token is: elzkas8abu

0 Likes

#17

Just now crashed again
debug token is: elcddyvvtu

0 Likes

#18

There have been other users with crashes when running FTL alongside dnscrypt:

Try turning off dnscrypt, and see if you get any more crashes. Also, there is a new change in the branch which will fix these warning messages you see (you can re-run the checkout command to update):

[2019-02-14 21:59:00.056] WARN: overTime timeidx correction failed (4532: 0 / 6)
0 Likes

#19

I think this is not the issue
Because my pihole upstream forwarder is point to Quad9 IPv6 (filtered) and caused pihole crash.
But I change my upstream with Unbound or Knot-resolver, everything working fine.

I dont know what cause this happen? Any idea?

0 Likes

#20

Run the checkout command again to get the latest version of the fix branch. If FTL crashes, share the crash log located in /var/log/pihole-FTL.log.

0 Likes

#21

My debug token is: qaynoa526v
I got the lastest version of FTL
pihole-FTL.log: https://privatebin.net/?cb4d216669d916b5#kNYEBUOkPmbU85o23DolYLyQEvB0SJt4kCVXzisusB4=

0 Likes

#22

That’s definitely the problem I’ve been having. With the 2 combined Pi-hole crashes in less than a day. Updated FTL just now, fingers crossed!

0 Likes

#23

Try updating to v4.2.2, we may have fixed the crash you saw:

pihole checkout master
0 Likes

#24

@Mcat12 Thank you very much for the great work.

1 Like

#25

@Mcat12 Oh no!!! :(((
The “overhaul_overTime” works the last days without any crash. Now with 4.2.2 (master) it crashes within minutes again :frowning:

My token: db2wxofjeu (after reboot)

0 Likes

#29

v4.2.2 is just the released version of tweak/overhaul_overTime. I do not see any issues in your debug log, due to you rebooting. If you see crashes in /var/log/pihole-FTL.log, then share them.

0 Likes

#31

Hi,
I updated to latest version, but still crash couple times.
My debug token is: wavy78icdq

0 Likes

Lighttpd crash on Debian9 sid
#32

This thread will continue in Lighttpd crash on Debian9 sid, because you created a second post.

1 Like

split this topic #33

2 posts were split to a new topic: Pi-Hole V4.2 crashes on Ubuntu

0 Likes

closed #34

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.

0 Likes