Kern Sibbald wrote: > It appears that you have backtraced only a single thread. We need to see all > threads. If it was an automatic dump, something went wrong. If you did it > manually, probabably you did not enter "thread apply all bt" as explained in > the Kaboom chapter of the manual.
Aha -- I did this wrong. In my case, two bacula-sd processes were showing up during the hang, and I ran btraceback by hand with the PID of the younger (child?) process only. I saw the lockup again this morning, again with two -sd processes, and ran it with the PID of the older (parent?) process; this gave me a bunch of threads. If it's useful, I can forward the dump. However, I've just recompiled Bacula with the lock manager enabled, and I don't see the hang now. (Worse luck; I was hoping to recreate the hang, get the lock info, apply the patch and see if the problem went away. Dang these race conditions!) Thanks, Hugh -- Hugh Brown, Systems Manager The Centre for High-Throughput Biology [email protected] ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Bacula-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-devel
