[Csync2] (Repost) Connect to host which is not configured any more

[Andreas J. Koenig]

Sorry if this comes as a duplicate, the first posting didn't make it.

-------------------- Start of forwarded message --------------------
(Sorry this is still under 1.33, I have not had time to upgrade yet)

I notice the following buggy behaviour. I once had a host in the pool
that was living on dyndns and only available every now and then. After
a short while we gave up to use csync2 because there were too many
troubles showing up. So we gave up the experiment and I removed that
other host from the configuration completely.

The bug I want to report now is that this host remains to haunt me.
It's in the database and I do not get rid of it with normal means. Or
am I missing something?


This is the command:

    /usr/sbin/csync2 -B -v -G somemaster_somedomain_org -N somemaster.somedomain.org  -cu

This is the config file:

    group somemaster_somedomain_org {
      host somemaster.somedomain.org;
      host (someotherslave.elsewhere.de);
      key /etc/csync2/somemaster_somedomain_org.key;
      include /home/ftp/pub/SOMEMASTER/authors;
      include /home/ftp/pub/SOMEMASTER/modules;
      include /home/ftp/pub/SOMEMASTER/scripts;
      auto left;
    }

And this is the output:

    Connecting to host someslave.dyndns.org (SSL) ...

After that it waits for some much too long timeout (~180 seconds)
before it gives up and then continues correctly.

Any solutions available?

Thanks,
-- 
andreas

-------------------- End of forwarded message --------------------