[Odessa] Oops!!! xxxx service is unavailable!

[yqhsmile]

Odessa ui always makes the following errors:

Svc Unavailable
**Oops!!! scheduler service is unavailable!**
This could be a network reason, or it could be that the scheduler microservice is not running, make sure there is no network problem or that the scheduler service is already running!

EdgeXFoundry uses a microservices architecture, each service is running independently, please make sure that the current service is already running, if you have manually started the service, click the Refresh button.


Svc Unavailable
**Oops!!! rule engine service is unavailable!**
This could be a network reason, or it could be that the rule engine microservice is not running, make sure there is no network problem or that the rule engine service is already running!

EdgeXFoundry uses a microservices architecture, each service is running independently, please make sure that the current service is already running, if you have manually started the service, click the Refresh button.


Svc Unavailable
**Oops!!! registry center service is unavailable!**
This could be a network reason, or it could be that the registry center microservice is not running, make sure there is no network problem or that the registry center service is already running!

EdgeXFoundry uses a microservices architecture, each service is running independently, please make sure that the current service is already running, if you have manually started the service, click the Refresh button.

error logs in edgex-ui-go:

2025/05/14 14:52:47 http: proxy error: dial tcp 172.19.0.12:59861: connect: connection refused

/rules-engine/ping

2025/05/14 14:55:59 http: proxy error: dial tcp: lookup edgex-kuiper on 127.0.0.11:53: no such host

/support-scheduler/api/v3/ping

2025/05/14 14:56:12 http: proxy error: dial tcp 172.19.0.12:59861: connect: connection refused

/rules-engine/ping

2025/05/14 14:58:03 http: proxy error: dial tcp: lookup edgex-kuiper on 127.0.0.11:53: no such host

/core-data/api/v3/ping

/core-data/api/v3/ping

/support-scheduler/api/v3/ping

2025/05/14 15:11:29 http: proxy error: dial tcp 172.19.0.12:59861: connect: connection refused

/rules-engine/ping

2025/05/14 15:11:31 http: proxy error: dial tcp: lookup edgex-kuiper on 127.0.0.11:53: no such host

And I found that there is such a problem in cmd/edgex-ui-server/res/docker/configuration.yaml:

Registry config is error ???? Why is it still consul ??? How to solve the three problems mentioned above???

Also, the ports here are different in cmd/edgex-ui-server/res/docker/configuration.yaml and docker-compose.yml，I changed 59863 in docker-compose.yml to 59861， but it still reports the three errors mentioned above.

Is there any problem with the Odessa version? How to solve it?

@judehung @cloudxxx8 @FelixTing @weichou1229

[cloudxxx8]

It looks like there are still lots of to do in edgex-ui.
Aside from the edgex-ui, do you see any issues for other services?

Please open the related issues to edgex-ui-go and see if there is any volunteer could help update it.

[2431236609]

Thank you, but this doesn't solve the problem completely.
We are looking forward to other solutions or an official solution.

[2431236609]

We still have this issue above.
When we just started using EdgeX (Odessa branch) the southbound sensor data is received correctly, but in the UI the AppService shows the following problem:

2 Possible cause:
- Keeper has replaced Consul as the registry
- However, the Web UI is still trying to connect to the old Consul API

3 Resolution
- This shouldn't affect core EdgeX functionality, right?
- Is this issue already on the roadmap?
- Is there any earlier version we can run?

We hope to resolve this issue promptly to enable visual management of the app.
Welcome your valuable suggestions.

[2431236609]

@cloudxxx8
Could you re-check this issue and give us some advice or help?

[cloudxxx8]

No, as I mentioned:
Please open the related issues with a clear context to edgex-ui-go repository and see if there is any volunteer could help update it.
I am not able to help any UI issue.

[2431236609]

Alright, it's a pity that this function is not available curently.