Yeah I think adding a documentation would be great. I spent a lot of
time figuring out the config file syntax, right options to use, etc..
I don't know what the process is for contributing to csync2. I hope
someone can help you with that.
Thanks!
--Michi
On Mon, Oct 22, 2012 at 1:13 PM, Vadim Comanescu <vadim...@gmail.com> wrote:
> Hi Michi,
> Thank you very much for your prompt reply. Indeed this solved my problem.
> Some small changes like starting the server in stand-alone mode as i am on
> solaris and it works better, and to figure out how to trigger the update.
> From node1 csync2 -xv -N node1 just works as i expected.
> Maybe I could contribute somehow to the documentation for such a setup, as I
> consider it to be a very common when one would use a private network for the
> heartbeat in a cluster. Don't really see a way to do that.
>
> Thanks again, really appreciate it.
> Vadim
>
> On Oct 22, 2012, at 10:34 PM, Michi Mutsuzaki wrote:
>
>> Hi Vadim,
>>
>> You can use IP addresses instead of hostnames in the config file. I
>> have a config file that looks like this:
>>
>> group mycluster
>> {
>> host node1@10.34.109.122;
>> host node2@10.34.95.104;
>> host node3@10.34.92.114;
>> key /etc/csync2.key_mycluster;
>> include /mycluster;
>> }
>>
>> Note that node{1,2,3} are not DNS hostnames, but arbitrary names that
>> just need to be unique within the cluster. Then, you need to start the
>> servers using -N option:
>>
>> $ csync2 -i -N node1 # on 10.34.109.122
>> $ csync2 -i -N node2 # on 10.34.95.104
>> $ csync2 -i -N node3 # on 10.34.92.114
>>
>> Let me know if this solves your problem.
>>
>> Thanks!
>> --Michi
>>
>> On Mon, Oct 22, 2012 at 11:33 AM, Vadim Comanescu <vadim...@gmail.com> wrote:
>>> Hello,
>>>
>>> I managed to compile and install csync2-1.34 on solaris for my latest
>>> project for synchronizing files in a heartbeat/pacemaker cluster.
>>> Now i'm faced with a very interesting situation, where the hostnames that
>>> need to be synchronized are not resolved by dns since the communication
>>> between them is done through a separate network dedicated for the
>>> heartbeat. The problem I have that each time a node would join the cluster
>>> i would have to modify the hosts file on each node of the cluster so that
>>> csync2 would be able to propagate the changed files to the new node.
>>> I would like to know what would be the main reason that all the definitions
>>> of a host in the cfg file are made using its hostname and not the host's
>>> IP? Would it be possible for it to use the IP's?
>>>
>>> Vadim
>>> _______________________________________________
>>> Csync2 mailing list
>>> Csync2@lists.linbit.com
>>> http://lists.linbit.com/mailman/listinfo/csync2
>
_______________________________________________
Csync2 mailing list
Csync2@lists.linbit.com
http://lists.linbit.com/mailman/listinfo/csync2
