IBM Support

AdminConsole of WAS AdminAgent might not recognize the registered node.

Troubleshooting


Problem

When trying to login at the administrative console (ISC) of the AdminAgent, it usually gives the option to login either at the AdminAgent itself, or at any of the registered nodes. However, in some cases, the registered nodes might be unavailable / greyed out, although the servers are started.

Symptom

Cause

After a fixpack installation, the file node-metadata.properties in ...profiles\AppSrv01\config\cells\<cellname>\nodes\<nodename>
of the registered node still has the old fixlevel information.
This file is not updated before the first start of the application server in the registered node.

Diagnosing The Problem

There is an ffdc log in the AdminAgent logs directory, which shows that the current version of the registered node does not match to the AdminAgent version.

    [2/18/14 11:12:34:812 CET] FFDC Exception:java.security.PrivilegedActionException SourceId:com.ibm.ws.management.component.AdminSubSystemImpl.initialize ProbeId:161 Reporter:com.ibm.ws.management.component.AdminSubSystemImpl@55a455a4
    java.security.PrivilegedActionException: com.ibm.ws.exception.ConfigurationError:

    ADMAA0007E: The administrative agent did not start the subsystem for the winwas70bNode03 node because the set of products and versions on the node {base=7.0.0.25} is not the same as the following set of administrative agent products and versions: {base=7.0.0.29}
    at com.ibm.ws.security.auth.ContextManagerImpl.runAs(ContextManagerImpl.java:5308)

This is basically irrelevant, as AdminAgent and registered nodes are usually installed in the same \WebSphere\AppServer, but nevertheless the AdminAgent will only discover Nodes which have the same fix level.

Resolving The Problem

After fixpack installation, ensure that the servers of the registered nodes have been started before the AdminAgent is started.

This ensures that the node-metadata.properties file of each registered node is updated with the correct fixlevel before the AdminAgent discovers the node.

Then the AdminAgent ISC shows the Node as available again, in this example AppSrv01:


[{"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Administrative Console (all non-scripting)","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"8.5;8.0;7.0","Edition":"Base;Network Deployment","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
15 June 2018

UID

swg21665049

Page Feedback