Estimate timeout

week) are checked sequentially. We seem to be exceeding a timeout limit. etimeout is for size estimates - so I don't think it applies. We have switched to "server estimate" for zfs-dump. Is there a per client amcheck estimate timeout, not based on number of client DLEs ? Amand

Re: AW: Estimate timeout

er Wilhelm" <[EMAIL PROTECTED]> wrote: > try different values for etime. > > Regards W.Trompler > > -Ursprüngliche Nachricht- > Von: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Im > Auftrag von Yogesh Hasabnis > Gesendet: Mittwoch, 07. Februar 2007 06:48 &

Estimate timeout

stname and the volume names): " START driver date 20070206 DISK planner DISK planner START planner date 20070206 INFO planner Adding new disk :. INFO planner Adding new disk :. START taper datestamp 20070206 label FULLBACK1 tape 0 FAIL planner 20070206 0 [Estimate timeout from ] FAIL pla

Re: estimate timeout and dump failure

On Friday 06 October 2006 10:32, Mike Galvez wrote: Mike, I think this is a known bug, you need to update to one of the 2.5.1p1 versions. It bit lots of us. See I ran the 20061004 snapshot last night, and it worked just fine. >I am using version

estimate timeout and dump failure

Hi, I am using version 2.5.0p2. on my dump host. One of my clients (same version) has a filesystem that consistently fails the estimate and dump phases. The same host has two other filesystems (smaller) that complete without problem. The amandad and selfcheck debug from this host shows no ind

Re: Estimate timeout from localhost / driver: WARNING: got empty schedule from planner

Joshua Baker-LePain wrote: > On Tue, 25 Apr 2006 at 9:22am, Thomas Grieder wrote > >> Since a few days I get this two error messages: >> >> Estimate timeout from localhost >> driver: WARNING: got empty schedule from planner > > 1) Using localhost in the diskl

Re: Estimate timeout from localhost / driver: WARNING: got empty schedule from planner

On Tue, 25 Apr 2006 at 9:22am, Thomas Grieder wrote Since a few days I get this two error messages: Estimate timeout from localhost driver: WARNING: got empty schedule from planner 1) Using localhost in the disklist is generally frowned upon. It's not a unique name, and will likely

Estimate timeout from localhost / driver: WARNING: got empty schedule from planner

Hi Since a few days I get this two error messages: Estimate timeout from localhost driver: WARNING: got empty schedule from planner I could not find any hints while searching google. Any ideas? Below amcheck an amdump mails: amcheck: Amanda Tape Server Host Check

Re: BUG (was: Re: Handitarded....odd (partial) estimate timeout errors.)

--On January 5, 2006 4:49:53 PM +0100 Paul Bijnens <[EMAIL PROTECTED]> wrote: Michael Loftis wrote: Paul asked for the logs, it seems like there's an amanda bug. The units Yes, indeed, there is a bug in Amanda! You have 236 DLE's for that host, and from my reading of the code the REQue

BUG (was: Re: Handitarded....odd (partial) estimate timeout errors.)

Michael Loftis wrote: Paul asked for the logs, it seems like there's an amanda bug. The units Yes, indeed, there is a bug in Amanda! You have 236 DLE's for that host, and from my reading of the code the REQuest UDP packet is limited to 32K instead of 64K (see planner.c lines 1377-1383) (Ne

Re: Handitarded....odd (partial) estimate timeout errors.

--On January 4, 2006 7:20:50 PM -0500 Jon LaBadie <[EMAIL PROTECTED]> wrote: Asking questions about things I know nothing ... :) Are you using iptables? If so, have you installed and configured the ??conntrack?? module? Paul asked for the logs, it seems like there's an amanda bug. The uni

Re: Handitarded....odd (partial) estimate timeout errors.

On Wed, Jan 04, 2006 at 03:38:56PM -0700, Michael Loftis wrote: > > > --On January 4, 2006 4:30:53 PM -0500 Jon LaBadie <[EMAIL PROTECTED]> wrote: > > > >You can find comments on the problem here: > > > > http://tinyurl.com/ca7pv > > > OK hmm something REALLY odd is happening. For t

Re: Handitarded....odd (partial) estimate timeout errors.

--On January 4, 2006 4:30:53 PM -0500 Jon LaBadie <[EMAIL PROTECTED]> wrote: You can find comments on the problem here: http://tinyurl.com/ca7pv OK hmm something REALLY odd is happening. For the DLEs that failed there are multiple sendsize requests... one in the main/first

Re: Handitarded....odd (partial) estimate timeout errors.

On Wed, Jan 04, 2006 at 02:01:36PM -0700, Michael Loftis wrote: > I added about half a dozen or so DLEs (splitting an existing one) and since > that time I get estimate timeout errors for some other DLEs on this host > (daily run snippet attached) ... i suspect I'm hitting a UD

Handitarded....odd (partial) estimate timeout errors.

I added about half a dozen or so DLEs (splitting an existing one) and since that time I get estimate timeout errors for some other DLEs on this host (daily run snippet attached) ... i suspect I'm hitting a UDP packet limit maybe, but...I'm really drawing a blank. I've turned up

AW: AW: AW: AW: AW: AW: AW: AW: Estimate timeout from server

: Sebastian Kösters Cc: amanda-users@amanda.org Betreff: Re: AW: AW: AW: AW: AW: AW: AW: Estimate timeout from server Sebastian Kösters wrote: > Hi! > > Thats all in sendsize: > > sendsize: debug 1 pid 5132 ruid 33 euid 33: start at Fri Nov 4 02:30:02 > 2005 > sendsize: version

Re: AW: AW: AW: AW: AW: AW: AW: Estimate timeout from server

Sebastian Kösters wrote: Hi! Thats all in sendsize: sendsize: debug 1 pid 5132 ruid 33 euid 33: start at Fri Nov 4 02:30:02 2005 sendsize: version 2.4.3 sendsize[5132]: time 0.007: waiting for any estimate child sendsize[5134]: time 0.007: calculating for amname '/pst', dirname '/pst', spindle

AW: AW: AW: AW: AW: AW: AW: AW: Estimate timeout from server

amanda-users@amanda.org Betreff: Re: AW: AW: AW: AW: AW: AW: AW: Estimate timeout from server Sebastian Kösters wrote: > Thats all in sendsize: > > sendsize: debug 1 pid 5132 ruid 33 euid 33: start at Fri Nov 4 02:30:02 > 2005 > sendsize: version 2.4.3 > sendsize[5132]: time 0.007:

AW: AW: AW: AW: AW: AW: AW: AW: Estimate timeout from server

: AW: AW: AW: AW: AW: AW: Estimate timeout from server Sebastian Kösters wrote: > Thats all in sendsize: > > sendsize: debug 1 pid 5132 ruid 33 euid 33: start at Fri Nov 4 02:30:02 > 2005 > sendsize: version 2.4.3 > sendsize[5132]: time 0.007: waiting for any estimate child >

Re: AW: AW: AW: AW: AW: AW: AW: Estimate timeout from server

Sebastian Kösters wrote: Thats all in sendsize: sendsize: debug 1 pid 5132 ruid 33 euid 33: start at Fri Nov 4 02:30:02 2005 sendsize: version 2.4.3 sendsize[5132]: time 0.007: waiting for any estimate child sendsize[5134]: time 0.007: calculating for amname '/pst', dirname '/pst', spindle -1 s

AW: AW: AW: AW: AW: AW: AW: Estimate timeout from server

PROTECTED] Gesendet: Donnerstag, 3. November 2005 15:20 An: Sebastian Kösters Cc: amanda-users@amanda.org Betreff: Re: AW: AW: AW: AW: AW: AW: Estimate timeout from server Sebastian Kösters wrote: > I found this in /tmp/amanda on the client [...] > sendsize[25487]: time 1519.255: . Did

Re: AW: AW: AW: AW: AW: AW: Estimate timeout from server

Sebastian Kösters wrote: I found this in /tmp/amanda on the client [...] sendsize[25487]: time 1519.255: . Did you cut something here? That would have been what was interesting. sendsize[25487]: estimate time for /pst level 0: 1519.252 Alex -- Alexander Jolk * BUF Compagnie * [EM

Re: AW: AW: AW: AW: AW: AW: AW: Estimate timeout from server

Sebastian Kösters wrote: I tried it by hand with /opt and it worked. -rw-r--r--1 root root 256 3. Nov 14:52 pst_opt_0.new tar (GNU tar) 1.13.25 i dont know why it has a Problem with /pst?! Ok its big (80GB) but not to big i think. You have failed to understand that we don

AW: AW: AW: AW: AW: AW: AW: Estimate timeout from server

PROTECTED] Gesendet: Donnerstag, 3. November 2005 14:46 An: Sebastian Kösters Betreff: Re: AW: AW: AW: AW: AW: AW: Estimate timeout from server Sebastian Kösters wrote: > I found this in /tmp/amanda on the client > ... > sendsize[25487]: argument list: /bin/tar --create --file

Re: AW: AW: AW: AW: AW: Estimate timeout from server

On Thu, Nov 03, 2005 at 02:38:04PM +0100, Sebastian Kösters enlightened us: > I found this in /tmp/amanda on the client > > sendsize: debug 1 pid 25485 ruid 33 euid 33: start at Thu Nov 3 14:00:25 > 2005 > sendsize: version 2.4.3 > sendsize[25487]: time 0.002: calculating for amname '/pst', dirna

AW: AW: AW: AW: AW: AW: Estimate timeout from server

der Jolk' Cc: amanda-users@amanda.org Betreff: AW: AW: AW: AW: AW: AW: Estimate timeout from server You are right. When i try it by hand nothing happens. It runs and runs and runs and the file stays at 0kb. I found no error messages. I also changed the persmissions of the amanda files /

AW: AW: AW: AW: AW: AW: Estimate timeout from server

] Im Auftrag von Alexander Jolk Gesendet: Donnerstag, 3. November 2005 14:21 An: Sebastian Kösters Cc: amanda-users@amanda.org Betreff: Re: AW: AW: AW: AW: AW: Estimate timeout from server Sebastian Kösters wrote: >>On the client amanda starts the following command: >> >>/bin/tar --

Re: AW: AW: AW: AW: AW: Estimate timeout from server

Sebastian Kösters wrote: On the client amanda starts the following command: /bin/tar --create --file /dev/null --directory /pst --one-file-system --listed-incremental /var/lib/amanda/gnutar-lists/pst_pst_0.new When run it by hand i get this error (translated from german to english) /bin/tar:

AW: AW: AW: AW: AW: Estimate timeout from server

. November 2005 09:58 An: Sebastian Kösters Cc: amanda-users@amanda.org Betreff: Re: AW: AW: AW: AW: Estimate timeout from server Sebastian Kösters wrote: > It does not work. Which means? Do you get an error message? Please cite it. What do the relevant log files say? You showed us yesterday t

Re: Estimate Timeout Issue - Dump runs fine

OK thanks - I have increased the etimeout to 2400 seconds and also changed the udp timeout within checkpoint to also be 2400 seconds so i'll see how the run goes tonight everything was fine today - no estimate timeout thanks for the pointer

Re: AW: AW: AW: AW: Estimate timeout from server

Sebastian Kösters wrote: It does not work. Which means? Do you get an error message? Please cite it. What do the relevant log files say? You showed us yesterday that the estimate phase took almost an hour on this machine, have you waited for that time? On the client amanda starts the f

AW: AW: AW: AW: Estimate timeout from server

?! -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Stefan G. Weichinger Gesendet: Mittwoch, 2. November 2005 22:01 An: amanda-users@amanda.org Betreff: Re: AW: AW: AW: Estimate timeout from server Sebastian Kösters wrote: > My report looks like t

AW: AW: AW: AW: Estimate timeout from server

: AW: AW: AW: Estimate timeout from server Sebastian Kösters wrote: > My report looks like this: > > NOTES: > planner: tapecycle (1) <= runspercycle (10) Please get that sorted out, I assume that this is not what you want, although it has nothing to do with your timeouts. > >

Re: AW: AW: AW: Estimate timeout from server

Sebastian Kösters wrote: > My report looks like this: > > NOTES: > planner: tapecycle (1) <= runspercycle (10) Please get that sorted out, I assume that this is not what you want, although it has nothing to do with your timeouts. > > Thats all. I tested with a seperate config. Have you incre

Re: Estimate Timeout Issue - Dump runs fine

Yep. So you can just increase etimeout and/or figure out why "/sbin/dump 1Ssf 1048576 - /dev/sda5" is taking so long. OK thanks - I have increased the etimeout to 2400 seconds and also changed the udp timeout within checkpoint to also be 2400 seconds so i'll see how the run goes tonight t

Re: Estimate Timeout Issue - Dump runs fine

On Wed, 2 Nov 2005 at 2:31pm, Tom Brown wrote Look in /tmp/amanda/sendsize*debug and/or amandad*debug to see how long the estimate is actually taking. Also, what do your iptables rules look like on the server? thanks - iptables are not being used, local firewall is off one of my amanda.de

Re: Estimate Timeout Issue - Dump runs fine

Look in /tmp/amanda/sendsize*debug and/or amandad*debug to see how long the estimate is actually taking. Also, what do your iptables rules look like on the server? thanks - iptables are not being used, local firewall is off sendsize degug is below and looks OK # more /tmp/amanda/sendsize.

Re: Estimate Timeout Issue - Dump runs fine

anner: ERROR Estimate timeout from "servername" Thing is though the actual dump of this filesystem runs fine - I have increased my eTimeout to 20mins but this still occurs - Any ideas on this one? Look in /tmp/amanda/sendsize*debug and/or amandad*debug to see how long the estimate is

AW: AW: AW: Estimate timeout from server

My report looks like this: These dumps were to tape DailySet150. The next tape Amanda expects to use is: DailySet150. FAILURE AND STRANGE DUMP SUMMARY: pst/pst lev 0 FAILED [Estimate timeout from pst] STATISTICS: Total Full Daily

Re: AW: AW: Estimate timeout from server

amandad: time 3438.570: dgram_recv: timeout after 10 seconds amandad: time 3438.570: waiting for ack: timeout, retrying Sounds like a simple estimate timeout to me, 3500s for one partition is quite long. Bump up your etimeout in amanda.conf to something like 5000s and see whether that works

AW: AW: Estimate timeout from server

20 KB sendsize[29469]: time 3428.562: waiting for /bin/tar "/pst" child sendsize[29469]: time 3428.562: after /bin/tar "/pst" wait sendsize[29469]: time 3428.562: done with amname '/pst', dirname '/pst', spindle -1 sendsize[29467]: time 3428.563: child 29469

Re: AW: Estimate timeout from server

Sebastian Kösters wrote: Which Log-Files from which Machine do you need to help me finding the error? The output of `amcheck ' on the amanda server. If there's one particular client that fails, the files from that client's /tmp/amanda/ corresponding to above amcheck, or double confirmation th

AW: Estimate timeout from server

Can no one help? -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Sebastian Kösters Gesendet: Mittwoch, 2. November 2005 07:50 An: amanda-users@amanda.org Betreff: Estimate timeout from server Hi, i get this error (Estimate timeout from server

Estimate Timeout Issue - Dump runs fine

on is around 900gig in size although only a few hundred meg are currently used. When the estimate runs it returns FAILURE AND STRANGE DUMP SUMMARY: planner: ERROR Estimate timeout from "servername" Thing is though the actual dump of this filesystem runs fine - I have increased my eTi

Estimate timeout from server

Hi, i get this error (Estimate timeout from server) on an new installed System (RedHat 9). I installed amanda like on every other Machine but it will not work (no reboot or something like this during the Backup). Which Log-Files from which Machine do you need to help me finding the error

Re: estimate timeout

On Monday 10 October 2005 03:20, Shai Ayal wrote: >Hi all, > >I have searched the archives but none of the emails with similar > subjects helped me. > >I have a FC2 amanda 2.4.4 server with 2 linux clients. The server is > using vtapes for daily backups. It all ran very nicely for many months > unt

Re: estimate timeout

On Mon, 10 Oct 2005 at 9:20am, Shai Ayal wrote I have a FC2 amanda 2.4.4 server with 2 linux clients. The server is using vtapes for daily backups. It all ran very nicely for many months until we ran out of disk space in the server. After a few days of bad backups due to full disk, we installe

estimate timeout

Hi all, I have searched the archives but none of the emails with similar subjects helped me. I have a FC2 amanda 2.4.4 server with 2 linux clients. The server is using vtapes for daily backups. It all ran very nicely for many months until we ran out of disk space in the server. After a few d

Re: Estimate timeout

>In amandad.debug on the client I get: >... >amandad: time 2951.811: sending REP packet: > >Amanda 2.4 REP HANDLE 00F-80930508 SEQ 1126652514 >OPTIONS features=feff9ffe7f; >ar0s1a 0 SIZE 30567356 >ar0s1a 1 SIZE 17959269 > > >amandad: time 2961.819: dgram_recv: timeout after 10 seconds >

Estimate timeout

name (both the machines real hostname and the one in amanda), but still I get this in my daily report: dc104 ar0s1a lev 0 FAILED [Estimate timeout from dc104] I've got 115 entries in my disklist (on some 60 hosts) and this is the only one I can't get to work. There doesn't s

RE: Estimate timeout

Well, the tar command by itself is still running, but the backup with the new version of tar is complete, so my "estimate timeout" problem is fixed with an updated tar executable. Thank you all. -Original Message- From: Joshua Baker-LePain [mailto:[EMAIL PROTECTED] Sent: Tuesd

Re: Estimate timeout

On Tue, 30 Aug 2005 at 1:19pm, Jon LaBadie wrote > On Tue, Aug 30, 2005 at 11:01:52AM -0400, LaValley, Brian E wrote: > > Can someone please help me get to the bottom of this issue? I have Amanda > > 2.4.4p2 on a Fedora Core 3 machine which is the tape server. It has no > > trouble backing up it

Re: Estimate timeout

On Tue, Aug 30, 2005 at 11:01:52AM -0400, LaValley, Brian E wrote: > Can someone please help me get to the bottom of this issue? I have Amanda > 2.4.4p2 on a Fedora Core 3 machine which is the tape server. It has no > trouble backing up itself and other Linux machines. The trouble comes with > a

RE: Estimate timeout

Ok, I'll try a new version of tar after my test of the tar command on its own. -Original Message- From: Joshua Baker-LePain [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 30, 2005 11:33 AM To: LaValley, Brian E Cc: Amanda (E-mail) Subject: RE: Estimate timeout On Tue, 30 Aug 2005

RE: Estimate timeout

On Tue, 30 Aug 2005 at 11:38am, LaValley, Brian E wrote > I'll have to get back to you on running the command by itself. My tar > version is: tar (GNU tar) 1.13 Bad, bad, bad. http://www.amanda.org/docs/faq.html#id2554919 -- Joshua Baker-LePain Department of Biomedical Engineering Duke Univers

RE: Estimate timeout

I'll have to get back to you on running the command by itself. My tar version is: tar (GNU tar) 1.13 -Original Message- From: Joshua Baker-LePain [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 30, 2005 11:21 AM To: LaValley, Brian E Cc: Amanda (E-mail) Subject: Re: Estimate timeout

Re: Estimate timeout

On Tue, 30 Aug 2005 at 11:01am, LaValley, Brian E wrote > sendsize: debug 1 pid 12359 ruid 548 euid 548: start at Mon Aug 29 18:00:02 > 2005 > sendsize: version 2.4.4p2 > sendsize[12359]: time 0.034: waiting for any estimate child: 1 running > sendsize[12361]: time 0.035: calculating for amname >

RE: Estimate timeout

There is no firewall. -Original Message- From: Guy Dallaire [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 30, 2005 11:02 AM To: LaValley, Brian E Cc: Amanda (E-mail) Subject: Re: Estimate timeout 2005/8/30, LaValley, Brian E <[EMAIL PROTECTED]>: > Can someone please help me g

Re: Estimate timeout

2005/8/30, LaValley, Brian E <[EMAIL PROTECTED]>: > Can someone please help me get to the bottom of this issue? I have Amanda > 2.4.4p2 on a Fedora Core 3 machine which is the tape server. It has no > trouble backing up itself and other Linux machines. The trouble comes with > a Sun Solaris 8 cl

Estimate timeout

e to: /opt/amanda/libexec/chg-scsi -slot current changer: got exit: 0 str: 6 /dev/nst0 taper: slot 6: date Xlabel DailySet1-A06 (new tape) taper: read label `DailySet1-A06' date `X' taper: wrote label `DailySet1-A06' date `20050829' planner: time 10735.451: got result fo

Estimate timeout issue

I have an AMANDA client machine with Solaris 8 and logical volumes on a disk. The AMANDA server's config has etimeout=29600 so it waits 59202 seconds and fails. planner: time 59202.106: error result for host coneng disk /dev/vx/dsk/opt: Estimate timeout from coneng planner: time 59202.108:

Re: Estimate timeout

On Sat, Jul 23, 2005 at 09:56:30AM -0400, LaValley, Brian E wrote: > My dumps aren't completing. One fishy thing I am seeing in the logs is two > of the same partition, "/home 1" and "/home 0" > What does this mean? > > As part of its planning amanda may do an estimate of the size of a potential d

Estimate timeout

My dumps aren't completing. One fishy thing I am seeing in the logs is two of the same partition, "/home 1" and "/home 0" What does this mean? Amanda 2.4 REQ HANDLE 000-B0F0E609 SEQ 1122119536 SECURITY USER backup SERVICE sendsize OPTIONS features=feff9ffe0f;maxdumps=1;hostname=blavalley-l; GN

Re: Dumps Fail - Estimate Timeout errors

Tom Brown wrote: actually digging around in /tmp/amanda i have come accross files with amandad.DATE.debug and a few of them apper to end like this amandad: time 111.846: dgram_recv: timeout after 10 seconds amandad: time 111.846: waiting for ack: timeout, retrying amandad: time 121.846: dgram_rec

Re: Dumps Fail - Estimate Timeout errors

Have a look on that client in /tmp/amanda, look for the files sendsize.DATETIME.debug and see how long the estimate did take. The first line of the file is the start time and the last line is the finish time. How long did it really take? You many have to change the "etimeout" parameter in amanda.

Re: Dumps Fail - Estimate Timeout errors

Have a look on that client in /tmp/amanda, look for the files sendsize.DATETIME.debug and see how long the estimate did take. The first line of the file is the start time and the last line is the finish time. How long did it really take? You many have to change the "etimeout" parameter in amanda.

Re: Dumps Fail - Estimate Timeout errors

Tom Brown wrote: Failure errors are hostname/dev/rd/c0d0p3 lev 0 FAILED [Estimate timeout from hostname] ... Does anyone know how to debug these timeout type issues as i have been using amanda for about 3 years now and have not encountered this before. Have a look on that client in /tmp

Dumps Fail - Estimate Timeout errors

ago worked last night without changes, and i can't figure out why. All clients were working fine at a different site as we move idc over the weekend so we have new network architecture. Failure errors are hostname/dev/rd/c0d0p3 lev 0 FAILED [Estimate timeout from hostname] hostname

Re: estimate timeout

McDonagh, Joe wrote: I have an estimate timeout of three hours, is there anyway to skip the estimate or what? It's getting estimate timeout, the fs is fine, it can be read from and everything, it just has loads of small files. You might want to consider upgrading the server and client involv

Re: estimate timeout

McDonagh, Joe wrote: I have an estimate timeout of three hours, is there anyway to skip the estimate or what? It's getting estimate timeout, the fs is fine, it can be read from and everything, it just has loads of small files. If you have amanda 2.4.5, you can use alternate methods fo

estimate timeout

I have an estimate timeout of three hours, is there anyway to skip the estimate or what? It's getting estimate timeout, the fs is fine, it can be read from and everything, it just has loads of small files.

Estimate Timeout through iptables firewall

This is mostly just for the archives. I had problems with some clients timing out on estimates when running through a linux firewall (2.6.9 patched and 2.6.10). The problem was that ip_conntrack_amanda was closing the return path before the clients could finish, so the estimate results were gettin

Re: Estimate timeout error

Nick Danger wrote: Paul Bijnens wrote: But the reply packet never got acknowledged by the server. Somehow it got lost or corrupted. Default route for reverse path not correct? Wrong subnetmask? Try do get a network trace at the client and server, and inbetween (don't know how to accomplish that on

Re: Estimate timeout error

Paul Bijnens wrote: But the reply packet never got acknowledged by the server. Somehow it got lost or corrupted. Default route for reverse path not correct? Wrong subnetmask? Try do get a network trace at the client and server, and inbetween (don't know how to accomplish that on a PIX firewall): S

Re: Estimate timeout error

Nick Danger wrote: There is a PIX between the two, but Im backing up a bunch (10?) linux and solaris servers in the same areas of the network, to this same amanda server without any issues so I dont believe it to be a firewall issue. There are no iptables running on either host (both linux in th

Re: Estimate timeout error

ndad: time 232.446: pid 21896 finish time Fri Dec 3 09:01:32 2004 Paul Bijnens wrote: Nick Danger wrote: Nope - still a problem. The error is still as below: FAILURE AND STRANGE DUMP SUMMARY: dominion.h /var lev 0 FAILED [Estimate timeout from dominion.xxx] dominion.h /usr/local lev 0 FAILED [Estima

Re: lev 0 FAILED [Estimate timeout from ******]

ave a Digital Unix machine that give me some strange results when i try to use amanda. If i configure disklist with 2 or more disks of the Digital Unix machine, "the amanda report" tell me this: xxx/ lev 0 FAILED [Estimate timeout from xx] xxx/usr lev 0 FAILED [E

Re: lev 0 FAILED [Estimate timeout from ******]

t; >>>try to use amanda. > >>> If i configure disklist with 2 or more disks of the Digital Unix > >>>machine, "the amanda report" tell me this: > >>> > >>>xxx/ lev 0 FAILED [Estimate timeout from xx] > >>>x

Re: Estimate timeout error

Nick Danger wrote: Nope - still a problem. The error is still as below: FAILURE AND STRANGE DUMP SUMMARY: dominion.h /var lev 0 FAILED [Estimate timeout from dominion.xxx] dominion.h /usr/local lev 0 FAILED [Estimate timeout from dominion.xxx] dominion.h /usr lev 0 FAILED [Estimate timeout from

Re: Estimate timeout error

is still as below: FAILURE AND STRANGE DUMP SUMMARY: dominion.h /var lev 0 FAILED [Estimate timeout from dominion.xxx] dominion.h /usr/local lev 0 FAILED [Estimate timeout from dominion.xxx] dominion.h /usr lev 0 FAILED [Estimate timeout from dominion.xxx] dominion.h /u00 lev 0 FAILED [Estimate

Re: lev 0 FAILED [Estimate timeout from ******]

gital Unix machine, "the amanda report" tell me this: xxx/ lev 0 FAILED [Estimate timeout from xx] xxx/usr lev 0 FAILED [Estimate timeout from xx] xxx/ lev 0 FAILED [Estimate timeout from xx] The amandad.20041202142753000.debug file in Digital Ma

Re: lev 0 FAILED [Estimate timeout from ******]

If i configure disklist with 2 or more disks of the Digital Unix > > machine, "the amanda report" tell me this: > > > > xxx/ lev 0 FAILED [Estimate timeout from xx] > > xxx/usr lev 0 FAILED [Estimate timeout from xx] > > x

Re: lev 0 FAILED [Estimate timeout from ******]

Nuno Dias schrieb: Hi, I have a Digital Unix machine that give me some strange results when i try to use amanda. If i configure disklist with 2 or more disks of the Digital Unix machine, "the amanda report" tell me this: xxx/ lev 0 FAILED [Estimate timeout from x

lev 0 FAILED [Estimate timeout from ******]

Hi, I have a Digital Unix machine that give me some strange results when i try to use amanda. If i configure disklist with 2 or more disks of the Digital Unix machine, "the amanda report" tell me this: xxx/ lev 0 FAILED [Estimate timeout from xx] xxx/usr le

Re: Estimate timeout error

On Monday 29 November 2004 09:00, Nick Danger wrote: Is there any way to properly calculate what your timeout estimate value should be other then trial and error? I have a partition on a machine that gives this error. " dominion.h /u00 lev 0 FAILED [Estimate timeout from dominion] Have a lo

Re: Estimate timeout error

On Monday 29 November 2004 09:00, Nick Danger wrote: >Is there any way to properly calculate what your timeout estimate > value should be other then trial and error? I have a partition on a > machine that gives this error. " > >dominion.h /u00 lev 0 FAILED [Estimate timeout fr

Re: Estimate timeout error

On Mon, Nov 29, 2004 at 09:00:44AM -0500, Nick Danger enlightened us: > Is there any way to properly calculate what your timeout estimate value > should be other then trial and error? I have a partition on a machine > that gives this error. " > > dominion.h /u00 lev 0 FAIL

Estimate timeout error

Is there any way to properly calculate what your timeout estimate value should be other then trial and error? I have a partition on a machine that gives this error. " dominion.h /u00 lev 0 FAILED [Estimate timeout from dominion] If I remove that partition from disklist, all other partitio

Re: Estimate timeout

Joshua Baker-LePain wrote: > "admin prohibited" is definately a result of iptables filtering. > Have a close look in homer. Execute "iptables -L". > > Maybe the solution is loading the amanda iptables module, > if that is available on the machine. I'd be interested to see if that fixes it. The fol

Re: Estimate timeout

On Thursday 10 June 2004 07:59, Joshua Baker-LePain wrote: >On Thu, 10 Jun 2004 at 1:40pm, Paul Bijnens wrote > >> I have been thinking about this problem, and, without any real >> testing to backup my hypothesis, I believe the problem lies in the >> default timeout in iptables for UDP traffic, as

Re: Estimate timeout

Joshua Baker-LePain wrote: It seems to be tuneable. From the header of the source code: * Module load syntax: * insmod ip_conntrack_amanda.o [master_timeout=n] * * Where master_timeout is the timeout (in seconds) of the master * connection (port 10080). This default

Re: Estimate timeout

On Thu, 10 Jun 2004 at 2:11pm, Paul Bijnens wrote > > Is this true even with ip_conntrack_amanda loaded? > > > I should have a look at the source code, or find a detailed doc that > explains it, to find out. > > Anyway that module should somehow know the etimeout parameter > of amanda.conf, whi

Re: Estimate timeout

Joshua Baker-LePain wrote: On Thu, 10 Jun 2004 at 1:40pm, Paul Bijnens wrote I have been thinking about this problem, and, without any real testing to backup my hypothesis, I believe the problem lies in the default timeout in iptables for UDP traffic, as you decided too. For TCP traffic, once a pa

Re: Estimate timeout

On Thu, 10 Jun 2004 at 1:40pm, Paul Bijnens wrote > I have been thinking about this problem, and, without any real testing > to backup my hypothesis, I believe the problem lies in the default > timeout in iptables for UDP traffic, as you decided too. > > For TCP traffic, once a packet is replied,

Re: Estimate timeout

Joshua Baker-LePain wrote: On Thu, 10 Jun 2004 at 9:31am, Paul Bijnens wrote Steven Schoch wrote: Now we're getting somewhere. The tcpdump shows this: 15:01:56.739818 homer > marge: icmp: host homer unreachable - admin prohibited [tos 0xc0] My guess is that ICMP message is something to do with a

Re: Estimate timeout

On Thu, 10 Jun 2004 at 9:31am, Paul Bijnens wrote > Steven Schoch wrote: > > > Now we're getting somewhere. The tcpdump shows this: > > > > 15:01:56.739818 homer > marge: icmp: host homer unreachable - admin > > prohibited [tos 0xc0] > > > > My guess is that ICMP message is something to do wi

Re: Estimate timeout

Steven Schoch wrote: on Wed, 09 Jun 2004 Paul Bijnens wrote: Try to find out where the UDP packet got dropped, using tcpdump or etherreal or other network analyzer on homer and marge. Now we're getting somewhere. The tcpdump shows this: 15:01:56.739818 homer > marge: icmp: host homer unreachable

Re: Estimate timeout

on Wed, 09 Jun 2004 Paul Bijnens wrote: Try to find out where the UDP packet got dropped, using tcpdump or etherreal or other network analyzer on homer and marge. Now we're getting somewhere. The tcpdump shows this: 14:54:28.697197 homer.858 > marge.amanda: udp 117 (DF) 14:54:29.176236 marge.aman

Re: Estimate timeout

Steven Schoch wrote: It was working for several days, then all of a sudden it stopped and hasn't worked since. First thing to ask is: what did change since then? Installed something? Reconfigured something? Rebooted system? amandad: time 447.906: sending REP packet: It took less than 550 seconds

Estimate timeout

imates for marge:/ setup_estimate: marge:/: command 0, options: last_level 0 next_level0 21 level_days 0 getting estimates 0 (39486) 1 (0) -1 (-1) ... planner: time 223.483: got result for host homer disk /home: 0 -> 4642543K, 4 -> 899568K, -1 -> -1K planner: time 10801.886: error result for

  1   2   >