<div dir="ltr">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.<div><br></div><div>-- </div><div>Steve<br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, May 13, 2016 at 9:08 AM, Vallimamod Abdullah <span dir="ltr"><<a href="mailto:vma@440hz.fr" target="_blank">vma@440hz.fr</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
This error message corresponds to sqlite3 SQLITE_CORRUPT error code. You may find this page interesting: <a href="https://www.sqlite.org/lockingv3.html#how_to_corrupt" rel="noreferrer" target="_blank">https://www.sqlite.org/lockingv3.html#how_to_corrupt</a><br>
You can alternatively try to put your core db in RAM disk: <a href="https://freeswitch.org/confluence/display/FREESWITCH/SSD+Tuning+for+Linux#SSDTuningforLinux-FreeSWITCH'score.dbI/Obottleneck" rel="noreferrer" target="_blank">https://freeswitch.org/confluence/display/FREESWITCH/SSD+Tuning+for+Linux#SSDTuningforLinux-FreeSWITCH'score.dbI/Obottleneck</a><br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Best Regards,<br>
Vallimamod<br></font></span><span class="im HOEnZb"><br></span></blockquote></div></div></div></div>