Cloud APM server prerequisites

Edit online
The Cloud APM server and supporting components are installed by a root user on a Red Hat® Enterprise Linux® system. Review the Cloud APM server prerequisites to ensure a successful installation.

After you start the installation of the Cloud APM server, a prerequisite scanner runs automatically and checks that all of the Cloud APM server prerequisites are met. A warning or failure message is displayed in the prerequisite scanner results if any of the prerequisites are not met. For more information about running the prerequisite scanner, see Prerequisite scanner.

Table 1 displays the Cloud APM server prerequisites, describes failure and warning conditions for each prerequisite, and suggests some corrective action to take.
Table 1. Cloud APM server prerequisites
Prerequisite Description Failure description in scan report Correction action
OS version The OS version must be either Red Hat Enterprise Linux V6.* or Red Hat Enterprise Linux V7.*. The OS is not a supported version. Install the Cloud APM server on a supported operating system.
os.RAMSize The amount of available memory that is required depends on whether you are installing the base or advanced offering and whether the Db2® database is local or remote. The available memory requirements are:
  • For the advanced offering and a local Db2, 24 GB
  • For the advanced offering and a remote Db2, 20 GB
  • For the base offering and a local Db2, 16 GB
  • For the base offering and a remote Db2, 12 GB
Not enough memory. Extend the memory size on the system to the required level.
Disk The amount of free disk space that is required depends on whether you are installing the base or advanced offering and whether the Db2 database is local or remote. The free disk space requirements are in Cloud APM server hardware requirements. Not enough disk space for the installation. Delete any unused files or enlarge the disk partition.
os.swapSize 4 GB or more of free swap space is recommended for the installation.

A warning is displayed if the swap size is 2 - 4 GB. The installation can continue but the server might experience poorer performance.

A FAIL condition is displayed if the swap size is less than 2 GB.

Not enough swap space available. Create or increase the available swap space.
numLogicalCPU The system must have at least 4 logical CPUs.

A warning is displayed if the number of CPUs is 2 - 4.

The system must have at least 4 logical CPUs. Increase the number of logical CPUs.
os.space.homedir At least 1 GB of space is required in the /home directory. Not enough disk space in the /home directory. Delete any unused files or enlarge the disk partition.
os.space.installdir The amount of free space that is required in the /install_dir directory depends on whether you are installing the base or advanced offering and whether the Db2 database is local or remote. The free space requirements are:
  • For the advanced offering and a local Db2, 80 GB
  • For the advanced offering and a remote Db2, 30 GB
  • For the base offering and a local Db2, 60 GB
  • For the base offering and a remote Db2, 20 GB
Not enough disk space in the /install_dir directory. Delete any unused files or enlarge the disk partition.
os.space.tmpdir 2 to 3 GB of free space is required in the system’s temp directory for the installation. Not enough disk space in the system's temporary directory (for example, /tmp/ on Linux/AIX®). Delete any unused files or enlarge the disk partition.
os.dir.opt=dir:/opt/ibm,
type:permission755+		 The /install_dir directory must have at least read/write/execute permissions for the owner and at least read/execute permissions for the group and others. A permissions issue was found with install_dir. Check whether the install_dir partition directory has at least read/write/execute permissions for the owner and read/execute permissions for group and other. Modify install_dir permissions. For example: chmod u+rwx,go+rx /install_dir.
os.umask The shell umask must be set to 0022. The shell umask is set to a different value than 0022. Some components, for example, the Db2 server, do not install properly if there are insufficient permissions on certain files. Set umask to 0022 before you run the installer: umask 0022; ./install.sh
os.dir.tmp=dir:/tmp,
type:permission777+		 The /tmp directory must have at least read/write/execute permissions for the owner and at least read/execute permissions for the group and others. A permissions issue was found with the /tmp directory. Check whether the /tmp partition directory has at least read/write/execute permissions for the owner and read/execute permissions for group and other. Modify permissions for /tmp. For example: chmod u+rwx,go+rx /tmp
CpuArchitecture The CPU processor architecture must be an Intel or AMD 64-bit CPU. Processor architecture is not either an Intel or AMD 64-bit CPU. Run the server installation on an Intel or AMD 64-bit compatible system.
rpmdbStatusCorrect The RPM package database must be intact. The RPM package database is not intact. To solve this problem, complete the following steps:
  1. Remove the rm-rf /var/lib/rpm/__db.00* rpm lock files.
  2. To rebuild the RPM database, enter the rpm --rebuilddb command.
  3. To uninstall all the components that you installed to the /opt/ibm/ directory, enter the/opt/ibm/ccm/uninstall.sh command.
  4. To restart the installation, run ./install.sh.
os.locahostInHostFile The localhost host name must be specified in the /etc/hosts file. The localhost host name is not available in the /etc/hosts file. Add an entry to the /etc/hosts file to define the localhost host name.
os.ulimit=
[type:maxprocesseslimit]
4096+		 The operating system must allow a user to have at least 4096 processes running. If less than that value, a FAIL condition is returned and the Cloud APM server installation fails. The maximum number of user processes is set too low on this operating system.

For more information about checking the limits and changing them, see Resolving maximum number of user processes, open files, and core file dependency failures.
os.ulimit=
[type:filedescriptorlimit]
32768+		 The operating system must allow a user to have at least 32,768 open files. If less than that value, a FAIL condition is returned and the Cloud APM server installation fails. The maximum number of open files is set too low on this operating system.

For more information about checking the limits and changing them, see Resolving maximum number of user processes, open files, and core file dependency failures.
os.ulimit=
[type:corefilesizelimit]
390000+		 The operating system must allow a user to create a core dump of at least 390000 KB. If less than that value, a FAIL condition is returned and the Cloud APM server installation fails. The maximum size of the core file is set too low on this operating system.

For more information about checking the limits and changing them, see Resolving maximum number of user processes, open files, and core file dependency failures.
os.mountcheck.tmp_nosuid,
s.mountcheck.home_noexec,
os.mountcheck.tmp_nosuid,
and os.mountcheck.tmp_noexec		 The /tmp or /home partitions must not be mounted with nosuid or nonexec flags or both. The /tmp or /home partitions are mounted with nosuid or noexec options. The installation will fail. Remount /tmp or /home and remove nosuid or noexec flags.
network.availablePorts.* The ports in Table 1 and Table 2 in Cloud APM server ports must be available. The specified port is not available. If a firewall is blocking the ports, you can either configure the firewall to allow traffic on certain ports or disable the firewall. For more information, see Configuring the firewall for incoming requests to the server.
network.ping.Self It must be possible to resolve the host name of the local computer system. The host name of the local computer system cannot be resolved. If the self-ping test fails, complete one of these steps:
  1. If you use a DNS server for host name resolution, complete these steps:
    • Check that the /etc/resolv.conf file exists and that it has entries for your DNS servers.
    • Verify that your DNS servers are reachable. Open a command prompt and enter:
      ping DNS_server_IP_address
  2. If you use the /etc/hosts file for host name resolution, check that the /etc/hosts file has an entry for your local computer system.
  3. If the IP address of your local computer system is assigned by a DHCP server, check that network interfaces are configured and that an IP address and a netmask are assigned to each interface in the DHCP configuration.
os.package.ksh The KornShell (ksh) package that is required for the Summarization and Pruning agent is missing. The ksh package that is required for the Summarization and Pruning agent is missing. You must first install the missing package, and start the installation again. (See Tips for resolving unmet dependencies in Cloud APM server prerequisites.)
os.package.bash A bash package that is required for the Cloud APM server is missing. The bash package that is required for the Cloud APM server is missing. You must first install the missing package, and start the installation again. (See Tips for resolving unmet dependencies in Cloud APM server prerequisites.)
os.package.lsof The List Open Files (lsof) package that is required for the Cloud APM server is missing. The lsof package that is required for the Cloud APM server is missing. You must first install the missing package, and start the installation again. (See Tips for resolving unmet dependencies in Cloud APM server prerequisites.)
os.package.rsync The rsync package that is required for the Cloud APM server is missing. The rsync package that is required for the Cloud APM server is missing. You must first install the missing package, and start the installation again. (See Tips for resolving unmet dependencies in Cloud APM server prerequisites.)
os.package.unzip The unzip package that is required for the Cloud APM server is missing. The unzip package that is required for the Cloud APM server is missing. You must first install the missing package, and start the installation again. (See Tips for resolving unmet dependencies in Cloud APM server prerequisites.)
os.package.nmap-ncat The nmap-ncat package that is required for the Cloud APM server is missing. The nmap-ncat package that is required for the Cloud APM server is missing. You must first install the missing package, and start the installation again. (See Tips for resolving unmet dependencies in Cloud APM server prerequisites.)
os.package.zip The zip package that is required for the Cloud APM server is missing. The zip package that is required for the Cloud APM server is missing. You must first install the missing package, and start the installation again. (See Tips for resolving unmet dependencies in Cloud APM server prerequisites.)
os.lib.libc_64=regex
{libc\.so.*}		 A library that is required for the Cloud APM server is missing. A library that is required for the Cloud APM server is missing. You must first install the missing libraries, and start the installation again. (See Tips for resolving unmet dependencies in Cloud APM server prerequisites.)
os.lib.libgcc_64=regex
{libgcc.*\.so.*}		 A library that is required for the Cloud APM server is missing. A library that is required for the Cloud APM server is missing. You must first install the missing libraries, and start the installation again. (See Tips for resolving unmet dependencies in Cloud APM server prerequisites.)
os.lib.libstdc_64=regex
{libstdc++\.so\.5}		 A library that is required for the Cloud APM server is missing. A library that is required for the Cloud APM server is missing. You must first install the missing libraries, and start the installation again. (See Tips for resolving unmet dependencies in Cloud APM server prerequisites.)
os.lib.libstdc_64=regex
{libstdc++\.so\.6}		 A library that is required for the Cloud APM server is missing. A library that is required for the Cloud APM server is missing. You must first install the missing libraries, and start the installation again. (See Tips for resolving unmet dependencies in Cloud APM server prerequisites.)
Table 2 displays the Db2-related Cloud APM server prerequisites, describes failure and warning conditions for each prerequisite, and suggests some corrective action to take.
Table 2. Db2-related prerequisites
Prerequisite Description Failure description
in scan report		 Corrective
action
db2.isInstalled A Db2 server must not exist on the local system. An existing Db2 server installation was discovered on system. Uninstall the existing Db2 server or choose a different system.
db2.usersNotPresent

A warning is displayed if users that are required by the Db2 server are detected on the system. The users are as follows:

  • itmuser
  • dasusr1
  • db2apm
  • db2fenc1
 Users that are required by Db2 server were detected on the system. Remove users or provide valid passwords for the users in the install_dir/install.properties file, which is available in the root directory of the installation media. If you do not remove the users then ensure the db2apm user is not a member of the root group.
db2.groupsNotPresent A warning is displayed if groups that are required by the Db2 server are detected on the system. Groups that are required by Db2 server are detected on the system. Remove existing groups or allow the installer use the groups for Db2 installation.
db2.servicesNotPresent Db2 services must not be running on the system. Running Db2 services were discovered on the system. Uninstall the existing Db2 server, clean up all remaining services, or choose a different system.
os.isUnixServiceRunning
.crond		 The Db2 server requires that the crond service is running. The crond service is not running. Start crond service.

If you create a Db2 database on an external system or if you connect to a MongoDB database on an external system, you must verify that the cron service is running on these systems.

os.kernelversion The Db2 installation requires Linux kernel version 2.6.16 or higher. The kernel version is not supported. Use a supported kernel version.
os.kernelsNotSupported When you install the Db2 agent on the Db2 server and on some VMs, the installation requires that the Linux Kernel versions not be in the range from 2.6.32-434 to 2.6.32-504.7.1 The kernel version is not supported. You must upgrade to one of the supported versions. Any other kernel starting from 2.6.16 or higher is valid.
os.isLDAPConfigured A warning is displayed if LDAP is configured on the system. System is configured to work with LDAP. The /etc/nsswitch.conf file contains sss (System Security Services ) or ldap, or winbind (Windows Active Directory) entries for password. It may cause problems when existing Db2-related users are present in LDAP and have different password than the one defined in the install_dir/install.properties file. If an itmuser and Db2 instance users are configured in your LDAP directory and you plan to install the Cloud APM server with a local Db2 server, follow the instructions in Installing on a system using an external directory service.
os.lib.libstdc++_32=regex
{libstdc++\.so\.6}		 A library that is required for Db2 is missing. A library that is required for Db2 is missing. You must first install the missing libraries, and start the installation again. (See Tips for resolving unmet dependencies in Cloud APM server prerequisites.)
os.lib.pam_64=regex
{libpam\.so.*}		 A library that is required for Db2 is missing. A library that is required for Db2 is missing. You must first install the missing libraries, and start the installation again. (See Tips for resolving unmet dependencies in Cloud APM server prerequisites.)
os.lib.pam_32=regex
{libpam\.so.*}		 A library that is required for Db2 is missing. A library that is required for Db2 is missing. You must first install the missing libraries, and start the installation again. (See Tips for resolving unmet dependencies in Cloud APM server prerequisites.)
os.package.sg3_utils
=sg3_utils		 A library that is required for Db2 is missing. A library that is required for Db2 is missing. You must first install the missing libraries, and start the installation again. (See Tips for resolving unmet dependencies in Cloud APM server prerequisites.)
os.dir.home
=[dir:/home,type:permission]
755+		 The /home directory of the Db2 users itmuser, dasusr1, db2apm, and db2fenc1 must have at least read/write/execute permissions for the owner and at least read/execute permissions for the group and others. A permissions issue was found with the /home directory. Check whether the /home directory has at least read/write/execute permissions for the owner and read/execute permissions for group and other. Modify /home permissions. For example: chmod u+rwx,go+rx /home.