On Wed, 12 May 2010 13:01:51 +0200 Foo <bfo...@yahoo.co.uk> wrote: > Just a FYI if someone else runs into this: > > after upgrading from 2.4.3 to 3.0.3 and then to 5.0.2 I'm getting > (ironically) the following mail from logcheck: > > May 12 11:45:10 HOSTNAME bacula-dir: 12-May 11:45 Message delivery ERROR: > Mail prog: /sbin/bsmtp: error while loading shared libraries: > libbac-5.0.1.so: cannot open shared object file: No such file or directory > > May 12 11:45:10 HOSTNAME bacula-dir: 12-May 11:45 Message delivery ERROR: > Mail program terminated in error. CMD=/sbin/bsmtp -h mailgw -f '"Bacula" > <bacula-...@domain>' -s "Bacula: Backup OK of OTHERHOST-fd Incremental" > f...@domain ERR=Child exited with code 127 > > But it does exist: > -rwxr-x--- 1 root root 1010330 2010-05-12 11:11 /usr/lib/libbac-5.0.1.so > > > The fix was to do a chown root:bacula on /usr/lib/libbac* > > The bacula group has the bacula-dir and -sd users in it here, as well as > some people who need to run bconsole (so executables like /sbin/bconsole > are all also root:bacula) > > Not sure if this is handled correctly by packaging, I used source for all > versions so far. >
I just want to confirm that I had the same problem (or very similar). I built 5.0.2 from the src rpm on CentOS 5.4 11-May 17:08 bac-dir JobId 10262: shell command: run BeforeJob "/opt/bacula/scripts/make_catalog_backup.pl MyCatalog" 11-May 17:08 bac-dir JobId 10262: BeforeJob: /opt/bacula/bin/dbcheck: error while loading shared libraries: libbacsql-5.0.1.so: cannot open shared object file: No such file or directory The fix was as Foo suggested (my libs are at a different path): # chown root:bacula /opt/bacula/lib64/libbac* Regards, -- Alex Chekholko ch...@genomics.upenn.edu ------------------------------------------------------------------------------ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users