WebLogic – Error starting managed server from Console : Node Manager associated with this machine is not reachable

This post cover steps on where to look for issues related to starting Managed Server via WebLogic Console.

If you are new to WebLogic then first go through WebLogic Domain, Administration Server and Managed Server here , start/stop in Weblogic Server here and Node Manager in WebLogic here

How to start Managed Server via WebLogic Console (/console application running on Administration Server) ?

  • Login to console http://hostname.domainname:admin_port/console
  • Environment -> Servers -> click on tab Control -> select Managed Server which you wish to start -> click on button Start

Prereq for Managed Server to start via Console ?
1.
Start Node Manager ($WL_HOME/server/bin/startNodeManager.sh)
2. Configure Machine and verify NodeManager details (Listen Address and Port) ; Environment -> Machines -> Configuration -> Node  Manager

.


.

3. Attach Managed Server to Machine : Environment -> Servers -> [select managed server] -> under General tab Configuration , select machine

4. Add domain loaction in $WL_HOME/common/nodemanager/nodemanager.domains
entry like
base_domain=/oracle/apps/fmw/user_projects/domains/base_domain

5. Restart Node Manager and try starting Managed Server from Console

.

Error Message

If you hit errors starting Managed Server (in WebLogic) from console like
For Server name_of_managed_server],  the Node Manager associated with machine [Machine_Name] is not reachable ” then here is step to troubleshoot

1. Check if Machine is configured against Node where Managed Server is running. (via console)
2. Check Node Manager IP and port number configured for that Machine (via console)
3. Check if Node Manager is running on that machine on that port (netstat -an | grep [port_number])
4. If Administration Server and Managed server are on different machine and if there is firewall between two machines then check Node Manager port is open across firewall
5. Check Node Manager log file for any errors
6. Check if there is any issue with SSL certificate (Administration Server communicates with NodeManager via SSL) : Disable hostname verification if this is an issue (or recreate certificate)
In my case there was error in Node Manager log file

12-Mar-2010 17:35:17 weblogic.nodemanager.server.NMServer main
SEVERE: Fatal error in node manager server
java. lang. Class Cast Exception: sun.nio.ch. InheritedChannel $InheritedSocketChannel
Impl
at weblogic.nodemanager.server.Listener.<init>(Listener.java:42)
at weblogic.nodemanager.server.SSLListener.<init>(SSLListener.java:32)
at weblogic.nodemanager.server.NMServer.start(NMServer.java:200)
at weblogic.nodemanager.server.NMServer.main(NMServer.java:355)
at weblogic.NodeManager.main(NodeManager.java:31)

Have you seen this issue in your Node Manager setup (I am using JRockit on Sun Solaris 10 Sparc 64 bit and Node Manager shipped with FMW 11.1.1.2.0 Binary) ?


Can you help me in fixing this issue ?

Did you get a chance to download Free Interview Questions related to WebLogic? If not, download it here http://k21academy.com/weblogic-interview-question

web

Learn Oracle Weblogic Server Administration

If you want to learn Oracle WebLogic Server Administration with tons of additional features like Live Interactive Sessions, Life time access to membership portal, Free re-taking sessions for next one year, Dedicated Machine to practice, On Job Support and much more

Click here to know more

Share This Post with Your Friends over Social Media!

About the Author Atul Kumar

Oracle ACE, Author, Speaker and Founder of K21 Technologies & K21 Academy : Specialising in Design, Implement, and Trainings.

follow me on:

Leave a Comment:

42 comments
sawanahluwalia says April 11, 2010

Atul,

I am confused, error posted by you is for node manager server and not for managed server, thus in case where your NM aint up how can you get MS started using it 🙂

Reply
Atul Kumar says April 11, 2010

@Sawanahluwalia,
Yes you are right , I can’t start managed server from console unless my node manager is up and listening.

I configured node manager as service (and configured to start it with Solaris Machine). I assumed that it should be up and tried starting managed server from console.

I got error message that node manager associated this this machine is not reachable and thats when I checked Node Manager log file and saw severe error message . I am still learning weblogic and this post is mainly for those who are new to WebLogic and Node manager (Like me ;-))

Reply
sawanahluwalia says April 12, 2010

As far as i go i would never start it from console 🙂
but trying new things would make you wear an experienced hat.

Hope you are doing good; keep in touch.

regards,
Sawan

Reply
kiran says April 12, 2010

Hello Atul,

Could you please tell some information about Oracle iflex Flexcube software and give some notes on it?

Thank you.


Best Regards,
Kiran

Reply
Arun says November 1, 2010

Can you please tell me where to add delay time for managed server startup in oracle fusion weblogic.

The requirement is to add wait/sleep while starting multiple instances via admin console.

Regards,
Arun

Reply
poornima says December 31, 2010

Hi Atul,
I was trying to configure the node manager for UCM 11g on weblogic on windows as a stand alone.

Unfortunately when I try to start my managed server from the console i get the following error!

———-
For server UCM_server1, the Node Manager associated with machine ossi-2215 is not reachable.
All of the servers selected are currently in a state which is incompatible with this operation or are not associated with a running Node Manager or you are not authorized to perform the action requested. No action will be performed.

—————————

First I installed weblogic, and then installed UCM by creating the domain for UCM. I had tried to configure the node after these steps by following the guidelines provided by oracle. But unfortunately I got lost.(In the console, i created a new entry for the machine, then associated the node manager to it)
I have also cross verified the steps mentioned in your post as well.

So basically I want to know how do I verify the following ( which is mentioned in ur post)on my windows machine?

1. Check if Machine is configured against Node where Managed Server is running. (via console)
2. Check Node Manager IP and port number configured for that Machine (via console)
3. Check if Node Manager is running on that machine on that port (netstat -an | grep [port_number])

Reply
Atul Kumar says December 31, 2010

@ Poornima,

Did you start NodeManager on your windows machine ?

Reply
poornima says December 31, 2010

Yes Atul. First i started my admin server and then the node manager from Oracle WebLogic–> WebLogic server 11gR1–> Node Manager

Reply
Atul Kumar says December 31, 2010

@ Poornima,
Login to WebLogic Console then click on “Servers” under environment.
On right side panel check which machine is attached to UCM managed server which you are trying to start from console .

If no machine is attached then click on that managed server and from “Machine” drop down menu attach machine. (You have to define machine first by clicking on “Machine” under Environment tab.

Once you know which machine is attached to this managed server then click on “Machine” under Environment in left panel and then click on Machine which is attached to your UCM managed server. Select tab NodeManager and check if Listen Address and Listen Port is same as one you see when you start NodeManager from windows start menu.

Reply
laick says August 8, 2011

“configured” and “started”… small difference?
check nm just like Atul said… if nm isn’t “Running”
go to Machine2 (via os not console), and check if nodemanager is runnig by
ps -ef | grep NodeManager
– if nm is down – fire it up by /weblogic../server/bin/startNodeManager(.sh)
– if nm is running, you have configuration error

Reply
Pawan says September 20, 2011

Can we start manage server thru console without running Node manager. Is there any work around for that.

Reply
Atul Kumar says September 21, 2011

@ Pawan,
Node manager must be configured and running to control managed servers via weblogic console.

It is not possible to start from console without node manager. What is issue in starting node manager.

Reply
hihihi says November 13, 2011

hi,

I would like to learn weblogic server administration. Can some one tell me where to start and what are the basic requirements to learn that and all.

Reply
Atul Kumar says November 13, 2011

@hihihi,
Check post and all posts listed in “Learn WebLogic with Us” at http://onlineappsdba.com/index.php/2008/07/24/domain-administration-managed-server-cluster-in-oracle-weblogic/

You can also check weblogic/fusion middleware training at focusthread http://focusthread.com/training

Reply
Naveen KNS. says January 22, 2012

Hi Atul,

I have a strange issue. I am installing OFA 11.1.1.5 on a single node. When I perform 13.5 step inhttp://docs.oracle.com/cd/E15586_01/fusionapps.1111/e21032/oim.htm#CFHHCBBH document, weblogic config.xml file was deleted (its showing 0 bytes).

Could you please advise me on this.

Thanks,
Naveen KNS>

Reply
Atul Kumar says January 24, 2012

@ Naveen KNS,
It should not happen, please create domain again (take backup at various logical steps to avoid such issues)

Reply
praveen sharma says February 16, 2012

managed servers in cluster looses connection with admin server and after some time they gets reconnected

Reply
Atul Kumar says February 17, 2012

@ praveen sharma,

Are managed server and admin server on same machine or different machine ?

If they are on different machine , are these machines in same subnet or different subnet ?

Is there any network level packet drop ?

Which type of clustering you are using unicast or multicast ?

Reply
kesh says April 27, 2012

Atul, your posts are very much helpful and one who doesn’t know about the weblogic can be able to perform this.

Great Going. God bless you!!!

Best Wishes
Kesh

Reply
madhu says September 7, 2012

i am working production server my server is going to failed not restartable
weblogic 10.3.5 jdl1.6 , jrockit

Reply
    Atul Kumar says September 7, 2012

    Check log file $DOMAIN_HOME/servers/[serverName]/logs to find root cause of not restartable

    Reply
Soori says April 4, 2013

Hi Atul,
In dev environment we have only 4GB RAM and when i try to start the managed server of a standalone machine, it is failing to restart after the deployment. error is out of memory exception. So do i need to go for additional memory to fix this or is there any other option to fix this?

Reply
Murali says August 5, 2013

Hi Atul,

Whenever I am trying to start WL Managed Server via console I am receiving error message: FAILED_NOT_RESTARTABLE and when I checked log file:

The system cannot find the path specified.
The system cannot find the path specified.
.
.
JAVA Memory arguments:
.
WLS Start Mode=Development
.
CLASSPATH=
.
PATH=E:\Oracle\oam\fmw\WLSERV~1.3\server\native\win\x64;E:\Oracle\oam\fmw\WLSERV~1.3\server\bin;E:\Oracle\java\jre\bin;E:\Oracle\java\bin;E:\Oracle\oam\fmw\WLSERV~1.3\server\native\win\x64\oci920_8;C:\Program Files\HP\NCU;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\idmu\common;C:\Program Files\System Center Operations Manager 2007\;C:\Program Files (x86)\HITACHI\DynamicLinkManager\bin;C:\Program Files (x86)\HITACHI\DynamicLinkManager\lib;c:\Program Files (x86)\HDVM\HBaseAgent\bin;c:\Program Files (x86)\HDVM\HBaseAgent\util\bin;C:\Program Files (x86)\Common Files\Hitachi;E:\Oracle\java\bin;E:\Oracle\oif\fmw\oif\bin;E:\Oracle\oif\fmw\oif\jdk\jre\bin\server;E:\Oracle\oif\fmw\oif\bin;E:\Oracle\oif\fmw\oif\opmn\bin;E:\Oracle\oif\fmw\oif\opmn\lib;E:\Oracle\oif\fmw\oif\perl\bin;
.
***************************************************
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http:\\hostname:port\console *
***************************************************
starting weblogic with Java version:
java version “1.7.0_17”
Java(TM) SE Runtime Environment (build 1.7.0_17-b02)
Java HotSpot(TM) 64-Bit Server VM (build 23.7-b01, mixed mode)
Starting WLS with line:
E:\Oracle\java\bin\java -Dweblogic.Name=oam_server2 -Djava.security.policy=\server\lib\weblogic.policy -Dweblogic.system.BootIdentityFile=E:\Oracle\admin\OAMDomain\mserver\OAMDomain\servers\oam_server2\data\nodemanager\boot.properties -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.security.SSL.ignoreHostnameVerification=false -Dweblogic.ReverseDNSAllowed=false
Usage: java [-options] class [args…]
(to execute a class)
or java [-options] -jar jarfile [args…]
(to execute a jar file)
where options include:
-d32 use a 32-bit data model if available
-d64 use a 64-bit data model if available
-server to select the “server” VM
-hotspot is a synonym for the “server” VM [deprecated]
The default VM is server.

-cp
-classpath
A ; separated list of directories, JAR archives,
and ZIP archives to search for class files.
-D=
set a system property
-verbose:[class|gc|jni]
enable verbose output
-version print product version and exit
-version:
require the specified version to run
-showversion print product version and continue
-jre-restrict-search | -no-jre-restrict-search
include/exclude user private JREs in the version search
-? -help print this help message
-X print help on non-standard options
-ea[:…|:]
-enableassertions[:…|:]
enable assertions with specified granularity
-da[:…|:]
-disableassertions[:…|:]
disable assertions with specified granularity
-esa | -enablesystemassertions
enable system assertions
-dsa | -disablesystemassertions
disable system assertions
-agentlib:[=]
load native agent library , e.g. -agentlib:hprof
see also, -agentlib:jdwp=help and -agentlib:hprof=help
-agentpath:[=]
load native agent library by full pathname
-javaagent:[=]
load Java programming language agent, see java.lang.instrument
-splash:
show splash screen with specified image
See http://www.oracle.com/technetwork/java/javase/documentation/index.html for more details.

Please advise?

Murali

Reply
    Atul Kumar says August 5, 2013

    @ Murali,
    Can you start weblogic server using command prompt ?
    What type of WeBlogic Server is this (Is this part of Fusion Middleware) ?

    Reply
Murali says August 6, 2013

Hi Atul,

No, the managed server does not start with command prompt either, the same error message is received.

And yes, it is part of Fusion Middleware. Please let me know if you need any further details.

rgds,

Murali

Reply
Murali says August 6, 2013

and thank you for look into this

Reply
Atul Kumar says August 6, 2013

@ Murali,
What type of Fusion Middleware installatio is this ?
Which managed server fails to start ?
Did it start-up ever work ?

Reply
Murali says August 6, 2013

Hi Atul,

Thank you for the swift reply.

It is Oracle Fusion Middleware 11g R2. Its the oam_server2 associated with OAM_Cluster assigned to OAM_HOST2 installed on OIF Server.( This is the document I used http://docs.oracle.com/cd/E27559_01/admin.1112/e28212/oam_11g.htm#BHCCCDJJ )

After successfull installation, first time it worked but after that unable to restart via console as well as via command prompt. On the console, the message is Failed_Not_Restartable and via command prompt the same error message as mentioned above.

Please let me know whether this is the information you are looking for?

rgds,

Murali

Reply
Murali says August 6, 2013

Also other oam_server1 in the same cluster installed on OAM Server starts perfectly fine but via command prompt though.

Reply
Atul Kumar says August 6, 2013

@ Murali,

Lets first fix OAM_SERVER2 on host 2 using command line

Did you install WebLOgic, 11gR2 on second host and then pack / unpack from host1 to host 2 ?

Reply
Murali says August 6, 2013

Yes Atul,

WebLogic has been installed on the second host and pack\unpack from host1 to host2 has been done.

Reply
Atul Kumar says August 8, 2013

@ Murali,
It looks some of the files are missing or permissions are not right from host2

___
The system cannot find the path specified.
___

Start OAM2 from command line and paste the error message

Reply
Sandesh Jain says September 16, 2014

Hi Atul,Murali,

I am facing the same issue , Please do help me in resolving this issue.

Thanks,
Sandesh

Reply
Mark says July 17, 2015

Hi. I wonder if you can point into right direction. On our oamdomain.com:8001/console – none of the Environment links are working. Just returns to the home page. Any advice? It is WLS admin console, not oamconsole

Thank you

Reply
Prabhu says June 2, 2016

Hi Atul Kumar
I am very new to weblogic, i have created a new domain in the admin console i can find the domain tree structure where i can have my server instances, but in my case if i click on the env>server> the server link is disabled and it doesn’t allow me to proceed further. Even i have uninstalled welogic and installed again as per wizard but problem is the same. This is the error i got in command prompt,
error 1:
<The included control tree for URI
[/PortalConfig/jms/quota/JMSQuota.book] is invalid.
java.lang.NullPointerException
I really dont have idea about this, please i request you provide me some solution for this
Weblogic version 10.3.6
java version :java version "1.6.0_43"
Java(TM) SE Runtime Environment (build 1.6.0_43-b01)
Java HotSpot(TM) 64-Bit Server VM (build 20.14-b01, mixed mode)
Thanks
Reg
Prabhu

Reply
    Sudhakar says September 7, 2018

    Prabhu, Did you get solution for above issue, we also got similar issue in our env.

    Reply
Emmanuel says July 23, 2016

Hi,

I configured two unix machine: machine1 and machine2

machine1 with AdminServer, cluster1{ms1 and ms2}*
machine 2 with cluster2 {ms3 and ms4}*
*ms means managed server

I have a coherence_cluster with coherece_server1 and coherence_server2
coherence_cluster points to cluster1 and cluster2 of managed servers
coherence_cluster has {cs1 and cs2}**
**cs means coherence server

the machine 1 has IP 192.168.131.131
the machine 2 has IP 192.168.131.132

When I deploy any application I get the error: 192.168.131.131 is not a local address, it happens when I start the cs2, but If i start only cs1, It works fine.

Can you help me?

Reply
Shivali Ahuja says February 20, 2017

This is with regards to an Application Server sitting over WebLogic. On bringing up the Application in WebLogic through Node Manager, it is brought up and running, but opening the Application Console, it returns Error 404 – Not Found. We are running Oracle EDQ on WebLogic. We have got certain Error Codes and Messages below :

1. BEA-149231 : Unable to set the activation state to true for the application “edq”. weblogic.application.ModuleException: java.lang.NullPointerException

2. BEA-000000 : Unexpected state during contextDestroyed: no ConfigManager instance in current ServletContext but one is expected to exist.

Can you please help me the same. I am newbie to weblogic. Any help would be much appreciated,

Thanks,
Shivali

Reply
sravan says March 3, 2017

hi …
in my weblogic homedirectory Start Node Manager ($WL_HOME/server/bin/startNodeManager.sh) is not available .. what i have to do now

Reply
Benny says February 9, 2018

This and your other weblogic blogs helped me alot to diagnose why I couldn’t start my new managed server running on weblogic 10.6.3 under Oracle EBS 12.2.7 environment.

I was trying to create a new managed server to run Oracle REST Data Service under it. But I couldn’t startup the new managed server. Thats when I read in your blog that you cannot start a managed service without a node manager unless I start it from command line using startManagedWebLogic.sh script. Then it worked. Then I discovered that the reason the nodemanager wasnt running was because I had cloned my EBS from another EBS where the port was different (it was 5573 instead of 5556). To resolve that I had to open the nodemanager.properties and change it to the correct port. Basically I had to sync the port#s between the properties file and the Node Manager config in the console. Now I can startup my nodemanager and it works and I can also startup my new managed server from inside the console. Thank you very much! This was great!

Reply
Sunil Puri says November 22, 2018

Hello, I am having an issue when ever I start the Weblogic server from the installed directory, actually it is asking for weblogic user ID and password but not accepting any character as password in the dos prompt, Please help me with this.

Reply
Add Your Reply