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.
/usr/share/clearwater/bin/run-in-signaling-namespace #!/bin/bash # @file run-in-signaling-namespace.sh # Project Clearwater - IMS in the Cloud # Copyright (C) 2015 Metaswitch Networks Ltd # # This program is free software: you can redistribute it and/or modify it # under the terms of the GNU General Public License as published by the # Free Software Foundation, either version 3 of the License, or (at your # option) any later version, along with the "Special Exception" for use of # the program along with SSL, set forth below. This program is distributed # in the hope that it will be useful, but WITHOUT ANY WARRANTY; # without even the implied warranty of MERCHANTABILITY or FITNESS FOR # A PARTICULAR PURPOSE. See the GNU General Public License for more # details. You should have received a copy of the GNU General Public # License along with this program. If not, see # <http://www.gnu.org/licenses/>. # # The author can be reached by email at [email protected] or by # post at Metaswitch Networks Ltd, 100 Church St, Enfield EN2 6BQ, UK # # Special Exception # Metaswitch Networks Ltd grants you permission to copy, modify, # propagate, and distribute a work formed by combining OpenSSL with The # Software, or a work derivative of such a combination, even if such # copying, modification, propagation, or distribution would otherwise # violate the terms of the GPL. You must comply with the GPL in all # respects for all of the code used other than OpenSSL. # "OpenSSL" means OpenSSL toolkit software distributed by the OpenSSL # Project and licensed under the OpenSSL Licenses, or a work based on such # software and licensed under the OpenSSL Licenses. # "OpenSSL Licenses" means the OpenSSL License and Original SSLeay License # under which the OpenSSL Project distributes the OpenSSL toolkit software, # as those licenses appear in the file LICENSE-OPENSSL. # Returns the namespace_prefix (only set if the signaling_namespace is in use). . /etc/clearwater/config [ -z "$signaling_namespace" ] || namespace_prefix="ip netns exec $signaling_namespace" $namespace_prefix $* ------------------------------------------------------------- nano /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver 10.0.0.11 nameserver 127.0.0.1 ------------------------------------------------------------------------------------------------------ /etc/clearwater/local_config local_ip=10.0.0.4 public_ip=84.39.45.34 public_hostname=84.39.45.34 etcd_cluster="10.0.0.4,10.0.0.5,10.0.0.6,10.0.0.7,10.0.0.8,10.0.0.9"
_______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org
