From 089aec2885fecce4fa202ccc402688c394774dc9 Mon Sep 17 00:00:00 2001 From: Martin Schwenke Date: Mon, 4 Mar 2024 14:29:41 +1100 Subject: [PATCH] ctdb-doc: Drop unnecessary, broken attempt at rpc.statd stack trace There is a typo here, since there will be no process called "status". Instead of fixing it, drop this because rpc.statd isn't the focus of this monitoring check and when systemd is init rpc.statd isn't restarted with nfs-ganesha. It stays running, so a confusing stack trace for rpc.statd is always logged. Signed-off-by: Martin Schwenke Reviewed-by: Amitay Isaacs --- ctdb/doc/examples/20.nfs_ganesha.check | 2 -- 1 file changed, 2 deletions(-) diff --git a/ctdb/doc/examples/20.nfs_ganesha.check b/ctdb/doc/examples/20.nfs_ganesha.check index b153acaedf9..92112aff384 100644 --- a/ctdb/doc/examples/20.nfs_ganesha.check +++ b/ctdb/doc/examples/20.nfs_ganesha.check @@ -4,5 +4,3 @@ unhealthy_after=1 service_stop_cmd="$CTDB_NFS_CALLOUT stop nfs" service_start_cmd="$CTDB_NFS_CALLOUT start nfs" service_check_cmd="$CTDB_NFS_CALLOUT check nfs" -# Ganesha initscript restarts rpc.statd and stack trace is desirable! -service_debug_cmd="program_stack_traces status 5"