mirror of
https://github.com/ArchiveBox/ArchiveBox.git
synced 2026-04-25 17:16:00 +03:00
[GH-ISSUE #719] Bug: Server Error (500) #1966
Labels
No labels
expected: maybe someday
expected: next release
expected: release after next
expected: unlikely unless contributed
good first ticket
help wanted
pull-request
scope: all users
scope: windows users
size: easy
size: hard
size: medium
size: medium
status: backlog
status: blocked
status: done
status: idea-phase
status: needs followup
status: wip
status: wontfix
touches: API/CLI/Spec
touches: configuration
touches: data/schema/architecture
touches: dependencies/packaging
touches: docs
touches: js
touches: views/replayers/html/css
why: correctness
why: functionality
why: performance
why: security
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ArchiveBox#1966
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Ruthalas on GitHub (Apr 21, 2021).
Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/719
Describe the bug
(After update) navigating to the webUI shows "Server Error (500)"
Steps to reproduce
Screenshots or log output
Some selected portions of the log that might be relevant:
ArchiveBox version
Here is the errors.log.
(I did try to run the
python manage.py migrate, but just got this:python: can't open file '/data/manage.py': [Errno 2] No such file or directory.)Please let me know if there is more information I can provide. Thank you for your help!
@pirate commented on GitHub (Apr 21, 2021):
Run
archivebox init.@Ruthalas commented on GitHub (Apr 21, 2021):
I do not know how to 'de-elevate' my terminal to run the command as another user.
Initial research shows ways to add users to the container- should I pursue that?
(I am running the docker container in unRAID, for context.)
Edit: I am reading the documentation linked in the error.
I will try the steps shown there to make the user.
I am not sure why this would be needed after updating the docker container, but it seems like the correct solution.
Edit: The archivebox user already exists, which is good, but I have not yet determined how to run the init as that user.
@pirate commented on GitHub (Apr 21, 2021):
Run it however you would run other archivebox commands like
archivebox add, or however you ran the very firstarchivebox initwhen you initially started using it.docker run -v $PWD:/data -it archivebox/archivebox initdocker-compose run --rm archivebox initIf you're trying to exec inside an existing container you need to login as the
archiveboxuser. You can trysu archiveboxinside the container, but ideally use whatever mechanism you are using to gain a shell in the first place to do it as thearchiveboxuser instead of root.@Ruthalas commented on GitHub (Apr 22, 2021):
I was able to achieve that via the following steps:
cd /datasu - archiveboxarchivebox initThank you for your prompt and detailed assistance!
@rsnitsch commented on GitHub (Aug 24, 2021):
I had the same problem. The main cause was
"no such column: core_archiveresult.uuid"along with the warning"You have X unapplied migrations."In other words: The database scheme was changed and my pre-existing database from an earlier archivebox version needed an update.I don't understand why
archivebox initwas recommended in this thread. It's supposed to initiate a new archivebox setup, not update a preexisting one. If it can do updates, too, then maybe the description for theinitcommand should be updated.Instead of running
archivebox init, I usedThis executes the database migrations only.
Addendum:
I just saw in the 0.6.2 changelog that the init command was enhanced recently: "add init --quick and server --quick-init options to quickly update the db version without doing a full re-init (for users with large archive collections this will make version upgrades a lot faster / less painful)"
I guess
init --quickdoes the same asmanage migrate.@pirate commented on GitHub (Aug 25, 2021):
Do not run
manage migrate, that is not for end users.initis indempotent and is used for both upgrading and initializing, you can run it as many times as you want safely within an archive. I don't recommend--quick-initas that won't do a full upgrade, it will only update the schéma without moving any files into new locations.