:)....ok thanks. What was it related to exactly since I did so many things to test that problem. was not sure it was a bug.
On Tue, Feb 3, 2009 at 4:18 PM, Nickolas Toursky <[email protected]> wrote: > > Arie, that was a bug which is now fixed. > Thanks for reporting. > > On Tue, Feb 3, 2009 at 4:01 PM, Arie Fishler <[email protected]> wrote: > > Well...issue solved here. Might have been a problem with the elastic IP > > accessing that machine and for some reason not identified right. > Otherwise > > don't know. I just "synchronized all" to the accessing server that has an > > Elastic IP assigned to it. > > > > On Tue, Feb 3, 2009 at 2:49 PM, Arie Fishler <[email protected]> wrote: > >> > >> I synchronized all on my mysqllvm role (on the master). The master > >> naturally did not restart. A new slave replaced the existing one. > >> > >> I changed the name of the role when synchronized. The security group for > >> that name was created correctly. > >> > >> Currently the master seems not to have a port open that was previously > >> open. Not when accessing via the public IP. It is replying on this port > >> through the private IP. > >> The slave (which has exactly the same setup) is setup correctly. > Listening > >> on the port with no problems (also on when accessing through the public > IP) > > > > > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
