Hi ! I am still looking for a way to solve/mitigate the issue when it is happening. I Used to terminate the instance to solve the issue (as it blocks the scaling) but it seems a reboot solve it. So it is probably a mater of restarting a good service but I can't find the good one or the good thing to trigger to re-schedule a connection :(
Anybody else is having this issue and is able to solve it without downtime ? On Thursday, February 9, 2017 at 5:38:31 PM UTC+1, [email protected] wrote: > > We have this problem as well. frequently it's just an issue with the > scalrizer agent not being able to start. either from uncaught python > exceptions to the update client not being able to resolve the url to the > repo etc. for most of our issues bypassing scalr and getting credentials > from AWS/Azure and manually updating the scalrizer agent fixes the issue, > In most of these instances the scalrizer logs are unavailable via scalr > since the update agent can't start the scalrizer agent and so there is no > logs passed to the admin node. > > On Thursday, February 9, 2017 at 2:27:19 AM UTC-7, Matthieu Serrepuy wrote: >> >> Hi ! >> >> I am having the exact same behavior. >> We are using Azure as provider and some times, some instances switch to >> "Resuming" state. >> I couldn't find anything obvious in the scalarizr logs on my own. >> >> Looking at tcpdump, I couldn't find traffic between our scalr instance >> and the problematic one. >> >> I was not paying so much attention to this, but it seems it prevents the >> auto-scaling to work properly. >> >> Can I have assistance on how to troubleshoot this issue ? Next time it >> happens I'll be glad to provide logs or traces to fix this issue for good. >> >> Thanks, >> >> Matt >> >> On Tuesday, November 15, 2016 at 6:58:07 PM UTC+1, Marc O'Brien wrote: >>> >>> Hi Rajeev, >>> >>> More details are needed to begin looking in to this issue. What version >>> of Scalr are you using? What Cloud Provider, and what steps are taken >>> leading up to this behavior? Are instances showing as "Running" in the >>> Cloud Provider dashboard when Scalr shows them as "Resuming" or are they >>> showing the same status there as well? Scalarizr agent logs will be useful >>> as well if you can upload them here. >>> >>> Many thanks, >>> Wm. Marc O'Brien >>> Scalr Technical Support >>> >>> >>> >>> On Monday, November 14, 2016 at 11:31:41 PM UTC-7, Rajeev Gangur wrote: >>>> >>>> Hello >>>> >>>> the Scalar server instance is in "*resuming" *status continuously >>>> ..for almost half day to a day.. it does not enable pause or resume >>>> option..Can somebody help how it can be made running status again? >>>> >>>> Regards >>>> Rajeev >>>> >>> -- 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/d/optout.
