next up previous contents index
suivant: The Bootstrap File monter: Bacula RPM Packaging FAQ précédent: Build Options   Table des matières   Index

RPM Install Problems

In general the RPMs, once properly built should install correctly. However, when attempting to run the daemons, a number of problems can occur:
Wrong /var/bacula Permissions
By default, the Director and Storage daemon do not run with root permission. If the /var/bacula is owned by root, then it is possible that the Director and the Storage daemon will not be able to access this directory, which is used as the Working Directory. To fix this, the easiest thing to do is:
  chown bacula:bacula /var/bacula
Note: as of 1.38.8 /var/bacula is installed root:bacula with permissions 770.
The Storage daemon cannot Access the Tape drive
This can happen in some older RPM releases where the Storage daemon ran under userid bacula, group bacula. There are two ways of fixing this: the best is to modify the /etc/init.d/bacula-sd file so that it starts the Storage daemon with group "disk". The second way to fix the problem is to change the permissions of your tape drive (usually /dev/nst0) so that Bacula can access it. You will probably need to change the permissions of the SCSI control device as well, which is usually /dev/sg0. The exact names depend on your configuration, please see the Tape Testing chapter for more information on devices.


next up previous contents index
suivant: The Bootstrap File monter: Bacula RPM Packaging FAQ précédent: Build Options   Table des matières   Index
Kern Sibbald 2007-11-03