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

Address is not accessible #253

Closed
MultiPath opened this issue Nov 7, 2020 · 10 comments
Closed

Address is not accessible #253

MultiPath opened this issue Nov 7, 2020 · 10 comments
Assignees
Labels
help wanted Extra attention is needed

Comments

@MultiPath
Copy link

Hi,

I am sorry for another maybe basic question which I cannot find doc or explanation from the README.
When I tried aim up --tf_logs <my_location> --host localhost --port 10008
It directly returned me

Failed to run Aim UI.
    Please check if address localhost:10008 is accessible.

Is it related to firewall? Or some setting I must do before launching it?

I originally thought it was functioned similarly as tensorboard and I am trying the same way.
My log files are located in a remote server, I tried to run aim at the server for some port, and I will forward it to my local machine's local port so that I can open it in a browser.

Thank you very much

@SGevorg SGevorg added the help wanted Extra attention is needed label Nov 8, 2020
@SGevorg
Copy link
Member

SGevorg commented Nov 8, 2020

@MultiPath thanks for sharing the issue. Will make sure to get you up and running soon.

On your remote server have you tried to run
aim up --tf_logs <log_dir> --host 0.0.0.0 --port 10008 ?
Essentially try either port 0.0.0.0 or 127.0.0.1 and map/tunnel it to localhost on your machine like you have been doing ?

BTW, please make sure the long_dir path you specify is the parent dir of your log dirs. So it looks something like this:
log_dir/your_tensorboard_log_dir

@gorarakelyan
Copy link
Contributor

gorarakelyan commented Nov 8, 2020

Please make sure that port 10008 is reachable and is not in use by another process.

You can use lsof or netstat to list ports that are already in use:

  • lsof command:
    sudo lsof -i -P -n | grep LISTEN
  • netstat
    sudo netstat -tulpn | grep LISTEN

@SGevorg
Copy link
Member

SGevorg commented Nov 12, 2020

Hi @MultiPath I was wondering if you were able to get it working?

@GingerNg
Copy link

I have the same problem and tried different ports, it does not work. This maybe a bug

@gorarakelyan
Copy link
Contributor

We are looking into it.

@gorarakelyan
Copy link
Contributor

Could you check if this answer solves the issue?

Please make sure to upgrade Aim.

@MultiPath
Copy link
Author

Hi, after updating the aim version. Now it returns me new errors:

docker.errors.APIError: 500 Server Error: Internal Server Error ("error while creating mount source path '/checkpoint/jgu/space/nat2020/.aim': mkdir /checkpoint/jgu/space: permission denied")

I am not sure why it said permission denied.

@SGevorg
Copy link
Member

SGevorg commented Nov 30, 2020

Hi @MultiPath, sorry for a relatively slow reply - took our time to investigate this issue. A strange issue never seen before.
We suspect it could be permissions on your machine for security reasons? Would be awesome to learn more to make sure Aim works everywhere regardless.
Would love to invite you to join Aim community slack so we could use the chat and help interactively resolve the issue and get you up and running?

This would help to eliminate the problem for other users too. 🙏

@gorarakelyan
Copy link
Contributor

Hi @MultiPath,

We just released v2.5.0. No more docker required to run Aim!

Try it out by installing the latest version pip install aim --upgrade.

@gorarakelyan
Copy link
Contributor

Closing this issue due to inactivity.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

4 participants