Starting a node manager with rsh

Environment : Forte 2F2, RS6000/AIX 4.1.5
I'm trying to use rsh to start a node manager on a remote system. The
problem that I'm experiencing is that the node manager starts but the
rsh doesn't return. I have to Ctrl-C to end the rsh. I've tried :
rsh remote start_nodemgr
rsh remote "start_nodemgr &"
rsh remote "start_nodemgr < /dev/null"
rsh -n remote start_nodemgr
rsh "nohup start_nodemgr &"
and others. If I rlogin to the remote system and start the node mgr the
shell tells me that I have running jobs when I try to exit even though
the jobs command doesn't show anything running. I am able to exit on
the second try.
What do I need to do to be able to remotely start the node manager
without logging in and logging out.
Thanks in advance
Chukk Haselhorst

I have resolved the issue buy setting NativeVersionEnabled=falase in nodemanager.properties

Similar Messages

Re: Starting a node manager with rsh

FYI,
rsh remote "start_nodemgr > /dev/null" did the trick
Even though the start_nodemgr output came back to my remote window it
seemed to tie up the remote shell.
Thanks for the help
Orsini, Francois wrote:
Hi,
Haven't you tried:
rsh remote "nohup start_nodemgr > /dev/null &"
or
rsh remote "start_nodemgr > /dev/null &"
instead of < /dev/null ....
--francois
From: Chukk Haselhorst
Sent: Thursday, April 03, 1997 1:03 PM
To: forte-users
Subject: Starting a node manager with rsh
Environment : Forte 2F2, RS6000/AIX 4.1.5
I'm trying to use rsh to start a node manager on a remote system. >>The problem that I'm experiencing is that the node manager starts but >>the rsh doesn't return. I have to Ctrl-C to end the rsh. I've tried :
rsh remote start_nodemgr
rsh remote "start_nodemgr &"
rsh remote "start_nodemgr < /dev/null"
rsh -n remote start_nodemgr
rsh "nohup start_nodemgr &"
and others. If I rlogin to the remote system and start the node mgr >> the shell tells me that I have running jobs when I try to exit even >> though the jobs command doesn't show anything running. I am able to >> exit on the second try.
What do I need to do to be able to remotely start the node manager
without logging in and logging out.
Thanks in advance
Chukk Haselhorst

I have resolved the issue buy setting NativeVersionEnabled=falase in nodemanager.properties

Can i use single node manager with two weblogic domain?

I am very new to weblogic and node manager.
i had created two domains in weblogic. (single node manger).
Can i connect both domains with same nodemanger?
How to do this?

The node manager uses a nodemanager.domains file to determine which domains it manages, for example,
domain_name=/path_to_domain/domain_name
other_domain_name=/path_to_other_domain/other_domain_name
This file can be found in the NODEMANAGER_HOME, that you specified when starting the node manager (startNodeManager - NODEMGR_HOME="${WL_HOME}/../oracle_common/common/nodemanager")
When you are running the domain on multiple machines you have to enroll the node manager into the domain (http://docs.oracle.com/cd/E23943_01/web.1111/e13813/reference.htm#i1065827)
A scripted example can be found here: Middleware Snippets: Automate WebLogic Installation and Configuration. The Node Manager administration guide can be found here: Oracle&reg; Fusion Middleware Node Manager Administrator's Guide for Oracle WebLogic Server 11g Release 1 (10.3.6) -….

Start the node manager and rerun the command

Seeing the following in weblogic server log. When will I get this error? And how to retun node manager ?
The node manager at host ....and port 5555 seems to be down. Start the node manager and rerun the command.

You will get this message when the machine's NodeManager was not started.
Take a look at the following links to see how to install and start the Node Manager:
http://e-docs.bea.com/wls/docs81/adminguide/nodemgr.html#1150128
http://e-docs.bea.com/wls/docs81/adminguide/confignodemgr.html#1142955

Server state failed when starting through node manager

Hi,
I'm getting the below error while starting the managed server through node manager
<Sep 14, 2010 3:49:34 PM> <Warning> <Exception while starting server 'ms01': java.io.IOException: Server failed to start up. See server
output log for more details.>
java.io.IOException: Server failed to start up. See server output log for more details.
at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:303)
at weblogic.nodemanager.server.Handler.handleStart(Handler.java:542)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:119)
at weblogic.nodemanager.server.Handler.run(Handler.java:66)
at java.lang.Thread.run(Thread.java:619)
I have checked the server logs and it shows the below error code
./admin-stdout.log:<Sep 15, 2010 4:15:56 PM PDT> <Error> <NodeManager> <BEA-300048> <Unable to start the server ms01 : Exception while starting server 'ms01': java.io.IOException: Server failed to start up. See server output log for more details.>
I have also checked WebLogic documentation for BEA-300048. It says "Cause: The most likely cause is a configuration error in the Shell/SSH/RSH NodeManager configuration".
but I'm using Java based node manager
All this is coming up when I enable StartScriptEnabled to true in nodemanager.properties.
What could be reason for failure?

Hi.
If you are not using the latest service pack (sp2) please do so. If you are and are still seeing this
problem please open a case with support.
Thanks
Michael
Tim Dawson wrote:
I get this message whenever I try to use the console to start a managed server
on a remote system.
<Jan 12, 2002 8:18:26 AM PST> <Emergency> <WebLogicServer> <Unable to create a
server socket for: weblogic2.dev.wamnet.com/172.17.27.84, port: 7001. java.net.BindException:
Cannot assign requested address: JVM_Bind Perhaps the address weblogic2.dev.wamnet.com/172.17.27.84
is incorrect or another process is using port 7001.>
I've checked and checked and the only thing running on that box is the node manager!
The console will start a managed server on the local system (i.e. the system
that the admin server is running on) without any complaints.
Any ideas? Thanks,
Tim--
Michael Young
Developer Relations Engineer
BEA Support

Automatically starting Oracle Enterprise Manager with chkconfig

Folks,
While Oracle Linux 6 is out (6.2 actually), Oracle has yet to get everything 'working out of the box' with 6.2. Right now (June 2012) you've got to download patches from Oracle, the new way to start services in Linux 6, upstart, doesn't work with all Oracle features yet, etc. Update: You can still use chkconfig with OL6.
Because of the above, I've been using Oracle Linux 5.8. Linux 5 uses something called chkconfig to register services. You first need to put a script in the right directory: /etc/rc.d/init.d. Linux looks in this directory for scripts and runs those scripts with either a start or stop after them depending on if the system is coming up or going down. Technically this happens every time you change your runlevel (google Unix runlevels for more info), not just when the system goes up or down.
Here's a script that you can put in /etc/rc.d/init.d. I named mine oracleEM:
[root@localhost ~]# cd /etc/rc.d/init.d
[root@localhost init.d]# vi oracleEM
Enter i to enter insert mode and then enter the below (or just copy and paste it)
*#!/bin/sh*
*#chkconfig: 2345 80 05*
*#description: Oracle Enterprise Manager*
ORA_HOME=/u01/app/oracle/product/11.2.0/dbhome_1
ORA_OWNER=oracle
ORA_SID=orcl
*# We're checking to see if ps returns 1 or 2 results for pmon_orcl*
*# If there are two, Oracle is running, one we are just seeing our grep*
ORACLE_STATUS=$(ps -eaf | grep pmon_$ORA_SID | wc -l)
*if [ ! -f $ORA_HOME/bin/emctl ]*
then
echo "Enterprise Manager startup: cannot start"
exit
fi
case "$1" in
*"start")*
*if [ $ORACLE_STATUS -lt 2 ]*
then
echo "Waiting for Oracle instance $ORA_SID to start before starting Enterprise Manager"
fi
*while [ $ORACLE_STATUS -lt 2 ];do*
echo "Waiting...."
sleep 5
ORACLE_STATUS=$(ps -eaf | grep pmon_$ORA_SID | wc -l)
done
su - $ORA_OWNER -c "$ORA_HOME/bin/emctl start dbconsole"
*"stop")*
su - $ORA_OWNER -c "$ORA_HOME/bin/emctl stop dbconsole"
esac
Press the Esc key to leave insert mode, then type *:wq* to write the file and quit.
We'll need to make the script executable, so we need to run the following command:
[root@localhost init.d]# *chmod +x oracleEM*
Finally we need to register the oracleEM script with Linux using the chkconfig command:
[root@localhost init.d]# *chkconfig --add oracleEM*
Now Enterprise Manager will start up automatically when you start your system, but only after Oracle has started.
Rich
Edited by: RichS on Jun 9, 2012 1:00 AM

The script you are using will not work for RHEL or Oracle Linux since it is incorrect and missing important coding.
You can probably fix the script by removing the dash (-) from the su command and adding the lockfile that is required for RHEL to process the stop routine at system shutdown. The dash will reset the shell environment and the startup won't work. You should also start it in the background in order not to prolong the system startup more then necessary.
lockfile=/var/lock/subsys/oracleEM
start)
   su $ORA_OWNER -c "$ORA_HOME/bin/emctl start dbconsole &" &>/dev/null
   touch $lockfile
stop)
   su $ORA_OWNER -c "$ORA_HOME/bin/emctl stop dbconsole"
   rm -rf $lockfile
...You do not need to start your Oracle instance before starting dbconsole. So there is no need for the "sleep" routine. You can start the Oracle Database control console even when the instance is down:
For instance:
<pre>
[oracle@vm005 ~]$ ps -ef | grep pmon
oracle 17749 10343 0 22:48 pts/3 00:00:00 grep pmon
$ emctl start dbconsole
Oracle Enterprise Manager 11g Database Control Release 11.2.0.1.0
Copyright (c) 1996, 2009 Oracle Corporation. All rights reserved.
https://vm005.example.com:1158/em/console/aboutApplication
Starting Oracle Enterprise Manager 11g Database Control ....... started.
</pre>

Could not start OAS node manager

i am getting this message while trying to start up the node manager (owsctl start -nodemgr)
OWS-08802: Oracle Web Listener 'node' does
not exist.
other services started okey. any idea ?

I am getting the sam message too please help
i am getting this message while trying to start up the node manager (owsctl start -nodemgr)
OWS-08802: Oracle Web Listener 'node' does
not exist.
other services started okey. any idea ?

Start EM(Enterprise Manager) with AdminServer(WebLogic) in services Windows

hi,
I have installed
WebLogic Server 1036 and Forms/Reports 11GR2
Installed WebLogic (AdminServer) to start with Windows Services!
It starts with Windows and open localhost: 7001/console 'successfully
echo off
SETLOCAL
set DOMAIN_NAME=FormsDomain
set USERDOMAIN_HOME=C:\Oracle\Middleware\user_projects\domains\FormsDomain
set SERVER_NAME=AdminServer
set PRODUCTION_MODE=true
set WLS_USER=weblogic
set WLS_PW=weblogic1
call C:\Oracle\Middleware\wlserver_10.3\server\bin\installSvc.cmd
ENDLOCAL
Everything ok so far!
However, I can not EM (Enterprise Manager) "localhost: 7001/em '
When I start the Server Admin Menu> Windows \ Start Menu \ Programs \ Oracle Classic Instance - FormsInst> Start Weblogic Server Admin
I can get 'localhost: 7001/em' usually
Can anyone give me an idea?

can someone help me?
checking the log returns this error!
####<25/09/2013 14h27min39s BRT> <Warning> <Munger> <RONEI> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <c45a6d0f723d9f21:-3dd7bb09:1415629670e:-8000-0000000000000002> <1380130059591> <BEA-2156203> <A version attribute was not found in element application in the deployment descriptor in C:\Oracle\Middleware\user_projects\applications\FormsDomain\em.ear/META-INF/application.xml. A version attribute is required, but this version of the Weblogic Server will assume that the JEE5 is used. Future versions of the Weblogic Server will reject descriptors that do not specify the JEE version.>
####<25/09/2013 14h27min39s BRT> <Error> <Deployer> <RONEI> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <c45a6d0f723d9f21:-3dd7bb09:1415629670e:-8000-0000000000000002> <1380130059671> <BEA-149205> <Failed to initialize the application 'em' due to error weblogic.management.DeploymentException: .
weblogic.management.DeploymentException:
at weblogic.application.internal.flow.BaseLifecycleFlow$CreateListenerAction.run(BaseLifecycleFlow.java:176)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.application.internal.flow.BaseLifecycleFlow$BaseAction.invoke(BaseLifecycleFlow.java:104)
at weblogic.application.internal.flow.HeadLifecycleFlow.createListener(HeadLifecycleFlow.java:117)
at weblogic.application.internal.flow.HeadLifecycleFlow.createListener(HeadLifecycleFlow.java:103)
at weblogic.application.internal.flow.HeadLifecycleFlow.createListeners(HeadLifecycleFlow.java:175)
at weblogic.application.internal.flow.HeadLifecycleFlow.prepare(HeadLifecycleFlow.java:281)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:648)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:59)
at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:144)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:39)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:191)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused By: java.lang.ClassNotFoundException: oracle.security.jps.wls.listeners.JpsApplicationLifecycleListener
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:297)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:179)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:247)
at weblogic.application.internal.flow.BaseLifecycleFlow$CreateListenerAction.run(BaseLifecycleFlow.java:140)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.application.internal.flow.BaseLifecycleFlow$BaseAction.invoke(BaseLifecycleFlow.java:108)
at weblogic.application.internal.flow.HeadLifecycleFlow.createListener(HeadLifecycleFlow.java:117)
at weblogic.application.internal.flow.HeadLifecycleFlow.createListener(HeadLifecycleFlow.java:103)
at weblogic.application.internal.flow.HeadLifecycleFlow.createListeners(HeadLifecycleFlow.java:175)
at weblogic.application.internal.flow.HeadLifecycleFlow.prepare(HeadLifecycleFlow.java:281)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:649)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:59)
at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:144)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:40)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:191)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:22)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:166)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:181)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:97)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)

Not able to start SOA managed server first time with node manager by WLST

Hi all,
I have created a SOA11g domain. Then using WLST utility I have started the Node Manager.
Then from WLST prompt I have connected to the Node Manager & started the Admin Server successfully.
But when ever I am starting the SOA manager server using WLST it's throwing the following error in WLST page : -
Error Starting server soa_server1: weblogic.nodemanager.NMException: Exception while starting server 'soa_server1'
In server log file I am getting the following error : -
Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication for user denied
weblogic.security.SecurityInitializationException: Authentication for user denied
I am getting this problem only when I am trying to start the domain for the first time after domain creation using WLST/nodemanager.
If I start & stop the SOA managed server from EM console & then try to start it aging from WLST/NodeManager then it's work fine.
Can anyone please tell me what can be the issue?
Thanks in Advance!!!
Edited by: 008 on Dec 6, 2012 7:53 PM

Hi,
I am getting this problem only when I am trying to start the domain for the first time after domain creation using WLST/nodemanager.
If I start & stop the SOA managed server from EM console & then try to start it aging from WLST/NodeManager then it's work fine.When you a server for the first time by using console or startManagedWeblogic.cmd, a file boot.properties is created under %DOMAIN_HOME%\servers\soa_server2\data\nodemanager...
The WLST/Nodemanager approach doesn't create the file so it won't work for the first start... But it will work just fine from the second on...
I've never tried, but you can try and create the boot.properties manually in your script with the following content... Password should be encrypted after the first successful start...
username=type-the-username-here
password=type-the-password-here
Cheers,
Vlad

Start managed server with the node manager???

Hello,
I have one admin server and one managed server for my domain. Can i Start the amdin and managed server from the node manager and not just the admin server. Currently with the install of node manager only the admin server starts and not the managed server. I need to log in to the admin server to start my managed server which is very cumbersome.
Edited by: user9021545 on Mar 11, 2011 1:58 PM

hi,
In order to start Managed server from the console itself,then u have to enroll your node manager.
Step1). Start the AdminServer...using startScript "startWebLogic.sh/cmd"
step2)start ur node manager using stat node manager scripts,
step3)Login to adminConsole and then see the NodeManager is Reachable or not
If reachanble
then run "setWLSEnv.sh/cmd".
Then run wlst.sh file
Step3)connect('weblogic','weblogic','t3://localhost:7001')
Step4)nmEnroll('C:/bea103/user_projects/domains/7001_Domain','C:/bea103/wlserver_10.3/common/nodemanager')
After this u will be able to start and stop managed server from console itself
Note:even after dis your managed server doesnt starts then please check under <DOMAIN_ROOT>\servers\<SERVER_NAME> whether you have a folder name as security and inside it whether you have file called as boot.properties
if no then follow these below steps
Please create a directory "security" inside your
<DOMAIN_ROOT>\servers\<SERVER_NAME>
inside "<DOMAIN_ROOT>\servers\<SERVER_NAME>\security" ( Example Location:
WLS103/user_projects/domains/Test_Domain/servers/AdminServer/security )
directory create a file with exactly same name as "boot.properties" and with
following 2 lines inside it:
username=weblogic
password=weblogic
NOTE: Here "weblogic" is the Administrator username & password...
if you want dont want to run Admin server from foreground then try runnin it as a background process
This link wi; b helpful for that
http://middlewareforum.com/weblogic/?cat=23
any further help in this den do let me know
Regards
Fabian

[wls8.1 sp.3] cannot remote start with node manager on another server

In this domain run on 2 physical servers in windows 2003. In machine that has admin server can start with node manager but another machine without admin server cannot remote start . when i remote start , the node manager has facing error messages as below:
# AT "node manager monitoring" in weblogic admin console
[[NodeManager:300033]Could not execute command ping on the node manager. Reason: weblogic.nodemanager.NodeManagerException: [CommandInvoker: Failed to send command: 'ping to server 'null' to NodeManager at host: 'xxx.xxx.xxx.24:5555' with exception Connection reset by peer.. Please ensure that the NodeManager is active on the target machine].]
# AT "nodemanger.log" has facing error messages as below:
<Aug 20, 2008 7:34:07 PM ICT> <Info> <[email protected]:5555> <NodeManage r started, log messages being written into file C:\bea\WEBLOG~1\common\NODEMA~1\ NodeManagerLogs\NodeManagerInternal\nm_server02_08_20_2008-19_34_03.log>
<Aug 20, 2008 7:59:58 PM ICT> <Warning> <Security> <BEA-090476> <Invalid/unknown SSL header was received from peer server01 - 10.208.50.23 during SSL handsha ke.> <Aug 20, 2008 8:00:11 PM ICT> <Warning> <Security> <BEA-090476> <Invalid/unknown SSL header was received from peer server01 - xxx.xxx.xxx.23 during SSL handsha key.>
I would REALLY appreciate any suggestions as to what might be the cause or what i could try.
Thanks ....

Hi,
It is up to you to decide whether you want to use nodemanager or not.
It does not make any difference if the server is started via script or nodemanager.
if i want everything (AS, MS, and NM) to come up at server boot i need to set each of them up as windows services (which is what i have at the moment) but this wont allow me to use the node manager ==> Yes this statement is correct.
You can either set AS and MS as windows service (or) AS and nodemanager as service.
Thanks,
Sharmela

NPE while starting Node Manager in SOA 11.1.1.5

I have installed SOA Suite 11g (11.1.1.5) as per Oracle Quick Start Guide for SOA Suite 11.1.1.5.
I start the database and Weblogic admin server. When I try to start the node manager, I am getting following error:
1 Nov, 2011 9:23:28 AM weblogic.nodemanager.server.NMServer <init>
WARNING: Node manager configuration properties file 'C:\Oracle\MIDDLE~3\WLSERV~1
.3\common\NODEMA~1\nodemanager.properties' not found. Using default settings.
<1 Nov, 2011 9:23:28 AM> <INFO> <Saving node manager configuration properties to
'C:\Oracle\MIDDLE~3\WLSERV~1.3\common\NODEMA~1\nodemanager.properties'>
1 Nov, 2011 9:23:28 AM weblogic.nodemanager.server.NMServer <init>
INFO: Saving node manager configuration properties to 'C:\Oracle\MIDDLE~3\WLSERV
~1.3\common\NODEMA~1\nodemanager.properties'
<1 Nov, 2011 9:23:28 AM> <SEVERE> <Fatal error in node manager server>
java.lang.NullPointerException
at java.util.Hashtable.containsKey(Hashtable.java:314)
at weblogic.nodemanager.server.NMServerConfig.initNetworkInfoList(NMServ
erConfig.java:491)
at weblogic.nodemanager.server.NMServerConfig.getNetworkInfoList(NMServe
rConfig.java:481)
at weblogic.nodemanager.server.NMServerConfig.getConfigProperties(NMServ
erConfig.java:545)
at weblogic.nodemanager.server.NMServer.<init>(NMServer.java:154)
at weblogic.nodemanager.server.NMServer.main(NMServer.java:375)
at weblogic.NodeManager.main(NodeManager.java:31)
1 Nov, 2011 9:23:28 AM weblogic.nodemanager.server.NMServer main
SEVERE: Fatal error in node manager server
java.lang.NullPointerException
at java.util.Hashtable.containsKey(Hashtable.java:314)
at weblogic.nodemanager.server.NMServerConfig.initNetworkInfoList(NMServ
erConfig.java:491)
at weblogic.nodemanager.server.NMServerConfig.getNetworkInfoList(NMServe
rConfig.java:481)
at weblogic.nodemanager.server.NMServerConfig.getConfigProperties(NMServ
erConfig.java:545)
at weblogic.nodemanager.server.NMServer.<init>(NMServer.java:154)
at weblogic.nodemanager.server.NMServer.main(NMServer.java:375)
at weblogic.NodeManager.main(NodeManager.java:31)
C:\Oracle\MIDDLE~3\WLSERV~1.3\common\NODEMA~1>goto finish
C:\Oracle\MIDDLE~3\WLSERV~1.3\common\NODEMA~1>ENDLOCAL
C:\Oracle\Middleware\wlserver_10.3\server\bin>
I checked "C:\Oracle\Middleware\wlserver_10.3\common\nodemanager" directory. There is no nodemanager.properties file there. Do I need to create it manually?
Please advise.
Thanks,
Vivek

I cut and paste the description of the note. There is a statement with the cause that states
"This issue happens only when the display name of a NIC configured for migration in nodemanager is null"
and it is a little ambigious. It implies there is a workaround of setting the display name, but doesn't discuss how to apply this workaround; the display name it refers to generated by a code call to the NetworkInterface.getDisplayName() method from the JDK.
I assume that the display name here is the parameter called Interface within the nodemanger.properties, but there is nothing within the note that confirms this, nor if setting this to the NICE name will fix this issue. here is a full list of the nodemanger.propertes file -> http://download.oracle.com/docs/cd/E12840_01/wls/docs103/nodemgr/java_nodemgr.html#wp1068415
I'd download and try the patch in your place; it's a WLS patch (as nodemanager is part of WLS) so shouldn't affect SOA Suite. Failing that, open a SR.

Node manager or the Admin server - which one to start first?

Hi Experts,
Somewhere i see its this way.
OBIEE 11.1.1.6 | OBIEE
To start the Oracle Business Intelligence system, you start:
the Node Manager(It is by default windows service in Enterprise Installation of OBIEE 11G)
the Administration Server (It is weblogic Admin Server)
the Managed Servers(Comes with Enterprise Installation of OBIEE 11G)
and then you start the system components.(All OBIEE Components : BI Server,Presentation Server,Schedular,Java Host,Cluster Services.
and at other places i see this...
OBIEE 11G - Starting Oracle Business Intelligence | GerardNico.com (BI, OBIEE, OWB, DataWarehouse)
To start the Oracle Business Intelligence system, you start:
the Administration Server
the Node Manager
the Managed Servers,
and then you start the system components.
I have Linux environment and it has just single BI Server and i go like this.
1) startWeblogic.sh script
2) startNodeManager.sh
3) startManagedWeblogic.sh
4) then system components.
Thanks
Ashish

so the way i am starting OBIEE Services currently is basically wrong ie..
1) startWeblogic.sh script
2) startNodeManager.sh
3) startManagedWeblogic.sh
4) then system components.
( by the way everything comes up perfect even if i start the nodemanager after the startWeblogic.sh script)
and i should do it this way..
1)startNodeManager.sh
2)startWeblogic.sh script
3)startManagedWeblogic.sh
4) then system components.
Kindly confirm...

Unable to start Node Manager

Hello everyone,
I've installed WLS 10.3.3 on windows. *2 Managed servers (jitu-pc, jitu-pc1) & 1 admin server on same machine*.
Below are the SSL configurations for both:
Host Name Verification = None
Machine>Node Manager: Type=PLAIN
When I try to start the node manager ($BEA_HOME\server\bin\startNodeManager.cmd" I get below error:
<Oct 15, 2010 4:11:33 AM> <INFO> <Secure socket listener started on port 5556>
Oct 15, 2010 4:11:33 AM weblogic.nodemanager.server.SSLListener run
*INFO: Secure socket listener started on port 5556*
<Oct 15, 2010 4:12:04 AM GMT+05:30> <Warning> <Security> <BEA-090476> <Invalid/unknown SSL header was received from peer 01HW165700.entcorp.ttsl.com - 172.17.43.84 during SSL handshake.>
<Oct 15, 2010 4:12:04 AM GMT+05:30> <Warning> <Security> <BEA-090476> <Invalid/unknown SSL header was received from peer 01HW165700.entcorp.ttsl.com - 172.17.43.84 during SSL handshake.>
<Oct 15, 2010 4:12:04 AM> <WARNING> <Uncaught exception in server handlerjavax.net.ssl.SSLHandshakeException: [Security:090476]Invalid/unknown SSL header was received from peer 01HW165700 - 172.17.43.84 during SSL handshake.>
javax.net.ssl.SSLHandshakeException: [Security:090476]Invalid/unknown SSL header was received from peer 01HW165700 - 172.17.43.84 during SSL handshake.
at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireException(Unknown Source)
at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireAlertSent(Unknown Source)
at com.certicom.tls.record.ReadHandler.fireAlert(Unknown Source)
at com.certicom.tls.record.ReadHandler.getProtocolVersion(Unknown Source)
at com.certicom.tls.record.ReadHandler.checkVersion(Unknown Source)
at com.certicom.tls.record.ReadHandler.readRecord(Unknown Source)
at com.certicom.tls.record.ReadHandler.readUntilHandshakeComplete(Unknown Source)
at com.certicom.tls.interfaceimpl.TLSConnectionImpl.completeHandshake(Unknown Source)
at com.certicom.tls.record.ReadHandler.read(Unknown Source)
at com.certicom.io.InputSSLIOStreamWrapper.read(Unknown Source)
at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264)
at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306)
at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158)
at java.io.InputStreamReader.read(InputStreamReader.java:167)
at java.io.BufferedReader.fill(BufferedReader.java:136)
at java.io.BufferedReader.readLine(BufferedReader.java:299)
at java.io.BufferedReader.readLine(BufferedReader.java:362)
at weblogic.nodemanager.server.Handler.run(Handler.java:70)
at java.lang.Thread.run(Thread.java:619)
Can anybody tell me what am I missing ?

Thanks Jay,
That worked.
Also, I've one more doubt.
I browsed to the $WEBLOGIC_HOME/common/nodemanager directory.
From there I executed $WEBLOGIC_HOME/server/bin startNodeManager.cmd.
But before starting there is no "nodemanager.properties" file.
After I started node manager, it started with default properties, and wrote the same to "nodemanager.properties" file in the same directory I started the node manager from.
Then I aborted the node manager, edited the property file for SecureListener and then restarted. Then everything went up and fine.
My question is that is there any default "nodemanager.properties" ?

Unable to start SOA server through Node Manager

Hi All,
I am trying to install AIA 11.1.1.6.0 on the top of SOA Suite 11.1.1.6.0.
I was able to install successfully the weblogic server, rcu, soa and osb servers. Now, before installing the AIA, the document i am following it says, make sure to start the soa server through the node manager.
Now i start the admin server, then the node manager, to make sure i have checked that the node manager is up, i logged in to the weblogic console, went to Machines, and i can see that it is up and reachable.
Now using the WLST commands, first i connected to the node manager using command nmConnect(), then i am trying to start the soa server through node manager using the command start('soa_server1') command.
I am getting an error while trying to start soa server with nmStart() command, below is the error message...
"Error starting server soa_server1: weblogic.nodemanager.NMException: Exception while starting server 'soa_server1'"
I executed the dumpStack() command, and i am getting the output as "No stack trace available"
If i am able to start the soa server through the node manager, i can go ahead and install the AIA pack but this is not letting me go forward.
I also tried to start the soa server through the weblogic console., go to servers tab, select the soa_server1 and start, the soa server state is going to "FAILED_NOT_RESTARTABLE".
I followed some of the blogs like...
http://neeraj-soa-tips.blogspot.com/2010/06/starting-admin-and-managed-servers.html
http://www.javamonamour.org/2011/09/nmconnect-nmstart-nmkill.html
Experts, please give your advice.
Many Thanks,
N

Hi Narsing,
I'm assuming that you've followed the required Pre-config steps. If it is not working, I'd suggest to start the Admin and SOA server without node manager first. Then start your node manager and see if it is reachable from the WLS console. Then shut down your SOA server from command prompt and restart your SOA server from WLS console.
Verify the Listen Address of your Node Manager and start your node manager from command prompt by explicitly specifying the same address and port.
As WLS console internally uses node manager only to start your server, you would not need to use WLST scripts to do the same and only SOA server needs to be started using node manager.
Regards,
Neeraj Sehgal
Hi Neeraj,
I made sure that in the weblogic console, in the machines tab, local machine-->configuration--->Node Manager, I have given the correct Listen Address (Narsing-PC) and the listen port 5556.
I have made sure the property StartScriptEnabled= true.
I have started the admin server through startWebLogic.cmd command, now i start the node manager by going to the C:\Oracle\Middleware\wlserver_10.3\server\bin and running the command startNodeManager.cmd, then i go to the weblogic console--->servers--->control--->soa_server1--->start , it is going to      FAILED_NOT_RESTARTABLE status.
If i see the log messages in the nodemanager.log, this is the below message...
<Jun 28, 2012 11:25:09 PM> <INFO> <soa_domain> <soa_server1> <Server output log file is 'C:\Oracle\Middleware\user_projects\domains\soa_domain\servers\soa_server1\logs\soa_server1.out'>
<Jun 28, 2012 11:25:11 PM> <INFO> <soa_domain> <soa_server1> <Server failed during startup so will not be restarted>
<Jun 28, 2012 11:25:11 PM> <WARNING> <Exception while starting server 'soa_server1'>
java.io.IOException: Server failed to start up. See server output log for more details.
     at weblogic.nodemanager.server.AbstractServerManager.start(AbstractServerManager.java:196)
     at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:23)
     at weblogic.nodemanager.server.Handler.handleStart(Handler.java:609)
     at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:121)
     at weblogic.nodemanager.server.Handler.run(Handler.java:71)
     at java.lang.Thread.run(Thread.java:662)
The log message in the soa_server1.out file is as below...
Starting WLS with line:
C:\Oracle\MIDDLE~1\JDK160~1\bin\java -client -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8453,server=y,suspend=n -Djava.compiler=NONE -Xms512m -Xmx1024m -XX:PermSize=128m -XX:MaxPermSize=512m -Dweblogic.Name=soa_server1 -Djava.security.policy=C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.policy -Dweblogic.system.BootIdentityFile=C:\Oracle\Middleware\user_projects\domains\soa_domain\servers\soa_server1\data\nodemanager\boot.properties -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.security.SSL.ignoreHostnameVerification=false -Dweblogic.ReverseDNSAllowed=false -Xverify:none -da:org.apache.xmlbeans... -ea -da:com.bea... -da:javelin... -da:weblogic... -ea:com.bea.wli... -ea:com.bea.broker... -ea:com.bea.sbconsole... -Dplatform.home=C:\Oracle\MIDDLE~1\WLSERV~1.3 -Dwls.home=C:\Oracle\MIDDLE~1\WLSERV~1.3\server -Dweblogic.home=C:\Oracle\MIDDLE~1\WLSERV~1.3\server -Dcommon.components.home=C:\Oracle\MIDDLE~1\ORACLE~1 -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Ddomain.home=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1 -Djrockit.optfile=C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrocket_optfile.txt -Doracle.server.config.dir=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1\config\FMWCON~1\servers\soa_server1 -Doracle.domain.config.dir=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1\config\FMWCON~1 -Digf.arisidbeans.carmlloc=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1\config\FMWCON~1\carml -Digf.arisidstack.home=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1\config\FMWCON~1\arisidprovider -Doracle.security.jps.config=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1\config\fmwconfig\jps-config.xml -Doracle.deployed.app.dir=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1\servers\soa_server1\tmp\_WL_user -Doracle.deployed.app.ext=\- -Dweblogic.alternateTypesDirectory=C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.ossoiap_11.1.1,C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.oamprovider_11.1.1 -Djava.protocol.handler.pkgs=oracle.mds.net.protocol"|"oracle.fabric.common.classloaderurl.handler"|"oracle.fabric.common.uddiurl.handler"|"oracle.bpm.io.fs.protocol -Dweblogic.jdbc.remoteEnabled=false -Doracle.security.jps.policy.migration.validate.principal=false -da:org.apache.xmlbeans... -Dbpm.enabled=true -Dsoa.archives.dir=C:\Oracle\Middleware\Oracle_SOA1\soa -Dsoa.oracle.home=C:\Oracle\Middleware\Oracle_SOA1 -Dsoa.instance.home=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1 -Dtangosol.coherence.clusteraddress=227.7.7.9 -Dtangosol.coherence.clusterport=9778 -Dtangosol.coherence.log=jdk -Djavax.xml.soap.MessageFactory=oracle.j2ee.ws.saaj.soap.MessageFactoryImpl -Dweblogic.transaction.blocking.commit=true -Dweblogic.transaction.blocking.rollback=true -Djavax.net.ssl.trustStore=C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\DemoTrust.jks -Dem.oracle.home=C:\Oracle\Middleware\oracle_common -Djava.awt.headless=true -Dbam.oracle.home=C:\Oracle\Middleware\Oracle_SOA1 -Dums.oracle.home=C:\Oracle\Middleware\Oracle_SOA1 -Dweblogic.management.discover=false -Dweblogic.management.server=http://localhost:7001 -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=C:\Oracle\MIDDLE~1\patch_wls1036\profiles\default\sysext_manifest_classpath;C:\Oracle\MIDDLE~1\patch_oepe180\profiles\default\sysext_manifest_classpath;C:\Oracle\MIDDLE~1\patch_ocp371\profiles\default\sysext_manifest_classpath;C:\Oracle\MIDDLE~1\patch_adfr1111\profiles\default\sysext_manifest_classpath weblogic.Server
FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
ERROR: transport error 202: bind failed: Address already in use
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]
<Jun 28, 2012 11:25:11 PM> <FINEST> <NodeManager> <Waiting for the process to die: 4808>
<Jun 28, 2012 11:25:11 PM> <INFO> <NodeManager> <Server failed during startup so will not be restarted>
<Jun 28, 2012 11:25:11 PM> <FINEST> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>
Someone please help, if i am able to start the soa manged server, i can go ahead and install the AIA Foundation pack...
Many Thanks.

Starting a node manager with rsh

Similar Messages

Maybe you are looking for