Menu
▾
▴
[Bacula-bugs] [bacula 0000389]: FD freeze during backup
|
From: <bac...@li...> - 2005-07-30 18:57:49
|
The following bug has been CLOSED ====================================================================== http://bugs.bacula.org/bug_view_advanced_page.php?bug_id=0000389 ====================================================================== Reported By: jaworski Assigned To: ====================================================================== Project: bacula Bug ID: 389 Category: Win32 File Daemon (client) Reproducibility: sometimes Severity: major Priority: normal Status: closed ====================================================================== Date Submitted: 07-29-2005 11:35 PDT Last Modified: 07-30-2005 11:57 PDT ====================================================================== Summary: FD freeze during backup Description: My Bacula 1.37.30 and Windows Bacula-FD with Volume Shadow Copy Enabled. My test job freezed durning backup when all volumes was full (cannot find appendable volumes). When I cancel this job, Bacula write on Bconsole screen: Automatically selected Job: JobId=55 Job=dti6a.2005-07-29_19.21.09 Confirm cancel (yes/no): yes 2001 Job dti6a.2005-07-29_19.21.09 marked to be canceled. 3000 Job dti6a.2005-07-29_19.21.09 marked to be canceled. * EOD EOF EOD EOF EOD EOF EOD EOF EOD EOFbacula-sd: append.c:249 NULL Volume name. This shouldn't happen!!! bacula-sd: append.c:276 NULL Volume name. This shouldn't happen!!! ====================================================================== ---------------------------------------------------------------------- jaworski - 07-29-2005 11:55 PDT ---------------------------------------------------------------------- This bug possibly don't refer with Win32 File Daemon as I previously suspected, but Director or Storage Daemon... ---------------------------------------------------------------------- kern - 07-30-2005 11:57 PDT ---------------------------------------------------------------------- Although part of the error message was not appropriate, this is not a bug. As far as I can see, your job did not freeze at all, but was blocked because you did not label a new Volume as it requested. If you don't understand this, please read the tutorial chapter of the manual, and ask on the bacula-users email list. I've suppressed the message that said that a Null volume name should not happen (it is in fact the case when the job is canceled). Bug History Date Modified Username Field Change ====================================================================== 07-29-05 11:35 jaworski New Bug 07-29-05 11:55 jaworski Bugnote Added: 0001090 07-30-05 11:57 kern Bugnote Added: 0001092 07-30-05 11:57 kern Resolution open => not a bug 07-30-05 11:57 kern Status new => closed ====================================================================== |