Upgraded OMV and gets SQL error: "sqlite3.OperationalError: disk I/O error"

[Tore]

I have a container with sabnzbd 3.5.2 in an old version of Openmediavault (4.x) and decided to install OMV 6 fresh on a new disk.
So I did and I have started up the containers and I can login to sabnzbd.
But I get an sql error every 15 minutes that I would like to fix.


I added a bit of a log file but get this:
New users are not allowed to post links

Trying to readd that log:

Code: Select all

2022-08-02 16:19:33,235::INFO::[notifier:123] Sending notification: Error - SQL Command Failed, see log (type=error, job_cat=None)
2022-08-02 16:19:33,235::ERROR::[database:153] SQL Command Failed, see log
2022-08-02 16:19:33,236::INFO::[database:154] SQL: SELECT * FROM history WHERE name LIKE ? ORDER BY completed desc LIMIT ?, ?
2022-08-02 16:19:33,236::INFO::[database:155] Arguments: ('%%', 0, 1000000)
2022-08-02 16:19:33,236::INFO::[database:156] Traceback: 
Traceback (most recent call last):
  File   "/app/sabnzbd/sabnzbd/database. py", line 124, in execute
    self.c.execute(command, args)
sqlite3.OperationalError: disk I/O error

EDIT: OK, adding a blank in "database. py" fixed that "posting link" issue. So the log snippet is now complete

[sander]

So ... did you Google "sqlite3.OperationalError: disk I/O error" ?

[Tore]

Yes, didn't find much that felt relevant for this.

I realized that it was some sorty of permission problem, but wanted a pointer on were to look.

I have fiddled with the settings and I could upgrade sab to 3.6.0 and that got rid of the error.

So problem solved.

[sander]

So: a permission problem?

[Tore]

Yes, Probably. I could not find the reason for it initially, but deleting the old one and starting with a new container fixed it.