Good morning, Dan. Presently, I'm running pihole-FTL under debug -- restarted as DL6ER suggested. Shall I assume if I open another window to do that that would be OK? One won't interfere with the other, will it?
It shouldn't, you'd just be reading the log file so no locking of anything should take place. Just want to check and see if there were any indicators prior to the engine falling over earlier.
OK. Tnx once again. Token is bcjb8rkj4f .
Thanks. I do see some of the init killing the process.
[2017-05-02 07:00:13.969] FATAL: FTL received SIGTERM from PID/UID 10112/0, scheduled to exit gracefully
[2017-05-02 07:00:13.969] Shutting down...
[2017-05-02 07:00:13.970] ########## FTL terminated! ##########
Interesting. The memory usage is climbing fairly rapidly. About 11% when it was booted, now 28%. (log file = 697.73kB.)
On the settings page, PiHole FTL indicates Memory utilization is 16.0% but used memory is 145.14MB.
The card is a 32GB card.
Does that seem right?
How does free look?
Mem: Total 945520 Used 494808 Free 450712 Shared 13004 Buffers 43388
That doesn't look too off the mark for now. If you could keep an eye on it and see how it behaves as time goes on though.
That is already quite a lot - and it is more than pihole.log (which should not happen).
You could go to the window now that has pihole-FTL open in the debugger and do a [Ctrl] + [C] to interrupt FTL. The debugger will it keep running, but paused. You will reach the debuggers interpreter line (gdb)
Please do
print counters
print memory
and post the results (or show screenshots, or whatever is most convenitent for you).
You can then let FTL continue where you interrupted it with
continue
OK. Just I have the results -- trying to figure out how to copy/paste between RDT and anytjhihng else. ;<)
OK, I'll do this manually ...
print counters
$1 = {queries = 7646. invalid queries = 880. blocked = 169.
wildcardblocked = 0. cached 3466. unknown = 0. forwarded = 2. clients = 6
domains = 192. Queries_MAX = 10000. forwarded+MAX = 4. clients_MAX = 10.
domains_MAX = 1000. overtime_MAX = 300. gravity = 104740. overTime = 205.
IPv4 = 5030. IPv6 = 1736. PTR = 0. SRV = 0. windcarddomains = -1.
forwarded queries = 3131}
print memory
$2 [wildcarddomains = 0. domainnames = 4157. clientips = 82.
clientnames = 15. forwardedips = 30. forwardednames = 44. forwarddata = 410.
quit
Note: "Memory usage" in PiHole "status" in web UI is 29.0% and climbing slowly from about 11% after this morning's reboot.
That all looks fine. Please try to switch to debug mode so that FTL becomes a bit more verbose. I never tried to do this online, but you may be able to achieve it using
set variable debug = 1
continue
once you interrupted FTL.
Browse to some site you have not have opened before and you should see some output like
[2017-05-04 16:26:07.881] New domain: 1.gravatar.com (1454/2000)
Let's see if strange behavior becomes apparent like this.
Thanks!
Let's wait for if memory allocation messages pop up (they look like the following).
[2017-05-04 14:00:14.720] Notice: Increasing queries struct size from 20000 to 30000 (1.04 MB)
[2017-05-04 14:00:14.721] at query time: May 4 14:00:14
Might be tough to see given that the screen is almost constantly scrolling -- messages as to new threads and threads exited.
I'll do my best. :<)
It will log the interesting lines into /var/log/pihole-FTL.log, so you don't have to watch your screen all of the time 
and: those messages go away if you close all browser windows that show the dashboard
It sounds likely that you see the same issue these guys are seeing:
Please also have a look at my answer there. Maybe one of you finds something I can work one once I'm back.
Yes, I see that. Well, at least I don't feel alone. ;<)
I don't see any of the memory allocation messages as you describe in /var/log/pihole-FTL.log -- but I may have done something wrong.
As I write this, the UI is showing Memory usage to be 86.2% (with red icon) and it's increasing. I'm going to reboot while I can still get RDT to work-- hoping to keep it running overnight.
Thanks for working on this! :<)
Rick
Please update to FTL v2.6.2.
1 Like
Hi. That did it! :<)
Memory usage is stable at roughly 10.7% and the UI is quite responsive. Working perfectly again! (Using PH 3.0.1; Web interface 3.0.1a; FTL 2.6.2.)
Thanks for squashing the bug! :<)