question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Visdom Always Offline

See original GitHub issue

I cloned visdom, installed from source (using pip install -e .) and then also ran (python setup.py install) to finish the installation (visdom==0.1.7.2). I started up the server (python -m visdom.server) and was able to bring up visdom in Chrome but it remains offline.

I can only click on the two dropdowns and when I click on “main”, the following error prints out:

INFO:tornado.access:200 GET /env (::1) 22.98ms
INFO:tornado.access:200 GET /static/js/main.js?v=b65d2039276f4c6580171aca25bdd5e7 (::1) 3.40ms
INFO:tornado.access:200 GET /static/css/style.css?v=6c9680f97ddb1c54aee0576b12b8ce3b (::1) 1.66ms
INFO:tornado.access:200 GET /favicon.png (::1) 2.62ms
INFO:tornado.access:200 GET /env/socket (::1) 2.49ms
ERROR:tornado.application:Uncaught exception POST /env/env/main (::1)
HTTPServerRequest(protocol='http', host='localhost:8097', method='POST', uri='/env/env/main', version='HTTP/1.1', remote_ip='::1')
Traceback (most recent call last):
  File "../anaconda3/lib/python3.6/site-packages/tornado/web.py", line 1541, in _execute
    result = method(*self.path_args, **self.path_kwargs)
  File "../anaconda3/lib/python3.6/site-packages/visdom-0.1.7.2-py3.6.egg/visdom/server.py", line 718, in post
    load_env(self.state, args, self.subs[sid])
KeyError: None
ERROR:root:ERROR: 500: {'exc_info': (<class 'KeyError'>, KeyError(None,), <traceback object at 0x7f27ef1e5648>)}
ERROR:tornado.access:500 POST /env/env/main (::1) 2.50ms
INFO:tornado.access:304 GET /favicon.png (::1) 2.12ms
INFO:tornado.access:101 GET /vis_socket (::1) 0.49ms

The javascript console then has the following error:

WebSocket connection to 'ws://localhost:8097/env/socket' failed: Error during WebSocket handshake: Unexpected response code: 200 WrappedWebSocket@VM518:164

When I try to run the code example:

>>> import visdom
>>> import numpy as mp
>>> vis = visdom.Visdom()
>>> vis.text('Hello, world')
'window_36084c0e4eddf6'

The following is output but nothing shows up in visdom.

INFO:root:Opened visdom socket from ip: ::1
INFO:tornado.access:200 POST /events (::1) 0.85ms

The javascript console then has the following error:

Post http://localhost:9087/env/env/main 500 (Internal Sever Error)

send | @ | jquery.min.js?v=e071…4711cfc2ab99fe104:4
-- | -- | --
  | ajax | @ | jquery.min.js?v=e071…4711cfc2ab99fe104:4
  | r.(anonymous function) | @ | jquery.min.js?v=e071…4711cfc2ab99fe104:4
  | r.selectEnv | @ | main.js?v=b65d203927…580171aca25bdd5e7:1
  | r | @ | react-dom.min.js?v=8…04ed9a2dac56860e:14
  | a | @ | react-dom.min.js?v=8…04ed9a2dac56860e:12
  | s | @ | react-dom.min.js?v=8…04ed9a2dac56860e:12
  | f | @ | react-dom.min.js?v=8…04ed9a2dac56860e:12
  | m | @ | react-dom.min.js?v=8…04ed9a2dac56860e:12
  | r | @ | react-dom.min.js?v=8…04ed9a2dac56860e:15
  | processEventQueue | @ | react-dom.min.js?v=8…04ed9a2dac56860e:12
  | r | @ | react-dom.min.js?v=8…04ed9a2dac56860e:14
  | handleTopLevel | @ | react-dom.min.js?v=8…04ed9a2dac56860e:14
  | i | @ | react-dom.min.js?v=8…04ed9a2dac56860e:14
  | perform | @ | react-dom.min.js?v=8…04ed9a2dac56860e:15
  | batchedUpdates | @ | react-dom.min.js?v=8…04ed9a2dac56860e:14
  | i | @ | react-dom.min.js?v=8…04ed9a2dac56860e:14
  | dispatchEvent | @ | react-dom.min.js?v=8…04ed9a2dac56860e:14

Are there setup steps that I missed?

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Comments:13 (6 by maintainers)

github_iconTop GitHub Comments

1reaction
JackUrbcommented, Mar 12, 2018

Yeah that’s somewhat related to https://github.com/facebookresearch/visdom/issues/273, the feature used to work properly so the docs had prepopulated an empty env but I haven’t had a chance to fix the env access by path yet. Thanks for noting it!

1reaction
drothermelcommented, Mar 12, 2018

Ahh, yup, thats the problem, I went to localhost:8097/env (based on some docs I’ll update). When I went to just localhost:8097 then it works as expected, thank you!

Read more comments on GitHub >

github_iconTop Results From Across the Web

Visdom Always Offline · Issue #294 - GitHub
I started up the server (python -m visdom.server) and was able to bring up visdom in Chrome but it remains offline. I can...
Read more >
Visdom - SoundCloud
Play Visdom on SoundCloud and discover followers on SoundCloud | Stream tracks, albums, playlists on desktop and mobile.
Read more >
Wisdom From The Top with Guy Raz | Podcast on Spotify
Listen to Wisdom From The Top with Guy Raz on Spotify. ... Behavior Design Lab, says the key to behavior change isn't what...
Read more >
What Is the Gift of the Word of Wisdom? by Don Stewart
The Various Gifts of the Holy Spirit (Part Two) – Question 20 Wisdom is the ... But in your hearts regard Christ the...
Read more >
Sketch-Based Steering in Visdom
Visdom is a modular integrated visualization system which is developed to ... Mankind always had to cope with the unpredictability of the forces...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found