Des, Looking back through this trail, I've just realized you might be running all components on the same VM instance. If so, you might have hit https://github.com/Metaswitch/ellis/issues/4 - ellis, homer and homestead all install iptables rules that claim port 80 (HTTP) and whichever is install last receives the HTTP queries. I've raised issue https://github.com/Metaswitch/crest/issues/9 to cover fixing this properly, but in the meantime you should be able to issue "sudo iptables-restore /usr/share/clearwater/ellis/iptables.rules".
Please let me know how you get on. Thanks, Matt From: Matt Williams Sent: 07 June 2013 09:08 To: [email protected] Subject: RE: Error on trying Ellis Web page Des, Glad to hear you got DNS working! Please can you check /var/log/ellis/ellis-0.log as well as /var/log/ellis/ellis-1.log? ellis runs two processing threads and each has its own log file. I'd always expect to see at least one line of log output per handled request. Hopefully /var/log/ellis/ellis-0.log will both report the request and why it's failing. If we don't see any logs in /var/log/ellis/ellis-0.log, I'd suggest running tcpdump and checking that the request is actually hitting the ellis server. Incidentally, to restart ellis, you need to do "sudo monit restart ellis". "sudo service clearwater-infrastructure restart" only restarts the infrastructure - upgrading packages and fixing up configuration files if required. There's a little more information on this at https://github.com/Metaswitch/clearwater-docs/wiki/Troubleshooting%20and%20Recovery#general if you're interested. Please let me know what /var/log/ellis/ellis-0.log shows. Thanks, Matt From: [email protected] [mailto:[email protected]] On Behalf Of Des Hartman Sent: 07 June 2013 03:40 To: [email protected] Subject: [Clearwater] Error on trying Ellis Web page Did the manual install, got the DNS working, but now stuck with ellis web page. When I go to http://ellis.local I get: "{"status": 404, "message": "Not Found", "reason": "unknown", "detail": {}, "error": true}" My DNS is set up locally on the server, not EC2. Looks like I am reaching a web server, but just not getting data back. This is what I see in the Ellis log tail -f /var/log/ellis/ellis-1.log 2013-06-07 12:24:33,545 I web:1447 1439:140200949659392] 200 GET /ping (127.0.0.1) 0.26ms 2013-06-07 12:26:13,648 I web:1447 1439:140200949659392] 200 GET /ping (127.0.0.1) 0.30ms 2013-06-07 12:26:23,660 I web:1447 1439:140200949659392] 200 GET /ping (127.0.0.1) 0.22ms 2013-06-07 12:26:33,671 I web:1447 1439:140200949659392] 200 GET /ping (127.0.0.1) 2.33ms 2013-06-07 12:28:33,803 I web:1447 1439:140200949659392] 200 GET /ping (127.0.0.1) 0.27ms I tried a restart of the services as shown below. #sudo service clearwater-infrastructure restart Ign http://repo.cw-ngv.com binary/ InReleaserwater-infrastructure Hit http://repo.cw-ngv.com binary/ Release.gpg Hit http://repo.cw-ngv.com binary/ Release Hit http://repo.cw-ngv.com binary/ Packages Ign http://repo.cw-ngv.com binary/ Translation-en_AU Ign http://repo.cw-ngv.com binary/ Translation-en Reading package lists... Done Reading package lists... Done Building dependency tree Reading state information... Done Skipping bono, it is not installed and only upgrades are requested. clearwater-infrastructure is already the newest version. clearwater-memcached is already the newest version. clearwater-tcp-scalability is already the newest version. ellis is already the newest version. homer is already the newest version. homestead is already the newest version. restund is already the newest version. sprout is already the newest version. sprout-libs is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 68 not upgraded. * Reloading daemon monitor configuration monit Thanks Des Hartman
_______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/listinfo/clearwater
