Centralized Agent Upgrade (CAU) for Unix AIX Agents fails during the deployment phase. The Service Manager remains on the old version while the Agent may appear upgraded. This occurs when moving from versions using legacy library formats to newer shared object formats.
mv -f ${AgentBinPath}/libsysapi.a ${SMgrBinPath}/libsysapi.a
mv -f ${AgentBinPath}/libzu00132.a ${SMgrBinPath}/libzu00132.aThe Service Manager (smgr) log contains the following errors:
ERROR 256: mv -f /path/to/bin/libsysapi.a /path/to/smgr/bin/libsysapi.a
mv: 0653-401 Cannot rename /path/to/bin/libsysapi.a to /path/to/smgr/bin/libsysapi.a: A file or directory in the path name does not exist.
U00022052 Error in file processing, the previous processing will be rolled back.Additionally, after an attempted upgrade, the Service Manager may fail to start with:
exec(): 0509-036 Cannot load program ucybsmgr because of the following errors:
0509-150 Dependent module libsysapi.so could not be loaded.
0509-022 Cannot load module libsysapi.so.
0509-026 System error: A file or directory in the path name does not exist.
deployment.txt script incorrectly references deprecated *.a library files instead of current *.so files.libsysapi.so and libzu00132.so upon restart.Update to a fix version listed below or a newer version if available.
Fix version:
Component(s): CAU Agent Unix
Automic Automation.Engine 24.4.5 - TBA
Automic AUtomation Engine 26.1.0 - TBA
Workaround If an immediate upgrade is required before applying the fix:
LIBPATH environment variable to explicitly include the Service Manager's bin directory before starting the agent:export LIBPATH=/path/to/servicemanager/bin:$LIBPATH
Article title: How to register to Broadcom Software Product updates and Critical Alerts
https://knowledge.broadcom.com/external/article?articleId=133819