ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

EEM 12.6 install Fails but left partially installed


Article ID: 208415


Updated On:


CA Workload Automation AE


Installing EEM 12.6 from the AutoSys R12 installation image. The installation of EEM fails. However, it appears that it was able to partially install EEM components. CA Directory exists but the iTechnology folder is empty.

When looking at the $CASHCOMP/CADirectory/dxserver/logs/itechpoz_alarm.log, the following error is posted...

[64] 20210114.123615.626 DSA_E1990 Cannot register SNMP address

[64] 20210114.123615.626 DSA_E1280 Error in initialization files

[64] 20210114.123615.626 DSA_I1240 DSA shutting down


The error in the itechpoz_alarm.log is the key to understanding the root cause of this particular type of EEM install failure. When installing EEM, CA Directory is installed first. It then must be started for the rest of the EEM install to complete successfully. To do this, the installer su's to the dsa user and starts the dxserver process. The file owner of the dxserver binary is set to root and the sticky bit is set in the file permissions. This will allow the dxserver to be started by the dsa user, but run as root. If for any reason the dxserver process is not running as root, it is unable to register the necessary ports that it needs, resulting in a failure to start. Since it is not able to start, the remainder of the EEM install is unable to start successfully.

If the file system where EEM is installing contains a nosetuid restriction, the dxserver process gets started as the dsa user rather than root. It is then unable to register the required ports and shuts down.


Release : 12

Component : CA Workload Automation AE (AutoSys)


Ensure the filesystem where EEM is being installed does not have a nosetuid restriction.