Hopswork 3.0 error restarting local services

Hi Everyone,

i’ve been done installing hopswork a while ago, at first everything works normally, but now hopswork UI cant be accessed it’s say Error 404 Page Does not exist, here’s the capture

im already tried to run /srv/hops/kagent/kagent/bin/shutdown-all-local-services.sh then /srv/hops/kagent/kagent/bin/start-all-local-services.sh, but still some services wont start here’s the status, how to fix this issue and find the root cause of this error? thank you before

[root@hostname]# /srv/hops/kagent/kagent/bin/status-all-local-services.sh
2023-02-02 08:30:46 INFO [agent/setupLogging] Hops-Kagent started.
2023-02-02 08:30:46 INFO [agent/setupLogging] Heartbeat URL: https://hopsworks.glassfish.service.consul:8182/hopsworks-api/api/agentresou                          rce?action=heartbeat
2023-02-02 08:30:46 INFO [agent/setupLogging] Host Id: [hostname]
2023-02-02 08:30:46 INFO [agent/setupLogging] Hostname: [hostname]
2023-02-02 08:30:46 INFO [agent/setupLogging] Public IP: [ip-address]
2023-02-02 08:30:46 INFO [agent/setupLogging] Private IP: [private-ip-address]
2023-02-02 08:30:46 INFO [service/alive] Service ndb_mgmd is alive
2023-02-02 08:30:46 INFO [service/alive] Service node_exporter is alive
2023-02-02 08:30:46 INFO [service/alive] Service alertmanager is alive
2023-02-02 08:30:46 INFO [service/alive] Service ndbmtd is alive
2023-02-02 08:30:46 INFO [service/alive] Service mysqld is alive
2023-02-02 08:30:46 INFO [service/alive] Service mysqld_exporter is alive
2023-02-02 08:30:46 INFO [service/alive] Service glassfish-domain1 is alive
2023-02-02 08:30:46 INFO [service/alive] Service kagent is alive
2023-02-02 08:30:46 INFO [service/alive] Service opensearch is alive
2023-02-02 08:30:46 INFO [service/alive] Service elastic_exporter is alive
2023-02-02 08:30:46 INFO [service/alive] Service grafana is alive
2023-02-02 08:30:46 INFO [service/alive] Service pushgateway is alive
2023-02-02 08:30:46 INFO [service/alive] Service prometheus is alive
2023-02-02 08:30:46 INFO [service/alive] Service consul is alive
2023-02-02 08:30:46 INFO [service/alive] Service zookeeper is alive
**2023-02-02 08:30:46 ERROR [service/alive] Service namenode is DEAD.**
2023-02-02 08:30:46 INFO [service/alive] Service docker is alive
**2023-02-02 08:30:47 ERROR [service/alive] Service kafka is DEAD.**
**2023-02-02 08:30:47 ERROR [service/alive] Service datanode is DEAD.**
2023-02-02 08:30:47 INFO [service/alive] Service airflow-webserver is alive
**2023-02-02 08:30:47 ERROR [service/alive] Service airflow-scheduler is DEAD.**
**2023-02-02 08:30:47 ERROR [service/alive] Service onlinefs is DEAD.**
**2023-02-02 08:30:47 ERROR [service/alive] Service hopsfsmount is DEAD.**
2023-02-02 08:30:47 INFO [service/alive] Service epipe is alive
2023-02-02 08:30:47 INFO [service/alive] Service hivemetastore is alive
2023-02-02 08:30:47 INFO [service/alive] Service hiveserver2 is alive
**2023-02-02 08:30:47 ERROR [service/alive] Service historyserver is DEAD.**
2023-02-02 08:30:47 INFO [service/alive] Service logstash is alive
2023-02-02 08:30:47 INFO [service/alive] Service opensearch-dashboards is alive
**2023-02-02 08:30:47 ERROR [service/alive] Service resourcemanager is DEAD.**
2023-02-02 08:30:47 INFO [service/alive] Service flinkhistoryserver is alive
**2023-02-02 08:30:47 ERROR [service/alive] Service sparkhistoryserver is DEAD.**
2023-02-02 08:30:47 INFO [service/alive] Service filebeat-spark is alive
2023-02-02 08:30:47 INFO [service/alive] Service filebeat-service is alive
2023-02-02 08:30:47 INFO [service/alive] Service filebeat-tf-serving is alive
2023-02-02 08:30:47 INFO [service/alive] Service filebeat-sklearn-serving is alive
2023-02-02 08:30:47 INFO [service/alive] Service filebeat-jupyter is alive
**2023-02-02 08:30:47 ERROR [service/alive] Service nodemanager is DEAD.**
**2023-02-02 08:30:47 ERROR [service/alive] Service livy is DEAD.**
[root@hostname]#