Re: client timing out
Paul Bijnens wrote: > > C. Wilson wrote: > > > I have not been able to get a backup of one of my amanda clients for 3 > > days. The only errors I can find is in the > > amandad.20031104013547000.debug, which are: > > You left out the "noop" request just before, I believe. > > > > > amandad: time 7453.715: dgram_recv: timeout after 10 seconds > > amandad: time 7453.715: waiting for ack: timeout, retrying > > amandad: time 7463.715: dgram_recv: timeout after 10 seconds > > amandad: time 7463.715: waiting for ack: timeout, retrying > > amandad: time 7473.715: dgram_recv: timeout after 10 seconds > > amandad: time 7473.715: waiting for ack: timeout, retrying > > amandad: time 7483.715: dgram_recv: timeout after 10 seconds > > amandad: time 7483.715: waiting for ack: timeout, retrying > > amandad: time 7493.715: dgram_recv: timeout after 10 seconds > > amandad: time 7493.715: waiting for ack: timeout, giving up! > > amandad: time 7493.715: pid 4331 finish time Tue Nov 4 03:40:41 2003 > > > > I've searched the FAQ which suggested that I increase the ctimeout value > > in the amanda.conf file. I increased the value from 30 to 120 on the > > Amanda server, but it's still timing out. > > This is just a symptom that the the computer never received an ack > packet. Something in the netwrok setup? (is the computer replying > to the correct server? multiple Network card? Firewall blocking? > etc. etc.) > Increasing the ctimeout will not help. > > -- > Paul Bijnens, XplanationTel +32 16 397.511 > Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 > http://www.xplanation.com/ email: [EMAIL PROTECTED] > *** > * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * > * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * > * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * > * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * > * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* > * ... "Are you sure?" ... YES ... Phew ... I'm out * > *** I have two amandad debug files on the client: amandad.20031107100613000.debug amandad.20031107100613.debug The "noop" is in the amandad.20031107100613.debug file, that has no errors. The amandad.20031107100613000.debug file is the one with the timeout errors. I find no errors in my Amanda server debug files. There's no firewall and I don't see any evidence that's it's dropping off the net. It only has one ethernet card and I checked to make sure the router and the box were set at Full Duplex. No packet loss or collisions and DNS seems to be working fine. I'm still confussed on what it can be and how to resolve it. Thanks for your response, CWilson
client timing out
I have not been able to get a backup of one of my amanda clients for 3 days. The only errors I can find is in the amandad.20031104013547000.debug, which are: amandad: time 7453.715: dgram_recv: timeout after 10 seconds amandad: time 7453.715: waiting for ack: timeout, retrying amandad: time 7463.715: dgram_recv: timeout after 10 seconds amandad: time 7463.715: waiting for ack: timeout, retrying amandad: time 7473.715: dgram_recv: timeout after 10 seconds amandad: time 7473.715: waiting for ack: timeout, retrying amandad: time 7483.715: dgram_recv: timeout after 10 seconds amandad: time 7483.715: waiting for ack: timeout, retrying amandad: time 7493.715: dgram_recv: timeout after 10 seconds amandad: time 7493.715: waiting for ack: timeout, giving up! amandad: time 7493.715: pid 4331 finish time Tue Nov 4 03:40:41 2003 I've searched the FAQ which suggested that I increase the ctimeout value in the amanda.conf file. I increased the value from 30 to 120 on the Amanda server, but it's still timing out. Should I keep increasing the ctimeout value until I find the magic number or is there anything else I should be looking at? Thanks in advance, CWilson
Re: problems running amrecover
I figured out the problem, I was using the SCSI tapetype instead of the
IDE for the STT8000A. Thanks for the fast response Paul and redirecting
my focus on the tape drive, instead of gzip.
What it should be for IDE:
define tapetype STT8000A {
comment "STT8000A Tape Device"
length 3850 mbytes # 4/8 Gig tapes
filemark 0 kbytes # I don't know what this means
speed 505 kbytes
}
Thanks,
CWilson
"C. Wilson" wrote:
>
> Paul Bijnens wrote:
> >
> > C. Wilson wrote:
> > >
> > > amrestore: 0: skipping start of tape: date 20030709 label VOL02
> > > amrestore: 1: restoring plate.tech.net._.20030709.0
> > >
> > > gzip: stdin: not in gzip format
> > > Error 32 (Broken pipe) offset 26624+26624, wrote 0
> > > amrestore: pipe reader has quit in middle of file.
> > > amidxtaped: time 12.741: amrestore terminated normally with status: 2
> > > amidxtaped: time 12.741: rewinding tape ...
> > > amidxtaped: time 24.756: done
> > > amidxtaped: time 24.756: pid 10098 finish time Thu Jul 10 11:53:04 2003
> >
> > What is the file header on the tape? Try:
> >
> >amrestore -h /dev/the/tape
> >
> # /usr/local/sbin/amrestore -h /dev/nht0
> amrestore: 0: skipping start of tape: date 20030709 label VOL02
> amrestore: 1: restoring pluto.chi.cooketech.net._.20030709.0
>
> gzip: stdin: not in gzip format
> Error 32 (Broken pipe) offset 26624+26624, wrote 0
> amrestore: pipe reader has quit in middle of file.
>
>
> > What is the blocksize of your tape device? Try:
> >
> > mt -f /dev/the/tape status
> # mt -f /dev/ht0 status
> SCSI 2 tape drive:
> File number=0, block number=0, partition=0.
> Tape block size 512 bytes. Density code 0x0 (default).
> Soft error count since last status=0
> General status bits on (0):
>
> >
> > (I don't remember how solaris reacts to different blocksizes,
> > must be using to much linux here.)
> No Solaris needed, just Linux (RedHat 7.2)
> >
> > --
> > Paul Bijnens, XplanationTel +32 16 397.511
> > Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512
> > http://www.xplanation.com/ email: [EMAIL PROTECTED]
> > ***
> > * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, *
> > * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, *
> > * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, *
> > * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, *
> > * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...*
> > * ... "Are you sure?" ... YES ... Phew ... I'm out *
> > ***
>
Re: problems running amrecover
Paul Bijnens wrote: > > C. Wilson wrote: > > > > amrestore: 0: skipping start of tape: date 20030709 label VOL02 > > amrestore: 1: restoring plate.tech.net._.20030709.0 > > > > gzip: stdin: not in gzip format > > Error 32 (Broken pipe) offset 26624+26624, wrote 0 > > amrestore: pipe reader has quit in middle of file. > > amidxtaped: time 12.741: amrestore terminated normally with status: 2 > > amidxtaped: time 12.741: rewinding tape ... > > amidxtaped: time 24.756: done > > amidxtaped: time 24.756: pid 10098 finish time Thu Jul 10 11:53:04 2003 > > What is the file header on the tape? Try: > >amrestore -h /dev/the/tape > # /usr/local/sbin/amrestore -h /dev/nht0 amrestore: 0: skipping start of tape: date 20030709 label VOL02 amrestore: 1: restoring pluto.chi.cooketech.net._.20030709.0 gzip: stdin: not in gzip format Error 32 (Broken pipe) offset 26624+26624, wrote 0 amrestore: pipe reader has quit in middle of file. > What is the blocksize of your tape device? Try: > > mt -f /dev/the/tape status # mt -f /dev/ht0 status SCSI 2 tape drive: File number=0, block number=0, partition=0. Tape block size 512 bytes. Density code 0x0 (default). Soft error count since last status=0 General status bits on (0): > > (I don't remember how solaris reacts to different blocksizes, > must be using to much linux here.) No Solaris needed, just Linux (RedHat 7.2) > > -- > Paul Bijnens, XplanationTel +32 16 397.511 > Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 > http://www.xplanation.com/ email: [EMAIL PROTECTED] > *** > * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * > * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * > * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * > * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * > * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* > * ... "Are you sure?" ... YES ... Phew ... I'm out * > *** -- Cheryl Wilson UNIX Systems Engineer Cooke Technologies
problems running amrecover
First, let me start by saying I don't have much Admin. experience with
Linux. I offered to help a friend get Amanda running on his Linux box
(RedHat 7.2), since I installed it on my Solaris 8 servers without any
problems.
I installed version 2.4.4 and got it configured as a server without any
problems. I'm able to do an "amdump", but I keep getting the following
errors when I try to do an "amrecover"
Continue [?/Y/n/s/t]? y
tar: ./home/cwilson/inetd.conf: Not found in archive
tar: Error exit delayed from previous errors
extract_list - child returned non-zero status: 2
Continue [?/Y/n/r]?
I've gone through my debug logs and I was able to find the following
errors in the amidxtaped debug file.
amrestore: 0: skipping start of tape: date 20030709 label VOL02
amrestore: 1: restoring plate.tech.net._.20030709.0
gzip: stdin: not in gzip format
Error 32 (Broken pipe) offset 26624+26624, wrote 0
amrestore: pipe reader has quit in middle of file.
amidxtaped: time 12.741: amrestore terminated normally with status: 2
amidxtaped: time 12.741: rewinding tape ...
amidxtaped: time 24.756: done
amidxtaped: time 24.756: pid 10098 finish time Thu Jul 10 11:53:04 2003
EXTRA INFO:
Tape drive is a Seagate STT8000A
define tapetype STT8000A {
comment "STT8000A Tape Device"
length 4000 mbytes # 4/8 Gig tapes
filemark 22 kbytes # I don't know what this means
speed 551 kbytes
}
In my disklist I'm calling this dump type:
define dumptype Scomp-nohold {
comment "partitions on amanda server straight to tape"
program "GNUTAR"
index yes
compress client best
exclude list ".amanda.excludes"
holdingdisk no
priority high
}
Here's some version info:
gzip 1.3
gtar 1.13.25
Any help would be greatly appreciated.
Thanks,
--
CWilson
