Unable to Create Cluster

I am creating my cluster, between my two servers.

I am mainly getting this error:

2016-10-25 12:12:15 . Starte [rsync --delete -av --exclude-from=/etc/mobydick/clustersync.blacklist -a /mnt/SHARE_SNAP/ rsync://10.87.36.172/SHARE]
@ERROR: access denied to SHARE from unknown (10.87.36.171)
rsync error: error starting client-server protocol (code 5) at main.c(1534) [sender=3.0.9]
2016-10-25 12:12:25 . Exit: [5]
2016-10-25 12:12:25 Could not complete filesystem synchronisation
2016-10-25 12:12:25 . Starte [ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null root@10.87.36.172 mount -o remount /TARGET/SHARE 2>/dev/null]
2016-10-25 12:12:35 . Exit: [0]
2016-10-25 12:12:35 Unmount SHARE_SNAP
2016-10-25 12:12:35 Remove SHARE_SNAP
2016-10-25 12:12:35 Finished with errors

The processes in the log there, seems to go along, then run into the above. I don’t think I missed any steps on the set up. I added the key from Master to slave. This was the configuring the cluster, after added the slave on the master. I am unable to access the web GUI now, even without the cluster to check things I may have missed.

Would that issue relate to the key saying root@SYSTEM and it should be something else? Just a thought.

Sorry, but I noticed this in my logs on Secondary:

ct 25 17:41:13 localhost nrpe[11310]: Host 10.87.36.171 is not allowed to talk to us!
Oct 25 17:42:13 localhost nrpe[11459]: Host 10.87.36.171 is not allowed to talk to us!
Oct 25 17:43:47 localhost nrpe[11621]: Host 10.87.36.171 is not allowed to talk to us!
Oct 25 16:49:48 localhost icinga: Warning: A system time change of 0d 0h 54m 20s (backwards in time) has been detected. Compensating…
Oct 25 16:50:00 localhost nrpe[11692]: Host 10.87.36.171 is not allowed to talk to us!
Oct 25 16:50:24 localhost nrpe[11720]: Host 10.87.36.171 is not allowed to talk to us!
Oct 25 16:50:40 localhost /USR/SBIN/CRON[11727]: (root) CMD (/var/rrd/mobydickrrd 1>/dev/null 2>&1)
Oct 25 16:50:48 localhost nrpe[11734]: Host 10.87.36.171 is not allowed to talk to us!
Oct 25 16:51:24 localhost nrpe[11764]: Host 10.87.36.171 is not allowed to talk to us!
Oct 25 16:51:38 localhost nrpe[11778]: Host 10.87.36.171 is not allowed to talk to us!
Oct 25 16:51:49 localhost icinga: SERVICE ALERT: DU-PBX2;time;OK;HARD;4;NTP OK: Offset 0.0002448558807 secs
Oct 25 16:51:49 localhost icinga: SERVICE NOTIFICATION: admin;DU-PBX2;time;OK;notify-service-by-email;NTP OK: Offset 0.0002448558807 secs
Oct 25 16:52:53 localhost nrpe[11886]: Host 10.87.36.171 is not allowed to talk to us!

This shows up in my Primary:

Oct 25 16:45:34 localhost icinga: SERVICE ALERT: DU-PBX2;firmware sync;CRITICAL;SOFT;3;CHECK_NRPE: Error - Could not complete SSL handshake.
Oct 25 16:45:34 localhost icinga: SERVICE ALERT: DU-PBX2;disk usage;CRITICAL;HARD;4;CHECK_NRPE: Error - Could not complete SSL handshake.
Oct 25 16:45:34 localhost icinga: SERVICE NOTIFICATION: admin;DU-PBX2;disk usage;CRITICAL;notify-service-by-email;CHECK_NRPE: Error - Could not complete SSL handshake.
Oct 25 16:45:44 localhost icinga: SERVICE ALERT: DU-PBX2;load;CRITICAL;SOFT;3;CHECK_NRPE: Error - Could not complete SSL handshake.
Oct 25 16:45:54 localhost icinga: SERVICE ALERT: DU-PBX2;filesystem sync;CRITICAL;HARD;4;CHECK_NRPE: Error - Could not complete SSL handshake.
Oct 25 16:45:54 localhost icinga: SERVICE NOTIFICATION: admin;DU-PBX2;filesystem sync;CRITICAL;notify-service-by-email;CHECK_NRPE: Error - Could not complete SSL handshake.
Oct 25 16:45:54 localhost icinga: SERVICE ALERT: DU-PBX2;time;CRITICAL;SOFT;2;CHECK_NRPE: Error - Could not complete SSL handshake.
Oct 25 16:46:34 localhost icinga: SERVICE ALERT: DU-PBX2;firmware sync;CRITICAL;HARD;4;CHECK_NRPE: Error - Could not complete SSL handshake.
Oct 25 16:46:34 localhost icinga: SERVICE NOTIFICATION: admin;DU-PBX2;firmware sync;CRITICAL;notify-service-by-email;CHECK_NRPE: Error - Could not complete SSL handshake.
Oct 25 16:46:44 localhost icinga: SERVICE ALERT: DU-PBX2;load;CRITICAL;HARD;4;CHECK_NRPE: Error - Could not complete SSL handshake.
Oct 25 16:46:44 localhost icinga: SERVICE NOTIFICATION: admin;DU-PBX2;load;CRITICAL;notify-service-by-email;CHECK_NRPE: Error - Could not complete SSL handshake.
Oct 25 16:46:54 localhost icinga: SERVICE ALERT: DU-PBX2;time;CRITICAL;SOFT;3;CHECK_NRPE: Error - Could not complete SSL handshake.
Oct 25 16:47:54 localhost icinga: SERVICE ALERT: DU-PBX2;time;CRITICAL;HARD;4;CHECK_NRPE: Error - Could not complete SSL handshake.
Oct 25 16:47:54 localhost icinga: SERVICE NOTIFICATION: admin;DU-PBX2;time;CRITICAL;notify-service-by-email;CHECK_NRPE: Error - Could not complete SSL handshake.
Oct 25 16:49:21 localhost cib: [2930]: info: cib_stats: Processed 9 operations (0.00us average, 0% utilization) in the last 10min
Oct 25 16:50:01 localhost /USR/SBIN/CRON[7599]: (root) CMD (/var/rrd/mobydickrrd 1>/dev/null 2>&1)
Oct 25 16:55:01 localhost /USR/SBIN/CRON[8420]: (root) CMD (/var/rrd/mobydickrrd 1>/dev/null 2>&1)

Hi,

do you get this error on the first initial sync (when you try adding the secondary node)? Or could you already add the secondary node and a later re-sync failed?
A possible cause could be a IP conflict on 10.87.36.171 or some firewall issue. Beware that the nodes private interfaces MUST be connected DIRECTLY without any switch/router in between.

Regards,
Thomas

Yes, I had the eth3, heartbeat connection, directly connected with a crossover cable. My cluster seems to not sync occasionally when I have to rebuild it. It just seems to hang. I have had it just resync after a while. And last week, I had to rebuild the cluster again (due to something else) and it just stayed un-synced. SO I readded the slave again, and it came right up. Every time I have had a solid ping going from server to server via the 192.168.100.2/3 to ensure the connectivity but I still got the cannot connect to the server. Very odd. So I was fully aware of the direct connection, and currently have two ethernet ports configured: one management and one heartbeat.