-
Notifications
You must be signed in to change notification settings - Fork 1.1k
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Error: root initializing-- Visdom does not show graphs, only has a weird blank table #884
Comments
Hi there, the table shows the selected environments to be compared: in your case its However, you probably want to inspect all graphs of only a single environment, namely Best |
Bug Description
after initializing visdom using python -m visdom.server -port ${port} --hostname ${node}
ERROR:root:initializing
INFO:root:Application Started
INFO:root:Working directory: /gpfs/scratch/fanj06/visdom_cache
Reproduction Steps
Enter steps to reproduce the behavior:
Expected behavior
Give a clear and concise description of what you expected to happen.
Screenshots
Client logs:
For issues that make it to the point of reaching the frontend in a browser, please include the javascript logs from that browser. In Chrome, javascript logs can be found via View -> Developer -> JavaScript Console.
Server logs:
ERROR:root:initializing
INFO:root:Application Started
INFO:root:Working directory: /gpfs/scratch/fanj06/visdom_cache
INFO:tornado.access:200 POST /env/main (192.168.0.92) 1.01ms
INFO:tornado.access:101 GET /vis_socket (192.168.0.92) 0.59ms
INFO:root:Opened visdom socket from ip: 192.168.0.92
INFO:tornado.access:200 POST /events (192.168.0.92) 0.57ms
INFO:tornado.access:200 POST /events (192.168.0.92) 0.40ms
INFO:tornado.access:200 POST /events (192.168.0.92) 0.35ms
INFO:tornado.access:200 POST /events (192.168.0.92) 0.53ms
INFO:tornado.access:200 POST /win_exists (192.168.0.92) 0.48ms
INFO:tornado.access:200 POST /update (192.168.0.92) 1.80ms
INFO:tornado.access:200 POST /win_exists (192.168.0.92) 0.32ms
INFO:tornado.access:200 POST /update (192.168.0.92) 1.29ms
INFO:tornado.access:200 POST /events (192.168.0.92) 0.36ms
INFO:tornado.access:200 POST /events (192.168.0.92) 0.94ms
Additional context
Add any other context about the problem here. (like proxy settings, network setup, overall goals, etc.)
The text was updated successfully, but these errors were encountered: