SystemEDGE on Linux Fails During Agent Registration/Discovery

Products

• CA Server Automation
• CA Virtual Assurance for IM

Issue/Introduction

After installing SystemEDGE and attempting to discover it within VAIM the agent may crash in some scenarios as part of the registration process. The $CASYSEDGE/config/port1691/.sysedge.id file will be incomplete and will be missing the UUID line. The modified time of the .sysedge.id file will roughly match the time of the first occurrence of the agent crashing.

 

Example of a "bad" .sysedge.id file:

[install]
sysNameCIM=agenthostname.ca.com

 

Example of a "good" .sysedge.id file:

[install]
sysNameCIM=agenthostname.ca.com
uuid=00000001-A954-F311-2319-00128F8CA777

 

Environment

SystemEDGE on supported Linux platforms. However, the problem is more likely to occur on newer versions of Linux such as Red Hat Enterprise Linux 7.

Cause

SystemEDGE uses data from the output of the /sbin/ifconfig command in order to facilitate the generation of the UUID contained within the .sysedge.id. On some modern and/or lean/lite versions of Linux /sbin/ifconfig is not installed by default. SysEDGE is then unable to generate a UUID successfully and may crash.

Resolution

Ensure that the /sbin/ifconfig command is available on the system in question. For Red Hat Enterprise Linux, this command is included with the "net-tools" package. This can generally be installed with the command:

yum install net-tools

Once the ifconfig binary is available, on the problem systems:

1. /opt/CA/SystemEDGE/bin/sysedgectl stop
2. rm /opt/CA/SystemEDGE/data/port1691/.sysedge.id
3. /opt/CA/SystemEDGE/bin/sysedgectl start
4. Rediscover in VAIM (Right click -> Policy -> SystemEDGE -> Discover agent)

 

If you encounter this problem on other non-Red Hat distributions of Linux, check with the OS vendor to ensure that you install the correct package.

Additional Information

If the above is addressed and the agent continues to crash ensure you are running SystemEDGE 5.9 B16326.