One of my users, whose phone has BLF lines, is having trouble accessing voicemail. The logs say the core database is locked. It is not clear if that is what is causing the inability to access voicemail. Any ideas? 2013-04-11 11:14:31.962286 [ERR] switch_core_sqldb.c:579 NATIVE SQL ERR [database is locked] insert into sip_subscriptions (proto,sip_user,sip_host,sub_to_user,sub_to_host,presence_hosts,event,contact,call_id,full_from,full_via,expires,user_agent,accept,profile_name,hostname,network_port,network_ip,version,orig_proto, full_to) values ('sip','519','xxx.com','519','xxx.com','xxx.com,192.168.4.1','line-seize','"519" <sip:519@192.168.4.235>','540bafdc-5146c237-f2c1bfea@192.168.4.235','"519" < sip:519@xxx.com>;tag=AB12B2E0-A28C235B','SIP/2.0/UDP 192.168.4.235;branch=z9hG4bK3073a02e92D29019',1365704072,'PolycomSoundPointIP-SPIP_320-UA/ 3.3.5.0247','','phone','pbx.xxx.com','5060','192.168.4.235',-1,'','< sip:519@xxx.com>;tag=GvUHrcCb8WWl') 2013-04-11 11:14:32.222286 [ERR] switch_core_sqldb.c:579 NATIVE SQL ERR [database is locked] BEGIN EXCLUSIVE 2013-04-11 11:14:32.222286 [CRIT] switch_core_sqldb.c:1679 ERROR [database is locked] 2013-04-11 11:14:32.222286 [ERR] switch_core_sqldb.c:579 NATIVE SQL ERR [cannot commit - no transaction is active] COMMIT 2013-04-11 11:15:02.102979 [ERR] switch_core_sqldb.c:579 NATIVE SQL ERR [database is locked] insert into sip_dialogs (sip_from_user,sip_from_host,call_info,call_info_state,hostname,expires,rcd,profile_name) values ('519','xxx.com','appearance-index=1','seized','pbx.xxx.com ',1365704101,1365704071,'phone') 2013-04-11 11:15:02.502977 [ERR] switch_core_sqldb.c:579 NATIVE SQL ERR [database is locked] BEGIN EXCLUSIVE 2013-04-11 11:15:02.502977 [CRIT] switch_core_sqldb.c:1679 ERROR [database is locked] 2013-04-11 11:15:02.502977 [ERR] switch_core_sqldb.c:579 NATIVE SQL ERR [cannot commit - no transaction is active] COMMIT
What database are you using? Sqlite? MySQL? PostgreSQL? Check if there's anything else connected to the same database and what queries are being run. Perhaps something is holding a lock on the voicemail table. -Steve On 11 April 2013 19:20, Steven Schoch <schoch+freeswitch.org@xwin32.com>wrote:
One of my users, whose phone has BLF lines, is having trouble accessing voicemail. The logs say the core database is locked. It is not clear if that is what is causing the inability to access voicemail. Any ideas?
2013-04-11 11:14:31.962286 [ERR] switch_core_sqldb.c:579 NATIVE SQL ERR [database is locked] insert into sip_subscriptions (proto,sip_user,sip_host,sub_to_user,sub_to_host,presence_hosts,event,contact,call_id,full_from,full_via,expires,user_agent,accept,profile_name,hostname,network_port,network_ip,version,orig_proto, full_to) values ('sip','519','xxx.com','519','xxx.com','xxx.com,192.168.4.1','line-seize','"519" <sip:519@192.168.4.235>','540bafdc-5146c237-f2c1bfea@192.168.4.235','"519" <sip:519@xxx.com>;tag=AB12B2E0-A28C235B','SIP/2.0/UDP 192.168.4.235;branch=z9hG4bK3073a02e92D29019',1365704072,'PolycomSoundPointIP-SPIP_320-UA/ 3.3.5.0247','','phone','pbx.xxx.com','5060','192.168.4.235',-1,'','< sip:519@xxx.com>;tag=GvUHrcCb8WWl') 2013-04-11 11:14:32.222286 [ERR] switch_core_sqldb.c:579 NATIVE SQL ERR [database is locked] BEGIN EXCLUSIVE 2013-04-11 11:14:32.222286 [CRIT] switch_core_sqldb.c:1679 ERROR [database is locked] 2013-04-11 11:14:32.222286 [ERR] switch_core_sqldb.c:579 NATIVE SQL ERR [cannot commit - no transaction is active] COMMIT 2013-04-11 11:15:02.102979 [ERR] switch_core_sqldb.c:579 NATIVE SQL ERR [database is locked] insert into sip_dialogs (sip_from_user,sip_from_host,call_info,call_info_state,hostname,expires,rcd,profile_name) values ('519','xxx.com','appearance-index=1','seized','pbx.xxx.com ',1365704101,1365704071,'phone') 2013-04-11 11:15:02.502977 [ERR] switch_core_sqldb.c:579 NATIVE SQL ERR [database is locked] BEGIN EXCLUSIVE 2013-04-11 11:15:02.502977 [CRIT] switch_core_sqldb.c:1679 ERROR [database is locked] 2013-04-11 11:15:02.502977 [ERR] switch_core_sqldb.c:579 NATIVE SQL ERR [cannot commit - no transaction is active] COMMIT
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
On Thu, Apr 11, 2013 at 11:44 AM, Steven Ayre <steveayre@gmail.com> wrote:
What database are you using? Sqlite? MySQL? PostgreSQL?
The one that came with FreeSWITCH (Sqlite). Check if there's anything else connected to the same database and what
queries are being run. Perhaps something is holding a lock on the voicemail table.
FreeSWITCH is the only thing that is connected to the database. I have no other programs on that machine accessing that database. The problem eventually went away after letting it sit for a couple of minutes. I suspect the DB locked was just a symptom of the real problem which may have happened earlier. The user couldn't connect to VM for some reason, so he made multiple tries in rapid succession, which locked the database somehow. The trouble is that I can't reproduce it. -- Steve
I'd be interested to hear more about this.. as far as I knew the internal SQLite DB wouldn't become culprit to this sort of problem. Could any core devs comment on this? Cal On Thu, Apr 11, 2013 at 9:01 PM, Steven Schoch < schoch+freeswitch.org@xwin32.com> wrote:
On Thu, Apr 11, 2013 at 11:44 AM, Steven Ayre <steveayre@gmail.com> wrote:
What database are you using? Sqlite? MySQL? PostgreSQL?
The one that came with FreeSWITCH (Sqlite).
Check if there's anything else connected to the same database and what
queries are being run. Perhaps something is holding a lock on the voicemail table.
FreeSWITCH is the only thing that is connected to the database. I have no other programs on that machine accessing that database.
The problem eventually went away after letting it sit for a couple of minutes. I suspect the DB locked was just a symptom of the real problem which may have happened earlier. The user couldn't connect to VM for some reason, so he made multiple tries in rapid succession, which locked the database somehow. The trouble is that I can't reproduce it.
-- Steve
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
participants (3)
-
Cal Leeming [Simplicity Media Ltd]
-
Steven Ayre
-
Steven Schoch