From: Mantis B. T. <no...@bu...> - 2015-03-11 22:48:28
|
The following issue has been CLOSED ====================================================================== http://bugs.bacula.org/view.php?id=2126 ====================================================================== Reported By: Blindfreddy Assigned To: ====================================================================== Project: Bacula Bug Reports Issue ID: 2126 Category: Director Reproducibility: always Severity: major Priority: normal Status: closed Resolution: no change required Fixed in Version: ====================================================================== Date Submitted: 2015-03-10 11:38 GMT Last Modified: 2015-03-11 22:48 GMT ====================================================================== Summary: Director fails to start after changing from mysql 5.5 to mariadb 10.0 Description: The bacula director fails to start on raspian after 'upgrading' from mysql 5.5 to mariadb 10.0 , because it can no longer connect to the configured Catalog / database. The error log states that the database credentials are incorrect, however, they worked under mysql 5.5 and were not changed. Also, mysql privileges were not changed and access to the Catalog database using mysql client and same credentials works fine. Performing the same database upgrade on ubuntu server 14.04 on an AMD x64 platform works flawlessly, so this seems to be platform specific to raspbian / debian wheezy. Steps to Reproduce: on raspberry pi running raspbian: 1. install bacula-director-mysql 2. validate that the director starts - worked fine for me, can run bconsole and get director status information 3. 'upgrade' mysql to MariaDB as described here: http://blog.pi3g.com/2014/07/easy-mariadb-installation/ 4. when upgrade finishes, restart the director service --> fails. As stated above, same procedure on ubuntu server 14.04 on AMD works fine, ie. director can connect to catalog and runs fine. Additional Information: SW versions on raspberry pi: MariaDb version: 10.0.12+maria-1~wheezy armhf director version: bacula-director-mysql 5.2.6+dfsg-9 armhf log output after upgrade to mariadb: 10-Mar 12:12 bacula-dir JobId 0: Fatal error: Could not open Catalog "MyCatalog", database "bacula". 10-Mar 12:12 bacula-dir JobId 0: Fatal error: mysql.c:210 Unable to connect to MySQL server. Database=bacula User=bacula MySQL connect failed either server not running or your authorization is incorrect. 10-Mar 12:12 bacula-dir ERROR TERMINATION Please correct configuration file: /etc/bacula/bacula-dir.conf root@rpi4:/home/andrev# service bacula-director start [ ok ] Starting Bacula Director...: bacula-dir. root@rpi4:/home/andrev# service bacula-director start [ ok ] Starting Bacula Director...: bacula-dir. root@rpi4:/home/andrev# date && service bacula-director status Tue Mar 10 12:36:20 CET 2015 [ ok ] bacula-dir is running. root@rpi4:/home/andrev# date && service bacula-director status Tue Mar 10 12:36:42 CET 2015 [FAIL] bacula-dir is not running ... failed! root@rpi4:/home/andrev# on ubuntu server: bacula-director-mysql 5.2.6+dfsg-9.1ubuntu3 amd64 mariadb-server-10.0 10.0.17+maria-1~trusty amd64 root@s1:/var/log# service bacula-director status * bacula-dir is running root@s1:/var/log# sudo bconsole Connecting to Director localhost:9101 1000 OK: s1-dir Version: 5.2.6 (21 February 2012) Enter a period to cancel a command. *status Status available for: 1: Director 2: Storage 3: Client 4: All Select daemon type for status (1-4): 1 s1-dir Version: 5.2.6 (21 February 2012) x86_64-pc-linux-gnu ubuntu 14.04 Daemon started 06-Mar-15 17:42. Jobs: run=0, running=0 mode=0,0 Heap: heap=405,504 smbytes=43,071 max_bytes=47,488 bufs=189 max_bufs=195 Scheduled Jobs: Level Type Pri Scheduled Name Volume =================================================================================== Incremental Backup 10 10-Mar-15 23:05 BackupClient1 *unknown* Full Backup 11 10-Mar-15 23:10 BackupCatalog *unknown* ==== Running Jobs: Console connected at 10-Mar-15 12:29 No Jobs running. ==== No Terminated Jobs. ==== *root@s1:/var/log# ====================================================================== ---------------------------------------------------------------------- (0007073) kern (administrator) - 2015-03-11 22:48 http://bugs.bacula.org/view.php?id=2126#c7073 ---------------------------------------------------------------------- Bacula does not support Maria DB thus this is not a bug. Although MariaDB may be quite compatible with MySQL, as best I know, it is not binary compatible, which means that you must at a minimum recompile Bacula with the version of MariaDB you are using. Even if you do so, we do not guarantee that it will work and we do not support it. If your upgrade procedure works with one version of Ubuntu but not with another version, then it appears to be either a Ubuntu or MariaDB version problem. If a developer were to include a DB backend driver that is tested to work with MariaDB, we would certainly consider including it. Not a supported DB backend thus not a bug. Issue History Date Modified Username Field Change ====================================================================== 2015-03-10 11:38 Blindfreddy New Issue 2015-03-11 22:48 kern Note Added: 0007073 2015-03-11 22:48 kern Status new => closed 2015-03-11 22:48 kern Resolution open => no change required ====================================================================== |