Re: 2.5.1p3: amcheck can't connect with bsdauth

* Jean-Louis Martineau <[EMAIL PROTECTED]> [20070214 11:16]: > Jean-Francois Malouin wrote: > > > >amandad:COMPRESS_BEST_OPT="--best" UNCOMPRESS_OPT="-dc" > >amandad: time 0.000: getpeername returned: Transport endpoint is not > >conn

Re: 2.5.1p3: amcheck can't connect with bsdauth

* Jean-Louis Martineau <[EMAIL PROTECTED]> [20070214 11:16]: > Jean-Francois Malouin wrote: > > > >amandad:COMPRESS_BEST_OPT="--best" UNCOMPRESS_OPT="-dc" > >amandad: time 0.000: getpeername returned: Transport endpoint is not > >conn

Re: dumpers

On Wed, Feb 14, 2007 at 07:23:27AM +0100, Dipl.Ing.Trompler Wilhelm wrote: > Dear reader, > > I am using VERSION="Amanda-2.4.4p2" on a LINUX 2.6.5 with LTO-3 tapes. In > general the performance is great, but on every forced, complete backup, the > procedure takes almost 24 hours. > > I have to b

Re: 2.5.1p3: amcheck can't connect with bsdauth

Jean-Francois Malouin wrote: amandad:COMPRESS_BEST_OPT="--best" UNCOMPRESS_OPT="-dc" amandad: time 0.000: getpeername returned: Transport endpoint is not connected This is strange, it's like the stdin of amandad is not connected to the network socket. Apply the attached patch and r

Re: dumpers

Hi, In your dumptypes definition what do you have the maxdumps variable set to? I had a similar problem, I think even if you have inparallel set to a high number there will still only be one dumper per client unless you set the maxdumps to something other then 1. -Sergei On (02/14/07 07:23

Re: 2.5.1p3: amcheck can't connect with bsdauth

* Jean-Louis Martineau <[EMAIL PROTECTED]> [20070214 10:22]: > Jean-Francois, > > Do you have an amanda..debug file? Post it. attached. > Could you show your inetd configuration? In one line: amanda-conf3 stream tcp nowait amanda /opt/amanda/amanda3/libexec/amandad am

Re: 2.5.1p3: amcheck can't connect with bsdauth

Jean-Francois, Do you have an amanda..debug file? Post it. Could you show your inetd configuration? Did 10088 the correct port number for your confX testing config? Jean-Francois Malouin wrote: Hi, Just had my first hand at 2.5.1p3 and I got a error with amcheck similar to the one I reported b

Re: 2.5.1p3: amcheck can't connect with bsdauth

Oups! That should have been bsdtcp auth NOT bsd. Sorry! jf * Jean-Francois Malouin <[EMAIL PROTECTED]> [20070214 09:57]: > Hi, > > Just had my first hand at 2.5.1p3 and I got a error with amcheck similar > to the one I reported back in September with 2.5.1p1 while usin

2.5.1p3: amcheck can't connect with bsdauth

Hi, Just had my first hand at 2.5.1p3 and I got a error with amcheck similar to the one I reported back in September with 2.5.1p1 while using bsdauth client authentication (server is the only client at the moment, irix-6.5.x): WARNING: yorick: selfcheck request failed: EOF on read from yorick Cli

Re: dumpers

Hi, Run 'amstatus ', it will tell you why it don't start new dump in parallel. Jean-Louis Dipl.Ing.Trompler Wilhelm wrote: Dear reader, I am using VERSION="Amanda-2.4.4p2" on a LINUX 2.6.5 with LTO-3 tapes. In general the performance is great, but on every forced, complete backup, the proc

Re: dumpers

Stefan G. Weichinger schrieb: > Dipl.Ing.Trompler Wilhelm schrieb: >> Dear reader, >> >> I am using VERSION="Amanda-2.4.4p2" on a LINUX 2.6.5 with LTO-3 tapes. In >> general the performance is great, but on every forced, complete backup, the >> procedure takes almost 24 hours. >> >> I have to back

Re: dumpers

Dipl.Ing.Trompler Wilhelm schrieb: > Dear reader, > > I am using VERSION="Amanda-2.4.4p2" on a LINUX 2.6.5 with LTO-3 tapes. In > general the performance is great, but on every forced, complete backup, the > procedure takes almost 24 hours. > > I have to backup about 700 GB uncompressed, and sup