[Spce-user] Fw: 503 for web backend on ec2 doesn't init
Manu Raghavan
manu at voxology.co
Mon Mar 16 16:00:52 EDT 2015
Hello,
In trying to use either your pre-configured ec2 image, or the CE installer on a new ec2 instance of Debian wheezy (v7),
the web interfaces do not spin up completely.
I’ve tried initializing these services by hand, but haven’t been successful so far.
When hitting <host>:1443 to set up the backend, nginx returns a 503 because the underlying web application is not set up.
The logs and port scanning of different interfaces seem to imply that one or more web applications (ngcp-panel, ngcp-www-scs) do not spin up.
I’ve also tried to spin them up manually, but without success so far. I’ve tried this with mr3.7.1 and mr3.7.2 with the same result:
# /etc/init.d/ngcp-panel start
Starting NGCP-Panel Webapp:Use of uninitialized value $value in pattern match (m//) at /usr/share/perl5/Config/General.pm line 872.
Killed
error ... failed!
failed!
# /etc/init.d/ngcp-www-csc start
Starting NGCP-CSC Webapp:ngcp-www-csc not yet configured. Edit /etc/default/ngcp-www-csc first. ... (warning).
.
In the latter case, /etc/default/ngcp-www-csc has the line, RUN_DAEMON configured to NO, which seems to imply something else
is misconfigured by ngcpcfg apply or earlier.
I was able to set up a vagrant box successfully earlier in a testbed setup. I would appreciate any guidance on getting Sipwise CE configured correctly on a public host.
Thanks in advance,
Manu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20150317/8738d96d/attachment.html>
More information about the Spce-user
mailing list