If you mean "Synchronize to all", instances are getting replaced (Scalr starting instance of a new AMI and then terminates an old one), not restarted. When you do synchronize on mysql instance, master keeps running and slaves get replaced. And it may take some time for slaves to download latest database snapshot before mysql is started - may be that's why you were seeing it not running? Event log is a first place to check in such cases.
On Dec 30, 11:28 pm, Robert <[email protected]> wrote: > After posting this I moved my initialization script from onHostInit to > onHostUp and onRebootComplete, because I read the description of when > the event fires a bit more closely - "Instace booted up, Scalr > environment not configured and services not initialized yet." - and > that seems too early in the process. > > But I don't think that really solves the mystery. I started looking > into this after doing a synchronization and discovering that MySQL > wasn't running after the server came back up. I start MySQL in my > initialization script. It started correctly when I terminated and re- > launched the instance. My suspicion is that my initialization script > was not run when the instance was restarted after the > synchronization. Shouldn't an onHostInit script always be run when an > instance is started, whether it's a result of a reboot, or an explicit > launch, or a synchronization, or scaling up that role? Does the > launch sequence vary based on the type of launch? > > On Dec 30, 1:03 pm, Alex Kovalyov <[email protected]> wrote: > > > "No scripts to execute on event 'hostInit" can mean not only scripts on this > > particular instance but also covers events on other instances ( Scalr allows > > you to execute script on entire farm or a role upon event on some particular > > instance). > > We'll correct a message text so it can be distinguished. > > > You have all scripts assigned on HostUp and they are being executed, > > according to Scripting log. > > > Please provide more info to [email protected] if we're missing something. > > > Alex > > > On 29.12.08 21:49, "Robert" <[email protected]> wrote: > > > > So far I'm seeing two problems with my instance after running a > > > synchronize to all: > > > > 1. My instance console says that it's not running my hostInit script: > > > > INFO: Host 10.254.110.131/app initialized. Awaiting authentication > > > data. > > > DEBUG: No scripts to execute on event 'hostInit'. > > > > 2. My EBS is mounted at the old mount point that I had originally set > > > up yesterday or the day before (/mnt/ebs) instead of where it should > > > be (/mnt/ebs/www). The contents of the EBS looks correct. > > > > After terminating and re-launching the farm, the EBS is mounted at the > > > correct mount point and the hostInit script has been run. The only > > > thing that the hostInit script is doing currently is to start MySQL. > > > > My guess is that there's a bug in how synchronize to all starts an > > > instance, and maybe also how it shuts one down? > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
