Hi, As mentioned in response to another report of the same problem, this is probably caused by a bug in Sprout, tracked under https://github.com/Metaswitch/sprout/issues/1656, which can cause Sprout to attempt to use the wrong port.
The workaround for this is to remove the "chronos_hostname" option from the shared_config. Instructions on how to edit shared config can be found here: http://clearwater.readthedocs.io/en/latest/Modifying_Clearwater_settings.html We expect that this bug will be fixed in the next release, due next week. Regards, Seb. From: Clearwater [mailto:[email protected]] On Behalf Of Silvestro Ciampoli Sent: 21 December 2016 11:22 To: [email protected] Subject: [Project Clearwater] Error stack.cpp:325: Failed to start UDP transport for port 172 (Permission denied) Hi Ellie, below the output of the clearwater-version command. Please consider that I'm deploying Clearwater by Cloudify. The deployment seems to be completed but checking the status I see the error on Sprout node. Thank you for your support. BR, Silvestro ------- [sprout]ubuntu@sprout-1z1voi:~$ /usr/share/clearwater/bin/clearwater-version clearwater-cluster-manager 1.0-161202.152523 clearwater-config-manager 1.0-161202.152523 clearwater-diags-monitor 1.0-161202.130810 clearwater-etcd 1.0-161202.152523 clearwater-infrastructure 1.0-161202.130810 clearwater-log-cleanup 1.0-161202.130810 clearwater-management 1.0-161202.152523 clearwater-monit 5.18-161123.110109 clearwater-nginx 1.0-161109.130509 clearwater-queue-manager 1.0-161202.152523 clearwater-socket-factory 1.0-161202.130810 clearwater-tcp-scalability 1.0-161202.130810 sprout 1.0-161202.163421 sprout-base 1.0-161202.163421 sprout-bgcf 1.0-161202.163421 sprout-icscf 1.0-161202.163421 sprout-mmtel-as 1.0-161202.163421 sprout-scscf 1.0-161202.163421 ---------------------------------------------------------------------- Message: 1 Date: Tue, 20 Dec 2016 10:57:59 +0000 From: "Eleanor Merry (projectclearwater.org)" <[email protected]<mailto:[email protected]>> To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: Re: [Project Clearwater] Error stack.cpp:325: Failed to start UDP transport for port 172 (Permission denied) Message-ID: <bl2pr02mb2084783467ffac04b5833f499b...@bl2pr02mb2084.namprd02.prod.outlook.com<mailto:bl2pr02mb2084783467ffac04b5833f499b...@bl2pr02mb2084.namprd02.prod.outlook.com>> Content-Type: text/plain; charset="us-ascii" Hi Silvestro, What version of Clearwater are you using? I'm wondering if you've got different versions of the base Sprout component and the Sproutlets, and this is causing the error. What's the output of running '/usr/share/clearwater/bin/clearwater-version'? Ellie From: Clearwater [mailto:[email protected]] On Behalf Of Silvestro Ciampoli Sent: 20 December 2016 10:34 To: [email protected]<mailto:[email protected]> Subject: [Project Clearwater] Error stack.cpp:325: Failed to start UDP transport for port 172 (Permission denied) Hi, I'm trying to deploy Clearwater on an Openstack environment. I'm encountering an issue on the sprout node. [sprout]ubuntu@sprout-1z1voi:~$ sudo monit summary Monit 5.18.1 uptime: 18h 18m Service Name Status Type node-sprout-1z1voi.clearwate... Running System sprout_process Execution failed | Does... Process ntp_process Running Process nginx_process Running Process clearwater_queue_manager_pro... Running Process etcd_process Running Process clearwater_diags_monitor_pro... Running Process clearwater_config_manager Running Process clearwater_cluster_manager Running Process sprout_uptime Not monitored Program poll_sprout_sip Not monitored Program poll_sprout_http Not monitored Program nginx_uptime Status ok Program monit_uptime 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 Looking at the log, I see the error below. It seems it is trying to configure port 172; it's not clear to me why it is trying to use this low port number. Do you have any suggestions? Please you can find more details on the log provided in attachment. thanks in advance, Silvestro ------------------------ .. .. 0-12-2016 10:09:57.235 UTC Debug pjsip: sip_endpoint.c Creating endpoint instance... 20-12-2016 10:09:57.238 UTC Debug alarm.cpp:241: Started reraising alarms every 30 seconds 20-12-2016 10:09:57.238 UTC Debug alarm.cpp:253: Reraising all alarms with a known state 20-12-2016 10:09:57.255 UTC Verbose pjsip: pjlib epoll I/O Queue created (0x7fb1594f34c0) 20-12-2016 10:09:57.255 UTC Verbose pjsip: sip_endpoint.c Module "mod-msg-print" registered 20-12-2016 10:09:57.255 UTC Debug pjsip: sip_transport. Transport manager created. 20-12-2016 10:09:57.255 UTC Verbose pjsip: sip_endpoint.c Module "mod-tsx-layer" registered 20-12-2016 10:09:57.255 UTC Verbose pjsip: sip_endpoint.c Module "mod-stateful-util" registered 20-12-2016 10:09:57.255 UTC Verbose pjsip: sip_endpoint.c Module "mod-sprout-util" registered 20-12-2016 10:09:57.255 UTC Error stack.cpp:325: Failed to start UDP transport for port 172 (Permission denied) 20-12-2016 10:09:57.255 UTC Error pjsip: Assert failed: stack.cpp:767 status == 0 20-12-2016 10:09:57.256 UTC Error main.cpp:1771: Error initializing stack Permission denied .. .. ----- ::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. ---------------------------------------------------------------------------------------------------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.projectclearwater.org/pipermail/clearwater_lists.projectclearwater.org/attachments/20161220/c76ea3f6/attachment-0001.html> ------------------------------ Message: 2 Date: Tue, 20 Dec 2016 15:07:26 +0000 From: "Matt Williams (projectclearwater.org)" <[email protected]<mailto:[email protected]>> To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: [Project Clearwater] Release note for Tauros Message-ID: <cy4pr02mb2872cfb6eb47cdc20d8042e190...@cy4pr02mb2872.namprd02.prod.outlook.com<mailto:cy4pr02mb2872cfb6eb47cdc20d8042e190...@cy4pr02mb2872.namprd02.prod.outlook.com>> Content-Type: text/plain; charset="us-ascii" The release for Project Clearwater sprint "Tauros" has been cut. The code for this release is tagged as release-113 in GitHub. This release includes the following bug fixes: * REGISTER expires 0 gets 401 Unauthorized rather than deregistering (https://github.com/Metaswitch/sprout/issues/1640) * AKAv2 authentication is not thread-safe (https://github.com/Metaswitch/sprout/issues/1600) * Deregistration in GR deployment causes sprout to send 2 deregistration HTTP requests to homestead (https://github.com/Metaswitch/sprout/issues/1555) * scary red cassandra logs when upgrading (https://github.com/Metaswitch/homestead/issues/396) * Homestead returns inconsistent HTTP errors (500 and 503) for the same underlying error (THRIFT_EAGAIN) (https://github.com/Metaswitch/homestead/issues/389) * SAS logs for Cassandra database failures are too low-level (https://github.com/Metaswitch/homestead/issues/388) * Errors reported when upgrading the Clearwater packages (https://github.com/Metaswitch/homestead/issues/333) * Homestead provides no useful indication why it fails for a MAA with an unsupported authentication scheme (https://github.com/Metaswitch/homestead/issues/308) * Misleading SAS log when running non-FT deployment (https://github.com/Metaswitch/homestead/issues/293) * Homestead-prov/Homer are spamming ping handler errors to syslog (https://github.com/Metaswitch/crest/issues/313) * Log spam in Crest (https://github.com/Metaswitch/crest/issues/297) * Crest based processes will sometimes not recovery properly if Cassandra fails (https://github.com/Metaswitch/crest/issues/283) * SyntaxWarning Error when installing Homer/Homestead (https://github.com/Metaswitch/crest/issues/216) * Running run-in-signaling-namespace not as sudo gives a misspelt error message (https://github.com/Metaswitch/clearwater-infrastructure/issues/398) * config-manager crashes if /etc/clearwater/shared_config contains non-ASCII content (https://github.com/Metaswitch/clearwater-infrastructure/issues/344) * Error log in syslog when cluster manager is restarted (https://github.com/Metaswitch/clearwater-etcd/issues/372) * check_cluster_state shows the clusters in a different order when run several times (https://github.com/Metaswitch/clearwater-etcd/issues/365) * In a 4-node deployment, etcd failed to start on one node and couldn't be trivially fixed (https://github.com/Metaswitch/clearwater-etcd/issues/359) * Cluster manager logs repeated errors in normal operation (https://github.com/Metaswitch/clearwater-etcd/issues/324) * Warning text when installing pyzmq (https://github.com/Metaswitch/clearwater-etcd/issues/258) * Mark node failed hangs when run on one of several failed nodes (https://github.com/Metaswitch/clearwater-etcd/issues/250) To upgrade to this release, follow the instructions at http://docs.projectclearwater.org/en/stable/Upgrading_a_Clearwater_deployment.html. If you are deploying an all-in-one node, the standard image (http://vm-images.cw-ngv.com/cw-aio.ova) has been updated for this release. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.projectclearwater.org/pipermail/clearwater_lists.projectclearwater.org/attachments/20161220/7ecd4b57/attachment.html> ------------------------------ Subject: Digest Footer _______________________________________________ Clearwater mailing list [email protected]<mailto:[email protected]> http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org ------------------------------ End of Clearwater Digest, Vol 44, Issue 11 ****************************************** ________________________________
_______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org
