Hi, I've recently upgraded Scalr from 4.4 to 4.5. I've created a role that has scalarizr-ec2 v2.4.1 running on it and have been launching a test farm with this role in it. If I leave Scalr alone after launching the farm it sits in Initializing state until it times out. In my Scalr message sender log I can see these sorts of entries for the server that is launching:
*[05/Mar/2014 11:14:05][0.0.30][msg_sender][2167][139995350418896] ERROR Delivery failed, message:'eb052699-9395-4dc3-b779-d34d4887617a' error:'<type 'exceptions.Exception'> server:e775d281-59ad-4abf-9509-5fea59471a67 error:can't determine IP line: 274'* *[05/Mar/2014 11:31:33][0.0.30][msg_sender][5950][140567929726416] ERROR Delivery failed, message:'5219eb8c-f2ed-443d-aa0e-7db9616d9331' error:'<type 'exceptions.Exception'> server:e775d281-59ad-4abf-9509-5fea59471a67 error:can't determine IP line: 274'* If I go into the Scalr Internal Messaging for the server while it is launching I find it sat on the "out/HostInit" message or "out/HostUp" message having failed after three attempts. If for each of these messages I choose to resend them from the actions menu I end up with a complete launch of the server. Is there something I could have missed in the upgrade that would cause these messages to be sent automatically? As far as I'm aware I've got the required security groups in place on the EC2 side as this worked when it was on 4.4. I've got cron jobs and the required daemons set up as detailed in the wiki page for upgrading from 4.4 to 4.5. Is there anything else I should be running or something I've missed? Thanks, Mike -- You received this message because you are subscribed to the Google Groups "scalr-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
