Troubleshoot > General troubleshooting

General Troubleshooting

Operations Agent times out before discovery is complete

Problem: Discovery fails with the following error:

0: ERR: <time stamp>: agtrep (24436/139655007979264): (agtrep-133) No output received from discovery policy action
0: ERR: <time stamp>: agtrep (24436/139655007979264): (agtrep-151) Timeout occurred when executing action ""/var/opt/OV/bin/instrumentation/AWSCollect.sh"" - will be terminated.

Solution:Increase the Operations Agent time-out on the node.

  1. On the managed node, run the following in the command prompt:

    ovconfchg -edit 
  2. Increase the timeout as following:

    [agtrep]

    ACTION_TIMEOUT=30

    RESEND_RELATIONSHIP_INSTANCES=TRUE

    [conf.server]

Or

  1. On the managed node, run the following in the command prompt:

    ovconfchg -ns agtrep -set ACTION_TIMEOUT 30
  2. Run the following command to restart :

    ovc -restart agtrep

EC2, EBS, ECS services or cluster data is logged as -1

Problem: Data is not received (no data points) for the default time set.

Solution: To resolve this problem, follow these steps:

  1. Check the AWSMP log file available at the following location:

    /var/opt/OV/log/AWS/ 
  2. If the Datapoints fetched: 0, then edit the respective configuration file available at following location:

    /var/opt/OV/conf/coudmp/AWS/

    List of configuration files available for AWS:

    • AWSECSClusterMetrics.cfg
    • AWSECSServiceMetrics.cfg
    • AWSEBSMetrics.cfg
    • AWSMetrics.cfg
  3. Add a property DELTA=<value> and check for the data. By default, DELTA=10.
  4. Add a property PERIOD=<value> and check for the data. By default, PERIOD=Collection_Frequency.

  5. If the data logged is incorrect, then increase the DELTA value.

AWS Aspect deployment on Agent proxy node fails

To resolve this issue on OMi 10.60, you must update to OMi 10.60 IP1 version.

To resolve this issue on OMi 10.12, you must update to OMi 10.12 IP2 version.

AWSCloudWatchLog.log file is empty or the file does not exist

Problem: An event is generated.

Solution: If the log file is empty, ensure to check the AWS Cloud Watch Log Aspect for policy rules and events. If the log file does not exist, ensure that AWS Cloud Watch Log Aspect is deployed before deploying the AWS Log Collection Aspect.

AddOn Package for Streaming of AWS Logs cannot be imported

Problem: AddOn Package for Streaming of AWS Logs cannot be imported because of unresolved references.

Solution: The AddOn package for streaming of AWS logs is dependent on AWS CloudWatch aspect. Therefore, install the OMi_MP_for_Amazon_Web_Services_01.30.000.zip and then proceed with the re-installation of AddOn package for streaming of  AWS logs.