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
can not connect to visdom server On Linux #174
Comments
I'm not quite familiar with how visdom will act on linux (as I know networking on linux tends to vary by distribution) but it could be possible that routing to localhost isn't properly configured. Are you able to successfully ping localhost via a terminal? |
@JackUrb , I am using CentOS 7.2. When I use
|
Are you able to ping localhost without the port? just |
Yes, I can |
And when you run the server the line |
No, both on Windows and CentOS, when I run the server using
appers. The output of
|
Hm no other lines - What is the console output when you ctrl c? Also what is the output of I can't tell if the issue is something on tornado's end in not fully starting up or on the side of the browser side |
The output of
The output of
On CentOS, I tested both firefox and chrome. Neither of them works properly. |
Alright this seems to imply the visdom server is running properly (as |
Ah alright so the page does eventually load at least - can you check the contents of the javascript console in the window on CentOS? It's possible that some of the dependancies are not getting loaded for some reason. |
Yeah the issue is definitely there - where is it trying to load those files from? You should be able to see on the network tab. |
I think I have found the root cause. Thanks to the f**king GFW. On my windows, my browser connect to internet via proxy, but on CentOS, there is no proxy. So some of the resources can't be loaded properly on CentOS. |
Ah that would definitely explain it. I know it's possible to connect through a proxy on CentOS, though I'm not sure how easy it is. Hopefully you'll be able to use visdom properly once you have that set up though! I'm going to close the issue now that we're sure it's external to us |
Ok, thanks for your help and patience~ 👍 |
你好jdhao,
谢谢 @jdhao |
@SMZCC, I think using English is preferred. Actually I have not spent my time to solve this problem. There are two ways I can think of to solve this problem, one is to set up your browser and connect to any website via proxy (so you have to install a shadowsocks client on your Ubuntu). Another way is to download the blocked javascript resource and put it somewhere the visdom page expect them to be (although I do not where). You may ask the visdom developer for help for the second way. |
|
@SMZCC , I would rather advise you to try this tool, https://github.com/lanpa/tensorboard-pytorch. |
Hi @SMZCC @jdhao. It definitely is possible to download the required scripts manually and store them in the location that visdom expects them. We used to make these packages install during the initial download and setup, but then it was impossible to get visdom when our external content distributors were down. Here's the function that actually does the collecting. This line is the file name that we expect to find the file that we download from the location stored in key. As long as you download these files and put them in the expected location, the server won't need to attempt to download them externally on runtime. |
|
I used the line
You will need to find out where your visdom package folder is, as in my case it is |
I am facing the same issue, is anyone here got the things sorted out? |
@lixuanze please open a new issue and fill out the complete set of details, otherwise it is impossible to diagnose your problem. |
I have installed visdom python package on my Linux system After starting the visdom server, I can not open the page
localhost:8097
. I have tried to addLocalForward 127.0.0.1:8097 127.0.0.1:8097
to~/.ssh/config
, but it does not help either. I have also tried to install visdom on my Windows computer, and it works fine.Any idea how to fix this?
The text was updated successfully, but these errors were encountered: