|
From: Jonathan S. <jhs...@sb...> - 2008-09-03 15:54:46
|
A few days ago John Descher responded to my previous message by
confirming that Bacula cannot use an address that is not an IP
address or domain name, and so cannot have a host or client
identified by a dynamic IP address. John: I appreciate your
response, but you answered my last question. The first one was the
show stopper, and I'm still wrestling with that.
To recap, after I followed your advice about using IP addresses I was
able to run the example job described in "A Brief Tutorial" (Chapter
9 of the Bacula manual), but it failed with the error:
(gedit:15893): WARNING **: Failed to create file
'/root/.gnome2/gedit/gedit-print-settings.J2LQGU': No such file or directory
I revisited this problem this morning to see if I could get any
farther on my own. I looked for a reference to /root/.gnome2/gedit
(or any reference to the string 'gedit') in Bacula's conf files, but
found none. For lack of a better approach, I created that directory
myself, with owner root, group bacula, both having "create and delete
files" permission. Then I started bconsole and tried to run the
sample job again.
The job immediately said "you have messages." When I displayed them
I got a large number of error messages (enough to overflow the
shell's buffer). All of them said:
03-Sep 10:18 Sonata-Ubuntu-dir JobId 6: Error: message.c:590
fopen /var/lib/bacula/log failed: ERR=Permission denied
After the last error message, Bacula tried to start the sample job, and said:
03-Sep 10:19 Sonata-Ubuntu-dir JobId 7: No prior Full backup
Job record found.
03-Sep 10:19 Sonata-Ubuntu-dir JobId 7: No prior or suitable
Full backup found in catalog. Doing FULL backup.
*
03-Sep 10:19 Sonata-Ubuntu-dir JobId 7: Start Backup JobId
7, Job=Client1.2008-09-03_10.19.03
03-Sep 10:19 Sonata-Ubuntu-dir JobId 7: Using Device "FileStorage"
After a delay of a minute or somewhat less, bconsole
terminated. When I tried to restart it I found that the director had
terminated too.
The messages about /var/lib/bacula/log particularly puzzle me. I was
running bconsole and all of the daemons through sudo (with root
privileges), so I don't see how bacula could be denied permission to
access anything.
I got inconsistent results trying to reproduce this problem. The
next time I tried it I didn't get the messages about
/var/lib/bacula/log, and bconsole and the directory didn't terminate,
but I didn't get a backup, either -- or any messages explaining why.
This all seems to murky to expect an immediate solution, but I hope
you can make another suggestion that will help me move forward. |