Starting Node Manager

We have a configuration where weblogic installed as
          /weblogic/bea/wlserevr6.1
          The applications are installed as
          /usr1/config/<app>
          To start the node manager I copied the certificates into /usr1/config
          directory and specified the path on the command line for nodce manager.
          When I try to start node manager from the /usr/config directory I get an
          access control exception.
          However I am able to start node manager from the directory where weblogic is
          installed.
          Any ideas?

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.

Similar Messages

OBIEE 11g (11.1.1.5.0) - Issue with starting Node Manager

Hi,
Have anyone faced an issue with starting Node Manager in OBIEE 11g (11.1.1.5.0)? OS is 64 bit Linux, WebLogic is 10.3.5. I used the software-install method and followed by running config.sh. Everything completed successfully. I updated the catalog and rpd location in the FMW control screen.
To get it activated I bounced services and when I try to start Node Manager it gives below error --
<Aug 30, 2011 2:02:42 PM CDT> <Info> <Security> <BEA-090906> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true>
<Aug 30, 2011 2:02:42 PM> <SEVERE> <Fatal error in node manager server>
java.io.IOException: Unsupported cypher suite: TLS_RSA_EXPORT_WITH_RC4_40_MD5
at weblogic.nodemanager.server.SSLListener.init(SSLListener.java:82)
at weblogic.nodemanager.server.NMServer.start(NMServer.java:206)
at weblogic.nodemanager.server.NMServer.main(NMServer.java:377)
at weblogic.NodeManager.main(NodeManager.java:31)
Aug 30, 2011 2:02:42 PM weblogic.nodemanager.server.NMServer main
SEVERE: Fatal error in node manager server
java.io.IOException: Unsupported cypher suite: TLS_RSA_EXPORT_WITH_RC4_40_MD5
at weblogic.nodemanager.server.SSLListener.init(SSLListener.java:82)
at weblogic.nodemanager.server.NMServer.start(NMServer.java:206)
at weblogic.nodemanager.server.NMServer.main(NMServer.java:377)
at weblogic.NodeManager.main(NodeManager.java:31)
+ set +x
I see the same issue reported in ML OBIEE 11g - Node manager fails to start upon upgrade [ID 1329442.1] and WebLogic Server: Node Manager Startup is Failing with java.io.IOException: Unsupported cypher suite [ID 1329260.1] I tried to modify commEnv.sh. But it didnt help me.
Please let me know if anyone have faced similar issue and what exactly did you do to resolve it.
Cherrish Vaidiyan
Edited by: Cherrish on Aug 30, 2011 3:14 PM

Hi,
There are Two types of Cipher suites --- Certicom Cipher Suite and SunJSSE Equivalent Cipher Suite. And with Weblogic 10.3.5, you are using Sun JSSE Cipher Suite, and by default Node Manager uses the Certicom Cipher Suite.
In the nodemanager.properties, Add CipherSuite=SSL_RSA_EXPORT_WITH_RC4_40_MD5, save and restart Node Manager.
Reference Metalink Note: WebLogic Server 10.3.x: Getting "Unsupported Cipher" Exceptions When Starting Node Manager [ID 1307325.1]
Cherrish Vaidiyan

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

Need help: error when starting node manager

When attempting to start node manager i recieve the following error:
<Sep 30, 2004 1:30:47 PM EDT> <Error> <NodeManager> <Node manager could not find the required library, libNodeManager.so, in path - /usr/j2se/jre/lib/i386/client:/usr/j2se/jre/lib/i386:/usr/j2se/jre/../lib/i386:/export/home/bea/weblogic81/server/lib/solaris:/export/home/bea/weblogic81/server/lib/solaris/oci920_8:/usr/lib>
i have copied the file, libnodemanager.so to every directory in the path above, spelling and case are correct, permissions set to rwxrwxrwx but still get error.
wl 8.1 sp2 solaris 9.1.
please help if you can.
thanks.
vb

Hi Chaitanya,
Does the nodemanager.domains file exists in
/home/xyz/Oracle/Middleware/Oracle_Home/oracle_common/common/nodemanager?
Does it contain a reference to your domain?
For example:
tetra=/u01/app/oracle/domains/tetra
Regards Peter
http://theheat.dk

Start node manager using WLST

I am trying to start node manager using WLST with following command
wls:/offline> nmConnect('weblogic','weblogic123','localhost','5556','FirstDomain','C:\Oracle\Middleware\user_projects\domains\FirstDomain','plain')but getting below exception
Traceback (innermost last):
File "<console>", line 1, in ?
File "<iostream>", line 123, in nmConnect
File "<iostream>", line 618, in raiseWLSTException
WLSTException: Error occured while performing nmConnect : Cannot connect to Node
Manager. : Connection refused: connect. Could not connect to NodeManager. Check
that it is running at localhost:5,556.
Use dumpStack() to view the full stacktrace
wls:/offline>
I am using weblogic 11g.
Can anybody let me know how to fix this issue.

You can use something like this:
beahome = '/home/oracle/soasuite';
pathseparator = '/';
adminusername = 'weblogic';
adminpassword = 'magic11g';
domainname = 'base_domain';
domainlocation = beahome + pathseparator + 'user_projects' + pathseparator + 'domains' + pathseparator + domainname;
nodemanagerhomelocation = beahome + pathseparator + 'wlserver_10.3' + pathseparator + 'common' + pathseparator + 'nodemanager';
print 'START NODE MANAGER';
startNodeManager(verbose='true', NodeManagerHome=nodemanagerhomelocation, ListenPort='5556', ListenAddress='localhost');
print 'CONNECT TO NODE MANAGER';
nmConnect(adminusername, adminpassword, 'localhost', '5556', domainname, domainlocation, 'ssl');
print 'START ADMIN SERVER';
nmStart('AdminServer');
nmServerStatus('AdminServer');More information can be found here: http://middlewaremagic.com/weblogic/?p=6040
in particular the "Starting the SOA environment" section

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.

Unable to start node manager of WebLogic 12c on OEL 5.9 64 bit

Hi,
I have WLS 12 running on OEL 5.9 64 bit.
The installation ise JDK instead of the default JRockit.
The version of Java that has been installed is from rpm: jdk-7u25-linux-x64.rpm
I have created a domain.
I am unable to start the Node Manager the first time, and thus unable to create the file nodemanager.properties.
I get an error:
weblogic.nodemanager.common.ConfigException: Native version is enabled but nodemanager native library could not be loaded
I have added JAVA_USE_64BIT=true in the commEnv.sh, but it seems not to help.
Does someone know how to get the nodde manager runing on a Linux x86 64 bit?
Thanks by advance for any tip.

Hello, try this:
1. Set the environment to use the 64 bit WLS library:
export LD_LIBRARY_PATH=
/u01/Middleware/wlserver_10.3/server/native/linux/x86_64/:/u01/Middleware/wlserver_10.3/server/native/linux/i686/
2. Retry the domain configuration:
/u01/Middleware/Oracle_PFRD/bin/config.sh

Connection Refused when starting node manager on Linux

Hi,
I'm using Weblogic 6.1 SP 2 on Redhat Linux 7.1 with Sun JDK 1.3.1. When I'm running
the Node Manager on one machine and try to connect to it from another machine (Admin
Server) I'm getting the following message:
<May 28, 2002 6:35:59 PM IDT> <Error> <NodeManager> <Could not start server 'EnvelopeManagedBackup'
via Node Manager - reason: '[SecureCommandInvoker: Could not create a socket to the
NodeManager running on host 'jarjar:5555' to execute command 'online null', reason:
Connection refused: connect. Ensure that the NodeManager on host 'jarjar' is configured
to listen on port '5555' and that it is actively listening]'>
The Node Manager is listening on the server's listen address (jarjar) and on the
correct port (5555). When running netstat -a | grep 5555 on the server I get the
following (jarjar is the computer name):
tcp 0 0 jarjar:5555 *:* LISTEN
The admin server is registered in the nodemanager.hosts file.
Can anyone help me on this?

....I happened to get "execute command 'online null'" because of a missing
"Listen Address" and/or "Listen Port" entry in the "Remote Start" tab of the
Administration Server.
Node Manager passes on such values when starting up a managed server - if
either is blank, the managed server can not identify the Admin Server to
register to...
Paola R.

While i m starting node manager in weblogic

Dear All,
my weblogic server was working fine after restarted the windows server, when i am trying to start the node manager i m getting below error, please guide me please, this is production
<Sep 22, 2013 12:58:07 AM> <WARNING> <There was a problem initializing the domain 'weblogic_domain' at 'D:\Oracle\Middleware\u
_domain'. Please make sure that this domainName: 'weblogic_domain' is registered and is fully enrolled for this nodemanager at
projects\domains\weblogic_domain'.>
Sep 22, 2013 12:58:07 AM weblogic.nodemanager.server.NMServer findOrCreateDomainManager
WARNING: There was a problem initializing the domain 'weblogic_domain' at 'D:\Oracle\Middleware\user_projects\domains\weblogic
at this domainName: 'weblogic_domain' is registered and is fully enrolled for this nodemanager at: 'D:\Oracle\Middleware\user_
ain'.
<Sep 22, 2013 12:58:07 AM> <WARNING> <I/O error while reading domain directory>
java.io.IOException: Invalid state file format. State file contents:
        at weblogic.nodemanager.common.StateInfo.load(StateInfo.java:135)
        at weblogic.nodemanager.server.AbstractServerMonitor.loadStateInfo(AbstractServerMonitor.java:497)
        at weblogic.nodemanager.server.AbstractServerMonitor.isCleanupAfterCrashNeeded(AbstractServerMonitor.java:156)
        at weblogic.nodemanager.server.ServerMonitor.isCleanupAfterCrashNeeded(ServerMonitor.java:25)
        at weblogic.nodemanager.server.AbstractServerManager.recoverServer(AbstractServerManager.java:147)
        at weblogic.nodemanager.server.ServerManager.recoverServer(ServerManager.java:23)
        at weblogic.nodemanager.server.DomainManager.initialize(DomainManager.java:105)
        at weblogic.nodemanager.server.DomainManager.<init>(DomainManager.java:60)
        at weblogic.nodemanager.server.NMServer.findOrCreateDomainManager(NMServer.java:284)
        at weblogic.nodemanager.server.NMServer.getDomainManager(NMServer.java:273)
        at weblogic.nodemanager.server.Handler.handleDomain(Handler.java:227)
        at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:109)
        at weblogic.nodemanager.server.Handler.run(Handler.java:71)
        at java.lang.Thread.run(Thread.java:662)
Sep 22, 2013 12:58:07 AM weblogic.nodemanager.server.Handler handleDomain
WARNING: I/O error while reading domain directory
java.io.IOException: Invalid state file format. State file contents:
        at weblogic.nodemanager.common.StateInfo.load(StateInfo.java:135)
        at weblogic.nodemanager.server.AbstractServerMonitor.loadStateInfo(AbstractServerMonitor.java:497)
        at weblogic.nodemanager.server.AbstractServerMonitor.isCleanupAfterCrashNeeded(AbstractServerMonitor.java:156)
        at weblogic.nodemanager.server.ServerMonitor.isCleanupAfterCrashNeeded(ServerMonitor.java:25)
        at weblogic.nodemanager.server.AbstractServerManager.recoverServer(AbstractServerManager.java:147)
        at weblogic.nodemanager.server.ServerManager.recoverServer(ServerManager.java:23)
        at weblogic.nodemanager.server.DomainManager.initialize(DomainManager.java:105)
        at weblogic.nodemanager.server.DomainManager.<init>(DomainManager.java:60)
        at weblogic.nodemanager.server.NMServer.findOrCreateDomainManager(NMServer.java:284)
        at weblogic.nodemanager.server.NMServer.getDomainManager(NMServer.java:273)
        at weblogic.nodemanager.server.Handler.handleDomain(Handler.java:227)
        at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:109)
        at weblogic.nodemanager.server.Handler.run(Handler.java:71)
        at java.lang.Thread.run(Thread.java:662)
thanks

why do you mis-post this problem in an Oracle database forum when root cause & fix are external to any Oracle database?

Unable to start Manager server using Node Manager

Hi,
I have deployed Admin server in one of my unix machine(machine1) and i able to start my Admin server using node manager, and when i try to start my Managed server in another machine(machine2) using the node manager(that machine node manager) its throwing error;
Note: am able to start Managed server using Adminurl and able to connect to Managed server node manager successfully,
but not able to start Managed server using node manager
its giving exception as below;
error:- wls:/nm/webdomain> nmStart('ms1')
Starting server ms1 ...
Error Starting server ms1: weblogic.nodemanager.NMException: Exception while starting server 'ms1'
Managed server log: -
<Dec 13, 2011 3:40:17 PM> <INFO> <NodeManager> <Working directory is '/root/Oracle/Middleware/user_projects/domains/webdomain'>
[root@LinuxVM ~]# cat /root/Oracle/Middleware/user_projects/domains/webdomain/servers/ms1/logs/ms1.out00071
<Dec 13, 2011 3:40:17 PM> <INFO> <NodeManager> <Starting WebLogic server with command line: /root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/bin/java -Dweblogic.Name=ms1 -Dbea.home=/root/Oracle/Middleware -Djava.security.policy=/root/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.policy -Djava.library.path="/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/lib/i386/jrockit:/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/lib/i386:/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/../lib/i386:/root/Oracle/Middleware/patch_wls1035/profiles/default/native:/root/Oracle/Middleware/patch_ocp360/profiles/default/native:/root/Oracle/Middleware/wlserver_10.3/server/native/linux/i686:/root/Oracle/Middleware/wlserver_10.3/server/native/linux/i686/oci920_8" -Djava.class.path=/root/Oracle/Middleware/patch_wls1035/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/root/Oracle/Middleware/patch_ocp360/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/lib/tools.jar:/root/Oracle/Middleware/wlserver_10.3/server/lib/weblogic_sp.jar:/root/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.jar:/root/Oracle/Middleware/modules/features/weblogic.server.modules_10.3.5.0.jar:/root/Oracle/Middleware/wlserver_10.3/server/lib/webservices.jar:/root/Oracle/Middleware/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/root/Oracle/Middleware/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar::/root/Oracle/Middleware -Dweblogic.system.BootIdentityFile=/root/Oracle/Middleware/user_projects/domains/webdomain/servers/ms1/data/nodemanager/boot.properties -Dweblogic.nodemanager.ServiceEnabled=true weblogic.Server >
<Dec 13, 2011 3:40:17 PM> <INFO> <NodeManager> <Working directory is '/root/Oracle/Middleware/user_projects/domains/webdomain'>
Nodemanager log:
<Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Rotated server output log to "/root/Oracle/Middleware/user_projects/domains/webdomain/servers/ms1/logs/ms1.out00070">
<Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Server error log also redirected to server log>
<Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Starting WebLogic server with command line: /root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/bin/java -Dweblogic.Name=ms1 -Dbea.home=/root/Oracle/Middleware -Djava.security.policy=/root/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.policy -Djava.library.path="/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/lib/i386/jrockit:/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/lib/i386:/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/../lib/i386:/root/Oracle/Middleware/patch_wls1035/profiles/default/native:/root/Oracle/Middleware/patch_ocp360/profiles/default/native:/root/Oracle/Middleware/wlserver_10.3/server/native/linux/i686:/root/Oracle/Middleware/wlserver_10.3/server/native/linux/i686/oci920_8" -Djava.class.path=/root/Oracle/Middleware/patch_wls1035/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/root/Oracle/Middleware/patch_ocp360/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/lib/tools.jar:/root/Oracle/Middleware/wlserver_10.3/server/lib/weblogic_sp.jar:/root/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.jar:/root/Oracle/Middleware/modules/features/weblogic.server.modules_10.3.5.0.jar:/root/Oracle/Middleware/wlserver_10.3/server/lib/webservices.jar:/root/Oracle/Middleware/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/root/Oracle/Middleware/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar::/root/Oracle/Middleware -Dweblogic.system.BootIdentityFile=/root/Oracle/Middleware/user_projects/domains/webdomain/servers/ms1/data/nodemanager/boot.properties -Dweblogic.nodemanager.ServiceEnabled=true weblogic.Server >
<Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Working directory is '/root/Oracle/Middleware/user_projects/domains/webdomain'>
<Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Rotated server output log to "/root/Oracle/Middleware/user_projects/domains/webdomain/servers/ms1/logs/ms1.out00071">
<Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Server error log also redirected to server log>
<Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Server output log file is '/root/Oracle/Middleware/user_projects/domains/webdomain/servers/ms1/logs/ms1.out'>
<Dec 13, 2011 3:40:26 PM> <INFO> <webdomain> <ms1> <Server failed during startup so will not be restarted>
<Dec 13, 2011 3:40:26 PM> <WARNING> <Exception while starting server 'ms1'>
java.io.IOException: Server failed to start up. See server output log for more details.
at weblogic.nodemanager.server.AbstractServerManager.start(AbstractServerManager.java:200)
at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:23)
at weblogic.nodemanager.server.Handler.handleStart(Handler.java:604)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:119)
at weblogic.nodemanager.server.Handler.run(Handler.java:71)
at java.lang.Thread.run(Thread.java:662)

You can start a managed server as follows:
print 'START NODE MANAGER';
startNodeManager(verbose='true', NodeManagerHome=nodemanagerhomelocation, ListenPort='5556', ListenAddress='localhost');
print 'CONNECT TO NODE MANAGER';
nmConnect(adminusername, adminpassword, 'localhost', '5556', domainname, domainlocation, 'ssl');
print 'START ADMIN SERVER';
nmStart('AdminServer');
nmServerStatus('AdminServer');
print 'CONNECT TO ADMIN SERVER';
connect(adminusername, adminpassword);
print 'START MANAGED SERVER';
start('VideotheekWebServer','Server');
nmServerStatus('VideotheekWebServer');
print 'START CLUSTER';
start('VideotheekCluster','Cluster');
nmServerStatus('VideotheekServer1');
nmServerStatus('VideotheekServer2');JVM properties are set using the admin console and edit the startup properties of your managed server (configuration, server start).
The properties file (startup.properties) is saved in the directory <domain-home>/servers/<server-name>/data/nodemanager.

Error in Starting soa Managed server on WEBLOGIC 11g..Windows 7

Hi All,
I have an exception coming up while starting the soa_server1 managed soa server in Weblogic Domain.
I have started the Admin server but while starting the soa managed server we are getting the following error :
<Jul 26, 2010 9:29:04 PM PDT> <Critical> <EmbeddedLDAP> <BEA-000000> <java.io.Fi
leNotFoundException: D:\Oracle\Middleware\user_projects\domains\SOA_Domain\serve
rs\AdminServer\data\ldap\replicadata\soa_server1.status (The process cannot acce
ss the file because it is being used by another process)
at java.io.FileOutputStream.open(Native Method)
at java.io.FileOutputStream.<init>(FileOutputStream.java:179)
at java.io.FileOutputStream.<init>(FileOutputStream.java:70)
at com.octetstring.vde.replication.Replicator.increment(Replicator.java:
88)
at com.octetstring.vde.replication.Replicator.run(Replicator.java:301)
at com.octetstring.vde.replication.Replication.run(Replication.java:339)
>
Pointers on this error would help us.
Regards,
Ramnath

Lets us try to start your environment by using a WLST script.
Before you try starting the servers by using the script, could you first check your weblogic console,
to see if the server soa_server1 is running or not (click on environment, servers) maybe the enterprise manager is out of sync.
The following steps are necessary the run the script:
First edit the nodemanager.properties (which is located in the directory <middleware-home>/wlserver_10.3/common/nodemanager).
Find the entry StartScriptEnabled and set this property to true.
Open a command shell and navigate to the directory <middleware-home>/wlserver_10.3/server/bin and run the file setWLSEnv.cmd
(this sets your environment variables, so that we can run a WLST script).
Copy the following script into a file named for example StartScript.py and adjust variables as needed
beahome = '<middleware-home>';
linux = false;
adminusername = 'weblogic';
adminpassword = 'transfer-solutions';
domainname = 'base_domain';
pathseparator = '/';
if not linux:
print 'SETTING WINDOWS PATH SEPARATOR';
pathseparator = '\\';
domainlocation = beahome + pathseparator + 'user_projects' + pathseparator + 'domains' + pathseparator + domainname;
nodemanagerhomelocation = beahome + pathseparator + 'wlserver_10.3' + pathseparator + 'common' + pathseparator + 'nodemanager';
print 'START NODE MANAGER';
startNodeManager(verbose='true', NodeManagerHome=nodemanagerhomelocation, ListenPort='5556', ListenAddress='localhost');
print 'CONNECT TO NODE MANAGER';
nmConnect(adminusername, adminpassword, 'localhost', '5556', domainname, domainlocation, 'ssl');
print 'START ADMIN SERVER';
nmStart('AdminServer');
nmServerStatus('AdminServer');
print 'CONNECT TO ADMIN SERVER';
connect(adminusername, adminpassword);
print 'START SOA SERVER';
start('soa_server1','Server');
nmServerStatus('soa_server1');Run this script as follows, but first stop the servers already running
java weblogic.WLST <directory>/StartScript.py

Can i set a node manager serve for 2 domain on one machin??

My question is simple.
I installed webcenter suite and soa suite in a machine using difference linux user and difference middleware home.
and I want to set a node manager server for two domains (soa_domain and webcenter_domain).
Is is possible?
When I tried to register domain list in node manager domain list using nmEnroll() of wlst, it failed.
please check following logs in 7101 is admin server port of soa domain and I ran node manager on webcenter domain.
Thanks in advance.
BmW.
~~~~~~~~~~~~~~~~~~
wls:/offline> connect()
Please enter your username :weblogic
Please enter your password :
Please enter your server URL [t3://localhost:7001] :t3://localhost:7101
Connecting to t3://localhost:7101 with userid weblogic ...
Successfully connected to Admin Server 'AdminServer' that belongs to domain 'soa_domain'.
Warning: An insecure protocol was used to connect to the
server. To ensure on-the-wire security, the SSL port or
Admin port should be used instead.
wls:/soa_domain/serverConfig> wls:/soa_domain/serverConfig> wls:/soa_domain/serverConfig> wls:/soa_domain/serverConfig> nmEnroll('/u02/app/soa11g/middleware/user_projects/domains/soa_domain', '/u02/app/wc11g/middleware/wlserver_10.3/common/nodemanager');
Enrolling this machine with the domain directory at /u02/app/soa11g/middleware/user_projects/domains/soa_domain ...
Traceback (innermost last):
File "<console>", line 1, in ?
File "<iostream>", line 1447, in nmEnroll
File "<iostream>", line 1848, in raiseWLSTException
WLSTException: Error occured while performing nmEnroll : Problem enrolling the machine. : /u02/app/soa11g/middleware/user_projects/domains/soa_domain/config/nodemanager/nm_password.properties (Permission denied)
Use dumpStack() to view the full stacktrace
wls:/soa_domain/serverConfig> exit();

you might be victim of the "node manager starts WL Server with same Unix user id that was used to start Node Manager itself" problem
see here http://forums.oracle.com/forums/thread.jspa?threadID=2184607&tstart=89
I have been looking everywhere for a simple way to tell Node Manager to use a different Unix UID,
anybody any clue?
here http://download.oracle.com/docs/cd/E12840_01/wls/docs103/nodemgr/overview.html the Node Manager doc page

Can we start Node server as a windows service?

Hi,
I am starting admin server, managed server as windows service. I've also started node manager as windows service on a node machine. But, now if i want to start the node server, I am starting it from windows console. Instead of this, can i start the node server as windows service? If yes, please give the details.
Thanks

When you also want the WebLogic Server as a service - Re: Installing Weblogic Admin Server as service - service won't start

After I do Node Manager nmConnect(...) I can no longer start a managed svr

I am running 10.3.2 on both windown and redhat
I have a domain with AdminServer and one managed server.
I can start AdminServer from the shell with startWebLogic.cmd
I can log into the web based 'console'
I can go to Environment -> Servers and start/shutdown the managed server.
If I use WLST and...
connect('user', 'pass', 't3://localhost:7001')
nmEnroll('fullPathToDomainDir')
I am still OK, I can still use the console to start and stop the managed server and I can so WLST start('managedSever')
I stop running the AdminServer from the shell - it is no longer running.
Now, I want to start the AdminServer with Node Manager, so (with WLST)...
nmConnect('user','pass','localhost','5556','domainName)
I get the error...
'Cannot connect to Node Manager: Access to domain 'domainname' for user 'user' denied
As suggested elsewhere, I go and edit nm_password.properties and change the hashed user/pass to
username=user
password=pass
I go back to WLST, now nmConnect works!!!
I can then do..
nmStart('AdminServer')
The AdminServer start, I go to the web console, and I try to start the managed server, I get...
'For server managedServer, the Node Manager associated with machine machineName is not reachable'
So it looks like the re-hashed password from nmConnect(...), while it works for WLST, it no longer works for the console.
Bottom line, I can get either get the console to start the managed server (if I do WLST connect(...) + nmEnroll(...)) or I can get WLST to start the servers (if I reset nm_password.properties and do nmConnect), but I can not get WLST to start the AdminServer and have the AdminSever console start the managed server.
I know for a fact that others have run into this, but in the threads I found, the thread stops before a soluton is posted.
Anyone know about this issue?
Regards

There are a couple of things you need to keep in mind:
-- There is one and only one valid username / passwrod for connecting to the node manager.
-- When you use nmEnroll, the username / password placed in the nm_password.properties file is taken from the admin server, hashed an placed in the nm_password file.
-- When you edit the nm_password.properties, and place the line "enter in username=user / password='pass',", in clear text, you have over ridden the U/P \thje admin server knows.
That is why you have a situation, oen of the two works but never both at the same time.
What you need to do is:
-- Log in to the WL Console.
-- in the Domain Tree, click at teh root level, which is the domain name.
-- Under the security tab, under advanced there is a node manager username / password.
-- Click on "Lock and edit", and change those to match what you are using through WLST.
-- Activate changes.
-- Just to make sure all is well, use nmEnroll to re enroll the node manager again , this way the nm_password.properties file will be set up correctly.
Now, both the WL Console should be able to talk to the node manager as well as nmConnect('user','pass','localhost','5556','domainName) would succeed.
Also, if you want to use node manager to start /servers, make sure you edit the file ( $WL_HOME/common/nodemanager/nodemanager.properties) and change the line
StartScriptEnabled=false
to
StartScriptEnabled=true
This will ensure all the proper class paths and properties etc needed are set up when using the node manager.
You would need to bounce the node manager for this change t take effect
Hope this helps.

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>

Starting Node Manager

Similar Messages

Maybe you are looking for