Your message dated Sat, 13 May 2006 00:15:11 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#332743: Please check against 1.38
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: bacula-sd
Version: 1.36.2-2sarge1
Severity: important
The bacula-sd process seems to be disppearing when I'm requested
to change tapes, insert a new one and run "mount" in the bconsole.
The last message in the log file was:
============
08-Oct 10:27 torf-sd: FullWeekly.2005-10-08_08.00.00 Warning: Couldn't rewind
device /dev/nst0 ERR=dev.c:406 Rewind error on /dev/nst0. ERR=No medium found.
08-Oct 10:27 torf-sd: Please mount Volume "bacula14" on Storage Device
"Streamer" for Job FullWeekly.2005-10-08_08.00.00
08-Oct 10:27 torf-fd: FullWeekly.2005-10-08_08.00.00 Fatal error: backup.c:477
Network send error 32768 to SD. ERR=Broken pipe
08-Oct 10:27 torf-dir: FullWeekly.2005-10-08_08.00.00 Error: Bacula 1.36.2
(28Feb05): 08-Oct-2005 10:27:35
[...]
SD Errors: 0
FD termination status: Error
SD termination status: Error
Termination: *** Backup Error ***
============
I ran "mount" in the bconsole and it told me that the backup failed. When
looking with "ps ax | grep bacula" there was no "bacula-sd" process any more.
This is my Streamer definition:
Device {
Name = Streamer
Media Type = DDS-3
Archive Device = /dev/nst0
AutomaticMount = yes;
AlwaysOpen = yes;
RemovableMedia = yes;
RandomAccess = no;
VolumePollInterval = 60
OfflineOnUnmount = yes
CloseOnPoll = no
MaximumOpenWait = 2 days
}
P.S.: Strangely the automatic mount doesn't work either. I always need to
issue a "mount" manually after changing tapes.
-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.10
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to de_DE.UTF-8)
Versions of packages bacula-sd depends on:
ii bacula-common 1.36.2-2sarge1 Network backup, recovery and verif
ii debconf 1.4.30.13 Debian configuration management sy
ii libacl1 2.2.23-1 Access control list shared library
ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an
ii libcomerr2 1.37-2sarge1 common error description library
ii libgcc1 1:3.4.3-13 GCC support library
ii libkrb53 1.3.6-2sarge2 MIT Kerberos runtime libraries
ii libpq3 7.4.7-6sarge1 PostgreSQL C client library
ii libssl0.9.7 0.9.7e-3 SSL shared libraries
ii libstdc++5 1:3.3.5-13 The GNU Standard C++ Library v3
ii libwrap0 7.6.dbs-8 Wietse Venema's TCP wrappers libra
ii zlib1g 1:1.2.2-4.sarge.2 compression library - runtime
-- no debconf information
--- End Message ---
--- Begin Message ---
I currently don't want to reproduce it in my production environment. (I
will try that later though.) But according to a statement from the upstream
this is a general problem of the 2.6 kernel with Bacula 1.36. From his mail
on the bacula-users mailing list:
,-----[ Kern Sibbald ]----
| It looks like you stumbled into a change they made in the 2.6 kernel, which
| will undoubtely cause a lot of people a *lot* of pain. The change prohibits
| a program from opening a drive in read/write mode if there is no volume in
| the drive.
|
| If this is what is causing your problem, you can solve it by:
| 1. Ensuring that there is some tape in the drive befort starting the SD,
| and before issuing a "mount" command in the console.
| 2. Upgrade to version 1.38.0
`--------------------
So this issue is known and the upload of 1.38 very likely fixes it.
Kindly
Christoph
--- End Message ---
