mirror of
https://github.com/advplyr/audiobookshelf.git
synced 2026-05-30 23:40:40 +02:00
[Bug]: SequelizeDatabaseError: SQLITE_FULL: database or disk is full #1967
Assignees
adam (Adam Melkus)
Clear assignees
adam (Adam Melkus)
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: starred/audiobookshelf#1967
Reference in New Issue
Block a user
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 @Wonneproppen on GitHub (May 8, 2024).
What happened?
Audiobookshelf stops working after each and any database transaction. After a restart I can see the following error message:
SequelizeDatabaseError: SQLITE_FULL: database or disk is full
There is enough space on the disk, so this does not seem to be the issue.
What did you expect to happen?
Audiobookshelf should not stop working ;-)
Steps to reproduce the issue
Audiobookshelf version
2.8.1
How are you running audiobookshelf?
Other (list in "Additional Notes" box)
What OS is your Audiobookshelf server hosted from?
Linux
If the issue is being seen in the UI, what browsers are you seeing the problem on?
Chrome
Logs
Additional Notes
It runs on a X86 QNAP via https://www.myqnap.org/product/audiobookshelf/
@nichwall commented on GitHub (May 8, 2024):
Looks like you have a corrupt database. Can you try restoring from a backup?
@Wonneproppen commented on GitHub (May 8, 2024):
Thanks for the quick reply.
I tried the following:
a. from last night
b. created 3 weeks ago
result for all: during backup installation: lost web socket connection, stopped working
@nichwall commented on GitHub (May 8, 2024):
Can you look at any logs? Crash logs are stored in
/metadata/logs/crash_logs.txt.Is
/config, where the database is stored, on a network drive?@Wonneproppen commented on GitHub (May 9, 2024):
During recovery:
{"timestamp":"2024-05-09
07:45:13.308","source":"Server.js:164","message":"[Server] Unhandled
rejection: Error: ENOENT: no such file or directory, open
'/share/CACHEDEV1_DATA/.qpkg/Audiobookshelf/metadata/authors/1273b1ff-e35a-48a7-911a-a3f17c27cb96.jpg',
promise: Promise {\n [Error: ENOENT: no such file or directory,
open
'/share/CACHEDEV1_DATA/.qpkg/Audiobookshelf/metadata/authors/1273b1ff-e35a-48a7-911a-a3f17c27cb96.jpg']
{\n errno: -2,\n code: 'ENOENT',\n syscall: 'open',\n path:
'/share/CACHEDEV1_DATA/.qpkg/Audiobookshelf/metadata/authors/1273b1ff-e35a-48a7-911a-a3f17c27cb96.jpg'\n
}\n}","levelName":"FATAL","level":5mestamp":"2024-05-09
07:45:13.308","source":"Server.js:164","message":"[Server] Unhandled
rejection: Error: ENOENT: no such file or directory, open
'/share/CACHEDEV1_DATA/.qpkg/Audiobookshelf/metadata/authors/1273b1ff-e35a-48a7-911a-a3f17c27cb96.jpg',
promise: Promise {\n [Error: ENOENT: no such file or directory,
open
'/share/CACHEDEV1_DATA/.qpkg/Audiobookshelf/metadata/authors/1273b1ff-e35a-48a7-911a-a3f17c27cb96.jpg']
{\n errno: -2,\n code: 'ENOENT',\n syscall: 'open',\n path:
'/share/CACHEDEV1_DATA/.qpkg/Audiobookshelf/metadata/authors/1273b1ff-e35a-48a7-911a-a3f17c27cb96.jpg'\n
}\n}","levelName":"FATAL","level":5}
@nichwall commented on GitHub (May 9, 2024):
Is this restoring from a backup using the web interface or are you manually extracting and applying the backup?
Can you try upgrading your server to 2.9.0 and then restoring a backup? There were some backup issues fixed in the past month or so but don't remember exactly when they were found/fixed.
@Wonneproppen commented on GitHub (May 9, 2024):
I am doing the backups/restore via the web interface.
Will do as soon as the qpkg for 2.9.0. is available (https://www.myqnap.org/product/audiobookshelf/)
@nichwall commented on GitHub (May 9, 2024):
Sounds good, thanks! The QNAP package is not maintained by us, so not sure when you can get that. If you're using docker you can get updates immediately by updating the tag you're pulling from.
@Wonneproppen commented on GitHub (May 9, 2024):
I installed it via docker with the same behavior.
After restoring the backup, abs stopped working.
@advplyr commented on GitHub (May 9, 2024):
I'm not sure that this is an Abs issue. It seems like you are having issues with the file system and you should reach out to the QPKG maintainer.
@nichwall commented on GitHub (May 9, 2024):
I wonder if the QNAP system does something weird (like allowing for multiple access to the SQLite database and causing corruption)? I'm not familiar with how "corrupt" the database can get before it fails. Is it any corruption, only certain columns/lookup related things being accessed, etc?
How big is the SQLite file?
@Wonneproppen commented on GitHub (May 11, 2024):
I am using abs since ~1 year on my qnap via qpkg and never had such an issue. I was also running version 2.8.1. via qpkg since some months.
Interesting fact: I rolled back an old backup (~1 month) and now abs is working stable, but I am getting [FfmpegHelpers] Resize Image Error Error: spawn /opt/ffmpeg/ffmpeg EACCES undefined undefined.
Thanks for your support and this really great software!
@caffeineaddiction commented on GitHub (May 14, 2024):
"""
(13) SQLITE_FULL
The SQLITE_FULL result code indicates that a write could not complete because the disk is full. Note that this error can occur when trying to write information into the main database file, or it can also occur when writing into temporary disk files.
Sometimes applications encounter this error even though there is an abundance of primary disk space because the error occurs when writing into temporary disk files on a system where temporary files are stored on a separate partition with much less space that the primary disk.
"""
https://www.sqlite.org/rescode.html#full
possibly out of memory and swap was turned off?