Hi Bertrand,

It looks like you are trying to upload shared configuration, but this is 
failing because your etcd cluster is unhealthy.

You ran clearwater-etcdctl cluster-health on a node, and the log looks like 
etcd on that node has not managed to contact etcd on any of the other nodes and 
form a cluster.

When you install the first set of nodes in a Project Clearwater deployment, you 
need to make sure that each of the nodes in the deployment has the correct 
value of etcd_cluster in /etc/clearwater/local_settings. It should be set to a 
comma separated list that contains the IP address of each of the nodes in the 
cluster. You should put this local_config in place on each of your nodes before 
installing any of the software packages using apt-get.

You will also need to start clearwater-etcd running on each of your nodes, and 
allow them to form a healthy cluster, before you can run upload_shared_config 
on any of your nodes. This means that you need to have clearwater-management 
installed on all of your nodes, before running upload_shared_config.

You should be able to get your system working by putting the correct 
configuration in place on all of your nodes, then installing 
clearwater-management. Get in touch if that does not work, and I will try to 
help out.

Yours,

Chris

From: Clearwater [mailto:clearwater-boun...@lists.projectclearwater.org] On 
Behalf Of Bertrand Bouge
Sent: 09 May 2016 12:10
To: clearwater@lists.projectclearwater.org
Subject: [Project Clearwater] Error when i try to upload shared_config


Hi,

Please I request your help.

I am beginner and I'm trying to make a configuration with 3 nodes and a DNS 
server. I followed the official document but here I have an error message to 
verify shared config with this 
command:/usr/share/clearwater/clearwater-config-manager/scripts/upload_shared_config

[bono]pfe@bono:~$ sudo 
/usr/share/clearwater/clearwater-config-manager/scripts/upload_shared_config

[sudo] password for pfe:

Upload shared configuration failed to 
http://192.168.1.126:4000/v2/keys/clearwater/site1/configuration/shared_config

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current

                                 Dload  Upload   Total   Spent    Left  Speed

100   708  100   100  100   608     14     86  0:00:07  0:00:07 --:--:--     0

{"errorCode":300,"message":"Raft Internal Error","cause":"etcdserver: request 
timed out","index":0}

Detailed output being sent to 
/var/log/clearwater-queue-manager/queue_operation.log (see joigned file)



[bono]pfe@bono:~$ clearwater-etcdctl cluster-health

member b232a431f0f1f66 is unreachable: no available published client urls

member 27470ba4b88bce9e is unreachable: no available published client urls

member 73079f127bc11ea8 is unreachable: no available published client urls

cluster is unhealthy


[bono]pfe@bono:~$ clearwater-etcdctl member list

etcd cluster has no published client endpoints.

Try '--no-sync' if you want to access non-published client 
endpoints(http://192.168.1.126:4000).

Error:  client: no endpoints available

[bono]pfe@bono:~$ nano /etc/clearwater/shared_config
# Deployment definitions
home_domain=ims.hom
sprout_hostname=sprout.ims.hom
hs_hostname=hss.ims.hom:8888
hs_provisioning_hostname=hss.ims.hom:8889
ralf_hostname=ralf.ims.hom:10888
xdms_hostname=homer.ims.hom:7888

# Email server configuration
smtp_smarthost=smtp.gmail.com<http://smtp.gmail.com>
smtp_username=bertrand...@gmail.com<mailto:bertrand...@gmail.com>
smtp_password=########
email_recovery_sender=clearwa...@ims.hom<mailto:email_recovery_sender=clearwa...@ims.hom>

# Keys
#signup_key=.....
#turn_workaround=.....
#ellis_api_key=......
#ellis_cookie_key=......


Is there a specific configuration I should edit to avoid this ?



Regards,


--
Bertrand Bouge
bertrand...@gmail.com<mailto:bertrand...@gmail.com>
_______________________________________________
Clearwater mailing list
Clearwater@lists.projectclearwater.org
http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org

Reply via email to