Okay, try sudo systemctl restart pihole-FTL and then check the logs to see what it looks like after a restart.
And a new pihole -d token URL would be good to see.
pihole -d still hanging at: *** [ DIAGNOSING ]: Discovering active DHCP servers (takes 10 seconds)
If a debug run doesn't complete then there's something else pretty wrong with the install.
Does pihole-FTL -vv show some results?
The piholes were working perfectly fine before the recent upgrade..
pihole-FTL -vv:
****************************** FTL **********************************
Version: v5.8
****************************** dnsmasq ******************************
Version: pi-hole-2.85
Compile options: IPv6 GNU-getopt no-DBus no-UBus no-i18n IDN DHCP DHCPv6 Lua TFTP no-conntrack ipset auth cryptohash DNSSEC loop-detect inotify dumpfile
****************************** SQLite3 ******************************
Version: 3.35.4
Compile options: COMPILER=gcc-6.3.0 20170516 DEFAULT_FOREIGN_KEYS OMIT_DEPRECATED OMIT_LOAD_EXTENSION OMIT_PROGRESS_CALLBACK THREADSAFE=1
******************************** LUA ********************************
Lua 5.4.1 Copyright (C) 1994-2020 Lua.org, PUC-Rio
And
sudo pihole-FTL dhcp-discover
Also just hangs?
Scanning all your interfaces for DHCP servers
Timeout: 10 seconds
WARN: Could not sendto() in send_dhcp_discover() (/root/project/src/dhcp-discover.c:223): Network is unreachable
* Received 309 bytes from eth0:192.168.10.1
Offered IP address: 192.168.10.3
Server IP address: 192.168.10.1
Relay-agent IP address: N/A
BOOTP server: (empty)
BOOTP file: (empty)
DHCP options:
Message type: DHCPOFFER (2)
server-identifier: 192.168.10.1
lease-time: 86400 ( 1d )
renewal-time: 43200 ( 12h )
rebinding-time: 75600 ( 21h )
netmask: 255.255.255.0
broadcast: 192.168.10.2
domain-name: "localdomain"
dns-server: 192.168.10.3
dns-server: 192.168.10.4
router: 192.168.10.1
--- end of options ---
* Received 300 bytes from eth0:192.168.10.1
DHCPOFFER XID (293301492) does not match our DHCPDISCOVER XID (884089454) - ignoring packet (not for us)
DHCP packets received on interface wlan0: 0
DHCP packets received on interface lo: 0
and it dies there...
That's almost at the very end. It's missing only a single line:
DHCP packets received on interface wlan0: 0
DHCP packets received on interface eth0: 1
I think we'll need to wait for someone with a bit more knowledge on pihole-FTL's internal workings. But that may take a little bit.
Ok. Hope you guys can get to the bottom of this mystery. Seems to be affecting quite a few people now?
I have the same problem after upgrade
Just an update. Been 12h since I nuked the DB and both piholes are still functioning perfectly.
This may not be missing because of
indicated that at least one of the interfaces (I guess eth0) was down and couldn't be used for probing at all.
I think the report is complete.
We have a bugfix around for the issue described earlier (the name column issues), it just awaits review/approval and merge (+ release as v5.8.1):
That is weird because that's the only interface that I use for the Pi. It shouldn't be down and unreachable.
Oh, I missed that. Sorry. What do you mean exactly with
? There isn't anything expected to come thereafter.
It doesn't finish and it just hangs there and doesn't send me back to the CLI prompt.
Same thing happens when I run pihole -d. It just hangs at the discovering DHCP..
Getting the very same issue on my RPI 3B+ after the last update.
Need to restart the services every X hours to fix web interface,
additionally looks like API are not working when interface is "out of order" (I am using Pi-Hole Remote iOS app and getting Pi-hole is not responding)
If it can be useful - There's a javascript error on page :
If I can be of any help to troubleshoot by providing logs or additional infos just let me know !
Maybe you can do a pihole -d and post the token here? That would be useful to the devs I think..
Sure , I just deleted and re-created FTL DB as suggested - Will see if it fix up things. If not, I'll share the diagnosis token during outage time
1 Like
Nearly 24 hours since the DB was nuked and everything seems to be working fine now.
Me too - Issue was happening in 1-2 hours after restart - I have nuked DB 6 hrs ago and no issues so far.
Talked too earlier - Issue appeared again out of nowhere...
Can see this in pihole-ftl.log :
[2021-04-18 17:57:00.558 3212/T3216] SQLite3 message: no such column: name in "UPDATE network_addresses SET name = NULL WHERE nameUpdated < 1587225420;" (1)
[2021-04-18 17:57:00.558 3212/T3216] ERROR: SQL query "UPDATE network_addresses SET name = NULL WHERE nameUpdated < 1587225420;" failed: SQL logic error
[2021-04-18 17:57:00.559 3212/T3216] SQLite3 message: API call with invalid database connection pointer (21)
[2021-04-18 17:57:00.559 3212/T3216] SQLite3 message: misuse at line 165242 of [5d4c65779d] (21)
[2021-04-18 17:57:00.559 3212/T3216] Error while trying to close database: bad parameter or other API misuse
So looks like a DB issue to me.