Managed server will not start

Question

I have a new WebLogic 10 server and none of the new app servers will start. Gets the message "the Node Manager associated with machine sitportal1 is not reachable.
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. " When I check the node manager logs (node manager service IS running) it has the error lsited below. I found this solution but not sure how to check or verify it. *Solution:
It could be that the CA certificates sent to the server are being shown in the wrong order for the chain. Review the CAs and see if the order such as Public, Intermediate, Root CA is respected. *
Any guidance would be appreciated and points awarded. Thanks
Dec 23, 2008 2:46:59 PM> <Warning> <Uncaught exception in server handler: javax.net.ssl.SSLKeyException: [Security:090482]BAD_CERTIFICATE alert was received from 127.0.0.1 - 127.0.0.1. Check the peer to determine why it rejected the certificate chain (trusted CA configuration, hostname verification). SSL debug tracing may be required to determine the exact reason the certificate was rejected.>
javax.net.ssl.SSLKeyException: [Security:090482]BAD_CERTIFICATE alert was received from 127.0.0.1 - 127.0.0.1. Check the peer to determine why it rejected the certificate chain (trusted CA configuration, hostname verification). SSL debug tracing may be required to determine the exact reason the certificate was rejected.
     at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireException(Unknown Source)
     at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireAlertReceived(Unknown Source)
     at com.certicom.tls.record.alert.AlertHandler.handle(Unknown Source)
     at com.certicom.tls.record.alert.AlertHandler.handleAlertMessages(Unknown Source)
     at com.certicom.tls.record.MessageInterpreter.interpretContent(Unknown Source)
     at com.certicom.tls.record.MessageInterpreter.decryptMessage(Unknown Source)
     at com.certicom.tls.record.ReadHandler.processRecord(Unknown Source)
     at com.certicom.tls.record.ReadHandler.readRecord(Unknown Source)
     at com.certicom.tls.record.ReadHandler.readUntilHandshakeComplete(Unknown Source)
     at com.certicom.tls.interfaceimpl.TLSConnectionImpl.completeHandshake(Unknown Source)
     at com.certicom.tls.record.ReadHandler.read(Unknown Source)
     at com.certicom.io.InputSSLIOStreamWrapper.read(Unknown Source)
     at sun.nio.cs.StreamDecoder$CharsetSD.readBytes(StreamDecoder.java:411)
     at sun.nio.cs.StreamDecoder$CharsetSD.implRead(StreamDecoder.java:453)
     at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:183)
     at java.io.InputStreamReader.read(InputStreamReader.java:167)
     at java.io.BufferedReader.fill(BufferedReader.java:136)
     at java.io.BufferedReader.readLine(BufferedReader.java:299)
     at java.io.BufferedReader.readLine(BufferedReader.java:362)
     at weblogic.nodemanager.server.Handler.run(Handler.java:66)
     at java.lang.Thread.run(Thread.java:595)

Answer 1

Hii
This is a Common Error.
1.Make sure your Admin Server is in Running mode.
2.Make sure that your Managed Server is in shutdown mode.
3.Make sure that your domain mapping is correct.
4.Any domain created before creation of Node Manager Service will not be accessible via node Manager(even after restarting node manager), solution is to run the WLST command “nmEnroll” to enroll that domain with the Node Manager.
Here are the steps to do "nmEnroll".
Example:
cd $BEA_HOME\user_projects\domains\<domain_name>\bin
setDomainEnv.cmd
java weblogic.WLST
wls> connect(‘weblogic’,'weblogic’,
‘t3://mymachine.mydomain:7001′)
wls> nmEnroll(‘C:\bea\user_projects\domains/<domainName>’, ‘C:\bea\wlserver_<version>/common/nodemanager’)
5.Start your Node Manager and look for the logs where it specifies the Domain Mapping Path.
6.Verify the domain path.
7.Now Start your Managed Server.