diff options
| author | Martin Schwenke <martin@meltin.net> | 2012-09-06 20:22:38 +1000 |
|---|---|---|
| committer | Martin Schwenke <martin@meltin.net> | 2012-10-18 20:05:42 +1100 |
| commit | 8d7562f3f8a0e62d9348c4a4ee72ffd8f1e41c4a (patch) | |
| tree | 5abb1035fb4dd3f0bd8c6d9550786e280ae8438c /ctdb/include/ctdb_private.h | |
| parent | 6372592982fd7302524bb9926f56029c57fe2037 (diff) | |
| download | samba-8d7562f3f8a0e62d9348c4a4ee72ffd8f1e41c4a.tar.gz samba-8d7562f3f8a0e62d9348c4a4ee72ffd8f1e41c4a.tar.xz samba-8d7562f3f8a0e62d9348c4a4ee72ffd8f1e41c4a.zip | |
common: Debug ctdb_addr_to_str() using new function ctdb_external_trace()
We've seen this function report "Unknown family, 0" and then CTDB
disappeared without a trace. If we can reproduce it then this might
help us to debug it.
The idea is that you do something like the following in /etc/sysconfig/ctdb:
export CTDB_EXTERNAL_TRACE="/etc/ctdb/config/gcore_trace.sh"
When we hit this error than we call out to gcore to get a core file so
we can do forensics. This might block CTDB for a few seconds.
Signed-off-by: Martin Schwenke <martin@meltin.net>
(This used to be ctdb commit 7895bc003f087ab2f3181df3c464386f59bfcc39)
Diffstat (limited to 'ctdb/include/ctdb_private.h')
| -rw-r--r-- | ctdb/include/ctdb_private.h | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/ctdb/include/ctdb_private.h b/ctdb/include/ctdb_private.h index 94b45c0d850..6f6d898167d 100644 --- a/ctdb/include/ctdb_private.h +++ b/ctdb/include/ctdb_private.h @@ -666,6 +666,7 @@ struct ctdb_fetch_handle { /* internal prototypes */ void ctdb_set_error(struct ctdb_context *ctdb, const char *fmt, ...) PRINTF_ATTRIBUTE(2,3); void ctdb_fatal(struct ctdb_context *ctdb, const char *msg); +void ctdb_external_trace(void); bool ctdb_same_address(struct ctdb_address *a1, struct ctdb_address *a2); int ctdb_parse_address(struct ctdb_context *ctdb, TALLOC_CTX *mem_ctx, const char *str, |