Hi, Greg. On 26/12/15 02:01, Greg Woods wrote:
> > Greg, you mention having compiled the SD on Jessie, but I guess you've > > also compiled the Director, right? Since both must have the same > > version. Though I suppose that the Director may also be on another host > > that includes Bacula 7.0.5 in its repositories. > The latter is correct. Most of my machines are at Fedora 23. At release, > these had 7.0.5, although 7.2.0 update packages have since been > released. The one system that is not Fedora 23 is my Raspberry Pi that I > use as the storage server; that runs Debian Jessie. In order to be able > to use the 7.0.5 director, I had to compile 7.0.5 storage server on > Jessie. The hardest part about this was creating a proper systemd unit > file for bacula-sd. I finally installed the bacula-sd package, saved off > the systemd unit file that it provided, then removed the package and > installed the compiled storage daemon. This all works, but it is very > convoluted. As I mentioned in another mail of this thread, I'm testing in a virtual machine with Bacula 7.2.x. Beyond the mentioned problem (that it can solve compiling the code from the Git repository), I had no problems with systemd files. For that I invoked the configure script with the --with-systemd switch and then: ---------------------------------------------------------------------- root@baculatest:/usr/src/bacula/bacula# make install-autostart-sd (cd platforms && make DESTDIR= install-autostart-sd || exit 1) make[1]: Entering directory '/usr/src/bacula/bacula/platforms' make[2]: Entering directory '/usr/src/bacula/bacula/platforms/debian' Installing bacula-sd boot script ... Installing bacula-sd symlinks ... update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults make[2]: Leaving directory '/usr/src/bacula/bacula/platforms/debian' make[1]: Leaving directory '/usr/src/bacula/bacula/platforms' ---------------------------------------------------------------------- root@baculatest:/usr/src/bacula/bacula# make install-autostart-dir (cd platforms && make DESTDIR= install-autostart-dir || exit 1) make[1]: Entering directory '/usr/src/bacula/bacula/platforms' make[2]: Entering directory '/usr/src/bacula/bacula/platforms/debian' Installing bacula-dir boot script ... Installing bacula-dir symlinks ... update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults make[2]: Leaving directory '/usr/src/bacula/bacula/platforms/debian' make[1]: Leaving directory '/usr/src/bacula/bacula/platforms' ---------------------------------------------------------------------- root@baculatest:/var/log/bacula# systemctl enable bacula-sd Synchronizing state for bacula-sd.service with sysvinit using update-rc.d... Executing /usr/sbin/update-rc.d bacula-sd defaults Executing /usr/sbin/update-rc.d bacula-sd enable ---------------------------------------------------------------------- root@baculatest:/var/log/bacula# systemctl enable bacula-dir Synchronizing state for bacula-dir.service with sysvinit using update-rc.d... Executing /usr/sbin/update-rc.d bacula-dir defaults Executing /usr/sbin/update-rc.d bacula-dir enable ---------------------------------------------------------------------- But now I'm having some problems getting the two processes starts from systemd (I get a "Permission denied" message for both processes). After reviewing more closely, I found the owner and group was correct and it was a issue with the permission bits 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 ---------------------------------------------------------------------- Have you had a problem like this and found the cause of it? > > About using Jessie, is it worth compile the Director and SD? > If you're going to compile one, you should probably compile both. Yes, I have compiled both. > Now I have heard that Fedora 23 can be installed on a Raspberry Pi 2, > and I got one of those for Christmas, so I will be attempting that this > weekend. Interesting Christmas present :-) Good luck with that. Then tell us how it went. > This isn't because I have anything against Debian, it's just > that maintenance will be a lot easier if I can use the distro's package > management system and easily update all the various Bacula components at > the same time. Running "dnf update bacula*" is way easier than compiling > from source and mucking about with systemd. And now I have had to > exclude bacula packages from updates on my systems to avoid having the > file daemons upgraded to a newer version than my storage server, so this > becomes even more of an issue for me now. Yes, I understand. The maintenance and management is easier if we can standardize everything, especially if it is under the umbrella of the repositories systems provided by the distributions. Thanks for your reply. Best regards, Daniel
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
