I finally setup csync2 on debian - its nice! Its a simple sort of configuration tool that I need for now.
I followed this guide for setting up csync2 on redhat, and then read the debian readme, which included instructions for creating keys:
csync2 for Debian----------------- You need to create an SSL certificate for the local Csync2 server. You can create a certificate using the following commands: openssl genrsa -out /etc/csync2_ssl_key.pem 1024 openssl req -new -key /etc/csync2_ssl_key.pem -out /etc/csync2_ssl_cert.csr openssl x509 -req -days 600 -in /etc/csync2_ssl_cert.csr \ -signkey /etc/csync2_ssl_key.pem -out /etc/csync2_ssl_cert.pem
Then I also had to use the command “csync2 -k /etc/csync2_ssl_cert.key”.
I didn’t have to do anything with openbsd.inetd other than restart it, and I’m not sure if that was even necessary. I initially typed in a peer’s hostname wrong, so I had to remove the sqlite db in /var/lib/csync2/.
I’ve only done one test but I like it so far! Hopefully I can use this to alleviate my current dependency on subversion for configuration files.
UPDATE: I do have to restart openbsd-inetd to get csync2 to work right.
More notes: * hostnames are tricky - the names in the /etc/csync2.cfg file need to be the same as the /etc/hostname for each member of the cluster. * I’m finding it easier to go server by server, using non-volatile files, and I’m including /etc/csync2.cfg in the list of files to sync so I can update them later