On Thu, 2005-03-24 at 00:18 +0100, Arno Lehmann wrote:
> Hi.
> 
> David Clymer wrote:
> 
> ...
> > When I try to run the director as the bacula user, it just fails to run
> > without displaying any error messages or a non-zero exit code.
> 
> How are the access rights for all the files the director needs?
> 
> > Am I doing something wrong?
> 
> Probably, but I don't know what :-)
> 
> If the file rights are ok, you are sure you actually run the newly built 
> version, and all the other obvious stuff you might try running the 
> director unter strace (or gdb, if you know how to use that).
> 
> strace usually gives me helpful hints without much knowledge about 
> program's internals.
> 
> Somewhat towards strace's output I usually find what operations did not 
> succeed.
> 

I had just circumvented this problem by installing the newly released
debian package for 1.36.2, which just worked. When another user emailed
with a similar problem, I went back and figured it out. So, for anyone
else who hates finding unconcluded threads in mailing list
archives...here's the solution:

It was a permissions problem after all. Files in the bacula working
directory (/usr/local/var/bacula/working, in my case) were owned by
root, and bacula (running as the bacula user) did not have permission to
write to them. 

I found this out by doing that which I should have done in the first
place: I ran bacula-dir using the debuging switch:

gorilla:/usr/local/src/bacula-1.36.2# bacula-dir -d99 -c 
/etc/bacula/bacula-dir.conf -u bacula -g bacula
bacula-dir: dird.c:131 Debug level = 99
bacula-dir: postgresql.c:166 pg_real_connect done
bacula-dir: postgresql.c:168 db_user=bacula db_name=bacula db_password=bacula
15-Apr 11:47 gorilla-dir: ERROR TERMINATION at message.c:262
Could not open console message file 
/usr/local//var/bacula/working/gorilla-dir.conmsg: ERR=Permission denied
15-Apr 11:47 gorilla-dir:  Error: message.c:684 fopen 
/usr/local//var/bacula/working/gorilla-dir.mail.gorilla-dir.135034776 failed: 
ERR=Permission denied
15-Apr 11:47 gorilla-dir:  Error: message.c:722 fopen 
/usr/local//var/bacula/working/log failed: ERR=Permission denied
15-Apr 11:47 gorilla-dir:  Error: message.c:722 fopen 
/usr/local//var/bacula/working/log failed: ERR=Permission denied
15-Apr 11:47 gorilla-dir:  Error: message.c:684 fopen 
/usr/local//var/bacula/working/gorilla-dir.mail.gorilla-dir.135034776 failed: 
ERR=Permission denied
15-Apr 11:47 gorilla-dir:  Error: message.c:684 fopen 
/usr/local//var/bacula/working/gorilla-dir.mail.gorilla-dir.135034776 failed: 
ERR=Permission denied
15-Apr 11:47 gorilla-dir:  Error: message.c:722 fopen 
/usr/local//var/bacula/working/log failed: ERR=Permission denied


Tada! My problem was revealed in all its all its glory. A quick change
of ownership did the trick:

chown -R bacula /usr/local/var/bacula

-davidc
--
Why should I fear death? If I am, death is not. If death is, I am not.
Why should I fear that which cannot exist when I do? -Epicurus,
philosopher (c. 341-270 BCE)



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to