Armin Schindler wrote: > > I tried new pre-0.2 now and the problem still exist. After 5 days of perfect > run, the segfault happens at the same place again:
<snip> > So I think the problem is sqlite. > I think of moving to another database. Does anyone uses mysql? I regularly have opbx stay up for 20+ days without a restart, and have never seen a crash due to sqlite. On the extremely rare occasion that one of my boxes crashes these days, I always analyse the coredump. My understanding of the sqlite in opbx is that it's simply a lightweight sql replacement for berkeley db. Apart from inciting a database holy war, using mysql for that kind of thing is overkill, and introduces another point of failure. From your stacktrace, it looks as if the keys are getting corrupted somehow. Are your sqlite libs up to date? _______________________________________________ Openpbx-dev mailing list [email protected] http://lists.openpbx.org/mailman/listinfo/openpbx-dev
