You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been trying the new SQLite database type for the cache as suggest by Daniel on the Discord (message link) and I've decided to look into the logs a bit and found that Portmaster is complaining quite a bit about the database being locked. Unsure if it breaks anything, it's hard to tell with me not knowing where to look, but it's been sending those log messages quite a bit, way more than I think it should, so I wanted to make this issue just ini case it is something noteworthy. (logs in the debug info)
Debug Information:
Version 1.6.33
Portmaster 1.6.33
built with go1.24.1 (gc -cgo) for linux/amd64
at 2025-03-17T14:49:16Z
commit 32c7f6e7d15e29290f3446370ffdf699ed262f2d (clean)
at 2025-03-17T14:31:48Z
from https://github.com/safing/portmaster
Licensed under the GPLv3 license.
Platform: arch "rolling"
System: arch linux (arch) "rolling"
Kernel: 6.13.8-arch1-1 x86_64
Unexpected Logs
2025-03-27 01:05:32.588 WRN face_cache:109 ▶ 940 database: failed to finish flushing write cache to "cache" database: database is locked (5) (SQLITE_BUSY)
2025-03-27 01:10:32.587 WRN face_cache:109 ▶ 942 database: failed to finish flushing write cache to "cache" database: database is locked (5) (SQLITE_BUSY)
2025-03-27 01:14:35.312 WRN er/resolve:467 ▶ 944 resolver: query to dot://dns.quad9.net:853#config failed: query failed
2025-03-27 01:15:32.588 WRN face_cache:109 ▶ 946 database: failed to finish flushing write cache to "cache" database: database is locked (5) (SQLITE_BUSY)
2025-03-27 01:15:48.311 WRN er/resolve:467 ▶ 948 resolver: query to dot://dns.quad9.net:853#config failed: query failed
2025-03-27 01:15:51.379 WRN er/resolve:467 ▶ 950 resolver: query to dot://dns.quad9.net:853#config failed: query failed
2025-03-27 01:20:32.589 WRN face_cache:109 ▶ 952 database: failed to finish flushing write cache to "cache" database: database is locked (5) (SQLITE_BUSY)
2025-03-27 01:25:32.587 WRN face_cache:109 ▶ 954 database: failed to finish flushing write cache to "cache" database: database is locked (5) (SQLITE_BUSY)
2025-03-27 01:25:32.588 WRN face_cache:109 ▶ 956 database: failed to finish flushing write cache to "cache" database: database is locked (5) (SQLITE_BUSY)
2025-03-27 01:30:32.588 WRN face_cache:109 ▶ 958 database: failed to finish flushing write cache to "cache" database: database is locked (5) (SQLITE_BUSY)
250327 01:31:48.697 CURRENT TIME
Greetings and welcome to our community! As this is the first issue you opened here, we wanted to share some useful infos with you:
🗣️ Our community on Discord is super helpful and active. We also have an AI-enabled support bot that knows Portmaster well and can give you immediate help.
📖 The Wiki answers all common questions and has many important details. If you can't find an answer there, let us know, so we can add anything that's missing.
Obviously this should not happen (too much). I will check if there is an issue with the SQLite config - I think the WAL should have prevented this, as well as the locking mechanism we specified. Possibly we also need to give it a timeout.
Otherwise we'll add some locking ourselves to mitigate.
I've been trying the new SQLite database type for the cache as suggest by Daniel on the Discord (message link) and I've decided to look into the logs a bit and found that Portmaster is complaining quite a bit about the database being locked. Unsure if it breaks anything, it's hard to tell with me not knowing where to look, but it's been sending those log messages quite a bit, way more than I think it should, so I wanted to make this issue just ini case it is something noteworthy. (logs in the debug info)
Debug Information:
Version 1.6.33
Platform: arch "rolling"
Unexpected Logs
Status: Online
Resolvers: 8/8
Config: 10
Updates: beta (14/30)
Goroutine Stack
The text was updated successfully, but these errors were encountered: