The issue I am facing: Was nslookup timeouts but got resolved but some debug entries don't look good
Details about my system:
Docker Tag 2024.05.0
Pi-hole v5.18.2
FTL v5.25.2
Web Interface v5.21
What I have changed since installing Pi-hole: Pihole is running on k3s on Raspberry Pie. That Pie was reinstalled. I had also different MTU in LAN 8100 so I thought it was its fault but I was wrong although I restore MTU to 1500 and never ever touching that again, more problems than benefits.
I saw that topic Why Pi-hole DNS request timed out and there was issue with interface name and pihole probably bind to a different device though I couldn't check that in my log is it also that way. So I removed pihole pods and they were recreated and nslookup works fine now. But After that, when pihole came back I generated debug here https://tricorder.pi-hole.net/rf6vYEoB/ . If someone could look at it. Because there are some errors and I don't know if they are irrelevant. Why when entering it I see white page?
The SQL errors in your debug log are related only to the long-term database:
[2024-08-29 11:23:00.084 232/T283] Encountered error while trying to store client in long-term database
[2024-08-29 11:23:00.084 232/T283] Statement finalization failed when trying to store queries to long-term database
[2024-08-29 11:23:00.084 232/T283] Error while trying to close database: database is locked
[2024-08-29 11:23:00.090 232/T283] ERROR: SQL query "DELETE FROM network_addresses WHERE lastSeen < 1693387380;" failed: database is locked (SQLITE_BUSY)
[2024-08-29 11:24:01.082 232/T283] ERROR: SQL query "END TRANSACTION" failed: database is locked (SQLITE_BUSY)
[2024-08-29 11:24:01.082 232/T283] END TRANSACTION failed when trying to store queries to long-term database
[2024-08-29 11:24:01.082 232/T283] Keeping queries in memory for later new attempt
[2024-08-29 11:24:02.130 232/T283] ERROR: SQL query "END TRANSACTION" failed: database is locked (SQLITE_BUSY)
[2024-08-29 11:24:02.131 232/T283] WARNING: Storing devices in network table failed: database is locked
[2024-08-29 11:25:01.018 232/T283] ERROR: SQL query "END TRANSACTION" failed: database is locked (SQLITE_BUSY)
[2024-08-29 11:25:01.018 232/T283] END TRANSACTION failed when trying to store queries to long-term database
[2024-08-29 11:25:01.018 232/T283] Keeping queries in memory for later new attempt
[2024-08-29 11:25:02.062 232/T283] ERROR: SQL query "END TRANSACTION" failed: database is locked (SQLITE_BUSY)
[2024-08-29 11:25:02.062 232/T283] WARNING: Storing devices in network table failed: database is locked
The error database is locked (SQLITE_BUSY) is only a temporary issue.
The queries are kept in memory and as soon as the system is able to write to the database file, these queries are stored in the database.