Server state failed when starting through node manager

Hi,
I'm getting the below error while starting the managed server through node manager
<Sep 14, 2010 3:49:34 PM> <Warning> <Exception while starting server 'ms01': 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)
I have checked the server logs and it shows the below error code
./admin-stdout.log:<Sep 15, 2010 4:15:56 PM PDT> <Error> <NodeManager> <BEA-300048> <Unable to start the server ms01 : Exception while starting server 'ms01': java.io.IOException: Server failed to start up. See server output log for more details.>
I have also checked WebLogic documentation for BEA-300048. It says "Cause: The most likely cause is a configuration error in the Shell/SSH/RSH NodeManager configuration".
but I'm using Java based node manager
All this is coming up when I enable StartScriptEnabled to true in nodemanager.properties.
What could be reason for failure?

Hi.
If you are not using the latest service pack (sp2) please do so. If you are and are still seeing this
problem please open a case with support.
Thanks
Michael
Tim Dawson wrote:
I get this message whenever I try to use the console to start a managed server
on a remote system.
<Jan 12, 2002 8:18:26 AM PST> <Emergency> <WebLogicServer> <Unable to create a
server socket for: weblogic2.dev.wamnet.com/172.17.27.84, port: 7001. java.net.BindException:
Cannot assign requested address: JVM_Bind Perhaps the address weblogic2.dev.wamnet.com/172.17.27.84
is incorrect or another process is using port 7001.>
I've checked and checked and the only thing running on that box is the node manager!
The console will start a managed server on the local system (i.e. the system
that the admin server is running on) without any complaints.
Any ideas? Thanks,
Tim--
Michael Young
Developer Relations Engineer
BEA Support

Similar Messages

Unable to start SOA server through Node Manager

Hi All,
I am trying to install AIA 11.1.1.6.0 on the top of SOA Suite 11.1.1.6.0.
I was able to install successfully the weblogic server, rcu, soa and osb servers. Now, before installing the AIA, the document i am following it says, make sure to start the soa server through the node manager.
Now i start the admin server, then the node manager, to make sure i have checked that the node manager is up, i logged in to the weblogic console, went to Machines, and i can see that it is up and reachable.
Now using the WLST commands, first i connected to the node manager using command nmConnect(), then i am trying to start the soa server through node manager using the command start('soa_server1') command.
I am getting an error while trying to start soa server with nmStart() command, below is the error message...
"Error starting server soa_server1: weblogic.nodemanager.NMException: Exception while starting server 'soa_server1'"
I executed the dumpStack() command, and i am getting the output as "No stack trace available"
If i am able to start the soa server through the node manager, i can go ahead and install the AIA pack but this is not letting me go forward.
I also tried to start the soa server through the weblogic console., go to servers tab, select the soa_server1 and start, the soa server state is going to "FAILED_NOT_RESTARTABLE".
I followed some of the blogs like...
http://neeraj-soa-tips.blogspot.com/2010/06/starting-admin-and-managed-servers.html
http://www.javamonamour.org/2011/09/nmconnect-nmstart-nmkill.html
Experts, please give your advice.
Many Thanks,
N

Hi Narsing,
I'm assuming that you've followed the required Pre-config steps. If it is not working, I'd suggest to start the Admin and SOA server without node manager first. Then start your node manager and see if it is reachable from the WLS console. Then shut down your SOA server from command prompt and restart your SOA server from WLS console.
Verify the Listen Address of your Node Manager and start your node manager from command prompt by explicitly specifying the same address and port.
As WLS console internally uses node manager only to start your server, you would not need to use WLST scripts to do the same and only SOA server needs to be started using node manager.
Regards,
Neeraj Sehgal
Hi Neeraj,
I made sure that in the weblogic console, in the machines tab, local machine-->configuration--->Node Manager, I have given the correct Listen Address (Narsing-PC) and the listen port 5556.
I have made sure the property StartScriptEnabled= true.
I have started the admin server through startWebLogic.cmd command, now i start the node manager by going to the C:\Oracle\Middleware\wlserver_10.3\server\bin and running the command startNodeManager.cmd, then i go to the weblogic console--->servers--->control--->soa_server1--->start , it is going to FAILED_NOT_RESTARTABLE status.
If i see the log messages in the nodemanager.log, this is the below message...
<Jun 28, 2012 11:25:09 PM> <INFO> <soa_domain> <soa_server1> <Server output log file is 'C:\Oracle\Middleware\user_projects\domains\soa_domain\servers\soa_server1\logs\soa_server1.out'>
<Jun 28, 2012 11:25:11 PM> <INFO> <soa_domain> <soa_server1> <Server failed during startup so will not be restarted>
<Jun 28, 2012 11:25:11 PM> <WARNING> <Exception while starting server 'soa_server1'>
java.io.IOException: Server failed to start up. See server output log for more details.
 at weblogic.nodemanager.server.AbstractServerManager.start(AbstractServerManager.java:196)
 at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:23)
 at weblogic.nodemanager.server.Handler.handleStart(Handler.java:609)
 at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:121)
 at weblogic.nodemanager.server.Handler.run(Handler.java:71)
 at java.lang.Thread.run(Thread.java:662)
The log message in the soa_server1.out file is as below...
Starting WLS with line:
C:\Oracle\MIDDLE~1\JDK160~1\bin\java -client -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8453,server=y,suspend=n -Djava.compiler=NONE -Xms512m -Xmx1024m -XX:PermSize=128m -XX:MaxPermSize=512m -Dweblogic.Name=soa_server1 -Djava.security.policy=C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.policy -Dweblogic.system.BootIdentityFile=C:\Oracle\Middleware\user_projects\domains\soa_domain\servers\soa_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=C:\Oracle\MIDDLE~1\WLSERV~1.3 -Dwls.home=C:\Oracle\MIDDLE~1\WLSERV~1.3\server -Dweblogic.home=C:\Oracle\MIDDLE~1\WLSERV~1.3\server -Dcommon.components.home=C:\Oracle\MIDDLE~1\ORACLE~1 -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Ddomain.home=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1 -Djrockit.optfile=C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrocket_optfile.txt -Doracle.server.config.dir=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1\config\FMWCON~1\servers\soa_server1 -Doracle.domain.config.dir=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1\config\FMWCON~1 -Digf.arisidbeans.carmlloc=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1\config\FMWCON~1\carml -Digf.arisidstack.home=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1\config\FMWCON~1\arisidprovider -Doracle.security.jps.config=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1\config\fmwconfig\jps-config.xml -Doracle.deployed.app.dir=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1\servers\soa_server1\tmp\_WL_user -Doracle.deployed.app.ext=\- -Dweblogic.alternateTypesDirectory=C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.ossoiap_11.1.1,C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.oamprovider_11.1.1 -Djava.protocol.handler.pkgs=oracle.mds.net.protocol"|"oracle.fabric.common.classloaderurl.handler"|"oracle.fabric.common.uddiurl.handler"|"oracle.bpm.io.fs.protocol -Dweblogic.jdbc.remoteEnabled=false -Doracle.security.jps.policy.migration.validate.principal=false -da:org.apache.xmlbeans... -Dbpm.enabled=true -Dsoa.archives.dir=C:\Oracle\Middleware\Oracle_SOA1\soa -Dsoa.oracle.home=C:\Oracle\Middleware\Oracle_SOA1 -Dsoa.instance.home=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1 -Dtangosol.coherence.clusteraddress=227.7.7.9 -Dtangosol.coherence.clusterport=9778 -Dtangosol.coherence.log=jdk -Djavax.xml.soap.MessageFactory=oracle.j2ee.ws.saaj.soap.MessageFactoryImpl -Dweblogic.transaction.blocking.commit=true -Dweblogic.transaction.blocking.rollback=true -Djavax.net.ssl.trustStore=C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\DemoTrust.jks -Dem.oracle.home=C:\Oracle\Middleware\oracle_common -Djava.awt.headless=true -Dbam.oracle.home=C:\Oracle\Middleware\Oracle_SOA1 -Dums.oracle.home=C:\Oracle\Middleware\Oracle_SOA1 -Dweblogic.management.discover=false -Dweblogic.management.server=http://localhost:7001 -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=C:\Oracle\MIDDLE~1\patch_wls1036\profiles\default\sysext_manifest_classpath;C:\Oracle\MIDDLE~1\patch_oepe180\profiles\default\sysext_manifest_classpath;C:\Oracle\MIDDLE~1\patch_ocp371\profiles\default\sysext_manifest_classpath;C:\Oracle\MIDDLE~1\patch_adfr1111\profiles\default\sysext_manifest_classpath weblogic.Server
FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
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]
<Jun 28, 2012 11:25:11 PM> <FINEST> <NodeManager> <Waiting for the process to die: 4808>
<Jun 28, 2012 11:25:11 PM> <INFO> <NodeManager> <Server failed during startup so will not be restarted>
<Jun 28, 2012 11:25:11 PM> <FINEST> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>
Someone please help, if i am able to start the soa manged server, i can go ahead and install the AIA Foundation pack...
Many Thanks.

Adding patch jar file while starting Managed Server through Node Manager

Hi,
I am using Weblogic Express 10.0 on Linux env, Jrockit JVM.
I have a patch jar file from BEA, I added it to Weblogic start script, when I start the Managed server by using startManagedWeblogic.sh script, I can see that patch jar file is added to classpath when I grep for Java process.(ps -ef | grep -i java).
But when I start the Managed server through NodeManager and grep for java process, I dont see the patch jar file added to classpath of Managed server process which is started.
Can someone let me know if I have to add the patch jar file somewhere else along with Weblogic start script if starting Managed server through Node Manager?
Weblogic Consultant

Thanks for your response.
I found another way to do this.
Edit nodemanager.properties file and set StartScriptEnabled=true (By default it is false), and then restart the Node Manager process.
Enabling this setting to true will enable the NodeManager process to use startManagedWeblogic.sh script while starting the managed server, all the added jar files, memory settings will be taken from start script of Weblogic
Weblogic Consultant

[wls8.1 sp.3] cannot remote start with node manager on another server

In this domain run on 2 physical servers in windows 2003. In machine that has admin server can start with node manager but another machine without admin server cannot remote start . when i remote start , the node manager has facing error messages as below:
# AT "node manager monitoring" in weblogic admin console
[[NodeManager:300033]Could not execute command ping on the node manager. Reason: weblogic.nodemanager.NodeManagerException: [CommandInvoker: Failed to send command: 'ping to server 'null' to NodeManager at host: 'xxx.xxx.xxx.24:5555' with exception Connection reset by peer.. Please ensure that the NodeManager is active on the target machine].]
# AT "nodemanger.log" has facing error messages as below:
<Aug 20, 2008 7:34:07 PM ICT> <Info> <[email protected]:5555> <NodeManage r started, log messages being written into file C:\bea\WEBLOG~1\common\NODEMA~1\ NodeManagerLogs\NodeManagerInternal\nm_server02_08_20_2008-19_34_03.log>
<Aug 20, 2008 7:59:58 PM ICT> <Warning> <Security> <BEA-090476> <Invalid/unknown SSL header was received from peer server01 - 10.208.50.23 during SSL handsha ke.> <Aug 20, 2008 8:00:11 PM ICT> <Warning> <Security> <BEA-090476> <Invalid/unknown SSL header was received from peer server01 - xxx.xxx.xxx.23 during SSL handsha key.>
I would REALLY appreciate any suggestions as to what might be the cause or what i could try.
Thanks ....

Hi,
It is up to you to decide whether you want to use nodemanager or not.
It does not make any difference if the server is started via script or nodemanager.
if i want everything (AS, MS, and NM) to come up at server boot i need to set each of them up as windows services (which is what i have at the moment) but this wont allow me to use the node manager ==> Yes this statement is correct.
You can either set AS and MS as windows service (or) AS and nodemanager as service.
Thanks,
Sharmela

JVM Initialization Error when Starting the Second Managed Server

Hi,
I am getting the below error when starting the 2nd Managed server on Solaris X86 machine.
starting weblogic with Java version:
java version "1.5.0_17"
Java(TM) Platform, Standard Edition for Business (build 1.5.0_17-b04)
Java HotSpot(TM) Client VM (build 1.5.0_17-b04, mixed mode, sharing)
Starting WLS with line:
/usr/jdk/instances/jdk1.5.0/bin/java -client -Xms256m -Xmx512m -XX:CompileThre shold=8000 -XX:PermSize=48m -XX:MaxPermSize=128m -Xverify:none -da -Dplatform .home=/beafiler/weblogic10g/bea/wlserver_10.0 -Dwls.home=/beafiler/weblogic10g/b ea/wlserver_10.0/server -Dweblogic.home=/beafiler/weblogic10g/bea/wlserver_10.0/ server -Dwli.home= -Dweblogic.management.discover=false -Dweblogic.management.s erver=http://test_admin:7001 -Dwlw.iterativeDev=false -Dwlw.testConsole=false - Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=/beafiler/weblogic10g/bea/patch_wss 110/profiles/default/sysext_manifest_classpath:/beafiler/weblogic10g/bea/patch_w lw1021/profiles/default/sysext_manifest_classpath:/beafiler/weblogic10g/bea/patc h_wls1002/profiles/default/sysext_manifest_classpath:/beafiler/weblogic10g/bea/p atch_cie640/profiles/default/sysext_manifest_classpath -Dweblogic.security.provi ders.authentication.LDAPDelegatePoolSize=50 -Dweblogic.Name=wls_test2 -Djava.sec urity.policy=/beafiler/weblogic10g/bea/wlserver_10.0/server/lib/weblogic.policy weblogic.Server
Error occurred during initialization of VM
Could not reserve enough space for object heap
Can any one please help me troubleshoot this?
Edited by: user4877326 on Jul 13, 2010 1:33 PM

Hi P.k,
The table QRTZ92_TRIGGERS is there in the database.But while trying to run this command (UPDATE QRTZ92_TRIGGERS set NEXT_FIRE_TIME=1 where NEXT_FIRE_TIME < 0)in database i am getting the table or view does not exist.
What is GTC resource?
OIM version - 11.1.1.5.0.
-Deena.

Issue With Business Objects Installation-STW00213 The Central Management Server has failed to start.

Hi,
I am in the process of installing Business Objects XI 3.1 in one of our server. While installing I am getting the error 'The Central Management Server has failed to start. Press 'retry' to attempt to start it again or 'cancel' to skip any actions dependendent on the Central Management Server. STW00213.'
I have tried re-installing the BO, and also tried installing without giving admin password. But it doesn't work. And also I ahve tried giving the passwords of database and CMS Admin without Sepcia Characters. But it also doesn't work.
If I cancel and install the BO, Server Intelligence Agent is not available in Central Management Server.
Could anyone help on this issue?
Thanks
Prakadesh

Hi Prakadesh,
Try these steps.
1. Stop and disable the service of current SIA. You can do it from start-->run services.msc. Double click the SIA service and change the status to disable.
2. Login into sqlplus and drop all the CMS tables.
3. Create a new SIA pointing to Oracle from the CCM.
4. Start the new SIA and check if all services come up and you are able to login into Manager servers.
If this does not work, check the event viewer for error messages.
Regards
Chinmaya

REP-52266: The in-process Reports Server rep_myhostname failed to start

Hi Everyone,
My name is John and I've a small 10g report configuration issue which I would like to share and, hopefully, some of you might already have come across it and able to assist and guide me through it.
First, I've installed Oracle Developer Suite 10g 10.1.2.0.2 together with Report Builder 10.1.2.0.2 and Oracle Forms Developer 10.1.2.0.2 onto a 32bit Window 2000 Professional machine.
I've tried to run the following URL which test for the servlet connectivity and it returns fine with all the valid reports servlet commands page.
http://myhostname:8889/reports/rwservlet
However, as I've tried to run the 'test.rdf' report using the following link:
http://myhostname:8889/reports/rwservlet?destype=cache&desformat=PDF&report=test.rdf&userid=user/pass@host
And it returns the following error on the browser:
REP-52266: The in-process Reports Server rep_myhostname failed to start.oracle.reports.RWException: IDL:oracle/reports/RWException:1.0
Then I set trace option on in the myhostname.conf file and restart the OC4J instance. And the trace file has the following results:
*[2009/2/18 11:21:31:687] Info 56021 (EngineManager:spawnEngine): Engine rwURLEng-0 has been launched*
*[2009/2/18 11:21:31:687] State 56004 (EngineInfo:setState): Engine rwURLEng-0 state is: Initial*
*[2009/2/18 11:21:31:687] Debug 50103 (JobStore:writePersistFile): Purge persistent file*
*[2009/2/18 11:21:31:717] Debug 50103 (JobStore:writePersistFile): Purge persistent file done*
*[2009/2/18 11:21:51:766] Warning 50103 (EngineManager:registerEngine): REP-55103: API URLEngine:getEngineEnvs not applicable to URL engine*
*[2009/2/18 11:21:51:766] Info 56026 (EngineManager:registerEngine): Reports Server started up engine rwURLEng-0*
*[2009/2/18 11:21:51:856] Debug 50103 (EngineManager:updateEngineState): Engine rwURLEng-0 status is 1*
*[2009/2/18 11:21:51:856] State 56004 (EngineInfo:setState): Engine rwURLEng-0 state is: Ready*
*[2009/2/18 11:23:1:687] Info 56106 (EngineManager:manage): Engine rwEng-0 is destroyed due to timeout*
*[2009/2/18 11:23:1:687] Exception 56097 (): Engine rwEng-0 callback timeout*
oracle.reports.RWException: IDL:oracle/reports/RWException:1.0
*     at oracle.reports.utility.Utility.newRWException(Utility.java:756)*
*     at oracle.reports.server.EngineManager.manage(EngineManager.java:291)*
*     at oracle.reports.server.IdleThread.run(IdleThread.java:88)*
*[2009/2/18 11:23:1:707] Debug 50103 (ServerPacketReceiver:handlePacket): Got a request packet*
*[2009/2/18 11:23:1:717] Info 56029 (EngineManager:shutdownEngine): Shutting down engine rwURLEng-0*
*[2009/2/18 11:23:1:717] State 56004 (EngineInfo:setState): Engine rwURLEng-0 state is: Shutdown*
*[2009/2/18 11:23:1:727] Info 56047 (EngineManager:remove): Reports Server shut down engine rwURLEng-0*
*[2009/2/18 11:23:5:813] Info 50103 (ServerPacketHandler:stop): Multicastmanager stopped successfully*
*[2009/2/18 11:23:5:813] Info 50002 (RWServer:shutdown): Server is shutting down*
*[2009/2/18 11:23:5:813] Info 50103 (RWServer:startServer): Notify thread to exit*
*[2009/2/18 11:23:5:843] Info 50103 (RWServer:startServer): RWServer thread exits*
*[2009/2/18 11:23:5:843] Exception 56097 (): Engine rwEng-0 callback timeout*
oracle.reports.RWException: IDL:oracle/reports/RWException:1.0
*     at oracle.reports.utility.Utility.newRWException(Utility.java:756)*
*     at oracle.reports.server.EngineManager.manage(EngineManager.java:291)*
*     at oracle.reports.server.IdleThread.run(IdleThread.java:88)*
I've not changed any of the report's related configuration files and the java version of the machine is 1.4.2_06. I do not know whether I need to apply a patch for this particular Developer Suite version or is there something which I've not done in terms of post-installation tasks. Thank you for your time and effort. Any feedback is much appreciated as I've been spending a number of days to solve this problem. Thank you and have a nice day.
Kind Regards,
John

Hi,
Thanks for your reply and here is the output of the rwEng-0.trc file. I could not find anything "interesting" as you mentioned. Please let me know if you find anything missing in there. Also, currently there is only one network printer setup on the machine. Can you please elaborate on the printer bit as I'm unsure of what to troubleshoot. Also, I forgot to inform you that I have a previous version of Developer 2000 Form and Report installed prior to the 10g Developer Suite installation. Does it ring a bell to any other problem? Thank you again for your time and effort. Have a nice day.
Kind Regards,
John
*[2009/2/18 11:21:35:773] Debug 50103 (RWEngine:init): args[0]=name=rwEng-0*
*[2009/2/18 11:21:35:773] Debug 50103 (RWEngine:init): args[1]=server=rep_myhostname*
*[2009/2/18 11:21:35:773] Debug 50103 (RWEngine:init): args[2]=ORACLE_HOME=C:\oracle\ora10g1*
*[2009/2/18 11:21:35:773] Debug 50103 (RWEngine:init): args[3]=engineimplclass=oracle.reports.engine.EngineImpl*
*[2009/2/18 11:21:35:773] Debug 50103 (RWEngine:init): args[4]=traceopts=trace_all*
*[2009/2/18 11:21:35:773] Debug 50103 (RWEngine:init): args[5]=tracefile=C:\oracle\ora10g1\reports\logs\rep_EZRA\rwEng-0.trc*
*[2009/2/18 11:21:35:773] Debug 50103 (RWEngine:init): args[6]=tracemode=trace_replace*
*[2009/2/18 11:21:35:773] Debug 50103 (RWEngine:init): args[7]=cacheDir=C:\oracle\ora10g1\reports\cache*
*[2009/2/18 11:21:35:783] Debug 50103 (RWEngine:init): args[8]=server_ior=C:\TEMP\tmp_1440568*
*[2009/2/18 11:21:36:284] Info 50128 (RWEngine:init): orb init succeeded*
*[2009/2/18 11:21:37:45] Info 55007 (EngineImpl:loadLibrary): Load rw.dll succeeded*
*[2009/2/18 11:21:37:45] Debug 50103 (EngineImpl:init): useDataCache = null*
*[2009/2/18 11:21:37:45] Debug 50103 (EngineImpl:init): ignoreDataParameter = null*
*[2009/2/18 11:21:37:75] Debug 50103 (EngineImpl:EngineImpl): start CInitEngine()*
*[2009/2/18 11:21:37:75] Debug 50103 (EngineImpl:EngineImpl): commandline[0] = rw*
*[2009/2/18 11:21:37:75] Debug 50103 (EngineImpl:EngineImpl): commandline[1] = ora_rw20_3tng*
*[2009/2/18 11:21:37:75] Debug 50103 (EngineImpl:EngineImpl): commandline[2] = rep_myhostname*
*[2009/2/18 11:21:37:75] Debug 50103 (EngineImpl:EngineImpl): commandline[3] = C:\oracle\ora10g1\reports\cache*
*[2009/2/18 11:21:37:85] Debug 50103 (EngineImpl:EngineImpl): commandline[4] = null*
*[2009/2/18 11:21:37:85] Debug 50103 (EngineImpl:EngineImpl): commandline[5] = null*
*[2009/2/18 11:21:37:85] Debug 50103 (EngineImpl:EngineImpl): commandline[6] = trace_all*
*[2009/2/18 11:21:37:85] Debug 50103 (EngineImpl:EngineImpl): commandline[7] = C:\oracle\ora10g1\reports\logs\rep_EZRA\rwEng-0.trc*
*[2009/2/18 11:21:37:85] Debug 50103 (EngineImpl:EngineImpl): commandline[8] = trace_replace*
*[2009/2/18 11:21:37:85] Debug 50103 (EngineImpl:EngineImpl): commandline[9] = null*
*[2009/2/18 11:21:37:85] Debug 50103 (EngineImpl:EngineImpl): commandline[10] = null*
*[2009/2/18 11:21:37:85] Debug 50103 (EngineImpl:EngineImpl): commandline[11] = null*

Trusted CA Certificate Ignored When Connecting To Node Manager

I have a question about Node Manager.
I have the following configuration:
OS: Linux (CentOS 5.4) 32bit
Oracle WebLogic Server 11gR1 (10.3.2)
Portal, Forms, Reports and Discoverer (11.1.1.2.0) - only Forms and Reports are installed and configured
All configured components start successfuly, but I receive the following security related messages when I connect to Node Manager.
java -Dweblogic.security.SSL.ignoreHostnameVerification=true -Dweblogic.security.TrustKeyStore=DemoTrust weblogic.WLST
Initializing WebLogic Scripting Tool (WLST) ...
Welcome to WebLogic Server Administration Scripting Shell
Type help() for help on available commands
wls:/offline> nmConnect('weblogic', <weblogic password>, 'icweb001', '5556', <domain name>)
Connecting to Node Manager ...
<Nov 25, 2009 3:35:35 PM EST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 3,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Nov 25, 2009 3:35:35 PM EST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 2,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
Successfully Connected to Node Manager.
wls:/nm/DynaMed>I understand that the two BEA-090898 messages associated with the specified certificates are informational, but is there anything I can do to either,
1) correct the certificate so the messages are not generated, or
2) change my setup so that the messages are not displayed?
Thanks in advance for your help.

The certificates at issue belong to the $JAVA_HOME keystore in weblogic
$JAVA_HOME/jre/lib/security/cacerts
ttelesecglobalrootclass3ca, Feb 10, 2009, trustedCertEntry,
ttelesecglobalrootclass2ca, Feb 10, 2009, trustedCertEntry,I was able to stop the warning messages from appearing when connecting to node manager, by removing these two certificates from the $JAVA_HOME/jre/lib/security/cacerts keystore.
cd $JAVA_HOME/jre/lib/security
cp -p cacerts cacerts.original
chmod 644 cacerts
keytool -delete -alias ttelesecglobalrootclass2ca -keystore cacerts
keytool -delete -alias ttelesecglobalrootclass3ca -keystore cacerts
chmod 444 cacerts cacerts.originalOnce the certs are removed from the keystore, the warning messages no longer appear when connecting to node manager.
Some additional information on these two certificates can be found at:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6803022Edited by: wblum on Feb 18, 2010 1:10 PM

Start the node manager and rerun the command

Seeing the following in weblogic server log. When will I get this error? And how to retun node manager ?
The node manager at host ....and port 5555 seems to be down. Start the node manager and rerun the command.

You will get this message when the machine's NodeManager was not started.
Take a look at the following links to see how to install and start the Node Manager:
http://e-docs.bea.com/wls/docs81/adminguide/nodemgr.html#1150128
http://e-docs.bea.com/wls/docs81/adminguide/confignodemgr.html#1142955

'Failed to start Light Display Manager'

Introduction removed
I'm having some trouble with xorg, 'startx' refused to work (I have xorg-server obviously). I read symlinks and configs that are meant to be present in /etc and /usr, and I can't detect anything abnormal. I have the non-proprietary xf86-video-intel drivers installed, and I don't think any config is required on those.
And of course, the PC won't boot directly into the OS now, with the message:
[FAILED] Failed to start Light Display Manager.
See 'systemctl status lightdm.service' for details.
[OK] Reached target Graphical Interface.
I have no way of typing into the console, and therefore logging on, when this error is present.
Last edited by Paspie (2014-04-12 19:48:56)

https://wiki.archlinux.org/index.php/Sy … _boot_into
EDIT: you'd want to specify the multi-user target. If you need help adding this to your kernel line while booting up, this would depend on which boot loader you use. With grub legacy you'd hit 'e' on the menu screen to edit the kernel parameters. With syslinux it is tab ... I think. With the new grub, I'm not sure, it may still be 'e'.
Last edited by Trilby (2014-05-27 12:08:53)

LS AppDomain Host Process, Failed to start Fabric Pool Manager.

Hi,
Today renewed the
Certificate in and the server will not start.
Can someone help me.
I've tried for several hours to fix it.
System
Provider
[ Name]
LS AppDomain Host Process
EventID
50006
[ Qualifiers]
50181
Level
2
Task
1029
Keywords
0x80000000000000
TimeCreated
[ SystemTime]
2015-02-21T22:57:29.000000000Z
EventRecordID
6508871
Channel
Lync Server
Computer
srvlync.itexpert.pl
Security
EventData
System.ApplicationException: Failed to start Fabric Pool Manager. at Microsoft.Rtc.AppDomainHost.Launcher.Initialize(String[] args) at Microsoft.Rtc.AppDomainHost.Launcher.Main(String[] args)
System
Provider
[ Name]
LS Server
EventID
12330
[ Qualifiers]
50152
Level
2
Task
1000
Keywords
0x80000000000000
TimeCreated
[ SystemTime]
2015-02-21T23:00:06.000000000Z
EventRecordID
6508872
Channel
Lync Server
Computer
srvlync.itexpert.pl
Security
EventData
C:\Program Files\Microsoft Lync Server 2013\Server\Core\RtcHost.exe
C3E8302D
The worker process failed to initialize itself in the maximum allowable time.

Hi,
It can be the issue with Windows Fabric service.
Please try to Repair the Window Fabric Component with the following steps:
1. Stop Lync Services
2. Remove Windows Fabric application
3. Don’t Restart
4. Install Windows Fabric (C:\Sources\WindowsFabric)
5. Restart Windows
6. Confirm Windows
Fabric Service starts
Then test the issue again.
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Re: Starting a node manager with rsh

FYI,
rsh remote "start_nodemgr > /dev/null" did the trick
Even though the start_nodemgr output came back to my remote window it
seemed to tie up the remote shell.
Thanks for the help
Orsini, Francois wrote:
Hi,
Haven't you tried:
rsh remote "nohup start_nodemgr > /dev/null &"
or
rsh remote "start_nodemgr > /dev/null &"
instead of < /dev/null ....
--francois
From: Chukk Haselhorst
Sent: Thursday, April 03, 1997 1:03 PM
To: forte-users
Subject: Starting a node manager with rsh
Environment : Forte 2F2, RS6000/AIX 4.1.5
I'm trying to use rsh to start a node manager on a remote system. >>The problem that I'm experiencing is that the node manager starts but >>the rsh doesn't return. I have to Ctrl-C to end the rsh. I've tried :
rsh remote start_nodemgr
rsh remote "start_nodemgr &"
rsh remote "start_nodemgr < /dev/null"
rsh -n remote start_nodemgr
rsh "nohup start_nodemgr &"
and others. If I rlogin to the remote system and start the node mgr >> the shell tells me that I have running jobs when I try to exit even >> though the jobs command doesn't show anything running. I am able to >> exit on the second try.
What do I need to do to be able to remotely start the node manager
without logging in and logging out.
Thanks in advance
Chukk Haselhorst

I have resolved the issue buy setting NativeVersionEnabled=falase in nodemanager.properties

Starting a node manager with rsh

Environment : Forte 2F2, RS6000/AIX 4.1.5
I'm trying to use rsh to start a node manager on a remote system. The
problem that I'm experiencing is that the node manager starts but the
rsh doesn't return. I have to Ctrl-C to end the rsh. I've tried :
rsh remote start_nodemgr
rsh remote "start_nodemgr &"
rsh remote "start_nodemgr < /dev/null"
rsh -n remote start_nodemgr
rsh "nohup start_nodemgr &"
and others. If I rlogin to the remote system and start the node mgr the
shell tells me that I have running jobs when I try to exit even though
the jobs command doesn't show anything running. I am able to exit on
the second try.
What do I need to do to be able to remotely start the node manager
without logging in and logging out.
Thanks in advance
Chukk Haselhorst

I have resolved the issue buy setting NativeVersionEnabled=falase in nodemanager.properties

REP-52266: The in-process Reports Server rep_adminserver_ikit_asinst_1 failed to start.oracle.reports.RWException: IDL:oracle/reports/RWException:1.0

Hi,
I have installed oracle forms and reports 11gR2 on Windows 7 Professional 64bit (and configured in development mode), the forms are working fine but when i run a report i get this message
REP-52266: The in-process Reports Server rep_adminserver_ikit_asinst_1 failed to start.oracle.reports.RWException: IDL:oracle/reports/RWException:1.0

I was trying to add a new destination:
<destination class="oracle.reports.server.DesMail" destype="mail"/>
I couldn't make it work , so I commented my changes.
In fact, I should have gone back to a backup file , as weblogic seemed to have changed the file itself!! (attributes of the xml tags were in different order, and more things ...) but just undoing what I have done did the trick.
This file seems to be quite picky, I left this tag uncommented
</pluginParam>
and the same REP-5226 error happened.

Admin Server 4 fails to start up with new Internet Protocol (IP) address

By default, the Netscape Admin Server 4.x uses the Internet Protocol (IP)
address that was entered in its configuration at the time the server was
installed. However, if a system administrator decides to change the IP address,
the server will fail to start. 

The following is an example of the error message: 

# ./start-admin
Info: Cache expiration set to 600 seconds
Netscape-Administrator/4.0 B99.035.2034
startup failure: could not bind to port 4050, IP address 208.12.45.56 (Invalid
Argument)
The error log will show: 
[29/Oct/1999:11:32:58] info: successful server startup
[29/Oct/1999:11:32:58] info: Netscape-Administrator/4.0 B99.035.2034
[29/Oct/1999:11:32:58] failure: startup failure: could not bind to port 4050,
IP address 208.12.45.56 (Cannot assign requested address)

In addition, if the system administrator manually clears the IP address for the Admin
Server in Console (by clicking the Configuration tab, clicking the Network tab,
selecting Process Settings, and then selecting IP Address), the server will
also fail to start. The following are examples of the error message and error
log entries.
 
# ./start-admin
Info: Cache expiration set to 600 seconds
Netscape-Administrator/4.0 B99.165.2023
startup failure: could not bind to port 4100, IP address
(Directory open error)
The error log will show: 
[03/Dec/1999:09:32:43] info: successful server startup
[03/Dec/1999:09:32:43] info: Netscape-Administrator/4.0 B99.165.2023
[03/Dec/1999:09:32:43] failure: startup failure: could not bind to port 4100,
IP address (Error 0)

These problems affect both Admin Server 4.0 and 4.1.

(See attachment)

Hi Laurent,
although I was given the advice earlier that I should simply take the machine back to the shop, or call the help centre, I ended up just praying that it would be OK. A couple of days after I posted the message I think there was an update to download and install, just a regular one from Apple from the Software Update option for the operating system or it may have been one for Final Cut Pro X, and once it installed I never had the problem again, so my prayers were answered.
It was pretty scary at the time because I thought it must be some hardware malfunction, but because it was resolved through an update it suggested it was a software issue. Hopefully it is the same with you.
I'm now running 10.7.2 and have had no recurrence of the problem in many months, thankfully.
It might have nothing to do with it, but the only other two things that may have somehow caused errors in the system startup (and I doubt these will be "unrelated" to people who know how computers work better than I do, but I feel I should mention them just in case), but I also updated Final Cut Pro X from a glitchy version to version 10.0.2 around the same time, and I also had an application installed which didn't function correctly in OS10.7 called PowerController (a simple app that can start up the computer at a set time and play music from iTunes as an alarm clock) and it was in the group of apps that were set to start at the starting up of the computer.
Anyway, I hope your problem is resolved as easily. Pray about it too!

Server state failed when starting through node manager

Similar Messages

Maybe you are looking for