History reverting to upgrade date - activity data lost or not displayed

[spagafus]

Set your log file level to debug, repeat the steps that cause the problem and post the debug infos ZIP which can be retrieved in the System / Bugreport section. If other tools are involved post their logs as well.

Version: 5.1.8
Container version: v5.1.8-ls103
Container release type: Release
Container author: linuxserver.io

Upgraded from image: linuxserver/nzbhydra2:v4.2.1-ls46 on 15/06/23 and now the history reverts to that date. I haven't been able to determine if it happens after a cleanup job runs or some other event trigger.

This is an example of the result from the Search History page which shows a gap as if there's been no activity between 06-15 and 06-24 though there has been activity.

2023-06-24 06:19 | Update query | TV |   | API |  
2023-06-15 08:10 | Update query | TV |   | API

Download History will also remove items downloaded since the upgrade date. New items will be shown until the data reverts back to 06-15 and the cycle begins again.

• What do you expect to happen? What does happen?
  Expect continuity in history data.

• Can the problem be reproduced? How?
  As far as I can tell it's not user triggered. I has happened multiple times since upgrade.

• If you use a docker container please tell me which one.
  See above.

[spagafus]

If this is due to a corrupted db and a one-off problem then I'm willing to remove and let the app recreate it. The history and stats are nice to have but not critical.

[theotherp]

You can certainly try. Just rename the database file while hydra is shut down.

…

On Tue, 27 Jun 2023, 13:52 Q-Droid, ***@***.***> wrote: If this is due to a corrupted db and a one-off problem then I'm willing to remove and let the app recreate it. The history and stats are nice to have but not critical. — Reply to this email directly, view it on GitHub <#873 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADNUA6LBPUPNKQPD6CW5CM3XNLCQ5ANCNFSM6AAAAAAZSOTKE4> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[spagafus]

Moving forward with a new DB and so far it's working as expected. Unless you're interested in more info we can chalk this up as a one-off corruption and close this issue.

[theotherp]

Kinda busy so if you're happy so am I 😊

…

On Wed, 28 Jun 2023, 14:22 Q-Droid, ***@***.***> wrote: Moving forward with a new DB and so far it's working as expected. Unless you're interested in more info we can chalk this up as a one-off corruption and close this issue. — Reply to this email directly, view it on GitHub <#873 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADNUA6KCQZGRP2BRPF4ARATXNQOZDANCNFSM6AAAAAAZSOTKE4> . You are receiving this because you commented.Message ID: ***@***.***>