Greetings, I have a freeswitch installation that is configured to use MySQL (via ODBC) in switch.xml. Today we had one of our freeswitch hosts go out of service with this error: *2018-01-03 00:14:51.340034 [ERR] switch_core_sqldb.c:587 NATIVE SQL ERR [database disk image is malformed]* *delete from sip_registrations where sip_user='rcampos1' and sip_host='10.201.0.94'* Through some searching, we determined that is the result of the sqlite db becoming corrupt. There were no power events, but it simply stopped working. Now... I don't even want to use sqllite. We have MySQL configured and is working properly. Here is our config from switch.xml <param name="core-db-dsn" value="freeswitch:freeswitch:freeswitch" /> <param name="auto-create-schemas" value="true"/> <param name="auto-clear-sql" value="true"/> <param name="core-dbtype" value="MYSQL"/> The registrations and calls ARE showing up in MySQL, so the ODBC connection is working. Why would Freeswitch continue to use SQLite even though we have configured the core to use MySQL? Even after clearing out the /freeswtich/db directory, upon restart, the following files show up again. It's as if Freeswitch is writing to both SQLite and MySQL. -rw-r--r-- 1 14K Jan 3 00:16 call_limit.db -rw-r--r-- 1 5.0K Jan 3 00:16 fifo.db -rw-r--r-- 1 93K Jan 3 00:16 sofia_reg_external.db -rw-r--r-- 1 99K Jan 3 00:26 sofia_reg_internal.db Any help would be greatly appreciated. Thanks, Geoff
I finally figured it out. I didn't realize that I needed a specific odbc-dsn parameter in both the internal and external sip_profiles. Adding the following to both of my profiles seems to have resolved the issues. <param name="odbc-dsn" value="freeswitch:freeswitch:freeswitch"/> I wish the documentation on the various ODBC settings was a little more clear. Anyway... all good now, we are no longer relying on corruption prone SQLite for our registrations. Thanks, Geoff *GEOFF MINA*Chief Executive Officer Connect First / Contact Center Solutions, Built Better. 3101 Iris Ave #200, Boulder, CO 80301 720.335.5924 <%28720%29%20335-5924> gmina@connectfirst.com / www.connectfirst.com <http://connectfirst.com/> [image: https://docs.google.com/uc?export=download&id=0B5b6KnVfm9lJTlFrQzRVUjJ2ZVE&r...] This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. On Tue, Jan 2, 2018 at 5:26 PM, Geoff Mina <gmina@connectfirst.com> wrote:
Greetings, I have a freeswitch installation that is configured to use MySQL (via ODBC) in switch.xml. Today we had one of our freeswitch hosts go out of service with this error:
*2018-01-03 00:14:51.340034 [ERR] switch_core_sqldb.c:587 NATIVE SQL ERR [database disk image is malformed]* *delete from sip_registrations where sip_user='rcampos1' and sip_host='10.201.0.94'*
Through some searching, we determined that is the result of the sqlite db becoming corrupt. There were no power events, but it simply stopped working. Now... I don't even want to use sqllite. We have MySQL configured and is working properly. Here is our config from switch.xml
<param name="core-db-dsn" value="freeswitch:freeswitch:freeswitch" /> <param name="auto-create-schemas" value="true"/> <param name="auto-clear-sql" value="true"/> <param name="core-dbtype" value="MYSQL"/>
The registrations and calls ARE showing up in MySQL, so the ODBC connection is working. Why would Freeswitch continue to use SQLite even though we have configured the core to use MySQL? Even after clearing out the /freeswtich/db directory, upon restart, the following files show up again. It's as if Freeswitch is writing to both SQLite and MySQL.
-rw-r--r-- 1 14K Jan 3 00:16 call_limit.db -rw-r--r-- 1 5.0K Jan 3 00:16 fifo.db -rw-r--r-- 1 93K Jan 3 00:16 sofia_reg_external.db -rw-r--r-- 1 99K Jan 3 00:26 sofia_reg_internal.db
Any help would be greatly appreciated.
Thanks, Geoff
Do you want to contribute to our documentation by clarifying it? I can give you access to the Confluence editors. Em qua, 3 de jan de 2018 às 00:22, Geoff Mina <gmina@connectfirst.com> escreveu:
I finally figured it out. I didn't realize that I needed a specific odbc-dsn parameter in both the internal and external sip_profiles. Adding the following to both of my profiles seems to have resolved the issues.
<param name="odbc-dsn" value="freeswitch:freeswitch:freeswitch"/>
I wish the documentation on the various ODBC settings was a little more clear. Anyway... all good now, we are no longer relying on corruption prone SQLite for our registrations.
Thanks, Geoff
*GEOFF MINA*Chief Executive Officer Connect First / Contact Center Solutions, Built Better.
3101 Iris Ave #200, Boulder, CO 80301 720.335.5924 <%28720%29%20335-5924> gmina@connectfirst.com / www.connectfirst.com <http://connectfirst.com/>
[image: https://docs.google.com/uc?export=download&id=0B5b6KnVfm9lJTlFrQzRVUjJ2ZVE&r...]
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager.
On Tue, Jan 2, 2018 at 5:26 PM, Geoff Mina <gmina@connectfirst.com> wrote:
Greetings, I have a freeswitch installation that is configured to use MySQL (via ODBC) in switch.xml. Today we had one of our freeswitch hosts go out of service with this error:
*2018-01-03 00:14:51.340034 [ERR] switch_core_sqldb.c:587 NATIVE SQL ERR [database disk image is malformed]* *delete from sip_registrations where sip_user='rcampos1' and sip_host='10.201.0.94'*
Through some searching, we determined that is the result of the sqlite db becoming corrupt. There were no power events, but it simply stopped working. Now... I don't even want to use sqllite. We have MySQL configured and is working properly. Here is our config from switch.xml
<param name="core-db-dsn" value="freeswitch:freeswitch:freeswitch" /> <param name="auto-create-schemas" value="true"/> <param name="auto-clear-sql" value="true"/> <param name="core-dbtype" value="MYSQL"/>
The registrations and calls ARE showing up in MySQL, so the ODBC connection is working. Why would Freeswitch continue to use SQLite even though we have configured the core to use MySQL? Even after clearing out the /freeswtich/db directory, upon restart, the following files show up again. It's as if Freeswitch is writing to both SQLite and MySQL.
-rw-r--r-- 1 14K Jan 3 00:16 call_limit.db -rw-r--r-- 1 5.0K Jan 3 00:16 fifo.db -rw-r--r-- 1 93K Jan 3 00:16 sofia_reg_external.db -rw-r--r-- 1 99K Jan 3 00:26 sofia_reg_internal.db
Any help would be greatly appreciated.
Thanks, Geoff
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.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
Sure. I can at least contribute the knowledge gained last night. Thanks. Geoff
On Jan 3, 2018, at 7:01 AM, Ítalo Rossi <italo@freeswitch.org> wrote:
Do you want to contribute to our documentation by clarifying it? I can give you access to the Confluence editors.
Em qua, 3 de jan de 2018 às 00:22, Geoff Mina <gmina@connectfirst.com> escreveu: I finally figured it out. I didn't realize that I needed a specific odbc-dsn parameter in both the internal and external sip_profiles. Adding the following to both of my profiles seems to have resolved the issues.
<param name="odbc-dsn" value="freeswitch:freeswitch:freeswitch"/>
I wish the documentation on the various ODBC settings was a little more clear. Anyway... all good now, we are no longer relying on corruption prone SQLite for our registrations.
Thanks, Geoff
GEOFF MINA Chief Executive Officer Connect First / Contact Center Solutions, Built Better.
3101 Iris Ave #200, Boulder, CO 80301 720.335.5924 gmina@connectfirst.com / www.connectfirst.com
<image002.png>
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager.
On Tue, Jan 2, 2018 at 5:26 PM, Geoff Mina <gmina@connectfirst.com> wrote: Greetings, I have a freeswitch installation that is configured to use MySQL (via ODBC) in switch.xml. Today we had one of our freeswitch hosts go out of service with this error:
2018-01-03 00:14:51.340034 [ERR] switch_core_sqldb.c:587 NATIVE SQL ERR [database disk image is malformed] delete from sip_registrations where sip_user='rcampos1' and sip_host='10.201.0.94'
Through some searching, we determined that is the result of the sqlite db becoming corrupt. There were no power events, but it simply stopped working. Now... I don't even want to use sqllite. We have MySQL configured and is working properly. Here is our config from switch.xml
<param name="core-db-dsn" value="freeswitch:freeswitch:freeswitch" /> <param name="auto-create-schemas" value="true"/> <param name="auto-clear-sql" value="true"/> <param name="core-dbtype" value="MYSQL"/>
The registrations and calls ARE showing up in MySQL, so the ODBC connection is working. Why would Freeswitch continue to use SQLite even though we have configured the core to use MySQL? Even after clearing out the /freeswtich/db directory, upon restart, the following files show up again. It's as if Freeswitch is writing to both SQLite and MySQL.
-rw-r--r-- 1 14K Jan 3 00:16 call_limit.db -rw-r--r-- 1 5.0K Jan 3 00:16 fifo.db -rw-r--r-- 1 93K Jan 3 00:16 sofia_reg_external.db -rw-r--r-- 1 99K Jan 3 00:26 sofia_reg_internal.db
Any help would be greatly appreciated.
Thanks, Geoff
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.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
Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.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
Did you figure out the root of the corruption issue? Sqlite has proven stable in FS over trillions of calls in both small and large installs so I wonder whats actually causing the issue you are seeing. From: FreeSWITCH-users [mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of Geoff Mina Sent: Tuesday, January 2, 2018 9:21 PM To: freeswitch-users@lists.freeswitch.org Subject: Re: [Freeswitch-users] sqlite DB - help?! I finally figured it out. I didn't realize that I needed a specific odbc-dsn parameter in both the internal and external sip_profiles. Adding the following to both of my profiles seems to have resolved the issues. <param name="odbc-dsn" value="freeswitch:freeswitch:freeswitch"/> I wish the documentation on the various ODBC settings was a little more clear. Anyway... all good now, we are no longer relying on corruption prone SQLite for our registrations. Thanks, Geoff GEOFF MINA Chief Executive Officer Connect First / Contact Center Solutions, Built Better. 3101 Iris Ave #200, Boulder, CO 80301 <tel:%28720%29%20335-5924> 720.335.5924 <mailto:gmina@connectfirst.com> gmina@connectfirst.com / <http://connectfirst.com/> www.connectfirst.com This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. On Tue, Jan 2, 2018 at 5:26 PM, Geoff Mina <gmina@connectfirst.com <mailto:gmina@connectfirst.com> > wrote: Greetings, I have a freeswitch installation that is configured to use MySQL (via ODBC) in switch.xml. Today we had one of our freeswitch hosts go out of service with this error: 2018-01-03 00:14:51.340034 [ERR] switch_core_sqldb.c:587 NATIVE SQL ERR [database disk image is malformed] delete from sip_registrations where sip_user='rcampos1' and sip_host='10.201.0.94' Through some searching, we determined that is the result of the sqlite db becoming corrupt. There were no power events, but it simply stopped working. Now... I don't even want to use sqllite. We have MySQL configured and is working properly. Here is our config from switch.xml <param name="core-db-dsn" value="freeswitch:freeswitch:freeswitch" /> <param name="auto-create-schemas" value="true"/> <param name="auto-clear-sql" value="true"/> <param name="core-dbtype" value="MYSQL"/> The registrations and calls ARE showing up in MySQL, so the ODBC connection is working. Why would Freeswitch continue to use SQLite even though we have configured the core to use MySQL? Even after clearing out the /freeswtich/db directory, upon restart, the following files show up again. It's as if Freeswitch is writing to both SQLite and MySQL. -rw-r--r-- 1 14K Jan 3 00:16 call_limit.db -rw-r--r-- 1 5.0K Jan 3 00:16 fifo.db -rw-r--r-- 1 93K Jan 3 00:16 sofia_reg_external.db -rw-r--r-- 1 99K Jan 3 00:26 sofia_reg_internal.db Any help would be greatly appreciated. Thanks, Geoff
It only happened the once. Didn’t look into root cause - just eliminated the problem. This is running on an SSD backed Amazon EC2 instance. The hypervisor, vm, and FS all have been up and running for months without issue. No restarts or power cycles. I tried to use sqlite3 to inspect the file, but it wouldn’t open the DB.
On Jan 3, 2018, at 7:33 AM, Ken Rice <krice@freeswitch.org> wrote:
Did you figure out the root of the corruption issue? Sqlite has proven stable in FS over trillions of calls in both small and large installs so I wonder whats actually causing the issue you are seeing.
From: FreeSWITCH-users [mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of Geoff Mina Sent: Tuesday, January 2, 2018 9:21 PM To: freeswitch-users@lists.freeswitch.org Subject: Re: [Freeswitch-users] sqlite DB - help?!
I finally figured it out. I didn't realize that I needed a specific odbc-dsn parameter in both the internal and external sip_profiles. Adding the following to both of my profiles seems to have resolved the issues.
<param name="odbc-dsn" value="freeswitch:freeswitch:freeswitch"/>
I wish the documentation on the various ODBC settings was a little more clear. Anyway... all good now, we are no longer relying on corruption prone SQLite for our registrations.
Thanks, Geoff
GEOFF MINA Chief Executive Officer Connect First / Contact Center Solutions, Built Better.
3101 Iris Ave #200, Boulder, CO 80301 720.335.5924 gmina@connectfirst.com / www.connectfirst.com
<image001.png>
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager.
On Tue, Jan 2, 2018 at 5:26 PM, Geoff Mina <gmina@connectfirst.com> wrote: Greetings, I have a freeswitch installation that is configured to use MySQL (via ODBC) in switch.xml. Today we had one of our freeswitch hosts go out of service with this error:
2018-01-03 00:14:51.340034 [ERR] switch_core_sqldb.c:587 NATIVE SQL ERR [database disk image is malformed] delete from sip_registrations where sip_user='rcampos1' and sip_host='10.201.0.94'
Through some searching, we determined that is the result of the sqlite db becoming corrupt. There were no power events, but it simply stopped working. Now... I don't even want to use sqllite. We have MySQL configured and is working properly. Here is our config from switch.xml
<param name="core-db-dsn" value="freeswitch:freeswitch:freeswitch" /> <param name="auto-create-schemas" value="true"/> <param name="auto-clear-sql" value="true"/> <param name="core-dbtype" value="MYSQL"/>
The registrations and calls ARE showing up in MySQL, so the ODBC connection is working. Why would Freeswitch continue to use SQLite even though we have configured the core to use MySQL? Even after clearing out the /freeswtich/db directory, upon restart, the following files show up again. It's as if Freeswitch is writing to both SQLite and MySQL.
-rw-r--r-- 1 14K Jan 3 00:16 call_limit.db -rw-r--r-- 1 5.0K Jan 3 00:16 fifo.db -rw-r--r-- 1 93K Jan 3 00:16 sofia_reg_external.db -rw-r--r-- 1 99K Jan 3 00:26 sofia_reg_internal.db
Any help would be greatly appreciated.
Thanks, Geoff
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.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
Hi, Do you have wss endpoints? On 01/03/2018 04:32 PM, Geoff Mina wrote:
It only happened the once. Didn’t look into root cause - just eliminated the problem.
This is running on an SSD backed Amazon EC2 instance. The hypervisor, vm, and FS all have been up and running for months without issue. No restarts or power cycles.
I tried to use sqlite3 to inspect the file, but it wouldn’t open the DB.
On Jan 3, 2018, at 7:33 AM, Ken Rice <krice@freeswitch.org <mailto:krice@freeswitch.org>> wrote:
Did you figure out the root of the corruption issue? Sqlite has proven stable in FS over trillions of calls in both small and large installs so I wonder whats actually causing the issue you are seeing.
*From:* FreeSWITCH-users [mailto:freeswitch-users-bounces@lists.freeswitch.org] *On Behalf Of *Geoff Mina *Sent:* Tuesday, January 2, 2018 9:21 PM *To:* freeswitch-users@lists.freeswitch.org <mailto:freeswitch-users@lists.freeswitch.org> *Subject:* Re: [Freeswitch-users] sqlite DB - help?!
I finally figured it out. I didn't realize that I needed a specific odbc-dsn parameter in both the internal and external sip_profiles. Adding the following to both of my profiles seems to have resolved the issues.
<param name="odbc-dsn" value="freeswitch:freeswitch:freeswitch"/>
I wish the documentation on the various ODBC settings was a little more clear. Anyway... all good now, we are no longer relying on corruption prone SQLite for our registrations.
Thanks,
Geoff
*GEOFF MINA_ _*Chief Executive Officer Connect First / Contact Center Solutions, Built Better.
3101 Iris Ave #200, Boulder, CO 80301 720.335.5924 <tel:%28720%29%20335-5924> gmina@connectfirst.com <mailto:gmina@connectfirst.com> / www.connectfirst.com <http://connectfirst.com/>
<image001.png>
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager.
On Tue, Jan 2, 2018 at 5:26 PM, Geoff Mina <gmina@connectfirst.com <mailto:gmina@connectfirst.com>> wrote:
Greetings,
I have a freeswitch installation that is configured to use MySQL (via ODBC) in switch.xml. Today we had one of our freeswitch hosts go out of service with this error:
*2018-01-03 00:14:51.340034 [ERR] switch_core_sqldb.c:587 NATIVE SQL ERR [database disk image is malformed]*
*delete from sip_registrations where sip_user='rcampos1' and sip_host='10.201.0.94'*
Through some searching, we determined that is the result of the sqlite db becoming corrupt. There were no power events, but it simply stopped working. Now... I don't even want to use sqllite. We have MySQL configured and is working properly. Here is our config from switch.xml
<param name="core-db-dsn" value="freeswitch:freeswitch:freeswitch" />
<param name="auto-create-schemas" value="true"/>
<param name="auto-clear-sql" value="true"/>
<param name="core-dbtype" value="MYSQL"/>
The registrations and calls ARE showing up in MySQL, so the ODBC connection is working. Why would Freeswitch continue to use SQLite even though we have configured the core to use MySQL? Even after clearing out the /freeswtich/db directory, upon restart, the following files show up again. It's as if Freeswitch is writing to both SQLite and MySQL.
-rw-r--r-- 1 14K Jan 3 00:16 call_limit.db
-rw-r--r-- 1 5.0K Jan 3 00:16 fifo.db
-rw-r--r-- 1 93K Jan 3 00:16 sofia_reg_external.db
-rw-r--r-- 1 99K Jan 3 00:26 sofia_reg_internal.db
Any help would be greatly appreciated.
Thanks,
Geoff
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org <mailto:consulting@freeswitch.org> http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org <mailto: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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.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
-- Saludos / Regards / Cumprimentos António Silva
participants (4)
-
António Silva
-
Geoff Mina
-
Ken Rice
-
Ítalo Rossi