How to start managed servers simultaneously using WLST?

Hi folks,
I am trying to write a simple script to provide a simple way to bounce my env, I am pretty much done. However, my script now starts (and stops) the managed servers sequentially which is not what I wanted.
I am wondering if there is a way to start (and stop) the managed servers within a domain in parallel as I can definitely do that using Admin Console.
I do have an idea in mind:
Write a simple python script to start/stop a single managed server, then use another shell script to trigger the python script in background mode.
But I think this approach is really ugly, and am wondering if there is a native way to do that in WLST.
Thanks for your repose in advance.

This does not solve my problem, what I am trying to do is to being a an indefinite about of managed servers at the same time, not all the managed servers.
For example, suppose I have 5 clusters in a domain, and there are 3 servers in each cluster. I might want to bring up all the major servers first at the same time,
which mean to bring up one server in each cluster at the same time.
Please help.

Similar Messages

How nodemanager starts managed servers?

Hello All,
I'm facing strange issue with weblogic server. Currently i'm using WLS 8.1 SP 4 on solaris 9 server.
To start weblogic i have customize the script such that when server goes on reboot it will pick the startweblogic.sh script from /opt/bin and start the weblogic. Where as in startweblogic.sh i have mentioned -
NMLOG=/u001/wls8/bea/user_projects/prodDomain/logs/optbin/nodemanager.log; export WL8NMLOG
ADMINLOG=/u001/wls8/bea/user_projects/prodDomain/logs/optbin/adminserver.log; export WL8ADMINLOG
CLUSTERLOG=/u001/wls8/bea/user_projects/prodDomain/logs/optbin/cluster.log; export WL8CLUSTERLOG
cd /u001/wls8/bea/weblogic81/server/bin/
su weblogic -c "./startNodeManager.sh >> $NMLOG 2>&1" &
sleep 60
cd /u001/wls8/bea/user_projects/prodDomain/
su weblogic -c "./startadminserver.sh >> $ADMINLOG 2>&1" &
sleep 1200
cd /u001/wls8/bea/user_projects/prodDomain/
su weblogic -c "./startcluster.sh >> $CLUSTERLOG 2>&1" &
Though the script works as expected till adminserver is UP/Running, but script doesn't wait for 1200 secs. to start cluster. Somehow nodemanager starts the managed servers immediately after the adminserver is UP.
I have checked the nodemanager.properties file, there is nothing such mentioned. Also, from console i have unchecked the option of AutoStart for both managed servers.
Can anyone tell me how nodemanager starts the managed servers automatically??
Thanks,
HK

can you please tell me what is this .startCluster.sh script.
is it your custom script?
And the idea i have in my mind is that after
cd /u001/wls8/bea/weblogic81/server/bin/
su weblogic -c "./startNodeManager.sh >> $NMLOG 2>&1" &
sleep 60
cd /u001/wls8/bea/user_projects/prodDomain/
su weblogic -c "./startadminserver.sh >> $ADMINLOG 2>&1" &
sleep 1200
you can give the command to start the individual managed servers like:
cd /u001/wls8/bea/user_projects/prodDomain/
su weblogic -c "./startManagedWebLogic.sh <arguments> >> $CLUSTERLOG 2>&1" &
I think this way it will work....

How to start managed servers in parallel?

Hello everyone,
I am developing a wlst script that would start all managed servers on a particular machine (machine_name should be provided) from the admin server side. The script works fine. However, since there were some domains that have 25+ managed servers for a single machine, it takes some time to start all of them in sequence. Is there a way to trigger a start command for each of the managed servers that I need to start just like what the node manager does when i start them through admin console? Something like triggering parallel processes running on background. Here is my code snippet:
                #It focuses only on all managed servers defined within the listen address provided
                if (server_listenaddress == managed_server) and (server_name != admin_name):
                        if (execute_command == "start"):
                                print 'About to start',server_name,'on',server_listenaddress,'...'
                                print
                                try:
                                        start(server_name)
                                        print
                                        state(server_name,'Server')
                                        print
                                        nmDisconnect()
                                except WLSTException:
                                        print 'Server instance',server_name,'could not be started. Skipping this server..'
                                        print
                                        state(server_name,'Server')
                        else:
                                print 'About to stop',server_name,'on',server_listenaddress,'...'
                                print
                                try:
                                        shutdown(server_name,force='true')
                                        print
                                        state(server_name,'Server')
                                        print
                                except WLSTException:
                                        print 'Server instance',server_name,'could not be stopped. Skipping this server..'
                                        print
                                        state(server_name,'Server')
                elif (server_name == admin_name):
                        #It skips to restart the admin server since this script it only to restart managed servers.
                        print 'Server',server_name,'is the admin server. Skipping...'
                        print
                else:
                        print 'Managed server',server_name,'is not configured with',managed_server,'listen address. Skipping this server..'
Thanks in advance for all your help!!
regards,
Rustan

Works perfectly, thanks!!!
In summary, I just modified this line:
start(server_name)
and changed it to:
start(server_name, block='false')
In Admin Console, it is set to false but in WLST, it is defaulted to true so we need to explicitly set it to false.
"Oracle Fusion Middleware Oracle WebLogic Scripting Tool, block is always set to true."

How to start Managed Servers in Cluster in background

I am new to weblogic. I have two managed servers each on two boxes, i need to start these managed servers in background.
Thanks

I got this error while starting Managed Server2 on machine A. Managed Server was started using the same command line with clean start. I am using JDK1.5.0_14
eg., nohup ./startManagedWebLogic.sh Managed-mn2 http://localhost:7001 &
<Dec 12, 2008 2:17:11 PM EST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
[thread 43 also had an error]#
# An unexpected error has been detected by HotSpot Virtual Machine:
# SIGBUS
Exception (0xa)in thread " at pc=0xff390c50CompilerThread0, pid=21379" , tid=1java.lang.OutO
fMemoryError: requested
34416#
bytes# Java VM: Java HotSpot(TM) Server VM (1.5.0_14-b03 mixed mode)
for # Problematic frame:
Chunk::new# . Out of swap space?
C [libc_psr.so.1+0xc50]
An error report file with more information is saved as hs_err_pid21425.log
Exception in thread "CompilerThread0" java.lang.OutOfMemoryError: requested 34416 bytes for Chunk::new. Out of swap space?
Edited by: user10705269 on Dec 12, 2008 11:42 AM

Starting managed Servers under WLS 8.1 using Operator Role

Hi,
we've configured a user who is acting in the default 'Operator' role.
He can shutdown a managed server using the admin console, but when
trying to restart that managed server via node manager he fails with an exception.
weblogic.management.NoAccessRuntimeException: Access not allowed for subject:
principals=[oper, Operators], on ResourceType: Server Action: write, Target: ExpectedToRun
According to the documentation http://edocs.bea.com/wls/docs81/secwlres/secroles.html
this role should be allowed to start managed servers.
-- What are we doing wrong ? --
Cheers,
Robert

I believe this is a known problem, please contact BEA support for a patch.
Thanks,
-satya
Robert Akolk wrote:
Hi,
we've configured a user who is acting in the default 'Operator' role.
He can shutdown a managed server using the admin console, but when
trying to restart that managed server via node manager he fails with an exception.
weblogic.management.NoAccessRuntimeException: Access not allowed for subject:
principals=[oper, Operators], on ResourceType: Server Action: write, Target: ExpectedToRun
According to the documentation http://edocs.bea.com/wls/docs81/secwlres/secroles.html
this role should be allowed to start managed servers.
-- What are we doing wrong ? --
Cheers,
Robert

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 servers

Hi,
Environment: WebLogic 6.1 SP2, JDK1.3.1, Solaris 8
1. How to start the managed servers using NodeManager from the command line? Already
NodeManager configured and able to start managed servers from the Admin Console.
So from the console start/stop/kill managed servers is fine. From the command
line, if I use `weblogic.Server` to start managed server it's not using the node
manager.
2. In the `java weblogic.nodemanager.NodeManager help`, option `starttemplate`
defaults to `nodemanager.sh`. Any details on this please ?
3. Each time we start managed server with Node Manager, it writes the output to
the new file `OutputFile=./config/NodeManagerlogs/<server>/startserver-<XXXX.log`.
From the documentation it looks like we can set logs directory
`-Dweblogic.nodemanager.savedLogsDirectory=path`, however is it possible to specify
the log file name also?
4. Where is the location of the java applications `System.out`, if the managed
server is started with NodeManager. If the managed server is started with `weblogic.Server`
the `System.out` are printed to the console. So this enables us to redirect to
a file.
thanks
Sarva Meduri

I think you can configure the NodeMgr to start ManagedServers instead of having the
Windows Service start the servers. Basically you configure NodeMgr as a Windows Service
and then let NM take care of starting other servers. I believe you have to set
ManagedServer's HostsMigratableServices attribute to false to enable NM start the server.
By default it is true.
prasen
Gerardo Rojas wrote:
Hi:
I have been trying to configure my WebLogic environment to start the managed servers
in a domain automatically when the machine is rebooted. I have done some testing
with Node Manager but, as I understood, Node Manager only restarts a server if
it was started using Node Manager and the server crashes or fails. On the other
hand, if the server is installed as a Windows service, it will be started at reboot
time, but not when the server (not the machine) crashes or fails. So, both solutions
seems to be uncompatible. Is it right?? Is it possible to have both benefits,
that is, to get the managed servers started at boot time (as done by Windows services)
and restarted each time they fail (as done by Node Manager)?
Thanks,
Gerardo

How to start Managed server in weblogic10gr3....please help me out...

hi...
How to start Managed server in weblogic10gr3....please help me out...

Hi
You can start Managed server in admin console ->servers
or you can start the managed servers in Independent mode(without admin server)
by using the startManagedWebLogic.cmd/>startManagedWebLogic.sh (this requires weblogic authentication).
Hope this helps
thanks

Multicast Error When Starting Managed Servers

Environment: HP-UX 11i, Weblogic 8.1 SP1.
          We're getting the following error when we start managed servers in our clustered environment:
          <Feb 24, 2004 6:33:12 PM CST> <Error> <Cluster> <BEA-000116> <Failed to join cluster PDICluster at address 2
          37.0.0.1 due to: java.net.SocketException: Can't assign requested address.
          java.net.SocketException: Can't assign requested address
          at java.net.PlainDatagramSocketImpl.join(Native Method)
          at java.net.PlainDatagramSocketImpl.join(PlainDatagramSocketImpl.java:134)
          at java.net.MulticastSocket.joinGroup(MulticastSocket.java:274)
          at weblogic.cluster.FragmentSocket.initializeMulticastSocket(FragmentSocket.java:92)
          at weblogic.cluster.FragmentSocket.start(FragmentSocket.java:109)
          at weblogic.cluster.MulticastManager.startListening(MulticastManager.java:164)
          at weblogic.cluster.ClusterCommunicationService.initialize(ClusterCommunicationService.java:52)
          at weblogic.t3.srvr.T3Srvr.initializeHere(T3Srvr.java:922)
          at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:664)
          at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:342)
          at weblogic.Server.main(Server.java:32)
          >
          We also get the same error when we try the util.multicastTest application. So far, we've done the following things to troubleshoot this:
          1) Different multicast addresses/ports;
          2) The util.multicastTest app.
          3) We're researching whether or machine or network may be causing this, but since the admin. server and managed servers are running on the same server, I don't see how the network could be causing this.
          Can anyone give me any ideas as to what might be going wrong? We've set this up on other machines before with the same OS and same version of Weblogic. So I'm at a loss at the moment as to what might be going wrong.
          Thanks in advance for any help...
          Brian


Environment: HP-UX 11i, Weblogic 8.1 SP1.
          We're getting the following error when we start managed servers in our clustered environment:
          <Feb 24, 2004 6:33:12 PM CST> <Error> <Cluster> <BEA-000116> <Failed to join cluster PDICluster at address 2
          37.0.0.1 due to: java.net.SocketException: Can't assign requested address.
          java.net.SocketException: Can't assign requested address
          at java.net.PlainDatagramSocketImpl.join(Native Method)
          at java.net.PlainDatagramSocketImpl.join(PlainDatagramSocketImpl.java:134)
          at java.net.MulticastSocket.joinGroup(MulticastSocket.java:274)
          at weblogic.cluster.FragmentSocket.initializeMulticastSocket(FragmentSocket.java:92)
          at weblogic.cluster.FragmentSocket.start(FragmentSocket.java:109)
          at weblogic.cluster.MulticastManager.startListening(MulticastManager.java:164)
          at weblogic.cluster.ClusterCommunicationService.initialize(ClusterCommunicationService.java:52)
          at weblogic.t3.srvr.T3Srvr.initializeHere(T3Srvr.java:922)
          at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:664)
          at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:342)
          at weblogic.Server.main(Server.java:32)
          >
          We also get the same error when we try the util.multicastTest application. So far, we've done the following things to troubleshoot this:
          1) Different multicast addresses/ports;
          2) The util.multicastTest app.
          3) We're researching whether or machine or network may be causing this, but since the admin. server and managed servers are running on the same server, I don't see how the network could be causing this.
          Can anyone give me any ideas as to what might be going wrong? We've set this up on other machines before with the same OS and same version of Weblogic. So I'm at a loss at the moment as to what might be going wrong.
          Thanks in advance for any help...
          Brian

How to find the NodeManager Status using WLST

Hi All,
can anyone please let me know how to find the nodemanager status using wlst, the nodemanager status whether it is 'Reachable' or not.
Thank you.

Hi Bob,
As James pointed, we faced the same. We could not find any mbean to find the Node Manager Stat that we can monitor from Weblogic console.
The best I can suggest, use the below WLST command after connecting to 'Node Manager:
nm()
Currently connected to Node Manager to monitor the domain xxxdomain.Grep for 'connected to Node Manager to monitor the domain <Your WLS domain name>' and if successfull, your node manager is UP & Connected other wise not 'Reachable'.
Regards,
qumar

How to set XPoweredByHeaderLevel to NONE using wlst

How to set XPoweredByHeaderLevel to NONE using wlst (by default the value is SHORT).
I mean, I have created a domain using wlst.
Now I want to set XPoweredByHeaderLevel of WebAppContainerMBean to NONE using wlst.
It will be helpful if a sample python(Jython) script is provided.
Please help.

Here is a quick Jython example of how to do what you want:
#assuming you already have correct imports for wlst module
#connect to the AdminServer using proper credentials and host information
wlst.connect(username, password, host_info)
#extract domain name
domainName = wlst.domainName
#start an edit session and navigate to the WebAppContainerMBean
wlst.edit()
wlst.cd("/WebAppContainer/" + domainName)
wlst.startEdit()
#set the value of the XPoweredByHeaderLevel attribute to "NONE"
wlst.cmo.setXPoweredByHeaderLevel("NONE")
#activate the change
wlst.activate()

Problem in starting Managed Servers

I am getting probelm in starting managed servers in WL 6.0,i tried with giving
password while starting
[wlerror.txt]

I think your port number are conflicting.
Check your port number for both the server
"Shridhar" <[email protected]> wrote:
>
>
>
I am getting probelm in starting managed servers in WL 6.0,i tried with
giving
password while starting

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.

Node Manager starting managed servers under different users

Hi all,
I have multiple domains running on the same server.
Is it possible to get node manager to start managed servers from different domains under different users?
Default is the user under which node manager was started originally.
Thanks
Arnaud

Oracle documentation is still in confussion state for Unix platform nodemanager.
NodeManager Admin Guide had chapter 3 for General configuration of nodemanger. Chapter 5 is for script based nodemanager.
In chapter 5 there is clear way defined for " Starting a node manger for Unix machine".
chapter 3 is mess there is clear-cut direction to reach the remote startup of servers.
Why we have so many types of nodemanager for connect. howbout start them?
Can someone expert in Oracle WebLogic please respond to this.
*Nodemanagers are NOT meant for multiuser development env.
They are defined for production env and for HA, FailOver.*
Edited by: PavanBhavanishekhar on Jan 6, 2010 9:10 PM

How to create users and groups using WLST Offline with Weblogic 8.1.4

How to create users and groups using WLST Offline with Weblogic 8.1.4?
Any ideas?

Hi this is how i created a user using WLST Offline?
cd('/Security/' + domainName)
# Delete the default user name weblogic
# incase you want to remove the defualt user weblogic
delete('weblogic','User')
# Creating a new user defined
create(userName, 'User')
# Setting the password of the user you created.
cd ('/Security/' + domainName + '/User/' + userName)
cmo.setPassword(password)
Regards
Makenzo

How to start managed servers simultaneously using WLST?

Similar Messages

Maybe you are looking for