Hi Victor,

Thanks for posting and raising this! The error you're seeing is because Ellis 
is attempting to provision subscribers using the wrong URI - the provisioning 
API uses port 8889 (not 8888). I've raised an issue to track fixing this 
(https://github.com/Metaswitch/chef/issues/114).

In the meantime, you should be able to fix the problem on your system by adding 
the line "hs_provisioning_hostname=localhost:8889" to /etc/clearwater/config. 
To pick up the changed config run "sudo service clearwater-infrastructure 
restart && sudo monit restart ellis".

Ellie

From: [email protected] 
[mailto:[email protected]] On Behalf Of Victor de 
Araujo Greggio
Sent: 26 March 2014 18:43
To: [email protected]
Subject: [Clearwater] All-in-one Image on EC2

Dear all,

I'm new to the group and this is my first message. I'm sorry if it was already 
posted, I've tried to find this subject on archive but I didn't succeed.

I have just installed an All-in-one image in EC2.

Everything seems to be ok when I check by monit command but when I try to 
signup via Ellis I've got an error message saying that it failed to update the 
server.

When I checked out the log file(/var/log/ellis/ellis-0.log) I saw the following 
lines:

2014-03-26 18:23:19,103 W utils:73 11116:140304169670400] Non-OK HTTP response. 
HTTPResponse(code=404,request_time=0.03207993507385254,buffer=<_io.BytesIO 
object at 
0x2ca1530>,_body=None,time_info={},request=<tornado.httpclient.HTTPRequest 
object at 
0x2d50390>,effective_url='http://my-server-name:8888/public/sip%3A6505550537%40example.com/associated_private_ids',headers={'Content-Length':
 '0', 'Connection': 'close'},error=HTTPError('HTTP 404: Not Found',))

2014-03-26 18:23:19,103 W numbers:113 11116:140304169670400] Failed to fetch 
private identities from homestead

It seems to me that it is failing while trying to update homestead base with 
the new number that it got from Ellis database, is that right?

I've tried to simulate the POST above using curl and got the same error(404). I 
just have success when I send a GET to /PING as following:

$ curl --head http:// 
my-server-name:8888/public/sip:[email protected]/associated_private_ids
HTTP/1.1 404 Not Found
Content-Length: 0

$ curl --head http:// my-server-name:8888/ping
HTTP/1.1 200 OK
Content-Length: 2
Content-Type: text/plain

Is there anything else that I could check that could be missing or not well 
configured?

I used the AMI image from March, 14th 2014.

Thanks,
Victor Greggio
_______________________________________________
Clearwater mailing list
[email protected]
http://lists.projectclearwater.org/listinfo/clearwater

Reply via email to