It is the amanda client host (ufo1000) that closed the connection, check
the system log file and amanda debug files.
Jean-Louis
On 11/29/2012 08:51 AM, Olivier Nicole wrote:
Hi,
I have a strange combination of errors:
[data read: Connection reset by peer]
[index read: Connection reset
Hi,
I have a strange combination of errors:
[data read: Connection reset by peer]
[index read: Connection reset by peer]
[missing size line from sendbackup]
I giigled for these, but they never show up combined like that.
Below is the report and amdump.
Thank you if you can tell me what
hi
I forgot to say that the client run
amanda-backup_client-2.6.0p1-1.rhel4 and the server
amanda-backup_server-2.5.2p1-1.rhel5
julien
julien brule a écrit :
Hi list,
I've got the "Mesg read: Connection reset by peer" problem
I see in the dumper.debug file on the s
Hi list,
I've got the "Mesg read: Connection reset by peer" problem
I see in the dumper.debug file on the server this line
dumper: time 27813.730: (sockaddr_in6 *)0x904c30 = { 10, 10080,
:::145.238.170.197 }
dumper: time 27873.720: security_seterror(handle=0x8c66c18, driver
Takashi Kurakata wrote:
Hi all
I'm sorry if you understand my English.I have the pleasure of writing to
you again.
I examine why this log "Mesg read: Connection reset by peer" is output.
To want to repeat it, I executed the following commands on the server.
- amdump daily
Hi all
I'm sorry if you understand my English.I have the pleasure of writing to you
again.
I examine why this log "Mesg read: Connection reset by peer" is output.
To want to repeat it, I executed the following commands on the server.
- amdump daily
- iptables -A INPUT -p tcp -
Thanks for all the help... I upgraded my amanda-server version to 2.5.2
and that seems to have fixed the problem.
Jean-Louis Martineau wrote:
Steven Settlemyre wrote:
From amdump log:
This similar flow happens every time it fails. At first I was worried
about the "not enough diskspace" messa
Steven Settlemyre wrote:
From amdump log:
This similar flow happens every time it fails. At first I was worried
about the "not enough diskspace" message, but this is just because my
holding disk filled up. I see the same thing happening in successful
runs.
In some case, this error is fatal,
t; Steven Settlemyre wrote:
>>>> I haven't changed my configs for months and things were running great
>>>> until last week. Since last tues, none of my dailies have finished,
>>>> and last night a monthly failed.
>>>>
>>>> Looking t
ed,
and last night a monthly failed.
Looking through the logs I see the problem always seems to start with
"data write: Connection reset by peer" and "Don't know how to send
ABORT command to chunker". I'm having a hard time interpreting the
logs and can't seem to fin
and last night a monthly failed.
>>
>> Looking through the logs I see the problem always seems to start with
>> "data write: Connection reset by peer" and "Don't know how to send
>> ABORT command to chunker". I'm having a hard time interpreting the
&
start with
"data write: Connection reset by peer" and "Don't know how to send
ABORT command to chunker". I'm having a hard time interpreting the
logs and can't seem to find too much in the archives about this. Was
wondering if someone could walk me through an expl
I haven't changed my configs for months and things were running great
until last week. Since last tues, none of my dailies have finished, and
last night a monthly failed.
Looking through the logs I see the problem always seems to start with
"data write: Connection reset by peer&q
0 0 linux:amanda*:*
If I execute the command as
amrecover
It is giving the following prolem
AMRECOVER Version 2.5.0p2. Contacting server on linux
...
amrecover: Error reading line from server: Connection
reset by peer
Please provide the solution .
Thanks & Reg
On Mon, 7 Aug 2006, mario wrote:
> the ubuntu package "cdrw-taper" caused this problem, afer removing it
> everything seems to go fine (it came with a weird/broken perl script). I
> have some other sort of problem now, which i will post in a new mail.
If it behaves like plain Debian, make sure use
t; > START planner date 20060807
> > WARNING planner tapecycle (8) <= runspercycle (28)
> > INFO planner Adding new disk localhost:md1.
> > STATS driver startup time 0.067
> > FATAL driver reading result from taper: Connection reset by peer
> > FAIL planner localhost
s.
>START planner date 20060807
>WARNING planner tapecycle (8) <= runspercycle (28)
>INFO planner Adding new disk localhost:md1.
>STATS driver startup time 0.067
>FATAL driver reading result from taper: Connection reset by peer
>FAIL planner localhost md1 20060807 0 [dump lar
ercycle (28)
> INFO planner Adding new disk localhost:md1.
> STATS driver startup time 0.067
> FATAL driver reading result from taper: Connection reset by peer
> FAIL planner localhost md1 20060807 0 [dump larger than tape, 30864297
> KB, but cannot incremental dump new disk]
&
TAL driver reading result from taper: Connection reset by peer
FAIL planner localhost md1 20060807 0 [dump larger than tape, 30864297
KB, but cannot incremental dump new disk]
FATAL planner cannot fit anything on tape, bailing out
# netstat -nap |grep 1008
tcp0 0 0.0.0.0:10
blem: your tape is full (or broken).
>
>
>
> > Some dumps may have been left in the holding disk.
> > Run amflush to flush them to tape.
> > The next tape Amanda expects to use is: SMTLSet106.
> >
> > /-- server / lev 0 FAILED ["data write: Connection res
disk.
Run amflush to flush them to tape.
The next tape Amanda expects to use is: SMTLSet106.
/-- server / lev 0 FAILED ["data write: Connection reset by peer"]
Is this backup bypassing the holdingdisk?
And was it interrupted by the tape full error above?
I checked the servers /
write: Connection reset by peer"]
I checked the servers /tmp/amanda directory and less the debuy file But
I see nothing there to alarm me!..
# less amandad.20060704144439000.debug
amandad: time 0.000: sending ack:
Amanda 2.4 ACK HANDLE 003-18910808 SEQ 1152020450
amandad: time 0.007: bs
anakin /boot RESULTS MISSING
> >^^^
> > | ...
> > | driver: FATAL reading result from taper: Connection reset by peer
> > ^
>
> Seems like taper died suddenly?
> Or the TCP connecti
/ RESULTS MISSING
^^^
| anakin /boot RESULTS MISSING
^^^
| ...
| driver: FATAL reading result from taper: Connection reset by
^^^
| anakin /boot RESULTS MISSING
^^^
| ...
| driver: FATAL reading result from taper: Connection reset by peer
On Wed, Jun 25, 2003 at 06:04:23PM -0500, Brian G. Peterson wrote:
> amandates botch: hda6 lev 0: new dumpdate 1056177662 old 1056177943
> sendbackup-gnutar: time 0.022: doing level 0 dump from date: 1970-01-01
> 0:00:00 GMT
> sendbackup: time 0.024: spawning /usr/lib/amanda/runtar in pipeline
> s
> On Wednesday 25 June 2003 18:37, Brian G. Peterson wrote:
> >I got one response telling me to make sure that the tar was gnu tar.
> > All that checked out. Any other ideas? I'm really stuck here...
>
> Perchance have you got another older version of tar that's found first
> in the $PATH? Do a
ports from the Amanda server.
>
>Can somebody please give me some pointers on what can cause the
> connection reset error? I can't find anything like this via Google
> or on the Amanda Faq-o-matic.
>
>Thank you,
>
> - Brian Peterson
>
>FAILURE AND STRANGE DUMP SUMMARY:
>
Thanks. - Brian
Joshua Baker-LePain asks:
> What's in the /tmp/amanda/sendbackup*debug on the client corresponding to
> the failing dump?
Here is the debug output typical of one of the failed hdb1 dumps:
sendbackup.20030623143153.debug:
sendbackup: debug 1 pid 6582 ruid 33 euid 33: start at Mon
On Wed, 25 Jun 2003 at 5:37pm, Brian G. Peterson wrote
> I got one response telling me to make sure that the tar was gnu tar. All
> that checked out. Any other ideas? I'm really stuck here...
What's in the /tmp/amanda/sendbackup*debug on the client corresponding to
the failing dump?
--
Josh
what can cause the connection
reset error? I can't find anything like this via Google or on the Amanda
Faq-o-matic.
Thank you,
- Brian Peterson
FAILURE AND STRANGE DUMP SUMMARY:
ethos.brav hdb1 lev 0 FAILED [mesg read: Connection reset by peer]
FAILED AND STRANGE DUMP DETAILS:
/--
Jon LaBadie suggests:
> Just a shot in the dark ...
>
> On Tue, Jun 24, 2003 at 08:28:15AM -0500, Brian G. Peterson wrote:
> ...
> > sendbackup: start [ethos.braverock.com:hdb1 level 0]
> > sendbackup: info BACKUP=/bin/tar
> > sendbackup: info RECOVER_CMD=/bin/tar -f... -
>
pointers on what can cause the connection
reset error? I can't find anything like this via Google or on the Amanda
Faq-o-matic.
Thank you,
- Brian Peterson
FAILURE AND STRANGE DUMP SUMMARY:
ethos.brav hdb1 lev 0 FAILED [mesg read: Connection reset by peer]
FAILED AND STRANGE DUMP DE
>-> i have to launch "/usr/local/sbin/amrecover -d /dev/rmt/0" instead of
>"/usr/local/sbin/amrecover DailySet1"
One point -- you should use a non-rewinding device name for anything
you do with Amanda. So that should be "-d /dev/rmt/0n".
Also, I'm guessing, based on the device name, that you're
Hi,
Ok i just find the problem :
-> in the ined.conf the user amanda was not well write
-> i have to launch "/usr/local/sbin/amrecover -d /dev/rmt/0" instead of
"/usr/local/sbin/amrecover DailySet1"
Sorry for annoying. I just post my solution in hope it helps some.
Bye
Lorenzo
er: error reading tape: Connection reset by peer
> Hi,
>
> I successfuly backup files to my DLT (thanks the FAQ ;-)
> When I want to restore, i got an problem :
>
> amrecover: error reading tape: Connection reset by peer
> extract_list - child returned non-zero status: 1
>
> P
Hi,
I successfuly backup files to my DLT (thanks the FAQ ;-)
When I want to restore, i got an problem :
amrecover: error reading tape: Connection reset by peer
extract_list - child returned non-zero status: 1
PS : I use Sparc/Solaris8 + Amanda version 2.4.2p2 + gtar1.13.19
Can
>Also, I've read other messages in the archive with this problem and it seems
>to relate to firewall settings. The remote system is not behind any type of
>firewall, but the amanda backup server dis behin a firewall on the local
>network. What kind of timeout setting would i have to set on th
On three of my remote systems running Amanda 2.4.2p2 i am always getting a
"mesg read: Connection reset by peer" error back from the email report. And
the filesystems are not being backed up.
ss3.airsse /home lev 0 FAILED [mesg read: Connection reset by peer]
mc4.airsce /home le
>sendbackup: debug 1 pid 18993 ruid 5023 euid 5023 start time Wed Jul 4 03:43:28 2001
>index tee cannot write [Broken pipe]
>sendbackup: pid 18995 finish time Wed Jul 4 05:43:45 2001
>
>Failed backup occured because the index tee cannot write.
No, that's just a symptom of the connection being s
04, 2001 2:42 AM
To: Edward Tsang
Cc: [EMAIL PROTECTED]
Subject: Re: Connection reset by peer problem again
>... Firewall is present between the client and amanda server. But we already ope
>ned a full hole for amanda traffic.
>...
> sugar /export/home lev 0 FAILED [mesg read: C
>... Firewall is present between the client and amanda server. But we already ope
>ned a full hole for amanda traffic.
>...
> sugar /export/home lev 0 FAILED [mesg read: Connection reset by peer]
This says the client (or the firewall) closed this connection and dumper
on the se
llowing is an extract of amanda report
FAILURE AND STRANGE DUMP SUMMARY:
sugar /export/home lev 0 FAILED [mesg read: Connection reset by peer]
FAILED AND STRANGE DUMP DETAILS:
/-- sugar /export/home lev 0 FAILED [mesg read: Connection reset by peer]
sendbackup: start [sugar:/export/ho
>Here is the result from the amdump log:
>driver: result time 559.820 from dumper0: FAILED 00-1 [data read:
>Connection
> reset by peer]
>driver: QUITTING time 559.841 telling children to quit
OK, now that I understand you're not splitting clients among multiple
se
>I am running amanda 2.4.1-p1 on some Compaq tru-64 boxes attached to DLT's.
>The number of systems I have been backing up has grown dramatically
>recently, so I have split the backups up to run to two different Amanda
>servers.
>
>The problem I have is that I can run backups from 2 of my clients
ound in the archives.
I have checked all of the /tmp/amanda *.debug files with no clues.
I have tried running a continues ping between the machines while the backup
was running-no impact.
Here is the result from the amdump log:
driver: result time 559.820 from dumper0: FAILED 00-1 [data read:
46 matches
Mail list logo
