[Freeswitch-users] database disk image is malformed
krice at freeswitch.org
Fri May 13 20:29:58 MSD 2016
Make sure the filesystem perms are correct for the user that freeswitch is running as.
It is safe to stop FreeSWITCH, remove the files, and allow FreeSWITCH to recreate them with the correct permissions. The only file that needs to hang around across reboots is the voicemail one which contains the metadata for any voicemails that are still on the system. If you are not using mod_voicemail on a particular FreeSWITCH install, it is also safe to delete.
From: freeswitch-users-bounces at lists.freeswitch.org [mailto:freeswitch-users-bounces at lists.freeswitch.org] On Behalf Of Steven Schoch
Sent: Friday, May 13, 2016 11:18 AM
To: FreeSWITCH Users Help <freeswitch-users at lists.freeswitch.org>
Subject: Re: [Freeswitch-users] database disk image is malformed
I'm pretty sure the core.db is not corrupted. I ran "sqlite3 core.db", dumped all the tables, and got no errors. Then I removed the entire core.db file and restart freeswitch. It still gave me those errors immediately after it created a brand new core.db. I don't want to go through the trouble of the RAM disk route until I find the root cause first.
On Fri, May 13, 2016 at 9:08 AM, Vallimamod Abdullah <vma at 440hz.fr <mailto:vma at 440hz.fr> > wrote:
This error message corresponds to sqlite3 SQLITE_CORRUPT error code. You may find this page interesting: https://www.sqlite.org/lockingv3.html#how_to_corrupt
You can alternatively try to put your core db in RAM disk: https://freeswitch.org/confluence/display/FREESWITCH/SSD+Tuning+for+Linux#SSDTuningforLinux-FreeSWITCH'score.dbI/Obottleneck
-------------- next part --------------
An HTML attachment was scrubbed...
Join us at ClueCon 2016 Aug 8-12, 2016
More information about the FreeSWITCH-users