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

server is STARTING now, please try again later! #21

Closed
kokasumi opened this issue Apr 16, 2019 · 10 comments
Closed

server is STARTING now, please try again later! #21

kokasumi opened this issue Apr 16, 2019 · 10 comments
Assignees

Comments

@kokasumi
Copy link

kokasumi commented Apr 16, 2019

Scene

  1. Nacos-K8S deployed in Aliyun K8S cluster
  2. Use k8s Ingress type expose the nacos,and can access through domain
  3. Get ready the config file through nacos console
  4. I can get the config file through ’curl -X GET "http://cluster-ip:8848/nacos/v1/cs/configs?dataId=nacos.cfg.dataId&group=test"‘,and get config file in Spring Cloud project.

Question:
I can't register the service,regadless of in Spring Cloud project alse through 'curl -X PUT 'http://cluster-ip:8848/nacos/v1/ns/instance?serviceName=nacos.naming.serviceName&ip=20.18.7.10&port=8080'' 。And in spring cloud return failed to req API:/nacos/v1/ns/instance after all servers([cluster-ip:8848]) tried ,and return the result server is STARTING now, please try again later! through 'curl -X PUT 'http://cluster-ip:8848/nacos/v1/ns/instance?serviceName=nacos.naming.serviceName&ip=20.18.7.10&port=8080'' .

How could I do to solve the problem?Thanks!

@paderlol
Copy link
Collaborator

You need to check the following nacos server logs to see if there are any exceptions

@paderlol paderlol self-assigned this Apr 16, 2019
@kokasumi
Copy link
Author

You need to check the following nacos server logs to see if there are any exceptions

How can I check the logs,I use the "kubectl logs -f nacos-0",and have no any access log.Is there has any other logs?

@paderlol
Copy link
Collaborator

u can see the log in the nfs log or kubectl exec in pod

@kokasumi
Copy link
Author

kokasumi commented Apr 16, 2019

u can see the log in the nfs log or kubectl exec in pod

In pod,I can see some logs in "data/" folder,where can i see the register logs!

057AD538-0E34-4249-8590-06D9A6C004BB

@HiroC222
Copy link
Contributor

1111
同款问题

@kokasumi
Copy link
Author

In access_log logs,I see the error log,the status code is 503 and 400.
05C29BAF-ED73-4fb4-B898-FD2B1E724F16
76634EDC-0D72-41c3-B978-31FAD84EEDB5

Is there has any problem in nacos server config?

@kokasumi
Copy link
Author

I have 3 nodes,and exec "tailf naming-server.log"
AB0D8D89-603E-40ad-8297-03A921F77705
113A44EB-8278-4a2c-97F1-906F3C9ABA1F
BE0516CA-0558-4b5f-8068-C07BA5CBF0E4

@kokasumi
Copy link
Author

@paderlol Tank you for your help.I solved the problem after nacos cluster restart.

@kokasumi
Copy link
Author

1111
同款问题
重启集群试试

@HiroC222
Copy link
Contributor

是的,我这边也ok。 只有重启nacos-0后才会正常,单独重启1、2都不行,所有都重启也没好使。

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants