Hi Asra, Looking at your /etc/resolv.conf, it looks like there is a DNS server configured with IP address 10.0.0.11. That explains why you are able to ping your other boxes. However, Project Clearwater uses the dnsmasq service for DNS, and this needs to be configured separately.
If you follow the instructions at http://clearwater.readthedocs.io/en/stable/Clearwater_DNS_Usage.html#client-configuration on each node, Project Clearwater should be able to contact your nameserver and look up the other servers in your deployment. Please get in touch if that doesn't help. Yours, Chris From: Clearwater [mailto:[email protected]] On Behalf Of [email protected] Sent: 23 May 2016 16:43 To: [email protected] Subject: [Project Clearwater] FW: Issue to solve 'hs_hostname' resolution in Sprout Hi Chris ; Thanks for your kind response. Regarding to the last issue ,please see the attachments. So if you have any idea about this, please share it with me Thanks again Best Regards Asra From: Chris Elford [mailto:[email protected]] Sent: Thursday, May 19, 2016 6:04 PM To: BANEAMOON Asra IMT/OLN; [email protected]<mailto:[email protected]> Subject: RE: [Project Clearwater] Issue to solve 'hs_hostname' resolution in Sprout Hi Asra, It looks like both of your recent emails are the same problem: your nodes are struggling to look each other up on DNS. The first place to look is your network setup. This should tell us what might be going wrong. Can you please run the following commands on your Sprout nodes, and send over the results? It would also be useful to take a look at /etc/clearwater/local_config. * ip address show * /usr/share/clearwater/bin/run-in-signaling-namespace ip address show * /usr/share/clearwater/bin/run-in-signaling-namespace ping hs.reflexion.ncc Can you also send the contents of /etc/resolv.conf? Chris From: Clearwater [mailto:[email protected]] On Behalf Of [email protected]<mailto:[email protected]> Sent: 18 May 2016 12:32 To: [email protected]<mailto:[email protected]> Subject: [Project Clearwater] Issue to solve 'hs_hostname' resolution in Sprout Hello Chris, We had an issue with sprout service : it failed to resolve 'hs_hostname' ("hs.reflexion.ncc" in our case). You can see an example in the attached sprout log file (for example at time '18-05-2016 08:12:29.384'). In term of configuration: - In the 'shared_config' file (please see the attached file), we have the line : 'hs_hostname=hs.reflexion.ncc:8888' - In our DNS we have an entry for 'hs' in the reflexion.ncc zone; and the ping to 'hs.reflexion.ncc' is working fine from sprout VM As workaround, we have put in comment (#) the 'hs_hostname=hs.reflexion.ncc:8888' line in 'shared_config' file, now we replace it by 'hs_hostname=10.0.0.8:8888' line; where 10.0.0.8 is the address of Homestead machine so then the sprout service is working. Do you know why it is not working with the last configuration? How to solve this issue? Best regards, Asra _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.
_______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org
