General reason: the configuration file was modified when the Nacos service was not closed
Solution: close Nacos and delete the data, logs and status directories under the Nacos installation folder Then restart
Read More:
- [Solved] Nacos Start Error: failed to req API:127.0.0.1:8848/nacos/v1/ns/service/list. code:503 msg: server is DOWN now
- Nacos Error: server is DOWN now, please try again later! [How to Solve]
- [Solved] Kafka Start Log Error: WARN Found a corrupted index file due to requirement failed: Corrupt index found
- [Solved] HBase shell command Error: ERROR: connection closed
- NFS startup error: restart failed [How to Solve]
- [Solved] JIRA startup error: JIRA startup failed, JIRA has been locked.
- How to Solve “Error db.num is null” when starting Nacos
- Dubbo Error: HTTP method names must be tokens
- [Solved] Rsync synchronization Error: @ERROR: Unknown module xxx
- Hbase Error: Regions In Transition [How to Solve]
- HBase shell Find ERROR: org.apache.hadoop.hbase.PleaseHoldException: Master is initializing
- [Solved] Postgres Start Error: Job for postgresql.service failed because the control process exited with error code.
- [Solved] failed to req API:localhost:8848/nacos/v1/ns/instance. code:500 msg: java.net.ConnectException
- How to Solve VMware Workstation Error: This virtual machine appears to be in use.
- [Solved] Kibana Error: Kibana server is not ready yet
- Rabbitmq failed to stop normally: ERROR: node with name “rabbit” already running on “localhost”
- [Solved] Redis startup error Creating Server TCP listening socket 127.0.0.1:6379: bind: No error
- [Solved] “Failed to run kubelet“ err=“failed to run Kubelet: misconfiguration: kubelet cgroup driver: \“cgrou
- When installing zookeeper, you can view the process start, but the status display error: Error contacting service. It is probably not running
- [Solved] Redis Execute redis-cli shutdown Error: (error) ERR Errors trying to SHUTDOWN. Check logs.