bacula-dir.conf shows syntax error when mysql dbname is left blank
Bug #689327 reported by
kenchan
This bug affects 5 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| bacula (Debian) |
Fix Released
|
Unknown
|
|||
| bacula (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
| dbconfig-common (Ubuntu) |
Fix Released
|
Low
|
Unassigned | ||
Bug Description
Binary package hint: bacula
????
ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: bacula-
ProcVersionSign
Uname: Linux 2.6.32-27-generic i686
Architecture: i386
Date: Mon Dec 13 02:13:26 2010
ErrorMessage: サブプロセス installed post-installation script はエラー終了ステータス 1 を返しました
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
SourcePackage: bacula
Title: package bacula-
Related branches
Revision history for this message
| kenchan (kenchan-sun) wrote | #1 |
Revision history for this message
| Clint Byrum (clint-fewbar) wrote | #2 |
| summary: |
- package bacula-director-mysql 5.0.1-1ubuntu1 failed to install/upgrade: - サブプロセス installed post-installation script はエラー終了ステータス 1 を返しました + bacula-dir.conf shows syntax error when dbname is left blank |
| Changed in bacula (Ubuntu): | |
| status: | New → Triaged |
| summary: |
- bacula-dir.conf shows syntax error when dbname is left blank + bacula-dir.conf shows syntax error when mysql dbname is left blank |
| Changed in dbconfig-common (Ubuntu): | |
| importance: | Undecided → Low |
| status: | New → Confirmed |
| Changed in bacula (Debian): | |
| status: | Unknown → Fix Committed |
| Changed in bacula (Debian): | |
| status: | Fix Committed → Fix Released |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #3 |
| Changed in bacula (Ubuntu): | |
| status: | Triaged → Fix Released |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #4 |
| Changed in dbconfig-common (Ubuntu): | |
| status: | Confirmed → Fix Released |
To post a comment you must log in.
Hello kenchan, thanks for filing this (separate) bug report and working with us to make Ubuntu better.
The relevant error message is here:
dbconfig-common: writing config to /etc/dbconfig-
Creating config file /etc/dbconfig-
Processing configuration...Ok.
* Starting Bacula Director...
13-12月 02:13 bacula-dir: ERROR TERMINATION at lex.c:784
Config error: expected a string, got T_EOL: =
: line 236, col 12 of file /etc/bacula/
dbname = ; DB Address = ""; dbuser = ""; dbpassword = ""
...fail!
This happened because you did not enter any configuration value for 'dbname'. There may be db backends where that is ok (I think pgsql will put user here if it is empty), but it should surround the value in quotes like the address/
This occurs because of the way the file is generated in debian/
I'm also going to add dbconfig-common because it should never allow an empty dbname for mysql, as this is never actually a valid situation.