Skip to content

NACOS 1.0.0 code:503 msg: server is DOWN now, please try again later! #1189

New issue
New issue
Closed
Closed
NACOS 1.0.0 code:503 msg: server is DOWN now, please try again later!#1189
@haochencheng

Description

@haochencheng
haochencheng
opened on May 8, 2019
2019-05-08 11:17:09.746  INFO 50906 --- [ing.beat.sender] com.alibaba.nacos.client.naming          : [BEAT] 68da671b-ef91-47e0-b5d0-d3a458bd743a sending beat to server: {"cluster":"DEFAULT","ip":"192.168.69.244","metadata":{"preserved.register.source":"SPRING_CLOUD"},"port":40100,"scheduled":true,"serviceName":"DEFAULT_GROUP@@microservice-integration-gateway","weight":1.0}
2019-05-08 11:17:09.748 DEBUG 50906 --- [ing.beat.sender] com.alibaba.nacos.client.naming          : Request from server: http://127.0.0.1:8848/nacos/v1/ns/instance/beat?beat=%7B%22cluster%22%3A%22DEFAULT%22%2C%22ip%22%3A%22192.168.69.244%22%2C%22metadata%22%3A%7B%22preserved.register.source%22%3A%22SPRING_CLOUD%22%7D%2C%22port%22%3A40100%2C%22scheduled%22%3Atrue%2C%22serviceName%22%3A%22DEFAULT_GROUP%40%40microservice-integration-gateway%22%2C%22weight%22%3A1.0%7D&serviceName=DEFAULT_GROUP%40%40microservice-integration-gateway&encoding=UTF-8&namespaceId=68da671b-ef91-47e0-b5d0-d3a458bd743a
2019-05-08 11:17:09.751 ERROR 50906 --- [ing.beat.sender] com.alibaba.nacos.client.naming          : request 127.0.0.1:8848 failed.

com.alibaba.nacos.api.exception.NacosException: failed to req API:http://127.0.0.1:8848/nacos/v1/ns/instance/beat. code:503 msg: server is DOWN now, please try again later!
	at com.alibaba.nacos.client.naming.net.NamingProxy.callServer(NamingProxy.java:340)
	at com.alibaba.nacos.client.naming.net.NamingProxy.reqAPI(NamingProxy.java:367)
	at com.alibaba.nacos.client.naming.net.NamingProxy.reqAPI(NamingProxy.java:304)
	at com.alibaba.nacos.client.naming.net.NamingProxy.sendBeat(NamingProxy.java:227)
	at com.alibaba.nacos.client.naming.beat.BeatReactor$BeatTask.run(BeatReactor.java:109)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run$$$capture(FutureTask.java:266)
	at java.util.concurrent.FutureTask.run(FutureTask.java)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)

2019-05-08 11:17:09.751 ERROR 50906 --- [ing.beat.sender] com.alibaba.nacos.client.naming          : [CLIENT-BEAT] failed to send beat: {"cluster":"DEFAULT","ip":"192.168.69.244","metadata":{"preserved.register.source":"SPRING_CLOUD"},"port":40100,"scheduled":true,"serviceName":"DEFAULT_GROUP@@microservice-integration-gateway","weight":1.0}

Activity

leavegee

leavegee commented on May 8, 2019

@leavegee
leavegee
on May 8, 2019

the same to you .

leavegee

leavegee commented on May 8, 2019

@leavegee
leavegee
on May 8, 2019

solved. cluster.conf can`t mark localhost or 127.0.0.1 . must be specific ip or domain

nkorange

nkorange commented on May 8, 2019

@nkorange
nkorange
on May 8, 2019
Collaborator

@haochencheng Check your error log on server, the directory is {nacos.home}/logs.

imkiven

imkiven commented on May 9, 2019

@imkiven
imkiven
on May 9, 2019

也有同样的问题， cluster.conf 没有localhost或者127.0.0.1，三个节点，其中一个节点始终报这个错误，控制台可以打开

imkiven
mentioned this on May 9, 2019
imkiven

imkiven commented on May 9, 2019

@imkiven
imkiven
on May 9, 2019

@haochencheng 解决这个问题了吗

haochencheng

haochencheng commented on May 9, 2019

@haochencheng
haochencheng
on May 9, 2019
Author

@haochencheng 解决这个问题了吗

没有。

haochencheng

haochencheng commented on May 9, 2019

@haochencheng
haochencheng
on May 9, 2019
Author

127.0.0.1
when i cluster.conf mark localhost or 127.0.0.1 ,
it will be throw IllegalArgumentException like that

java.lang.IllegalArgumentException: server: 192.168.199.200:8848 is not in serverlist
	at com.alibaba.nacos.naming.cluster.ServerListManager.onReceiveServerStatus(ServerListManager.java:196)
	at com.alibaba.nacos.naming.cluster.ServerListManager$ServerStatusReporter.run(ServerListManager.java:415)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)

i write my inet in cluster.conf like that

#it is ip
#example
192.168.199.200

and restart nacos , when id register a new service it will be return

server is DOWN now, please try again later!%

here is my naming-server.log

2019-05-09 15:35:59,465 INFO listen for service meta change

2019-05-09 15:36:02,362 INFO [SERVER-INIT] got port: 8848

2019-05-09 15:36:02,362 INFO [SERVER-INIT] got path: /nacos

2019-05-09 15:36:04,263 INFO receive config info: unknown#192.168.199.200:8848#1557387364262#2


2019-05-09 15:36:04,264 INFO [NACOS-DISTRO] healthy server list changed, disable health check for 60000 ms from now on, old: [], new: [{"adWeight":0,"alive":true,"ip":"192.168.199.200","key":"192.168.199.200:8848","lastRefTime":1557387364262,"lastRefTimeStr":"2019-05-09 15:36:04","servePort":8848,"site":"unknown","weight":2}]

2019-05-09 15:36:19,269 INFO receive config info: unknown#192.168.199.200:8848#1557387379269#2


2019-05-09 15:36:31,031 INFO [HEALTH-CHECK] health check is false

2019-05-09 15:36:34,274 INFO receive config info: unknown#192.168.199.200:8848#1557387394273#2


2019-05-09 15:36:49,278 INFO receive config info: unknown#192.168.199.200:8848#1557387409278#2
haochencheng

haochencheng commented on May 9, 2019

@haochencheng
haochencheng
on May 9, 2019
Author

@nkorange

nkorange

nkorange commented on May 10, 2019

@nkorange
nkorange
on May 10, 2019
Collaborator

This is a server list error. What's the content in cluster.conf?

imkiven

imkiven commented on May 10, 2019

@imkiven
imkiven
on May 10, 2019

我没有错误，但是我在群里看到很多人都是集群某一个节点有问题

nkorange

nkorange commented on May 15, 2019

@nkorange
nkorange
on May 15, 2019
Collaborator

@haochencheng If you run Nacos in cluster mode, you have to configure at least 3 nodes in cluster.conf

ljh205sy

ljh205sy commented on May 15, 2019

@ljh205sy
ljh205sy
on May 15, 2019

The same to you. How to fixed it?

dolcevitaforever

dolcevitaforever commented on May 20, 2019

@dolcevitaforever
dolcevitaforever
on May 20, 2019

我也是这个问题， 集群里面都是配置的真实ip，注册服务的时候，其中一台机器一直报错503，服务也没注册上去 @nkorange
request 192.168.1.221:8848 failed.
com.alibaba.nacos.api.exception.NacosException: failed to req API:http://192.168.1.221:8848/nacos/v1/ns/instance/beat. code:503 msg: server is DOWN now, please try again later!
at com.alibaba.nacos.client.naming.net.NamingProxy.callServer(NamingProxy.java:340)
at com.alibaba.nacos.client.naming.net.NamingProxy.reqAPI(NamingProxy.java:367)
at com.alibaba.nacos.client.naming.net.NamingProxy.reqAPI(NamingProxy.java:304)
at com.alibaba.nacos.client.naming.net.NamingProxy.sendBeat(NamingProxy.java:227)
at com.alibaba.nacos.client.naming.beat.BeatReactor$BeatTask.run(BeatReactor.java:109)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
2019-05-20 12:19:48.084 [com.alibaba.nacos.naming.beat.sender] ERROR com.alibaba.nacos.client.naming -
request 192.168.1.221:8848 failed.
com.alibaba.nacos.api.exception.NacosException: failed to req API:http://192.168.1.221:8848/nacos/v1/ns/instance/beat. code:503 msg: server is DOWN now, please try again later!
at com.alibaba.nacos.client.naming.net.NamingProxy.callServer(NamingProxy.java:340)
at com.alibaba.nacos.client.naming.net.NamingProxy.reqAPI(NamingProxy.java:367)
at com.alibaba.nacos.client.naming.net.NamingProxy.reqAPI(NamingProxy.java:304)
at com.alibaba.nacos.client.naming.net.NamingProxy.sendBeat(NamingProxy.java:227)
at com.alibaba.nacos.client.naming.beat.BeatReactor$BeatTask.run(BeatReactor.java:109)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)

并且看到221机器的 naming-ephemeral.log这个日志一直在刷这个信息：
2019-05-20 12:24:41,829 INFO waiting server list init...

2019-05-20 12:24:42,829 INFO waiting server list init...

2019-05-20 12:24:43,829 INFO waiting server list init...

2019-05-20 12:24:44,829 INFO waiting server list init...

2019-05-20 12:24:45,175 DEBUG sync checksums: {com.alibaba.nacos.naming.iplist.ephemeral.a74cd717-d6b8-4a76-a7ca-0c601793c6d6##DEFAULT_GROUP@@service-feign=621f8b50571ba2f64a22d8a4c728fcc}

2019-05-20 12:24:45,829 INFO waiting server list init...

2019-05-20 12:24:46,829 INFO waiting server list init...

2019-05-20 12:24:47,830 INFO waiting server list init...

2019-05-20 12:24:48,830 INFO waiting server list init...

2019-05-20 12:24:49,830 INFO waiting server list init...

2019-05-20 12:24:50,176 DEBUG sync checksums: {com.alibaba.nacos.naming.iplist.ephemeral.a74cd717-d6b8-4a76-a7ca-0c601793c6d6##DEFAULT_GROUP@@service-feign=621f8b50571ba2f64a22d8a4c728fcc}

2019-05-20 12:24:50,830 INFO waiting server list init...

2019-05-20 12:24:51,830 INFO waiting server list init...

2019-05-20 12:24:52,830 INFO waiting server list init...

2019-05-20 12:24:53,831 INFO waiting server list init...

2019-05-20 12:24:54,831 INFO waiting server list init...

2019-05-20 12:24:55,176 DEBUG sync checksums: {com.alibaba.nacos.naming.iplist.ephemeral.a74cd717-d6b8-4a76-a7ca-0c601793c6d6##DEFAULT_GROUP@@service-feign=621f8b50571ba2f64a22d8a4c728fcc}

2019-05-20 12:24:55,831 INFO waiting server list init...

nkorange

nkorange commented on May 20, 2019

@nkorange
nkorange
on May 20, 2019 · edited by nkorange
Collaborator

@dolcevitaforever 三台机器的cluster.conf内容一样吗？naming-raft.log看看是否有报错，重启221是否能解决？

9 remaining items

Loading
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @imkiven@leavegee@nkorange@haochencheng@ljh205sy

        Issue actions
          NACOS 1.0.0 code:503 msg: server is DOWN now, please try again later! · Issue #1189 · alibaba/nacos