TIPS rsync issue with xivo HA

[rjm]

Final step in setting up Xivo HA having an rsync issue. After turning on tun and getting Features.ini set up, I proceeded to:

Next, return to the Linux CLI of Master while still logged in as root. (1) Set up file synchronization by running this script: xivo-sync -i. (2) Start configuration synchronization by running: xivo-master-slave-db-replication 192.168.1.2 using the actual IP address of your Slave. (3) Finally, synchronize the two servers by running xivo-sync on Master.

Only I get this:



I am also seeing this in the HA configuration section of Xivo:



Anyone have any thoughts on what is going on here?

 

[wardmundy]

Looks like your passwords didn't sync up. Did you follow ALL of the steps?? Try setting them both back to normal server mode and start over.

 

[rjm]

Ok. I thought I did at this point. But I'll start over. Thanks.

 

[rjm]

Now I am absolutely sure of two thing. 1. I missed a reboot step. 2. I haven't skipped a step. Still getting this:


Just to be clear, I set both boxes back to default no HA. Restarted both boxes with xivo-service restart. Checked my ip address configurations for neorouter. Redid the HA configuration. Pointed back to the remote box for each. Tried to sync up.

Everything looked good until I tried the last step, xivo-sync which is where it bombs out. Is there a step somewhere to create rsync credentials? I don't see it here: http://nerdvittles.com/?p=19350

Looking further, I see that xivo-sync -i did not work past the first time. I think I need to restart somehow. When I run it, I get:

SSH key /root/.ssh/xivo_id_rsa already exist

Checking the help, it doesn't seem that there is an uninstall or remove.

UPDATE: So xivo-sync -i will not replace existing keys if you have them. You are going to have to go in and manually remove them. I moved the private and public keys stored under the /root/.ssh directory on the Master. Then ran xivo-sync -i again. I was prompted for a password on the Slave. Viola! Ran xivo-sync and all is good. Miller time.

Thank you Ward for ALL your help! Thank you! Thank you! Thank you!

 

[wardmundy]

You probably need to delete the existing key. You reinstalled the software, remember?

 

[rjm]

Exactly. I was probably editing the prior post while you were typing. Thanks again Ward. I am newer to Linux. Better than I was, but with a long way to go.

 

[wardmundy]

Then you have to start over. Be sure to try the step to log into the other NeoRouter server with SSH. You should be able to get in without entering a password if you completed the initial steps correctly.

 

[rjm]

xivo-sync works correctly without a password. I do need one for ssh. Are my keys still gonzo?

 

[rjm]

I repeated it. Deleting the keys, reinstalling them. I was asked for a password to ssh, but xivo-sync works and is successful but does not ask for a password. Are you sure I need to start over?

 

[wardmundy]

If it syncs you're good to go.

 

[rjm]

Cool! Thanks!!! She is syncing like a champ.

EDIT: I then asked if the status below, which is different from the howto, is correct for the slave. I mistakenly included the ip address so I reuploaded it here.

 

[wardmundy]

No idea. Shut down master gracefully with halt and see what happens.

 

[rjm]

Ok. If you are following along, stopping the xivo service did not appear to start the slave server and transfer traffic. Halting debian did, at least going by the pbxstatus lights.

Oh, and btw if you are curious, restarting the master appeared to shut down the slave almost immediately.

I am only wondering if there is a notice feature, like an email or something that the master is down...

Now I have more confidence in the most important feature to me, HA, time to set up everything else. Thanks again Ward.

 

[wardmundy]

If Asterisk crashes on the master, the slave will not kick in. It takes a network failure on master to trigger the slave. Unlike on some other platforms, I have never seen Asterisk individually fail with XiVO so this shouldn't be a problem. Notification is not provided unless you set up a script to ping master and notify you when it fails.

 

[rjm]

It sounds like all I need to do is set up a ping monitor? Or should I set up a website monitor as well?