[asterisk-bugs] [JIRA] (ASTERISK-21662) Res_odbc keeps losing connection to MySQL

[Michael L. Young (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-21662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael L. Young updated ASTERISK-21662:
----------------------------------------

    Assignee: Michael L. Young  (was: Duane Larson)
      Status: Triage  (was: Waiting for Feedback)
    
> Res_odbc keeps losing connection to MySQL
> -----------------------------------------
>
>                 Key: ASTERISK-21662
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21662
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_odbc
>    Affects Versions: 11.3.0
>         Environment: Debian 6.0
>            Reporter: Duane Larson
>            Assignee: Michael L. Young
>         Attachments: odbc.ini.txt, res_odbc.txt
>
>
> For some reason my ODBC connection to my MySQL server keeps losing its connection.  Because of this calls might be delayed until Asterisk re-establishes the connection.
> I have posted this before in the forum and never got an answer.
> http://forums.asterisk.org/viewtopic.php?p=170284
> Here are the errors I see
> {noformat}
> [Apr 19 15:05:18] WARNING[7380][C-00000003] res_odbc.c: SetConnectAttr (Txn isolation) returned an error: HY000: [MySQL][ODBC 5.1 Driver]MySQL server has gone away
> [Apr 19 15:05:18] WARNING[7380][C-00000003] res_odbc.c: SQL Execute returned an error -1: 08S01: [MySQL][ODBC 5.1 Driver][mysqld-5.1.42]MySQL server has gone away (65)
> [Apr 19 15:05:18] WARNING[7380][C-00000003] res_odbc.c: SQL Execute error -1! Verifying connection to asterisk [MySQL-asterisk]...
> [Apr 19 15:05:18] WARNING[7380][C-00000003] res_odbc.c: Connection is down attempting to reconnect...
> [Apr 19 15:05:23] NOTICE[7380][C-00000003] res_odbc.c: Connecting asterisk
> [Apr 19 15:05:23] NOTICE[7380][C-00000003] res_odbc.c: res_odbc: Connected to asterisk [MySQL-asterisk]
> [Apr 19 15:05:23] WARNING[7380][C-00000003] res_odbc.c: SQL Execute returned an error -1: 42S22: [MySQL][ODBC 5.1 Driver][mysqld-5.1.42]Unknown column 'callbackextension' in 'where clause' (91)
> [Apr 19 15:05:23] WARNING[7380][C-00000003] res_odbc.c: SQL Execute error -1! Verifying connection to asterisk [MySQL-asterisk]...
> [Apr 19 15:05:23] WARNING[7380][C-00000003] res_odbc.c: Connection is down attempting to reconnect...
> [Apr 19 15:05:28] NOTICE[7380][C-00000003] res_odbc.c: Connecting asterisk
> [Apr 19 15:05:28] NOTICE[7380][C-00000003] res_odbc.c: res_odbc: Connected to asterisk [MySQL-asterisk]
> [Apr 19 15:05:28] WARNING[7380][C-00000003] res_odbc.c: SQL Execute returned an error -1: 42S22: [MySQL][ODBC 5.1 Driver][mysqld-5.1.42]Unknown column 'callbackextension' in 'where clause' (91)
> [Apr 19 15:05:28] WARNING[7380][C-00000003] res_odbc.c: SQL Execute error -1! Verifying connection to asterisk [MySQL-asterisk]...
> [Apr 19 15:05:28] WARNING[7380][C-00000003] res_odbc.c: Connection is down attempting to reconnect...
> [Apr 19 15:05:33] NOTICE[7380][C-00000003] res_odbc.c: Connecting asterisk
> [Apr 19 15:05:33] NOTICE[7380][C-00000003] res_odbc.c: res_odbc: Connected to asterisk [MySQL-asterisk]
> [Apr 20 13:24:25] WARNING[7380][C-00000004] res_odbc.c: SetConnectAttr (Txn isolation) returned an error: HY000: [MySQL][ODBC 5.1 Driver]MySQL server has gone away
> [Apr 20 13:24:25] WARNING[7380][C-00000004] res_odbc.c: SQL Execute returned an error -1: 08S01: [MySQL][ODBC 5.1 Driver][mysqld-5.1.42]MySQL server has gone away (65)
> [Apr 20 13:24:25] WARNING[7380][C-00000004] res_odbc.c: SQL Execute error -1! Verifying connection to asterisk [MySQL-asterisk]...
> [Apr 20 13:24:25] WARNING[7380][C-00000004] res_odbc.c: Connection is down attempting to reconnect...
> [Apr 20 13:24:30] NOTICE[7380][C-00000004] res_odbc.c: Connecting asterisk
> [Apr 20 13:24:30] NOTICE[7380][C-00000004] res_odbc.c: res_odbc: Connected to asterisk [MySQL-asterisk]
> {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira