Troubleshooting the Alarm: "The load time ... is greater than the maximum configured acceptable load delay."

Author: Xavier Villarroel November 10, 2023 14:15

Overview

This article provides information on how to troubleshoot the following alarm:

The load time estimated by dividing the size of the files on disk waiting to be loaded by the average loading speed in bytes per s for the last five minutes is greater than the maximum configured acceptable load delay.

Root Cause

The "maximum configured acceptable load delay" alarm indicates that there are too many files to load in the LGP Database.

Diagnosis

This situation is checked every 5 minutes. Hence, to discover if it identifies a real issue, you need to check whether it repeats every 5 minutes or not.

To check the periodicity of the alarm, follow one of the options below:

Search for the LGP messages in the syslog file by running the following command:
```
grep tp_lgp /var/log/messages
```
Search for the LGP messages in the tp_walkall output by running the following command:
```
tp_walkall | grep tp_lgp
```

Back to top

Resolution

If the trap is sent only once, it means that the server caught up in the following 5 minutes interval. In this case, there is nothing to worry about. You can safely clear this alarm.
If the trap is sent every 5 minutes, please file a request in the support portal, and provide the syslog file and the output of the tp_walkall command (the full command is presented in the Diagnosis section above).