Bacula 7.4.3 comms authorization failure on armhf

Bug #1654031 reported by Richard Neighbour
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
bacula (Ubuntu)
New
Undecided
Unassigned

Bug Description

All attempts to connect bconsole or bat to bacula-director, or between bacula-director and bacula-sd fail when version 7.4.3 is deployed on armhf (RPi 2). I have not been able to verify connectivity to bacula-fd 7.4.3 at this time.

Version 7.0.5 is fine on both armhf and amd64 on xenial and yakkity
Version 7.4.3 is fine on amd64 yakkity

Reported error is an authorization problem. e.g.

root@selene:~# bconsole -d 99
Connecting to Director localhost:9101
bconsole: bsock.c:305-0 OK connected to server Director daemon localhost:9101.
Director authorization problem.
Most likely the passwords do not agree.
If you are using TLS, there may have been a certificate validation error during the TLS handshake.
For help, please see http://www.bacula.org/rel-manual/en/problems/Bacula_Frequently_Asked_Que.html

Expected result is a login console which responds to commands :-)

To me this looks to be related to the Bacula 7.4.3 armhf package itself as 7.0.5 works as expected on yakkity and only fails once Bacula is updated (or on a fresh install) so config has been proven prior to the the 7.4.3 update and all the passwords are most definitely correct and TLS is not in use. No errors observed during update process itself.

root@selene:~# lsb_release -rd
Description: Ubuntu 16.10
Release: 16.10

root@selene:~# apt-cache policy bacula-console
bacula-console:
  Installed: 7.4.3+dfsg-1+sid1build1
  Candidate: 7.4.3+dfsg-1+sid1build1
  Version table:
 *** 7.4.3+dfsg-1+sid1build1 500
        500 http://ports.ubuntu.com/ubuntu-ports yakkety/universe armhf Packages
        100 /var/lib/dpkg/status

root@selene:~# apt-cache policy bacula-director-pgsql
bacula-director-pgsql:
  Installed: 7.4.3+dfsg-1+sid1build1
  Candidate: 7.4.3+dfsg-1+sid1build1
  Version table:
 *** 7.4.3+dfsg-1+sid1build1 500
        500 http://ports.ubuntu.com/ubuntu-ports yakkety/universe armhf Packages
        100 /var/lib/dpkg/status

bacula-sd:
  Installed: 7.4.3+dfsg-1+sid1build1
  Candidate: 7.4.3+dfsg-1+sid1build1
  Version table:
 *** 7.4.3+dfsg-1+sid1build1 500
        500 http://ports.ubuntu.com/ubuntu-ports yakkety/universe armhf Packages
        100 /var/lib/dpkg/status

I'm happy to use this install for test & investigation of the issues - rebuilding as needed.

The intended use case is for the RPi to run at least the storage daemon to allow a director running on another host to remotely connect to a USB HD and DAT72 drive. If the director can also be reliably run from the RPi making it a self-contained backup system for a small network that's a bonus. A similar setup using a RPi B+ and Bacula 5.2 has been in use for a few years and works superbly and while Bacula 7 might well be compilable from source on that platform that's not something that fills me with joy.

Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better.

I totally like that you checked Xenial & Yakkety and that on armhf & amd64.
That already points to a specific version.

You said it would not fill you with joy to take it from source, but to help verifying where the issue comes in please could you check the latest upstream version of bacula to see if this is a bug in Ubuntu or in the upstream project itself?
If it turns out to be upstream, this bug would best be submitted and addressed upstream first.

If you want to try something slightly easier first you might try zesty, it only has 7.4.4+dfsg-5 which is a minor update to what is in Yakkety. The changelog doesn't hold an entry that I#d clearly consider a fix to your case. But if you'd consider that easier to try please do so first. If it would fix your case we might bisect from there.

If you do end up filing a bug upstream, please link to it here. Thanks!

tags: added: needs-upstream-report
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.