The Agent Technology aws_agtgate service appears to hang whenever Atech is owned by a non-root user and all of NSM is started from the root user account using "unistart all" or "unistart atech".
Article ID: 22093
Updated On:
Products
Issue/Introduction
Description:
A non-root user is designated as the owner of NSM 11.0 Agent Technology during the install. If this user attempts to start the Atech agents using the "awservices start" command, all Atech common services and agents start with no problem. But, if any authorized user attempts to start the Atech agents using either "unistart all" or "unistart atech", the aws_agtgate service fails Cgene initialization and DIA communications fail. The pingagt utility will timeout and errors similar to the following are seen in the aws_agtgate.log file:
Error initializing Cgene -1 ( DNA Down )
Solution:
The "su" command used in the CA-atech init bootstrap script, which is executed whenever NSM components are started using the "unistart" utility, does not pass the setting of the SHLIB_PATH environment variable to the non-root user who owns Agent Technology. This in turn causes the JVM to fail to initialize when the aws_agtgate executes the DIA initialization to establish DIA communications.
To correct this, you must edit the /sbin/init.d/CA-atech init bootstrap script and change the following line:
output="`su $PRODUCT_OWN -c \"$AWSERVICES start\"`"
to
output="`su $PRODUCT_OWN -c \"CA_SECTION=ccs; export CA_SECTION; . /etc/profile.CA; $AWSERVICES start; unset CA_SECTION\"`"
This will assure that the non-root user that owns Atech will get SHLIB_PATH set properly in the environment before executing the "awservices start" command.
Please note that this problem is resolved in the NSM 11.2 release.
Environment
Component:
Feedback
