Starting managed servers after rebooting

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

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

Similar Messages

  • 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

  • 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

  • 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

    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.

  • 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
              

  • 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

  • Have NodeManager start managed servers on machine reboot

    Is there any way to have the Node Manager start all the managed servers belonging to a domain when a server reboots?
    I know I could create a separate Windows service for each of the managed servers I want running when the server comes on-line, or I could do some fancy scripting at start-up to connect to the Node Manager and have it start the managed servers.
    But I was hoping there would be a more elegant way of having the NM start them when it comes on-line.
    Ideas appreciated,
    dmac.

    Hi Dmac,
    To achieve this in Windows, you must consider the following WLS Components:
    1. Node Manager
    2. Admin Server
    3. Managed Server
    Node Manager
    For Node Manager, if you want the component to start automatically on boot up, your best option is to create a Windows Service. You may have selected the option to create a service for Node Manager during the WebLogic Server installation. Use Start -> Run -> services.msc from the Start menu to load the Windows Services Manager. If there is no service for Node Manager, use the following steps to create one.
    Create a Windows service for Node Manager:
    1. WL_HOME\server\bin\installNodeMgrSvc.cmd
    2. Verify in Windows Services that a service was created.
    Admin Server
    For the Admin Server, you can also create a Windows Service. Here are the steps for doing so:
    Create a Windows service for the Admin Server
    1. Create a text file named %MIDDLEWARE_HOME%\user_projects\domains\<domain name>\servers\AdminServer\security\boot.properties. Add the following lines:
    username=weblogic
    password=<the weblogic username password>
    2. Create a command script called installAdmServer_Service.cmd which you will want to make sure has lines like:
    SETLOCAL
    set DOMAIN_NAME=<your wls domain>
    set USERDOMAIN_HOME=<path to domain> # e.g., C:\middleware\FMW11g\user_projects\domains\ClassicDomain
    set SERVER_NAME=AdminServer
    set PRODUCTION_MODE=true
    cd %USERDOMAIN_HOME%
    call %USERDOMAIN_HOME%\bin\setDomainEnv.cmd
    call "<your middleware home>\wlserver_10.3\server\bin\installSvc.cmd"
    ENDLOCAL
    3. For troubleshooting/debugging purposes it is helpful to redirect standard out and error to a text file. Although most information is captured in the AdminServer server log files, you will not see all standard out and error when the server is started via a MS Windows Service (unlike when you start an AdminServer from the command prompt using startWebLogic.cmd). To redirect standard out to a text file, backup and edit installSvc.cmd and change the line at the bottom of the file so it includes the -log parameter, e.g.
    "%WL_HOME%\server\bin\beasvc" -install -svcname:"%DOMAIN_NAME%_%SERVER_NAME%" -javahome:"%JAVA_HOME%" -execdir:"%USERDOMAIN_HOME%" -extrapath:"%WL_HOME%\server\bin" -password:"%WLS_PW%" -cmdline:%CMDLINE% -log:"<your middleware home>\user_projects\domains\<your wls domain name>\servers\AdminServer\logs\AdminServer-stdout.txt"
    4. Now run "installAdmServer_Service.cmd." The Service should be installed. It will have a name like "beasvc %DOMAIN_NAME%_%SERVER_NAME%" (e.g. beasvc ClassicDomain_AdminServer). The Service "Startup Type" will be "Automatic." Start the Service. The Service will come back fairly quickly to say it is started. The actual time taken for the admin server to start and reach a state of 'RUNNING' will be longer - perhaps two or three minutes. The state of the server can be monitored by reviewing the stdout txt file.
    Managed Server
    For the Managed Server, you can also create a Windows Service. Here are the steps for doing so:
    Create a Windows service for the Managed Server (using wls_forms as an example)
    1. Create a text file named %MIDDLEWARE_HOME%\user_projects\domains\<domain name>\servers\WLS_FORMS\security\boot.properties. Add the following lines:
    username=weblogic
    password=<the weblogic username password e.g manager11g>
    2. Create a command script called installWLSFORMS_Service.cmd which has lines like
    SETLOCAL
    set DOMAIN_NAME=<your wls domain>
    set USERDOMAIN_HOME=<path to domain> # e.g. C:\middleware\FMW11g\user_projects\domains\ClassicDomain
    set SERVER_NAME=WLS_FORMS
    set PRODUCTION_MODE=true
    set ADMIN_URL=http://mymachine.mycompany.com:7001
    cd %USERDOMAIN_HOME%
    call %USERDOMAIN_HOME%\bin\setDomainEnv.cmd
    call "<your middleware home>\wlserver_10.3\server\bin\installSvc.cmd"
    ENDLOCAL
    NOTES:
    a. The ADMIN_URL value should reference the AdminServer hostname and listen port.
    b. The SERVER_NAME value is case sensitive. For example, if you are creating a MS Windows service for a different managed server such as 'wls_ods1' then the value needs to match the case of the server name otherwise the startup of the server via the MS Windows service will fail.
    c. Be careful that there are no trailing spaces after each line in the command file - trailing spaces will cause the managed server to fail at startup. For example a trailing space in the ADMIN_URL value will result in the error
    <19-Jan-2010 11:37:58 o'clock GMT> <Error> <EmbeddedLDAP> <BEA-171524> <Cannot determine the Listen address for the Admin server
    3. Now run "installWLSFORMS_Service.cmd." The Service should be installed, it will have a name like "beasvc %DOMAIN_NAME%_%SERVER_NAME%" (e.g. beasvc ClassicDomain_WLS_FORMS). The Service "Startup Type" will be "Automatic." Start the Service. The Service will come back fairly quickly to say it is started. The actual time taken for the managed server to start and reach a state of 'RUNNING' will be longer - perhaps two or three minutes. The state of the server can be monitored by reviewing the stdout txt file.
    Configuring the Windows service to restart upon failure
    As with any Windows Service, it is possible to configure the service to restart itself upon failure. These are standard options available when configuring a Windows Service in the context of Windows Services Manager. However, it is important to understand that Windows Services Manager only monitors the JVM process. If the JVM process fails (shuts down), then Windows Services Manager will attempt to restart it. But there are some scenarios where the Admin Server or Managed Server may go into an unhealthy or failed state but the JVM is still running. The Windows Service will not know to restart the process in these cases, whereas if the Admin Server and Managed Server had been started using Node Manager, Node Manager would recognize such a state and restart the process accordingly. So it may be desirable to start Node Manager with a Windows Service and then start the Admin Server and Managed Servers with Node Manager to take advantage of this monitoring feature. Below you will find one such example of how to do this.
    Example of starting the Admin Server and a Managed Server using Node Manager
    1. Create a batch script similar to this:
    Myscript.cmd
    call D:\Product\Oracle\Middleware\user_projects\domains\base_domain\bin\setDomainEnv.cmd
    java weblogic.WLST D:\Product\Oracle\Middleware\user_projects\domains\base_domain\ServerStart.py
    2. Create a Python script similar to this:
    ServerStart.py
    nmConnect('weblogic', 'welcome1', '192.168.0.101', '5556', 'base_domain','D:\Product\Oracle\MIDDLE~1\USER_P~1\domains\BASE_D~1','ssl')
    nmStart('AdminServer')
    connect ('weblogic','welcome1','t3://192.168.0.101:7001')
    nmstart('myserver','Server','t3://192.168.0.101:7002')
    If you want this to happen automatically on boot up, you can run the script (myscript.cmd) from the Windows Scheduler. You must configure the scheduler to run the script on system startup. This will execute the script without requiring an interactive login to Windows (unattended).
    Some Additional Information to Remember
    The startup.properties file for the Admin and Managed servers must have "AutoRestart=true." This can be set in the "Health Monitoring" tab for each respective server in the WLS console.
    The boot.properties file must be configured and present for each server that you plan to start automatically so that you are not prompted for the user name and password each time. If you are not currently prompted when you start the servers then it is already done.
    The nodemanager.properties file must have "StartScriptEnabled=true" and "StartScriptName=StartWeblogic.cmd" in place.

  • 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....

  • Problem Starting Managed Servers

    Hi,
    I am trying to start Managed Server on Sun Solaris. My admin Server and managed Server
    are on the same Machine.
    My admin Server starts up with out any problem. WhenI try to bring up my Managed
    Server its not reading the command line arguments which I supplied through the Console:
    Servers -> serverName -> Remote Start->Arguments. For some reason these command arguments
    are not read and so I am having errors like Unable to load libraries, etc.
    Also when I saw the log file for managed server the class path and the arguments
    are printed in a different way than I have set. I dont know if thats a problem or
    not. I am copying part of that for your reference.
    classpath=/opt/j2sdk1_3_1_01/jre/lib/rt.jar\:/opt/weblogic6.1\:/opt/weblogic6.1/lib/weblogic_sp.jar\:/opt/weblogic6.1/lib/weblogic.jar\
    serverStartArgs=-Dweblogic.management.server\=sunserver\:7210 -Djava.security.policy\=\=/opt/weblogic6.1/lib/weblogic.policy
    I have checked the config.xml file and what ever I have set in the console is being
    saved properly in the xml file.
    Can any one know why the back slash is printed above even though I havent typed that
    in the console. Has any one have experince with setting the command line arguments
    and class path through console for Managed servers.
    I am stuck up at this point. Any help in this regard will be greatly appreciated.
    Thanks,
    Kiran

    Seems a method signature does not match with the implementation in the
    library either due to namemangling or incompatible versions of libraries.
    You are loading your own custom native libraries for security.
    Best would be use the default startManagedServer -- once the server has
    started, copy and paste the entire value of java.library.path into the
    startup arguments for Remote start.
    For instance in my server log file:
    ####<Apr 10, 2002 6:47:10 PM PDT> <Info> <Management> <mountview> <myserver>
    <main> <system> <> <141034> <Java system property: java.library.path =
    /home/sabha/600sp2only/jdk130/jre/bin/../lib/sparc/hotspot:/home/sabha/600sp
    2only/jdk130/jre/bin/../lib/sparc::/home/sabha/600sp2only/wlserver6.0/lib/so
    laris:/home/sabha/600sp2only/wlserver6.0/lib/solaris/oci816_8:/usr/lib>
    I would set that as the arguments :
    -Djava.library.path=/home/sabha/600sp2only/jdk130/jre/lib/sparc/hotspot:/hom
    e/sabha/600sp2only/jdk130/jre/bin/../lib/sparc::/home/sabha/600sp2only/wlser
    ver6.0/lib/solaris:/home/sabha/600sp2only/wlserver6.0/lib/solaris/oci816_8:/
    usr/lib
    If this does not work, then java for some reason is not taking library paths
    set as java.library.path and I dont know how to set LD_LIBRARY_PATH as part
    of arguments to java. Another thing is before starting the NodeManager, set
    the LD_LIBRARY_PATH to point the library directories and see if this helps.
    regards,
    Sabha
    "Kiran" <[email protected]> wrote in message
    news:[email protected]...
    >
    Sabha,
    I am trying to start the managed server via remote start. After readingyour reply
    I have cleaned up the argument list for remote start. Now I am gettingaltogether
    a different error.(Surpsisingly I was able to start the managed serversusing srartManagedServer.sh.
    I dont know why I am having trouble to do the same through the remotestart).
    >
    I am getting a unsatisfied link error. In your reply you have asked me toadd -Djava.library.path
    to the argument liist which I did. Below you can find the exact error Ihave got:
    >
    >
    The WebLogic Server did not start up properly.
    Exception raised:
    java.lang.UnsatisfiedLinkError:/export/home/spbbprf1/Servers/v25_0/bb/pub/libinterface.so:
    ld.so.1: /usr/bin/../java/bin/../bin/sparc/native_threads/java: fatal:relocation
    error: file /export/home/spbbprf1/Servers/v25_0/bb/pub/libinterface.so:symbol Opsys_oneWayCryptCmpApi:
    referenced symbol not found
    at java.lang.ClassLoader$NativeLibrary.load(Native Method)
    at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1382)
    at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1306)
    at java.lang.Runtime.loadLibrary0(Runtime.java:749)
    at java.lang.System.loadLibrary(System.java:820)
    atamdocs.APILink.accesscontrol.sum.EncryptApi.<clinit>(EncryptApi.java:20)
    atamdocs.APILink.accesscontrol.sum.UserJoltBackend.<clinit>(UserJoltBackend.ja
    va:52)
    >
    atamdocs.APILink.accesscontrol.sum.SumManagerImpl.<init>(SumManagerImpl.java:5
    9)
    >
    at java.lang.Class.newInstance0(Native Method)
    at java.lang.Class.newInstance(Class.java:237)
    atamdocs.uamsimpl.server.storage.multi.MultiManagerImpl.<init>(MultiManagerImp
    l.java:208)
    >
    at java.lang.Class.newInstance0(Native Method)
    at java.lang.Class.newInstance(Class.java:237)
    atamdocs.uamsimpl.server.storage.cache.CachingManagerImpl.<init>(CachingManage
    rImpl.java:81)
    >
    at java.lang.Class.newInstance0(Native Method)
    at java.lang.Class.newInstance(Class.java:237)
    at amdocs.uams.UamsSystem.getUamsManager(UamsSystem.java:156)
    atamdocs.uamsimpl.server.ejb.wl6.WLUamsDelegate.<init>(WLUamsDelegate.java:61)
    atamdocs.uamsimpl.server.ejb.wl6.WLUamsDelegate.<init>(WLUamsDelegate.java:55)
    at java.lang.Class.newInstance0(Native Method)
    at java.lang.Class.newInstance(Class.java:237)
    at amdocs.uamsimpl.server.ejb.wl6.WLUamsRealm.<init>(WLUamsRealm.java:42)
    at java.lang.Class.newInstance0(Native Method)
    at java.lang.Class.newInstance(Class.java:237)
    at weblogic.security.acl.Realm.getRealm(Realm.java:84)
    at weblogic.security.acl.Realm.getRealm(Realm.java:62)
    atweblogic.security.SecurityService.initializeRealm(SecurityService.java:258)
    at weblogic.security.SecurityService.initialize(SecurityService.java:115)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:402)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
    at weblogic.Server.main(Server.java:35)
    Reason: Fatal initialization exception
    >
    >
    Please let me know if you need more description.
    Thanks,
    Kiran
    "Sabha" <[email protected]> wrote:
    Either you are attempting to start a managed server through its
    NodeManager
    for which the remote startup arguments are not correct or something else
    is
    wrong. How are you starting the server? The remote start is only when you
    want to start the server through NodeManager and not for normalinvocation
    of the startManagedServer script.
    Does the server really start? can you paste the startup arguments for the
    remote start of the managed server as saved in the config.xml.
    What is the log generated when the managed server is startedup.
    -Sabha
    "Kiran" <[email protected]> wrote in message
    news:[email protected]...
    Sabha,
    The main problem is:
    What ever I am trying to give in the command line arguments through theConsole:
    Servers -> serverName -> Remote Start->Arguments.
    is not being read during managed server start up.
    I have all the libraries defined defined in java.lib.path. I dont knowwhy
    its not
    being read by managed server during start up. Am I missing something.
    -Kiran
    "Sabha" <[email protected]> wrote:
    If its unable to load the performance packs, try setting
    java.library.path
    to the solaris lib directories. /usr/lib, /home/oracle/lib paths -- oryou
    can just copy what is in the admin weblogic.log file for the
    java.library.path (make sure the paths are correct and applicable forthe
    maanged server box also) and pass that as an argument as
    in -Djava.library.path=/usr/lib:/bea/wlserver6.1/lib/solaris...
    -Sabha
    "Kiran" <[email protected]> wrote in message
    news:[email protected]...
    Hi,
    I am trying to start Managed Server on Sun Solaris. My admin Server
    and
    managed Server
    are on the same Machine.
    My admin Server starts up with out any problem. WhenI try to bring
    up
    my
    Managed
    Server its not reading the command line arguments which I supplied
    through
    the Console:
    Servers -> serverName -> Remote Start->Arguments. For some reason
    these
    command arguments
    are not read and so I am having errors like Unable to load
    libraries,
    etc.
    Also when I saw the log file for managed server the class path and
    the
    arguments
    are printed in a different way than I have set. I dont know if thats
    a
    problem or
    not. I am copying part of that for your reference.
    classpath=/opt/j2sdk1_3_1_01/jre/lib/rt.jar\:/opt/weblogic6.1\:/opt/weblog
    i
    c
    6.1/lib/weblogic_sp.jar\:/opt/weblogic6.1/lib/weblogic.jar\
    serverStartArgs=-Dweblogic.management.server\=sunserver\:7210 -Djava.secur
    i
    t
    y.policy\=\=/opt/weblogic6.1/lib/weblogic.policy
    I have checked the config.xml file and what ever I have set in the
    console
    is being
    saved properly in the xml file.
    Can any one know why the back slash is printed above even though I
    havent
    typed that
    in the console. Has any one have experince with setting the command
    line
    arguments
    and class path through console for Managed servers.
    I am stuck up at this point. Any help in this regard will be greatlyappreciated.
    Thanks,
    Kiran

  • Node Manager Not Starting Managed Servers

    I have nodemanager configured to restart managed servers automatically upon reboot but when I physically restart the 2nd node none of the managed servers start and there are no errors. Steps completed and verified....
    1) Nodemanager.properties has domain path and 'crashrecoveryenabled' set to 'true'
    2) managed servers have autorestart set to 'true' and -Xnohup parameter added to startup arguments.
    3) Boot.properties files ave the username and password (encrypted) to start up the server.
    Here is the nodemanager.log file and you can clearly see it is grabbing the startup files. It almost looks like the server files are trying to get loaded before the nodemanager port is available but I see no errors. Any ideas?
    <Dec 28, 2009 9:16:59 AM> <Info> <QA10311> <WebProxyServer2> <Working directory is "C:\bea\user_projects\domains\QA10311">
    <Dec 28, 2009 9:16:59 AM> <Info> <QA10311> <WebProxyServer2> <Server output log file is "C:\bea\user_projects\domains\QA10311\servers\WebProxyServer2\logs\WebProxyServer2.out">
    <Dec 28, 2009 9:47:09 AM> <INFO> <Loading domains file: C:\bea\WLSERV~1.3\common\nodemanager\nodemanager.domains>
    <Dec 28, 2009 9:47:16 AM> <INFO> <Loading identity key store: FileName=C:/bea/WLSERV~1.3/server\lib\DemoIdentity.jks, Type=jks, PassPhraseUsed=true>
    <Dec 28, 2009 9:47:18 AM> <INFO> <Loaded node manager configuration properties from 'C:\bea\WLSERV~1.3\common\nodemanager\nodemanager.properties'>
    <Dec 28, 2009 9:47:21 AM> <Info> <QA10311> <ACR2> <Startup configuration properties loaded from "C:\bea\user_projects\domains\QA10311\servers\ACR2\data\nodemanager\startup.properties">
    <Dec 28, 2009 9:47:21 AM> <Info> <QA10311> <CommandNet2> <Startup configuration properties loaded from "C:\bea\user_projects\domains\QA10311\servers\CommandNet2\data\nodemanager\startup.properties">
    <Dec 28, 2009 9:47:21 AM> <Info> <QA10311> <FPCE2> <Startup configuration properties loaded from "C:\bea\user_projects\domains\QA10311\servers\FPCE2\data\nodemanager\startup.properties">
    <Dec 28, 2009 9:47:21 AM> <Info> <QA10311> <MQServer2> <Startup configuration properties loaded from "C:\bea\user_projects\domains\QA10311\servers\MQServer2\data\nodemanager\startup.properties">
    <Dec 28, 2009 9:47:22 AM> <Info> <QA10311> <PortalServer2> <Startup configuration properties loaded from "C:\bea\user_projects\domains\QA10311\servers\PortalServer2\data\nodemanager\startup.properties">
    <Dec 28, 2009 9:47:22 AM> <Info> <QA10311> <ShoppingCart2> <Startup configuration properties loaded from "C:\bea\user_projects\domains\QA10311\servers\ShoppingCart2\data\nodemanager\startup.properties">
    <Dec 28, 2009 9:47:22 AM> <Info> <QA10311> <webapp2> <Startup configuration properties loaded from "C:\bea\user_projects\domains\QA10311\servers\webapp2\data\nodemanager\startup.properties">
    <Dec 28, 2009 9:47:22 AM> <Info> <QA10311> <WebProxyServer2> <Startup configuration properties loaded from "C:\bea\user_projects\domains\QA10311\servers\WebProxyServer2\data\nodemanager\startup.properties">
    <Dec 28, 2009 9:47:22 AM> <Info> <QA10311> <WUA2> <Startup configuration properties loaded from "C:\bea\user_projects\domains\QA10311\servers\WUA2\data\nodemanager\startup.properties">
    <Dec 28, 2009 9:47:27 AM> <INFO> <Secure socket listener started on port 5556, host qaportal2.FCQA.COM>

    Hi,
    Entries in nodemanager.properties looks fine, but how are you testing this functionality?
    If you will stop servers monitored by nodemanager, stop nodemanager and then reboot physical server, on startup if nodemanager is configured as daemon it will start nm process but will do nothing to managed server process.
    To test "CrashRecoveryEnabled=true" kill the managed server pid and then stop/kill nodemanager process. Then perform physical server reboot, now if nm is configured as daemon process server reboot will start nodemanager. Once NM is up first thing it check is the server it was monitoring earlier and if under directory $WL_HOME/servers/<server>/data/nodemanager it finds "pid" and "lck" file it checks if that pid exists and if not then go for a restart of weblogic server instance.
    This has worked for me...!
    Thanks,
    Ranjan
    http://www.middlewaresupport.wordpress.com

  • Start managed servers via admin console

    Hello,
    I have installed weblogic server, created a domain, added a managed server. All working fine. Now I want to be able to start managed server through admin console.
    According to this documentation (http://docs.oracle.com/cd/E13222_01/wls/docs81/adminguide/confignodemgr.html), it should all be pre-configured for development environment. But when i try start the managed server in admin console, it says "server does not have a machine associated with it." I added a machine and assigned that machine to the managed server, now it says "the Node Manager associated with machine m1 is not reachable.".
    Can someone point to instructions on how to setup this on dev environment. In one of the instructions, it is suggested to change nodemanager.properties in common\nodemanager folder. But this file doesn't exist in my environment.
    All i want is to start all admin and managed server with one script or with start the admin server and able to start the managed servers via console.
    Thanks,

    Hi,
    Check from the console whether your node manager is reachable or not.
    Console Path:
    Machines -> <YOUR_MACHINE_NAME> -> Monitoring (tab) -> Node Manager Status (sub-tab) -> Status: Reachable
    You Can follow the below link for "Node manager not reachable"
    http://middlewaremagic.com/weblogic/?p=5205
    Once done,check the status of the node manager.
    Still even after this if the node manager is not reachable
    Check the node manager logs,whether you get any exceptions
    location $weblogic_home\wlserver_10.3\common\nodemanager\nodemanger.log
    You can take help of the below link for trouble shooting the basic node manager exceptions.
    http://middlewaremagic.com/weblogic/?p=2887
    Or You can even paste the error's on this post itself,we will guide you .
    Regards
    FAbian

  • Not able to restart managed servers after password change in console

    im doin the following steps,am i doin anything wrong?
    1)shutdown all managed servers
    2)change pwd in admin console
    3)edit boot.properties file with new pwd in admin server
    4)copy these boot file to every managed server
    5)now restart admin server.(able to do it succesfully)
    6)not able to restart managed servers (im getting the following error.
    Can any help me out plz very urgent?
    <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.
    weblogic.security.SecurityInitializationException: Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(Unknown Source)
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(Unknown Source)
    at weblogic.security.service.SecurityServiceManager.initialize(Unknown Source)
    at weblogic.security.SecurityService.start(SecurityService.java:141)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    Truncated. see log file for complete stacktrace
    <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>

    Hi,
    *1)In order to export the user data on to the server,do we have to create a specific directory to save this data into the server.*
    Yes ....you can give any Existing Directory Path in the AdminConsole Export Page.... Any Directory in your File System.
    *2)Is there any other way by not exporting or importing the data?*
    That is the only way to prevent the Data Loss....There are some other ways to do it without using Admin Console like Using WLST or Using JMX you can export the Data but all these techniques will exactly do the same thing ... The AdminConsole is the easiest way to do it.
    Thanks
    Jay SenSharma
    http://middlewaremagic.com/weblogic/  (Middleware Magic Is Here)

  • Error while starting managed servers in a cluster

    Hi,
              I have Weblogic 8.1.3 deployed on my system. We've have a Ant script that set's up the project domain etc. We have an admin server and two other managed servers which are part of a cluster. I am able to start the admin server and access the admin console without any errors. However when I start any of the managed servers in the cluster, using the following command (startManagedWebLogic.cmd Reactor-1 http://localhost:80 OR startManagedWebLogic.cmd Reactor-2 http://localhost:80)
              I get the error listed below. The same Ant script was used to setup the project on another system and it worked but I haven't been able to set it up on my system.
              The error says that it could be due to servers having duplicate names in the cluster but thats not the case here, the managed servers are named Reactor-1 and 2.
              Also, the IP address being accessed, 192.168.141.50:81 is not my system, its another system on the network. I've done a full text search for the IP address but I've not been able to find it in ANY file under c:\bea.
              Can someone please tell me if I've missed something? I'd appreciated any help with this.
              Thanks
              Ameeth
              <Mar 21, 2005 4:52:43 PM GMT+05:30> <Notice> <Cluster> <BEA-000142> <Trying to download cluster JNDI tree from server Reactor-1
              .>
              <Mar 21, 2005 4:52:44 PM GMT+05:30> <Warning> <Net> <BEA-000905> <Could not open connection with host: 127.0.0.1 and port: 81.>
              <Mar 21, 2005 4:52:44 PM GMT+05:30> <Error> <Cluster> <BEA-000141> <TCP/IP socket failure occurred while fetching statedump ove
              r HTTP from Reactor-1.
              java.net.ConnectException: Tried all: '1' addresses, but could not connect over HTTP to server: '127.0.0.1', port: '81'
              at weblogic.net.http.HttpClient.openServer(Ljava.lang.String;I)V(HttpClient.java:275)
              at weblogic.net.http.HttpClient.openServer()V(HttpClient.java:329)
              at weblogic.net.http.HttpClient.<init>(Ljava.net.URL;Lweblogic.security.SSL.SSLClientInfo;Lweblogic.security.SSL.SSLSoc
              ketFactory;I)V(HttpClient.java:128)
              at weblogic.net.http.HttpClient.New(Ljava.net.URL;Lweblogic.security.SSL.SSLClientInfo;Lweblogic.security.SSL.SSLSocket
              Factory;I)Lweblogic.net.http.HttpClient;(HttpClient.java:196)
              at weblogic.net.http.HttpURLConnection.connect()V(HttpURLConnection.java:119)
              at weblogic.cluster.MemberManager.waitForSync(J)V(MemberManager.java:213)
              at weblogic.cluster.MemberManager.waitToSyncWithCurrentMembers()V(MemberManager.java:160)
              at weblogic.cluster.ClusterCommunicationService.initialize()V(ClusterCommunicationService.java:58)
              at weblogic.t3.srvr.T3Srvr.initializeHere()V(T3Srvr.java:924)
              at weblogic.t3.srvr.T3Srvr.initialize()V(T3Srvr.java:670)
              at weblogic.t3.srvr.T3Srvr.run([Ljava.lang.String)I(T3Srvr.java:344)
              at weblogic.Server.main([Ljava.lang.String)V(Server.java:32)
              >
              <Mar 21, 2005 4:52:47 PM GMT+05:30> <Notice> <Security> <BEA-090170> <Loading the private key stored under the alias DemoIdenti
              ty from the jks keystore file C:\bea\weblogic81\server\lib\DemoIdentity.jks.>
              <Mar 21, 2005 4:52:47 PM GMT+05:30> <Notice> <Security> <BEA-090171> <Loading the identity certificate stored under the alias D
              emoIdentity from the jks keystore file C:\bea\weblogic81\server\lib\DemoIdentity.jks.>
              <Mar 21, 2005 4:52:47 PM GMT+05:30> <Warning> <WebLogicServer> <BEA-000311> <Attempting to use low strength (exportable) certif
              icates with a full strength (domestic) license.>
              <Mar 21, 2005 4:52:47 PM GMT+05:30> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file C
              :\bea\weblogic81\server\lib\DemoTrust.jks.>
              <Mar 21, 2005 4:52:47 PM GMT+05:30> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file C
              :\bea\JROCKI~1\jre\lib\security\cacerts.>
              <Mar 21, 2005 4:52:48 PM GMT+05:30> <Notice> <WebLogicServer> <BEA-000355> <Thread "SSLListenThread.Default" listening on port
              7002, ip address 127.0.0.1>
              <Mar 21, 2005 4:52:48 PM GMT+05:30> <Notice> <WebLogicServer> <BEA-000355> <Thread "ListenThread.Default" listening on port 81,
              ip address 127.0.0.1>
              <Mar 21, 2005 4:52:48 PM GMT+05:30> <Notice> <Cluster> <BEA-000102> <Joining cluster ReactorCluster on 237.0.0.1:7001>
              <Mar 21, 2005 4:52:48 PM GMT+05:30> <Notice> <WebLogicServer> <BEA-000332> <Started WebLogic Managed Server "Reactor-1" for dom
              ain "ReactorAdminServer" running in Development Mode>
              <Mar 21, 2005 4:52:48 PM GMT+05:30> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
              <Mar 21, 2005 4:52:51 PM GMT+05:30> <Warning> <Net> <BEA-000905> <Could not open connection with host: 127.0.0.1 and port: 82.>
              <Mar 21, 2005 4:52:52 PM GMT+05:30> <Error> <Cluster> <BEA-000141> <TCP/IP socket failure occurred while fetching statedump ove
              r HTTP from 8288749592481618145S:localhost:[81,81,-1,-1,81,-1,-1,0,0]:192.168.141.50:81,192.168.141.50:82:ReactorAdminServer:Re
              actor-1.
              java.io.IOException: Reference to server no longer exists.
              Possible reasons for failure include having servers with duplicate names running on a cluster. Please check your configuratio
              n for this error.
              at weblogic.rmi.cluster.ServerInfoManager.updateServerInfo(Lweblogic.rmi.cluster.ServerInfo)V(ServerInfoManager.java:1
              11)
              at weblogic.rmi.cluster.ServerInfoManager.readUpdate(Ljava.lang.Object)V(ServerInfoManager.java:95)
              at weblogic.cluster.MemberAttributes.readExternal(Ljava.io.ObjectInput)V(MemberAttributes.java:103)
              at java.io.ObjectInputStream.readExternalData(Ljava.io.Externalizable;Ljava.io.ObjectStreamClass)V(Unknown Source)
              at java.io.ObjectInputStream.readOrdinaryObject(Z)Ljava.lang.Object;(Unknown Source)
              at java.io.ObjectInputStream.readObject0(Z)Ljava.lang.Object;(Unknown Source)
              at java.io.ObjectInputStream.readObject()Ljava.lang.Object;(Unknown Source)
              at weblogic.cluster.HTTPExecuteRequest.execute(Lweblogic.kernel.ExecuteThread)V(HTTPExecuteRequest.java:91)
              at weblogic.kernel.ExecuteThread.execute(Lweblogic.kernel.ExecuteRequest)V(ExecuteThread.java:219)
              at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:178)
              at java.lang.Thread.startThreadFromVM(Ljava.lang.Thread)V(Unknown Source)

    make sure you use a unique cluster multicast ip address. are you sure that your etc/hosts file has proper entries for localhost?

Maybe you are looking for

  • How can i get my ipod to work properly?

    My ipod is not charging at all when connected to the adapter or to my mac. when i connect to the charger either the battery sign comes up with the connect to power symbol. or the apple sign keeps flashing on and off. it doesnt charge. I already tried

  • Adobe AIR for android, what is going on ?

    Hello! Few days ago i decided to try develop adobe air for android. Updated my phone to android 2.2 installed Android SDK , Adobe AIR SDK. Now there are few tutorials out there how to set up Air ap for android. They all state that u have to install R

  • Problem with disc 2?

    i just got my G4. installing disc 1 of tiger went fine. then at the end of installation for disc 2 it says there were errors and i have to reinsert the disc. then the cycle starts over and over again. i'm unable to restart my computer or quit the ins

  • "Files" and other tabs not visible for document library after script editor webpart is added

    I created a document library and uploaded a few documents to ti.  On the ribbon, I could see both "Files" and "Library" tabs.  I then added a Script Editor webpart to this page because I needed to run some javascript on this page.  Now, when I go to

  • COOIS report: not able to select operations based on work centers

    Hi All, When accessing the COOIS report using operation listv& selecting the std profile.I need to get the operation perfomred on specific work center. I enter the work center & plant code in the selection fields available in the "select at operarion