Can you please explain why this is considered a bug? If the database is corrupt (or at least, the operator configured the package to use a wrong database) isn't this "expected" behavior?
Relevant part of the DpkgTerminalLog.gz:
Creating config file /etc/dbconfig-common/bacula-director-mysql.conf with new version
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2).
unable to connect to mysql server.
error encountered creating user:
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
dbconfig-common: bacula-director-mysql configure: aborted.
Can you please explain why this is considered a bug? If the database is corrupt (or at least, the operator configured the package to use a wrong database) isn't this "expected" behavior?
Relevant part of the DpkgTerminalLog.gz: common/ bacula- director- mysql.conf with new version mysqld/ mysqld. sock' (2). mysqld/ mysqld. sock' (2) director- mysql configure: aborted.
Creating config file /etc/dbconfig-
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/
unable to connect to mysql server.
error encountered creating user:
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/
dbconfig-common: bacula-