On Tue, Apr 1, 2008 at 2:45 AM, Mister Olli <[EMAIL PROTECTED]> wrote:
> OK 'bsdtcp' authentication works. So its definitely a firewall issue.
> So how to configure amanda that I use bsd authentication over UDP?
>
> what ports are in use for the transmission of the gtar ouput?
This page should
hi...
> This would be an excellent diagnostic check, at least. If it works,
> then you know you have a firewall problem. If not, you can look for
> something else.
OK 'bsdtcp' authentication works. So its definitely a firewall issue.
So how to configure amanda that I use bsd authentication over
On Mon, Mar 31, 2008 at 9:03 AM, Mister Olli <[EMAIL PROTECTED]> wrote:
> sorry not an option, cause authentication scheme needs to be the same on
> all backup clients.
> and changing the rest because of (maybe) one firewall issue on an ESX
> server is too much work.
It doesn't need to be the
hi...
> > I just re-read the docs about ports, and I hope to understand it right.
> > - If I have a firewall between the backup client and server, the
> > easiest thing is to compile the client with custom --with-tcpportrange
> > and --with-udpportrange settings, and then open these ports in the
Mister Olli wrote:
I just re-read the docs about ports, and I hope to understand it right.
- If I have a firewall between the backup client and server, the
easiest thing is to compile the client with custom --with-tcpportrange
and --with-udpportrange settings, and then open these ports in the
f
Hi...
> Hmm.. this sounds like a network/firewall issue to me, with a 90
> second timeout. Have you had a look at the packet dump between the
> server and the client? Are reply packets being dropped? Amanda's
> STARTUP_TIMEOUT is 60s, so this is probably some other timeout.
There are no filter r
On Sun, Mar 30, 2008 at 4:56 PM, Mister Olli <[EMAIL PROTECTED]> wrote:
> I had a look at into the '/tmp/amanda/client/weekly/sendbackup*' files,
> and they all show the same failure:
> sendbackup: time 89.994: index tee cannot write [Broken pipe]
>
> Also this failure occurs constantly around
hi...
I had a look at into the '/tmp/amanda/client/weekly/sendbackup*' files,
and they all show the same failure:
sendbackup: time 89.994: index tee cannot write [Broken pipe]
Also this failure occurs constantly around second 89 to 90.
A complete sendbackup logfile looks like this:
==
OK, here's what I see in the 'strace' output, repeated 15
thousand-some-odd times:
write(1, "nfo\nc0121610 t __constant_c_and_"..., 10240) = -1 EPIPE (Broken pipe)
--- SIGPIPE (Broken pipe) @ 0 (0) ---
So for some reason gtar is ignoring the SIGPIPE signal. There's
probably something else going
On Wed, Mar 26, 2008 at 6:16 PM, Mister Olli <[EMAIL PROTECTED]> wrote:
> hi
So, to summarize, the only command that fails is one which would
otherwise spew massive amounts of data to the console.
I think that the best debugging method at the moment is to return to
running amanda, let it get
hi
> > gtar --create --file - --directory /boot --one-file-system
> > --listed-incremental /root/gtar_test/gnutar-lists/172.31.3.9_boot_0.new
> > --sparse --ignore-failed-read --totals --exclude-from
> > /root/gtar_test/sendbackup._boot.20080320110639.exclude . | cat
> > /dev/null
>
> This d
On Wed, Mar 26, 2008 at 4:11 AM, Mister Olli <[EMAIL PROTECTED]> wrote:
> these 3 command work like a charme (executed for testing, and narrowing
> down the failure):
>
> ===
>
> gtar --create --file - --directory /boo
hi...
Am Dienstag, den 25.03.2008, 17:52 -0400 schrieb Dustin J. Mitchell:
> On Tue, Mar 25, 2008 at 3:13 PM, Mister Olli <[EMAIL PROTECTED]> wrote:
> > > > > > but this does not work, gtar proccess are eating a lot of CPU
> > cycles:
>
> I only have three emails from this conversation, but fr
On Tue, Mar 25, 2008 at 3:13 PM, Mister Olli <[EMAIL PROTECTED]> wrote:
> > > > > but this does not work, gtar proccess are eating a lot of CPU cycles:
I only have three emails from this conversation, but from the number
of quote characters above, there seem to have been more. Oliver, can
you su
hi...
I'm sorry for the delay in the reply, I was on vacations during easter,
and didn't had a chance to work on this.
> > > > but this does not work, gtar proccess are eating a lot of CPU cycles:
> > > > =
> > > > > gtar --crea
Mister Olli <[EMAIL PROTECTED]> (Do 20 Mär 2008 18:42:14 CET):
> hi...
>
> I have big troubles with amanda on vmware ESX server 3.
>
> The gtar proccess hang up/ go into endless loop...
>
> however with the help of the vmware support, we were able to figure out
> the following:
>
> gtar works,
hi...
I have big troubles with amanda on vmware ESX server 3.
The gtar proccess hang up/ go into endless loop...
however with the help of the vmware support, we were able to figure out
the following:
gtar works, if called like this:
> gtar --create --file - --di
17 matches
Mail list logo
