wandb: Error while calling W&B API: permission denied
Hello,
I am training a model on a remote server and I got this error after running on the terminal wandb login and running the training script itself.
wandb: Tracking run with wandb version 0.8.15
wandb: Run data is saved locally in wandb/run-20191107_074736-rjih2419
wandb: ERROR Error while calling W&B API: permission denied (<Response [403]>)
wandb: ERROR Launch exception: Permission denied to access wandb/Dressyou Recommender system/rjih2419
wandb: ERROR To disable wandb syncing set WANDB_MODE=dryrun
wandb: ERROR W&B process (PID 19599) did not respond
wandb: ERROR W&B process failed to launch, see: wandb/debug.log
Traceback (most recent call last):
File "script/train.py", line 168, in <module>
wandb.init(entity="wandb", project="Dressyou Recommender system")
File "/home/amal/miniconda3/envs/all_dep_cuda/lib/python3.7/site-packages/wandb/__init__.py", line 1051, in init
_init_headless(run)
File "/home/amal/miniconda3/envs/all_dep_cuda/lib/python3.7/site-packages/wandb/__init__.py", line 288, in _init_headless
"W&B process failed to launch, see: {}".format(path))
wandb.run_manager.LaunchError: W&B process failed to launch, see: wandb/debug.log
Do you have an idea how to solve this please ?
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Reactions: 1
- Comments: 21 (8 by maintainers)
Hey @bamal it looks like you’re trying to launch runs into the “wandb” team. The quickest fix is to set entity=“bamal” (or your wandb username) when you call wandb.init
Hey @radoye that’s a permission error. You’re trying to save results to
entity="wandb", project="set-run-name-to-id"which you don’t have permission to. In your call to init, addentity="YOUR_USERNAME"and try again.@vanpelt This indeed solves the problem. It is a bit confusing when the
sample-projectinstructions fail, though. Maybe mention this there?to anyone who has stumbled upon this topic, ensure that your program isn’t setting your “entity” somewhere in your code. It will default to your account when you are logged in, but if it is set somewhere else it will still show you as logged in successfully but will deny you (because your account doesn’t have access to this other entity)
Hi @vanpelt , I am having a similar issue. However, in my case, I am part of more than one teamwork. My wandb keeps logging in to only one of them. I have tried deleting the old entry from my
.netrcfile and deleting thewandb/settingsfile as well. And then redoing thewandb loginwith the correctAPI_KEY, but it still showswandb: Currently logged in as: old-team. Any advices? I tried setting theentityas my user and as the team name, but the two solutions find the old team.Issue Label Bot is not confident enough to auto-label this issue. See dashboard for more details.