Re: Node Agent running as Windows Server, but shows as stopped in Admin Console

[jjpi...@efirstbank.com]

Are there any log entries/errors in the DMGR or nodeagent logs?

[jjpi...@efirstbank.com]

Well, in lieu of any log info, it sounds like the DMGR and nodeagent aren'te getting along properly.

Have you already attempted cycling both?

[bleo...@markelcorp.com]

Thanks for the quick reply. I don't see anything out of the ordinary in the log files. The application server and enterprise apps are showing an "unavailable" state. The node manager is showing as "stopped". Even still, all applications are accessible and seem to be functioning correctly.

[bleo...@markelcorp.com]

We recently installed an SSL cert on our WebSphere 6.1 application server. Now, the node agent is showing a stopped/inactive state in the admin console (even though it is running as a windows service) and we cannot synchronize the server.

Our apps are still running as expected, but we just cannot synchronize.

Any help/guidance will be greatly appreciated.

Thanks!

[bleo...@markelcorp.com]

I've stopped and restarted both many times to no avail. (just did it again for good measure). Not really sure what else to try at this point.

Thanks again for your quick response!

[jjpi...@efirstbank.com]

Are you able to attach your nodeagent's log?

[iliy...@gmail.com]

I think its due to the SSL configuration problem.
Have you able to do a manual sync between node and the deployment manager?

[bleo...@markelcorp.com]

I Agree - when I attempt to do a manual sync from within the Admin Console, I get the following error:

"The synchronize operation can not be performed on node stapp520Node01 because its node agent is not active"

As stated in my previous post, the node agent is running as a Windows service, but the admin console is seeing it as stopped.

The strange thing is that I applied SSL certs to two other WebSphere app servers following the same steps with no problems at all.

[iliy...@gmail.com]

What I was trying to say is to do a manual sync from the command prompt.

i.e you can run the manual sync command from the profiles root directory.

syncnode "soap-port" -username -password

If you get SSL related errors when you run the synccommand, then I think the node is not using the same trustore which Dmgr is using.

So you can take the trustore file i.e trust.p12 which Dmgr is using and copy it to the location where your node is using, you can find the path in security.xml

Moreover, it would be easier to find the solution to this issue if you could attach the nodeagent log file.

Thanks

[bleo...@markelcorp.com]

My apologies - I've attached the syncNode.log after attempting to sync the DMGR host at port 8879. It seems to be looking for a server.xml file in the Cell manager directory.

Thanks!

[Doug Breaux]

Agree that this sounds like a classic certificate mismatch problem, and you
should try manual syncing and looking at the node agent log.

The official manual sync sequence is;

1. stop node agents
2. stop dmgr
3. start dmgr
4. on node, run synchnode <dmgr hostname>

You may see an error there, or you may see a prompt about trusting a new
certificate. If the latter, answer affirmative to trust the certificate, and
your problem should be resolved.

If the former, I'd expect certificate-related errors in the log, and you'll
have to perform further activities. It may be that you're using different
trust stores, as suggested, but it may be that your key/trust stores have
multiple certificates in them and the different nodes are choosing different
defaults to use. If that's the case, you can explicitly choose defaults
through the console and/or delete old, unused certificates. Even so, I'd use
the command-line for syncing the first time afterwards.

--
Doug

[bk...@us.ibm.com]

It looks like you might have run the syncNode command from the dmgr profile. If so, you should run the command from the problem node profile instead.

[bleo...@markelcorp.com]

Thanks - I was able to successfully synchronize the node with the deployment manager via command-line.

I stopped the node, synchronized it with the dmgr, restarted the dmgr, started the node and all seems okay (except the Node Agent is still showing as "stopped" in the admin console).

[bleo...@markelcorp.com]

startManager -username wasadmin -
password wasadmin
ADMU0116I: Tool information is being logged in file
E:\IBM\WebSphere\AppServer\profiles\Dmgr01\logs\dmgr\startServer.log
ADMU7701I: Because dmgr is registered to run as a Windows Service, the request
to start this server will be completed by starting the associated
Windows Service.
ADMU0116I: Tool information is being logged in file
E:\IBM\WebSphere\AppServer\profiles\Dmgr01\logs\dmgr\startServer.log
ADMU0128I: Starting tool with the Dmgr01 profile
ADMU3100I: Reading configuration for server: dmgr
ADMU3200I: Server launched. Waiting for initialization status.
ADMU3000I: Server dmgr open for e-business; process id is 3556