[Csync2] How Can I Troubleshoot Config Command Failed?

Lars Ellenberg lars.ellenberg at linbit.com
Mon Oct 10 13:35:44 CEST 2011


On Mon, Oct 10, 2011 at 01:31:27PM +0200, Lars Ellenberg wrote:
> On Sat, Oct 08, 2011 at 02:15:17PM -0400, Shalom Levytam wrote:
> > Just a quick update.  I've managed to get a sync to work by running
> > csync2 -ii -vvv on the remote.  however, if i attempt to run csync2 -i
> > -vvv I receive a "Can't set TCP_NODELAY option on TCP socket" error
> > message and am unable to make the connection.
> 
> 
> Don't do -vvv in inetd mode.
> csync2 -i only.
> 
> Keywords: csync2, centos6, xinetd, "Can't set TCP_NODELAY option on TCP socket".
> 
> Problem is, at least I think so, that xinetd starts csync2 with stderr
> on stdout, and csync2 with -v logs warnings to stderr, which is stdout,
> and gets connected to the reply channel of the invoking csync2, which
> again thinks that's some weird protocol error, and closes the
> connection.
> 
> > Can anyone help with this?
> 
> Does it work with "csync2 -i", without any -v?

Oh. Of course you could try to use syslog instead as well:
  csync2 -i -l -vvv

> > slevytam
> > 
> > On 2011-10-08, at 1:20 PM, Shalom Levytam wrote:
> > 
> > > Hi,
> > > 
> > > I have been really struggling to get a simple implementation of
> > > csync working and would really appreciate some assistance.  I'm
> > > getting a Config command failed. and have no idea how to
> > > troubleshoot the problem.  
> > > 
> > > If someone could be please help, I'd be very thankful.
> > > 
> > > slevytam
> > > 
> > > 
> > > 
> > > 
> > > Output from csync2 -xvvv
> > > ...
> > > Connecting to host mail.the10thfloor.com (PLAIN) ...
> > > Local> CONFIG \n
> > > Peer> 
> > > ERROR from peer mail.the10thfloor.com: Connection closed.
> > > Config command failed.
> > > 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.
> > > Finished with 2 errors.
> > > 
> > > iptables -L for both systems
> > > ACCEPT     tcp  --  anywhere             anywhere            state NEW tcp dpt:csync2
> > > 
> > > [root at www1 csync2]# uname -n
> > > www1.the10thfloor.com
> > > 
> > > [root at mail csync2]# uname -n
> > > mail.the10thfloor.com
> > > 
> > > csync2.cfg for both hosts
> > > 
> > >> nossl * *;
> > >> group mygroup
> > >> {
> > >>      host www1.the10thfloor.com;
> > >>      host mail.the10thfloor.com;
> > >>      key /etc/csync2/mygroup.key;
> > >>      include /home/the10thfloor/test/;
> > >>      exclude *~ .*;
> > >>      auto none;
> > >> }
> > > 
> > > same key used for both systems: /etc/csync2/mygroup.key
> > > _______________________________________________
> > > Csync2 mailing list
> > > Csync2 at lists.linbit.com
> > > http://lists.linbit.com/mailman/listinfo/csync2
> > 
> 
> > _______________________________________________
> > Csync2 mailing list
> > Csync2 at lists.linbit.com
> > http://lists.linbit.com/mailman/listinfo/csync2
> 
> 
> -- 
> : Lars Ellenberg
> : LINBIT | Your Way to High Availability
> : DRBD/HA support and consulting http://www.linbit.com
> 
> DRBD® and LINBIT® are registered trademarks of LINBIT, Austria.
> _______________________________________________
> Csync2 mailing list
> Csync2 at lists.linbit.com
> http://lists.linbit.com/mailman/listinfo/csync2

-- 
: Lars Ellenberg
: LINBIT | Your Way to High Availability
: DRBD/HA support and consulting http://www.linbit.com

DRBD® and LINBIT® are registered trademarks of LINBIT, Austria.


More information about the Csync2 mailing list