need help to solve the--- "NettyRemotingServer bind fail bind(..)" #13004
expressways
started this conversation in
General
Replies: 4 comments 1 reply
-
version 3.1.1 |
Beta Was this translation helpful? Give feedback.
0 replies
-
From the stack log, it may be that the IP or port on the worker machine is occupied |
Beta Was this translation helpful? Give feedback.
0 replies
-
If you are sure that the port is not occupied by another program, please check whether the address here in the two configuration files is the same, if it is the same, this will cause this error |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
[ERROR] 2022-11-25 04:14:54.795 +0800 org.apache.dolphinscheduler.remote.NettyRemotingServer:[143] - [WorkflowInstance-0][TaskInstance-0] - NettyRemotingServer bind fail bind(..) failed: Address already in use, exit
io.netty.channel.unix.Errors$NativeIoException: bind(..) failed: Address already in use
[ERROR] 2022-11-25 04:14:54.795 +0800 org.apache.dolphinscheduler.server.worker.registry.WorkerWaitingStrategy:[104] - [WorkflowInstance-0][TaskInstance-0] - Recover from waiting failed, the current server status is RUNNING, will stop the server
org.apache.dolphinscheduler.remote.exceptions.RemoteException: NettyRemotingServer bind 1234 fail
at org.apache.dolphinscheduler.remote.NettyRemotingServer.start(NettyRemotingServer.java:144)
at org.apache.dolphinscheduler.server.worker.rpc.WorkerRpcServer.start(WorkerRpcServer.java:93)
at org.apache.dolphinscheduler.server.worker.registry.WorkerWaitingStrategy.reStartWorkerResource(WorkerWaitingStrategy.java:130)
at org.apache.dolphinscheduler.server.worker.registry.WorkerWaitingStrategy.reconnect(WorkerWaitingStrategy.java:97)
at org.apache.dolphinscheduler.server.worker.registry.WorkerConnectionStateListener.onUpdate(WorkerConnectionStateListener.java:54)
at org.apache.dolphinscheduler.plugin.registry.zookeeper.ZookeeperConnectionStateListener.stateChanged(ZookeeperConnectionStateListener.java:49)
at org.apache.curator.framework.state.ConnectionStateManager.lambda$processEvents$0(ConnectionStateManager.java:281)
at org.apache.curator.framework.listen.MappingListenerManager.lambda$forEach$0(MappingListenerManager.java:92)
at org.apache.curator.framework.listen.MappingListenerManager.forEach(MappingListenerManager.java:89)
at org.apache.curator.framework.listen.StandardListenerManager.forEach(StandardListenerManager.java:89)
at org.apache.curator.framework.state.ConnectionStateManager.processEvents(ConnectionStateManager.java:281)
at org.apache.curator.framework.state.ConnectionStateManager.access$000(ConnectionStateManager.java:43)
at org.apache.curator.framework.state.ConnectionStateManager$1.call(ConnectionStateManager.java:134)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
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)
[INFO] 2022-11-25 04:14:57.795 +0800 org.apache.dolphinscheduler.server.worker.WorkerServer:[148] - [WorkflowInstance-0][TaskInstance-0] - Worker server is stopping, current cause : Recover from waiting failed, the current server status is RUNNING, will stop the server
[INFO] 2022-11-25 04:14:57.796 +0800 org.apache.dolphinscheduler.server.worker.WorkerServer:[171] - [WorkflowInstance-0][TaskInstance-0] - Worker begin to kill all cache task, task size: 1
[INFO] 2022-11-25 04:14:57.796 +0800 org.apache.dolphinscheduler.plugin.task.api.ProcessUtils:[55] - [WorkflowInstance-548][TaskInstance-12306] - Begin kill task instance, processId: 0
[ERROR] 2022-11-25 04:14:57.796 +0800 org.apache.dolphinscheduler.plugin.task.api.ProcessUtils:[58] - [WorkflowInstance-548][TaskInstance-12306] - Task instance kill failed, processId is not exist
Beta Was this translation helpful? Give feedback.
All reactions