--On Saturday, June 11, 2005 17:45:17 -0400 "Lengyel, Florian" <FLengyel AT 
gc.cuny DOT edu> wrote:

> Amanda version: amanda-2.4.4p3-1
> OS: CentOS
> Kernel: uname -a
> Linux amanda.grid.cuny.edu 2.6.9-5.0.3.ELsmp #1 SMP Sat Feb 19 19:38:02 CST
> 2005 i686 i686 i386 GNU/Linux
> 
> Trouble: amanda is set up on a tape server; there are two clients so far.
> One is running RH linux 7.3 but has the latest (2.4.4) amanda code built
> from 
> source...the other is using an older rpm under RH linux 9. The source build
> machine
> gives estimates for its DLEs, and the other seems to want to wait until
> grass to grows 
> under its mounting bracket, according to amstatus Daily, part of which
> reads:
> 
> m254.gc.cuny.edu:/home/m254/yzhu/                        getting estimate
> m254.gc.cuny.edu:/home/www                               getting estimate
> m254.gc.cuny.edu:sda1                                    getting estimate
> m254.gc.cuny.edu:sda2                                    getting estimate
> m254.gc.cuny.edu:sda3                                    getting estimate
> m254.gc.cuny.edu:sda5                                    getting estimate
> m254.gc.cuny.edu:sda7                                    getting estimate
> neptune-gw.gc.cuny.edu:hda1                  0     8390k estimate done
> neptune-gw.gc.cuny.edu:hda5                  0  6361840k estimate done
> neptune-gw.gc.cuny.edu:hda6                  0  1361030k estimate done
> neptune-gw.gc.cuny.edu:hda7                  0   163620k estimate done
> 
> I'm checking through the documentation...amcheck succeeds. Have I made one
> of the usual configuration oversights?

Try checking the debug files on m254.gc.cuny.edu (default is in /tmp/amanda)
and see if there is more information there.

One possibility is a firewall blocking the estimate response, since the
response usually occurs long after most firewall connection timeouts.
Look for 'no response' errors in the client debg files.

Just so your backups don't hang forever you might want to make sure your
etimout isn't set larger than necessary. Don't forget it is multiplied by
the number of DLEs on the host, so a setting of 1 hour on your m254 host
could result in a wait of up to 7 hours. You can use a negative number
it will be the per host timeout instead of per DLE.

Frank


--
Frank Smith                                                fsmith AT hoovers 
DOT com
Sr. Systems Administrator                                 Voice: 512-374-4673
Hoover's Online                                             Fax: 512-374-4501