Hi Amit, The error message outlines the connection that is failing : host='192.168.197.131', port=80
You will need to make sure that the Scalr server host is reachable at 192.168.197.131:80 from the cloud instance. This may simply be an inbound firewall rule on the Scalr server, but you will need to verify this and ensure that the agent is able to establish proper communication with the Scalr server. Additional details are available in our documentation for Required Network Configuration <https://scalr-wiki.atlassian.net/wiki/display/docs/Required+Network+Configuration+for+Scalr> . Many thanks, Wm. Marc O'Brien Scalr Technical Support On Monday, October 10, 2016 at 3:08:27 PM UTC-6, Amit Saini wrote: > > Hi lgor > > Yes you are right Its configured on 192.168.197.131. > > Do i need to change the IP Address..?? or what else I need to do to make > it fix. > > Cloud you please suggest me a way to solve this Issue. I am new to the > Scalr > > Regards > Amit Saini > > On Monday, October 10, 2016 at 4:52:56 PM UTC-4, DicsyDel wrote: >> >> Scalr is installed and configured on 192.168.197.131. Agent is unable >> to start because it's unable to establish connectivity with scalr host >> to pull configuration. Both way communication between agent and scalr >> is required. >> >> Regards, >> Igor >> >> On 10 October 2016 at 13:45, Amit Saini <amit....@gmail.com> wrote: >> > Hi Marc, >> > >> > >> > This is same behaviors of all FARMS/Role not for particular FARM and >> AWS >> > console indicate that the machines are running in sate not in >> initializing >> > State >> > >> > >> > Don't Know I am Right or Wrong : But Its look like the Scalarizr agents >> is >> > not able to communicate with my Scalr to notify the state. I have >> analyzed >> > the AWS Instance and found everything fine >> > >> > >> > I have installed Scalr on Ubuntu 14 and VMWare where firewall is >> disable. >> > >> > >> > Please find the scalarizr logs >> > >> > >> > Getting WARNING: >> > >> > >> > >> > >> > >> > 2016-10-10 20:02:37,818+00:00 - WARNING - scalarizr.app - Failed to >> talk to >> > UpdateClient: Failed to get UpdateClient status. Timeout: 60 seconds >> reached >> > >> > Traceback (most recent call last): >> > >> > File >> > >> "/opt/scalarizr/embedded/lib/python2.7/site-packages/scalarizr-4.11.7-py2.7.egg/scalarizr/app.py", >> >> >> > line 958, in _talk_to_updclient >> > >> > error_text='Failed to get UpdateClient status') >> > >> > File >> > >> "/opt/scalarizr/embedded/lib/python2.7/site-packages/scalarizr-4.11.7-py2.7.egg/scalarizr/util/__init__.py", >> >> >> > line 332, in wait_until >> > >> > raise BaseException(msg) >> > >> > BaseException: Failed to get UpdateClient status. Timeout: 60 seconds >> > reached >> > >> > >> > >> > Regards >> > Amit Saini >> > >> > >> > On Monday, October 10, 2016 at 2:53:49 PM UTC-4, Marc O'Brien wrote: >> >> >> >> Hi Amit, >> >> >> >> Are you able to SSH in to these machines and gather any logs while >> they >> >> are in the OS booting stage? Does the AWS console indicate that the >> >> machines are running or still initializing? Is this behavior >> impacting all >> >> roles/farms or only this one? If only this farm is impacted, what is >> >> different about this farm or role that could be causing the failure to >> boot? >> >> This information should help you isolate why these instances are >> failing to >> >> boot when other farms previously launched successfully for you. >> >> >> >> Many thanks, >> >> Wm. Marc O'Brien >> >> Scalr Technical Support >> >> >> >> On Monday, October 10, 2016 at 7:37:07 AM UTC-6, Amit Saini wrote: >> >>> >> >>> Hi Marc, >> >>> >> >>> When I was monitoring my Server and observer some strange behavior >> with >> >>> my Server and EC2 Instance >> >>> >> >>> >> >>> 1. Its taking lot of time in 3rd step "Wait for OS to finish >> booting". It >> >>> take near about 40 Minutes. >> >>> >> >>> Which is same time mention in FARM setting to terminated the Instance >> if >> >>> not get the Hostup notification (Refer Image 1,2) >> >>> >> >>> >> >>> 2. If after 40 minutes, My EC2 Instance got terminated and a New >> instance >> >>> start running (Refer Image 3 ,4) Initialization process start again >> and then >> >>> 3rd step wait for 40 minutes and then terminated >> >>> >> >>> >> >>> >> >>> I have change the Instance termination 2400 Seconds to 5000 Seconds >> >>> (Refer Image 5)but got the same issue after 3rd step EC2 Instance got >> >>> terminated and new Instance start >> >>> >> >>> >> >>> >> >>> Its look like that Instance is not able to boot the OS >> >>> >> >>> Please Check at the security Group (Refer Image6,7) >> >>> >> >>> >> >>> Kindly Help >> > >> > -- >> > 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 scalr-discus...@googlegroups.com. >> > For more options, visit https://groups.google.com/d/optout. >> > -- 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 scalr-discuss+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
