4 \chapter{Bacula RPM Packaging FAQ}
6 \index[general]{FAQ!Bacula\textsuperscript{\textregistered} - RPM Packaging }
7 \index[general]{Bacula\textsuperscript{\textregistered} - RPM Packaging FAQ }
11 \ilink{How do I build Bacula for platform xxx?}{faq1}
13 \ilink{How do I control which database support gets built?}{faq2}
16 \ilink{What other defines are used?}{faq3}
18 \ilink{I'm getting errors about not having permission when I try to build the
19 packages. Do I need to be root?}{faq4}
21 \ilink{I'm building my own rpms but on all platforms and compiles I get an
22 unresolved dependency for something called
23 /usr/afsws/bin/pagsh.}{faq5}
25 \ilink{I'm building my own rpms because you don't publish for my platform.
26 Can I get my packages released to sourceforge for other people to use?}{faq6}
28 \ilink{Is there an easier way than sorting out all these command line options?}{faq7}
30 \ilink{I just upgraded from 1.36.x to 1.38.x and now my director daemon won't start. It appears to start but dies silently and I get a "connection refused" error when starting the console. What is wrong?}{faq8}
32 \ilink{There are a lot of rpm packages. Which packages do I need for what?}{faq9}
36 \index[general]{Answers }
41 {\bf How do I build Bacula for platform xxx?}
42 The bacula spec file contains defines to build for several platforms:
43 Red Hat 7.x (rh7), Red Hat 8.0 (rh8), Red Hat 9 (rh9), Fedora Core (fc1,
44 fc3, fc4, fc5, fc6, fc7, fc8), Whitebox Enterprise Linux 3.0 (wb3), Red Hat Enterprise Linux
45 (rhel3, rhel4, rhel5), Mandrake 10.x (mdk), Mandriva 2006.x (mdv) CentOS (centos3, centos4, centos5)
46 Scientific Linux (sl3, sl4, sl5) and SuSE (su9, su10, su102, su103, su110). The package build is controlled by a mandatory define set at the beginning of the file. These defines basically just control the dependency information that gets coded into the finished rpm package as well
47 as any special configure options required. The platform define may be edited
48 in the spec file directly (by default all defines are set to 0 or "not set").
49 For example, to build the Red Hat 7.x package find the line in the spec file
68 Alternately you may pass the define on the command line when calling rpmbuild:
73 rpmbuild -ba --define "build_rh7 1" bacula.spec
74 rpmbuild --rebuild --define build_rh7 1" bacula-x.x.x-x.src.rpm
81 {\bf How do I control which database support gets built?}
82 Another mandatory build define controls which database support is compiled,
83 one of build\_sqlite, build\_mysql or build\_postgresql. To get the MySQL
84 package and support either set the
110 in the spec file directly or pass it to rpmbuild on the command line:
114 rpmbuild -ba --define "build_rh7 1" --define "build_mysql 1" bacula.spec
115 rpmbuild -ba --define "build_rh7 1" --define "build_mysql4 1" bacula.spec
116 rpmbuild -ba --define "build_rh7 1" --define "build_mysql5 1" bacula.spec
123 {\bf What other defines are used?}
124 Three other building defines of note are the depkgs\_version, docs\_version and
125 \_rescuever identifiers. These two defines are set with each release and must
126 match the version of those sources that are being used to build the packages.
127 You would not ordinarily need to edit these. See also the Build Options section
128 below for other build time options that can be passed on the command line.
131 {\bf I'm getting errors about not having permission when I try to build the
132 packages. Do I need to be root?}
133 No, you do not need to be root and, in fact, it is better practice to
134 build rpm packages as a non-root user. Bacula packages are designed to
135 be built by a regular user but you must make a few changes on your
136 system to do this. If you are building on your own system then the
137 simplest method is to add write permissions for all to the build
138 directory (/usr/src/redhat/, /usr/src/RPM or /usr/src/packages).
139 To accomplish this, execute the following command as root:
143 chmod -R 777 /usr/src/redhat
144 chmod -R 777 /usr/src/RPM
145 chmod -R 777 /usr/src/packages
150 If you are working on a shared system where you can not use the method
151 above then you need to recreate the appropriate above directory tree with all
152 of its subdirectories inside your home directory. Then create a file named
156 in your home directory (or edit the file if it already exists)
157 and add the following line:
161 %_topdir /home/myuser/redhat
167 Another handy directive for the .rpmmacros file if you wish to suppress the
168 creation of debug rpm packages is:
172 %debug_package %{nil}
180 {\bf I'm building my own rpms but on all platforms and compiles I get an
181 unresolved dependency for something called /usr/afsws/bin/pagsh.} This
182 is a shell from the OpenAFS (Andrew File System). If you are seeing
183 this then you chose to include the docs/examples directory in your
184 package. One of the example scripts in this directory is a pagsh
185 script. Rpmbuild, when scanning for dependencies, looks at the shebang
186 line of all packaged scripts in addition to checking shared libraries.
187 To avoid this do not package the examples directory. If you are seeing this
188 problem you are building a very old bacula package as the examples have been
189 removed from the doc packaging.
193 {\bf I'm building my own rpms because you don't publish for my platform.
194 Can I get my packages released to sourceforge for other people to use?} Yes,
195 contributions from users are accepted and appreciated. Please examine the
196 directory platforms/contrib-rpm in the source code for further information.
200 {\bf Is there an easier way than sorting out all these command line options?} Yes,
201 there is a gui wizard shell script which you can use to rebuild the src rpm package.
202 Look in the source archive for platforms/contrib-rpm/rpm\_wizard.sh. This script will
203 allow you to specify build options using GNOME dialog screens. It requires zenity.
207 {\bf I just upgraded from 1.36.x to 1.38.x and now my director daemon
208 won't start. It appears to start but dies silently and I get a "connection
209 refused" error when starting the console. What is wrong?} Beginning with
210 1.38 the rpm packages are configured to run the director and storage
211 daemons as a non-root user. The file daemon runs as user root and group
212 bacula, the storage daemon as user bacula and group disk, and the director
213 as user bacula and group bacula. If you are upgrading you will need to
214 change some file permissions for things to work. Execute the following
219 chown bacula.bacula /var/bacula/*
220 chown root.bacula /var/bacula/bacula-fd.9102.state
221 chown bacula.disk /var/bacula/bacula-sd.9103.state
226 Further, if you are using File storage volumes rather than tapes those
227 files will also need to have ownership set to user bacula and group bacula.
231 {\bf There are a lot of rpm packages. Which packages do I need for
232 what?} For a bacula server you need to select the packsge based upon your
233 preferred catalog database: one of bacula-mysql, bacula-postgresql or
234 bacula-sqlite. If your system does not provide an mtx package you also
235 need bacula-mtx to satisfy that dependancy. For a client machine you need
236 only install bacula-client. Optionally, for either server or client
237 machines, you may install a graphical console bacula-gconsole and/or
238 bacula-wxconsole. The Bacula Administration Tool is installed with the
239 bacula-bat package. One last package, bacula-updatedb is required only when
240 upgrading a server more than one database revision level.
244 \item {\bf Support for RHEL3/4/5, CentOS 3/4/5, Scientific Linux 3/4/5 and x86\_64}
245 The examples below show
246 explicit build support for RHEL4 and CentOS 4. Build support
247 for x86\_64 has also been added.
252 Build with one of these 3 commands:
255 --define "build_rhel4 1" \
256 --define "build_sqlite 1" \
257 bacula-1.38.3-1.src.rpm
260 --define "build_rhel4 1" \
261 --define "build_postgresql 1" \
262 bacula-1.38.3-1.src.rpm
265 --define "build_rhel4 1" \
266 --define "build_mysql4 1" \
267 bacula-1.38.3-1.src.rpm
269 For CentOS substitute '--define "build_centos4 1"' in place of rhel4.
270 For Scientific Linux substitute '--define "build_sl4 1"' in place of rhel4.
272 For 64 bit support add '--define "build_x86_64 1"'
276 \section{Build Options}
277 \index[general]{Build Options}
278 The spec file currently supports building on the following platforms:
282 --define "build_rh7 1"
283 --define "build_rh8 1"
284 --define "build_rh9 1"
287 --define "build_fc1 1"
288 --define "build_fc3 1"
289 --define "build_fc4 1"
290 --define "build_fc5 1"
291 --define "build_fc6 1"
292 --define "build_fc7 1"
293 --define "build_fc8 1"
294 --define "build_fc9 1"
296 Whitebox Enterprise build
297 --define "build_wb3 1"
299 Red Hat Enterprise builds
300 --define "build_rhel3 1"
301 --define "build_rhel4 1"
302 --define "build_rhel5 1"
305 --define "build_centos3 1"
306 --define "build_centos4 1"
307 --define "build_centos5 1"
309 Scientific Linux build
310 --define "build_sl3 1"
311 --define "build_sl4 1"
312 --define "build_sl5 1"
315 --define "build_su9 1"
316 --define "build_su10 1"
317 --define "build_su102 1"
318 --define "build_su103 1"
319 --define "build_su110 1"
320 --define "build_su111 1"
323 --define "build_mdk 1"
326 --define "build_mdv 1"
329 for mysql 3.23.x support define this
330 --define "build_mysql 1"
331 if using mysql 4.x define this,
332 currently: Mandrake 10.x, Mandriva 2006.0, SuSE 9.x & 10.0, FC4 & RHEL4
333 --define "build_mysql4 1"
334 if using mysql 5.x define this,
335 currently: SuSE 10.1 & FC5
336 --define "build_mysql5 1"
339 --define "build_postgresql 1"
342 --define "build_sqlite 1"
344 Build the client rpm only in place of one of the above database full builds:
345 --define "build_client_only 1"
348 --define "build_x86_64 1"
350 Supress build of bgnome-console:
351 --define "nobuild_gconsole 1"
353 Build the WXWindows console:
354 requires wxGTK >= 2.6
355 --define "build_wxconsole 1"
357 Build the Bacula Administration Tool:
359 --define "build_bat 1"
361 Build python scripting support:
362 --define "build_python 1"
364 Modify the Packager tag for third party packages:
365 --define "contrib_packager Your Name <youremail@site.org>"
367 Install most files to /opt/bacula directory:
368 --define "single_dir_install 1"
370 Supress building the rescue files:
371 --define "nobuild_rescue 1"
376 \section{RPM Install Problems}
377 \index[general]{RPM Install Problems}
378 In general the RPMs, once properly built should install correctly.
379 However, when attempting to run the daemons, a number of problems
382 \item [Wrong /var/bacula Permissions]
383 By default, the Director and Storage daemon do not run with
384 root permission. If the /var/bacula is owned by root, then it
385 is possible that the Director and the Storage daemon will not
386 be able to access this directory, which is used as the Working
387 Directory. To fix this, the easiest thing to do is:
389 chown bacula:bacula /var/bacula
391 Note: as of 1.38.8 /var/bacula is installed root:bacula with
393 \item [The Storage daemon cannot Access the Tape drive]
394 This can happen in some older RPM releases where the Storage
395 daemon ran under userid bacula, group bacula. There are two
396 ways of fixing this: the best is to modify the /etc/init.d/bacula-sd
397 file so that it starts the Storage daemon with group "disk".
398 The second way to fix the problem is to change the permissions
399 of your tape drive (usually /dev/nst0) so that Bacula can access it.
400 You will probably need to change the permissions of the SCSI control
401 device as well, which is usually /dev/sg0. The exact names depend
402 on your configuration, please see the Tape Testing chapter for
403 more information on devices.