1. When the node agent fails to trust the DM.
Logs indicated:
.
[3/10/12 17:50:21:780 CDT] 00000027 RoleBasedAuth A SECJ0305I: The role-based authorization check failed for admin-authz operation StatusCache:placeReport:com.ibm.ws.management.status.StatusReport. The user UNAUTHENTICATED (unique ID: unauthenticated) was not granted any of the following required roles: operator, administrator. ( All of IBM infocenter instructions just confused me more, google was not helpful either)
.
[3/10/12 17:50:21:780 CDT] 00000027 RoleBasedAuth A SECJ0305I: The role-based authorization check failed for admin-authz operation StatusCache:placeReport:com.ibm.ws.management.status.StatusReport. The user UNAUTHENTICATED (unique ID: unauthenticated) was not granted any of the following required roles: operator, administrator. ( All of IBM infocenter instructions just confused me more, google was not helpful either)
Tried a simple
approach:
1.stop
all of the nodeagents since all of them where out of synch.
2.Manually sync
the node with syncNode.sh "./syncNode.sh pwas6cons 10045" pointing to
the DMs SOAP port
3. Start the node
agent
Logs look much
clean and beautiful now.
Nodeagent Logs:
[3/10/12 18:19:35:690 CDT] 00000028 NodeSyncTask A ADMS0003I: The configuration synchronization completed successfully.
[3/10/1218:20:35:694 CDT] 00000029 NodeSyncTask A ADMS0003I: The configuration synchronization completed successfully.
2.You have included this fix in this email, but
the symptoms of this issue is when you see cluster application updates
reflecting different timestamps for each instance and when you log into the
deployment manager and synchronize 2 -3 minutes later when you refresh the
status it shows as not being synchronized.[3/10/12 18:19:35:690 CDT] 00000028 NodeSyncTask A ADMS0003I: The configuration synchronization completed successfully.
[3/10/1218:20:35:694 CDT] 00000029 NodeSyncTask A ADMS0003I: The configuration synchronization completed successfully.
you would clearn up : */tmp, */config/temp and */wstemp areas
Incase cluster
application updates not working as intended then please follow the steps to
prevent the issue from happening again, if this works we then will come up with
a script to clean up */tmp, */config/temp and */wstemp areas.
1) Stop the dmgr
2) on dmgr side delete the contents under wstemp, temp and config/temp
folder from <profile_root>
3) start the dmgr.
4) Stop the Node using stopNode command from the <profile_root>/bin of
AppServer
5)synchronizing the node by running syncNode.sh from <profile_root>/bin
if security is able then please run following command
syncNode.sh <DMgr_hostName><SOAP_PORT_of_DMGR> -username <username> -password <password>
6)Start the node and server.
1) Stop the dmgr
2) on dmgr side delete the contents under wstemp, temp and config/temp
folder from <profile_root>
3) start the dmgr.
4) Stop the Node using stopNode command from the <profile_root>/bin of
AppServer
5)synchronizing the node by running syncNode.sh from <profile_root>/bin
if security is able then please run following command
syncNode.sh <DMgr_hostName><SOAP_PORT_of_DMGR> -username <username> -password <password>
6)Start the node and server.
No comments:
Post a Comment