Moliere Christian wrote:
Here it is log of strace with gtar process :
write(1, "./bac2002/www/corr/arbo/gabarits"..., 57) = 57
write(1, "./bac2002/www/corr/arbo/gabarits"..., 60) = 60
write(1, "./bac2002/www/corr/arbo/gabarits"..., 58) = 58
read(0, "tmargin=\"0\" topmargin=\"0\" margin"..., 10240) = 8192
read(0, "r: #000099;}\nA.BACK {text-decora"..., 2048) = 2048
write(1, "./bac2002/www/corr/arbo/gabarits"..., 64
it is blocked like that
It seems to be blocked while writing to the index process (fd 1).
Have a look in /tmp/amanda.datestamp.debug and near the end
of the file, there is something like:
sendbackup: time 0.160: started index creator: "tar -tf - 2>/dev/null |
sed -e 's/^\.//'"
Is there an error message in the neighborhood?
Now we have to find out if that pipe is still working as it should.
Is the tar and sed running?
Sed writes it's output over a tcp socket to the server.
There, dumper accepts the connection, and continues the pipe with a
gzip, which writes it into the (temporary) indexfile.
Somewhere along that pipe, there is something blocking...
With strace etc, try to find for each process where it is blocking
(start at the end: gzip that writes into the temporary indexfile).
To see the index written over the network, you can tcpdump traffic
between that host and client using port that you find
/tmp/sendbackup.datestamp.debug near the beginning:
sendbackup: try_socksize: send buffer size is 65536
sendbackup: time 0.001: stream_server: waiting for connection: 0.0.0.0.4840
sendbackup: time 0.001: stream_server: waiting for connection: 0.0.0.0.4841
sendbackup: time 0.001: stream_server: waiting for connection: 0.0.0.0.4842
sendbackup: time 0.002: waiting for connect on 4840, then 4841, then 4842
sendbackup: time 0.018: stream_accept: connection from 192.168.200.45.4843
sendbackup: time 0.019: stream_accept: connection from 192.168.200.45.4844
sendbackup: time 0.019: stream_accept: connection from 192.168.200.45.4845
sendbackup: time 0.019: got all connections
The third connection is the port that sends the index to the server.
In this case port 4845.
with tcpdump, the syntax becomes:
tcpdump host yourhost and host yourclient and port 4845
--
Paul Bijnens, Xplanation Tel +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUM Fax +32 16 397.512
http://www.xplanation.com/ email: Paul.Bijnens AT xplanation DOT com
***********************************************************************
* I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, *
* quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, *
* stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, *
* PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, *
* kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... *
* ... "Are you sure?" ... YES ... Phew ... I'm out *
***********************************************************************
|
