-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Bug: NOT NULL constraint failed: core_archiveresult.output when upgrading v0.4.24 archive to v0.6 #705
Comments
Ah sorry for the trouble, that shouldn't happen. In the meantime while I investigate, if you have a backups from v0.4.24, can you try migrating to v0.5.6 first, then from there to v0.6? The issue is caused by some extractor outputs being null in your old archive (which shouldn't happen, they shouldn't get saved in the first place if there is no output, but the old v0.4.x series had problems with this). I can add a case to handle this in v0.6 and create them as emptystrings instead, but it will take a bit of time to test. Also helpful would be a sample |
I downgraded to v0.5.6. Rather than restoring a backup from v0.4.24, I deleted everything in the directory except the
Here is a random
|
One thing I notice looking at that JSON file is that it has a mix of absolute paths. I originally had ArchiveBox in Maybe that is screwing it up somehow? I'm not sure why it cares about absolute paths, since I think the expectation is that |
It doesn't actually use those paths for anything, so that wont affect it. They're just added for human readers to find files easier. Instead of starting fresh on v0.5.6, can you try starting fresh on v0.6? Backup & delete the main index files, leaving only the |
Starting fresh with v0.6.0 results in the same |
Ok, I'll push a fix for that one then. Hang tight, thanks for your patience. |
Is there anything that can be done to import old archives? Any guidance would be helpful. I tried to add snapshot_id to index.json inside archived website (like |
What version are you trying to import @milosz? I recommend upgrading through 0.5 then to 0.6 after. |
I have ~20G archive backup from 2019 year. Thanks, I will try this intermediate step. I am thrilled that it is possible. |
New instructions here: https://github.com/ArchiveBox/ArchiveBox/wiki/Upgrading-or-Merging-Archives Also note I've added a new DB/filesystem troubleshooting area to the wiki that may help people arriving here from Google: https://github.com/ArchiveBox/ArchiveBox/wiki/Upgrading-or-Merging-Archives#database-troubleshooting Contributions/suggestions welcome there. |
I upgraded from v0.4.24 to v0.6.0 and ran
archivebox init
. After the list of migrations, it output:The text was updated successfully, but these errors were encountered: