APM Agent install prerequisite checker and installation failures
harrietj 100000VRFW Comment (1) Visits (5683)
There are some unexpected agent prerequisites you may not be aware of. Here are some failures you might see and how to correct them.
In the case of CpuArchitecture FAIL ppc64 ppc64le
Problem: When trying to install the APM agent 8.1.4 on RHEL PowerPC, we encounter this error in the logs. KAX - IBM Tivoli Monitoring Shared Libraries [version 06351400]: Property Result Found Expected ======== ====== ===== ======== CpuArchitecture FAIL ppc64 ppc64le
Solution: Install on PowerPC Little Endian (ppc64le)
The agent installer determined that the system is PowerPC Big Endian (ppc64). However, the APMv8 agents are only supported on PowerPC Little Endian (ppc64le). By the way, there is an RFE requesting PowerPC Big Endian support: http
In the case of os.SELinux set to Enforcing
Problem: When trying to install the APM HTTP agent 8.1.4 with SELinux set to 'ENFORCING' this error is encountered.
KHU - Monitoring Agent for HTTP Server Prerequisite Checker [version 01000600]:
Even though the documentation says that the installation will work when SELinux is set to 'ENFORCING', the pre-req checker will fail when set to that level.
Solution: skip the pre-req check AND set SELinux to 'ENFORCING' then the installation proceeds.
In the case of user.isAdmin and the ms sql agent
Problem: installing the 8.1.3 MS SQL agent fails even though the Administrator id has the correct permissions.
The following agents FAILED to install: Monitoring Agent for Microsoft SQL Server user.isAdmin FAIL False
Solution: skip the pre-req check. This is resolved in 8.1.4
In the case of no synthetic agent data in APM GUI
In the case of agent installation failure
ERROR: Cannot create wrapper script: "D:\
The root cause may be that the agent installation image was extracted to a directory with space in its name (like c:\IBM APM install\) and the 8dot3name was not enabled in the windows server.
Subscribe and follow us for all the latest information directly on your social feeds: