Hi, Bryn. On 24/12/15 14:17, Bryn Hughes wrote:
>> Thanks for your answers and for the considerations mentioned about the >> versions. >> >> 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. >> >> About using Jessie, is it worth compile the Director and SD? That is, >> improvements regarding the versions provided by Jessie (5.2.6) make a >> substantial difference? What improvements have you noticed? >> >> My idea is to use Jessie for Director and storage daemon. Among the >> client hosts I've Squeeze LTS, CentOS 5.10, Ubuntu and Microsoft Windows >> server (2008R2 SP1 server edition and 2003R2 SP2 standard edition). >> >> From what I was looking for Squeeze, the latest version is on Backports >> (5.2.6) because the version on the squeeze-lts repository is even older >> (5.0.2). I think the Ubuntu version of Bacula is the same as on Debian >> Squeeze. Moreover, I think CentOS does not include Bacula in their >> repositories (at least in the official repositories, according I was >> watching). So maybe in this case the compilation is the only alternative. >> >> Have you found any problem using some version of File Daemon for Windows >> (especially in versions of Windows such as those mentioned above)? > I too am running a 7.0.5 director and storage daemon with mostly 5.2.6 > clients. > > Compiling the 7.x binaries is simple enough on a Debian/Ubuntu box to > make it well worth it. I haven't seen any particular reason to worry > about the file daemon (clients) though, they appear to work fine with > the 5.x binaries as shipped. However on the director/storage side > there's been more than a few bugs squashed between 5.2 and 7.0.5! 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 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. Binaries have the following owners: --------------------------------------------------------------------------- backup:~# ll /usr/sbin/bacula-dir -rwxr-xr-x 1 root root 505728 sep 8 2014 /usr/sbin/bacula-dir backup:~# ll /usr/sbin/bacula-sd -rwxr-xr-x 1 root root 344632 sep 8 2014 /usr/sbin/bacula-sd --------------------------------------------------------------------------- I was making a comparison in a Jessie server using Storage Daemon an Director with Bacula 5.2.6. 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 --------------------------------------------------------------------------- It seems that in the case of the packaged version, the change of user and group is made differently. May have to do with it? Thanks for your replies. Happy Holidays! 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
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
