My Oracle Support Banner

WebLogic Managed Server Starts When Using Node Manager but Admin Console Reports Start Failed (Doc ID 861098.1)

Last updated on AUGUST 07, 2017

Applies to:

Oracle WebLogic Server - Version 9.0 and later
Information in this document applies to any platform.
***Checked for relevance on 3-Jun-2016***

Symptoms

Using NodeManager to start a managed server, the console reports the state of the server first as "FAILED_NOT_RESTARTABLE," then it shows it as "RUNNING," but finally the status is set to "FAILED."

Looking at the output of the server in question, the following can be seen:

Redirecting output from WLS window to /usr/app/nohup_MS1_20090424.log
<Apr 24, 2009 11:49:31 AM> <Debug> <NodeManager> <Waiting for the process to die: 15870>
<Apr 24, 2009 11:49:31 AM> <Info> <NodeManager> <Server failed during startup so will not be restarted>

Checking the output from NodeManager, the following is seen:

<Apr 24, 2009 11:49:32 AM> <Warning> <Exception while starting server 'MS1': 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:619)

Changes

Adding nohup and & to the NodeManager script used to start the managed server.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.