Andrew, Thanks for your reply. I observed that nginx and ellis services was running correctly in ellis node.
You can find the logs of ellis [1] and nginx [2] after restarting services but I wonder is it required to register users in homestead before running the "rake test" command ? Best Regards, [1] https://docs.google.com/document/d/1M_7jwnTwYF2pXVZtBp5VGLgAKZC2_rWW7B9uoUijAOA/edit?usp=sharing [2] https://docs.google.com/document/d/1H953N_g93uyVTXa7ldeMw1jT6XcvjeVFVmGvhyiId54/edit?usp=sharing sudo monit summary Monit 5.18.1 uptime: 8d 23h 4m Service Name Status Type node-ellis-0.example.com Running System ntp_process Running Process nginx_process Running Process mysql_process Running Process ellis_process Running Process clearwater_queue_manager_pro... Running Process etcd_process Running Process clearwater_diags_monitor_pro... Running Process clearwater_config_manager_pr... Running Process nginx_ping Status ok Program nginx_uptime Status ok Program monit_uptime Status ok Program poll_ellis Status ok Program poll_ellis_https Status ok Program clearwater_queue_manager_uptime Status ok Program etcd_uptime Status ok Program poll_etcd_cluster Status failed Program poll_etcd Status ok Program 2017-06-14 13:45 GMT+02:00 Andrew Edmonds <[email protected]>: > Hi Alioune, > > > > Thank you for your question and for the detailed logs you have provided. > > > > When HTTP requests are sent to Ellis in order to provision subscribers > they pass through nginx. nginx is a generic HTTP web server that should > forward these HTTP requests on to Ellis. However if we look at the error > logs we can see: > > > > - Account creation failed with HTTP code 502, body <html> > > <head><title>502 Bad Gateway</title></head> > > <body bgcolor="white"> > > <center><h1>502 Bad Gateway</h1></center> > > <hr><center>*nginx/1.4.6 (Ubuntu)*</center> > > </body> > > </html> > > > > This shows that the error is coming from nginx and it means that nginx > can’t communicate with Ellis. This could be caused by one of the following: > > > > · The Ellis process is not running > > · Some state has got stuck that means that nginx and Ellis can’t > communicate > > > > To investigate this access your Ellis VM’s console and run “sudo monit > summary”, this will show you what processes are running . To restart nginx > and the Ellis process run the commands “sudo service nginx restart” and > “sudo service ellis restart”. If this still does not work you can check the > most recent log in /var/log/ellis and the /var/log/nginx/error.log. > > > > Thanks, > > > > Andrew > > > > *From:* Clearwater [mailto:[email protected]] > *On Behalf Of *Alioune BA > *Sent:* Tuesday, June 13, 2017 3:59 PM > *To:* [email protected] > *Subject:* [Project Clearwater] Fail to test Clearwater with > clearwater-live-test > > > > Hi all, > > I'm trying to setup Clearwater IMS core with the release-85 of > clearwater-heat. > > Clearwater node are running and now I would like to test the IMS core > using clearwater-live-test with commands [1] and [2] > But according to the logs in [3] all test fails with messages "502 Bad > Gateway" and "Account creation failed with HTTP code 502" > > Please do you have any suggestion to solve that issue ? > > I follow [4] to setup clearwater-live-test > 192.168.74.8 = bono > 192.168.74.4 = ellis > The server from which i run [1] and [2] can ping all nodes of Clearwater > > [1] rake test[example.com] SIGNUP_CODE=secret PROXY=192.168.74.8 > ELLIS=192.168.74.14 > [2] rake test[example.com] SIGNUP_CODE=secret ELLIS=192.168.74.14 > [3] https://docs.google.com/document/d/1rhdojSbDP58DgClFaAjyF8Tsy5urz > O_8dRe8TlAeVUQ/edit?usp=sharing > [4] http://clearwater.readthedocs.io/en/stable/Running_the_live_tests.html > > _______________________________________________ > Clearwater mailing list > [email protected] > http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists. > projectclearwater.org > >
_______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org
