Hi Helpers,
as you can see, I am currently backing up just one client using gnutar.
Now, having one tapecycle run, suddenly 3 of 14 mountpoints on the same machine failed
for reasons I don't get.
The mail from today, report from the night 25.-26.
---cut-on---
...
machine /some/mountpoint_1 lev 1 FAILED [could not connect to machine]
machine /some/mountpoint_2 lev 1 FAILED [could not connect to machine]
machine /some/mountpoint_3 lev 1 FAILED [could not connect to machine]
STATISTICS:
...
DUMP SUMMARY:
DUMPER STATS TAPER STATS
HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
-------------------------- --------------------------------- ------------
...
machine -mountpoint_8 0 880720 352416 40.0 5:411033.4 7:03 833.0
machine -mountpoint_9 FAILED ---------------------------------------
machine -mountpoint_A FAILED ---------------------------------------
machine -mountpoint_B 1 10 32 320.0 0:00 589.5 0:02 36.8
machine -mountpoint_C FAILED ---------------------------------------
machine -mountpoint_D 1 679990 78272 11.5 1:061188.4 1:30 865.6
...
(brought to you by Amanda version 2.4.2p2)
---cut-off---
On the client-machine in /tmp/amanda I found no information leading to errors at
sendsize.20020126004755.debug, nor at runtar.20020126???????.debug but at
amandad.20020126004937.debug:
---cut-on---
...
got packet:
--------
Amanda 2.4 REQ HANDLE 000-90B80708 SEQ 1012002305
...
sending ack:
----
Amanda 2.4 ACK HANDLE 000-90B80708 SEQ 1012002305
...
amandad: got packet:
----
Amanda 2.4 REQ HANDLE 000-78BA0708 SEQ 1012002304
amandad: received other packet, NAKing it
addr: peer 192.168.1.15 dup 192.168.1.15, port: peer 854 dup 855
sending nack:
----
Amanda 2.4 NAK HANDLE 000-78BA0708 SEQ 1012002304
ERROR amandad busy
----
... ... ...
---cut-off---
Why is amandad still busy? Or why ist the backup-server requesting a former sequenz?
adTHANXvance
Sascha
