diff options
| author | Martin Schwenke <martin@meltin.net> | 2014-02-07 17:37:00 +1100 |
|---|---|---|
| committer | Amitay Isaacs <amitay@gmail.com> | 2014-02-19 12:04:47 +1100 |
| commit | 2532149f8f9bbe6d3c8f5ac6e5e4bc2ad1681e27 (patch) | |
| tree | 9d23e4a4a0a3621cd511f5c77b45ed3247a0af86 /ctdb/doc | |
| parent | 79e2725f339e7c5336b4053348c4266268de6ca3 (diff) | |
| download | samba-2532149f8f9bbe6d3c8f5ac6e5e4bc2ad1681e27.tar.gz | |
ctdb-scripts: Enhancements to hung script debugging
* Add stack dumps for "interesting" processes that sometimes get
stuck, so try to print stack traces for them if they appear in the
pstree output.
* Add new configuration variables CTDB_DEBUG_HUNG_SCRIPT_LOGFILE and
CTDB_DEBUG_HUNG_SCRIPT_STACKPAT. These are primarily for testing
but the latter may be useful for live debugging.
* Load CTDB configuration so that above configuration variables can be
set/changed without restarting ctdbd.
Add a test that tries to ensure that all of this is working.
Signed-off-by: Martin Schwenke <martin@meltin.net>
Reviewed-by: Amitay Isaacs <amitay@gmail.com>
Diffstat (limited to 'ctdb/doc')
| -rw-r--r-- | ctdb/doc/ctdbd.conf.5.xml | 30 |
1 files changed, 30 insertions, 0 deletions
diff --git a/ctdb/doc/ctdbd.conf.5.xml b/ctdb/doc/ctdbd.conf.5.xml index a1f6db5ef61..37b1cf94cbb 100644 --- a/ctdb/doc/ctdbd.conf.5.xml +++ b/ctdb/doc/ctdbd.conf.5.xml @@ -1375,6 +1375,36 @@ CTDB_SET_MonitorInterval=20 </varlistentry> <varlistentry> + <term>CTDB_DEBUG_HUNG_SCRIPT_LOGFILE=<parameter>FILENAME</parameter></term> + <listitem> + <para> + FILENAME specifies where log messages should go when + debugging hung eventscripts. This is a testing option. + See also <citetitle>CTDB_DEBUG_HUNG_SCRIPT</citetitle>. + </para> + <para> + No default. Messages go to stdout/stderr and are logged + to the same place as other CTDB log messages. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>CTDB_DEBUG_HUNG_SCRIPT_STACKPAT=<parameter>REGEXP</parameter></term> + <listitem> + <para> + REGEXP specifies interesting processes for which stack + traces should be logged when debugging hung eventscripts + and those processes are matched in pstree output. See + also <citetitle>CTDB_DEBUG_HUNG_SCRIPT</citetitle>. + </para> + <para> + Default is "exportfs\|rpcinfo". + </para> + </listitem> + </varlistentry> + + <varlistentry> <term>CTDB_DEBUG_LOCKS=<parameter>FILENAME</parameter></term> <listitem> <para> |