config_too_long is an indication that event processing takes longer than
the configured expected time for event execution. If the execution
time of an event exceeds a preset timer, the message config_too_long is
logged periodically. There are several reasons why a config_too_long
event may be logged:
1. A large number of resources are processed during the event. In this
case, the event processing time may be within expected tolerances,
hence normal. In this case, to not be unneccesarily alerted by these
messages, you may extend the configured time until warning as follows:
smitty hacmp
Extended Configuration
Extended Event Configuration
Change/Show Time Until Warning
2. Event processing is slow due performance degradation or errors in
other components. Performance would need to be analyzed step by step.
3. Event processing hangs
In cases 1. and 2,. config_too_long messages will occur intermittently,
interleaved with output from the event scripts on nodes where events are
run. In case 3. config_too_long messages will occur without further
logging of event processing.
the configured expected time for event execution. If the execution
time of an event exceeds a preset timer, the message config_too_long is
logged periodically. There are several reasons why a config_too_long
event may be logged:
1. A large number of resources are processed during the event. In this
case, the event processing time may be within expected tolerances,
hence normal. In this case, to not be unneccesarily alerted by these
messages, you may extend the configured time until warning as follows:
smitty hacmp
Extended Configuration
Extended Event Configuration
Change/Show Time Until Warning
2. Event processing is slow due performance degradation or errors in
other components. Performance would need to be analyzed step by step.
3. Event processing hangs
In cases 1. and 2,. config_too_long messages will occur intermittently,
interleaved with output from the event scripts on nodes where events are
run. In case 3. config_too_long messages will occur without further
logging of event processing.
No comments:
Post a Comment