Hi !
But if i use client compression, it should happen on the client, and
then the zipped image should be sent to the amanda server, or am i wrong
? The tar command is piped to gzip on the client. What's the server
waiting for ? The sendsize works well, the runtar works well, but the
sendbackup fails if the client compr. is enabled. That's not clear to me
at all. What happens on the sendback command ?
Perhaps you or anyone else has a solution. My network is not the cause
of the problem. I have a switched environment and can use the whole
bandwith on it.
Thx. in advance
Franz
On Mon, 2003-10-06 at 15:17, Paul Bijnens wrote:
> Franz Skale wrote:
>
> > The problem on the XP running cygwin and Amanda Client 2.4.4p1, lies
> > on the gzip command. I enabled "client fast" in the amanda.conf on
> > the server. If client compress is enabled then the backup fails with:
> > "gzip: stdin: Connection reset by peer". So i turned of client
> > compression. Fazit, the backup works, but the netload is enourmous.
> > The magic thing is, that amanda nevertheless shows the same error,
> > but the dump went on the holding disk. See the output at the end of
> > the mail. Now my question. Is gzip buggy on cygwin, or is it another
> > problem which let gzip fail on stdin compression ? Server Side
> > compression is not working, and the error is still the same. ("gzip:
> > stdin: Connection reset by peer"). Is there a fix or a workaround
> > with some gzip parameters ?
>
> I do not use Cygwin (yet), but to me this seems like the client
> not closing the network socket when finished. Be it gzip or amanda
> on the other end, the error is the same, but the impact is different.
> (I have no solution. Fiddling with gzip will not help, I think.)
--
kind regards, +43-664-8279163
Franz Skale +43-1-7189880-0
Systems Engineer www.cubit.at
PGP KeyID 0xB294D39A
Key Fingerprint B508 8896 B83C B374 770D 80EF 3AD9 4A66 B294 D39A
signature.asc
Description: This is a digitally signed message part
|
