Hi Rashid, It looks like there are two separate problems here:
· Homer is failing to install. · Ellis is not producing any logs (so probably isn’t running). You say that you are using the same shared_config as previously. In release Articuno, we changed the way Sprout is configured, and this may be causing some of your problems. From the release note: Once you’ve upgraded, you may also need to change your sproutlet configuration, and add a DNS record for your S-CSCF cluster. Previously most Sproutlets/Application servers (AS) either used the value of the ‘scscf_uri’ parameter for their configuration or had other hard-coded configuration. Now you have the finer control over the configuration - each Sproutlet/AS has three configuration options. The options have the same format for each Sproutlet/AS, as listed here, with <sproutlet> replaced by the appropriate Sproutlet or AS name: · <sproutlet>: The port that the Sproutlet/AS listens on. The default value is 5054 for some Sproutlets/ASs (those enabled by default) and 0 for others (those disabled by default) · <sproutlet>_prefix: The identifier prefix for this Sproutlet/AS, used to build the uri, as described below. The default value is simply the Sproutlet/AS name: <sproutlet> · <sproutlet>_uri: The full identifier for this Sproutlet/AS, used for routing and receiving requests between nodes. The default value is created using the prefix and the hostname of the parent Sprout node, i.e. “sip:<sproutlet_prefix>.<sprout_hostname>;transport=tcp<sip:%3csproutlet_prefix%3e.%3csprout_hostname%3e;transport=tcp>”. We recommend that you don’t set this yourself anymore, and use the defaults provided. As a concrete example, below are the S-CSCF options and the default values. · scscf=5054 · scscf_prefix=scscf · scscf_uri=sip:scscf.<sprout_hostname>;transport=tcp As we’ve split out the S-CSCF configuration, you’ll also now need to set up DNS records for the S-CSCF cluster specifically (rather than just using the sprout cluster). A good first step would be to update your shared configuration files and see whether that fixes any of your issues. Once you have done that, we may be able to dig deeper into the other issues. Yours, Chris From: Clearwater [mailto:[email protected]] On Behalf Of Rashid Mijumbi Sent: 05 April 2016 11:01 To: [email protected] Subject: [Project Clearwater] Manual Installation No longer Working Dear all, I have not been able to successfully do a manual installation the last 3 or so days. I did so (multiple times) successfully in the past. Here are my details: VMs are running in OpenStack with Ubuntu-14.04-trusty-server-x86_64, 1vCPU, 2GB RAM, 8GB Disk It appears that I am getting multiple errors during installation. One of the errors is during installation of homer which repeatedly gives the error: TCP poll failed to 127.0.0.1 9160 nc: connect to 127.0.0.1 port 9160 (tcp) failed: Connection refused Failed to connect to '127.0.0.1:7199<http://127.0.0.1:7199>': Connection refused for about 5 minutes. Installation of homestead gives the same errors for an even longer period. Ultimately, the installation completes, but I cannot access the ellis URL in a browser. I would like to believe that my local_config and shared_config files are okay as I have used the same setup in the past and it worked quite well. The command "sudo service ellis stop" seems to work, while "sudo service clearwater-infrastructure restart" gives the following output * Restarting clearwater-infrastructure clearwater-infrastructure nginx: [warn] conflicting server name "87.44.18.128" on [::]:80, ignored nginx: the configuration file /etc/nginx/nginx.conf syntax is ok nginx: configuration file /etc/nginx/nginx.conf test is successful Configuring monit for only localhost access [ OK ] "sudo monit status" says that everything is either running or status is ok, while "sudo clearwater-etcdctl cluster-health" shows that all cluster members are healthy. Is anyone facing a similar problem or is it just something horribly wrong with my machines ? I am attaching a number of installation error log files as well as files from /var/log. The folder /var/log/ellis is empty! Regards, Rashid
_______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org
