Hello Josip I don't know why, but I've run ldconfig several time and didn't worked, only when I remove the /etc/ld.so.cache that s3 worked.
Best regards *Wanderlei Hüttel* Em qui., 17 de jun. de 2021 às 07:04, Josip Deanovic < djosip+n...@linuxpages.net> escreveu: > On Wednesday 2021-06-16 16:44:34 Wanderlei Huttel wrote: > > Hello Erick > > > > I guess I've discovered the problem. > > I had to remove the libs cache "rm /etc/ld.so.cache" and just > > run "ldconfig" to create a new cache and then running command "s3" > > worked fine. > > > > I guess my bacula configuration (director and storage are OK), I've made > > a backup and it worked. > > > Hello! > > You don't have to remove /etc/ld.so.cache file. Just run ldconfig. > > By default only libraries found in /lib and /usr/lib will be cached. > Recent Linux distributions removed lib directory and replaced it with a > symlink pointing to usr/lib in the root directory. > > Suse 9 and probably 10 and later, used to run ldconfig with a specific > config file with every package install or update thus ignoring > /etc/ld.so.conf file which is just one of many bad decisions they did. > > > Regards! > > -- > Josip Deanovic > > > _______________________________________________ > Bacula-users mailing list > Bacula-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bacula-users >
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
