On Wed, Sep 05, 2012 at 02:27:16PM +0200, Nils Stöckmann wrote:
> Hi!
>
> I have problems running csync2-1.34 on a second NIC.
>
> First of all, I have it running via xinted:
>
> netstat -vaept | grep -e csync
> Proto Recv-Q Send-Q Local Address Foreign Address
> State User Inode PID/Pro
> tcp 0 0 *:csync2 *:*
> LISTEN root 8150 853/xinetd
>
> Connecting WORKSif I leave out the connection identifier in csync2.cfg.
> Connection works too, if I change the /etc/hosts file in a way, that the
> host names are ....-eth1. In this case, however, i have severe problems
> with other services and also csync2 produces a identification error,
> most probably because the certificates are not given out to
> "<hostname>-eth1".
>
> /etc/csync2.cfg:
> > nossl leihnix*h* leihnix*h*;
> >
> > group cfg_sync-etc {
> > host leihnix6h1@leihnix6h1-eth1;
> > host leihnix5h1@leihnix5h1-eth1;
> > key /etc/csync2/cfg_sync-etc.key;
> >
> >
> > include /etc/;
> >
> > exclude /etc/.hg/;
> > (........long list.....)
> > exclude *.cache;
> > exclude *.log;
> >
> >
> > auto younger;
> >
> > backup-directory /mnt/backup/csync2/cfg_sync-etc/;
> > backup-generations 4;
> > }
>
> ifconfig:
> > root@leihnix6h1:/etc# ifconfig | grep -e \\.1 -e eth
> > eth0 Link encap:Ethernet HWaddr 00:0c:6e:ff:a2:7b
> > inet addr:192.168.1.16 Bcast:0.0.0.0 Mask:255.255.255.0
> > eth1 Link encap:Ethernet HWaddr 00:80:c8:f6:c5:33
> > inet addr:172.31.1.16 Bcast:0.0.0.0 Mask:255.255.255.0
> > eth0 Link encap:Ethernet HWaddr 00:25:22:db:e7:84
> > inet addr:192.168.1.11 Bcast:0.0.0.0 Mask:255.255.255.0
> > eth1 Link encap:Ethernet HWaddr 00:80:c8:f6:c5:31
> > inet addr:172.31.1.11 Bcast:0.0.0.0 Mask:255.255.255.0
>
> hosts file: (identical on both; Same result if i leave out the private
> 172.31.1.0/24 IPs.)
> --------------------
> 172.31.1.16 leihnix6h1
> 172.31.1.11 leihnix5h1
> 127.0.0.1 localhost
> 192.168.1.11 leihnix5h1
> 192.168.1.16 leihnix6h1
> ----------------------
>
>
> Csync2 produces the following error:
> > SQL: SELECT peername FROM dirty GROUP BY peername ORDER BY random()
> > SQL Query finished.
> > SQL: SELECT filename, myname, force FROM dirty WHERE peername =
> > 'leihnix5h1-eth1' ORDER by filename ASC
> > SQL Query finished.
> > Connecting to host leihnix5h1-eth1 (PLAIN) ...
> > Can't resolve peername.
See that?
> > ERROR: Connection to remote host failed.
> > Host stays in dirty state. Try again later...
> > SQL: SELECT command, logfile FROM action GROUP BY command, logfile
> > SQL Query finished.
> > SQL: COMMIT TRANSACTION
> > Finished with 1 errors.
> > root@leihnix6h1:/etc#
>
>
> Why doesn't the way described in the csync2 paper work?
Because it cannot resolve the peername.
nothing in the system can resolve what you mean by leihnix5h1-eth1,
it is not in the hosts file, it is not in dns, the resolver cannot
find an IP address to that name... it simply does not know where to
connect to.
That's what "Can't resolve" means.
> It'd be really nice if some of you could help me out here.
would
172.31.1.16 leihnix6h1 leihnix6h1-eth1
172.31.1.11 leihnix5h1 leihnix5h1-eth1
work for you?
--
: Lars Ellenberg
: LINBIT | Your Way to High Availability
: DRBD/HA support and consulting http://www.linbit.com
_______________________________________________
Csync2 mailing list
Csync2@lists.linbit.com
http://lists.linbit.com/mailman/listinfo/csync2
