-
-
Notifications
You must be signed in to change notification settings - Fork 76
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade to 5.x failed during database migration #885
Comments
@brianjmurrell I just ran into this myself. Did you get around it somehow? |
I'm afraid the only option is to delete the database file. You will lose
history and stats but no settings.
…On Sun, 8 Oct 2023, 18:21 Dave Parker, ***@***.***> wrote:
@brianjmurrell <https://github.com/brianjmurrell> I just ran into this
myself. Did you get around it somehow?
—
Reply to this email directly, view it on GitHub
<#885 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADNUA6OCIRD2RMKBG7UEG2LX6LHI7AVCNFSM6AAAAAA3I7PVIOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONJSGA4TONJYG4>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
I've reverted to 4.4.0 and it seems to back to where it was. Do you know if there is a upgrade path to 5.x from 4.4 or do I just need to nuke the db? Thanks |
Just delete the database file and start it again.
…On Sun, 8 Oct 2023, 18:46 Dave Parker, ***@***.***> wrote:
I'm afraid the only option is to delete the database file. You will lose
history and stats but no settings.
I've reverted to 4.4.0 and it seems to back to where it was. Do you know
if there is a upgrade path to 5.x from 4.4 or do I just need to nuke the db?
Thanks
—
Reply to this email directly, view it on GitHub
<#885 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADNUA6IWPY2XXFQ2G7URUHDX6LKGPAVCNFSM6AAAAAA3I7PVIOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONJSGEYDEOBSHE>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
OK - stupid user error - I failed to note that I needed to grab both the generic and the amd64 archive. Problem solved - thanks for your help :) |
Make sure to follow
https://github.com/theotherp/nzbhydra2/wiki/Updating-from-4.x-to-5.x
…On Sun, 8 Oct 2023, 20:29 Dave Parker, ***@***.***> wrote:
@theotherp <https://github.com/theotherp> ok - interesting: I wiped the
contents of the database directory, installed 5.5.11 over the top of 4.4.0
and it starts. But - I'm still seeing:
An update is available. Your version: 4.4.0. Latest version: 5.1.11.
at the bottom and it's still complaining about the wrapper scripts Any
idea what else I need to tweak?
—
Reply to this email directly, view it on GitHub
<#885 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADNUA6N6CUWAMAP2HHL4JA3X6LWJDAVCNFSM6AAAAAA3I7PVIOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONJSGEZDIMJZGM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
I tried to update from 4.x to 5.x using https://github.com/theotherp/nzbhydra2/wiki/Updating-from-4.x-to-5.x and it's now failing to start. The journal simply repeats over and over again:
I tried to repair the database:
The text was updated successfully, but these errors were encountered: