IBM Support

Universal Agent shows no application subnodes

Technical Blog Post


Abstract

Universal Agent shows no application subnodes

Body

Despite Universal Agent has been deprecated since long time and most of the workload is now replaced by custom
agents built with Agent Builder, there are still lot of UA-based applications running around the World.

It is becoming rare to face issues with this agent, but in case it happens, it is good to know what to do.
In this article we will talk about an error scenario where an UA application that is known to run fine on many other
nodes, is producing no sub-nodes on TEP for a specific node.
The same metafile was working fine previously on the same node, customer did a "Clear Offline Entries" to remove some
older application sub-nodes and then restarted Universal Agent.
Since then, the expected sub-nodes no longer appeared again.

The metafile cannot be wrong because it is exactly the same used on the other UA machines.
The UA subnodes (application nodes) are created when the metafile is correctly loaded and processed and the
data collection for its attributes is attempted.
Even if data collection fails, the sub-nodes should have been anyway created on TEP navigator tree.

I tested the same metafile on my environment and I got the sub-nodes correctly created, even if of course the
data collection failed because the invoked scripts was not generating the expected results.

This means that something went wrong during metafile processing.
Looking at the Universal Agent RAS1 log I found error messages like these:


(Tue Feb 27 16:19:03 2018.0027-A:kumddata.cpp,182,"applSpaceList::allocApplicationSpace") Error: allocateAttrInfoList failed
(Tue Feb 27 16:19:03 2018.0028-A:kumdchsv.cpp,1430,"DCHserver::dp_register") Error: allocating application space. applName: <APP1AL> attrGroup: <CHK>

..

..

(Tue Feb 27 16:19:03 2018.002A-3:kumpcadm.c,8357,"KUMP_ConstructApplDataModel") *** dp_register failed for application <app1al> SourceState 1 SEptr @7F466C035050

(Tue Feb 27 16:19:03 2018.002B-3:kumprapr.c,1015,"KUMP_ReleaseApplResources") Freeing application entry @7F466C034A90 <app1al>

..

..

(Tue Feb 27 16:19:03 2018.003B-A:kumdchsv.cpp,1430,"DCHserver::dp_register") Error: allocating application space. applName: <APP1AL> attrGroup: <CHK>


 

And into the activity log instead:

 


KUMPV008E Processing Error: Application registration with agent failed for app1al

Tue Feb 27 16:19:03 2018 KUM0005E   Metafile APP1AL.mdl validation failed.

ERROR Metafile APP1AL.mdl validation failed.


 

This confirmed that Universal Agent was not able to complete metafile processing to create attribute groups and attributes.
But the same metafile used on my environment completed fine, so the problem is not with the metafile itself.
The same application was already present on the UA configuration files, so I suspected a possible problem or corruption with it.

For example, KUMATBLS was already including the following entries:


APP1AL00 APP1844600 0
APP1AL00 APP208200 0
APP1AL00 APP6353600 0
APP1AL00 APP5810100 0
APP1AL00 APP6314800 0

That are the tables produced for the attribute groups belonging to the application APP1AL (metafile app1al.mdl)

There was also a duplication for metafile APP1AL.mdl into KUMPCNFG.

So I tried the following actions:

 

1) Make a backup of KUMPCNFG and KUMATBLS
2) Stop the Universal Agent
3) Edit the KUMATBLS and remove the following lines:

APP1AL00 APP1844600 0
APP1AL00 APP208200 0
APP1AL00 APP6353600 0
APP1AL00 APP5810100 0
APP1AL00 APP6314800 0

Save and exit

4) Edi the KUMPCNFG file and remove both the lines for APP1AL.mdl

 Save and exit

 
5) Start the Univeral agent

6) perform a new import for the APP1AL.mdl metafile using um_console

 

Above actions are performed to have a clean situation before re-importing the application metafile from scratch and actually
helped to have the application sub-nodes correctly created.

So in case you face something similar with your UA, before starting any troubleshooting try cleaning up files KUMPCNFG and KUMATBLS
and re-import the metafile from scratch, it will get rid of possible incongruence or corruption of the UA working files.

Hope it helps.

Best Regards

 

Tutorials Point

 

Subscribe and follow us for all the latest information directly on your social feeds:

 

 

image

 

image

 

image

 

 

  

Check out all our other posts and updates:

Academy Blogs:https://goo.gl/U7cYYY
Academy Videos:https://goo.gl/TLfMoF
Academy Google+:https://goo.gl/HnTs0w
Academy Twitter :https://goo.gl/AhR8CL


image

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"","label":""},"Component":"","Platform":[{"code":"","label":""}],"Version":"","Edition":"","Line of Business":{"code":"","label":""}}]

UID

ibm11085121