Pushpendra, Responses inline.
Richard From: Kumar, Pushpendra [mailto:pushpendra.ku...@intel.com] Sent: 01 March 2018 10:34 To: Richard Whitehouse (projectclearwater.org) <richard.whiteho...@projectclearwater.org> Subject: RE: Problems in manual installation of clearwater Thanks Richards for replying, 1. Yes, I have installed the ellis from root only. (while installing Ubuntu VM I have given hostname as Ellis, username as ellis) Should hostname Ellis is fine or I give different name, I will change the username to clearwater or Ubuntu(should every node have different username or username can be same). [Richard] It's fine for the hostname. We'd normally name the box "ellis-1", but if you only plan on having one node, just using ellis should be fine for a hostname. The username can be the same on every node. 2. Yes, I have selected the openSSH server and DNS server at the time of installing VM. So I have to create VM again from scratch :). Is bind9 necessary to uninstall? [Richard] Yes, otherwise dnsmasq won't be correctly configured. 3. Can I use any home_domain (like example.com or anything or only that <zone> in which I am installing the deployment) [Richard] You need to use a DNS zone for which you can configure DNS records in. So long as you can do that, you can use anything. 4. As I follow manual document, after editing and uploading shared_config file they move on to logon to ellis. Is there any other steps before move on to log on to ellis (DNS configuration etc). [Richard] You need to configure DNS records before logging into Ellis will work - it needs the DNS records set up . 5. One more thing, should I use NAT or Bridge adapter in network setting in virtualbox as NAT will private IP only and Bridge adapter will give public IP. Is port forwarding need to do in bridge adapter also? [Richard] If your IT networking allows the Bridge adapter to work, then that's probably the easier way to go. (In Bridge adapter mode, your PC will act as a network switch, and the MAC addresses from the virtual machines will be visible to your network). So I have to installed all the VM again or can I modifies existing one. Thanks, Pushpendra From: Richard Whitehouse (projectclearwater.org) [mailto:richard.whiteho...@projectclearwater.org] Sent: Thursday, March 1, 2018 3:28 PM To: Kumar, Pushpendra <pushpendra.ku...@intel.com<mailto:pushpendra.ku...@intel.com>>; clearwater@lists.projectclearwater.org<mailto:clearwater@lists.projectclearwater.org> Subject: RE: Problems in manual installation of clearwater Pushpendra, I think there are two reasons you are hitting problems installing Clearwater: 1) The ellis node that you've created has a user called ellis, which as I described below is required to be a system user under which the ellis processes run. I'd suggest you create the node with a different username (e.g. ubuntu or clearwater). 2) The ellis server has bind9 installed on it, prior to installing Clearwater, which is conflicting with dnsmasq which Clearwater uses for caching DNS queries. You'll need to uninstall this before installing the Clearwater software. At a guess, you selected the 'DNS server' task selection when installing the Ubuntu VM. We'd recommend that the only task selection you make as part of installing the Ubuntu VM is 'OpenSSH server', as that's useful to log into the node remotely, which allows you to copy and paste commands, and upload files easily. We'll make a change to Clearwater so it detects this misconfiguration and requires it to be corrected prior to installing Clearwater. Hope this helps! Richard From: Kumar, Pushpendra [mailto:pushpendra.ku...@intel.com] Sent: 01 March 2018 03:41 To: Richard Whitehouse <richard.whiteho...@metaswitch.com<mailto:richard.whiteho...@metaswitch.com>> Subject: RE: Problems in manual installation of clearwater Thanks for replying. I am using virtualbox for installing nodes, I have installed ellis first time on that node (for reconfirm, I installed all the nodes again on virtualbox, but same errors (dpkg). thanks From: Kumar, Pushpendra Sent: Thursday, March 1, 2018 9:07 AM To: 'Richard Whitehouse' <richard.whiteho...@metaswitch.com<mailto:richard.whiteho...@metaswitch.com>> Subject: RE: Problems in manual installation of clearwater Hi Richard, Thanks for replying. I am using virtualbox for installing nodes, I have installed ellis first time on that node (for reconfirm, I installed all the nodes again on virtualbox). This is the output of netstat -pltun: [ellis]ellis@Ellis:~$ sudo netstat -pltun [sudo] password for ellis: Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 10.224.61.25:53 0.0.0.0:* LISTEN 25075/named tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN 25075/named tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 28512/sshd tcp 0 0 127.0.0.1:953 0.0.0.0:* LISTEN 25075/named tcp 0 0 127.0.0.1:2812 0.0.0.0:* LISTEN 9667/monit tcp 0 0 127.0.0.1:8000 0.0.0.0:* LISTEN 2019/nginx tcp 0 0 127.0.0.1:3306 0.0.0.0:* LISTEN 8998/mysqld tcp 0 0 10.224.61.25:2380 0.0.0.0:* LISTEN 12039/etcd tcp6 0 0 :::53 :::* LISTEN 25075/named tcp6 0 0 :::22 :::* LISTEN 28512/sshd tcp6 0 0 ::1:953 :::* LISTEN 25075/named tcp6 0 0 :::4000 :::* LISTEN 12039/etcd tcp6 0 0 :::80 :::* LISTEN 2019/nginx udp 0 0 10.224.61.25:53 0.0.0.0:* 25075/named udp 0 0 127.0.0.1:53 0.0.0.0:* 25075/named udp 0 0 0.0.0.0:68 0.0.0.0:* 703/dhclient udp 0 0 10.224.61.25:123 0.0.0.0:* 9178/ntpd udp 0 0 127.0.0.1:123 0.0.0.0:* 9178/ntpd udp 0 0 0.0.0.0:123 0.0.0.0:* 9178/ntpd udp 0 0 0.0.0.0:49694 0.0.0.0:* 703/dhclient udp6 0 0 :::29724 :::* 703/dhclient udp6 0 0 :::53 :::* 25075/named udp6 0 0 fe80::a00:27ff:fe11:123 :::* 9178/ntpd udp6 0 0 ::1:123 :::* 9178/ntpd udp6 0 0 :::123 :::* 9178/ntpd I am also getting 502 Bad Gateway when I trying to connect ellis using http://ellis.iind.intel.com Thanks Pushpendra From: Richard Whitehouse [mailto:richard.whiteho...@metaswitch.com] Sent: Thursday, March 1, 2018 4:21 AM To: Kumar, Pushpendra <pushpendra.ku...@intel.com<mailto:pushpendra.ku...@intel.com>>; clearwater@lists.projectclearwater.org<mailto:clearwater@lists.projectclearwater.org> Subject: RE: Problems in manual installation of clearwater Pushpendra, usermod: user ellis is currently used by process 1343 dpkg: error processing package ellis (--configure): subprocess installed post-installation script returned error exit status 8 Processing triggers for libc-bin (2.19-0ubuntu6.9) ... Processing triggers for ureadahead (0.100.0-16) ... Errors were encountered while processing: ellis E: Sub-process /usr/bin/dpkg returned an error code (1) It sounds like you attempted to install ellis on a node was installed on a node in which there already was an ellis user - is that correct? Ellis requires a user to run the components as for security so that we aren't running components as root which don't require root privileges, and this is required to be ellis. dnsmasq: failed to create listening socket for 127.0.0.1: Address already in use dnsmasq: failed to create listening socket for port 53: Address already in use $sudo DEBIAN_FRONTEND=noninteractive apt-get install clearwater-management --yes Errors were encountered while processing: ellis E: Sub-process /usr/bin/dpkg returned an error code (1) >From these logs, and the similar logs regarding bono, sprout and >clearwater-management it looks like there's already a service running on the >nodes which is bound to port 53 before you install Clearwater. We've only regularly tested performing the manual install on a clean Ubuntu box, and if I create a new Ubuntu VM (e.g. the basic Ubuntu 14.0.4 VM in -a22323d8 ) I don't see anything already running on Port 53 before I install Clearwater. ubuntu@ip-10-0-162-214:~$ sudo netstat -pltun Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 1133/sshd tcp6 0 0 :::22 :::* LISTEN 1133/sshd udp 0 0 0.0.0.0:5254 0.0.0.0:* 582/dhclient udp 0 0 0.0.0.0:68 0.0.0.0:* 582/dhclient udp6 0 0 :::21727 :::* 582/dhclient Can you clarify what image you are attempting to install ellis on where you are seeing these errors, and what's already installed on the box? Can you run the above netstat command? For the error: reload: Job is not running: clearwater-monit /usr/share/clearwater/infrastructure/scripts/memcached: line 43: /etc/memcached.conf: No such file or directory reload: Job is not running: clearwater-monit Can you provide the complete output of the vellum build log? It'd be useful to know in what context this error was output - had something in the build already failed? It sounds like it failed to install memcached on the vellum node. Regarding smtp_smarthost - this needs to be an SMTP server which can send mail so that Ellis can send password recovery emails. If it's not configured then password recovery emails won't work. See the entry in http://clearwater.readthedocs.io/en/stable/Clearwater_Configuration_Options_Reference.html#core-options for details about the SMTP options. Regarding home_domain, it's described in Clearwater Options reference - see http://clearwater.readthedocs.io/en/stable/Clearwater_Configuration_Options_Reference.html#core-options - it needs to be a domain which will resolve to the P-CSCFs (e.g. the bono nodes in the deployment). It's usually also the root domain for all of the domains used. iind.intel.com might be a good choice if you can configure DNS entries under that domain - you'll need to configure the DNS entries listed in http://clearwater.readthedocs.io/en/stable/Clearwater_DNS_Usage.html in this domain You will need to complete the DNS configuration before Ellis will work - it needs a DNS entry to exist in order to communicate with the other nodes in the deployment. Richard From: Kumar, Pushpendra [mailto:pushpendra.ku...@intel.com] Sent: 28 February 2018 19:00 To: Richard Whitehouse <richard.whiteho...@metaswitch.com<mailto:richard.whiteho...@metaswitch.com>> Subject: Problems in manual installation of clearwater Hi Richards, I need your help in Clearwater project manual installation, Its on high priority so please consider that. I am installing the clearwater usingg manual installation. I have created the 6 VMs on virtualbox (using bridge adapter in network setting, used the same IP as public_ip and local_ip in local.conf) as I follow http://clearwater.readthedocs.io/en/stable/Manual_Install.html. while installing I have faced some errors (mentioned below), it will be your great help if u guide some solutions for them: One more thing as I am using bridge adapter in network, I have not did any port forwarding as mention in document (I am able to ping vm from one to another i.e. they are are communicating) 1.in installtion of ellis: $sudo DEBIAN_FRONTEND=noninteractive apt-get install ellis --yes usermod: user ellis is currently used by process 1343 dpkg: error processing package ellis (--configure): subprocess installed post-installation script returned error exit status 8 Processing triggers for libc-bin (2.19-0ubuntu6.9) ... Processing triggers for ureadahead (0.100.0-16) ... Errors were encountered while processing: ellis E: Sub-process /usr/bin/dpkg returned an error code (1) Note: First time I install ellis I got this error, then I installed again in new node from scratch then also got the same error. dnsmasq: failed to create listening socket for 127.0.0.1: Address already in use dnsmasq: failed to create listening socket for port 53: Address already in use $sudo DEBIAN_FRONTEND=noninteractive apt-get install clearwater-management --yes Errors were encountered while processing: ellis E: Sub-process /usr/bin/dpkg returned an error code (1) 2.in installation of bono: $sudo DEBIAN_FRONTEND=noninteractive apt-get install bono restund --yes dnsmasq: failed to create listening socket for 127.0.0.1: Address already in use dnsmasq: failed to create listening socket for port 53: Address already in use 3.in installation of sprout: $sudo DEBIAN_FRONTEND=noninteractive apt-get install sprout --yes dnsmasq: failed to create listening socket for port 53: Address already in use dnsmasq: failed to create listening socket for port 53: Address already in use dnsmasq: failed to create listening socket for 127.0.0.1: Address already in use dnsmasq: failed to create listening socket for 127.0.0.1: Address already in use $sudo DEBIAN_FRONTEND=noninteractive apt-get install clearwater-management --yes dnsmasq: failed to create listening socket for port 53: Address already in use dnsmasq: failed to create listening socket for 127.0.0.1: Address already in use 4.in installtion of homer: $sudo DEBIAN_FRONTEND=noninteractive apt-get install homer --yes dnsmasq: failed to create listening socket for port 53: Address already in use [fail] invoke-rc.d: initscript dnsmasq, action "start" failed. dnsmasq: failed to create listening socket for 127.0.0.1: Address already in use 5.in installtion of dime: $sudo DEBIAN_FRONTEND=noninteractive apt-get install dime clearwater-prov-tools --yes dnsmasq: failed to create listening socket for port 53: Address already in use dnsmasq: failed to create listening socket for 127.0.0.1: Address already in use 6.in installtion of vellum: * Starting DNS forwarder and DHCP server dnsmasq dnsmasq: failed to create listening socket for port 53: Address already in use * Restarting DNS forwarder and DHCP server dnsmasq dnsmasq: failed to create listening socket for 127.0.0.1: Address already in use [fail] reload: Job is not running: clearwater-monit /usr/share/clearwater/infrastructure/scripts/memcached: line 43: /etc/memcached.conf: No such file or directory reload: Job is not running: clearwater-monit -->I ignore above errors and move on to next step i.e. editing shared_config file and uploading -->shared_config file: [bono]bono@Bono:/etc/clearwater$ cat shared_config ##################################################################### # No Shared Config has been provided # Replace this file with the Shared Configuration for your deployment ##################################################################### # Deployment definitions home_domain=iind.intel.com sprout_hostname=sprout.iind.intel.com sprout_registration_store=vellum.iind.intel.com hs_hostname=hs.iind.intel.com:8888 hs_provisioning_hostname=hs.iind.intel.com:8889 homestead_impu_store=vellum.iind.intel.com ralf_hostname=ralf.iind.intel.com:10888 ralf_session_store=vellum.iind.intel.com xdms_hostname=homer.iind.intel.com:7888 chronos_hostname=vellum.iind.intel.com cassandra_hostname=vellum.iin.intel.com # Email server configuration smtp_smarthost= smtp_username=username smtp_password=password email_recovery_sender=clearwa...@example.org<mailto:email_recovery_sender=clearwa...@example.org> # Keys signup_key=secret turn_workaround=secret ellis_api_key=secret ellis_cookie_key=secret ? What would I use in smtp_smarthost= (is it localhost?) ques: Is home_domain =iind.intel.com is right? (when I ping using #ping ellis it automatically takes like ellis.iind.intel.com) , it basically the intel's domain. -->local_config : (IP ans hostname changed in every node) local_ip=10.224.61.25 public_ip=10.224.61.25 public_hostname=Ellis etcd_cluster="10.224.61.20,10.224.61.21,10.224.61.22,10.224.61.25,10.224.61.48,10.224.61.50" ? After that when I am trying to connect to ellis using http://ellis.iind.intel.com or http://10.224.61.25 it is giving like 502 Bad Gateway nginx /1.4.6 (Ubuntu). I have not did any DNS configuration yet (because I am using the intel domain or do I need to do it... in which node and how). ? I will love to hear your response Thanks Pushpendra
_______________________________________________ Clearwater mailing list Clearwater@lists.projectclearwater.org http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org
