Kern Sibbald wrote:
> At this point some sort of SCSI hardware problem is the highest probability as
> I see it. If you can show that it is closelog(), then I would re-evaluate
> that.
Just so this gets to the mailing list archives: I think I've tracked
this down to a problem with calling closelog(), a non-threadsafe libc
routine, after fork(). I've added more backtraces and a detailed
explanation to the bug report here:
http://bugs.bacula.org/view.php?id=1536
I can work around this by disabling the syslog directive in the
Messages stanza of bacula-sd.conf:
Messages {
Name = Standard
director = agnatha-dir = all
syslog = all, !skipped
}
With that "syslog = all" line commented out, the problem goes away;
with it enabled, I can reproduce the hang fairly regularly.
Thanks, and please let me know if you have any questions.
--
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
