Fail to start the primary node agent at Portal Cluster V6 - Urgent
praka...@rigelsoft.com
Under dynamic cluster environemnt(with 2 nodes with DMGR + XD) everything was smooth until Database server abnormal down due storage issue, after DB back to operation, restarted all the servers, DMGR, node agents and node servers(server1, portal server).
DMGR, APP2 node agent and servers started without any issue but App1 node agent unable to start due following error.
Found that there was fix pack PK54912(http://www-01.ibm.com/support/docview.wss?uid=swg1PK54912), after applying this fix pack all nodes and DMGR, same issue unable to start node agent at APP1.
Also tried ./syncNode.sh 8879 but still failed.
******************* from nodeagent.log *******************
[5/13/09 12:32:32:072 SGT] 0000000a XDAComponentI I CWXDA0002I: XDA service XDAComponentImpl started successfully.
[5/13/09 12:32:32:120 SGT] 00000016 Peer I ODCF8520I: Peer infrastructure is operational: 10.12.2.51 udp_port=11009 tcp_port=11012.
[5/13/09 12:32:32:229 SGT] 0000000a AsyncPmiBridg I ASPS0010I: In management overlay network, with name=RGSPRODMGMTCell01\RGSPR1\nodeagent
[5/13/09 12:32:32:492 SGT] 0000000a TreeBuilder I INIT 210 ms. nodes:47
[5/13/09 12:32:36:351 SGT] 0000000a ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl initialize FFDC0009I: FFDC opened incident stream file /opt/IBM/WebSphere/wp_profile/logs/ffdc/nodeagent_0000000a_09.05.13_12.32.36_0.txt
[5/13/09 12:32:36:354 SGT] 0000000a ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl resetIncidentStream FFDC0010I: FFDC closed incident stream file /opt/IBM/WebSphere/wp_profile/logs/ffdc/nodeagent_0000000a_09.05.13_12.32.36_0.txt
[5/13/09 12:32:36:311 SGT] 0000000a UserRegistryI E SECJ0331E: The registry implementation file com.ibm.ws.wim.registry.WIMUserRegistry cannot be initialized because of the following exception com.ibm.websphere.wim.exception.WIMConfigurationException: CWWIM5034E The parameter value 'uid' is not correct for the parameter 'loginProperties'. The parameter must have one of the following values: 'null'.
at com.ibm.ws.wim.adapter.db.DBAdapter.initialize(DBAdapter.java:277)
at com.ibm.ws.wim.RepositoryManager.initialize(RepositoryManager.java:518)
Any of you come across same issue, please update me your suggestion.
Thanks & Regards
Prakasam
dec...@us.ibm.com
1. compare the security.xml from the dmgr to the one in the node that's failing. You may have a mismatch there.
2. Compare the wim/wimconfig.xml from the dmgr as well.
If mismatch, copy dmgr one over to node.
Hope that helps.
Tim