Hi all! In a virtual machine with Debian Jessie I am testing Bacula 7.2.x. Initially I had downloaded the tarball of here [1] (published in 2015-08-13), but here I got some errors when running the configuration script: --------------------------------------------------------------------------- make[2]: Entering directory '/usr/src/bacula-7.2.0/platforms/systemd' Makefile:24: *** missing separator. Stop. make[2]: Leaving directory '/usr/src/bacula-7.2.0/platforms/systemd' Makefile:88: recipe for target 'clean' failed make[1]: *** [clean] Error 2 make[1]: Leaving directory '/usr/src/bacula-7.2.0/platforms' Makefile:280: recipe for target 'clean' failed make: *** [clean] Error 1 --------------------------------------------------------------------------- According I read on this message [2], it seems that this was fixed by Kern Sibbald on 2015-08-18 in the Git repository, but the tarball was not updated. This makes me wonder if the branch 7.2 is recommended for production or there is another that we consider stable branch. After cloning the "Branch-7.2", I was able to compile without these errors. But I'm having some difficulties with the startup script for the Storage Daemon and Director: --------------------------------------------------------------------------- root@baculatest:~# /etc/init.d/bacula-dir start Starting Bacula Director: start-stop-daemon: unable to start /usr/sbin/bacula-dir (Permission denied) bacula-dir --------------------------------------------------------------------------- root@baculatest:~# /etc/init.d/bacula-sd start Starting Bacula Storage Daemon: start-stop-daemon: unable to start /usr/sbin/bacula-sd (Permission denied) bacula-sd --------------------------------------------------------------------------- In the first case, the following line is executed: --------------------------------------------------------------------------- start-stop-daemon --start --quiet --pidfile /var/run/bacula-dir.9101.pid --chuid bacula:bacula --exec /usr/sbin/bacula-dir -- -c /etc/bacula/bacula-dir.conf --------------------------------------------------------------------------- And in the second runs the following line: --------------------------------------------------------------------------- start-stop-daemon --start --quiet --pidfile /var/run/bacula-sd.9103.pid --chuid bacula:bacula --exec /usr/sbin/bacula-sd -- -c /etc/bacula/bacula-sd.conf --------------------------------------------------------------------------- I've created the "bacula" user and group. I was making a comparison in a Jessie server using Storage Daemon an Director with Bacula 5.2.6 packaged. Here the binaries have the same owners (root:root), but there are some differences in how the binaries are invoked: --------------------------------------------------------------------------- start-stop-daemon --start --quiet --pidfile $PIDFILE --oknodo --exec /usr/sbin/bacula-sd -- -c /etc/bacula/bacula-sd.conf -u bacula -g tape --------------------------------------------------------------------------- start-stop-daemon --start --quiet --pidfile $PIDFILE --oknodo --exec /usr/sbin/bacula-dir -- -c /etc/bacula/bacula-dir.conf -u bacula -g bacula --------------------------------------------------------------------------- Beyond that difference, I found another difference from the binaries permissions, so I changed the permissions for "others": ---------------------------------------------------------------------- root@baculatest:/etc/bacula# ll /usr/sbin/bacula-* -rwxr-x--- 1 root root 2929712 Dec 24 19:50 /usr/sbin/bacula-dir -rwxr-x--- 1 root root 940720 Dec 24 19:50 /usr/sbin/bacula-fd -rwxr-x--- 1 root root 1928928 Dec 24 19:50 /usr/sbin/bacula-sd root@baculatest:/etc/bacula# chmod o+rx /usr/sbin/bacula-* ---------------------------------------------------------------------- Now I do not get the permissions error, but for some reason the processes are not initiated: ---------------------------------------------------------------------- root@baculatest:~# systemctl start bacula-sd.service root@baculatest:~# systemctl status bacula-sd.service ● bacula-sd.service - LSB: Start Bacula Storage daemon at boot time Loaded: loaded (/etc/init.d/bacula-sd) Active: active (exited) since Sat 2015-12-26 11:30:12 ART; 9s ago Process: 2001 ExecStop=/etc/init.d/bacula-sd stop (code=exited, status=0/SUCCESS) Process: 3026 ExecStart=/etc/init.d/bacula-sd start (code=exited, status=0/SUCCESS) Dec 26 11:30:12 baculatest bacula-sd[3026]: Starting Bacula Storage Daemon: bacula-sd ---------------------------------------------------------------------- root@baculatest:~# systemctl start bacula-dir.service root@baculatest:~# systemctl status bacula-dir.service ● bacula-dir.service - LSB: Start Bacula Director daemon at boot time Loaded: loaded (/etc/init.d/bacula-dir) Active: active (exited) since Sat 2015-12-26 11:31:04 ART; 5s ago Process: 2010 ExecStop=/etc/init.d/bacula-dir stop (code=exited, status=0/SUCCESS) Process: 3045 ExecStart=/etc/init.d/bacula-dir start (code=exited, status=0/SUCCESS) Dec 26 11:31:04 baculatest bacula-dir[3045]: Starting Bacula Director: bacula-dir ---------------------------------------------------------------------- But I do not see the running processes: ---------------------------------------------------------------------- root@baculatest:~# ps ax | grep bacula 3055 pts/1 S+ 0:00 grep bacula ---------------------------------------------------------------------- I wonder if anyone on the list had a similar problem and found the cause of the problem. Thanks in advance. Best regards, Daniel [1] http://sourceforge.net/projects/bacula/files/bacula/7.2.0/ [2] http://bacula.10910.n7.nabble.com/Another-weird-configure-error-this-time-systemd-td81943.html
Attachment:
signature.asc
Description: OpenPGP digital signature