In TDB 1.3.5, tdb_runtime_check_for_robust_mutexes() always returns false on Linux system. With TDB 1.3.4, this works correctly. The culprit is this patch: commit 05b61ea47d1a30e6c37e46c199eb975f79099ed3 Author: Jeremy Allison <jra@samba.org> Date: Fri Mar 20 10:59:08 2015 -0700 lib: tdb: Use sigaction when testing for robust mutexes. Working fix that copes with oldact.sa_handler == NULL if no handler initially set. Fixes bug #11175 - Lots of winbindd zombie processes on Solaris platform. https://bugzilla.samba.org/show_bug.cgi?id=11175 Signed-off-by: Jeremy Allison <jra@samba.org> Reviewed-by: Michael Adam <obnox@samba.org> Reverting this patch fixes the issue.
Just a quick comment: I've just successfully created a mutexed tdb on Ubuntu 12.04. It must be something RHEL specific. Looking deeper.
Making this bug public...
This is only with the standalone tdb build. lib/tdb/wscript does not contain a check for sigaction()
Created attachment 11141 [details] Patch This patch fixes it for me
Created attachment 11142 [details] Possible patches for master
Created attachment 11145 [details] Backported patches for v4-2 branch
Comment on attachment 11145 [details] Backported patches for v4-2 branch We need to backport tdb 1.3.6 completely...
Why do we need to backport the whole thing? This is a very simple bug. We should probably just go with my one-liner that adds the sigaction check.
(In reply to Volker Lendecke from comment #8) Because we need to require 1.3.6 in case we're using a system library. And in case someone does a standalone build in lib/tdb in v4-2-test we should not generate a 1.3.6 build with a different feature set.
Well, why not leave this unfixed then. Isn't a whole new tdb release too much for a Samba point release? Distros are the only ones who will build standalone tdb and they can fix it themselves with my proposed minimal waf build. We will pull much more into an innocent 4.2.next than JUST this bugix if we port back the whole thing.
(In reply to Volker Lendecke from comment #10) The full backport doesn't look too risky to me: https://bugzilla.samba.org/attachment.cgi?id=11154&action=edit And bug #11319 would also be fixed.
Should be fixed with tdb-1.3.6