• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

NodeManager Error in WLS81

 
Ranch Hand
Posts: 79
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,
Plz help me with this.
I have a Linux Box and I have installed a WebLogic Domain in it.
In the same Linux box I have Admin Server and Managed Server.
Now I started the admin server and I started the nodemanager listening at the box's IP address at port 5555. Now from the browser/console, I am trying to start the managed server but I am not able to start it.
I am getting the following erros:



<Nov 19, 2004 5:24:01 PM CST> <Info> <NodeManager@10.194.219.135:5555> <Starting Server dizzyDomain: izzy1 ...>
<Nov 19, 2004 5:24:01 PM CST> <Info> <NodeManager@10.194.219.135:5555> <BaseProcessControl: saving process id of Weblogic Managed server 'dizzy1', pid: 5391>
<Nov 19, 2004 5:24:03 PM CST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with BEA WebLogic JRockit(TM) 1.4.2_04 JVM Version ari-31788-20040616-1032-linux-ia32 from BEA Systems, Inc.>
<Nov 19, 2004 5:24:04 PM CST> <Info> <Management> <BEA-141140> <The managed server is going to contact the admin server at http://10.194.219.135:7001 to check if there exists a running admin server at this URL.>
<Nov 19, 2004 5:24:04 PM CST> <Info> <Configuration Management> <BEA-150017> <This server is being started as a dependent managed server.>
<Nov 19, 2004 5:24:04 PM CST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 8.1 SP3 Tue Jun 29 23:11:19 PDT 2004 404973
WebLogic XMLX Module 8.1 SP3 Tue Jun 29 23:11:19 PDT 2004 404973 >
<Nov 19, 2004 5:24:04 PM CST> <Info> <Configuration Management> <BEA-150015> <Connecting to the administration server http://10.194.219.135:7001 to retrieve the initial configuration.>
<Nov 19, 2004 5:24:06 PM CST> <Notice> <Log Management> <BEA-170019> <The server log file /home/c1ddewan/bea/weblogic81/common/nodemanager/dizzy1/dizzy1.log is opened. All server side log events will be written to this file.>
<Nov 19, 2004 5:24:09 PM CST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Nov 19, 2004 5:24:10 PM CST> <Notice> <Security> <BEA-090170> <Loading the private key stored under the alias DemoIdentity from the jks keystore file /home/c1ddewan/bea/weblogic81/server/lib/DemoIdentity.jks.>
<Nov 19, 2004 5:24:10 PM CST> <Notice> <Security> <BEA-090171> <Loading the identity certificate stored under the alias DemoIdentity from the jks keystore file /home/c1ddewan/bea/weblogic81/server/lib/DemoIdentity.jks.>
<Nov 19, 2004 5:24:10 PM CST> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file /home/c1ddewan/bea/weblogic81/server/lib/DemoTrust.jks.>
<Nov 19, 2004 5:24:10 PM CST> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file /home/c1ddewan/bea/jrockit81sp3_142_04/jre/lib/security/cacerts.>
***************************************************************************
<Nov 19, 2004 5:24:11 PM CST> <Warning> <Security> <BEA-090504> <Certificate chain received from bbmklrp99 - 10.194.219.135 failed hostname verification check. Certificate contained bbmkxl6b but check expected bbmklrp99>
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.'
<Nov 19, 2004 5:24:11 PM 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 : [Security:090504]Certificate chain received from bbmklrp99 - 10.194.219.135 failed hostname verification check. Certificate contained bbmkxl6b but check expected bbmklrp99>
Reason: weblogic.management.configuration.ConfigurationException: Due to faulty SSL configuration, this server is unable to establish a connection to the node manager.
<Nov 19, 2004 5:24:11 PM 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.>


I even tried changing Host Verification to NONE. but even then it is not working.
It is not in the production environment so I dont really care about the security right now.
Just want this stuff to be up and running.

Plz reply me asap
Thanks in advance.



Deepak
 
Greenhorn
Posts: 9
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,

I have no much idea as I am pursuing weblogic but can suggest you few things.

1. Check the Listen Address of the node maneger and port.
2. After proper address and port click on monitoring and check it should not give any error.

Now move further........

Best of luck,
Rajat
 
Deepak Dew
Ranch Hand
Posts: 79
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi ,
I could solve the problem.
In the console, managed-server->config->keystore ->advance option
choose HostName verifier Not reqd.

Thanks

Deepak
 
Ranch Hand
Posts: 977
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,

tanks for the information, I had the same problem an was able to fix it after reading your post...


regards.
 
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Alternatly, supposing that you dont care about you right setup and security,
you can define your hosts just wirting your ip address and host name
example:
10.11.96.113 XPTO23.bigapple.com. XPTO23
try restart your server and nodemanager instance.
thank you.
 
reply
    Bookmark Topic Watch Topic
  • New Topic