-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
NACOS 1.0.0 code:503 msg: server is DOWN now, please try again later! #1189
Comments
the same to you . |
solved. cluster.conf can`t mark localhost or 127.0.0.1 . must be specific ip or domain |
@haochencheng Check your error log on server, the directory is |
也有同样的问题, cluster.conf 没有localhost或者127.0.0.1,三个节点,其中一个节点始终报这个错误,控制台可以打开 |
@haochencheng 解决这个问题了吗 |
没有。 |
i write my inet in cluster.conf like that
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
|
This is a server list error. What's the content in cluster.conf? |
我没有错误,但是我在群里看到很多人都是集群某一个节点有问题 |
@haochencheng If you run Nacos in cluster mode, you have to configure at least 3 nodes in cluster.conf |
The same to you. How to fixed it? |
我也是这个问题, 集群里面都是配置的真实ip,注册服务的时候,其中一台机器一直报错503,服务也没注册上去 @nkorange 并且看到221机器的 naming-ephemeral.log这个日志一直在刷这个信息: 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... |
@dolcevitaforever 三台机器的cluster.conf内容一样吗?naming-raft.log看看是否有报错,重启221是否能解决? |
你好, @nkorange 重启221之后,还是一样的错误 重启了221之后,看到221的naming-raft.log中有这个信息: 2019-05-20 12:30:50,721 INFO add listener: com.alibaba.nacos.naming.domains.meta.00-00---000-NACOS_SWITCH_DOMAIN-000---00-00 2019-05-20 12:30:54,617 INFO 192.168.1.220:8848 has become the LEADER, local: {"heartbeatDueMs":5000,"ip":"192.168.1.221:8848","leaderDueMs":16491,"state":"FOLLOWER","term":0,"voteFor":""}, leader: {"heartbeatDueMs":5000,"ip":"192.168.1.220:8848","leaderDueMs":19496,"state":"LEADER","term":38,"voteFor":"192.168.1.220:8848"} 99的naming-raft.log中: 2019-05-20 10:57:32,434 INFO [RAFT] received beat with 0 keys, RaftCore.datums' size is 0, remote server: 192.168.1.221:8848, term: 37, local term: 0 2019-05-20 10:57:32,534 INFO raft peers changed: [{"adWeight":0,"alive":false,"ip":"192.168.1.220","key":"192.168.1.220:8848","lastRefTime":0,"lastRefTimeStr":"","servePort":8848,"site":"unknown","weight":1}, {"adWeight":0,"alive":false,"ip":"192.168.1.221","key":"192.168.1.221:8848","lastRefTime":0,"lastRefTimeStr":"","servePort":8848,"site":"unknown","weight":1}, {"adWeight":0,"alive":false,"ip":"192.168.1.99","key":"192.168.1.99:8848","lastRefTime":0,"lastRefTimeStr":"","servePort":8848,"site":"unknown","weight":1}] 我这个集群应该是启动成功的,可是现在服务注册的时候, 控制台还是221节点的503错误: at com.alibaba.nacos.client.naming.net.NamingProxy.callServer(NamingProxy.java:340) |
@nkorange 99的日志贴错了,是这段 2019-05-20 12:27:33,885 INFO vote 192.168.1.220:8848 as leader, term: 38 2019-05-20 12:27:38,849 INFO 192.168.1.220:8848 has become the LEADER, local: {"heartbeatDueMs":5000,"ip":"192.168.1.99:8848","leaderDueMs":18519,"state":"FOLLOWER","term":38,"voteFor":"192.168.1.220:8848"}, leader: {"heartbeatDueMs":5000,"ip":"192.168.1.220:8848","leaderDueMs":18222,"state":"LEADER","term":38,"voteFor":"192.168.1.220:8848"} 2019-05-20 12:27:38,849 INFO [RAFT] received beat with 0 keys, RaftCore.datums' size is 0, remote server: 192.168.1.220:8848, term: 38, local term: 38 |
@dolcevitaforever 在220上执行
看看返回结果是什么。 |
@nkorange 你好, 220上执行 返回结果是: |
@dolcevitaforever 这是个bug,参考 #1091 ,1.0.1会发布修复这个问题。当前你可以基于master分支运行命令:
来构建最新修复包,构建后包的位置在distribution/target/下 |
好的, thanks ` @nkorange |
The text was updated successfully, but these errors were encountered: