summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorRonnie Sahlberg <ronniesahlberg@gmail.com>2010-10-28 13:43:57 +1100
committerRonnie Sahlberg <ronniesahlberg@gmail.com>2010-10-28 13:45:40 +1100
commita1cfa23d6055fd0843367154026d84d1ca8bc1ae (patch)
tree029f9a901fe7d5e2d49025a435aa17cf031a3d35
parentdb8cb31d8b8d773b5a655354b69e92dd4489c51b (diff)
downloadsamba-a1cfa23d6055fd0843367154026d84d1ca8bc1ae.tar.gz
samba-a1cfa23d6055fd0843367154026d84d1ca8bc1ae.tar.xz
samba-a1cfa23d6055fd0843367154026d84d1ca8bc1ae.zip
Both nfs and nfslock scripts can fail under redhat in very rare situations.
Ctdb can also be configured to ignore checking for knfsd and if it is alive. In that situation, no attempt will be made to restart nfs, and sicne nfs is not running, lockd can not be restarted either. To workaround this, everytime we try to restart the lockmanager, also try to restart nfsd (This used to be ctdb commit 953dbfbddad656a64e30a6aca115cb1479d11573)
-rwxr-xr-xctdb/config/events.d/60.nfs1
1 files changed, 1 insertions, 0 deletions
diff --git a/ctdb/config/events.d/60.nfs b/ctdb/config/events.d/60.nfs
index ed96ab87e7..57c81d3520 100755
--- a/ctdb/config/events.d/60.nfs
+++ b/ctdb/config/events.d/60.nfs
@@ -82,6 +82,7 @@ case "$1" in
(ctdb_check_rpc "lockd" 100021 1)
[ $? = "0" ] || {
echo "Trying to restart lock manager service"
+ startstop_nfs restart
startstop_nfslock restart
exit 1
}