Hawai Finance

May 17 2018

WebLogic – Error starting managed server from Console: Node Manager associated with this machine is not reachable – Oracle Trainings for Apps – Fusion DBA, managed email server.#Managed #email #server


Sign Up for Blog Updates

Get my blog updates related to Oracle Tips, How Tos, New Features and Troubleshooting direct to your email Account

Managed email server

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

  • April 10, 2010 /
  • weblogic /
  • By Atul Kumar /

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)

Managed email server

3. Attach Managed Server to Machine : EnvironmentServers – [select managed server] – under General tab Configuration , select machine

4. Add domain loaction in $WL_HOME/common/nodemanager/nodemanager.domains

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

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

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 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

Managed email server

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

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 : Oracle Gold Partner specialising in Design, Implement, and Trainings.

Leave a Comment:


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

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 ;-))

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.

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

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.

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])

Written by admin

Leave a Reply

Your email address will not be published. Required fields are marked *