On Wednesday 28 June 2006 17:06, Rumko wrote:
> I had 2 jobs working in parallel on the same pool and same tape drive
> (and ofcourse same volume). Did a status storage=DAT72 (DAT72 is the
> name of the device in sd) ... it stopped in the middle of the output
> (when it wanted to print what jobs are waiting to reserve the drive)
> and I did a ctrl+c ... reran bconsole again, tried again, same thing
> ... repeated that about 2 times I think and then left it alone, after
> a while the director crashed with "Program received signal SIGPIPE,
> Broken pipe." ... :)
I have never seen the Director or any other Bacula daemon "crash" from a
SIGPIPE, and I do not think it is possible. The daemons can report that a
SIGPIPE occurred, but simply breaks the specific TCP/IP connection and should
never cause a crash.
Note, if you do not run Bacula with the options specified in the Kaboom
chapter of the manual, a SIGPIPE *will* interrupt the debugger session, but
that does not imply a crash.
>
>
> Was running both sd and dir in gdb, sd didn't crash, but for dir I've
> attached the bt.
As far as I can see from the traceback the Director did not crash, but then
the symbols have been stripped out, which reduces the amount of information
supplied.
--
Best regards,
Kern
(">
/\
V_V
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
