Hi Thomas,
instances_connection_policy: public
This is example of error:
[16/Jan/2014 14:50:40][0.0.30][msg_sender][1658][140256117217712] ERROR
Delivery failed, message:'703c39c3-6795-46f0-bfbf-55c280a8f953'
error:'<type 'exceptions.Exception'>
server:66d9d1ee-991b-4f4e-8e3d-a6a889d1f0fb error:can't determine IP line:
274'
P.S. I did some posts before and to fix that error, I have to do next:
/usr/share/pyshared/scalarizr/platform/__init__.py
def is_private_ip(ipaddr):
return any(map(lambda x: ipaddr.startswith(x), ('10.', '172.',
'192.168.')))
and add my public networks + block any scalarizr updates, otherwise system
will not be able to detect IP of the server :(
Субота, 18 січня 2014 р. 15:34:39 UTC+1 користувач Thomas Orozco написав:
>
> Hi Mykhaylo
>
> Could you do the following:
> - Indicate the value for the instances_connection_policy configuration
> key you used (if you used the installer, this is
> /var/scalr/app/etc/config.yml)
> - Provide the logs for the message sender process (if you used the
> installer, they are in /var/log/scalr/msgsender.log)
>
> Thanks!
>
> On Friday, January 17, 2014 2:09:17 PM UTC+1, Mykhaylo Dobrovolskyy wrote:
>>
>> Hi,
>>
>> it could be the same problem as I'm seeing right now with our openstack
>> installation.
>>
>> We did only one interface with public IP allocated to it already. Scalr
>> is not seeing that configuration as right network configuration and if you
>> check system logs - you will see that scalr is saying that can't identify
>> IP of the instance. (it's just an option regarding what it could be)
>>
>> Середа, 15 січня 2014 р. 16:11:56 UTC+1 користувач Mike McCarthy написав:
>>>
>>> No, sadly not. We hit a few other issues with using Openstack so setup
>>> everything on AWS. Scalr quite happily integrated with that environment
>>> without any problems. I've not had chance to revisit working with
>>> openstack since then but would be happy to hear if anyone else had a
>>> similar problem to this and overcame it.
>>>
>>> On Wednesday, January 15, 2014 11:18:18 AM UTC, ramon makkelie wrote:
>>>>
>>>> i have the same problem
>>>> did you fixed it yet?
>>>>
>>>> Op woensdag 23 oktober 2013 13:04:24 UTC+2 schreef Mike McCarthy:
>>>>>
>>>>> Hi,
>>>>>
>>>>> I'm currently working on a POC setup of Openstack Grizzly and Scalr
>>>>> and have hit a bit of a wall I'm hoping for some help with. At present I
>>>>> have an Openstack Grizzly installation up and running on an ubuntu 12.04
>>>>> VM
>>>>> within Virtualbox and have set up a second Ubuntu 12.04 VM to run Scalr
>>>>> on. I used the Scalr installer from github to get Scalr itself up and
>>>>> have added Openstack as an environment.
>>>>>
>>>>> The problem I have is when I come to try import a role it just
>>>>> hangs. I've got a Centos6.4 instance running and installed scalarizr on
>>>>> it and then gone through the wizard to create a role from a non Scalr
>>>>> server. This gives me the command to launch scalarizr which when
>>>>> executed
>>>>> gives me this output:
>>>>>
>>>>> [root@host-50-50-1-3 ~]# scalarizr --import -y -o
>>>>> server-id=da233379-a7e4-45f8-a81d-4a55a6f8c5f0 -o role-name=base -o
>>>>> crypto-key=vLQWa7QZqG7KT+1KdQAuIg0etvFlfMNM26I/Jg/H -o platform=openstack
>>>>> -o queryenv-url=http://192.168.100.70/query-env -o
>>>>> messaging-p2p.producer-url=http://192.168.100.70/messaging -o
>>>>> env-id=1 -o region=RegionOne -o scalr-id=581c81e7
>>>>> 2013-10-23 11:43:33,612 - INFO - scalarizr - [pid: 3437] Starting
>>>>> scalarizr 0.21.24
>>>>> Starting import process...
>>>>> Don't terminate Scalarizr until Scalr will create the new role
>>>>> 2013-10-23 11:43:33,732 - INFO - scalarizr.config - State: importing
>>>>> 2013-10-23 11:44:30,890 - INFO - scalarizr - Starting API server on
>>>>> http://0.0.0.0:8010
>>>>> 2013-10-23 11:44:31,545 - INFO - scalarizr.messaging.p2p.consumer -
>>>>> Building message consumer server on 0.0.0.0:8013
>>>>> 2013-10-23 11:44:34,202 - INFO - scalarizr.snmp.agent - [pid: 3515]
>>>>> Starting SNMP server on 0.0.0.0:8014
>>>>> 2013-10-23 11:45:20,213 - INFO - scalarizr.handlers.lifecycle - Server
>>>>> will be imported into Scalr
>>>>>
>>>>> And this is where it just sits. The import wizard in my browser just
>>>>> says "Waiting for running Scalarizr on server..." and nothing else seems
>>>>> to
>>>>> happen. I'd appreciate any pointers anyone can give as to either how to
>>>>> fix this or what logs files I can look in to try and figure out what is
>>>>> going on. The scalarizr_debug.log is identical to the output above and I
>>>>> can't see anything in the syslog files or the apache logs on the Scalr
>>>>> server that would suggest a problem. Am I missing something?
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Mike
>>>>>
>>>>>
>>>>>
--
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/groups/opt_out.
