Hello Mark,
Apparently, the MySQL service has some problems, and the direct consequence is
that the director cannot start properly.
I would suggest to dig into MySQL logs to determine the problem, maybe a space
problem for example.
Once resolved, you should be able to start the director.
Best Regards,
Eric
On 2/19/24 05:23, Mark Martinson wrote:
Hello – I just upgraded to Bacula 15.0.1 from 13.0.3 on Ubuntu 22.04.1 Server
(Jammy). I run MySQL Server version 8.0.36 with Bacula and up until yesterday
it worked just fine (I had run a few Bacula backups prior to starting the
upgrade). I installed Bacula 13.0.3 and 15.0.1 from the Ubuntu repository by
modifying the /etc/apt sources.list and
/etc/apt/sources.list.d/Bacula-Community.list files. Modifying those files for
both installs worked.
Unfortunately, post the Bacula 15.0.1 upgrade, bacula-dir initially starts
successfully, but eventually stops.
Running $ sudo systemctl status bacula-dir, just after a $ sudo systemctl stop
bacula-dir and restart, I receive:
● bacula-dir.service - Bacula Director Daemon service
Loaded: loaded (/lib/systemd/system/bacula-dir.service; enabled; vendor
preset: enabled)
Active: active (running) since Sun 2024-02-18 22:19:24 CST; 5s ago
Main PID: 2884 (bacula-dir)
Tasks: 2 (limit: 38306)
Memory: 2.1M
CPU: 13ms
CGroup: /system.slice/bacula-dir.service
└─2884 /opt/bacula/bin/bacula-dir -fP -c
/opt/bacula/etc/bacula-dir.conf
Feb 18 22:19:24 LinuxS-WS1 systemd[1]: Started Bacula Director Daemon service.
Waiting a little bit and re-running status, I receive the following errors:
Command $ sudo systemctl status bacula-dir, results in:
× bacula-dir.service - Bacula Director Daemon service
Loaded: loaded (/lib/systemd/system/bacula-dir.service; enabled; vendor
preset: enabled)
Active: failed (Result: exit-code) since Sun 2024-02-18 21:02:12 CST;
54min ago
Process: 2144 ExecStart=/opt/bacula/bin/bacula-dir -fP -c
/opt/bacula/etc/bacula-dir.conf (code=exited, status=1/FAILURE)
Main PID: 2144 (code=exited, status=1/FAILURE)
CPU: 20ms
Feb 18 21:02:12 LinuxS-WS1 bacula-dir[2144]: MySQL connect failed either server
not running or your authorization is incorrect.
Feb 18 21:02:12 LinuxS-WS1 bacula-dir[2144]: 18-Feb 21:02 bacula-dir ERROR
TERMINATION
Feb 18 21:02:12 LinuxS-WS1 bacula-dir[2144]: Please correct configuration file:
/opt/bacula/etc/bacula-dir.conf
Feb 18 21:02:12 LinuxS-WS1 systemd[1]: bacula-dir.service: Main process exited,
code=exited, status=1/FAILURE
Feb 18 21:02:12 LinuxS-WS1 systemd[1]: bacula-dir.service: Failed with result
'exit-code'.
Note that both bacula-sd and bacula-fd are active and running without errors on
this machine.
Running $ sudo systemctl status mysql, I receive:
mysql.service - MySQL Community Server
Loaded: loaded (/lib/systemd/system/mysql.service; enabled; vendor
preset: enabled)
Active: failed (Result: exit-code) since Sun 2024-02-18 21:00:03 CST;
58min ago
Process: 1479 ExecStartPre=/usr/share/mysql/mysql-systemd-start pre
(code=exited, status=1/FAILURE)
CPU: 8ms
Feb 18 21:00:03 LinuxS-WS1 systemd[1]: mysql.service: Scheduled restart job,
restart counter is at 5.
Feb 18 21:00:03 LinuxS-WS1 systemd[1]: Stopped MySQL Community Server.
Feb 18 21:00:03 LinuxS-WS1 systemd[1]: mysql.service: Start request repeated
too quickly.
Feb 18 21:00:03 LinuxS-WS1 systemd[1]: mysql.service: Failed with result
'exit-code'.
Feb 18 21:00:03 LinuxS-WS1 systemd[1]: Failed to start MySQL Community Server.
Trying to login to mysql by running $ mysql -u root -p (and entering the proper
passcode when prompted), I receive:
ERROR 2002 (HY000): Can't connect to local MySQL server through socket
'/var/run/mysqld/mysqld.sock' (2)
Trying to restart mysql server by running $ sudo systemctl restart mysql, I
receive:
Job for mysql.service failed because the control process exited with error code.
See "systemctl status mysql.service" and "journalctl -xeu mysql.service" for
details.
Entering $ systemctl status mysql.service, I receive:
× mysql.service - MySQL Community Server
Loaded: loaded (/lib/systemd/system/mysql.service; enabled; vendor
preset: enabled)
Active: failed (Result: exit-code) since Sun 2024-02-18 22:02:28 CST; 39s
ago
Process: 2783 ExecStartPre=/usr/share/mysql/mysql-systemd-start pre
(code=exited, status=1/FAILURE)
CPU: 10ms
Feb 18 22:02:28 LinuxS-WS1 systemd[1]: mysql.service: Scheduled restart job,
restart counter is at 5.
Feb 18 22:02:28 LinuxS-WS1 systemd[1]: Stopped MySQL Community Server.
Feb 18 22:02:28 LinuxS-WS1 systemd[1]: mysql.service: Start request repeated
too quickly.
Feb 18 22:02:28 LinuxS-WS1 systemd[1]: mysql.service: Failed with result
'exit-code'.
Feb 18 22:02:28 LinuxS-WS1 systemd[1]: Failed to start MySQL Community Server.
Entering $ journalctl -xeu mysql.service, I receive:
The process' exit code is 'exited' and its exit status is 1.
Feb 18 22:02:27 LinuxS-WS1 systemd[1]: mysql.service: Failed with result
'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit mysql.service has entered the 'failed' state with result
'exit-code'.
Feb 18 22:02:27 LinuxS-WS1 systemd[1]: Failed to start MySQL Community Server.
░░ Subject: A start job for unit mysql.service has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit mysql.service has finished with a failure.
░░
░░ The job identifier is 3924 and the job result is failed.
Feb 18 22:02:28 LinuxS-WS1 systemd[1]: mysql.service: Scheduled restart job,
restart counter is at 5.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ Automatic restarting of the unit mysql.service has been scheduled, as the
result for
░░ the configured Restart= setting for the unit.
Feb 18 22:02:28 LinuxS-WS1 systemd[1]: Stopped MySQL Community Server.
░░ Subject: A stop job for unit mysql.service has finished
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A stop job for unit mysql.service has finished.
░░
░░ The job identifier is 4047 and the job result is done.
Feb 18 22:02:28 LinuxS-WS1 systemd[1]: mysql.service: Start request repeated
too quickly.
Feb 18 22:02:28 LinuxS-WS1 systemd[1]: mysql.service: Failed with result
'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit mysql.service has entered the 'failed' state with result
'exit-code'.
Feb 18 22:02:28 LinuxS-WS1 systemd[1]: Failed to start MySQL Community Server.
░░ Subject: A start job for unit mysql.service has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit mysql.service has finished with a failure.
░░
░░ The job identifier is 4047 and the job result is failed.
lines 5960-6004/6004 (END)
I checked the /etc/mysql/my.cnf file and the following three (3) lines are
uncommented:
[client-server]
port = 3306
socket = /var/run/mysqld/mysqld.sock
I did restart multiple times and try stopping and restarting bacula-dir and
mysql, but nothing is working.
I have backed up the relevant MySQL files – both with a Bacula backup and also
with an rsync to a secondary location prior to installing 15.0.1. I did not
uninstall and re-install mysql yet because I did read that you do need to purge
and clean the existing mysql files prior to reinstalling it. I was not sure
how this would affect Bacula. Do you have any thoughts on how I can reconnect
Bacula and MySQL and/or get MySQL back up and running? If you would like the
text of the relevant mysql and mysqld files, I would be happy to send it.
Many thanks for all of your help!
-Mark
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
