sin/samba-mirror
1
0
Fork 0
mirror of https://github.com/samba-team/samba.git synced 2025-01-10 01:18:15 +03:00
Code
40380a8042
samba-mirror/ctdb/config/nfs-checks.d/10.status.check

8 lines
208 B
Plaintext
Raw Normal View History

ctdb-scripts: Switch NFS checks to new style Note that the 60.ganesha RPC checks need to be identical to those in the nfs-checks.d/ directory. This is because the NFS unit test infrastructure checks output against what should be produced by the checks in nfs-checks.d/. This is a minor issue, since one of the aims of this work is to remove the need for a separate 60.ganesha. In most cases configuration variable CTDB_NFS_DUMP_STUCK_THREADS is now ignored. This is now handled by passing the desired number of threads to the command specified in the service_debug_cmd variable in a .check file. Signed-off-by: Martin Schwenke <martin@meltin.net> Reviewed-by: Amitay Isaacs <amitay@gmail.com>
2015-06-19 09:35:12 +03:00
# status
version="1"
restart_every=2
unhealthy_after=6
ctdb-scripts: Stop/start mount/rquotad/status via NFS call-out When an NFS check restarts a failed service by hand then systemd will be unable to stop or start this service again because (at least) the PID file will be wrong. Do this via the NFS Linux kernel call-out instead. Allow the call-out to use the services instead of doing manual restarts. Add variables for mount, status and rquotad services to support this. Adding systemd NFS services to the call-out will follow. BUG: https://bugzilla.samba.org/show_bug.cgi?id=13860 Signed-off-by: Martin Schwenke <martin@meltin.net> Reviewed-by: Amitay Isaacs <amitay@samba.org>
2019-03-20 09:35:44 +03:00
service_stop_cmd="$CTDB_NFS_CALLOUT stop status"
service_start_cmd="$CTDB_NFS_CALLOUT start status"
ctdb-scripts: Switch NFS checks to new style Note that the 60.ganesha RPC checks need to be identical to those in the nfs-checks.d/ directory. This is because the NFS unit test infrastructure checks output against what should be produced by the checks in nfs-checks.d/. This is a minor issue, since one of the aims of this work is to remove the need for a separate 60.ganesha. In most cases configuration variable CTDB_NFS_DUMP_STUCK_THREADS is now ignored. This is now handled by passing the desired number of threads to the command specified in the service_debug_cmd variable in a .check file. Signed-off-by: Martin Schwenke <martin@meltin.net> Reviewed-by: Amitay Isaacs <amitay@gmail.com>
2015-06-19 09:35:12 +03:00
service_debug_cmd="program_stack_traces rpc.statd 5"
Copy Permalink