Please explain what is pihole-FTL doing during reboot

Please follow the below template, it will help us to help you!

Please ensure that you are running the latest version of the beta code.
Run pihole -up to update to the latest, then verify that the problem still exists before reporting it.

Problem with Beta 5.0:
at every reboot pihole-FTL takes 100% of cpu on pizero wireless, for a good 4-5 minutes. but the ram stays at 65 M out of 480 M. Afterwards everything is fine and the dns resolving works like butter. But every reboot is taking a good 5 min of wait time for network resolutions to work.

Debug Token:
[Replace this text with the debug token provided from running pihole -d (or running the debug script through the web interface]

FTL is computing the number of distinct domains on the blocking lists. This takes much more time than anticipated on low(est)-end hardware. There is already a discussion about this (including a proposed solution!) here:

Please run

pihole checkout core tweak/gravity_count
pihole -g
pihole checkout ftl tweak/gravity_count

and check again if you still see the delay.

1 Like

If I switch branches, will any new changes done to the main beta branch will also be available in this branch?
At some point how will I know when to switch back to the main branch?

I'll test and let you know. Thanks.

It's almost instant on reboot. Magical. Thanks.

I'll try to think about notifying you. Best is you monitor the other discussion I referenced.

Happened now. Please go back on track using

pihole checkout core release/v5.0
pihole checkout ftl release/v5.0

Thank you very much.

1 Like