mirror of
https://github.com/ArchiveBox/ArchiveBox.git
synced 2026-04-25 09:06:02 +03:00
[GH-ISSUE #1506] Bug: sqlite3.OperationError: database is locked occurred during multiline url Add #3906
Labels
No labels
expected: maybe someday
expected: next release
expected: release after next
expected: unlikely unless contributed
good first ticket
help wanted
pull-request
scope: all users
scope: windows users
size: easy
size: hard
size: medium
size: medium
status: backlog
status: blocked
status: done
status: idea-phase
status: needs followup
status: wip
status: wontfix
touches: API/CLI/Spec
touches: configuration
touches: data/schema/architecture
touches: dependencies/packaging
touches: docs
touches: js
touches: views/replayers/html/css
why: correctness
why: functionality
why: performance
why: security
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ArchiveBox#3906
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @muuky on GitHub (Sep 3, 2024).
Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/1506
Describe the bug
I attempted to archive a large number of URLs at once through the Add button in the WebUI of ArchiveBox, which is set up via Docker. However, out of the 139 URLs, 51 started the snapshot process, but after 6 hours, they are still loading. The remaining 88 URLs didn't even begin the snapshot process.
After checking with the
docker logs {container id}command, I found that the error message ‘sqlite3.OperationError: database is locked’ was displayed. This is likely due to an excessive number of database read/write operations. Alternatively, it could be due to the installation on an HDD.Steps to reproduce
Screenshots or log output
ArchiveBox version
@pirate commented on GitHub (Sep 6, 2024):
Are you down to try on the beta release? There have been many performance and consistency improvements since 0.7 that could make this better:
https://github.com/ArchiveBox/ArchiveBox/releases/tag/v0.8.3-rc
In general usage on an HDD is always going to be slow though, we really recommend keeping the index.sqlite3 file on an SSD if possible.
@makew0rld commented on GitHub (Feb 17, 2025):
I had the same issue, and using the latest beta tag on Docker (
0.8.5rc51) fixed it for me. Or at least, I don't see the same error. I'm not sure yet how well things are archiving.@pirate commented on GitHub (Feb 17, 2025):
The new betas have much improved performance on slow disks, but they're also unstable and the schema might break between betas while we work on refining it. Don't rely on them for anything critical yet!