-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
[BUG] last resolver error: produced zero addresses #2529
Comments
OpenIM Server Versionrelease-v3.8 Operating System and CPU ArchitectureLinux (AMD) Deployment MethodSource Code Deployment Bug Description and Steps to ReproduceCall api /auth/user_token once every minute. After starting the server, the call is normal. Something goes wrong after a while.
Screenshots LinkNo response |
Hello! Thank you for filing an issue. If this is a bug report, please include relevant logs to help us debug the problem. Join slack 🤖 to connect and communicate with our developers. |
First, run the command "mage check" to check . |
|
|
When the message "produced zero addresses" appears, you need to take action. |
How did you set it up? |
The
|
I suggest you use the source code for the deployment. |
Can you tell me if the IP address 74.48.52.186 is a public one or just an internal network address? |
The server is compiled from source code. Both the compilation and execution are done inside a Docker container with image “golang”.
public, with linux firewall |
There's no need to use a public IP address. |
Is this issue related to the internal IP or public IP? |
When you run into an issue, take a look at the data on etcd. |
I keep running the follow command for a long time, during which it only outputs some PUT and DELETE.
|
try to watch /openim |
|
I deployed the server and all other components like redis and etcd kafka on the same server, and the issue has not occurred again. The issue may be caused by a communication problem between the server and other components that has not been resolved. For example, the server may not have properly reconnected after losing connection with Redis. |
We'll be testing it soon. Thanks for bringing this up. |
We deployed Mongo and Redis separately from the server and tested them for a while, but did not encounter this issue. You can try updating the code and testing again. If the issue persists, please provide more specific steps to reproduce the problem. |
etcdctl get "" --prefix --keys-only openim/auth/10.3.0.11:10200 openim/chat/10.3.0.11:30300 openim/conversation/10.3.0.11:10220 openim/encryption/10.3.0.11:10500 openim/friend/10.3.0.11:10240 openim/group/10.3.0.11:10260 openim/meeting/10.3.0.11:10112 openim/messageGateway/10.3.0.11:10140 openim/msg/10.3.0.11:10280 openim/office/10.3.0.11:30400 openim/organization/10.3.0.11:30500 openim/push/10.3.0.11:10170 openim/push/10.3.0.11:10171 openim/push/10.3.0.11:10172 openim/push/10.3.0.11:10173 openim/push/10.3.0.11:10174 openim/push/10.3.0.11:10175 openim/push/10.3.0.11:10176 openim/push/10.3.0.11:10177 openim/signal/10.3.0.11:10212 openim/third/10.3.0.11:10300 openim/user/10.3.0.11:10320 |
OpenIM Server Version
release-v3.8
Operating System and CPU Architecture
Linux (AMD)
Deployment Method
Source Code Deployment
Bug Description and Steps to Reproduce
每分钟一次调用api /auth/user_token。启动server后,调用正常。过一段时间后就会出错。
Screenshots Link
No response
The text was updated successfully, but these errors were encountered: