Node manager runs on 5559 port instead of 5556

As I found out recently, even though in Silent.xml NODEMGR_PORT value was "5556", installed as windows service, it runs on 5559. For example, if I specify it in Admin console, I get "Undefined" node manager status. But if I use 5559, I get "Reachable".
Can anybody tell me why it is so?

Should be declared in your nodemanager properties in wl_home\wlserver_10.3\common\nodemanager . You can change it here and then uninstall and reinstall the nodemanager service.

Similar Messages

Running OSB and SOA Suite as Windows Services? Node Manager

Hi,
Based on our current hardware configuration, we need to deploy our SOA Managed Server and Admin Server on the same machine as our OSB. Currently for development we just start the servers using the start scripts and keep a window open for them (3 of them: 1 - admin, 1 - soa_server1, and 1 - OSB.) We want to be able to run these as services and allow the admins to log out of the box. It seems like the Node Manager would allow us to do that but can we configure our Windows server to have a Node Manager running for the OSB and another for the SOA stuff on the same box? Do we even need to do that? Can we have a single Node Manager manage all three on port 5556?
I hope this makes sense. Thanks in advance for any quick responses.
Jeremy

Definitely you can (should) have a single node manager. You may refer below links -
http://blogs.oracle.com/jamesbayer/2010/01/weblogic_nodemanager_quick_sta.html
WLS 10.3.2 Adminserver startup failed when trying to run as Windows Service
Regards,
Anuj

Can I run more than one Node Manager per machine?

Hia,
We have a situation in our project where we need to run different domains on a Solaris machine in different java modes.
Say Domain1 should be running in 32bit version of java where as Domain2 should be running in 64bit mode due to the nature of testing currently going on in different domains.
We could successfully get the two domains running in different java modes in parallel by modifying the start scripts to decide which Sud data model to start the servers based on certain parms. However, the pain here is with the Node Manager.
My understanding is that there should be one Node Manager running per machine for all the domains running on that machine. So when ever I have to run a domain in a java mode different to that of what Node Manager is running on, I had to kill the node manager and start it in the same version that I want to start the other servers in since Node Manager uses its starting parms internally to start the Managed Servers (Note: there is no issue in running the Admin Server regardless of the node manager mode as expected).
Can somebody advise me if there is any way to get around this hassle?
I want to know if we can run more than one node manager per machine.
Below are the details of my env.
Weblogic Server 10.3
Solaris 10 SPARC 64 bit (SunOS 5.10 Generic_142900-14 sun4v sparc)
java version "1.6.0_20"
Hope all this makes sense...
Cheers,
Satish.
Edited by: apsnaidu on Mar 15, 2013 3:29 PM

You can run as many node manager as you want in a particular machine.
At the time of starting the node manager you need to pass hostname & Port.
This will start the nodemanager on different ports of a machine.
sh startNodeManager.sh <hostname> <port>
eg:- sh startNodeManager.sh dev_machine_01 5556
sh startNodeManager.sh dev_machine_01 5557
sh startNodeManager.sh dev_machine_01 5558
After starting your node manager in different ports you need to change machine details from admin console.

Multiple Node Manager Instances and servers sharing the same domain home.

Hi,
We have a 8 man server weblogic cluster spread over 4 machines. Each machine runs 2 man servers each.
Each of the machine is configured to run node manager.
We use shared storage accessible to all 8 servers and all 8 man servers have the same domain_home.
Lets call it W:/domain
Now the problem we are facing is that node manager running on 1 machine is trying to access/control a managed server on a different machine after a machine restart.
eg.
ManServer1 Home : W:/domain/servers/server1 ====> runs on Machine 1
ManServer2Home : W:/domain/servers/server2 ====> runs on Machine 2
Problem is node manager on machine 1 is trying to restart man server 2. The path W:/domain/servers/server2 is accessible to Machine 1.
After a restart, what I assume is happening is that the nodemanager is checking all servers folder under Domain_Home/Servers and trying to restart servers instead of restarting only those which it should start. The config file has the server and machine assignment done correctly. Is there a way to make this configuration towork. Or do we need to create different domain_home's for different man servers like
Domain_Home for MS1: W:/domain/MS1 ( Server Home would be : W:/domain/MS1/servers/MS1)
Domain_Home for MS2: W:/domain/MS2 ( Server Home would be : W:/domain/MS2/servers/MS2)
Regards,
Atheek
Edited by: atheek1 on 03-May-2010 00:27

Thanks - We have tried putting 2 dad entries in file, but not sure how you connect. You only specify a port number, so how does it connect that to a db???

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.

Stop managed server without node manager and admin server

What are the commonly used ways to stop managed Weblogic server without node manager running and without administration server running?
(I have only one solution: on the managed server startup dump process ID to a file, and then when I want to stop it, send a signal to this process ID and kill JVM. But it seems not very clean way.)
(The managed server is started when both node manager and admin server are down, and I provide boot.properties of admin server to the managed server to start.)
UPDATED: And I don't want to start neither admin server, nor node manager even temporarily.
Edited by: user12163080 on Jun 24, 2010 4:40 AM

Hai,
I read the Oracle weblogic wlst script document without Admin server you cannot connect the managed server through the WLST script. see the below lines
"The start command starts Managed Servers or clusters in a domain using Node Manager.
To use the start command, WLST must be connected to a running Administration Server.
To start Managed Servers without requiring a running Administration Server, use the
nmStart command with WLST connected to Node Manager."
"You shut down a server to which WLST is connected by entering the shutdown command
without any arguments.
When connected to a Managed Server instance, you only use the shutdown command to shut
down the Managed Server instance to which WLST is connected; you cannot shut down another
server while connected to a Managed Server instance.
WLST uses Node Manager to shut down a Managed Server. When shutting down a Managed
Server, Node Manager must be running.
In the event of an error, the command returns"
They are two option if you are using adminserver then we can stop the any Managed server.
The option is if you are using the nodemanager without admin server we can stop the any Managed server.
The last final solution to kill the particular Managed server pid.
Regards,
S.vinoth babu

Admin console cannot connect to Node Manager

I've just installed WLS 10.3.2, configured a domain (TEST), a machine (PHILO), a server (TEST1), and a node manager running on PHILO. I logged onto PHILO, ran "startNodeManager.sh", no problems, it says it's listening on 5556, like I configured. However, when I attempt to start the server TEST2 (associated with machine PHILO and in the domain TEST) from the admin gui I get the following error:
For server TEST1, the Node Manager associated with machine PHILO is not reachable.
All of the servers selected are currently in a state which is incompatible with this operation or are not associated with a running Node Manager or you are not authorized to perform the action requested. No action will be performed.
If I log onto the local server where the admin node is running, I can telnet to PHILO 5556, so why can't the node manager be reached?

I have a similar problem trying to start my Managed server. I get the following error:
Unexpected response from server: § ☻ ☻☻F
weblogic.management.scripting.ScriptException: Error occured while performing st
art : Server with name geo-apps failed to be started
at weblogic.management.scripting.ExceptionHandler.handleException(Except
ionHandler.java:48)
at weblogic.management.scripting.LifeCycleHandler.startServer(LifeCycleH
andler.java:501)
at weblogic.management.scripting.WLScriptContext.start(WLScriptContext.j
ava:477)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.python.core.PyReflectedFunction.__call__(Unknown Source)
at org.python.core.PyMethod.__call__(Unknown Source)
at org.python.core.PyObject.__call__(Unknown Source)
at org.python.core.PyObject.invoke(Unknown Source)
at org.python.pycode._pyx16.start$80(<iostream>:1270)
at org.python.pycode._pyx16.call_function(<iostream>)
at org.python.core.PyTableCode.call(Unknown Source)
at org.python.core.PyTableCode.call(Unknown Source)
at org.python.core.PyTableCode.call(Unknown Source)
at org.python.core.PyFunction.__call__(Unknown Source)
at org.python.pycode._pyx15.f$0(D:\product\Oracle\11.1.1\Middleware\user
projects\domains\basedomain\ServerStart.py:4)
at org.python.pycode._pyx15.call_function(D:\product\Oracle\11.1.1\Middl
eware\user_projects\domains\base_domain\ServerStart.py)
at org.python.core.PyTableCode.call(Unknown Source)
at org.python.core.PyCode.call(Unknown Source)
at org.python.core.Py.runCode(Unknown Source)
at org.python.util.PythonInterpreter.execfile(Unknown Source)
at weblogic.management.scripting.WLST.main(WLST.java:131)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at weblogic.WLST.main(WLST.java:29)
Problem invoking WLST - Traceback (innermost last):
File "D:\product\Oracle\11.1.1\Middleware\user_projects\domains\base_domain\Se
rverStart.py", line 4, in ?
File "<iostream>", line 1280, in start
File "<iostream>", line 1744, in raiseWLSTException
WLSTException: Error occured while performing start : Error starting the server
: Error occured while performing start : Server with name geo-apps failed to be
started
Use dumpStack() to view the full stacktrace

Starting manged server without node manager

Hi All
I know that we can start managed servers from admin console but for that we have to have node manager on that machine running.
But I want to know,if I dont want to use node manager,can i start some how managed servers from admin console.That is if my node manager is not running,can i start the managed servers using admin console.
Please let me know if it is possible or not.
Thanks in advance.
DJ

Without the node manager running, you cannot start the managed servers from the admin console.
There are other options you can use to start the managed servers though, which i guess you might be aware of.
Just in case you don't, it's nicely documented by Atul @ http://onlineappsdba.com/index.php/2008/08/03/oracle-weblogic-server-startupshutdown/
Hope this helps.
Thanks,
Patrick

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

WLST without Node Manager

We are not using node manager to start|stop the servers. But we are monitoring the servers, getting the runtime values of the servers remotely using WLST. Can we also use WLST to automatically start and stop the managed servers without node manager, when the server status is failed. Also, can we do that remotely?
Please advise me where I can find the documentation on it.

No, you cannot start and stop servers via WLST without a Node Manager running.
-satya
BEA Blog: http://dev2dev.bea.com/blog/sghattu/

WLST - Failing to run nmConnect() command / node manager becomes unreachabl

Hello guys,
I'm facing some issues to setup some configurations of one application that I've deployed on weblogic 10.3.3.0.
One of the needed steps in order to configure this applications is open the WLST in offline mode an run 2 commands:
*/bea/mytrack/wlserver_10.3/common/bin/wlst.sh*
Then I try to connect in the nodemanager:
* wls:/offline> nmConnect('admin30800','weblogic_password',port='30801',domainName='track30800')*
The following error returns:
Connecting to Node Manager ...
<Jul 13, 2011 2:23:45 PM CDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=thawte Primary Root CA - G3,OU=(c) 2008 thawte\, Inc. - For authorized use only,OU=Certification Services Division,O=thawte\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Jul 13, 2011 2:23:45 PM CDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 3,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Jul 13, 2011 2:23:45 PM CDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 2,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Jul 13, 2011 2:23:45 PM CDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=GlobalSign,O=GlobalSign,OU=GlobalSign Root CA - R3". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Jul 13, 2011 2:23:45 PM CDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "OU=Security Communication RootCA2,O=SECOM Trust Systems CO.\,LTD.,C=JP". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Jul 13, 2011 2:23:45 PM CDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=VeriSign Universal Root Certification Authority,OU=(c) 2008 VeriSign\, Inc. - For authorized use only,OU=VeriSign Trust Network,O=VeriSign\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Jul 13, 2011 2:23:45 PM CDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=KEYNECTIS ROOT CA,OU=ROOT,O=KEYNECTIS,C=FR". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Jul 13, 2011 2:23:45 PM CDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=GeoTrust Primary Certification Authority - G3,OU=(c) 2008 GeoTrust Inc. - For authorized use only,O=GeoTrust Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
Traceback (innermost last):
File "<console>", line 1, in ?
File "<iostream>", line 123, in nmConnect
File "<iostream>", line 646, in raiseWLSTException
WLSTException: Error occured while performing nmConnect : Cannot connect to Node Manager. : Access to domain 'track30800' for user 'admin30800' denied
I did some research and found this thread here: http://kr.forums.oracle.com/forums/thread.jspa?threadID=788163
that solves the initial problem, however after I performed the nmConnect and a storeUserConfig() command, I exit() from the WLST and restart the node manager with success, the node manager becomes unreachable.
I used the WL adm console and access -> appdomain -> environments -> machines -> monitoring -> node manager status to check the unreachable status.
Thanks in advance,
Davinod

Nice it worked!!
However when I try to start the servers controlled by this node manager I got this error:
-sh-3.2$ <Jul 14, 2011 8:43:42 AM> <WARNING> <Exception while starting server 'track30800-01'>
java.io.FileNotFoundException: /u01/track30800/user_projects/domains/track30800/servers/track30800-01/data/nodemanager/boot.properties (Permission denied)
at java.io.FileOutputStream.open(Native Method)
at java.io.FileOutputStream.<init>(FileOutputStream.java:179)
at java.io.FileOutputStream.<init>(FileOutputStream.java:131)
at weblogic.nodemanager.server.ServerManager.saveBootIdentity(ServerManager.java:495)
at weblogic.nodemanager.server.ServerManager.saveStartupConfig(ServerManager.java:438)
at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:301)
at weblogic.nodemanager.server.Handler.handleStart(Handler.java:567)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:118)
at weblogic.nodemanager.server.Handler.run(Handler.java:70)
at java.lang.Thread.run(Thread.java:619)
Jul 14, 2011 8:43:42 AM weblogic.nodemanager.server.Handler handleStart
WARNING: Exception while starting server 'track30800-01'
java.io.FileNotFoundException: /u01/track30800/user_projects/domains/track30800/servers/track30800-01/data/nodemanager/boot.properties (Permission denied)
at java.io.FileOutputStream.open(Native Method)
at java.io.FileOutputStream.<init>(FileOutputStream.java:179)
at java.io.FileOutputStream.<init>(FileOutputStream.java:131)
at weblogic.nodemanager.server.ServerManager.saveBootIdentity(ServerManager.java:495)
at weblogic.nodemanager.server.ServerManager.saveStartupConfig(ServerManager.java:438)
at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:301)
at weblogic.nodemanager.server.Handler.handleStart(Handler.java:567)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:118)
at weblogic.nodemanager.server.Handler.run(Handler.java:70)
at java.lang.Thread.run(Thread.java:619)
<Jul 14, 2011 8:43:42 AM CDT> <Error> <NodeManager> <BEA-300048> <Unable to start the server track30800-01 : Exception while starting server 'track30800-01'>
Edited: Should I change the chmod for 777 for this file in order to check that all users have write permission?
-rw-r--r-- 1 root iluser 193 Jun 24 11:05 boot.properties
Did I miss a step?
Thanks,
Davinod
Edited by: davinod on Jul 14, 2011 6:58 AM

How to configure Node manager on Linux on ssl port

Hi,
I have installed SOA BPM 11.1.1.3 on linux with ssl enabled. I am trying to configure Node Manager but it's not working.
Here are the steps I did to configure.
1. Created a machine
2. Added managed servers to the machine i.e. soa,bam
3. Enroll domain using nmEnroll using
cd $BEA_HOME/user_projects/domains/<domain_name>/bin/
. setDomainEnv.sh
java weblogic.WLST
wls> connect(’weblogic’,'weblogic1’, ‘t3://mymachine.mydomain:7001’)
wls> nmEnroll(’$BEA_HOME/user_projects/domains/<domain_name>’, ‘$BEA_HOME/wlserver_<version>/common/nodemanager’)
here 7001 is the admin server non-ssl port but when I try 7002 ssl port it doesn't connect. But I need to enroll it on ssl port as I have ssl enabled.
4. reset the node manager user/password same as weblogic console
5. started the node manager using $WL_HOME\server\bin\startNodeManager.sh
But when I log back into console and try to start my manage server it gives the following error
SEVERE: java.io.FileNotFoundException: /usr3/app/oracle/Middleware/user_projects/domains/wcbpm_domain/./config/jps-config.xml (No such file or directory)
<Aug 6, 2010 5:30:16 PM EDT> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: The dynamic loading of the OPSS java security policy provider class oracle.security.jps.internal.policystore.JavaPolicyProvider failed due to problem inside OPSS java security policy provider. Exception was thrown when loading or setting the JPSS policy provider. Enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: JPS-01538: The default policy provider was not found.I did not add my Admin server to be part of the machine.
Any help if I am missing anything or doing anything wrong.
Thanks

Hi,
Do I need to add Admin Server also part of the Machine where I added bam,soa servers. I tried again following the steps but gets the below error again. Appreciate if someone can list the steps as the docs are a bit vague:
<Aug 6, 2010 6:14:01 PM> <INFO> <wcbpm_domain> <bam_server1> <Starting WebLogic server with command line: /usr3/app/oracle/Middleware/user_projects/domains/wcbpm_domain/bin/startWebLogic.sh >
Aug 6, 2010 6:14:01 PM weblogic.nodemanager.server.ServerManager log
INFO: Starting WebLogic server with command line: /usr3/app/oracle/Middleware/user_projects/domains/wcbpm_domain/bin/startWebLogic.sh
<Aug 6, 2010 6:14:01 PM> <INFO> <wcbpm_domain> <bam_server1> <Working directory is '/usr3/app/oracle/Middleware/user_projects/domains/wcbpm_domain'>
Aug 6, 2010 6:14:01 PM weblogic.nodemanager.server.ServerManager log
'/usr3/app/oracle/Middleware/user_projects/domains/wcbpm_domain/servers/bam_server1/logs/bam_server1.out'
<Aug 6, 2010 6:14:02 PM> <INFO> <wcbpm_domain> <bam_server1> <Server failed during startup so will not be restarted>
Aug 6, 2010 6:14:02 PM weblogic.nodemanager.server.ServerManager log
INFO: Server failed during startup so will not be restarted
<Aug 6, 2010 6:14:02 PM> <WARNING> <Exception while starting server 'bam_server1'>
java.io.IOException: Server failed to start up. See server output log for more details.
        at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:331)
        at weblogic.nodemanager.server.Handler.handleStart(Handler.java:567)
        at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:118)
        at weblogic.nodemanager.server.Handler.run(Handler.java:70)
        at java.lang.Thread.run(Thread.java:619)
[WARN ] Use of -Djrockit.optfile is deprecated and discouraged.
[WARN ] Use of -Djrockit.optfile is deprecated and discouraged.
Unknown option or illegal argument: -XX:+UseParallelGC.
Please check for incorrect spelling or review documentation of startup options.
Could not create the Java virtual machine.
<Aug 6, 2010 6:14:02 PM> <FINEST> <NodeManager> <Waiting for the process to die: 590>
<Aug 6, 2010 6:14:02 PM> <INFO> <NodeManager> <Server failed during startup so will not be restarted>
<Aug 6, 2010 6:14:02 PM> <FINEST> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>Don't know if I hve missed any steps in node manager configuration.
Thanks

Domain wide administration port and node manager

I need a little help understanding how to properly configure the domain-wide
administration port in a clustered domain using node manager. After I enabled
the port in my domain, node manager will no longer start the managed servers
running on the same box as the domain's admin server. I don't have problems
starting remote managed servers. I see the problem but I don't know how to
fix it.
<Error> <Configuration Management> <BEA-150019> <The address provided to
get to the admin server (https://<host>@port) resolves to a managed server
local address (host@port) rather than a remote address as expected, or the
local managed server port might already be in use if you have setup domain
wide admin port, please check the configuration and correct the problem.>
The host I'm specifying is the host of my admin server, the port is the domain-wide
administration port. I don't get this error when starting my remote managed
servers, only the managed servers running on the same box as the admin server.
Grant

Cause might The managed server was given a URL to boot from that resolves to a managed server address. If the managed server is running on the same machine as the admin server, this can be caused by a failure to specify a unique admin port.
Inspect the address:port provided to the managed server from which to boot. This address should be changed to reference the admin server rather than resolving to a managed server. If the managed server is running on the same machine as the admin server, you must differentiate them by providing a unique port number.
Now we log a clear message that prints something like ,
The address provided to get to the admin server x.x.x.x resolves to a m
anaged server local address x.x.x.x:nnnn rather than a remote address as
expected, or the local managed server port might already be in use if you
have setup domain wide admin port, please check the configuration and correct
the problem.
Regards,
Prasanna Yalam

How to run OPatch against Node Manager from the admin server

How to run OPatch against Node Manager from the admin server

Hello,
I'm not sure what you meant by Opatch against nodemanager.You can check the below document about how to apply patches using Opatch
Oracle Fusion Middleware Patching with OPatch - 12c (12.1.2)
Refer the section " Common OPatch Commands When Patching an Oracle Fusion Middleware Oracle home"
/MR

Using node manager to make adminserver run as windows service.....

using:
Oracle weblogic server 11g
Oracle forms and Reports 11g
jdk 1.7.0
jre 7
i found these articles and they helped me start my forms and reports as serices but when i try to make my adminserver a windows service, it does not get past the step for Using the "nmStart" command to start a server.
the 2 articles:
http://docs.oracle.com/cd/E15586_01/web.1111/e13715/manage_servers.htm
http://wlsjavatips.blogspot.com/2009/09/how-to-install-node-manager-as-windows.html
This is what i get when i try to start it after it successfully connects:
http://i1281.photobucket.com/albums/a516/eortiz10/output_zps25fbf82f.png
* It connects to node manager but it does not start. It does start normally if i use "weblogicstart.cmd" but i would like the adminserver to start autmatically when server is on. can u explain/help in anyway.
Do i have to start the adminserver regularly then configure through there?

Was a resolution found for this?
We are having the same issue and investigating...
Thanks!

Node manager runs on 5559 port instead of 5556

Similar Messages

Maybe you are looking for