Node Manager Not Reachable

Hi Everyone,
I'm very new to WebLogic, so I apologize if this is a dumb question.
I'm trying to install WebLogic as server for OBIEE. My environment is pretty simple. I have two Oracle Red Hat Linux 32-bit physical machines, let's call them WLS_SERVER and OBIEE_SERVER. I installed OBIEE on the OBIEE_SERVER and tested it using the out of the box OC4J container and that worked fine.
Then I installed WebLogic 11g on the WLS_SERVER machine and I ran the config.sh script. I used the configuration GUI to register the two physical machines and an additional server object called BIServer. Out of the box, web logic comes with AdminServer server object. I heard it's a bad practice to deploy applications to the AdminServer, hence why I created the BIServer object. I associated BIServer with the OBIEE_SERVER machine.
I went to start the BIServer and I got the following error:
"For server BIServer, the Node Manager associated with machine OBIEE_SERVER is not reachable."
How do I setup a Node Manager on the OBIEE_SERVER? Do I also need to physical put the WebLogic install file on the OBIEE_SERVER box and also run the installer there? Or there a copy paste thing I do? What am I missing here?
I appreciate the help!
-Joe

I'm trying to install WebLogic as server for OBIEEI have not heard about OBIEE, but if your aim is to use weblogic as a server for hosting this then you definitely need to install weblogic on the physical box where OBIEE will be hosted.
I associated BIServer with the OBIEE_SERVER machine.
I went to start the BIServer and I got the following error:
"For server BIServer, the Node Manager associated with machine OBIEE_SERVER is not reachable."Again not sure what is BIServer but I think you are missing a number of steps here. If you are trying to run BIServer
on weblogic you definitely need to install WLS on this physical machine [OBIEE_SERVER]. You will then need to configure a node manager on OBIEE_SERVER machine to enable it to start remotely from the admin machine.
Link for Node Manager. Since you are in Linux you can try setting up script based node manager.
http://download.oracle.com/docs/cd/E13222_01/wls/docs92/server_start/nodemgr.html#wp1099239

Similar Messages

UCCX error-remote UCCX node is not reachable

Hi,
I am working in UCCX 9.0,trying to upload new script developed thorugh UCCX script editor ,whenever I click upload script through "script management" tab,giving error as "remote UCCX node is not reachable,it is not recommended to create,modify or delete the files in this state,as it will be inconsistent between nodes",let me know any idea about this error.
Thanks,
Baskar.

Hi,
RTMT is configured and found the following error.
2013-11-11 04:11:39 :INFO: Received request to start the service Cisco Unified CCX Engine
2013-11-11 04:11:39 :INFO: Checking if PID File exists.
2013-11-11 04:11:39 :INFO: process Cisco Unified CCX Engine is not running
2013-11-11 04:11:39 :INFO: Starting process Cisco Unified CCX Engine, Exe=/opt/cisco/uccx/bin/UCCX_Engine, Conf=/opt/cisco/uccx/conf/UCCX_EngineCfg.xml
2013-11-11 04:11:39 :INFO: Cisco Unified CCX Engine initialization complete.... PID 18469 updated in pid file /opt/cisco/uccx/conf/UCCX_Engine.pid
2014-06-05 05:45:46 :INFO: Received request to start the service Cisco Unified CCX Engine
2014-06-05 05:45:46 :INFO: Checking if PID File exists.
2014-06-05 05:45:47 :INFO: PID File exists, pid=18469
2014-06-05 05:45:47 :INFO: process Cisco Unified CCX Engine with PID 18469 might have crashed, PID file still exists
2014-06-05 05:45:47 :INFO: Stale PID entry 18469, removing PID file
2014-06-05 05:45:49 :INFO: Starting process Cisco Unified CCX Engine, Exe=/opt/cisco/uccx/bin/UCCX_Engine, Conf=/opt/cisco/uccx/conf/UCCX_EngineCfg.xml
2014-06-05 05:45:49 :INFO: Cisco Unified CCX Engine initialization complete.... PID 4201 updated in pid file /opt/cisco/uccx/conf/UCCX_Engine.pid
2014-06-05 07:04:03 :INFO: Received request to stop the service Cisco Unified CCX Engine
2014-06-05 07:04:03 :INFO: PID File exists, pid=4201
2014-06-05 07:04:03 :INFO: Stopping the Process Cisco Unified CCX Engine, pid=4201
2014-06-05 07:04:03 :INFO: Stopped the process Cisco Unified CCX Engine
2014-06-05 07:28:29 :INFO: Received request to start the service Cisco Unified CCX Engine
2014-06-05 07:28:29 :INFO: Checking if PID File exists.
2014-06-05 07:28:29 :INFO: process Cisco Unified CCX Engine is not running

Ise node is not reachable after upgrading 1.2

Hi, I was using beta version of ISE with 1.2.834 code. and now the official release came out so I upgraded it.
after that, the ISE is not communicating with AD, and when I go to download logs, It says node is not reachable even though it is STANDALONE mode.
does anyone know how to work around this ?
should I just delete everything and go from scratch ?

The ISE is not communicating to the AD, So, you have to rejoin the domain. For this purpose please follow the following actions:
Go to Administration > Identity Management > External Identity Stores and select Active Directory from the left-hand pane.
Click Join at the bottom of the configuration page:
Also please check the LDAP port

Node Manager not starting UCM Server automatically

Hi All,
I have configured Node Manager to start and stop UCM 11g server.
But whenever, I am restarting the host OS - Windows server 2003 64 bit, it does not start the UCM managed server, automatically.
I am running two managed servers on the same host OS, the first UCM manages server, starts automatically on every restart.
The second managed UCM server, does not start. I need to then manually start the managed server. There are no errors logged, and the manual start of the managed server happens without any issues.
As a workaround, I tried starting the managed server from Windows scheduler, but it does not start the server as well. I wrote a script like -
Myscript.cmd
call E:\..\user_projects\domains\prod_domain\bin\setDomainEnv.cmd
java weblogic.WLST c:\start....\ServerStart.py
scheduled the script (myscript.cmd) to run from the Windows Scheduler.
Any pointers would be very helpful. Are there any known issues, if there are two managed servers, and one starts automatically, which affects the starting of the second managed server?
I see the following error in the log file -
<14/10/2011 6:35:22 PM EST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.5.0 Fri Apr 1 20:20:06 PDT 2011 1398638 >
<14/10/2011 6:35:33 PM EST> <Info> <Management> <BEA-141223> <The server name PRD_UCM_Server1 specified with -Dweblogic.Name does not exist. The configuration includes the following servers {PRDAdminServer,PRD_UCM_server1,PRD_IBR_server1}.>
<14/10/2011 6:35:33 PM EST> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:
There are 1 nested errors:
weblogic.management.ManagementException: [Management:141223]The server name PRD_UCM_Server1 specified with -Dweblogic.Name does not exist. The configuration includes the following servers {PRDAdminServer,PRD_UCM_server1,PRD_IBR_server1}.
at weblogic.management.provider.internal.RuntimeAccessImpl.<init>(RuntimeAccessImpl.java:149)
at weblogic.management.provider.internal.RuntimeAccessService.start(RuntimeAccessService.java:41)
at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesManager.java:461)
at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServicesManager.java:166)
at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:881)
at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:568)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:469)
at weblogic.Server.main(Server.java:71)
Regards
Avi

Hi Avi,
Give a cross check to your ServerStart.py
As the error states The server name PRD_UCM_Server1 specified with -Dweblogic.Name does not exist
In your ServerStart.py you might have specified as follows
sh start MAnagedWeblogic.sh server=PRD_UCM_Server1
While these are the list of Server you have in your weblogic
PRDAdminServer,
PRD_UCM_server1,(You have Specified in your command PRD_UCM_Server1
PRD_IBR_server1
The Command should be as follows
sh start ManagedWeblogic.sh server=PRD_UCM_server1
This should help
Regards
Fabian

Node Manager not shutting down the Managed Servers

I have WebLogic Server 8.1 SP4 installed on around 9 separate boxes - 3 servers form one WLS domain of one admin + two managed servers. The managed servers are started using Node Manager from the admin console.
On one domain start/shutdown using Admin Console works just fine however the other two domains the managed servers startup fine but shutdown fails - or takes over 15 minutes. I see the following error in the Node Manager logs
NMMessage: Command read failed 'Connection reset' on socket/ <ip_address>
Any ideas on what I can do to fix this ? The servers which will not shutdown have EJB's installed on them. Dont think this could be related as shutting down the application results in the same problem as listed above.
Thanks,
Kevin.

The name of remote machine configured on admin server it must to be resolved on same machine in /etc/hosts:
Example:
On the admin server is configured the unix machine N1234
On the machine N1234 in the file nodemanager.hosts it must be present the IP of admin server
On the admin server in /etc/hosts it must be present
IP_N1234 N1234

Node Manager Not Starting Managed Servers

I have nodemanager configured to restart managed servers automatically upon reboot but when I physically restart the 2nd node none of the managed servers start and there are no errors. Steps completed and verified....
1) Nodemanager.properties has domain path and 'crashrecoveryenabled' set to 'true'
2) managed servers have autorestart set to 'true' and -Xnohup parameter added to startup arguments.
3) Boot.properties files ave the username and password (encrypted) to start up the server.
Here is the nodemanager.log file and you can clearly see it is grabbing the startup files. It almost looks like the server files are trying to get loaded before the nodemanager port is available but I see no errors. Any ideas?
<Dec 28, 2009 9:16:59 AM> <Info> <QA10311> <WebProxyServer2> <Working directory is "C:\bea\user_projects\domains\QA10311">
<Dec 28, 2009 9:16:59 AM> <Info> <QA10311> <WebProxyServer2> <Server output log file is "C:\bea\user_projects\domains\QA10311\servers\WebProxyServer2\logs\WebProxyServer2.out">
<Dec 28, 2009 9:47:09 AM> <INFO> <Loading domains file: C:\bea\WLSERV~1.3\common\nodemanager\nodemanager.domains>
<Dec 28, 2009 9:47:16 AM> <INFO> <Loading identity key store: FileName=C:/bea/WLSERV~1.3/server\lib\DemoIdentity.jks, Type=jks, PassPhraseUsed=true>
<Dec 28, 2009 9:47:18 AM> <INFO> <Loaded node manager configuration properties from 'C:\bea\WLSERV~1.3\common\nodemanager\nodemanager.properties'>
<Dec 28, 2009 9:47:21 AM> <Info> <QA10311> <ACR2> <Startup configuration properties loaded from "C:\bea\user_projects\domains\QA10311\servers\ACR2\data\nodemanager\startup.properties">
<Dec 28, 2009 9:47:21 AM> <Info> <QA10311> <CommandNet2> <Startup configuration properties loaded from "C:\bea\user_projects\domains\QA10311\servers\CommandNet2\data\nodemanager\startup.properties">
<Dec 28, 2009 9:47:21 AM> <Info> <QA10311> <FPCE2> <Startup configuration properties loaded from "C:\bea\user_projects\domains\QA10311\servers\FPCE2\data\nodemanager\startup.properties">
<Dec 28, 2009 9:47:21 AM> <Info> <QA10311> <MQServer2> <Startup configuration properties loaded from "C:\bea\user_projects\domains\QA10311\servers\MQServer2\data\nodemanager\startup.properties">
<Dec 28, 2009 9:47:22 AM> <Info> <QA10311> <PortalServer2> <Startup configuration properties loaded from "C:\bea\user_projects\domains\QA10311\servers\PortalServer2\data\nodemanager\startup.properties">
<Dec 28, 2009 9:47:22 AM> <Info> <QA10311> <ShoppingCart2> <Startup configuration properties loaded from "C:\bea\user_projects\domains\QA10311\servers\ShoppingCart2\data\nodemanager\startup.properties">
<Dec 28, 2009 9:47:22 AM> <Info> <QA10311> <webapp2> <Startup configuration properties loaded from "C:\bea\user_projects\domains\QA10311\servers\webapp2\data\nodemanager\startup.properties">
<Dec 28, 2009 9:47:22 AM> <Info> <QA10311> <WebProxyServer2> <Startup configuration properties loaded from "C:\bea\user_projects\domains\QA10311\servers\WebProxyServer2\data\nodemanager\startup.properties">
<Dec 28, 2009 9:47:22 AM> <Info> <QA10311> <WUA2> <Startup configuration properties loaded from "C:\bea\user_projects\domains\QA10311\servers\WUA2\data\nodemanager\startup.properties">
<Dec 28, 2009 9:47:27 AM> <INFO> <Secure socket listener started on port 5556, host qaportal2.FCQA.COM>

Hi,
Entries in nodemanager.properties looks fine, but how are you testing this functionality?
If you will stop servers monitored by nodemanager, stop nodemanager and then reboot physical server, on startup if nodemanager is configured as daemon it will start nm process but will do nothing to managed server process.
To test "CrashRecoveryEnabled=true" kill the managed server pid and then stop/kill nodemanager process. Then perform physical server reboot, now if nm is configured as daemon process server reboot will start nodemanager. Once NM is up first thing it check is the server it was monitoring earlier and if under directory $WL_HOME/servers/<server>/data/nodemanager it finds "pid" and "lck" file it checks if that pid exists and if not then go for a restart of weblogic server instance.
This has worked for me...!
Thanks,
Ranjan
http://www.middlewaresupport.wordpress.com

Node manager not starting

I have just installed a second CRS 5.0(2) server which I intend to add to the cluster, but I'm having a problem in that the Node Manager Service hangs on startup. The error I get is:
Event ID:7022
The CRS Node Manager Service Hung on starting.
I can see from the Windows services that the service remains in a 'starting state'.
I wanted to attach the MIVR logs to this post but I'm finding that there is no MIVR folder in c:/Program Files/wfavvid/log. Has the install completed successfully? I had no errors when installing the package.
I've checked the binding order of the NIC cards and they are correct. I have also run the 'postinstall.exe' but still the same problem.
On another note, how can you tell if the license provided (uploaded by someone else) includes HA software?
Thanks

Try checking out the MCVD logs and the application and system logs for any error with NIC or network connectivity.
As for the second question the key you are looking for in the Lic is the entry.
INCREMENT CRS_EXP_PRE_WARM_STBY cisco 5.0
In case its already uploaded in CRS the Control Center >Display Licenses will show HA enabled.

Node manager not starting servers as a OS service.

Node manager is starting upon simulating OS crash but it is not bringing up the managed servers running on that machine.
The following is the nodemanager.properties file -
[orawl@qa-wl2 nodemanager]$ more nodemanager.properties
#Mon Apr 11 14:55:43 EDT 2011
#Mon Apr 11 11:57:43 EDT 2011
DomainsFile=/home/orawl/oracle/middleware/wlserver_10.3/common/nodemanager/nodemanager.domains
LogLimit=0
PropertiesVersion=10.3
DomainsDirRemoteSharingEnabled=false
javaHome=/usr/lib/jdk1.6.0_24
AuthenticationEnabled=true
NodeManagerHome=/home/orawl/oracle/middleware/wlserver_10.3/common/nodemanager
JavaHome=/usr/lib/jdk1.6.0_24/jre
LogLevel=INFO
DomainsFileEnabled=true
StartScriptName=startWebLogic.sh
ListenAddress=
NativeVersionEnabled=true
ListenPort=5556
LogToStderr=true
SecureListener=true
LogCount=1
DomainRegistrationEnabled=false
StopScriptEnabled=false
QuitEnabled=false
LogAppend=true
StateCheckInterval=500
CrashRecoveryEnabled=true
StartScriptEnabled=true
LogFile=/home/orawl/oracle/middleware/wlserver_10.3/common/nodemanager/nodemanager.log
LogFormatter=weblogic.nodemanager.server.LogFormatter
ListenBacklog=50
#NodeManager SSL Properties
KeyStores=CustomIdentityAndCustomTrust
CustomIdentityKeyStoreType=JKS
CustomIdentityAlias=xxxxxxxxxxxx
CustomIdentityKeyStoreFileName=/home/orawl/oracle/middleware/keystores/xxxxxxxxxxxx.jks
CustomIdentityKeyStorePassPhrase={3DES}XXXXXXXXXXXXXXXXXXXXXXX
CustomIdentityPrivateKeyPassPhrase={3DES}XXXXXXXXXXXXXXXXXXXXXXX
CustomTrustKeyStoreType=JKS
CustomTrustKeyStoreFileName=/home/orawl/oracle/middleware/keystores/trustcacerts.jks
CustomTrustKeyPassPhrase=xxxxxxxxxxx
Please advice.

Hi All,
Add to my initial post , the error which is getting logged is -
<14/10/2011 6:35:22 PM EST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.5.0 Fri Apr 1 20:20:06 PDT 2011 1398638 >
<14/10/2011 6:35:33 PM EST> <Info> <Management> <BEA-141223> <The server name PRD_UCM_Server1 specified with -Dweblogic.Name does not exist. The configuration includes the following servers {PRDAdminServer,PRD_UCM_server1,PRD_IBR_server1}.>
<14/10/2011 6:35:33 PM EST> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:
There are 1 nested errors:
weblogic.management.ManagementException: [Management:141223]The server name PRD_UCM_Server1 specified with -Dweblogic.Name does not exist. The configuration includes the following servers {PRDAdminServer,PRD_UCM_server1,PRD_IBR_server1}.
     at weblogic.management.provider.internal.RuntimeAccessImpl.<init>(RuntimeAccessImpl.java:149)
     at weblogic.management.provider.internal.RuntimeAccessService.start(RuntimeAccessService.java:41)
     at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesManager.java:461)
     at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServicesManager.java:166)
     at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:881)
     at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:568)
     at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:469)
     at weblogic.Server.main(Server.java:71)
Regards,
Avi

Node Manager not starting UCM Server

Hi All,
I have configured Node Manager to start and stop UCM 11g server.
But whenever, I am restarting the host OS - Windows server 2003 64 bit, it does not start the UCM managed server, automatically.
I am running two managed servers on the same host OS, the first UCM manages server, starts automatically on every restart.
The second managed UCM server, does not start. I need to then manually start the managed server. There are no errors logged, and the manual start of the managed server happens without any issues.
As a workaround, I tried starting the managed server from Windows scheduler, but it does not start the server as well. I wrote a script like -
Myscript.cmd
call E:\..\user_projects\domains\prod_domain\bin\setDomainEnv.cmd
java weblogic.WLST c:\start....\ServerStart.py
scheduled the script (myscript.cmd) to run from the Windows Scheduler.
Any pointers would be very helpful. Are there any known issues, if there are two managed servers, and one starts automatically, which affects the starting of the second managed server?
Regards
Avi

Hi All,
Add to my initial post , the error which is getting logged is -
<14/10/2011 6:35:22 PM EST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.5.0 Fri Apr 1 20:20:06 PDT 2011 1398638 >
<14/10/2011 6:35:33 PM EST> <Info> <Management> <BEA-141223> <The server name PRD_UCM_Server1 specified with -Dweblogic.Name does not exist. The configuration includes the following servers {PRDAdminServer,PRD_UCM_server1,PRD_IBR_server1}.>
<14/10/2011 6:35:33 PM EST> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:
There are 1 nested errors:
weblogic.management.ManagementException: [Management:141223]The server name PRD_UCM_Server1 specified with -Dweblogic.Name does not exist. The configuration includes the following servers {PRDAdminServer,PRD_UCM_server1,PRD_IBR_server1}.
     at weblogic.management.provider.internal.RuntimeAccessImpl.<init>(RuntimeAccessImpl.java:149)
     at weblogic.management.provider.internal.RuntimeAccessService.start(RuntimeAccessService.java:41)
     at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesManager.java:461)
     at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServicesManager.java:166)
     at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:881)
     at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:568)
     at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:469)
     at weblogic.Server.main(Server.java:71)
Regards,
Avi

Node Manager not starting servicess after server reboot

We have WLS 10.1.3.5 with IDM/OAM(two domains in same server as its TEST environment) on Oracle Linux 5(64bit),when ever server reboots node manger is not starting managed servers.
I have enabled CrashRecoveryEnabled=true
Here is nodemanager.properties.
[oracle@oam nodemanager]$ cat nodemanager.properties
#Changed NM Listen Port
#Tue Mar 05 03:12:20 IST 2013
DomainsFile=/u01/Oracle/Middleware/wlserver_10.3/common/nodemanager/nodemanager.domains
LogLimit=0
DomainsDirRemoteSharingEnabled=false
PropertiesVersion=10.3
AuthenticationEnabled=true
NodeManagerHome=/u01/Oracle/Middleware/wlserver_10.3/common/nodemanager
javaHome=/u01/Oracle/Middleware/jdk160_24
JavaHome=/u01/Oracle/Middleware/jdk160_24/jre
LogLevel=INFO
DomainsFileEnabled=true
StartScriptName=startWebLogic.sh
ListenAddress=
NativeVersionEnabled=true
ListenPort=5556
LogToStderr=true
SecureListener=false
LogCount=1
StopScriptEnabled=false
DomainRegistrationEnabled=false
QuitEnabled=false
LogAppend=true
StateCheckInterval=500
CrashRecoveryEnabled=true
StartScriptEnabled=true
LogFile=/u01/Oracle/Middleware/wlserver_10.3/common/nodemanager/nodemanager.log
LogFormatter=weblogic.nodemanager.server.LogFormatter
ListenBacklog=50
here is my domain information in server.
=========================
[oracle@oam nodemanager]$ cat nodemanager.domains
#Domains and directories created by Configuration Wizard
#Tue Mar 05 05:24:37 IST 2013
OAMDomain=/u01/Oracle/Middleware/user_projects/domains/OAMDomain
IDMDomain=/u01/Oracle/Middleware/user_projects/domains/IDMDomain

Hi,
Entries in nodemanager.properties looks fine, but how are you testing this functionality?
If you will stop servers monitored by nodemanager, stop nodemanager and then reboot physical server, on startup if nodemanager is configured as daemon it will start nm process but will do nothing to managed server process.
To test "CrashRecoveryEnabled=true" kill the managed server pid and then stop/kill nodemanager process. Then perform physical server reboot, now if nm is configured as daemon process server reboot will start nodemanager. Once NM is up first thing it check is the server it was monitoring earlier and if under directory $WL_HOME/servers/<server>/data/nodemanager it finds "pid" and "lck" file it checks if that pid exists and if not then go for a restart of weblogic server instance.
This has worked for me...!
Thanks,
Ranjan
http://www.middlewaresupport.wordpress.com

NAC Manager Not Reachable

Hi Everyone,
I have a NAC setup with one CAM and 3 CAS.
We had a power failure last weekend, and since then I can't access the CAM. Not even via console cable. But I can console to the CAS. The CAM is ON as I can see the LEDs (all green).
I would like to restart the CAM and check. But I don't know whether it will have any affect on the network, like does my users still can have access to the network even if I switch off the CAM, as the CAS is still working.
Thank you in advance.

Hi,
I will appreciate any suggestion you guys have.

11g node manager reachable but server does not start from admin console

I have a issue with node manager is reachable from admin console and from command prompt it is not connected and could not able to start the managed server.
If i change /config/nodemanager/nm_password.properties plain text and restart it is not reachable in admin console abut can connect from command prompt. I could not able to start the even with this scenario.
i see below error when try to check machine monitor tab.
<Error> <NodeManager> <BEA-300033> <Could not execute command "getVersion" on the node manager. Reason: "Access to domain 'dom_11gint' for user 'Ckr10ycOJN' denied".>
Ckr10ycOJN username in config.xml
node manager and managed servers are not root user process.
Please help me if have any suggestions.

Pls. make sure the following points in your environment.
1) Check '*nodemanager.domains*' file in <<WL_HOME>>\commo\nodemanager directory
     a) This file should have the entry for your domain 'dom_11gint'.
     b) Ensure the path referred in the nodemanager.domains file is correct one.
2) Ensure the following remote server startup parameters are passed properly.
     a) In the Admin Console, Navigate Servers --> <<SERVER_NAME>> -->Configuration --> Server Start
     b) Pass the required Class Path, Arguments, User Name, Password(User name and Password to boot the managed servers)

Steps to setup and configure Node Manager on local and remote machine

Hello,
I am using WLS 10.3 on Windows.
I have two machines, One cluster and two managed servers (one on each machine) created under a domain. I have used configuration wizard to create the domain.
I have gone through documents on Node Manager and found what to configure. But I have not found when to configure. In other words I want to know what is the sequence of steps if I have to set Node Manager on my local machine (in which domain exists) and on remote machine.
Please let me know the sequence of steps I need to follow to set and configure the Node Manager on local and remote machine. I want to use Java Node Manager (not the Script node manager).
Thanks,
Sanjay

Hello,
Ok, let me tell you what I have done till now.
1) Installed WebLogic 10.3 on machine A (local machine, on which I have created domain and my Admin Server is running. Also Managed Server 1 is created on this machine).
2) Installed WebLogic 10.3 on machine B (remote machine, on which Managed Server 2 will be created).
3) On machine A I used the configuration wizard and create a domain. While creating the domain I did the following:
i) Created two managed servers.
ii) Created a cluster
iii) Assigned Servers to cluster.
iv) Created two machines.
v) Assigned servers to machines (Admin Server and MS_1 to machine A and MS_2 to machine B).
4) Sarted Admin Server.
5) On the Admin Console I made some configurations for the Node Manager on Machines -> Machine A -> Node Manager. Assigned the values:
i) Type (SSL)
ii) Listen Address (IP_Address of machine A)
iii) Listen Port (5556)
6) Similarly did for Machine B.
So till now phsically the managed server (MS_2) directory and configuration is not there on Machine B (its only configured on machine A because I created the domain on Machine A).
Now I want install/configure/setup NM on both the machines. Start my both the managed servers using Admin Console (which will use the node managers).
What are the sequence of steps I need to follow my task?
Any help and suggestions are welcome with warm regards.
Thanks,
Sanjay

For server the Node Manager associated with machine is not reachable

Hello all,
I am getting this error, when i start my Managed Server which is in shutdown state
For server SAA-Dev-1, the Node Manager associated with machine vm-bea-dev 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. No action will be performed.
The configuration details are
i am using weblogic 9.2 MP3 version in windows 2k3 server.
It has a machine vm-bea-dev, a cluster cluster-saa-dev, to which both the managed servers saa-dev-1 and saa-dev-2 are assigned. There are 3 applications deployed onto managed Server 1 and 1 for managed Server 2.
Managed Server 1 is in shutdown state, and when i start the server, it gives the error specified below
For server SAA-Dev-1, the Node Manager associated with machine vm-bea-dev 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. No action will be performed.
The same for Managed Server 2 too, and this server is in Admin State, i dont know how it went into that state.
Can somebody please help me reslove it.
Thanks in advance

Actually the cert is coming from your Dev machine but it is sending the Prod cert.
What cert is used by your admin server ? It should match the host name.
So your Dev machine is apparently using a copy of the prod cert / keystore rather than using its own DEV cert. It's not clear from your post whether this is the nodemanager using the wrong cert, or the managed server. So both should be checked.
The managed servers need to be using a cert that matches their host name. If you have a managed server on VM-BEA-DEV, then the cert needs to be CN=VM-BEA-DEV. You can also use a load-balancer CN name in the cert if you have the cluster's HTTP values set to match.
In your nodemanager.properties, are you explicitly accessing keystores, such as with:
KeyStores=CustomIdentityAndJavaStandardTrust
CustomIdentityAlias=some_alias
CustomIdentityKeyStoreFileName=some_path_to_keystore
CustomIdentityKeyStorePassPhrase={3DES}...
CustomIdentityKeyStoreType=jks
CustomIdentityPrivateKeyPassPhrase={3DES}
In my multi-machine clusters, I have multiple certificates such as:
admin machine1:
has a cert for use by the admin server and NM that matches the host name ( with node manager.properties entries such as the above )
has a 2nd cert that matches the load-balancer name for the cluster - used by the managed servers
all other machines:
has a cert for use by NM that matches the host name ( with node manager.properties entries such as the above )
has a 2nd cert that matches the load-balancer name for the cluster - used by the managed servers

I can not start a remote server via Node Manager

There is a workaround to this problem. The issue seems to be
that when the node manager tries to start the managed server
it can not find java.exe in the system path. So please go to
Control Panel->System->...->Environment, and modify your PATH
system environment variable to include the java bin directory
in it.
Then try using the node manager again to start the managed
servers and you should have no problems.
We are aware of the issue and working on having a fix for it.
Savvas
"Rakesh Chauhan" <[email protected]> wrote:
>
Hey Guys!
I am using WLS6.1 on WIN2000 boxes. And I am getting the same error on
the Admin
console when I try to start any of the two
managed servers.
<Sep 25,2001 1:39:12 PM EDT> <Info> <[email protected]:7002><WindowsProcessControl:
online successfully invoked on server 'server90', pid: 0> The interesting thing is that when I start managed server of its own,
it is started
successfully and you can Stop the managed
server from the Admin Console.
Really frusted, I hope I have configured everything correctly. Can somebody
help
me out ?
Thanks Rakesh
"Martin Matthews" <[email protected]> wrote:
This message is simply a message from the Admin Server saying that it
has asked
NodeManager on the remote machine to start a certain server.
To see the logs for server startup then you can find these either on
the Admin
machine at WL_HOME/config/NodeManagerClientLogs/<ManagedServerName>/*.log
or on the remote machine at
WL_HOME/config/NodeManagerLogs/<ManagedServerName>/*.log
Cheers
Martin
"Paul Nixon" <[email protected]> wrote:
I also would like to know the answer to the question below from Vincent.
I am getting
this message in the Admin console from either of my two managed servers
whenever
the console has successfully contacted the Node Manager in managed
server
host.
The Node Manager logs themselves also report "online successful". What
doesn't
seem to happen is WebLogic startup and I haven't found any error log
that explains
why.
I have set the Remote Startup parameters correctly [I think] for both
managed
servers so cannot see what further is required.
Any input appreciated.
Paul.
"Vincent Ducret" <[email protected]> wrote:
Hi everybody,
When I try to start a remote WLS 6.1 server from my computer, I receive
the message
below in my WLS administration console. The Node manager is runningon
the remote
machine and correctly configured, I hope!
What does this message mean ???
Thanks for your help
Vincent
<21 aoÃ»t 01 10:19:17 CEST> <Info> <[email protected]:5555>
<WindowsProcessControl:
online successfully invoked on server 'testserver', pid: 0>

Node Manager Not Reachable

Similar Messages

Maybe you are looking for