Wandb local downgrade
jjerry-k opened this issue · 7 comments
Hi, I'm Jerry in Korea.
I'm using wandb/local on my local mini pc.
When I updated wandb/local 0.9.40 to 0.9.49, I got some error like "Error: Could not save view." on page.
So, I tried to downgrade wandb/local 0.9.49 to 0.9.40.
But, I got a error message in docker logs.
*** Running /etc/my_init.d/00_regen_ssh_host_keys.sh...
*** Running /etc/my_init.d/01_enable-services.sh...
*** Copying services to runit
*** Copying jobber template
*** Enabling production mode
*** Running /etc/my_init.d/02_load-settings.sh...
*** Loading settings...
*** Booting runit daemon...
*** Runit started as PID 36
*** Starting wandb servers...
*** Migrating database...
panic: file does not exist
goroutine 1 [running]:
main.main()
/mnt/ramdisk/core/services/gorilla/cmd/migrate/main.go:115 +0xb05
*** All services started
*** Access W&B at http://localhost:8080
!!! Unable to start backend, see logs at /var/logs. Trying again in 1 minute
!!! Set the environment variable LOCAL_RESTORE=true if you're unable to login to the admin console
Have you ever encountered this error?
Hey Jerry,
Could to exec into your docker by using docker exec -it wandb-local bash
and then get the output for /var/logs/gorilla.log
for me? That should have some more info on what is going wrong here.
Thanks,
Ramit
Looks like the database was not correctly migrated when you upgraded. Let's start with getting you back down to 0.9.40, could you run the following set of commands?
docker pull wandb/local:0.9.40
docker stop wandb-local
docker run --rm -d -v wandb:/vol -p 8080:8080 --name wandb-local wandb/local:0.9.40
Once we can get you back to a place where your server is running fine, the recommended course of action would be to back up your database and then try to upgrade incrementally to make sure your database upgrades correctly as well.
Thank you for answering.
but, I already run that commands.
So, I got this error on 0.9.40 version.
#99 (comment)
We don't officially support downgrading, you'll need to upgrade the instance. Version 0.9.40 is over a year old. The current version is 0.25.0. I would atleast upgrade to 0.11.0 from May of this year, but you should get up to 0.25.0 to ensure you're running an up to date and secure version of the server.
@vanpelt
Thank you, Chris.
So, I have another question.
After closing this issue, Could I open a new issue?
Sure
Please, close this issue