Could not Start server "WebServer2" via Node Manager

[anyeguevara]

I installed WebLogic Server 6.1, everything went well during the install. My Admin server name is beaserver which does start without any issues.

I then pointed my browser to

http://localhost:7001/console

which yielded the admin screen (I had to sign on using system and my password).

I configured a new machine with the following characteristics
Name-turpial
Node Manager tab
Listen address-turpial.caripito.com
listen port-7002
default certificate - default
certificate password-default
trusted Certs file-default

Next, I defined a new server by right mouse clicking on the Servers link on the left hand pane. I am planning to use it as my ManagedServer. The new server has the following characteristics:
Name-WebServer2
Machine-turpial.caripito.com (selected off the drop down).
Listen Port: 5555
Listen Address-Left Blank
External DNS Name-Left Blank

Finally, I tried to start the WebServer2 server and get an error;namely, "Could not start server "WebServer2" via Node Manager -reason: SecureCommandInvoker: Could not create a socket to the NodeManager running on host turpial.caripito.com is configured to listen on port '5555' and that is actively listening".

If anyone can share some information pertaining to the above, I would really appreciate it.
How can I test to make sure the new machine is set up correctly ?
How can I test to make sure the new server is set up correctly ?

If you can point me to a step-by-step document, it would be great. I have review BEA's installation notes, but it is not very clear in this particular case.

Thanks !
Angelo

 

[wushutwist]

Quick Question:
Do you have NodeManager up and running on WebServer2? This is required for remote starting and stopping of Managed Servers.

 

[anyeguevara]

How can I make sure the Node Manager is up and running on WebServer2 ?

The only thing I did was the steps I had shown before;namely, defined a new machine and a new Server which points to that new machine.

Question: While creating a new Server do I need to create a new machine ? I think it threw an error when I tried creating a new server without a machine. Is this correct ?

Again, if you can point me to a step-by-step document, it would be really helpful.

Please advise, thanks for the help !
Angelo

 

[anyeguevara]

I was able to start the NodeManager after all, I did start the WebServer2 server.

This server is listening on port 9999, its machine is localhost. I set up the localhost machine as follows,
Configuration tab.
Listen address - localhost
Listen Port - 5555
Server Tab
Selected the default server (beaserver in my case) and the WebServer2 server.

If I open a browser and point it to

http://localhost:9999,

I get "Error 404 - Not found".

Should I be able to see a default page ?

Please advise.
Angelo

 

[pryaranjan]

Hi Angelo:
I am having the same problme in starting my webserver named CMServer on weblogic. I followd the steps that you wrote to create the localhost machine and select both the servers. I am still getting the same error
"Could not start server "CMServer" via Node Manager -reason: SecureCommandInvoker: Could not create a socket to the NodeManager running on host turpial.caripito.com is configured to listen on port '5555' and that is actively listening".

Can you help in starting the node manager and the server.

Thanks,
Ranjan

 

[newfie2000]

I have had that problem before and the way I solved it was to ensure that the port number of the Machine under which the Managed Server was deployed (click Machine -> Configuration -> Node Manager and check the value of the Listen Port) is the same as the port number of the Node Manager (i.e. the same as the value of the -Dweblogic.nodemanager.listenAddress= parameter in the startNodeManager script) My ports were not matching and that is why I was getting the error. Remember, the port number in the startNodeManager script has to match the port number of the Managed Server's Machine, not the Admin Server's Machine....that was where I went wrong.

Hope this helps!

 

[Guest_imported]

Can anyone please help?

I am trying wl6.1's nodemanager functionalities. Things all look fine. I could start the admin server and nodemanager (I am using a single machine doing multihoming). When I tried to start a managed server from the admin console, I got something like following:

Starting WebLogic Server ....
Connecting to

http://192.168.1.202:7001...

<Jul 5, 2002 1:20:35 PM EDT> <Notice> <WebLogicServer> <Starting WebLogic Managed Server &quot;nodeb&quot; for domain &quot;onlinestore&quot;>
<Jul 5, 2002 1:20:38 PM EDT> <Notice> <WebLogicServer> <ListenThread listening on port 7001, ip address 192.168.1.205>

and dos console said

<Jul 5, 2002 4:36:48 PM EDT> <Info> <NodeManager@192.168.1.205:5002> <WindowsPro
cessControl: online successfully invoked on server 'nodeb', pid: 0>

As you know the pid is not OK. I checked state of nodeb and it wasn't running.

Any idea why? Thanks a lot.

 

[Guest_imported]

Can anyone please help?

I am trying wl6.1's nodemanager functionalities. Things all look fine. I could start the admin server and nodemanager (I am using a single machine doing multihoming). When I tried to start a managed server from the admin console, I got something like following:

Starting WebLogic Server ....
Connecting to

http://192.168.1.202:7001...

<Jul 5, 2002 1:20:35 PM EDT> <Notice> <WebLogicServer> <Starting WebLogic Managed Server &quot;nodeb&quot; for domain &quot;onlinestore&quot;>
<Jul 5, 2002 1:20:38 PM EDT> <Notice> <WebLogicServer> <ListenThread listening on port 7001, ip address 192.168.1.205>

and dos console said

<Jul 5, 2002 4:36:48 PM EDT> <Info> <NodeManager@192.168.1.205:5002> <WindowsPro
cessControl: online successfully invoked on server 'nodeb', pid: 0>

As you know the pid is not OK. I checked state of nodeb and it wasn't running.

Any idea why? Thanks a lot.

 

[Guest_imported]

Hi I got NodeManager started, but once connect to it I got the follow error of handshake error, any idea?

I am using the demo crt. using my own cert get the same error too.



<Sep 23, 2002 2:12:23 PM MST> <Error> <NodeManager@XXX.XXX.XXX:5555> <Certificate chain untrusted>
<Sep 23, 2002 2:12:23 PM MST> <Error> <NodeManager@XXX.XXX.XXX:5555> <SocketInputHandler: Command read failed 'FATAL Alert:HANDSHAKE_FAILURE - The handshake handler was unable to negotiate an acceptable set of security parameters.' on socket XXX.XXX.XXX>
<Sep 23, 2002 2:12:23 PM MST> <Error> <NodeManager@XXX.XXX.XXX:5555> <Failed to write to socket Write Channel Closed, to XXX.XXX.XXX>
java.lang.NumberFormatException: null
at java.lang.Integer.parseInt(Integer.java:382)
at java.lang.Integer.parseInt(Integer.java:463)
at weblogic.nodemanager.SocketInputHandler.run(SocketInputHandler.java:109)