OK so any clue how I change this for the router roles?
did not send 'hostInit' event in 900 seconds after launch (Try increasing
timeouts in role settings). Considering it broken. Terminating instance.
|
On Tuesday, March 25, 2014 7:20:19 PM UTC-7, Aatxe Urrutia wrote:
>
> Hello I have setup opensource scalr in both ec2 ( which is pretty
> straightforward) and also in my local location ( to avoid having an
> instance running in ec2 24/7). I have registered the system and gotten
> whitelisted and downloaded the templates but when I bring up the VPC router
> it goes through all the stages then gets terminated because it doesn't get
> to the "HostUp" stage of the calls.
>
>
> I can login via the scalr key and see the connections ( & (I manually
> tested via telnet all the connections through the vpc to the local and
> public EIP)) in the logs such as
>
> "name": "SCALR_AVAIL_ZONE",
> "value": "us-west-2b"
> },
> {
> "name": "SCALR_EVENT_IMAGE_ID",
> "value": "ami-6d68f95d"
> },
> {
> "name": "SCALR_EVENT_EXTERNAL_IP",
> "value": "54.1x6.xx.xx"
> },
> {
> "name": "SCALR_EVENT_INTERNAL_IP",
> "value": "10.x.x.2xx"
> },
> {
> "name": "SCALR_EVENT_ROLE_NAME",
> "value": "router-ubuntu1204"
> },
> {
> "name": "SCALR_EVENT_ISDBMASTER",
> "value": ""
> },
> {
>
>
> "name": "SCALR_EVENT_INSTANCE_ID",
> "value": "i-81fx84xx"
> },
> {
> "name": "SCALR_EVENT_AMI_ID",
> "value": "ami-6d68f95d"
> },
> {
> "name": "SCALR_EVENT_REGION",
> "value": "us-west-2"
> },
> {
> "name": "SCALR_EVENT_AVAIL_ZONE",
> "value": "us-west-2b"
> },
> {
> "name": "SCALR_EVENT_NAME",
> "value": "HostInit"
> }
> ],
> "message_id": "898695xxxxxxxxxxxxx",
> "remote_ip": ""
> },
> "meta": {
> "server_id": "100xxxxxxxxxxxxxxxx",
> "scalr_version": "4.5.0"
> },
> "name": "HostInitResponse",
> "id": "xxxxxxxxxxxxxxxxxxxx"
> }
> 2014-03-26 00:51:40,296 - DEBUG - scalarizr.messaging.p2p.consumer -
> Received message 'HostInitResponse' (message_id: 8xxxxxxxxxxxxxxxxxxxxxxxx,
> format: json)
> 2014-03-26 00:51:40,328 - DEBUG - scalarizr.messaging.p2p - Commiting
> put_ingoing
> 2014-03-26 00:51:40,328 - DEBUG - scalarizr.messaging.p2p - Commited
> put_ingoing
> 2014-03-26 00:51:40,337 - DEBUG - scalarizr.messaging.p2p.consumer - "POST
> /control HTTP/1.1" 201 -
>
> all of the icons in scalr come on and I can use the ssh and other icons
> and I can login via scalr key but then it terminates via scalr ui
> eventually but not the actual node.
>
> Is perhaps there anything that would stop the HostUp call say for example
> if the following scalr agent code is mistaking the scalr server ip for its
> own ec2 range? i.e.
>
>
> def is_private_ip(ipaddr):
> return any(map(lambda x: ipaddr.startswith(x), ('10.', '172.',
> '192.168.')))
>
>
> Scalr server ip is in a local dc at 10.1.x & amazon ips are at a 10.4.x
>
>
> Or is there simply someother part I am not seeing about the "HostUp"
> event call & is there a way for me to check this on the VP i.e. specific
> port and to which ip? i.e. ip of scalr server in its config or some other
> mechanism?
>
--
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.
