Skip to Content
Information
Unsupported content Version 2.7.41 of the product is in limited support, while versions 2.7.43 and 2.7.44 are fully supported. This documentation includes content for all versions. You will not be able to leave comments for version 2.7.41.

 

Troubleshooting remote monitoring issues

This section provides the causes and resolution of the remote monitoring issues.

If LOGCollectionStatus parameter annotates an error or if the remote monitoring is not working and the BMC PATROL for Log Management KM instances are not being discovered, then the following methods help you to troubleshoot the issue and find out the root cause. 

Troubleshooting insufficient copy privileges

  1. Log into the remote host machine with the same user credentials that is used by the BMC PATROL for UNIX and Linux KM for remote monitoring.
  2. Create a file under the path $HOME/patrol/BMCPatrol/
    1. In case you were not able to create the file.
      1. Use another user for remote monitoring.
      2. Change the user permissions to qualify copying and executing the pmgreader file.

Troubleshooting unsupported target

  1. Log into the remote host machine and run the following cat /etc/*-release command. Check if the returned value is supported by the target machine in the system requirements.

  2. Open the KM logs and check from which folder the pmgreader file is being copied. You need to look for a debug message that matches the following:
    Copying pmgreader file from source <SOURCE_PATH> to host <HOSTNAME>, directory <DESTINATION_PATH>

    Check if the source path folder you found at the logs exists under $PATROL_HOME/pmg/ directory.

    1. If the folder does not exist and there are similar name conventions, this is due to compiling the pmgreader file on newer OS versions.

      For example, the log represents the source path as AIX5.2 but under the pmg path you have AIX5.3. This may happen due to compiling the pmgreader file on newer version of AIX OS but it still works on the remote host.

      Information
      Workaround

      Work around would be to copy the directory content into a new directory. 

      For example, cp -r AIX5.2/ AIX5.3

      Warning

      Note

      In version 2.7.20 and above, the KM logs are located under ‘$PATROL_HOME/logs/’ folder with the pmg_* name convention. 

      Prior to version 2.7.20, the KM logs were written to the SOW (System Output Window) log. In such cases you may need to redirect the PA SOW logs.

Troubleshooting corrupted pmgreader issues

  1. Log into the remote machine using the following path: $HOME/patrol/BMCPatrol/
  2. Run the ./pmgreader –v command

You should be able to see the Log KM version (same version as in the host machine)
image2016-5-2 17:16:40.png 


    1. In case, if the command shows an error message, it indicates that the file is corrupted.
      For example, if the pmgreader file is corrupted then it throws an error message.
      image2016-5-2 17:17:46.png

 

Warning

Note

If nothing is printed after executing the command then it may indicate that there is an execute permission or corrupted pmgreader file issue.

To check if the pmgreader is corrupted by using cksum

You can check the exact file size by using the cksum pmgreader command and do a check between both the pmgreader files at the source and destination directories.

For example, checking the cksum result on remote and local pmgreader files.

Remote host

image2016-5-2 17:13:17.png

Local host

image2016-5-2 17:14:5.png

Information
Workaround

Workaround is to copy the file manually from the source path as described in Troubleshooting unsupported target step 2 to the remote host path $HOME/patrol/BMCPatrol/pmgreader

If the manual copy failed with the timeout exception, this indicates that there is a connection issue between the local and remote hosts, resolve it first and then proceed with the analyses.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC PATROL for Log Management 2.7