From: Eric B. <eri...@ba...> - 2011-03-30 08:06:43
|
Hello Philipp, Le dimanche 27 mars 2011 11:03:24, Philipp Storz a écrit : > Hello bacula developers, > > we found that the bacula start scripts do not start the bacula daemons > with the parameters for user and group. > As a result, the daemons always run as root/root. > > I have attached a patch that patches the template files for the start > scripts , so that the daemons are started correctly. Can you make a try to add the -u and -g option to the startproc program instead of the bacula daemon? When you have a problem such as a segfault, the process can't attach gdb to itself because the uid/gid changed from root to a normal user (ptrace problem). I don't know if suse has this problem or not, can you try the backtrace generation with a simple kill -ABRT $(pidof bacula-dir) ? You should find the backtrace file somewhere with full information. Bye > To enable a smooth upgrade from prior suse rpms, I added the following > lines to the spec file: > > -- > %if %{suse} > # fix permissions for suse, as until now > # deamons always ran as root/root > if [ "$1" -gt 1 ] ; then > echo "fixing permissions for conmsg and log files because of update ..." > echo "update of user and group on suse systems..." > for f in %{working_dir}/*.conmsg %{working_dir}/log*; do > if [ -f $f ]; then > chown %{director_daemon_user}.%{daemon_group} $f -c > fi > done > fi > %endif > -- > > This fixes the permissions of the bacula log files and conmsg files, as > otherwise the bacula-dir cannot open the log and conmsg files. > > Of course, the rights of the backup devices have also to be checked, but > this has to be done manually in my view. > > best regards, > > Philipp -- Need professional help and support for Bacula ? Visit http://www.baculasystems.com |