search

zynesis / lsyncd-aws-autoscaling

Lsyncd auto configuration that works with Amazon Web Services (AWS) Auto Scaling
MIT License
17 stars 5 forks source link

Not syncing to multiple instances #4

Open Brettk80 opened 11 years ago

Brettk80 commented 11 years ago

Any known reason why syncing would happen to on instance in a LB group and not another? I've tested shh from the master to the box using the pub key setup and it works. Same directory structure, etc.

I have: Master Slave1 Slave2 - created from AMI image of Slave 1

Slave 1 updates, Slave 2 doesnt. They are all in the same LB group; though autoscaling hasnt been configured. Looking at the source though, it doesnt look like it matters that we're not using AutoScaling yet in the test environment.

Any pointers?

The slaves file seems to have multiple instances lists which are true:

a:2:{i:0;s:10:"i-847edbb3";i:1;s:10:"i-4d33ec79";}

Brettk80 commented 11 years ago

I've also trying running lsyncd manually to the additional instance and it works fine.

uzyn commented 11 years ago

Yes all it checks is LoadBalancing group and not AutoScaling.

You may wish to look into the log for lsyncd to see why it fails.

Brettk80 commented 11 years ago

There's an issue with lsyncd-2.1.5 and the rsyncOpts = {"-p", "-e", "ssh -i {{lsyncd.ssh_private_key}} -o StrictHostKeyChecking=no"} line in lsyncd.conf.lua

The syntax has changed.