Skip to content
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

Wandb local server start error #102

Open
liswp opened this issue Dec 19, 2022 · 2 comments
Open

Wandb local server start error #102

liswp opened this issue Dec 19, 2022 · 2 comments

Comments

@liswp
Copy link

liswp commented Dec 19, 2022

Current Behavior
Hi Wandb team,

I am a wandb user and currently encountering the following error when we run: wandb server start

*** 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...
2022/12/19 23:47:02 Created default user
2022/12/19 23:47:02 Generating new session key for auth...
2022/12/19 23:47:02 Generating new certificate and key for auth...
*** Booting runit daemon...
*** Runit started as PID 48
*** Setting up mysql database...
*** Starting wandb servers...
*** Configuring minio...
Bucket created successfully local/local-files.
mc: Unable to set 'notify_redis address=127.0.0.1:6379 format=access queue_limit=10000 queue_dir=/etc/minio/events key=filemetadata' to server: one or more targets are offline. Please use mc admin info --json to check the offline targets.
mc: Unable to enable notification on the specified bucket. A specified destination ARN does not exist or is not well-formed. Verify the destination ARN.

Above is the output from docker logs wandb-local

Please help. Many thanks.

Environment
OS: ubuntu linux 16.04

Browsers: Chrome and Firefox

Version: 16.04, pip 22.2.2, Docker version 18.09.7, build 2d0083d

@lesliewandb
Copy link

Hi @liswp, I see that you opened up two tickets with the same issue. I'll respond on the other one and close this one out.

@exalate-issue-sync
Copy link

WandB Internal User commented:
lesliewandb commented:
Hi @liswp, I see that you opened up two tickets with the same issue. I'll respond on the other one and close this one out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants