[asterisk-bugs] [JIRA] (ASTERISK-24090) app_voicemail reloads result in leaked IMAP sockets.
Rusty Newton (JIRA)
noreply at issues.asterisk.org
Tue Jul 22 12:35:56 CDT 2014
Rusty Newton created ASTERISK-24090:
---------------------------------------
Summary: app_voicemail reloads result in leaked IMAP sockets.
Key: ASTERISK-24090
URL: https://issues.asterisk.org/jira/browse/ASTERISK-24090
Project: Asterisk
Issue Type: Bug
Security Level: None
Components: Applications/app_voicemail/IMAP
Affects Versions: SVN, 1.8.22.0
Environment: Free pbx distro
Reporter: Louis Jocelyn Paquet
When we do a voicemail reload, the application is recreating new IMAP connection whithout closing the active one. This is resulting with extra open connection. After about 30 minutes, the old connections moving in states close_wait and stay like this until we restart asterisk.
For my production server with 65 users using IMAP storage vor voicemail, this is resulting with 65 extra IMAP connections every time we do an apply. So after 1 week, we got all IMAP TCP socket use and we need to restart Asterisk because the server cannot establish new IMAP connections.
I did some more investigation, here more details about the issue. I need to know who is the right group to adress this issue (free pbx or asterisk)
So, I reproduce the issue on a small server were I have only 1 custommer with IMAP connection. I have the same issue on my server were I have 66 custommer with imap voicemail.
So to reproduce the issue, you just have to connect one ATA (sip client) on a extension with an IMAP account on an other server (Imap storage)
So in the server, if I do tne netstat, I can see a conncetions.
{noformat}
[root at voip5b ~]# netstat -ap |grep imap
tcp 0 0 192.168.101.21:48237 publicIPhidden:imap ESTABLISHED 18675/asterisk
tcp 0 0 192.168.101.21:48236 publicIPhidden:imap ESTABLISHED 18675/asterisk
{noformat}
If I do an voicemail reload, you will see that the application is recreating new connections whithout closing the prevoius one. after 25-30 minutes, the old connections come in close_wait status and never get completely close. After a week, all port become use and the server cannot establish imap connections.
{noformat}
[root at voip5b ~]# asterisk -r
Asterisk 1.8.22.0, Copyright (C) 1999 - 2012 Digium, Inc. and others.
Created by Mark Spencer <markster at digium.com>
Asterisk comes with ABSOLUTELY NO WARRANTY; type 'core show warranty' for details.
This is free software, with components licensed under the GNU General Public
License version 2 and other licenses; you are welcome to redistribute it under
certain conditions. Type 'core show license' for details.
=========================================================================
Connected to Asterisk 1.8.22.0 currently running on voip5b (pid = 18675)
Verbosity is at least 3
voip5b*CLI> voicemail reload
Reloading voicemail configuration...
== Parsing '/etc/asterisk/voicemail.conf': == Found
== Parsing '/etc/asterisk/vm_general.inc': == Found
== Parsing '/etc/asterisk/vm_email.inc': == Found
voip5b*CLI> exit
{noformat}
{noformat}
[root at voip5b ~]# netstat -ap |grep imap
tcp 0 0 192.168.101.21:48239 publicIPhidden:imap ESTABLISHED 18675/asterisk
tcp 0 0 192.168.101.21:48237 publicIPhidden:imap ESTABLISHED 18675/asterisk
tcp 0 0 192.168.101.21:48240 publicIPhidden:imap ESTABLISHED 18675/asterisk
tcp 0 0 192.168.101.21:48236 publicIPhidden:imap ESTABLISHED 18675/asterisk
{noformat}
This is what happening on my production server (66 custommers). 66 IMAP new connections every time we do an apply in free pbx.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list