-
Notifications
You must be signed in to change notification settings - Fork 95
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] web ui shows Connection Lost #4624
Comments
also don't know how to run in docker mode |
i'm so sorry, we're on it! For your second problem, it's likely you don't have docker running on the machine you're running on. |
Hy Yuriy, Issue 1:I wasn't able to re-produce the issue. I do see from the screenshot the webui is having trouble connecting to the orchestrator node. What url are you using to reach the webui? Is it If you are calling the webui on a remote node, and I'll guess the node is If this works, it is just telling the frontend to connect to the orchestrator at Issue 2:The panic you are getting seems to originate from the code where we try to query docker's daemon information. It seems we are not handling edge cases well when the returned information is not what we expect. This code hasn't change in while, and it seems the bug just wasn't triggered all this time. Do you mind providing us with more information about your setup? Mainly the output of Lines 233 to 241 in 3fd303d
|
Thanks for helping 🙏🏻 @aronchick @wdbaruni @aronchick yep you was right, regular use Podman so I run docker on second node. checked but actually same results.
![]() on the server side:
Orchestrator run with: on docker:
so run this: Receive:
But there its no jobs in web ui ![]() ok at the end
|
@YuriyGavrilov sorry this took long to resolve. A fix #4645 for the WebUI request routing has just landed and will be released with v1.5.1 in the next couple of days. |
@wdbaruni thank you 🙏 happy to know it |
v1.5.1. is released with the fix. Thank you for your patience. Please feel free to reopen the issue if you are still facing issues |
Bug Description
Briefly describe the unexpected behavior or performance regression. What happened that wasn’t supposed to?
Just run bacalhau serve --node-type requester,compute --web-ui
Expected Behavior
Detail what you expected to happen instead of the bug.
Steps to Reproduce
but there is one and second on requestor
Bacalhau Versions - 1.5
bacalhau agent version
to get this.bacalhau version
for the client info.Host Environment
Provide details about the environment where the bug occurred:
Job Specification
(If applicable, provide the job spec used when the issue occurred.)
Logs
Agent Logs:
(Include here if applicable.)
Client Logs:
(Include here if applicable.)
There also some panic error when try to run ubuntu hello world
bacalhau docker run ubuntu echo hello --api-host=192.168.0.105
The text was updated successfully, but these errors were encountered: