I may have found a bug in version 5.3.2. After launching a server it gets 
stuck in "Pending".
After digging in the logs  ( step 4 ) I found that that the msg_sender.py 
throws an exception because of an undefined IP somehow ( while the IP is 
known in step 1 ) 
It happens on this line:
https://github.com/Scalr/scalr/blob/master/app/python/scalrpy/msg_sender.py#L141

These are the steps taken:

*1. Server is launched ( cloud specific properties )*
- Status: ACTIVE
- IP: x.x.x.x ( correct IP )

*2. Scalarizr on server sends HostInit message and awaits ack*

2015-04-08 11:11:58,580+02:00 - DEBUG - scalarizr.messaging.p2p.producer - 
Message 'HostInit' delivered (message_id: 
4ffe31e5-a751-482a-8cf8-64633deb49b6)
2015-04-08 11:11:58,599+02:00 - DEBUG - scalarizr.messaging.p2p.consumer - 
Waiting message acknowledge event: HostInit

*3. On Scalr server internal messaging I do see the received message 
awaiting processing:*
- type: in / HostInit
- status: Pending processing

*4. After inspection in the logs I found the following exception:*
[07/Apr/2015 10:55:35][          msg_sender][1.1][7732]    WARNING Delivery 
failed, message: 7344d83b-ee1c-4f25-aada-9661959c4ba2, server: 
{u'server_id': 'ac0360f0-1979-4642-9f86-3807057821e2', 
'scalarizr.ctrl_port': 8013, u'local_ip': None, u'farm_id': 2, u'platform': 
'openstack', u'farm_roleid': 6, 'scalarizr.key': '******', u'remote_ip': 
None}, reason: <type 'exceptions.Exception'> Make request failed, reason: 
<type 'exceptions.Exception'> Unable to determine ip
    file: 
/opt/scalr-server/embedded/scalr/app/python/scalrpy/msg_sender.py, line: 142
    file: 
/opt/scalr-server/embedded/scalr/app/python/scalrpy/msg_sender.py, line: 182

I've searched the Wiki and have checked all configs. As the IP is known in 
step 1, I don't think this issue is the result of a misconfiguration. What 
gives ?

Thanks

-- 
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.

Reply via email to