Tanti Technology

My photo
Bangalore, karnataka, India
Multi-platform UNIX systems consultant and administrator in mutualized and virtualized environments I have 4.5+ years experience in AIX system Administration field. This site will be helpful for system administrator in their day to day activities.Your comments on posts are welcome.This blog is all about IBM AIX Unix flavour. This blog will be used by System admins who will be using AIX in their work life. It can also be used for those newbies who want to get certifications in AIX Administration. This blog will be updated frequently to help the system admins and other new learners. DISCLAIMER: Please note that blog owner takes no responsibility of any kind for any type of data loss or damage by trying any of the command/method mentioned in this blog. You may use the commands/method/scripts on your own responsibility. If you find something useful, a comment would be appreciated to let other viewers also know that the solution/method work(ed) for you.

Thursday, 14 November 2013

config_too_long error in HACMP

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.


No comments:

Post a Comment