Unable to start Managed server from admin console using nodemanager

I changed the ip address and hostname of the server on which Weblogic Server 10.3.5 is running. After that I am unable to start the managed servers using Admin console. Is there any changes in the nodemanager configuration files which need to be done to start the managed servers from admin console.

Hi there,
Can you check the following configuration in Weblogic admin console ?
1- Check which listen address mentioned under the Machine configuration ( Environment > Machines > select appropriate nodemanager machine >Configuration > Node Manager ). If it is pointing to old host name, change it to new one.
2- Once you done with Step 1. Check whether the machine is reachable or not. ( Machine > [Your Machine] > Monitoring > status.
3- If still isuse persists.. Check the managed server startup log files ( for eg:- managedserver1.out under the path $DOMAIN_HOME\Servers\managedserver1\logs directory.
Thanks
Lakshman

Similar Messages

Error start managed server from admin console in SSL mode

I have configured Admin server, managed servers and node manager on the same physical server and commonly using a single SSL sertificate.
There is no problem to start node manager, admin server and managed server individually. But if I try to start managed server from the admin console then I am getting the following errors.
<Feb 22, 2005 11:02:26 AM CST> <Info> <[email protected]:6666> <Starting Server peoplesoft::PIA1 ...>
<Feb 22, 2005 11:02:26 AM CST> <Info> <NodeManager@xxxxxxxxxx:6666> <BaseProcessControl: saving process id of Weblogic Managed server 'PIA1', pid: 285390>
<Feb 22, 2005 11:02:35 AM CST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Classic VM Version 1.4.1 from IBM Corporation>
<Feb 22, 2005 11:02:36 AM CST> <Info> <Management> <BEA-141140> <The managed server is going to contact the admin server at http://xxxxxxxx:admin_server_portnumber to check if there exists a running admin server at this URL.>
<Feb 22, 2005 11:02:36 AM CST> <Info> <Configuration Management> <BEA-150017> <This server is being started as a dependent managed server.>
<Feb 22, 2005 11:02:36 AM CST> <Info> <Management> <BEA-141107> <Version: WebLogic Temporary Patch 8 CR174605 for PeopleSoft 09/09/2004 18:11:35
WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
WebLogic XMLX Module 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284 >
<Feb 22, 2005 11:02:37 AM CST> <Info> <Configuration Management> <BEA-150015> <Connecting to the administration server http://xxxxxxxxx.org:Admin_server_portnumber to retrieve the initial configuration.>
<Feb 22, 2005 11:02:45 AM CST> <Notice> <Log Management> <BEA-170019> <The server log file /home/xxxx/webserv/peoplesoft/PIA1/PIA1.log is opened. All server side log events will be written to this file.>
<Feb 22, 2005 11:03:01 AM CST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Feb 22, 2005 11:03:01 AM CST> <Warning> <Security> <BEA-090066> <Problem handling boot identity. The following exception was generated: java.lang.NullPointerException>
<Feb 22, 2005 11:03:10 AM CST> <Critical> <Security> <BEA-090174> <The trust keystore configuration specified on the command line or in boot.properties does not match the trust keystore configuration specified in config.xml.>
<Feb 22, 2005 11:03:10 AM CST> <Warning> <NodeManager> <BEA-300038> <The node manager is unable to monitor this server. Could not create an SSL connection to the node manager. Reason : null>
<Feb 22, 2005 11:03:10 AM CST> <Emergency> <WebLogicServer> <BEA-000342> <Unable to initialize the server: weblogic.management.configuration.ConfigurationException: Due to faulty SSL configuration, this server is unable to establish a connection to the node manager.>
The WebLogic Server did not start up properly.
Exception raised: 'weblogic.management.configuration.ConfigurationException: Due to faulty SSL configuration, this server is unable to establish a connection to the node manager.'
Reason: weblogic.management.configuration.ConfigurationException: Due to faulty SSL configuration, this server is unable to establish a connection to the node manager.
I am running everything on IBM UNIX server.
I appriciate your help.
Thanks & regards,
Laxman.

Hi
From the admin console ... Are you able to check the status of Node Manager ?
If yes ... please check the SSL configuration of managed servers ...
Check the domain administration port also.
Jin

Unable to start Managed servers from admin console

Hello!
We have a problem to start Managed Servers throw Node manager.
We get an error:
<Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Boot identity properties saved to "/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/data/nodemanager/boot.properties">
Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.ServerManager log
INFO: Boot identity properties saved to "/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/data/nodemanager/boot.properties"
<Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Startup configuration properties saved to "/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/data/nodemanager/startup.properties">
Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.ServerManager log
INFO: Startup configuration properties saved to "/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/data/nodemanager/startup.properties"
<Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Server error log also redirected to server log>
Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.LogFileRotationUtil log
INFO: Server error log also redirected to server log
<Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Starting WebLogic server with command line: /software/psoft/pt851/webserv/peoplesoft/bin/startManagedWebLogic.sh >
Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.ServerManager log
INFO: Starting WebLogic server with command line: /software/psoft/pt851/webserv/peoplesoft/bin/startManagedWebLogic.sh
<Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Working directory is '/software/psoft/pt851/webserv/peoplesoft'>
Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.ServerManager log
INFO: Working directory is '/software/psoft/pt851/webserv/peoplesoft'
<Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Rotated server output log to "/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/logs/PIA1.out00001">
Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.LogFileRotationUtil log
INFO: Rotated server output log to "/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/logs/PIA1.out00001"
<Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Server error log also redirected to server log>
Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.LogFileRotationUtil log
INFO: Server error log also redirected to server log
<Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Server output log file is '/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/logs/PIA1.out'>
Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.ServerManager log
INFO: Server output log file is '/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/logs/PIA1.out'
<Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Server failed during startup so will not be restarted>
Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.ServerManager log
INFO: Server failed during startup so will not be restarted
<Jan 26, 2012 2:17:54 PM> <WARNING> <Exception while starting server 'PIA1'>
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:662)
Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.Handler handleStart
WARNING: Exception while starting server 'PIA1'
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:662)
Additional information:
weblogic 10.3.3
PT8.51.11
Linux x86_64 RH5
When we starting Manged servers manualy, it's works fine.
Thank you.

Hello!
The problem is found.
We tried to startup managed server by running startManagedServer.sh script, but this script expecting to get parameters.
The NodeManager unable to send parameters to script that appears in nodemanager.properties file (StartScriptName).
So, I created a new script startPIA.sh, that calls to startManagedServer.sh and sends it 2 parameters:
./startManagedWebLogic.sh $SERVER_NAME $ADMIN_URL
Now, we can start and stop managed servers from admin console, BUT we still have an error in NodeManager:
<Jan 29, 2012 11:15:39 AM> <INFO> <peoplesoft> <PIA1> <Server failed during startup so will not be restarted>
Jan 29, 2012 11:15:39 AM weblogic.nodemanager.server.ServerManager log
INFO: Server failed during startup so will not be restarted
<Jan 29, 2012 11:15:39 AM> <WARNING> <Exception while starting server 'PIA1'>
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:662)
Jan 29, 2012 11:15:39 AM weblogic.nodemanager.server.Handler handleStart
WARNING: Exception while starting server 'PIA1'
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:662)
There are no errors in managed servers logs.
PIA1.out:
<Jan 29, 2012 11:15:38 AM> <INFO> <NodeManager> <Server output log file is '/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/logs/PIA1.out'>
Attempting to start WebLogic Server PIA1
No activity will be logged to this window.
Server activity will be logged to /software/psoft/pt851/webserv/peoplesoft/servers/PIA1/logs/PIA1_*
PID for WebLogic Server PIA1 is: 27018
<Jan 29, 2012 11:15:39 AM> <FINEST> <NodeManager> <Waiting for the process to die: 26847>
<Jan 29, 2012 11:15:39 AM> <INFO> <NodeManager> <Server failed during startup so will not be restarted>
<Jan 29, 2012 11:15:39 AM> <FINEST> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>
The status of managed server in admin console is RUNNING, but "Status of Last Action" is FAILED.
What can be the reason?
Thank you.

Problems starting managed server from admin console WL70 portal

I get the following exception when I try to start the managed server from admin server console. Both Admin server and managed server are on the same machine.

I get the following exception when I try to start the managed server from admin server console. Both Admin server and managed server are on the same machine.

Unable to start managed servers from Admin Console "FAILED_NOT_RESTARTABLE"

I recently installed WebLogic 10.3.5, JRockit, and ECM 11.1.1.5. I'm to the point where I am trying to get Nodemanager configured so I can stop/start managed servers through the admin console. I have the following listed in Environment > Servers:
AdminConsole - running
IBR_server1 - FAILED_NOT_RESTARTABLE
managedServer1 - FAILED_NOT_RESTARTABLE
UCM_server1 - FAILED_NOT_RESTARTABLE
I followed the tutorial at http://blogs.oracle.com/jamesbayer/entry/weblogic_nodemanager_quick_sta to get to the point where the AdminServer starts when the server reboots, so I think Nodemanager is working there. If I view Machines > Monitoring, it says Nodemanager "Reachable." However, when I go to restart IBR_server1, managedServer1, or UCM_server1, I get the FAILED_NOT_RESTARTABLE status. I am using the weblogic server's IP for the machine name/host because our DNS is still screwed up. Would that have any affect on this?
I'm completely unsure what to do now. The Nodemanager log shows:
INFO - <Loading domains file: E:\oracle\MIDDLE~1\WLSERV~1.3\common\nodemanager\nodemanager.domains>
WARNING - <Domains file not found: E:\oracle\MIDDLE~1\WLSERV~1.3\common\nodemanager\nodemanager.domains>
INFO - <Loading identity key store: FileName=E:/oracle/MIDDLE~1/WLSERV~1.3/server\lib\DemoIdentity.jks, Type=jks, PassPhraseUsed=true>
WARNING - <Node manager configuration properties file 'E:\oracle\MIDDLE~1\WLSERV~1.3\common\nodemanager\nodemanager.properties' not found. Using default settings.>
So I'm confused why it's saying the properties file and domains file are not found... I've checked and they exist at
E:\oracle\middleware\wlserver_10.3\common\nodemanager\nodemanager.properties
and
E:\oracle\middleware\wlserver_10.3\common\nodemanager\nodemanager.domains
The domains file contains
base_domain=e\:\\oracle\\middleware\\user_projects\\domains\\base_domain
Which is correct.
Any idea what I'm missing here? I can provide more detail if needed. Thank you.
EDIT: I should add that I can start the UCM and IBR managed servers using the start up scripts on the server, but that's not what I'm after. I want everything controlled through the AdminConsole and want to be sure that when the server reboots, all the managed servers come back up correctly.
Edited by: user5824683 on Oct 5, 2011 5:04 PM
Edited by: user5824683 on Oct 5, 2011 5:09 PM

I did a bit of digging, and it seems I have an issue with -Xnohup... I've verified this arugment exists in all of my managed servers properties files, yet it still bombs when I try to restart from the webLogic console. I should note that if I start fresh from the server, I can start all my manager servers using WLST nmStart().
starting weblogic with Java version:
java version "1.6.0_24"
Java(TM) SE Runtime Environment (build 1.6.0_24-b07)
Oracle JRockit(R) (build R28.1.3-11-141760-1.6.0_24-20110301-1430-windows-x86_64, compiled mode)
Starting WLS with line:
E:\java\JROCKI~1.1\bin\java -jrockit -Xms256m -Xmx512m -Dweblogic.Name=IBR_server1 -Djava.security.policy=E:\oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.policy -Dweblogic.system.BootIdentityFile=E:\oracle\middleware\user_projects\domains\base_domain\servers\IBR_server1\data\nodemanager\boot.properties -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.security.SSL.ignoreHostnameVerification=false -Dweblogic.ReverseDNSAllowed=false -Xnohup -Xverify:none -da -Dplatform.home=E:\oracle\MIDDLE~1\WLSERV~1.3 -Dwls.home=E:\oracle\MIDDLE~1\WLSERV~1.3\server -Dweblogic.home=E:\oracle\MIDDLE~1\WLSERV~1.3\server -Dcommon.components.home=E:\oracle\MIDDLE~1\ORACLE~1 -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Ddomain.home=e:\oracle\MIDDLE~1\USER_P~1\domains\BASE_D~1 -Djrockit.optfile=E:\oracle\MIDDLE~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrocket_optfile.txt -Doracle.server.config.dir=e:\oracle\MIDDLE~1\USER_P~1\domains\BASE_D~1\config\FMWCON~1\servers\IBR_server1 -Doracle.domain.config.dir=e:\oracle\MIDDLE~1\USER_P~1\domains\BASE_D~1\config\FMWCON~1 -Digf.arisidbeans.carmlloc=e:\oracle\MIDDLE~1\USER_P~1\domains\BASE_D~1\config\FMWCON~1\carml -Digf.arisidstack.home=e:\oracle\MIDDLE~1\USER_P~1\domains\BASE_D~1\config\FMWCON~1\arisidprovider -Doracle.security.jps.config=e:\oracle\MIDDLE~1\USER_P~1\domains\BASE_D~1\config\fmwconfig\jps-config.xml -Doracle.deployed.app.dir=e:\oracle\MIDDLE~1\USER_P~1\domains\BASE_D~1\servers\IBR_server1\tmp\_WL_user -Doracle.deployed.app.ext=\- -Dweblogic.alternateTypesDirectory=E:\oracle\MIDDLE~1\ORACLE~1\modules\oracle.ossoiap_11.1.1,E:\oracle\MIDDLE~1\ORACLE~1\modules\oracle.oamprovider_11.1.1 -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Dweblogic.jdbc.remoteEnabled=false -Ducm.oracle.home=E:\oracle\MIDDLE~1\ORACLE~2 -Dem.oracle.home=E:\oracle\middleware\oracle_common -Djava.awt.headless=true -Dweblogic.management.discover=false -Dweblogic.management.server=http://138.126.180.177:7001 -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=e:\oracle\MIDDLE~1\patch_wls1035\profiles\default\sysext_manifest_classpath weblogic.Server
Exception in thread "Main Thread" java.lang.NoClassDefFoundError: –Xnohup
Caused by: java.lang.ClassNotFoundException: –Xnohup
     at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
     at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:305)
     at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:246)
Could not find the main class: â€“Xnohup. Program will exit.
<Oct 6, 2011 12:38:13 PM> <FINEST> <NodeManager> <Waiting for the process to die: 4252>
<Oct 6, 2011 12:38:13 PM> <INFO> <NodeManager> <Server failed during startup so will not be restarted>
<Oct 6, 2011 12:38:13 PM> <FINEST> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>

Starting managed server from admin console

          Hi Anand Byrappagiri(Bea guy, I saw him on this group but can't remember),
          I did the same way as you said here but still getting following error.....Could you
          address me where I did a mistake
          Starting WebLogic Server ....
          Connecting to http://localhost:7001...
          <Mar 4, 2002 5:19:17 PM EST> <Notice> <WebLogicServer> <Starting WebLogic Managed
          Server "MyServer1" for domain "mydomain">
          <Mar 4, 2002 5:19:20 PM EST> <Emergency> <Server> <Unable to initialize the server:
          'Fatal initialization exception
          Throwable: java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
          Start server side stack trace:
          java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
          at weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
          at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
          at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
          at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
          at weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.java:164)
          at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
          at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
          at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
          at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          End server side stack trace
          java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
          ***************************************************************************Start
          server side stack trace:
          java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
          at weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
          at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
          at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
          at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
          at weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.java:164)
          at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
          at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
          at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
          at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          End server side stack trace
          <<no stack trace available>>
          '>
          The WebLogic Server did not start up properly.
          Exception raised: weblogic.management.configuration.ConfigurationException: connecting
          to http://localhost:7001/wl_management_internal2/Bootstrap - with nested exception:
          [java.net.ConnectException: Tried all: '1' addresses, but could not connect over
          HTTP to server: 'localhost', port: '7001']
          java.net.ConnectException: Tried all: '1' addresses, but could not connect over HTTP
          to server: 'localhost', port: '7001'
          at weblogic.net.http.HttpClient.openServer(HttpClient.java:203)
          at weblogic.net.http.HttpClient.openServer(HttpClient.java:254)
          at weblogic.net.http.HttpClient.<init>(HttpClient.java:117)
          at weblogic.net.http.HttpClient.New(HttpClient.java:149)
          at weblogic.net.http.HttpURLConnection.connect(HttpURLConnection.java:109)
          at weblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.java:279)
          at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:230)
          at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:990)
          at weblogic.management.Admin.initialize(Admin.java:320)
          at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:359)
          at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
          at weblogic.Server.main(Server.java:35)
          --------------- nested within: ------------------
          weblogic.management.configuration.ConfigurationException: connecting to http://localhost:7001/wl_management_internal2/Bootstrap
          - with nested exception:
          [java.net.ConnectException: Tried all: '1' addresses, but could not connect over
          HTTP to server: 'localhost', port: '7001']
          at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:1081)
          at weblogic.management.Admin.initialize(Admin.java:320)
          at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:359)
          at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
          at weblogic.Server.main(Server.java:35)
          Reason: Fatal initialization exception
          t weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          End server side stack trace
          <<no stack trace available>>
          Reason: Fatal initialization exception
          <Mar 4, 2002 5:37:12 PM EST> <Info> <[email protected]:5555> <WindowsProcessControl:
          online successfully invoked on server 'MyServer1', pid: 1892>


Change the "Listen Address" attribute of the admin server to be its machine
          name or IP address. I think you currently have it set to "localhost".
          Hopefully this should fix atleast one of the exceptions below.
          -- Anand
          "Janavi" <[email protected]> wrote in message
          news:[email protected]...
          >
          > Hi Anand Byrappagiri(Bea guy, I saw him on this group but can't remember),
          >
          > I did the same way as you said here but still getting following
          error.....Could you
          > address me where I did a mistake
          >
          >
          > __________________________________________
          > Starting WebLogic Server ....
          > Connecting to http://localhost:7001...
          >
          > <Mar 4, 2002 5:19:17 PM EST> <Notice> <WebLogicServer> <Starting WebLogic
          Managed
          > Server "MyServer1" for domain "mydomain">
          > <Mar 4, 2002 5:19:20 PM EST> <Emergency> <Server> <Unable to initialize
          the server:
          > 'Fatal initialization exception
          > Throwable: java.lang.ClassCastException:
          weblogic.security.acl.DefaultUserInfoImpl
          >
          >
          > Start server side stack trace:
          > java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
          > at
          weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
          > at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
          > at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
          > at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
          > at
          weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.jav
          a:164)
          >
          > at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
          > at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
          > at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
          > at
          weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
          > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          > End server side stack trace
          >
          > java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
          >
          >
          ***************************************************************************S
          tart
          > server side stack trace:
          > java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
          > at
          weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
          > at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
          > at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
          > at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
          > at
          weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.jav
          a:164)
          >
          > at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
          > at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
          > at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
          > at
          weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
          > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          > End server side stack trace
          >
          > <<no stack trace available>>
          > '>
          >
          > The WebLogic Server did not start up properly.
          > Exception raised:
          weblogic.management.configuration.ConfigurationException: connecting
          > to http://localhost:7001/wl_management_internal2/Bootstrap - with nested
          exception:
          >
          > [java.net.ConnectException: Tried all: '1' addresses, but could not
          connect over
          > HTTP to server: 'localhost', port: '7001']
          > java.net.ConnectException: Tried all: '1' addresses, but could not connect
          over HTTP
          > to server: 'localhost', port: '7001'
          > at weblogic.net.http.HttpClient.openServer(HttpClient.java:203)
          > at weblogic.net.http.HttpClient.openServer(HttpClient.java:254)
          > at weblogic.net.http.HttpClient.<init>(HttpClient.java:117)
          > at weblogic.net.http.HttpClient.New(HttpClient.java:149)
          > at weblogic.net.http.HttpURLConnection.connect(HttpURLConnection.java:109)
          > at
          weblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.java:27
          9)
          >
          > at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:230)
          > at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:990)
          > at weblogic.management.Admin.initialize(Admin.java:320)
          > at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:359)
          > at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
          > at weblogic.Server.main(Server.java:35)
          > --------------- nested within: ------------------
          > weblogic.management.configuration.ConfigurationException: connecting to
          http://localhost:7001/wl_management_internal2/Bootstrap
          > - with nested exception:
          > [java.net.ConnectException: Tried all: '1' addresses, but could not
          connect over
          > HTTP to server: 'localhost', port: '7001']
          > at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:1081)
          > at weblogic.management.Admin.initialize(Admin.java:320)
          > at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:359)
          > at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
          > at weblogic.Server.main(Server.java:35)
          > Reason: Fatal initialization exception
          >
          > t weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          > End server side stack trace
          >
          > <<no stack trace available>>
          > Reason: Fatal initialization exception
          >
          > <Mar 4, 2002 5:37:12 PM EST> <Info> <[email protected]:5555>
          <WindowsProcessControl:
          > online successfully invoked on server 'MyServer1', pid: 1892>
          > _______________________________________
          >

Starting Managed Server from Administration Console

Hi
I am new for SOA and fusion. Can anyone share the brief steps that are needed to start/stop a Managed Server from Admin Console.
I did a fresh install on RHEL5 and configure a domain. i was able to start the services from script which are created when creating a domain.
But when i assigned a Managed Server to a Node Manager and try starting the Managed server. It does not start and in the log i can see exceptions like below
Failed to invoke startup class "JPS Startup Class", java.lang.ClassNotFoundException: oracle.security.jps.wls.JpsWlsStartupClass
java.lang.ClassNotFoundException
Failed to invoke startup class "ODL-Startup", java.lang.ClassNotFoundException: oracle.core.ojdl.weblogic.ODLConfiguration
java.lang.ClassNotFoundException
I start the services in below order
Weblogic Server
node Manager
and
soa_server
Thanks
Hari

you must set to true the StartScriptEnabled property in nodemanager.properties

How to start managed server from admin server both running

I have an admin server on one machine and created a managed server on different
machine, I am not able to start managed server from either machine. When I used
the admin server machine to start the managed server remotely I got this message
Connecting to http://fkeita:7001...
<Jul 17, 2002 11:11:06 AM EDT> <Notice> <Security> <090082> <Security initializi
ng using realm myrealm.>
<Jul 17, 2002 11:11:06 AM EDT> <Notice> <WebLogicServer> <000328> <Starting WebL
ogic Managed Server "managedserver3" for domain "admindomain">
<Jul 17, 2002 11:11:28 AM EDT> <Emergency> <WebLogicServer> <000350> <Unable to
create a server socket on Channel Default for: BFINKELMAN/90.0.0.25, port: 8002.
java.net.BindException: Cannot assign requested address: JVM_Bind Perhaps the
a
ddress BFINKELMAN/90.0.0.25 is incorrect or another process is using port 8002.>
<Jul 17, 2002 11:11:29 AM EDT> <Emergency> <Security> <090085> <Server failed
to
bind to any port such that it is not reachable from the console.>
<Jul 17, 2002 11:11:29 AM EDT> <Emergency> <WebLogicServer> <000342> <Unable to
initialize the server: Fatal initialization exception>
When I tried to connect managed server from its machine to admin server (running
on separate machine ) I got this error
Starting WebLogic Server...
Connecting to http://fkeita:7001...
<Jul 17, 2002 11:15:18 AM EDT> <Notice> <Security> <090082> <Security initializi
ng using realm myrealm.>
<Jul 17, 2002 11:15:18 AM EDT> <Critical> <WebLogicServer> <000364> <Server fail
ed during initialization. Exception:java.lang.SecurityException: Authentication
for user system denied
java.lang.SecurityException: Authentication for user system denied
at weblogic.security.service.SecurityServiceManager.doBootAuthorization(
SecurityServiceManager.java:978)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
erviceManager.java:1116)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
at weblogic.Server.main(Server.java:31)
>
<Jul 17, 2002 11:15:18 AM EDT> <Emergency> <WebLogicServer> <000342> <Unable to
initialize the server: Fatal initialization exception
Throwable: java.lang.SecurityException: Authentication for user system denied
java.lang.SecurityException: Authentication for user system denied
at weblogic.security.service.SecurityServiceManager.doBootAuthorization(
SecurityServiceManager.java:978)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
erviceManager.java:1116)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
at weblogic.Server.main(Server.java:31)
>
The WebLogic Server did not start up properly.
Exception raised:
java.lang.SecurityException: Authentication for user system denied
at weblogic.security.service.SecurityServiceManager.doBootAuthorization(
SecurityServiceManager.java:978)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
erviceManager.java:1116)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
at weblogic.Server.main(Server.java:31)
Reason: Fatal initialization exception
Throwable: java.lang.SecurityException: Authentication for user system denied
java.lang.SecurityException: Authentication for user system denied
at weblogic.security.service.SecurityServiceManager.doBootAuthorization(
SecurityServiceManager.java:978)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
erviceManager.java:1116)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
at weblogic.Server.main(Server.java:31)
Thanks.

"fkeita" <[email protected]> wrote in message
news:[email protected]...
>
I have an admin server on one machine and created a managed server ondifferent
machine, I am not able to start managed server from either machine. When Iused
the admin server machine to start the managed server remotely I got thismessage
>
Connecting to http://fkeita:7001...
<Jul 17, 2002 11:11:06 AM EDT> <Notice> <Security> <090082> <Securityinitializi
ng using realm myrealm.>
<Jul 17, 2002 11:11:06 AM EDT> <Notice> <WebLogicServer> <000328><Starting WebL
ogic Managed Server "managedserver3" for domain "admindomain">
<Jul 17, 2002 11:11:28 AM EDT> <Emergency> <WebLogicServer> <000350><Unable to
create a server socket on Channel Default for: BFINKELMAN/90.0.0.25, port:8002.
java.net.BindException: Cannot assign requested address: JVM_Bind Perhapsthe
a
ddress BFINKELMAN/90.0.0.25 is incorrect or another process is using port8002.>
>
Try running netstat to see whether another process is actually running at
the given address/port.
Also check using ifconfig/ipconfig or directly checking /etc/hosts file of
the box to see whether the ips addreses are correct.
<Jul 17, 2002 11:11:29 AM EDT> <Emergency> <Security> <090085> <Serverfailed
to
bind to any port such that it is not reachable from the console.>
<Jul 17, 2002 11:11:29 AM EDT> <Emergency> <WebLogicServer> <000342><Unable to
initialize the server: Fatal initialization exception>
When I tried to connect managed server from its machine to admin server(running
on separate machine ) I got this error
Starting WebLogic Server...
Connecting to http://fkeita:7001...
<Jul 17, 2002 11:15:18 AM EDT> <Notice> <Security> <090082> <Securityinitializi
ng using realm myrealm.>
<Jul 17, 2002 11:15:18 AM EDT> <Critical> <WebLogicServer> <000364><Server fail
ed during initialization. Exception:java.lang.SecurityException:Authentication
for user system denied
java.lang.SecurityException: Authentication for user system denied
atweblogic.security.service.SecurityServiceManager.doBootAuthorization(
SecurityServiceManager.java:978)
atweblogic.security.service.SecurityServiceManager.initialize(SecurityS
erviceManager.java:1116)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
at weblogic.Server.main(Server.java:31)
>Seems to be some issue with security credentials.
Try running the manageed server directly (as sort of admin) by not passing
the admin server url and bringing it just like an admin server.
See if this works. If it works, then soemthing wrong in the way the admin
server is receiving the request/security credentials from managed server.
Also make sure both managed and admin servers are on the same patch/service
pack level.
-Sabha

How to start managed server from admin server both running on separate machines

          I have an admin server on one machine and created a managed server on different
          machine, I am not able to start managed server from either machine. When I used
          the admin server machine to start the managed server remotely I got this message
          Connecting to http://fkeita:7001...
          <Jul 17, 2002 11:11:06 AM EDT> <Notice> <Security> <090082> <Security initializi
          ng using realm myrealm.>
          <Jul 17, 2002 11:11:06 AM EDT> <Notice> <WebLogicServer> <000328> <Starting WebL
          ogic Managed Server "managedserver3" for domain "admindomain">
          <Jul 17, 2002 11:11:28 AM EDT> <Emergency> <WebLogicServer> <000350> <Unable to
          create a server socket on Channel Default for: BFINKELMAN/90.0.0.25, port: 8002.
          java.net.BindException: Cannot assign requested address: JVM_Bind Perhaps the
          a
          ddress BFINKELMAN/90.0.0.25 is incorrect or another process is using port 8002.>
          <Jul 17, 2002 11:11:29 AM EDT> <Emergency> <Security> <090085> <Server failed
          to
          bind to any port such that it is not reachable from the console.>
          <Jul 17, 2002 11:11:29 AM EDT> <Emergency> <WebLogicServer> <000342> <Unable to
          initialize the server: Fatal initialization exception>
          When I tried to connect managed server from its machine to admin server (running
          on separate machine ) I got this error
          Starting WebLogic Server...
          Connecting to http://fkeita:7001...
          <Jul 17, 2002 11:15:18 AM EDT> <Notice> <Security> <090082> <Security initializi
          ng using realm myrealm.>
          <Jul 17, 2002 11:15:18 AM EDT> <Critical> <WebLogicServer> <000364> <Server fail
          ed during initialization. Exception:java.lang.SecurityException: Authentication
          for user system denied
          java.lang.SecurityException: Authentication for user system denied
          at weblogic.security.service.SecurityServiceManager.doBootAuthorization(
          SecurityServiceManager.java:978)
          at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
          erviceManager.java:1116)
          at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
          at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
          at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
          at weblogic.Server.main(Server.java:31)
          >
          <Jul 17, 2002 11:15:18 AM EDT> <Emergency> <WebLogicServer> <000342> <Unable to
          initialize the server: Fatal initialization exception
          Throwable: java.lang.SecurityException: Authentication for user system denied
          java.lang.SecurityException: Authentication for user system denied
          at weblogic.security.service.SecurityServiceManager.doBootAuthorization(
          SecurityServiceManager.java:978)
          at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
          erviceManager.java:1116)
          at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
          at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
          at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
          at weblogic.Server.main(Server.java:31)
          >
          The WebLogic Server did not start up properly.
          Exception raised:
          java.lang.SecurityException: Authentication for user system denied
          at weblogic.security.service.SecurityServiceManager.doBootAuthorization(
          SecurityServiceManager.java:978)
          at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
          erviceManager.java:1116)
          at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
          at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
          at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
          at weblogic.Server.main(Server.java:31)
          Reason: Fatal initialization exception
          Throwable: java.lang.SecurityException: Authentication for user system denied
          java.lang.SecurityException: Authentication for user system denied
          at weblogic.security.service.SecurityServiceManager.doBootAuthorization(
          SecurityServiceManager.java:978)
          at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
          erviceManager.java:1116)
          at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
          at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
          at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
          at weblogic.Server.main(Server.java:31)
          Thanks.


          I used startmanagedweblogic managedserver1 http://fkeita:7001 to try to start managed
          server, but it did not work, and got error messages. Error messages are posted
          on my first posting.
          "pankaj" <[email protected]> wrote:
          >Use the startManagedWeblogic.cmd / .sh script to start your
          >Managed/Clustered servers
          >
          >
          >"fkeita" <[email protected]> wrote in message
          >news:[email protected]...
          >>
          >> I have an admin server on one machine and created a managed server
          >on
          >different
          >> machine, I am not able to start managed server from either machine.
          >When I
          >used
          >> the admin server machine to start the managed server remotely I got
          >this
          >message
          >>
          >> Connecting to http://fkeita:7001...
          >> <Jul 17, 2002 11:11:06 AM EDT> <Notice> <Security> <090082> <Security
          >initializi
          >> ng using realm myrealm.>
          >> <Jul 17, 2002 11:11:06 AM EDT> <Notice> <WebLogicServer> <000328>
          ><Starting WebL
          >> ogic Managed Server "managedserver3" for domain "admindomain">
          >> <Jul 17, 2002 11:11:28 AM EDT> <Emergency> <WebLogicServer> <000350>
          ><Unable to
          >> create a server socket on Channel Default for: BFINKELMAN/90.0.0.25,
          >port:
          >8002.
          >> java.net.BindException: Cannot assign requested address: JVM_Bind
          >Perhaps
          >the
          >> a
          >> ddress BFINKELMAN/90.0.0.25 is incorrect or another process is using
          >port
          >8002.>
          >>
          >> <Jul 17, 2002 11:11:29 AM EDT> <Emergency> <Security> <090085> <Server
          >failed
          >> to
          >> bind to any port such that it is not reachable from the console.>
          >> <Jul 17, 2002 11:11:29 AM EDT> <Emergency> <WebLogicServer> <000342>
          ><Unable to
          >> initialize the server: Fatal initialization exception>
          >>
          >> When I tried to connect managed server from its machine to admin server
          >(running
          >> on separate machine ) I got this error
          >>
          >> Starting WebLogic Server...
          >> Connecting to http://fkeita:7001...
          >> <Jul 17, 2002 11:15:18 AM EDT> <Notice> <Security> <090082> <Security
          >initializi
          >> ng using realm myrealm.>
          >> <Jul 17, 2002 11:15:18 AM EDT> <Critical> <WebLogicServer> <000364>
          ><Server fail
          >> ed during initialization. Exception:java.lang.SecurityException:
          >Authentication
          >> for user system denied
          >> java.lang.SecurityException: Authentication for user system denied
          >> at
          >weblogic.security.service.SecurityServiceManager.doBootAuthorization(
          >> SecurityServiceManager.java:978)
          >> at
          >weblogic.security.service.SecurityServiceManager.initialize(SecurityS
          >> erviceManager.java:1116)
          >> at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
          >> at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
          >> at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
          >> at weblogic.Server.main(Server.java:31)
          >> >
          >> <Jul 17, 2002 11:15:18 AM EDT> <Emergency> <WebLogicServer> <000342>
          ><Unable to
          >> initialize the server: Fatal initialization exception
          >> Throwable: java.lang.SecurityException: Authentication for user system
          >denied
          >> java.lang.SecurityException: Authentication for user system denied
          >> at
          >weblogic.security.service.SecurityServiceManager.doBootAuthorization(
          >> SecurityServiceManager.java:978)
          >> at
          >weblogic.security.service.SecurityServiceManager.initialize(SecurityS
          >> erviceManager.java:1116)
          >> at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
          >> at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
          >> at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
          >> at weblogic.Server.main(Server.java:31)
          >> >
          >>
          >***************************************************************************
          >> The WebLogic Server did not start up properly.
          >> Exception raised:
          >> java.lang.SecurityException: Authentication for user system denied
          >> at
          >weblogic.security.service.SecurityServiceManager.doBootAuthorization(
          >> SecurityServiceManager.java:978)
          >> at
          >weblogic.security.service.SecurityServiceManager.initialize(SecurityS
          >> erviceManager.java:1116)
          >> at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
          >> at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
          >> at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
          >> at weblogic.Server.main(Server.java:31)
          >> Reason: Fatal initialization exception
          >> Throwable: java.lang.SecurityException: Authentication for user system
          >denied
          >> java.lang.SecurityException: Authentication for user system denied
          >> at
          >weblogic.security.service.SecurityServiceManager.doBootAuthorization(
          >> SecurityServiceManager.java:978)
          >> at
          >weblogic.security.service.SecurityServiceManager.initialize(SecurityS
          >> erviceManager.java:1116)
          >> at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
          >> at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
          >> at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
          >> at weblogic.Server.main(Server.java:31)
          >>
          >> Thanks.
          >
          >

Error starting managed server through admin console

Hey,
I am trying to start the managed server through the admin console, but it gives fails and give errors in the log, below mention is the log file details:
####<2007-dec-18 kl 14:05 CET> <Error> <Security> <SESO-ODX251909> <ManagedServer_1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1197983149062> <BEA-090870> <The realm "myrealm" failed to be loaded: weblogic.security.service.SecurityServiceException: com.bea.common.engine.ServiceInitializationException: weblogic.security.spi.ProviderInitializationException: [Security:090730]Failed to verify credential mapper LDAP hierarchy
netscape.ldap.LDAPException: Server or network error (81)
     at netscape.ldap.LDAPConnThread.networkError(LDAPConnThread.java:768)
     at netscape.ldap.LDAPConnThread.run(LDAPConnThread.java:555)
     at java.lang.Thread.run(Thread.java:595)
weblogic.security.service.SecurityServiceException: com.bea.common.engine.ServiceInitializationException: weblogic.security.spi.ProviderInitializationException: [Security:090730]Failed to verify credential mapper LDAP hierarchy
netscape.ldap.LDAPException: Server or network error (81)
     at netscape.ldap.LDAPConnThread.networkError(LDAPConnThread.java:768)
     at netscape.ldap.LDAPConnThread.run(LDAPConnThread.java:555)
     at java.lang.Thread.run(Thread.java:595)
     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:469)
     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:822)
     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealms(CommonSecurityServiceManagerDelegateImpl.java:851)
     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1007)
     at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:854)
     at weblogic.security.SecurityService.start(SecurityService.java:141)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
com.bea.common.engine.ServiceInitializationException: weblogic.security.spi.ProviderInitializationException: [Security:090730]Failed to verify credential mapper LDAP hierarchy
netscape.ldap.LDAPException: Server or network error (81)
     at netscape.ldap.LDAPConnThread.networkError(LDAPConnThread.java:768)
     at netscape.ldap.LDAPConnThread.run(LDAPConnThread.java:555)
     at java.lang.Thread.run(Thread.java:595)
     at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:342)
     at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:292)
     at com.bea.common.engine.internal.ServiceEngineImpl.lookupService(ServiceEngineImpl.java:263)
     at com.bea.common.engine.internal.ServicesImpl.getService(ServicesImpl.java:71)
     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:461)
     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:822)
     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealms(CommonSecurityServiceManagerDelegateImpl.java:851)
     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1007)
     at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:854)
     at weblogic.security.SecurityService.start(SecurityService.java:141)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
weblogic.security.spi.ProviderInitializationException: [Security:090730]Failed to verify credential mapper LDAP hierarchy
netscape.ldap.LDAPException: Server or network error (81)
     at netscape.ldap.LDAPConnThread.networkError(LDAPConnThread.java:768)
     at netscape.ldap.LDAPConnThread.run(LDAPConnThread.java:555)
     at java.lang.Thread.run(Thread.java:595)
     at weblogic.security.providers.credentials.DefaultCredentialMapperLDAPHelper.getInstance(DefaultCredentialMapperLDAPHelper.java:115)
     at weblogic.security.providers.credentials.DefaultCredentialMapperProviderImpl.initialize(DefaultCredentialMapperProviderImpl.java:93)
     at com.bea.common.security.internal.legacy.service.SecurityProviderImpl.init(SecurityProviderImpl.java:53)
     at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:340)
     at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:292)
     at com.bea.common.engine.internal.ServiceEngineImpl.lookupService(ServiceEngineImpl.java:263)
     at com.bea.common.engine.internal.ServicesImpl.getService(ServicesImpl.java:71)
     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:461)
     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:822)
     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealms(CommonSecurityServiceManagerDelegateImpl.java:851)
     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1007)
     at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:854)
     at weblogic.security.SecurityService.start(SecurityService.java:141)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
>
####<2007-dec-18 kl 14:05 CET> <Critical> <WebLogicServer> <SESO-ODX251909> <ManagedServer_1> <Main Thread> <<WLS Kernel>> <> <> <1197983149109> <BEA-000362> <Server failed. Reason:
There are 1 nested errors:
weblogic.security.service.SecurityServiceRuntimeException: [Security:090399]Security Services Unavailable
     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:898)
     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1029)
     at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:854)
     at weblogic.security.SecurityService.start(SecurityService.java:141)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
I am using weblogic server 9.2 on windows. Node manager is working fine. i have tried installing weblogic server several times but it gives the same error each time i start a managed server. Kindly help.
Regards,
Alka

Can you start a managed server from the command line?
<Alka Parveen> wrote in message news:[email protected]...
Hey,
I am trying to start the managed server through the admin console, but it
gives fails and give errors in the log, below mention is the log file
details:
####<2007-dec-18 kl 14:05 CET> <Error> <Security> <SESO-ODX251909>
<ManagedServer_1> <[ACTIVE] ExecuteThread: '0' for queue:
'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <>
<1197983149062> <BEA-090870> <The realm "myrealm" failed to be loaded:
weblogic.security.service.SecurityServiceException:
com.bea.common.engine.ServiceInitializationException:
weblogic.security.spi.ProviderInitializationException:
[Security:090730]Failed to verify credential mapper LDAP hierarchy
netscape.ldap.LDAPException: Server or network error (81)
at netscape.ldap.LDAPConnThread.networkError(LDAPConnThread.java:768)
at netscape.ldap.LDAPConnThread.run(LDAPConnThread.java:555)
at java.lang.Thread.run(Thread.java:595)
weblogic.security.service.SecurityServiceException:
com.bea.common.engine.ServiceInitializationException:
weblogic.security.spi.ProviderInitializationException:
[Security:090730]Failed to verify credential mapper LDAP hierarchy
netscape.ldap.LDAPException: Server or network error (81)
at netscape.ldap.LDAPConnThread.networkError(LDAPConnThread.java:768)
at netscape.ldap.LDAPConnThread.run(LDAPConnThread.java:555)
at java.lang.Thread.run(Thread.java:595)
at
weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:469)
at
weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:822)
at
weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealms(CommonSecurityServiceManagerDelegateImpl.java:851)
at
weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1007)
at
weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:854)
at weblogic.security.SecurityService.start(SecurityService.java:141)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
com.bea.common.engine.ServiceInitializationException:
weblogic.security.spi.ProviderInitializationException:
[Security:090730]Failed to verify credential mapper LDAP hierarchy
netscape.ldap.LDAPException: Server or network error (81)
at netscape.ldap.LDAPConnThread.networkError(LDAPConnThread.java:768)
at netscape.ldap.LDAPConnThread.run(LDAPConnThread.java:555)
at java.lang.Thread.run(Thread.java:595)
at
com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:342)
at
com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:292)
at
com.bea.common.engine.internal.ServiceEngineImpl.lookupService(ServiceEngineImpl.java:263)
at
com.bea.common.engine.internal.ServicesImpl.getService(ServicesImpl.java:71)
at
weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:461)
at
weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:822)
at
weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealms(CommonSecurityServiceManagerDelegateImpl.java:851)
at
weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1007)
at
weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:854)
at weblogic.security.SecurityService.start(SecurityService.java:141)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
weblogic.security.spi.ProviderInitializationException:
[Security:090730]Failed to verify credential mapper LDAP hierarchy
netscape.ldap.LDAPException: Server or network error (81)
at netscape.ldap.LDAPConnThread.networkError(LDAPConnThread.java:768)
at netscape.ldap.LDAPConnThread.run(LDAPConnThread.java:555)
at java.lang.Thread.run(Thread.java:595)
at
weblogic.security.providers.credentials.DefaultCredentialMapperLDAPHelper.getInstance(DefaultCredentialMapperLDAPHelper.java:115)
at
weblogic.security.providers.credentials.DefaultCredentialMapperProviderImpl.initialize(DefaultCredentialMapperProviderImpl.java:93)
at
com.bea.common.security.internal.legacy.service.SecurityProviderImpl.init(SecurityProviderImpl.java:53)
at
com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:340)
at
com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:292)
at
com.bea.common.engine.internal.ServiceEngineImpl.lookupService(ServiceEngineImpl.java:263)
at
com.bea.common.engine.internal.ServicesImpl.getService(ServicesImpl.java:71)
at
weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:461)
at
weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:822)
at
weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealms(CommonSecurityServiceManagerDelegateImpl.java:851)
at
weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1007)
at
weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:854)
at weblogic.security.SecurityService.start(SecurityService.java:141)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
>
####<2007-dec-18 kl 14:05 CET> <Critical> <WebLogicServer> <SESO-ODX251909>
<ManagedServer_1> <Main Thread> <<WLS Kernel>> <> <> <1197983149109>
<BEA-000362> <Server failed. Reason:
There are 1 nested errors:
weblogic.security.service.SecurityServiceRuntimeException:
[Security:090399]Security Services Unavailable
at
weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:898)
at
weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1029)
at
weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:854)
at weblogic.security.SecurityService.start(SecurityService.java:141)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
I am using weblogic server 9.2 on windows. Node manager is working fine. i
have tried installing weblogic server several times but it gives the same
error each time i start a managed server. Kindly help.
Regards,
Alka

Start Managed Server from Admine clonsole FAILED_NOT_RESTARTABLE

when trying to start the managed server Managed-Server-01 from the WLS Admin Console the managed server status becomes <FAILED_NOT_RESTARTABLE> and not coming up:
Managed servers logs:
/usr/local/bea/user_projects/domains/eShop/servers/Managed-Server-01/logs:
3/data/nodemanager/boot.properties -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.security.SSL.ignoreHostnameVerification=false -Dweblogic.ReverseDNSAllowed=false>
<Sep 13, 2011 6:15:46 PM> <Debug> <NodeManager> <Environment: SERVER_NAME=Managed-Server-03>
<Sep 13, 2011 6:15:46 PM> <Info> <NodeManager> <Working directory is "/usr/local/bea/user_projects/domains/eShop">
<Sep 13, 2011 6:15:46 PM> <Info> <NodeManager> <Server output log file is "/usr/local/bea/user_projects/domains/eShop/servers/Managed-Server-03/logs/Managed-Server-03.out">
/usr/local/bea/user_projects/domains/eShop/bin/startWebLogic.sh: uname: not found
/usr/local/bea/user_projects/domains/eShop/bin/startWebLogic.sh: grep: not found
/usr/local/bea/user_projects/domains/eShop/bin/startWebLogic.sh: uname: not found
/usr/local/bea/user_projects/domains/eShop/bin/startWebLogic.sh: grep: not found
/usr/local/bea/user_projects/domains/eShop/bin/startWebLogic.sh: uname: not found
/usr/local/bea/user_projects/domains/eShop/bin/startWebLogic.sh: grep: not found
/usr/local/bea/user_projects/domains/eShop/bin/startWebLogic.sh: grep: not found
/usr/local/bea/user_projects/domains/eShop/bin/startWebLogic.sh: uname: not found
/usr/local/bea/user_projects/domains/eShop/bin/startWebLogic.sh: expr: not found
/usr/local/bea/user_projects/domains/eShop/bin/startWebLogic.sh: test: argument expected
<Sep 13, 2011 6:15:47 PM> <Debug> <NodeManager> <Waiting for the process to die: 1226>
<Sep 13, 2011 6:15:47 PM> <Info> <NodeManager> <Server failed during startup so will not be restarted>
<Sep 13, 2011 6:15:47 PM> <Debug> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>
--=--
Node Manager log during Managed-Server-01 start from WLS Admin Console shows:
15:46 PM> <Info> <eShop> <Managed-Server-03> <Working directory is "/usr/local/bea/user_projects/domains/eShop">
<Sep 13, 2011 6:15:46 PM> <Info> <eShop> <Managed-Server-03> <Server output log file is "/usr/local/bea/user_projects/domains/eShop/servers/Managed-Server-03/logs/Managed-Server
-03.out">
<Sep 13, 2011 6:15:47 PM> <Info> <eShop> <Managed-Server-03> <Server failed during startup so will not be restarted>
<Sep 13, 2011 6:15:47 PM> <Warning> <Exception while starting server 'Managed-Server-03': 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:6
Note:
The installation of WLS done using Root.
We can start/stop MS using conventional ways.
Cheers,

although i am not an expert,
but i am very confident that any WLS you install,
it can be configured like i tried it,
First Environment-----Machine
Add a machine by giving a name
Second Environment------Server
Add a server giving a sever name
Third Environment----machine
Add the server to the machine from the tab server
Fourth Environment-------server
Add A a SSL Port to the Sever and save
Click Start Server and every thing goes well
Thanks
Edited by: kashif, pakistan on Sep 14, 2011 4:09 AM

Configure Managed Server from Admin Console - Java arguments

Hi There;
I am configuring a managed server from the admin console and the one item that me up is when I add the following into the Arguments sections:
-Djava.protocol.handler.pkgs=oracle.mds.net.protocol'|'oracle.fabric.common.classloaderurl.handler'|'oracle.fabric.common.uddiurl.handler'|'oracle.bpm.io.fs.protocol.
Note The command line script used double quotes (") but the console gave an error - Arguments may not contain '"' This sounded reasonable so I switched the double quotes to single quotes.
Switching to single quotes allowed me to bypass the error.
The managed server fails when I start it from the console:
Error message:
oracle.fabric.common.classloaderurl.handler ' is not recognized as an internal or external command, operable program or batch file.- it is like it ignores the values after the single quotes and fials.
How can I configure this parameter?
note: I am running weblogic 10.3.6 on widows 2008. it is a SOA Managed Server I am trying to setup to run from the Admin Console.
J

Try leaving out the quotes
-Djava.protocol.handler.pkgs=oracle.mds.net.protocol|oracle.fabric.common.classloaderurl.handler|oracle.fabric.common.uddiurl.handler|oracle.bpm.io.fs.protocol
See also the documentation: URL (Java Platform SE 7 ) "interpreted as a list of packages separated by a vertical slash character |"

Starting managed servers from admin console vs. command line

Will the arguments I enter in the "Arguments" section of the "Server start" admin console page also be used if I start the managed server from the command line using startManagedWeblogic.sh?
And conversely, will changes I make to the scripts take effect when I start the server from the admin console?

No,
the arguments that you set thru Console GUI are effective when Node manager start your server.
Ammar Sajdi

Managed servers are started/stopped from admin console using NodeManager

Hi,
I have weblogic cluster and it has 4 managed servers on two different machines with each machine having 2 managed servers.
I have node manager setup on the two machines. I use admin console to start/stop managed servers.
Now there is a requirement to add TIBCO lib and bin path to weblogic managed server path. I have added the entries in LD_LIBARY_PATH but on starting the server using admin console the TIBCO lib/bin paths are not appended to weblogic server path.
I noticed that in nodemanager.properties we have set StartScriptEnabled=false and so it doesn't use startWebLogic.sh,which internally use other configuration files.
I'm wondering as how to add these entries in WebLogic server path. Also, how the nodemanager is able to start the managed server without using startWebLogic.sh script.
In general, what happens when I click the start button in Admin console to start the managed servers which calls NodeManager internally.
Your inputs are highly appreciated.
Thanks in advance.
BR,
Ajmal

Hi Ajmal,
For your issue there are two solution's as shown below:
Solution-1
You can add the TIBCO lib with the complete path where the TIBCO lib file is kept from console in Class Path
Console Path:
Servers > Configuration > Server Start
However this has to be done with all the managed serves.
Solution-2
If you don't want the burden to add the TIBCO lib files on every server from console then you can add the same lib files in the classpath of startWebLogic.sh and in nodemanager.properties we have set StartScriptEnabled=true. This will make sure that all the settings would be taken from the startWebLogic.sh.
This way whenever you start any of you managed servers from console it would pick up that lib files.
In both the solution you can check the managed servers *.out* files that the lib files would be present in there classpath.
Hope this would help you.
Regards,
Ravish Mody

How to start managed server from console?

Hi,
After several unsuccesful attempts to start a managed server from admin console,
which starts fine by script and stops by console, can somebody please mail me
what to enter in the "remote start" tab!
The documentation is very uncertain if the path have to be absolute or not. It
seems to be a problem with the classpath.
thanks in advance
Kai

The ServerStart element should look like below (WLS6.1sp1+). Using absolute
path is definitely OK. Please provide us more info if you still have this
problem such as files under WL_HOME\NodeManagerLogs\<mgr'ed servername>
especially config and <mgr'ed server name>_error.log
<ServerStart Arguments="-mx64m -ms64m" BeaHome="d:\bea"
ClassPath="d:\bea\load1;d:\bea\load1\lib\weblogic_sp.jar;d:\bea\load1\lib\we
blogic.jar"
Name="Server-1005280911753"
OutputFile="d:\bea\load1\config\NodeManagerClientLogs\managed1\startserver_1
005280991998.log"
RootDirectory="d:\bea\load1"
SecurityPolicyFile="d:/bea/load1/lib/weblogic.policy"/>
"Kai" <[email protected]> wrote in message news:3bea490f$[email protected]..
>
Hi,
After several unsuccesful attempts to start a managed server from adminconsole,
which starts fine by script and stops by console, can somebody please mailme
what to enter in the "remote start" tab!
The documentation is very uncertain if the path have to be absolute ornot. It
seems to be a problem with the classpath.
thanks in advance
Kai

Unable to start Managed server from admin console using nodemanager

Similar Messages

Maybe you are looking for