Charles Curley schreef:
On Wed, Jun 21, 2006 at 02:06:28PM -0400, Jon LaBadie wrote:
On Wed, Jun 21, 2006 at 11:43:31AM -0600, Charles Curley wrote:
On Wed, Jun 21, 2006 at 12:51:45PM -0400, Jon LaBadie wrote:
runtar is called from other programs and they write debug info to
things like sendsize and sendbackup. Anything interesting there?
Nothing that jumps out. Here's a recent sendbackup:
--------------------------------------------------
sendbackup: debug 1 pid 7550 ruid 33 euid 33: start at Wed Jun 21 11:40:12 2006
/usr/lib/amanda/sendbackup: version 2.4.5p1
parsed request as: program `GNUTAR'
disk `/etc'
device `/etc'
level 0
since 1970:1:1:0:0:0
options `|;bsd-auth;compress-fast;index;'
sendbackup: try_socksize: send buffer size is 65536
sendbackup: time 0.001: stream_server: waiting for connection: 0.0.0.0.44983
sendbackup: time 0.001: stream_server: waiting for connection: 0.0.0.0.37243
sendbackup: time 0.001: stream_server: waiting for connection: 0.0.0.0.50509
sendbackup: time 0.001: waiting for connect on 44983, then 37243, then 50509
sendbackup: time 30.002: stream_accept: timeout after 30 seconds
sendbackup: time 30.002: timeout on data port 44983
sendbackup: time 60.000: stream_accept: timeout after 30 seconds
sendbackup: time 60.000: timeout on mesg port 37243
sendbackup: time 90.000: stream_accept: timeout after 30 seconds
sendbackup: time 90.001: timeout on index port 50509
sendbackup: time 90.001: pid 7550 finish time Wed Jun 21 11:41:42 2006
--------------------------------------------------
Uhhh, Nothing stands out? Nothing like trying to set up the 3 needed
connections and not connecting, but timing out instead?
Nothing other than the problem I've already asked about & to which
I've gotten no answer: Is the client trying to connect to
0.0.0.0.50509? And if so, where is that set up?
0.0.0.0 means the amandad process is listening on any interface
(not only 127.0.0.1 or not only 192.169.0.1 etc.).
The normal conversation for "sendbackup" goes like this:
The server sends a UDP packet "sendbackup" request, and the DLE that it
wants to do, together with some options used, e.g. if it wants indexes
generated too.
The client then prepares two or three tcp-connections: one for data, for
error messages (which also contains the "Total size" line), and, if
needed, a connections transferring the indexes.
The client responds with a UDP packet on which ports these TCP
connections will be listening.
The server then needs to connect to each of these ports on the client.
And there is seems to fail.
As you said, you are using iptables, so problably the the packets are
being blocked by iptables.
To solve:
1. Easiest: load iptables helper module ip_conntrack_amanda:
modprobe ip_conntrack_amanda
(which will inspect the conversation above and open those two or
three ports selectively as needed).
2. If you cannot use that module (e.g. because the firewall is not
iptables or not recent enough), recompile amanda with a restricted
portrange and open that range in the firewall.
Details can be found in:
http://wiki.zmanda.com/index.php/Configuration_with_iptables
--
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 *
***********************************************************************
|
