Red Hat Bugzilla – Bug 333161
Feature Request: timeout on start/stop actions
Last modified: 2009-05-18 17:13:25 EDT
Description of problem:
We've seen several instances with ClusterSuite where startup or shutdown hangs.
With startup, one of the gfs mounts hung during the mount command. Strace on
the mount command showed no activity in the process, so it was apparently
blocked. During a stop call when relocating services, our clustered application
failed to shutdown and hung.
With the stop failure, it would be possible to add a timer to our stop action of
the /etc/init.d script, but that seems like overkill and it's a pain to do some
of the more advanced features in shell script. It would be desirable if
clustersuite were to set a configurable timer and if the starting of the
application takes too long, it would consider the start to have failed. On the
stop action, it would be desirable to have a similar timer with the possibility
of calling a second action if the timer is exceeded. stop, wait for 5 minutes
and then call the abort action, for example.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
start timeout => normal recovery (i.e., try to stop, then move somewhere else in
stop timeout => critical (i.e. if hardrecovery is set, reboot the node, else,
mark service 'failed')
status timeout => normal recovery
Upstream / community member would also like a status timeout
5.3 commit was:
Fixed in RHEL4.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.