Re: [Bacula-users] bacula-dir process failing to start. [SOLVED]

[Will M. <wmc...@gm...>]

On 31/01/06, Arthur Emerson III <em...@ms...> wrote:
> Will McDonald <wmc...@gm...>
> >
> > I've switched to 1.38.5-4 in the hopes of resolving the volume
> > management problems I've been having.
> [snip]
>
> > I built these RPMs on a CentOS 4 system with...
> >
> > rpmbuild --rebuild --define "build_centos4 1" --define "build_mysql 1"
> > --define "build_mysql4 1" /home/wmcdonald/bacula-1.38.5-4.src.rpm
> [snip]
>
> > [root@archive bacula]# /etc/bacula/bacula status
> > bacula-sd (pid 19307) is running...
> > bacula-fd (pid 19312) is running...
> > bacula-dir dead but pid file exists
>
> When I did the upgrade from 1.38.2 to 1.38.5-2 on my RHEL4.2
> system via rpmbuild, there were a few gotchas that stopped
> the director from starting.  One was that /etc/sysconfig/bacula
> needed these lines:
>
> DIR_USER=3D"bacula"
> DIR_GROUP=3D"disk"

I didn't have an /etc/sysconfig/bacula, created one with the contents
as specified and still experienced the same problem.

> The others were file permissions on /etc/bacula and it's contents,
> /var/bacula and it's contents, and I think the directory where
> those pid files above were stored.

Now I'm getting somewhere. I had noticed that something had changed
with /var/bacula but hadn't twigged. I have a broken link in
/var/log/bacula to /var/bacula/log.

> This is all due to the well-documented change of default behavior
> some place between 1.38.2 and 1.38.5, where the RPM's are installed
> running as non-root users by default instead of running as root
> in the past.

Apologies, I haven't been following the list particularly closely.
Again, I did notice the change to running as a less privileged user
but hadn't joined the dots. I kinda expected to see something obvious
in the strace if it was permissions/ownership and perhaps it's in
there and I just missed it.

> Don't have a clue if this is your problem or not, but figured
> that it's be a good place to start...

chown -R bacula:bacula /etc/bacula

... solved the problem. I can see from a clean install on a test
system the defaults are generally root:bacula and a few root:disk
though so I'll re-install and pay more attention to ownership. But I'm
over the hump and have the Director running.

Thanks for the pointers Arthur, really appreciated.

Will.