[asterisk-users] ODBC locks warning in CLI - Asterisk 18.104.22.168
lardconcepts at gmail.com
Wed Nov 23 12:40:32 CST 2016
It might be worth pointing out that 1.8x was released 6 years ago,
went into security fix only over 2 years ago, and reached "end of
life/no further fixes" over a year ago.
11.x went into "security fix only" last month - 13 and 14 are the
current versions - can you try with them?
On 23 November 2016 at 12:52, Stefan Viljoen <viljoens at verishare.co.za> wrote:
> Hi all
> I get this warning in the Asterisk CLI about once every ten minutes or so:
> [Nov 23 14:47:36] WARNING: res_odbc.c:647
> ast_odbc_prepare_and_execute: SQL Execute returned an error -1: HY000:
> [MySQL][ODBC 5.1 Driver][mysqld-5.1.73]Deadlock found when trying to get
> lock; try restarting transaction (105)
> [Nov 23 14:47:36] WARNING: res_odbc.c:659
> ast_odbc_prepare_and_execute: SQL Execute error -1! Verifying connection to
> cdr [asterisk-cdr]...
> [Nov 23 14:47:36] WARNING: res_odbc.c:763 ast_odbc_sanity_check:
> Connection is down attempting to reconnect...
> [Nov 23 14:47:36] NOTICE: res_odbc.c:1541 odbc_obj_connect: Connecting
> [Nov 23 14:47:36] NOTICE: res_odbc.c:1573 odbc_obj_connect: res_odbc:
> Connected to cdr [asterisk-cdr]
> Does this imply that I'm missing the ODBC CELs and / or CDRs that were
> trying to write to MySQL over ODBC when the above occurred?
> Or will the ODBC module in Asterisk (or ODBC itself?) recover gracefully and
> re-emit the CEL or CDR insert that hit the lock and were therefore NOT
> written to MySQL?
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
> Check out the new Asterisk community forum at: https://community.asterisk.org/
> New to Asterisk? Start here:
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
More information about the asterisk-users