Restart Managed Server from Adminserver FAILED_NOT_RESTARTABLE

Hi all,
I've got problems restarting the managed server from the adminkonsole ('Control'-Tab) and from within wlst while connected to the adminserver 'start('mymanaged','Server','t3://localhost:80', block='true') connected with the adminserver.
In the logfile of the administration occurs a nullPointerException:
java.lang.NullPointerException
     at javax.mail.internet.MimeUtility.decodeText(MimeUtility.java:480)
     at weblogic.deploy.service.internal.transport.http.DeploymentServiceServlet.mimeDecode(DeploymentServiceServlet.java:788)
     at weblogic.deploy.service.internal.transport.http.DeploymentServiceServlet.authenticateRequest(DeploymentServiceServlet.java:523)
     at weblogic.deploy.service.internal.transport.http.DeploymentServiceServlet.doPost(DeploymentServiceServlet.java:194)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:225)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:127)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3214)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:1983)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1890)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1344)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
The nodemanager-log shows an IOException:
<02.02.2007 12:08:42> <Warning> <Exception while starting server 'sunetweb': java.io.IOException: Server failed to start up. See server output log for more details.>
java.io.IOException: Server failed to start up. See server output log for more details.
     at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:246)
     at weblogic.nodemanager.server.Handler.handleStart(Handler.java:463)
     at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:115)
     at weblogic.nodemanager.server.Handler.run(Handler.java:66)
     at java.lang.Thread.run()V(Unknown Source)
In the console, the serverstate of the managed server is:
FAILED_NOT_RESTARTABLE
But in config.xml both servers have set auto-restart:true.
Starting from within wlst connected to Nodemanager instead works (nmStart("mymanaged", 'c:/win32app/bea/user_projects/domains/mydomain').
Also the serverstart with a command file works.
I want to restart the managed server from the console and from wlst connected to admin server.
What is wrong ?
Thanks, kind regards,
Thomas

Hi Jin,
I use wlst now to do what I want.
For a gentle restart of the managed server I connect to the Administration server and then run:
#shutdown mymanaged gently
shutdown(name='mymanaged',entityType='Server',ignoreSessions='true',timeOut=5, force='false')
#start the sever again
start('mymanaged','Server','t3://localhost:80', block='true')
Still it is not possible to restart the managed server from console (stopping works).
But wlst works for me.
I won't follow this problem further.
Thanks a lot.
Kind regards,
Thomas

Similar Messages

  • Start Managed Server from Admine clonsole FAILED_NOT_RESTARTABLE

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

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

  • Facing error in starting managed server from nodemanager

    Hi All,
    I have installed WebLogic server 10.3.4 and installed OSB 11.1.1.4.0. I created domain with one admin server and one managed server for osb. When I started managed server with the startManagedWebLogic command it got started successfully but when I am trying tp start the managed server from nodemanager I am getting the following error
    starting weblogic with Java version:
    FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
    [ERROR] aborted
    JRockit aborted: Unknown error (50)
    ERROR: transport error 202: bind failed: Address already in use
    ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
    JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]
    Starting WLS with line:
    D:\JDK\JROCKI~1.0\bin\java -jrockit -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8453,server=y,suspend=n -Djava.compiler=NONE -Xms256m -Xmx512m -Dweblogic.Name=osb_server1 -Djava.security.policy=D:\ORACLE~1\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.policy -Dweblogic.system.BootIdentityFile=D:\Oracle_OSB\Middleware\user_projects\domains\osb_domain\servers\osb_server1\data\nodemanager\boot.properties -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.security.SSL.ignoreHostnameVerification=false -Dweblogic.ReverseDNSAllowed=false -Xverify:none -da:org.apache.xmlbeans... -ea -da:com.bea... -da:javelin... -da:weblogic... -ea:com.bea.wli... -ea:com.bea.broker... -ea:com.bea.sbconsole... -Dplatform.home=D:\ORACLE~1\MIDDLE~1\WLSERV~1.3 -Dwls.home=D:\ORACLE~1\MIDDLE~1\WLSERV~1.3\server -Dweblogic.home=D:\ORACLE~1\MIDDLE~1\WLSERV~1.3\server -Dcommon.components.home=D:\ORACLE~1\MIDDLE~1\ORACLE~1 -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Ddomain.home=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\OSB_DO~1 -Djrockit.optfile=D:\ORACLE~1\MIDDLE~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrocket_optfile.txt -Doracle.server.config.dir=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\OSB_DO~1\config\FMWCON~1\servers\osb_server1 -Doracle.domain.config.dir=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\OSB_DO~1\config\FMWCON~1 -Digf.arisidbeans.carmlloc=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\OSB_DO~1\config\FMWCON~1\carml -Digf.arisidstack.home=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\OSB_DO~1\config\FMWCON~1\arisidprovider -Doracle.security.jps.config=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\OSB_DO~1\config\fmwconfig\jps-config.xml -Doracle.deployed.app.dir=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\OSB_DO~1\servers\osb_server1\tmp\_WL_user -Doracle.deployed.app.ext=\- -Dweblogic.alternateTypesDirectory=D:\ORACLE~1\MIDDLE~1\ORACLE~1\modules\oracle.ossoiap_11.1.1,D:\ORACLE~1\MIDDLE~1\ORACLE~1\modules\oracle.oamprovider_11.1.1 -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Dweblogic.jdbc.remoteEnabled=false -Dem.oracle.home=D:\Oracle_OSB\Middleware\oracle_common -Djava.awt.headless=true -Dweblogic.management.discover=false -Dweblogic.management.server=http://soaspt-app01.scotwat.net:7010 -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=D:\ORACLE~1\MIDDLE~1\patch_wls1034\profiles\default\sysext_manifest_classpath;D:\ORACLE~1\MIDDLE~1\patch_ocp360\profiles\default\sysext_manifest_classpath weblogic.Server
    [WARN ] Use of -Djrockit.optfile is deprecated and discouraged.
    FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
    [ERROR] aborted
    JRockit aborted: Unknown error (50)
    ERROR: transport error 202: bind failed: Address already in use
    ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
    JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]
    <11-Mar-2013 13:22:17> <FINEST> <NodeManager> <Waiting for the process to die: 5916>
    <11-Mar-2013 13:22:17> <INFO> <NodeManager> <Server failed during startup so will not be restarted>
    <11-Mar-2013 13:22:17> <FINEST> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>
    My nodemanager is started and reachable. The error above says "Address already in use" but I am able to start my managed server through startManagedWebLogic.cmd command.
    Can anyone please tell me what could be the issue. It is really urgent. Please help!!

    Hi Roshni,
    It is likely that a configuration is missing or not set properly in the Node Manager properties file (nodemanager.properties) since the managed server can be started up using startManagedWebLogic.cmd but not with Node Manager. I would complete the following steps to fix the problem:
    1. Go to %WLS_HOME%\common\nodemanager and open up nodemanager.properties (Make a backup of the file first). NOTE: WLS_HOME is your WebLogic Server home.
    2. Look for the parameters "StartScriptEnabled" and "StopScriptEnabled". They should be set to true. If not, please set them to true.
    3. Save and close the file.
    4. Restart the Node Manager
    If you are still unable to start the manager server using Node Manager, you may need to update the DEBUG_PORT parameter in setDomainEnv.cmd located in %MIDDLEWARE_HOME%\user_projects\domains\%DOMAIN_HOME%\bin (always make a backup before changing a configuration file). You may refer to Oracle Support note 1272642.1 for more information about the nodemanager.properties file and how to configure the DEBUG_PORT parameter in setDomainEnv.cmd if needed.
    Thanks,
    Scott (PITSS)
    http://pitss.com/us

  • Error start managed server from admin console in SSL mode

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

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

  • Starting Managed Server from Administration Console

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

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

  • How to start managed server from admin server both running

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

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

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

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

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

  • Error when trying to start managed server from node manager

    I have a managed server which is authenticated through a WeblogicAuthenticProvider. When starting the managed server from command line I need to setup certain jars in the classpath in order to start it successfully. However when I try and start the managed server from a node manager, I receive the following error.
    Any ideas as to what is going on are appreciated. Is there any way to force Weblogic Node manager to invoke the actual startManagedWeblogic.cmd when bringing up the managed server
    Thanks
    <Jun 5, 2006 9:21:05 AM EDT> <Info> <NodeManager@*.*:5555> <Starting Server TweCluster::TaxwareServer1 ...>
    <Jun 5, 2006 9:21:07 AM EDT> <Info> <NodeManager@*.*:5555> <Server TweCluster::TaxwareServer1 started, process id = 3,012>
    <Jun 5, 2006 9:21:11 AM EDT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with BEA WebLogic JRockit(TM) 1.4.2_05 JVM R24.4.0-1 Version ari-38120-20041118-1131-win-ia32 from BEA Systems, Inc.>
    <Jun 5, 2006 9:21:12 AM EDT> <Info> <Management> <BEA-141140> <The managed server is going to contact the admin server at http://zeus3dev:7001 to check if there exists a running admin server at this URL.>
    <Jun 5, 2006 9:21:12 AM EDT> <Info> <Configuration Management> <BEA-150017> <This server is being started as a dependent managed server.>
    <Jun 5, 2006 9:21:12 AM EDT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647
    WebLogic XMLX Module 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647 >
    <Jun 5, 2006 9:21:12 AM EDT> <Info> <Configuration Management> <BEA-150015> <Connecting to the administration server http://zeus3dev:7001 to retrieve the initial configuration.>
    <Jun 5, 2006 9:21:16 AM EDT> <Notice> <Log Management> <BEA-170019> <The server log file E:\bea8.1\weblogic81\common\nodemanager\TaxwareServer1\TaxwareServer1.log is opened. All server side log events will be written to this file.>
    The WebLogic Server did not start up properly.
    java.lang.NoClassDefFoundError: com/taxware/twe/util/crypto/CryptoUtil
    at com.taxware.twe.auth.server.GenericPrincipalValidator.<init>()V(GenericPrincipalValidator.java:41)
    at com.taxware.twe.auth.server.WeblogicPrincipalValidator.<init>()V(WeblogicPrincipalValidator.java:38)
    at com.taxware.twe.auth.server.WeblogicAuthenticationProvider.getPrincipalValidator()Lweblogic.security.spi.PrincipalValidator;(WeblogicAuthenticationProvider.java:188)
    at weblogic.security.service.PrincipalAuthenticator.initialize(Ljava.lang.String;[Lweblogic.management.security.ProviderMBean;)V(PrincipalAuthenticator.java:154)
    at weblogic.security.service.PrincipalAuthenticator.<init>(Ljava.lang.String;[Lweblogic.management.security.ProviderMBean;)V(PrincipalAuthenticator.java:262)
    at weblogic.security.service.SecurityServiceManagerDelegateImpl.doATN(Ljava.lang.String;Lweblogic.management.security.RealmMBean;)Lweblogic.security.service.PrincipalAuthenticator;(SecurityServiceManagerDelegateImpl.java:581)
    at weblogic.security.service.SecurityServiceManagerDelegateImpl.initializeRealm(Lweblogic.management.security.RealmMBean;Ljava.util.HashMap;)V(SecurityServiceManagerDelegateImpl.java:420)
    at weblogic.security.service.SecurityServiceManagerDelegateImpl.loadRealm(Ljava.lang.String;)V(SecurityServiceManagerDelegateImpl.java:700)
    at weblogic.security.service.SecurityServiceManagerDelegateImpl.initializeRealms()V(SecurityServiceManagerDelegateImpl.java:733)
    at weblogic.security.service.SecurityServiceManagerDelegateImpl.initialize(Lweblogic.security.acl.internal.AuthenticatedSubject;)V(SecurityServiceManagerDelegateImpl.java:876)
    at weblogic.security.service.SecurityServiceManager.initialize(Lweblogic.security.acl.internal.AuthenticatedSubject;)V(SecurityServiceManager.java:734)
    at weblogic.t3.srvr.T3Srvr.initializeHere()V(T3Srvr.java:822)
    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)
    Reason: com/taxware/twe/util/crypto/CryptoUtil                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

    Found a workaround:
    Manually, add PATH (and probably the other environment variables also) to
    ${WLS_HOME}/common/bin/commEnv.sh.

  • How to start managed server from console?

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

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

  • Problems starting managed server from admin console WL70 portal

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

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

  • Start managed server from console?

    If I try to start a new weblogic 10.3 managed server from the console then i get this error:
    "The server myserver does not have a machine associated with it.
    All of the servers selected are currently in a state which is incompatible with this operation or are not associated with a running Node Manager or you are not authorized to perform the action requested. No action will be performed."
    Starting the same managed server from the dos prompt "bin/startManagedServer.bat myserver" works, so why is the weblogic console not working?

    Hi,
    To start any managed servers from Admin Console you need to have a Machine associated with that Managed server and have to start nodemanager, then only you can start a managed server from console.
    Following are the steps:
    1) Create a Managed Server (MS-1)
    2) Create a Machines (MachineA)
    3) In the above created MachineA add the MS-1 which can be done from the below console path
    Console Path:
    Machines --> MachineA --> Configuration [Tab] --> Servers [Sub-Tab]
    4) Now start nodemanager using the startNodeManager.sh script which can be found in the below path
    Path:
    wlserver_10.3/server/bin/
    5) Now you can try to start your MS-1 using the Admin Console.
    Note: If you still cannot start the your managed servers then would suggest you to have a look at the below post
    Topic: NodeManager is not reachable
    http://middlewaremagic.com/weblogic/?p=5205
    Topic: Common NodeManager Issues in WebLogic
    http://middlewaremagic.com/weblogic/?p=2887
    Regards,
    Ravish Mody

  • Configure Managed Server from Admin Console - Java arguments

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

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

  • Error starting managment server from command line

    I tried to start the managment server from the command line like this:
    <jvm_home>/bin/jrcmd <pid start_management_server
    and I'm getting the following error:
    <pid> Not enough storage is available to run this command
    The system has plenty or resources. I'm unsure what storate the command refers too.
    The pid was found by using tasklist /svc at the command line to find the pid matching the domain service name.
    this is jrockit 1.42_13

    What operating system are you on? What is the complete version of JRockit ("java -version" will tell)?
    Regards,
    /Staffan

  • Nodemanager does not restart managed server after Linux OS reboot

    Running Linux 2.6.18, Sun JDK 1.6.0_14, and WebLogic 10.3, we have a correctly functioning nodemanager watching a single managed server. If I kill -9 the managed server, the nodemanager fires up a new one immediately. If, however, we reboot the box, the nodemanager will start cleanly and will not start the managed server. It appears to believe the node should remain down and reports its status as UNKNOWN.
    I've seen where this is a known problem on Windows boxes, easily gotten around by supplying the -Xrs parameter to the startup parms for the managed server. (Section 5 of the general nodemanager config doc.) I don't see, however, where there's an equally clean solution for Linux.
    Things I've tried:
    + When I set the server to DEBUG, it shows zero sign of receiving a shutdown signal. It's dumping loads of cluster messages, etc, into the log and then suddenly the log just ends so it's dying via kill -9. If the nodemanager is still running at that time, it might try to restart the managed server and log it somewhere as permanently failed.
    + The nodemanager only logs to INFO level, and logs no evidence of deciding to leave the node down. (DEBUG is an invalid LogLevel, so that's all I've got.)
    + A restart signal sent from our AdminServer (on another Linux box) successfully starts the managed node through the nodemanager. Nothing unusual occurs or is logged.
    Things I'm curious about:
    + Is there some way to see in what state the nodemanager believes the managed server to be?
    + Is there some value in some doc somewhere that might say the server should not be restarted?
    + Is there not a log of NodeManager client actions? I don't see anything in domain.log or AdminServer.log except when the NM is down.
    Thanks,
    Kevin
    ListenPort=5556
    ListenBacklog=50
    SecureListener=true
    AuthenticationEnabled=true
    NativeVersionEnabled=false
    CrashRecoveryEnabled=true
    JavaHome=/appl/java/jre
    StartScriptEnabled=false
    StopScriptEnabled=false
    StartScriptName=startWebLogic.sh
    StopScriptName=
    LogFile=/appl/bea/wlserver_10.3/common/nodemanager/logs/nodemanager.log
    LogLevel=INFO
    LogLimit=0
    LogCount=1

    can you set NativeVersionEnabled to true. We have faced this in windows which was fixed by changing this property. Some notes from that issue:
    Faced this interesting issue in Windows 2008 environment. Managed Servers were started by node manager and it was expected that on a system restart after a crash, the node manager will restore the state of the managed servers to the state it was before the crash. Node Manger was configured to run as a windows service. Hence it started after the server restart. But the individual managed servers were not getting started. Interestingly, for the managed servers started by the node manager there were no <Managed_Server_Name>.lck file in the <Server>/data/NodeManger folder.
    To fix this always set the following properties in the nodemanager.properties on the node maager home directory.
    CrashRecoveryEnabled=true /* This by default is set to false. This needs to be turned for auto restart after crash to work */
    NativeVersionEnabled=true /* This is by default set to true and it should be set as such. If you turn this off on platforms for which weblogic provide native JNI libraries ( e.g. as in Windows 2008) then this wont create the .lck file and hence node manager wont restart the managed server after the crash.
    Note: As per official documentation .lck files are required for weblogic node managers to do auto restart after system crash
    From Official documentation:
    After the system is restarted, Node Manager checks each managed domain specified in the nodemanager.domains file to determine if there are any server instances that were not cleanly shutdown. This is determined by the presence of any lock files which are created by Node Manager when a WebLogic Server process is created. This lock file contains the process identifier for WebLogic Server startup script. If the lock file exists, but the process ID is not running, Node Manager will attempt to automatically restart the server.
    If the process is running, Node Manager performs an additional check to access the management servlet running in the process to verify that the process corresponding to the process ID is a WebLogic Server instance.
    After the system is restarted, Node Manager checks each managed domain specified in the nodemanager.domains file to determine if there are any server instances that were not cleanly shutdown. This is determined by the presence of any lock files which are created by Node Manager when a WebLogic Server process is created. This lock file contains the process identifier for WebLogic Server startup script. If the lock file exists, but the process ID is not running, Node Manager will attempt to automatically restart the server.If the process is running, Node Manager performs an additional check to access the management servlet running in the process to verify that the process corresponding to the process ID is a WebLogic Server instance.
    */

  • Having problems removing a managed server from WL console

    Background:
    Running the 11 g R1 (11.1.1.5) server on Linux.
    Installed OIM, OAM, OVD, OID, WL. (other components may be added later)
    Have not yet integrated OIM and OAM.
    The Problem:
    We were running into a problem on our oim server, that warranted removal and reinstallation.
    we were attempting to remove the oim_server1 instance from the weblogic admin console.
    went to deployments, and deleted the entry there for oim_server1
    Then went to environment | servers
         The oim_server1 now shows as "FAILED_NOT_RESTARTABLE"
         and we can not remove this instance frome the admin instance.
         If we attempt to remove it, It gives the errors
              The server oim_server1 is a running server and may not be deleted.
              All of the servers selected are in a state which is incompatible with this operation.
    Restarted the WL Admin server, then went back into the console. This did not change the status of the managed server.
    Tried going to
    /data01/app/oracle/product/Middleware/user_projects/domains/IDMDomain/servers/oim_server1/tmp
    and removing the *.lok file...
    No luck.
    How do we get around this, so we can remove the incorrectly configured oim_server1 ?
    Edited by: 992276 on Mar 6, 2013 11:30 AM

    i was in the EXACT same situation but on weblogic 10.3.3.
    * two servers in FAILED_NOT_RESTARTABLE
    * try to delete them from admin console and i get the "is a running server and my not be deleted..../incompatible with this operation" messages
    i tried lots of things and but i could not get rid of those servers.
    ### What ended up working. ###
    i just started the servers. there is no way they should have started. i had already even deleted the server directories. but they started. and then i shut them down. and at that point i was able to delete them.
    hope this helps you or somebody. it seemed like such an unlikely solution. but it worked for me.
    Edited by: user8825653 on Mar 15, 2013 8:25 AM

Maybe you are looking for

  • Connect touch to 2 macs?

    can i do this? am going to get a touch soon, and.. would like to sync to my ical & address on my powerbook, but itunes on my desktop mac. will this work? (or can i only work with one mac) thanx, am new to this..!

  • QT 7 pro wont copy/paste

    Hello After I purchased QT pro 7, I tried to make a mpeg bigger by taking segments of my other movies, moving the playheads and cutting and pasting, but the frick'n things are still dimmed in the edit section; nothing happens! I checked for rights in

  • Videos will not work!

    I'm having 2 problems with videos: 1. About fifteen of my videos will not transfer to my ipod, when I try to drag and drop them nothing happens at all. They are in the correct format (mp4) and ten other videos had transferred without a problem, just

  • Why does Flash generate invalid class names for library items?

    I imported a bunch of bitmaps (PNGs).  The library symbol names all included the full file name and its extension.  When I check "export for actionscript" it generates a class name based on the symbol name, and it includes the ".png", even though tha

  • Updating Acrobat 9 MAC

    I have about 50 Macs on 10.7 I need to update from 9.3 to 9.5.1. I have updated my mac. I copied my Acrobat through Apple Remote Desktop. Under the user (non administrator) it does not show it changed. I log the user out and login as the local admini