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/Makefile.in | |
| 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/Makefile.in')
| -rwxr-xr-x | ctdb/Makefile.in | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/ctdb/Makefile.in b/ctdb/Makefile.in index 48cb57c5d6c..6c822601735 100755 --- a/ctdb/Makefile.in +++ b/ctdb/Makefile.in @@ -359,6 +359,7 @@ install: all $(PMDA_INSTALL) if [ ! -f $(DESTDIR)$(etcdir)/ctdb/notify.sh ];then ${INSTALLCMD} -m 755 config/notify.sh $(DESTDIR)$(etcdir)/ctdb; fi ${INSTALLCMD} -m 755 config/debug-hung-script.sh $(DESTDIR)$(etcdir)/ctdb if [ ! -f $(DESTDIR)$(etcdir)/ctdb/ctdb-crash-cleanup.sh ];then ${INSTALLCMD} -m 755 config/ctdb-crash-cleanup.sh $(DESTDIR)$(etcdir)/ctdb; fi + if [ ! -f $(DESTDIR)$(etcdir)/ctdb/gcore_trace.sh ];then ${INSTALLCMD} -m 755 config/gcore_trace.sh $(DESTDIR)$(etcdir)/ctdb; fi install_pmda: $(INSTALLCMD) -m 755 -d $(PMDA_DEST_DIR) |