Application Error after wandb local

[niclaswue]

I am on Ubuntu 22.04 LTS and use a conda environment with Python 3.9 and wandb as the only pip package. After wandb local and accessing http://hostname:8080 I get this

Refreshing or opening http://hostname:8080/signup or http://hostname:8080/authorize always results in the same error. How should I proceed to get more information on the error? docker logs -f wandb-local seems fine

[niclaswue]

One relevant log entry seems to be in /var/log/nginx/error.log

2022/05/05 14:05:04 [error] 105#105: *50 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.3.251, server: , request: "POST /graphql HTTP/1.1", upstream: "http://127.0.0.1:8081/graphql", host: "hostname:8080", referrer: "http://hostname:8080/"

I installled wandb local on a Ubuntu 20.04 Server and it worked fine.

[vanpelt]

Hey @niclaswue can share how you're getting "hostname" to resolve in your network? The most useful log here would be /var/log/gorilla.log as it looks like our service is unable to startup for some reason. My guess would be your database failed to migrate or was interrupted. If that's the case you'll want to stop the container, remove the volume, and start the instance again.

[niclaswue]

Thank you, for taking the time to look into this. I tried to remove the volume and even completely reinstalled docker but unfortunately the error persists. The file /var/log/gorilla.log exists but is empty for me. I attached all logs here: wandb-local-logs.zip

It could be a network problem. The hostname's IP is 192.168.3.42, it is resolved by a local DNS server. I am connected via VPN to the gateway 192.168.3.251. I also tried accessing the page from another computer in the local network but I got the same error. I tried setting the host explicitly with wandb local -e HOST=hostname but that makes no difference. If you could give me a pointer to where I should look, that would be great. However, as mentioned I successfully managed to set wandb up on another server and that would also suffice for me right now.

[jasonyoun]

I had the same problem but fixed it by making sure there are no running wandb processes in the background. I must have killed my code not so legally that left a hanging wandb process.

Find the process using ps -fA | grep wandb and kill any processes that are not supposed to run using kill -9. For me, there was a single wandb process that kept writing .fuse* files under the wandb folder. Just to make sure, I also removed all files under the wandb folder. After all these, I was able to get back without the 'Application Error' message.

[luisbergua]

Hi @jasonyoun, thanks for explaining this and for providing a solution! It seems this is solved so I'll close this but please feel free to re-open in case the error is still appearing.