Amitay Isaacs 71b89b2b7a ctdb-tool: Correctly print timed out event scripts output ...

The timed out error is ignored for certain events (start_recovery,
recoverd, takeip, releaseip).  If these events time out, then the debug
hung script outputs the following:

 3 scripts were executed last releaseip cycle
 00.ctdb              Status:OK    Duration:4.381 Thu Jul 16 23:45:24 2015
 01.reclock           Status:OK    Duration:13.422 Thu Jul 16 23:45:28 2015
 10.external          Status:DISABLED
 10.interface         Status:OK    Duration:-1437083142.208 Thu Jul 16 23:45:42 2015

The endtime for timed out scripts is not set.  Since the status is not
returned as -ETIME for some events, ctdb scriptstatus prints -ve duration.

Signed-off-by: Amitay Isaacs <amitay@gmail.com>
Reviewed-by: Martin Schwenke <martin@meltin.net>

2015-07-22 11:56:24 +02:00

..

ctdb_diagnostics

ctdb-tools: Update onnode and ctdb-diagnostics to use ctdb -X

2014-12-05 21:02:40 +01:00

ctdb_vacuum.c

ctdb-util: Rename db_wrap to tdb_wrap and make it a build subsystem

2014-09-10 01:36:15 +02:00

ctdb.c

ctdb-tool: Correctly print timed out event scripts output

2015-07-22 11:56:24 +02:00

ltdbtool.c

tool/ltdbtool: -h option does not require an argument

2013-09-25 14:35:46 +10:00

onnode

ctdb-tools: Bracket IP addresses in onnode (for IPv6)

2014-12-05 21:02:40 +01:00