Sai, Thanks for your fast response. Would you be able to tar up your /etc/clearwater directory and send to me to check the configuration?
Please run "tar zcf etc.clearwater.tar.gz /etc/clearwater" and send me the resulting etc.clearwater.tar.gz file. Thanks, Matt -- Matt Williams Lead Architect, Project Clearwater +44 (0) 20 8366 1177 From: [email protected] [mailto:[email protected]] Sent: 23 December 2015 10:29 To: Matt Williams <[email protected]> Cc: Eleanor Merry <[email protected]>; [email protected] Subject: RE: Finding problem in making ellis node up Hi Matt, Yes Configuration is written to /etc/clearwater/local_config not /etc/clearwater/local_configuration Merry Christmas in advance :) Regards, Sai From: Matt Williams [mailto:[email protected]] Sent: Wednesday, December 23, 2015 3:48 PM To: Sainath Ellendula (WT01 - Product Engineering Service) <[email protected]<mailto:[email protected]>> Cc: Eleanor Merry <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]> Subject: RE: Finding problem in making ellis node up Sai, Ellie is on vacation, so I've picked this up. Well spotted on the clearwater-etcdctl issue - that could easily be the root cause of all the issues you're seeing. clearwater-etcdctl only gives the "Could not determine local IP address" if it can't find local_ip in /etc/clearwater/local_config. As Ellie observed below, it looks like you might have written your local configuration to /etc/clearwater/local_configuration rather than /etc/clearwater/local_config. Please can you confirm that your configuration is written to /etc/clearwater/local_config and not /etc/clearwater/local_configuration? Also, it looks as though you might not be subscribed to the mailing list (meaning that you might not see all responses to your question) - you can subscribe at http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org. Thanks, Matt -- Matt Williams Lead Architect, Project Clearwater +44 (0) 20 8366 1177 From: Clearwater [mailto:[email protected]] On Behalf Of [email protected]<mailto:[email protected]> Sent: 23 December 2015 06:21 To: Eleanor Merry <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]> Subject: Re: [Clearwater] Finding problem in making ellis node up Hi Ellie, Yes, I have added shared configuration file to Ellis. In /etc/clearwater/local_config --> etcd_cluster given as IP's of all other nodes(bono,sprout, homer,homestead & ralf) including Ellis as well. When i entered command cluster-health & etcdctl member list getting below error: root@ellis:/etc/clearwater# sudo clearwater-etcdctl cluster-health Could not determine local IP address root@ellis:/etc/clearwater# sudo clearwater-etcdctl member list Could not determine local IP address root@ellis:/etc/clearwater# Coming to public hostname given as system's hostname. After i was trying to send logs, ellis Logs are not generating in path (in /var/log/ellis), Even after keeping "To turn on debug logging for Ellis, write LOG_LEVEL = logging.DEBUG to the local_settings.py file (at /usr/share/clearwater/ellis/local_settings.py)." Could you please guide me, am i following correct process. Thanks in advance!! Regards, Sai ________________________________ From: Eleanor Merry <[email protected]<mailto:[email protected]>> Sent: 07 December 2015 23:11 To: Sainath Ellendula (WT01 - Product Engineering Service); [email protected]<mailto:[email protected]> Subject: RE: Finding problem in making ellis node up Hi Sainath, Have you added the shared configuration file to Ellis yet? Ellis needs this in order to run successfully (but not to install). Also, how have you set up the etcd cluster on each node? Looking at the etcd_cluster below you don't have the Ellis node being part of the initial etcd cluster. On the initial install your etcd cluster value should be identical on each node (i.e. the etcd_cluster should contain the IP addresses of every initial node). What's the output of running "sudo clearwater-etcdctl cluster-health" and "sudo clearwater-etcdctl member list"? In the details below you've put the config as being in "/etc/clearwater/local_configuration" - it needs to be in "/etc/clearwater/local_config. Also, the public hostname looks like it's 'L-185000474', which doesn't look correct at all. Has this just been mangled by the mailing list? Finally, if none of the above helps can you please send me the Ellis logs (in /var/log/ellis)? Ellie From: [email protected]<mailto:[email protected]> [mailto:[email protected]] Sent: 07 December 2015 10:47 To: Eleanor Merry; [email protected]<mailto:[email protected]> Subject: Reg: Finding problem in making ellis node up Hi Ellie, I have followed all the steps and installed Ellis successfully. Steps followed for installation from below path : http://clearwater.readthedocs.org/en/stable/Manual_Install/index.html Configuration: /etc/clearwater/local_configuration local_ip=192.168.56.10 public_ip=10.156.60.190 public_hostname=L-185000474 etcd_cluster="192.168.56.11,192.168.56.12,192.168.56.13,192.168.56.14,192.168.56.15" hosts: cd /etc/hosts 127.0.0.1 localhost #127.0.1.1 ellis 192.168.56.10 ellis # The following lines are desirable for IPv6 capable hosts ::1 localhost ip6-localhost ip6-loopback ff02::1 ip6-allnodes ff02::2 ip6-allrouters After successful installation, Still Specific node "Ellis" is not coming UP. Command : Monit status, Pls find attachment for ellis process. Please guide me here, Am i following correct process. Thanks in advance!! Regards, Sainath The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com<http://www.wipro.com> The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com<http://www.wipro.com> The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com<http://www.wipro.com>
_______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org
