Nodeagent running but not synchronizing

[esha...@homeq.com]

I have Deployment manager with 2 Nodes test and dev. Both Nodes were working initially, but now dev is showing the nodeagent running in the admin console but not synchronized and will not synchronize. The AppServer for dev is also showing stopped all the time but it is not. When I start the dev nodeagent here is what I am getting in the SystemOut.log. Could someone please help me resolve this problem keeping existing apps intact.

SystemOut.log for dev nodeagent:
===
[4/14/05 8:22:23:302 PDT] 706da8 SecurityCompo I SECJ0240I: Security service initialization completed successfully
[4/14/05 8:22:23:309 PDT] 706da8 JMSRegistrati A MSGS0601I: WebSphere Embedded Messaging has not been installed
[4/14/05 8:22:28:525 PDT] 706da8 JMXSoapAdapte A ADMC0013I: SOAP connector available at port 8878
[4/14/05 8:22:28:537 PDT] 706da8 SecurityCompo I SECJ0243I: Security service started successfully
[4/14/05 8:22:28:538 PDT] 706da8 SecurityCompo I SECJ0210I: Security enabled false
[4/14/05 8:22:29:131 PDT] 706da8 RMIConnectorC A ADMC0026I: RMI Connector available at port 2809
[4/14/05 8:22:29:686 PDT] 706da8 Endpoint W ADMD0012E: Unable to initialize the transport of type: UDP
[4/14/05 8:23:01:288 PDT] 706da8 WsServer A WSVR0001I: Server nodeagent open for e-business
[4/14/05 8:33:22:595 PDT] 797d27 NodeSync E ADMS0012E: Unable to create administrative client connection: com.ibm.websphere.management.exception.AdminException: Admin client connection to deployment manager is unavailable
..
[4/14/05 8:33:22:869 PDT] 797d27 NodeSync E ADMS0005E: Unable to generate synchronization request: com.ibm.websphere.management.exception.AdminException: Admin client connection to deployment manager is unavailable
at com.ibm.ws.management.sync.NodeSync.getAdminClient(NodeSync.java:484)
at com.ibm.ws.management.sync.NodeSync.getCellRepositoryEpoch(NodeSync.java:344)
at com.ibm.ws.management.sync.NodeSyncTask.doSync(NodeSyncTask.java:220)
at com.ibm.ws.management.sync.NodeSyncTask.run(NodeSyncTask.java:139)
at java.lang.Thread.run(Thread.java:479)
---- Begin backtrace for nested exception
java.lang.NullPointerException
at com.ibm.ws.management.sync.NodeSync.getAdminClient(NodeSync.java:480)
at com.ibm.ws.management.sync.NodeSync.getCellRepositoryEpoch(NodeSync.java:344)
at com.ibm.ws.management.sync.NodeSyncTask.doSync(NodeSyncTask.java:220)
at com.ibm.ws.management.sync.NodeSyncTask.run(NodeSyncTask.java:139)
at java.lang.Thread.run(Thread.java:479)

[Daniel Garcia]

Hi,

Just type in the base machine:

syncNode <DeploymentManagerServer> <deploymentManager port, by default
8879> -username yourSecurityUser -password yourSecurityPassword

More info in:
http://publib.boulder.ibm.com/infocenter/ws51help/index.jsp?topic=/com.ibm.websphere.base.doc/info/welcome_base.html

Regards,
Dani

esha...@homeq.com escribió:

[esha...@homeq.com]

Thanks for the post, but still not working. I run syncNode on the affected node and that was successful, but when I try and startNode it gives me
[4/20/05 11:18:17:030 PDT] 706da8 RMIConnectorC A ADMC0026I: RMI Connector available at port 2809
[4/20/05 11:18:17:593 PDT] 706da8 Endpoint W ADMD0012E: Unable to initialize the transport of type: UDP
[4/20/05 11:18:49:230 PDT] 706da8 WsServer A WSVR0001I: Server nodeagent open for e-business

[Ken Hygh]

esha...@homeq.com wrote:

A WAG from the second line there: your network or nic isn't set up to
support UDP.

Ken

[esha...@homeq.com]

This problem only started after about two months of running good. There are two nodes on the server dev and test. The test node is working well it is just this one know that refuses to comunicate with the dmgr.

[sto...@ldschurch.org]

Check the dates on the system and be sure they are all within two minutes of the deployment manager. We see this problem about every month or so as the servers drift out of sync. If the servers are our of sync you can manually adjust the date and try to sync the systems again. (I would bounce the nodeagent just to be on the safe side). If that fixes the problem you might look into using NTP or something similar to keep the clocks synced.