samba.git/ctdb/config/debug-hung-script.sh, branch talloc-2.1.3

ctdb-scripts: Fix stack dumping when debugging hung scripts

2014-11-18T05:37:44+00:00

There are parentheses missing that stop the default pattern from
matching commands with trailing garbage (e.g. "exportfs.orig").

A careful check of POSIX (and running GNU sed with --posix) suggests
that "\|" isn't a supported way of specifying alternation in a regular
expression.  Therefore, it is clearer to switch to extended regular
expressions so that this has a chance of being portable (even though
the point is to print /proc//stack, which only works on Linux).

Signed-off-by: Martin Schwenke 
Reviewed-by: Amitay Isaacs 

Autobuild-User(master): Amitay Isaacs 
Autobuild-Date(master): Tue Nov 18 06:37:45 CET 2014 on sn-devel-104

ctdb-tests: Fix racy test for debugging hung scripts

2014-07-03T06:19:22+00:00

Debugging can still be running when a monitor event times out and
scriptstatus output changes.

When debugging a hung script to a log file, write to a temporary file
and move the temporary file over the log file when done.  The test
then waits for the log file to appear.

Signed-off-by: Martin Schwenke 
Reviewed-by: Amitay Isaacs 

Autobuild-User(master): Amitay Isaacs 
Autobuild-Date(master): Thu Jul  3 08:19:23 CEST 2014 on sn-devel-104

ctdb-scripts: Always print footer when debugging hung script

2014-07-03T03:55:13+00:00

There shouldn't be an early exit for the "init" event.  Just make the
"ctdb scriptstatus" call conditional.

While here, move the comment about only running a single instance to
be near locking code.  The comment is more useful there.

Signed-off-by: Martin Schwenke 
Reviewed-by: Amitay Isaacs

ctdb-scripts: Enhancements to hung script debugging

2014-02-19T01:04:47+00:00

* 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 
Reviewed-by: Amitay Isaacs

scripts: Do not run ctdb tool commands when debugging hung "init" event

2013-08-09T01:04:55+00:00

CTDB daemon is not ready to accept clients in INIT runstate (init event).
CTDB daemon will start accepting connections in SETUP runstate (setup event)
and later.

Also, minor log formatting changes.

Signed-off-by: Martin Schwenke 

(This used to be ctdb commit 81d7ce03b28d592a1337639e14d9ea141e20bfff)

scripts: Run scriptstatus for hung event

2013-07-29T04:02:13+00:00

The timeout information printed by ctdbd is less than useful because
it refers to the cumulative time taken by the eventscripts run so far.
Adding scriptstatus output indicates where time was actually spent.

Since there is now quite a bit of output, serialise the calls to this
script using flock.

Signed-off-by: Martin Schwenke 
Pair-programmed-with: Amitay Isaacs 

(This used to be ctdb commit 1b016b2dfc5d7d3f2a42ce4dfe569608e90eb714)

scripts: debug-hung-script.sh doesn't need functions/loadconfig

2013-01-08T04:18:47+00:00

Signed-off-by: Martin Schwenke 

(This used to be ctdb commit 8507303b525d20c74e8ec4e7c4f5f275945cd3b6)

Debug: When scripts hang, we may need to collect additional data in order to debug why the script hung.

2012-05-17T00:29:03+00:00

Break this debug and datacollection out into an external script to make it easier to modify what data we need to collect.
For now we only collect a pstree so we can see what part of the script we hung in.

S1037271

(This used to be ctdb commit 6e68797af67bee36f2bad045f94806e7e98f27e9)