We have a similar issue… where the next step is also to take a backtrace.
From what I understood in my post, it’s not yet possible on Debian:
Incorrect, Asterisk can be compiled to provide backtraces on any version of Debian (by my experience since Wheezy (7) ). That Sangoma have not done yet is a different story.
Consider that “Apply changes” also involves re-writing sqlite3 tables, I have long suspected that the asterisk ‘database’ code is not as rubust as it could be since moving from Berkeley to sqlite3, Asterisk itself has no awareness of mysql/mariadb outside of it’s add-on cdr odbc driver.
It is easy to ‘deadlock’, open a connection to /var/lib/asterisk/astdb.sqlite3 by any method that is not the ongoing asterisk user one and continually even just read data, in short order the database will be locked. BTDT
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.