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

[Bug] no error in the log and no dashboard process #20017

Closed
1 of 2 tasks
yiwei00000 opened this issue Nov 3, 2021 · 4 comments
Closed
1 of 2 tasks

[Bug] no error in the log and no dashboard process #20017

yiwei00000 opened this issue Nov 3, 2021 · 4 comments
Labels
bug Something that is supposed to be working; but isn't triage Needs triage (eg: priority, bug/not-bug, and owning component)

Comments

@yiwei00000
Copy link
Contributor

Search before asking

  • I searched the issues and found no similar issues.

Ray Component

Dashboard

What happened + What you expected to happen

When I use ray version 1.8.0, I use the command ray start --head --port = 6379 --dashboard host = 0.0.0. After starting, there is no error in the log, but there is no dashboard process, and I can't access ray dashboard in the browser

Versions / Dependencies

ray 1.8.0

Reproduction script

ray start --head --port=6379 --dashboard-host=0.0.0.0

Anything else

No response

Are you willing to submit a PR?

  • Yes I am willing to submit a PR!
@yiwei00000 yiwei00000 added bug Something that is supposed to be working; but isn't triage Needs triage (eg: priority, bug/not-bug, and owning component) labels Nov 3, 2021
@rkooo567
Copy link
Contributor

rkooo567 commented Nov 4, 2021

cc @edoakes @simon-mo

@simon-mo
Copy link
Contributor

simon-mo commented Nov 4, 2021

Can you add --include-dashboard=true?

@jfischer
Copy link

jfischer commented Nov 4, 2021

Hi, I ran into the same issue. I'm starting ray 1.8.0 with the following command line:

ray start --head --dashboard-host=0.0.0.0 --include-dashboard=true --block

I added a print to my local copy of Ray to get the exact cause of the import error. This is the error: No module named 'aiohttp.signals'

In my environment, I'm using version 3.8.0 of aiohttp. It does not have a signals submodule. Looking at the commit history for aiohttp, I suspect the following change is causing the problem: aio-libs/aiohttp@7f0cd0d#diff-2f6aee0ecbf53b6b3760ba0a15c5cbc47898bdcdab1db521a63ad99a7bca3d98

@simon-mo
Copy link
Contributor

simon-mo commented Nov 4, 2021

yes. please downgrade aiohttp to <3.8 for now. #19940 (comment) We currently pinned the version in development branch and will make Ray compatible with 3.8.0 soon #19951

@simon-mo simon-mo closed this as completed Nov 4, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something that is supposed to be working; but isn't triage Needs triage (eg: priority, bug/not-bug, and owning component)
Projects
None yet
Development

No branches or pull requests

4 participants