From d23e99b1aed613e6a0d0a1699c559389f85358f2 Mon Sep 17 00:00:00 2001
From: Scott Barninger <scott@barninger.com>
Date: Sun, 3 Sep 2006 13:32:31 +0000
Subject: [PATCH] Add faq 8.

---
 docs/manual/rpm-faq.tex | 19 ++++++++++++++++++-
 1 file changed, 18 insertions(+), 1 deletion(-)

diff --git a/docs/manual/rpm-faq.tex b/docs/manual/rpm-faq.tex
index 91892399..8b75ead3 100644
--- a/docs/manual/rpm-faq.tex
+++ b/docs/manual/rpm-faq.tex
@@ -28,7 +28,9 @@ Packaging FAQ}
    \ilink{I'm building my own rpms because you don't publish for my platform.
     Can I get my packages released to sourceforge for other people to use?}{faq6} 
 \item 
-   \ilink{Is there an easier way than sorting out all these command line options?}{faq7} 
+   \ilink{Is there an easier way than sorting out all these command line options?}{faq7}
+\item 
+   \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}  
 \end{enumerate}
 
 \subsection*{Answers}
@@ -198,6 +200,21 @@ creation of debug rpm packages is:
    Look in the source archive for platforms/contrib-rpm/rpm_wizard.sh. This script will 
    allow you to specify build options using gnome dialog screens. It requires zenity.
 
+\item 
+   \label{faq8}
+   {\bf 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?} Beginning with 1.38 the rpm packages are configured to run the director and storage daemons as a non-root user. The file daemon runs as user root and group bacula, the storage daemon as user bacula and group disk, and the director as user bacula and group bacula. If you are upgrading you will need to change some file permissions for things to work. Execute the following commands as root:
+
+\footnotesize
+\begin{verbatim}
+        chown bacula.bacula /var/bacula/*
+	chown root.bacula /var/bacula/bacula-fd.9102.state
+	chown bacula.disk /var/bacula/bacula-sd.9103.state
+        
+\end{verbatim}
+\normalsize
+
+Further, if you are using File storage volumes rather than tapes those files will also need to have ownership set to user bacula and group bacula.
+
 
 \item {\bf Support for RHEL3/4, CentOS 3/4 and x86\_64}
    The examples below show
-- 
2.39.5