Re: [Bobs-devel] Install Question

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

O.K.
I think I solved it but here is where I made a mistake.  I think its because
I was confused slightly by the setup of the share.  On the setup screen for
a new share you are asked the name of the server and the share
identification.  I took this to mean 'a text description of the share'.  So
I typed in 'Admin Directory'.  However, I did not realize that this would be
used as the name of the directory created under
/backup/bobsdata/current/process/mounts/main.  where 'main' is my server
name.  The tip was that the directory was named 'Admin Directory' just like
I had typed in as a description.  When I ran the first script by hand as
described below it was choking on mounting that directory.  So I went in and
deleted that share, created it anew using just the word 'admin' as a
description and now it passes he configuration test with no errors (except
that a backup doesn't exist).

So I guess I'm dense or maybe a slight clarification is needed on that entry
box for people like me (non hackers ;) )

Bottom line is I think its working....I guess I'll know in 24 hours....
If you'd like me to test something else on this let me know.... [or just
quietly go away :) ]

Thanks

James

----- Original Message -----
From: "Arnaud CONCHON" <arn...@ar...>
To: <jbe...@mi...>
Sent: Tuesday, June 24, 2003 1:52 PM
Subject: TR: [Bobs-devel] Install Question

>
>
> > -----Message d'origine-----
> > De : bob...@li...
> > [mailto:bob...@li...]De la part de Joe Zacky
> > Envoyé : mardi 24 juin 2003 04:55
> > À : bob...@li...
> > Objet : Re: [Bobs-devel] Install Question
> >
> >
> > 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
> >
> >
> >
> >
> > -------------------------------------------------------
> > This SF.Net email is sponsored by: INetU
> > Attention Web Developers & Consultants: Become An INetU Hosting Partner.
> > Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
> > INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
> > _______________________________________________
> > Bobs-devel mailing list
> > Bob...@li...
> > https://lists.sourceforge.net/lists/listinfo/bobs-devel
> >
>
>

----------------------------------------------------------------------------
----

----------------------------------------------------------------------------
---------------
Ce message et toutes les pièces jointes sont confidentiels et établis à
l'attention exclusive de ses destinataires.
Toute utilisation de ce message non conforme à sa destination, toute
diffusion ou toute publication, totale ou partielle, est interdite, sauf
autorisation expresse.
Si vous recevez ce message par erreur, merci de le détruire et d'en avertir
immédiatement l'expéditeur.
Le Groupe C3D, ses filiales et ses partenaires déclinent toute
responsabilité au titre de ce message s'il a été altéré, déformé ou
falsifié.

This message and all attachments are confidential and intended solely for
the addressees.
Any use not in accord with its purpose, any dissemination or disclosure,
either whole or partial, is prohibited except formal approval.
If you receive this message in error, please delete it and immediately
notify the sender.
Neither C3D Group nor any of its subsidiaries or affiliates shall be liable
for the message if altered, changed or falsified.
----------------------------------------------------------------------------
---------------