Database is in read-only mode after upgrade to 5.19 from 4.76

[vyper013]

nzbhydra-debuginfos-2023-07-16-09-52.zip

I have just completed an upgrade on a LXC container that has been running perfectly. So basically a bare metal install on an Ubuntu base (22.04).

the upgrade ran through and the only issue i had was my service was pointing at the exec, so i tested with the wrapper. this worked so i modified my service to use the python3 wrapper.

all boots ok but the DB is in read only... so I am assuming i missed something in a message somewhere...

How do i revert this? Or is it easier to restore and re-do the upgrade??

[theotherp]

It may just be that the file is locked by another process. Perhaps the old instance is still running? Or it just hasn't writing right sfor it. Try if you find a handle on the file. Try renaming it when hydra is shut down.

[vyper013]

Its not locked!! First thing i tried!! :) I rebooted a few times... shut down... renamed it, moved it changed ownership...

[theotherp]

Shut down hydra, rename the file, start hydra again. Is a new file created correctly?

…

On Sun, 16 Jul 2023, 12:45 vyper013, ***@***.***> wrote: Its not locked!! First thing i tried!! :) I rebooted a few times... shut down... renamed it, moved it changed ownership... — Reply to this email directly, view it on GitHub <#878 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADNUA6KKS3KIUXXVW77VYYDXQPA5XANCNFSM6AAAAAA2L2C5LQ> . You are receiving this because you commented.Message ID: ***@***.***>