Hi Andrew, Eventually I have found out the problem. It was a mtu issue on signaling net. I'm now able to continue my testing activity on our setup.
Thanks a lot for your support! BR, Silvestro ________________________________ Da: Silvestro Ciampoli Inviato: giovedì 20 aprile 2017 10:52:11 A: [email protected] Oggetto: Re: Sprout failed: Error: No local site registration store specified Hi Andrew, thank a lot for your help. To ease (hopefully)your investigation I preferred to re-run the live test (just basic_call ones) suggested on clearwater site. All the tests, expect the registration steps failed. On sprout log I can see TRANSPORT_ERROR messages. Do you have any idea regarding the reason I'm observing these kind of message? Please in attachment you can find the .pcap, log file of sprout and bono nodes and the output of the live test. Here below the steps performed: - 08:02:13: sudo service bono stop - 08:02:31: sudo service sprout stop - from an ubuntu desktop (10.0.0.230): rake test[example.com] SIGNUP_CODE=secret (it includes only basic call, registration and cancel tests) Please below you can find the list of the nodes running on Openstack. Thanks and regards, Silvestro ------------------------------------------------------- |bono-0.example.com | ACTIVE | - | Running | clearwater-private-signaling=192.168.1.6, 10.0.110.128; clearwater-private-management=192.168.0.7, 10.0.110.137 | |ellis-0.example.com | ACTIVE | - | Running | clearwater-private-management=192.168.0.4, 10.0.110.193 | | homer-0.example.com | ACTIVE | - | Running | clearwater-private-signaling=192.168.1.7, 10.0.110.130; clearwater-private-management=192.168.0.8, 10.0.110.139 | | homestead-0.example.com | ACTIVE | - | Running | clearwater-private-signaling=192.168.1.5; clearwater-private-management=192.168.0.6, 10.0.110.198 | | ns.example.com | ACTIVE | - | Running | clearwater-private-signaling=192.168.1.3; clearwater-private-management=192.168.0.3, 10.0.110.192 | | ralf-0.example.com | ACTIVE | - | Running | clearwater-private-signaling=192.168.1.4; clearwater-private-management=192.168.0.5, 10.0.110.197 | | sprout-0.example.com | ACTIVE | - | Running | clearwater-private-signaling=192.168.1.8; clearwater-private-management=192.168.0.9, 10.0.110.135 | ________________________________ Da: Clearwater <[email protected]> per conto di Andrew Edmonds <[email protected]> Inviato: martedì 18 aprile 2017 16:28:16 A: [email protected] Oggetto: Re: [Project Clearwater] Sprout failed: Error: No local site registration store specified Hi Silvestro, Thank you for your continued support of Clearwater, I am glad to hear you have all your nodes starting correctly now. I have taken a look through the diagnostics you have provided to try and see why your Zoiper calls are not working correctly. One thing you can do with the .cap trace you have sent is search for “sip”, this allows you to view all the SIP traffic flowing through your deployment. If I do this you can see a REGISTER at 10:35:23.2997597 that does not receive any response. This indicates to me that there might be an issue with your Sprout node processing registrations, however the Sprout logs you have attached do not cover this time period and I can’t see evidence of any calls being attempted in any of the diagnostics you’ve send me. Could you please collect another .cap trace on your Sprout node (and let me know the IP address of this node). As this trace is running could you please do the following, keeping a note of the time as you do so: · Register two subscribers on your Zoiper clients · Attempt to make a call between them Then could you send me that trace and the Sprout logs from the same time period. Thanks, Andrew From: Clearwater [mailto:[email protected]] On Behalf Of Silvestro Ciampoli Sent: Thursday, April 13, 2017 12:14 PM To: [email protected] Subject: Re: [Project Clearwater] Sprout failed: Error: No local site registration store specified Hi Andrew, thanks a lot for your suggestion. Now it seems that all nodes have started correctly. The problem that I'm encountering with this deploy now is that I'm not able to perform a call by Zoiper anymore. I'm able to register correctly by Zoiper two clients (running on two different ubuntu desktop) but the call was failing. In attachment you can find a .cap with registration and call_tentative gotten on one client interface. I attached also bono and sprout log. Please let me know if you have any suggestions. Thanks in advance, Silvestro Ciampoli ________________________________ Da: Clearwater <[email protected]<mailto:[email protected]>> per conto di Andrew Edmonds <[email protected]<mailto:[email protected]>> Inviato: mercoledì 12 aprile 2017 17:47:03 A: [email protected]<mailto:[email protected]> Oggetto: Re: [Project Clearwater] Sprout failed: Error: No local site registration store specified Hi Silvestro, Thank you for your question and the information you have provided. You were right to point out the error "Error main.cpp:1678: No local site registration store specified". This will be the cause of your Sprout process failing to start. In order to specify a local site registration store you need a sprout_registration_store option set in /etc/clearwater/shared_config, you can see here<https://clearwater.readthedocs.io/en/stable/Clearwater_Configuration_Options_Reference.html> for more details. Could you try the following steps: · add the line “sprout_registration_store=sprout.<domain name>” to /etc/clearwater/shared_config · run “sudo cw-upload_shared_config” · run “sudo monit summary” and see if the Sprout process is able to start. I believe the issue was caused by using a Heat template which is out-of-date in comparison to your Clearwater version. If you re-deploy using the latest stable version of the Heat template<https://github.com/Metaswitch/clearwater-heat/tree/stable> available on Github you should find that this is no longer an issue. Let me know if this helps. Thanks, Andrew From: Clearwater [mailto:[email protected]] On Behalf Of Silvestro Ciampoli Sent: Wednesday, April 12, 2017 11:18 AM To: [email protected]<mailto:[email protected]> Subject: [Project Clearwater] Sprout failed: Error: No local site registration store specified Hi, I'm sorry I missed to specify that to deploy Clearwater in Openstack I used the Heat template available on github. The configuration foreseen the separation between management and signaling network. BR, Silvestro Ciampoli ________________________________ Da: Silvestro Ciampoli Inviato: mercoledì 12 aprile 2017 11:02 A: [email protected]<mailto:[email protected]> Oggetto: Sprout failed: Error: No local site registration store specified Hi Clearwater Team, I'm trying to (re-)install Clearwater on Openstack (6 VMs) but I'm encountering an issue on the Sprout node. It was failing with the following error : "Error main.cpp:1678: No local site registration store specified". Please see the .log in attachment for further details. Do you have any suggestions? Below the status of other processes and the version information. Thanks in advance, Silvestro Ciampoli ------------------------------------ [sprout]ubuntu@0:~$ sudo monit summary Monit 5.18.1 uptime: 1h 0m Service Name Status Type node-0.sprout.hcllab.it Running System sprout_process Execution failed | Does... Process snmpd_process Running Process ntp_process Running Process nginx_process Running Process memcached_process Running Process clearwater_queue_manager_pro... Running Process etcd_process Running Process clearwater_diags_monitor_pro... Running Process clearwater_config_manager_pr... Running Process clearwater_cluster_manager_p... Running Process chronos_process Running Process astaire_process Running Process sprout_uptime Wait parent Program poll_sprout_sip Wait parent Program poll_sprout_http Wait parent Program nginx_ping Status ok Program nginx_uptime Status ok Program monit_uptime Status ok Program memcached_uptime Status ok Program poll_memcached Status ok Program clearwater_queue_manager_uptime Status ok Program etcd_uptime Status ok Program poll_etcd_cluster Status ok Program poll_etcd Status ok Program chronos_uptime Status ok Program poll_chronos Status ok Program astaire_uptime Status ok Progra /usr/share/clearwater/bin/clearwater-version astaire 1.0-170331.102803 chronos 1.0-170331.102347 clearwater-cluster-manager 1.0-170331.141119 clearwater-config-manager 1.0-170331.141119 clearwater-diags-monitor 1.0-170327.103718 clearwater-etcd 1.0-170331.141119 clearwater-infrastructure 1.0-170327.103718 clearwater-log-cleanup 1.0-170327.103718 clearwater-management 1.0-170331.141119 clearwater-memcached 1.0-170327.103718 clearwater-monit 5.18-170403.124108 clearwater-nginx 1.0-170223.132518 clearwater-queue-manager 1.0-170331.141119 clearwater-snmp-handler-astaire 1.0-170331.103056 clearwater-snmpd 1.0-170327.103718 clearwater-socket-factory 1.0-170327.103718 clearwater-tcp-scalability 1.0-170327.103718 memcached 1.6.00-0clearwater0.5 sprout 1.0-170403.142633 sprout-base 1.0-170403.142633 sprout-bgcf 1.0-170403.142633 sprout-icscf 1.0-170403.142633 sprout-mmtel-as 1.0-170403.142633 sprout-node 1.0-170403.142633 sprout-scscf 1.0-170403.142633 ::DISCLAIMER:: ---------------------------------------------------------------------------------------------------------------------------------------------------- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects. ----------------------------------------------------------------------------------------------------------------------------------------------------
_______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org
