Re: [Bobs-devel] Install Question

[Joe Z. <jz...@at...>]

James W. Beauchamp wrote:

> Hi all:
> I've installed BOBS on a Fresh RH 9.0 setup.  It's running but I'm not
> getting backups.  on the Current tab in the upper right corner I have
> "185718904.Preparation failed (mount)
> 130810167.Preparing backup
> 130810167.Preparation failed (mount)
>
> When I run the configuration check on the admin screen I get Pass for
> everything except this:
>
>       Attempting to write, read and delete a file on
>       /backup/bobsdata/current/process/mounts/main/Admin Directory FAIL
>       Write file test failed with these messages:
>
>       file already exists.
>
>
>
> (server name is 'main' and the directory mounted via NFS is 'Admin')
>
> The messges in the server logs show the successfull authentication and
>mount
> and unmount of the directory as BOBS does it so there isn't an error there.
> Do I have some kind of permission/user/owenership issue?
>
> Any help is appreciated.  I'm sure it's a stupid mistake on my part since
> this appears to work for most people out of the box.
>
> James
>
>
> James W. Beauchamp, P.E.
>  
>
That's a tough one. "Check Configuration" says it can mount and unmount 
okay, but the mount command during the backup fails - that's where the 
"Preparation failed (mount)" message comes from.

Let's start with the "file already exists." error in Check 
Configuration. The test is to write a file named "bobswritetest.out" and 
then delete it. See if that file exists on the 'main' computer, delete 
it if it does. Then on the bobs computer, with the Admin nfs share 
un-mounted, see if that file exists in 
/backup/bobsdata/current/process/mounts/main/Admin and delete it if it 
does. Then, copy the mount command from the Check Configuration page and 
manually run it as root. Then 'touch  
/backup/bobsdata/current/process/mounts/main/Admin/bobstest.out' and see 
if you get an error. If the write is successful, delete the file and 
unmount the share.

I notice your data directory is /backup/bobsdata instead of 
/var/bobsdata. I assume you used './configure --with-bobsdata=/backup'. 
That should be okay.

If you want to debug the actual backup, here's what you do (I hope I 
don't leave out something).
As root:

    * Comment out the check_loop line in /etc/crontab with a #.
    * Kill the cmdloop process: 'kill $(pidof -x cmdloop)'
    * Run the backup: /etc/cron.daily/backup.php
    * cd /backup/bobsdata/current/process/cmd. You should have several
      scripts sitting there waiting to run. They were created by backup.php.
    * Run each script in numerical order with ./script_name. For the
      bash scripts, if you want to see the commands being run you can
      run them as 'sh -xv script_name'. With patience and careful
      looking you should be able to spot the point of failure and see
      what the error message is.

Please let me know how it goes.

Joe