Hi,

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 Mahesh Kumar
Sent: 04 January 2017 06:02
To: [email protected]
Subject: [Project Clearwater] Error stack.cpp:325: Failed to start UDP 
transport for port 172 (Permission denied)

[          ]
Hello Team,

I'm trying to deploy Clearwater on an Open-stack environment. I'm encountering

an issue on the sprout node.

!!!!!!!!!!monit status!!!!!!!!!!!!!!!

[sprout]ubuntu@sprout-f5806:/var/log/sprout$ sudo monit summary
Monit 5.18.1 uptime: 1d 0h 7m
 Service Name                     Status                      Type
 node-sprout-f5806.clearwater...  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_ping                       Status ok                   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 failed               Program
 poll_etcd                        Status ok                   Program
!!!!!!!!!!error logs!!!!!!!!!!!!!!!!

04-01-2017 04:56:56.776 UTC Error stack.cpp:325: Failed to start UDP transport 
for port 172 (Permission denied)
04-01-2017 04:56:56.776 UTC Error pjsip: Assert failed: stack.cpp:767 status == 0
04-01-2017 04:56:56.776 UTC Error main.cpp:1771: Error initializing stack 
Permission denied
04-01-2017 04:57:39.187 UTC Status utils.cpp:631: Log level set to 2
04-01-2017 04:57:39.187 UTC Status main.cpp:1420: Access logging enabled to 
/var/log/sprout
04-01-2017 04:57:39.188 UTC Warning signalhandler.h:115: SIGNAL already hooked
04-01-2017 04:57:39.188 UTC Warning main.cpp:1465: SAS server option was 
invalid or not configured - SAS is disabled
04-01-2017 04:57:39.188 UTC Status snmp_agent.cpp:117: AgentX agent initialised
04-01-2017 04:57:39.190 UTC Status load_monitor.cpp:105: Constructing 
LoadMonitor
04-01-2017 04:57:39.190 UTC Status load_monitor.cpp:106:    Target latency 
(usecs)   : 100000
04-01-2017 04:57:39.190 UTC Status load_monitor.cpp:107:    Max bucket size     
     : 1000
04-01-2017 04:57:39.190 UTC Status load_monitor.cpp:108:    Initial token fill 
rate/s: 250.000000
04-01-2017 04:57:39.190 UTC Status load_monitor.cpp:109:    Min token fill 
rate/s    : 10.000000
04-01-2017 04:57:39.190 UTC Status dnscachedresolver.cpp:150: Creating Cached 
Resolver using servers:
04-01-2017 04:57:39.191 UTC Status dnscachedresolver.cpp:160:     172.16.0.94
04-01-2017 04:57:39.191 UTC Status sipresolver.cpp:60: Created SIP resolver

!!!!!!!!!!!!!!!clearwater-version!!!!!!!!!!
[sprout]ubuntu@sprout-f5806:/var/log/sprout$ 
/usr/share/clearwater/bin/clearwater-version
clearwater-cluster-manager               1.0-161212.142314
clearwater-config-manager                1.0-161212.142314
clearwater-diags-monitor                 1.0-161216.095808
clearwater-etcd                          1.0-161212.142314
clearwater-infrastructure                1.0-161216.095808
clearwater-log-cleanup                   1.0-161216.095808
clearwater-management                    1.0-161212.142314
clearwater-monit                         5.18-161212.145429
clearwater-nginx                         1.0-161215.173010
clearwater-queue-manager                 1.0-161212.142314
clearwater-socket-factory                1.0-161216.095808
clearwater-tcp-scalability               1.0-161216.095808
sprout                                   1.0-161216.102753
sprout-base                              1.0-161216.102753
sprout-bgcf                              1.0-161216.102753
sprout-icscf                             1.0-161216.102753
sprout-mmtel-as                          1.0-161216.102753
sprout-scscf                             1.0-161216.102753


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,

Regards,
Mahesh Kumar
TATA Consultancy Service
_______________________________________________
Clearwater mailing list
[email protected]
http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org

Reply via email to