Database is locked error

[aurtiks2005]

Expected Behaviour:

Proper deletion of unreachable ad-lists from Pi-hole diagnosis page. Besides that domains should be added to whitelist or blacklist without these errors.

Actual Behaviour:

It's possible to delete unreachable ad-lists from Pi-hole diagnosis page, but they appear again after reboot and sometimes web interface show "Database is locked" error during deletion. Also there are errors in FTL log
cat /var/log/pihole/FTL.log | grep -c "database is locked"
8

Debug Token:

https://tricorder.pi-hole.net/OnagWT8b/

Additional info:

groups www-data
www-data : www-data pihole


stat /var/www/html/
  File: /var/www/html/
  Size: 4096            Blocks: 8          IO Block: 4096   directory
Device: b301h/45825d    Inode: 133709      Links: 3
Access: (0775/drwxrwxr-x)  Uid: (   33/www-data)   Gid: (   33/www-data)
Access: 2023-08-17 13:58:18.466690785 +0200
Modify: 2023-08-17 14:00:23.439465417 +0200
Change: 2023-08-17 14:03:46.602222077 +0200
 Birth: 2023-08-17 13:58:18.466690785 +0200


ls -lah /etc/pihole/gravity.db
-rw-rw-r-- 1 pihole pihole 486M Aug 17 21:46 /etc/pihole/gravity.db


grep pihole /etc/group
pihole:x:995:www-data
pihole:x:1005:www-data


grep pihole /etc/passwd
pihole:x:999:1005::/home/pihole:/usr/sbin/nologin


grep pihole /etc/sudoers.d/pihole
www-data ALL=NOPASSWD: /usr/local/bin/pihole


sqlite3 /etc/pihole/pihole-FTL.db "PRAGMA integrity_check;"
ok

Also I searched through these topics

Database issue: attempt to write a readonly database

Fixed with: chown pihole:www-data -R /var/www/html/ chmod 0775 -R /var/www/html/

Database locked (dashboard and query log are empty)

The issue I am facing: I noted today that the dashboard is empty, as well as the query log. Tools --> Tail pihole.log and pihole-FTL.log are not showing anything either. When I run tail pihole-FTL.log from command line, I get: [2021-01-19 22:27:31.654 1306/T1310] SQLite3 message: file unlinked while open: /etc/pihole/gravity.db (28) [2021-01-19 22:27:31.707 1306/T1310] Compiled 0 whitelist and 0 blacklist regex filters for 0 clients in 1.2 msec [2021-01-19 22:30:01.174 1306/T1310] ERROR: SQL…

Database lock messages in FTL log

Not sure if this is actually an issue, but am curious what might be going on. This morning my pi-hole was not processing DNS for about 1.5h until I rebooted it. Looks like FTL must have crashed. I also updated this morning after that occurred since I saw there was an update available. Here's current FTL log. The actual outage was between about 6:25am to 7:40am. =/ I don't see any segfaults, or any other warnings of what actually happened.... Any thoughts on what might have gone sideways? FTL…

SQL error prepare: database is locked

Expected Behaviour: Running an standard installation that listens on both wired and wireless interfaces. PiHole works but hangs after a few days. Actual Behaviour: FTL log keeps showing errors about the database being locked, for example "SQLite3 message: database is locked in "SELECT hwaddr FROM network WHERE id = (SELECT network_id FROM network_addresses WHERE ip = ? GROUP BY ip HAVING max(lastSeen));" (5)" Tried to reboot but it doesn't help. Debug Token: https://tricorder.pi-hole.net/…

https://discourse.pi-hole.net/t/database-locked-again/63672
but no luck.

[Bucking_Horn]

@aurtiks2005

It's possible to delete unreachable ad-lists from Pi-hole diagnosis page, but they appear again (...)

That is the expected behaviour.

You are just clearing the messages about unreachable adlists.
The adlists themselves stay as they are.
If you should decide to remove adlists (e.g. because they are no longer maintained and accessible), you should do so via Pi-hole's Adlist group management.

[aurtiks2005]

@Bucking_Horn

You are just clearing the messages about unreachable adlists.

Now I see, thank you!

But during blocklist deletion from /admin/groups-adlists.php I faced with one database error. Looks like these log's records were made at the same time:

cat /var/log/pihole/FTL.log
..................................
[2023-08-18 13:27:13.233 1165/T1298] Blocking status is enabled
[2023-08-18 13:27:19.566 1165M] Received: Real-time signal 0 (34 -> 0)
[2023-08-18 13:27:19.668 1165/T1298] Compiled 1 whitelist and 0 blacklist regex filters for 6 clients in 20.9 msec
[2023-08-18 13:27:19.668 1165/T1298] ADLIST WARNING: Adlist with ID 17 (https://schakal.ru/hosts/hosts.txt) was inaccessible during last gravity run
[2023-08-18 13:27:20.308 1165/T1298] ADLIST WARNING: Adlist with ID 85 (https://v.firebog.net/hosts/static/w3kbl.txt) was inaccessible during last gravity run
[2023-08-18 13:27:20.460 1165/T1298] Blocking status is enabled
[2023-08-18 13:27:24.462 1165M] Received: Real-time signal 0 (34 -> 0)
[2023-08-18 13:27:24.517 1165/T1298] Compiled 1 whitelist and 0 blacklist regex filters for 6 clients in 42.8 msec
[2023-08-18 13:27:24.518 1165/T1298] ADLIST WARNING: Adlist with ID 17 (https://schakal.ru/hosts/hosts.txt) was inaccessible during last gravity run
[2023-08-18 13:27:25.128 1165/T1298] Blocking status is enabled

[aurtiks2005]

I don't see new errors for now. We will see how it goes.