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-common/bacula-director-
mysql.conf
Creating config file /etc/dbconfig-common/bacula-director-mysql.conf with new
version
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/bacula-dir.conf
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/user/password.
This occurs because of the way the file is generated in debian/bacula-
director-mysql.postinst and could be corrected by simply wrapping the
dbname in quotes. Marking this Triaged.
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.
** Summary changed:
- 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 changed:
- bacula-dir.conf shows syntax error when dbname is left blank
+ bacula-dir.conf shows syntax error when mysql dbname is left blank
** Also affects: dbconfig-common (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/689327
Title:
bacula-dir.conf shows syntax error when mysql dbname is left blank
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
