bacula-director-mysql config results in bad bacula-dir.conf
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bacula (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
After installation and configuration via debconf, bacula-mysql is broken.
10-Feb 13:57 bacula-dir JobId 0: Fatal error: Could not open Catalog "MyCatalog", database "bacula;".
10-Feb 13:57 bacula-dir JobId 0: Fatal error: mysql.c:203 Unable to connect to MySQL server.
Database=bacula; User=bacula
MySQL connect failed either server not running or your authorization is incorrect.
10-Feb 13:57 bacula-dir ERROR TERMINATION
Please correct configuration file: /etc/bacula/
10-Feb 13:58 bacula-dir JobId 0: Fatal error: Could not open Catalog "MyCatalog", database "bacula;".
10-Feb 13:58 bacula-dir JobId 0: Fatal error: mysql.c:203 Unable to connect to MySQL server.
Database=bacula; User=bacula
MySQL connect failed either server not running or your authorization is incorrect.
The issue is that it is trying to connect to "bacula;" (the ; is wrong).
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: bacula-
ProcVersionSign
Uname: Linux 3.2.0-14-virtual x86_64
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
Date: Fri Feb 10 14:12:49 2012
Ec2AMI: ami-0000013a
Ec2AMIManifest: FIXME
Ec2Availability
Ec2InstanceType: m1.small
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: bacula
UpgradeStatus: No upgrade log present (probably fresh install)