My Oracle Support Banner

Managed Server Fails To Start Via SSH Node Manager : <BEA-002606> Unable to create a server socket for listening on channel "Default" (Doc ID 1564370.1)

Last updated on OCTOBER 09, 2018

Applies to:

Oracle WebLogic Server - Version 11.1.1.6.0 and later
Information in this document applies to any platform.

Symptoms

 When using the SSH node manager script wlscontrol.sh to start a managed server, the server fails to start with error, "<BEA-002606> <Unable to create a server socket for listening on channel "Default"" similar to the following error stack:

<Feb 4, 2013 1:25:30 AM EST> <Error> <Server> <BEA-002606> <Unable to create a server socket for listening on channel "Default". The address xxx.xxx.x.xx. might be incorrect or another process is using port 8001: java.net.BindException: Cannot assign requested address.>

Note this is nothing to do with 'server migration,' it is purely SSH node manager startup via wlscontrol.sh

The user account under which these processes are executing has been verified and it has sufficient sudo rights to run the wlsifconfig.sh script.

As a test, "wlsifconfig.sh -addif eth0 xxx.xxx.x.xx 255.255.255.128" and related "removeif" commands can be executed without error.

It appears the wlscontrol.sh is failing to call the wlsifconfig.sh script.
However with debug output activated there is not much indicative logging:

AdminServer shows the error, "<BEA-300048> <Unable to start the server ms01 : Server failed to start (see server output log for details)>"

DEBUG: ShellClient: Executing shell command: ssh -l oracle -o PasswordAuthentication=no -p 22 mymachine /u00/app/oracle/product/dir/wlserver_10.3/common/bin/wlscontrol.sh -d mydomain -c -f startManagedWebLogic.sh -s \'ms02\' STAT
DEBUG: ShellClient: STDOUT: WLScontrol thinks ServerDir is: /u00/app/oracle/admin/mydomain/servers/ms02
DEBUG: ShellClient: STDOUT: WLScontrol thinks ServerName is: ms02
DEBUG: ShellClient: STDOUT: FAILED_NOT_RESTARTABLE
DEBUG: ShellClient: STDOUT: WLScontrol thinks ServerDir is: /u00/app/oracle/admin/mydomain/servers/ms01
DEBUG: ShellClient: STDOUT: WLScontrol thinks ServerName is: ms01
DEBUG: ShellClient: STDOUT: STARTING
DEBUG: ShellClient: STDERR: Server failed to start (see server output log for details)
<Feb 4, 2013 1:25:35 AM EST> <Error> <NodeManager> <BEA-300048> <Unable to start the server ms01 : Server failed to start (see server output log for details)>


The "Shell Command" value in use for the machine's node manager config is:

ssh -l oracle -o PasswordAuthentication=no -p %P %H /u00/app/oracle/product/dir/wlserver_10.3/common/bin/wlscontrol.sh -d %D -s %S %C

de-reffing the values results in a command thus :

ssh -l oracle -o PasswordAuthentication=no -p 22 mymachine /u00/app/oracle/product/dir/wlserver_10.3/common/bin/wlscontrol.sh
-d mydomain -c -f startManagedWebLogic.sh -s \'ms01\' START

This results in a managed instance process that starts normally, then fails and force shuts down due to no interface being configured:

<Mar 27, 2013 1:00:47 PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
<Mar 27, 2013 1:00:47 PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
<Mar 27, 2013 1:00:47 PM EDT> <Notice> <Cluster> <BEA-000162> <Starting "async" replication service with remote cluster address "ms01:8001,ms02:8001">
<Mar 27, 2013 1:00:47 PM EDT> <Emergency> <Security> <BEA-090087> <Server failed to bind to the configured Admin port. The port may already be used by another process.>
<Mar 27, 2013 1:00:47 PM EDT> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason: Server failed to bind to any usable port. See preceeding log message for details.>
<Mar 27, 2013 1:00:47 PM EDT> <Error> <Server> <BEA-002606> <Unable to create a server socket for listening on channel "Default". The address xxx.xxx.x.xx might be incorrect or another process is using port 8001: java.net.BindException: Cannot assign requested address.>
<Mar 27, 2013 1:00:47 PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Mar 27, 2013 1:00:47 PM EDT> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Mar 27, 2013 1:00:47 PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>

 

The /etc/hosts and ifconfig -a all show normal operation.

 

 





Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.