Thanks Nickolas!
On Aug 13, 1:24 pm, Nickolas Toursky <[email protected]> wrote:
> Sam,
>
> 'Uptime' field shown as returned by AWS. It indicates, how long the
> instance is running. Rebooting does not reflect it.
>
> Nick
>
> 2009/8/13 Sam <[email protected]>:
>
>
>
> > Hi Nickolas,
>
> > I did restart the farm then rebooted.
> > Even now I just rebooted the instance.
> > On the instance view it is showing
> > 4music-master-1 (slave)
>
> > i-3c5b4c48 Running eu-west-1a 0 day, 01:08 79.125.40.88
>
> > There is no way to find whether reboot was successful. It does not
> > update uptime field.
> > I am not convinced that it rebooted at all.
>
> > On Aug 13, 1:11 pm, Nickolas Toursky <[email protected]> wrote:
> >> Sam,
>
> >> This instance was rebooted 25 minutes ago (07:45 as per instance timezone).
>
> >> Replication status error has nothing to do with reboot.
>
> >> Nick
>
> >> 2009/8/13 Sam <[email protected]>:
>
> >> > I need to reboot my MySQL slave instance to boot some functionality
> >> > within the farm 2213.
> >> > I tried to reboot the slave MySQL instance of the role 4music-
> >> > master-1.
> >> > I does nothing. I saw the logs and following is the only error I found
> >> > there:
> >> > "Scalr cannot connect to instance 79.125.40.88:3306 (i-3c5b4c48) and
> >> > check replication status. (Error (22):Invalid argument)"
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
