Your message dated Wed, 14 Sep 2016 15:21:46 +0200
with message-id <[email protected]>
and subject line bacula-doc: authentication errors when bacula-fd is newer than
the director
has caused the Debian Bug report #806205,
regarding bconsole should report on clients that have newer version than sd/dir
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
806205: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806205
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: bacula-fd
Version: 7.0.5+dfsg-3
Severity: important
Tags: ipv6
Dear Maintainer,
* What led up to the situation?
Upgrading bacula-fd to . (and then to 7.0.5+dfsg-3) on the
client machines, while the backup server (which runs Debian stable)
still uses 5.2.6+dfsg-9.3 for both bacula-director and bacula-sd.
The server would be really difficult to upgrade, it should really
remain in Debian stable.
Only IPV6 communitation is allowed for bacula between the client and
the server. This may be related to bug #742914 that was precisely
fixed in 7.0.5+dfsg-2.
After this upgrade, I get messages like:
16-Nov 20:13 <server-hostname>. JobId 4415: Start Backup JobId 4415,
Job=BackupClient.2015-11-16_20.10.15_44
16-Nov 20:13 <server-hostname>. JobId 4415: Using Device "MyStorage"
16-Nov 20:13 <client-hostname>-fd JobId 4415: Fatal error: Authorization key
rejected by Storage daemon.
Please see http://www.bacula.org/en/rel-
manual/Bacula_Freque_Asked_Questi.html#SECTION00260000000000000000 for help.
16-Nov 20:13 <server-hostname>. JobId 4415: Fatal error: Bad response to
Storage command: wanted 2000 OK storage
, got 2902 Bad storage
16-Nov 20:13 <server-hostname>. JobId 4415: Error: Bacula <server-hostname>.
5.2.6 (21Feb12):
Prior to this update, everything went well.
* What exactly did you do (or not do) that was effective (or
ineffective)?
Reinstalling previous version from jessie (5.2.6+dfsg-9.3).
* What was the outcome of this action?
Going back to previous version worked.
* What outcome did you expect instead?
I would have expected bacula to run regardless of the versions differences
between client and server.
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.2.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages bacula-fd depends on:
ii bacula-common 7.0.5+dfsg-3
ii libacl1 2.2.52-2
ii libc6 2.19-22
ii libcap2 1:2.24-12
ii libgcc1 1:5.2.1-23
ii liblzo2-2 2.08-1.2
ii libssl1.0.2 1.0.2d-3
ii libstdc++6 5.2.1-23
ii libwrap0 7.6.q-25
ii lsb-base 9.20150917
ii ucf 3.0030
ii zlib1g 1:1.2.8.dfsg-2+b1
bacula-fd recommends no packages.
bacula-fd suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 7.4.3-1
It is now clearly documented that a newer file-daemon is not supported
by an older director.
--- End Message ---
