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
{{ message }}
This repository was archived by the owner on Sep 10, 2025. It is now read-only.
Repository navigation
This repository was archived by the owner on Sep 10, 2025. It is now read-only.
Pruning/auto-pruning not working due to locked database #55
When running puppet-summary prune
with any command-line flag, the command returns Error pruning: database is locked
and pruning does not occur. The -verbose flag did not provide more information. -auto-prune is also affected, judging from the ever-increasing space occupied by reports. (Edit: Actually, it doesn't seem to be affected; my bad.)
I was able to reproduce the issue on multiple clean Vagrant boxes running Debian Stretch.
To reproduce:
Install puppet-summary, using the binary release, go get installation or building it manually from source.
Start puppet-summary directly with puppet-summary serve
(Import some data)
Execute puppet-summary prune with any option/flag combination
I was able to resolve my issue by modifying SetupDB code & rebuilding:
I was "inspired" to try this after reading mattn/go-sqlite3#607 (among many other related issues), but I'm not particularly suggesting my fix -- I'll gladly admit that I'm out of my depth.
Activity
skx commentedon Feb 12, 2019
That looks sane, and safe. Sorry for the delay.
If you submit a pull-request with the change I'll accept it. Otherwise I'll make a new release over the weekend when I get round to it.
skx commentedon Feb 17, 2019
Closed by your pull-request in #56, much appreciated.
New release will be made within the hour.