.
FAILURE AND STRANGE DUMP SUMMARY:
zappa.zapp /imagelib lev 1 FAILED [bad CONNECT response]
zappa.zapp /boot lev 0 FAILED 20040615[could not connect to zappa.zappa.cx]
zappa.zapp /home/sunkan lev 1 FAILED 20040615[could not connect to zappa.zappa.cx]
zappa.zapp /var lev 1 FAILED 20040615
is: dflt12.
FAILURE AND STRANGE DUMP SUMMARY:
zappa.zapp /imagelib lev 1 FAILED [bad CONNECT response]
zappa.zapp /boot lev 0 FAILED 20040615[could not connect to zappa.zappa.cx]
zappa.zapp /home/sunkan lev 1 FAILED 20040615[could not connect to zappa.zappa.cx]
zappa.zapp /var lev 1 FAILED
to tape dflt10.
AS The next tape Amanda expects to use is: dflt11.
AS The next new tape already labelled is: dflt12.
AS FAILURE AND STRANGE DUMP SUMMARY:
AS zappa.zapp /imagelib lev 1 FAILED [bad CONNECT response]
AS zappa.zapp /boot lev 0 FAILED 20040615[could not connect to zappa.zappa.cx
to use is: dflt11.
The next new tape already labelled is: dflt12.
FAILURE AND STRANGE DUMP SUMMARY:
zappa.zapp /imagelib lev 1 FAILED [bad CONNECT response]
zappa.zapp /boot lev 0 FAILED 20040615[could not connect to
zappa.zappa.cx]
zappa.zapp /home/sunkan lev 1 FAILED 20040615
Andreas Sundstrom wrote:
Also what do you recommend as parameters to tcpdump, it's all running on the
same host does that mean I can sniff on lo?
This works for me on Linux 2.4.22:
sudo tcpdump -i lo -w trace.lo
--
Paul Bijnens, XplanationTel +32 16 397.511
Quoting Paul Bijnens [EMAIL PROTECTED]:
Andreas Sundstrom wrote:
Also what do you recommend as parameters to tcpdump, it's all running on
the
same host does that mean I can sniff on lo?
This works for me on Linux 2.4.22:
sudo tcpdump -i lo -w trace.lo
I have now made a dump on
Hi, Andreas,
on Dienstag, 15. Juni 2004 at 13:32 you wrote to amanda-users:
AS I have now made a dump on the traffic passing through lo during the amdump.
AS I
AS have also recompiled amanda with these two settings (as another friendly person
AS suggested): --with-tcpportrange=5,50040
Stefan G. Weichinger wrote:
Hi, Andreas,
on Dienstag, 15. Juni 2004 at 13:32 you wrote to amanda-users:
AS I have now made a dump on the traffic passing through lo during the amdump.
AS I
AS have also recompiled amanda with these two settings (as another friendly
person
AS suggested):
Andreas Sundstrom wrote:
I have now made a dump on the traffic passing through lo during the amdump. I
have also recompiled amanda with these two settings (as another friendly person
suggested): --with-tcpportrange=5,50040 --with-udpportrange=890,899
The dump is available at
Paul Bijnens wrote:
It seems ethereal store only the first few bytes of each packet.
There is probably an option to set that size; similar to tcpdump -s 1500.
That means I don't have the full info, but I believe I've seen enough!
Following up on myself.
I've digged into the amanda source, and
Amanda 2.4.4p1
Solaris 8
Realize that this is probably not the current version of amanda
but it might represent an ongoing issue.
We haven't been backing up a particular partition, its relatively
large given the size of the tape drive (22 Gig used on a 32 Gig
partition, tape drive is a DLT 7000
Paul Bijnens wrote:
Paul Bijnens wrote:
It seems ethereal store only the first few bytes of each packet.
There is probably an option to set that size; similar to tcpdump -s
1500.
That means I don't have the full info, but I believe I've seen enough!
Following up on myself.
I've digged into the
Hi Eric,
I had a similar problem with several versions of gtar (1.13, 1.13.25 and
1.14) on Solaris 8. By running the gtar command used by amanda
interactively with the -v flag, I found that gtar was SEGV-ing on a
specific user directory. When I added that directory to the amanda
exclude file,
Hi, Paul,
on Dienstag, 15. Juni 2004 at 16:49 you wrote to amanda-users:
PB And amanda cleans up the other two connections.
PB Amanda tries again with another set of ports a few times
PB but always trying to connect to 65535 for the index.
PB Then she gives up completely.
I also noticed the
Stefan G. Weichinger wrote:
Hi, Paul,
on Dienstag, 15. Juni 2004 at 16:49 you wrote to amanda-users:
PB And amanda cleans up the other two connections.
PB Amanda tries again with another set of ports a few times
PB but always trying to connect to 65535 for the index.
PB Then she gives up
Paul Bijnens wrote:
Just for fun: if you disable the indexing, then the backup will run
fine, I believe. (index no in dumptype).
Well, no it doesn't work that way either.
/Andreas
Hi, Andreas,
on Dienstag, 15. Juni 2004 at 21:56 you wrote to amanda-users:
Where could that one reside? A faulty network-module? Remember that
these things work fine here with each 2.6 ..
AS I'm almost sure it's some kind of kernel bug. That's why I have bothered
AS to narrow down on wich
Very very strange...
Do you have netcat installed?
What is the output of this command on 2.6.6rc2?
nc -v -v -s 127.0.0.1 -p 1234 127.0.0.1 1234
--
Paul Bijnens, XplanationTel +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512
unsubscribe [EMAIL PROTECTED]
--
Fernando Serto
Systems Administrator
Memetrics Pty.
Phone: +61 2 95560833
Fax: +61 2 95556911
Mobile: 0403 338 005
E-mail: [EMAIL PROTECTED]
---
Certain disclaimers and policies apply to all email sent from Memetrics.
For the full text of these disclaimers and
Paul Bijnens wrote:
Very very strange...
Do you have netcat installed?
What is the output of this command on 2.6.6rc2?
nc -v -v -s 127.0.0.1 -p 1234 127.0.0.1 1234
[EMAIL PROTECTED]:/tmp/amanda$ nc -v -v -s 127.0.0.1 -p 1234 127.0.0.1 1234
localhost [127.0.0.1] 1234 (?) open
/Andreas
20 matches
Mail list logo
