Re: [Bacula-users] Bacula 15.02 upgrade on Centos 7 -- Storage Daemon not starting

[Bill Arlofski via Bacula-users]

On 4/2/24 9:54 AM, sruckh--- via Bacula-users wrote:

I have upgraded from 13.x to 15.02 on a CentOS 7 server by changing yum repository and running yum update.  After RPMs were upgraded, I ran the scripts to upgrade the MySQL database.  When I try to start bacula-sd using systemctl no errors are returned, but the storage daemon is not starting (as seen by running 'ps -ef | grep bacula' ).  Running journalctl for bacula-sd does not show that bacula-sd is failing.

The systemctl status for bacula-sd is returning the following:

<SNIP> hostname removed to protect the innocent

● bacula-sd.service - Bacula Storage Daemon service
Loaded: loaded (/usr/lib/systemd/system/bacula-sd.service; enabled; vendor 
preset: disabled)
Active: inactive (dead) since Tue 2024-04-02 08:18:13 MST; 18min ago
Process: 4066 ExecStart=/opt/bacula/bin/bacula-sd -dt -c 
/opt/bacula/etc/bacula-sd.conf (code=exited, status=0/SUCCESS)
Main PID: 19946 (code=exited, status=1/FAILURE)

Apr 02 08:18:13 xxx.xxx.xxx systemd[1]: Starting Bacula Storage Daemon 
service...
Apr 02 08:18:13 xxx.xxx.xxx systemd[1]: Started Bacula Storage Daemon service.

</SNIP>



If the storage daemon is instead started manually from the command line (as 
root user) using the following command the storage daemon starts and does not 
terminate:

sudo /opt/bacula/bin/bacula-sd -d 200 -c /opt/bacula/etc/bacula-sd.conf

There is nothing in the system logs that would help narrow down the problem.  There is also nothing logged in /opt/bacula/log/bacula.log that mentions problems with the storage daemon.

Hello,

More than likely, the above command is/was the initial cause of your problem.

The Bacula SD typically runs as the user 'bacula'.





Try testing the config file syntax first with this:

# sudo -u bacula /opt/bacula/bin/bacula-sd -t



# sudo -u bacula /opt/bacula/bin/bacula-sd -d100 -f

Then, `chown bacula:bacula` any files it complains about, and try again until 
it starts up and remains running.

Next, find any file volumes the SD may have written to when run from the 
command line previously and chown them too.

Then, ctrl-c the running bacula-sd, and try to start with systemd, it should 
work now.


Hope this helps,
Bill

--
Bill Arlofski
w...@protonmail.com

Starting the SD as root (as shown above with the sudo command), will cause the SD to open its PID and state files (and any file volumes) as the root user. Later, when you try to start it with systemd - which will run it as the bacula user - it will not have access to these files and will just silently fail to start. That might/should fail with some read and/or write permissions on one or more files. If it does not fail, then start the SD in foreground more like:

signature.asc
Description: OpenPGP digital signature

_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users