[Freeswitch-users] FS shutdown not closing TCP port causes TIME_WAIT problems
mario_fs at mgtech.com
Tue Apr 3 19:53:22 MSD 2012
For anyone who may run into this see "FS shutdown not closing TCP port causes TIME_WAIT problems" for follow up and solution.
On Apr 2, 2012, at 1:33 PM, Mario G wrote:
> That's what I was thinking, trying to figure out how now. Will post a solution when I get one.
> On Apr 2, 2012, at 1:28 PM, Anthony Minessale wrote:
>>> From what I see, sofia uses the REUSEADDR flag so I will bet its yet
>> another MAC specific thing.
>> I am not really sure what you can do since you tend to find issues
>> deep inside libsofia-sip and its portability to OSX.
>> Maybe make your restart script sleep a bit?
>> su_setreuseaddr(socket, 1);
>> On Mon, Apr 2, 2012 at 3:13 PM, Mario G <mario_fs at mgtech.com> wrote:
>>> If FS is shutdown and started too quickly, the internal profile ip/port stays in use and FS will fail to start it. After searching on the wen I found many references to TIME_WAIT but all fixes were to the program source. So I am wondering if when FS/sofia shuts down they are not releasing the ip/port for internal. If it's true, I found some source changes to solve it. Google "TIME-WAIT" and you'll find lots of good stuff like http://serverfault.com/questions/329845/how-to-forcibly-close-a-socket-in-time-wait. Apparently there is no way to free up the port manually. Help/comments anyone?
>>> Mario G
>>> Professional FreeSWITCH Consulting Services:
>>> consulting at freeswitch.org
>>> Official FreeSWITCH Sites
>>> FreeSWITCH-users mailing list
>>> FreeSWITCH-users at lists.freeswitch.org
>> Anthony Minessale II
> Professional FreeSWITCH Consulting Services:
> consulting at freeswitch.org
> Official FreeSWITCH Sites
> FreeSWITCH-users mailing list
> FreeSWITCH-users at lists.freeswitch.org
-------------- next part --------------
An HTML attachment was scrubbed...
Join us at ClueCon 2011 Aug 9-11, 2011
More information about the FreeSWITCH-users