Hi Akshay, This error means that Scalr wasn't able to contact the instance started out of the created AMI. Check that /etc/rc.local still contains Scalr scripts calls, snmpd/snmptrapd is installed and working, curl installed, whatever else may affect communication.
Regards, Nick On Jan 7, 8:41 pm, Akshay Rao <[email protected]> wrote: > Tried to synchronize my instance. I waited for a while but the process hung > on "Synchronizing... (Abort)" status. Bundle log said everything finished > perfectly. I couldn't create an instance of it in a farm however. This > happened to 2 of my roles: tomcat and mysqllvm64. I decided to abort the > tomcat role since it looked complete (wanted to see what would happen). I > got the error "Rebundle complete, but the rebundled AMI is not operable by > Scalr. ". I am going to try and re-synchronize but I have my doubts that > this will work. > > Is this happening to anyone else? This is on* scalr.net* *not* on the open > source version. > > Akshay
-- You received this message because you are subscribed to the Google Groups "scalr-discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/scalr-discuss?hl=en.
