[Csync2] No transfer?
Lars Ellenberg
lars.ellenberg at linbit.com
Fri Sep 28 21:07:38 CEST 2007
On Fri, Sep 28, 2007 at 07:33:09PM +0200, Jordi Prats wrote:
> This also happens to me. This project seems dead because no one is in
> this list...
not exactly dead.
there are ~100 people on this list.
if you get no answers, then either no one cares, or no one knows what
you are asking, or no one found time yet to do your homework for you.
csync2 is a good tool for its intended purpose,
it may even be a good tool for some not initially intended uses.
normally it just works, as long as you use it as intended,
at least in the latest revision, to the best of my knowledge.
if it does not, you can run it in "debug" mode,
and try to figure what happens.
first, make sure you get some tcp connection.
e.g. use netcat.
after making sure the inetd does not listen on the csync2 port,
and assuming your nodes are named "pinky" and "brain":
brain# nc -q1 -l -p csync2 # or nc -q1 -l -p 30865, for that matter
pinky# echo blub | nc -q1 brain csync2
and vice versa.
now, if there now is no blub on brain, you are out of luck,
and need to fix network connectivity (firewalls? routing?)
if there is, go ahead.
next, make sure your node names do resolve,
and resolve to the exact same ip adresses
as the incoming connection seem to come from.
why? incoming connection from pinky to brain:
brain: hi, whos there?
pinky: it's me, pinky!
(brain and does a forward lookup of "pinky",
and verifies that it gets the same ip as the incoming connection
comes from. if they do not match, it is assumed that this is some
spoofing attempt).
next, debug run using csync2, single shot:
brain# csync2 -iii -vvv 2>&1 | tee csync2.debug.$HOSTNAME.log
pinky# csync2 -vvv -T 2>&1 | tee csync2.debug.$HOSTNAME.log
now, there are lots of cryptic things in there,
but some of the messages are plain english,
which should help to figure out what is going on.
hint: for debugging connection problems,
start with a very short config.
> Jordi
>
> Marcus Bointon wrote:
> >On 26 Sep 2007, at 10:39, Marcus Bointon wrote:
> >
> >>Connecting to host www2 (SSL) ...
you know, there is also tcpdump, tshark, wireshark...
if it works plain text,
but does not make any network traffic progress using ssl,
maybe you don't have any entropy left on that box?
(cat /proc/sys/kernel/random/entropy_avail)
> >Can someone please post an example log of what they normally get after
> >this?
well.
depending on the log level,
it looks for example like this:
# csync2 -Tv
Running in-sync check for aug-x <-> nudl-x.
Connecting to host nudl-x (SSL) ...
Finished with 0 errors.
hope that helps.
cheers,
--
: Lars Ellenberg http://www.linbit.com :
: DRBD/HA support and consulting sales at linbit.com :
: LINBIT Information Technologies GmbH Tel +43-1-8178292-0 :
: Vivenotgasse 48, A-1120 Vienna/Europe Fax +43-1-8178292-82 :
__
please use the "List-Reply" function of your email client.
More information about the Csync2
mailing list