[Freeswitch-users] Intermittent Long Delay On Startup Centos 7.1
sausageside at yahoo.com
Sat Oct 24 17:03:01 MSD 2015
I was running the following :Centos 7.1FreeSWITCH Version 1.7.0+git~20151021T165609Z~9fee9bc613~64bit (git9fee9bc 2015-10-21 16:56:09Z 64bit)Digital Ocean hosted "droplet", 2gig ram, 40 gig SSD, 2 CPU
though it also happens with FreeSWITCH Version 1.6.2+git~20150930T182428Z~c0c3c38f64~64bit (git c0c3c38 2015-09-30 18:24:28Z 64bit)
I have asked this on SO as well : http://stackoverflow.com/q/33305393/1642105
Intermittently, but about as often as 1 in 3, the start up process for Freeswitch pauses for a very long time (variable, but has been as long as 14 minutes). Running from the terminal window, here's the output. Notice the time between the "Add Task 2" and the next line :# /usr/bin/freeswitch -nonat -core -db /dev/shm -log /usr/local/freeswitch/log -conf /usr/local/freeswitch/conf -run /usr/local/freeswitch/run
2015-10-23 15:40:14.160101 [INFO] switch_event.c:685 Activate Eventing Engine.
2015-10-23 15:40:14.170805 [WARNING] switch_event.c:656 Create additional event dispatch thread 0
2015-10-23 15:40:14.272850 [INFO] switch_core_sqldb.c:3381 Opening DB
2015-10-23 15:40:14.282317 [INFO] switch_core_sqldb.c:1693 CORE Starting SQL thread.
2015-10-23 15:40:14.285266 [NOTICE] switch_scheduler.c:183 Starting task thread
2015-10-23 15:40:14.293743 [DEBUG] switch_scheduler.c:249 Added task 1 heartbeat (core) to run at 1445611214
2015-10-23 15:40:14.293837 [DEBUG] switch_scheduler.c:249 Added task 2 check_ip (core) to run at 1445611214
2015-10-23 15:49:47.883158 [NOTICE] switch_core.c:1386 Created ip list rfc6598.auto default (deny)If I spin up a virgin 6.7 machine (droplet) and follow my exact same install script, the longest pause I get at that spot is about 14 seconds, which is fine. Apart from the operating systems as supplied the two installations are similar.
Does anyone have a guess as to why does it take so long on centos 7.1, and not on 6.7?And what is that check_ip doing? An amateurs look at the check_ip() in the source shows it resolving a hostname, but if I run a wireshark trace on all network interfaces it shows no activity at that point relating to DNS lookups or anything (it does if I ping google.com so I think I would have seen it). That's the same on 6.7 as well, so it's obviously not meant to, bit I'm not sure how else to determine what it's waiting for.
-------------- next part --------------
An HTML attachment was scrubbed...
Join us at ClueCon 2016 Aug 8-12, 2016
More information about the FreeSWITCH-users