Amanda-Users

Re: dtimeout maximum?

2004-02-22 21:21:23
Subject: Re: dtimeout maximum?
From: stan <stanb AT panix DOT com>
To: amanda users list <amanda-users AT amanda DOT org>
Date: Sun, 22 Feb 2004 21:17:02 -0500
On Sun, Feb 22, 2004 at 03:12:44PM +0100, Paul Bijnens wrote:
> stan wrote:
> 
> >I'm having trouble with 1 or 2 machines repeatadly timing out during
> >backups. I've got dtimeout set to 300000 at the moment. 
> >
> >Seems to me that I rrember that there is a a maximum value ofr this? What
> >is this max? Have I exceded it?
> 
> There is no maximum value.  The timeout is there to catch the occurance
> that clients die without notififying the server in advance.
> 
> What does the /tmp/amanda.run{tar,dump}.* logfiles on that client tell
> you about the backup process?  Compare the logfile with one that did 
> succeed.
> Did it finish normally?
> How long did it take? Set your dtimeout accordingly.
> Or did it die?

The client thinks the server closed the connection (I think).

sendbackup: debug 1 pid 4071 ruid 1001 euid 1001: start at Fri Feb 20 00:59:31 
2004
/usr/local/amanda/libexec/sendbackup: version 2.4.3b4
  parsed request as: program `GNUTAR'
                     disk `hda2'
                     device `hda2'
                     level 3
                     since 2004:2:7:13:51:55
                     options 
`|;auth=bsd;compress-best;index;exclude-list=/usr/local/lib/amanda/exclude.gtar;'
sendbackup: try_socksize: send buffer size is 65536
sendbackup: time 0.007: stream_server: waiting for connection: 0.0.0.0.44222
sendbackup: time 0.007: stream_server: waiting for connection: 0.0.0.0.44223
sendbackup: time 0.007: stream_server: waiting for connection: 0.0.0.0.44224
sendbackup: time 0.007: waiting for connect on 44222, then 44223, then 44224
sendbackup: time 0.009: stream_accept: connection from 205.159.77.224.2044
sendbackup: time 0.010: stream_accept: connection from 205.159.77.224.2045
sendbackup: time 0.011: stream_accept: connection from 205.159.77.224.2046
sendbackup: time 0.011: got all connections
sendbackup: time 0.011: spawning /bin/gzip in pipeline
sendbackup: argument list: /bin/gzip --best
sendbackup-gnutar: time 0.011: pid 4073: /bin/gzip --best
sendbackup-gnutar: time 0.057: doing level 3 dump as listed-incremental from 
/usr/local/amanda/var/amanda/gnutar-lists/teddyhda2_2 to 
/usr/local/amanda/var/amanda/gnutar-lists/teddyhda2_3.new
sendbackup-gnutar: time 0.057: doing level 3 dump from date: 2004-02-07 
13:51:55 GMT
sendbackup: time 0.058: spawning /usr/local/amanda/libexec/runtar in pipeline
sendbackup: argument list: gtar --create --file - --directory / 
--one-file-system --listed-incremental 
/usr/local/amanda/var/amanda/gnutar-lists/teddyhda2_3.new --sparse 
--ignore-failed-read --totals --exclude-from 
/tmp/amanda/sendbackup.hda2.20040220005931.exclude .
sendbackup-gnutar: time 0.072: /usr/local/amanda/libexec/runtar: pid 4075
sendbackup: time 0.084: started index creator: "/bin/tar -tf - 2>/dev/null | 
sed -e 's/^\.//'"
sendbackup: time 785.403: 124: strange(?): 
sendbackup: time 785.413: 124: strange(?): gzip: stdout: Connection reset by 
peer
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
sendbackup: time 785.413: 124: strange(?): sendbackup: index tee cannot write 
[Broken pipe]
sendbackup: time 785.405: index tee cannot write [Broken pipe]
sendbackup: time 785.421: pid 4074 finish time Fri Feb 20 01:12:36 2004
sendbackup: time 785.446: error [/bin/tar got signal 13, compress returned 1]
sendbackup: time 785.446: pid 4071 finish time Fri Feb 20 01:12:36 2004

right?

-- 
"They that would give up essential liberty for temporary safety deserve
neither liberty nor safety."
                                                -- Benjamin Franklin

<Prev in Thread] Current Thread [Next in Thread>