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

Mon Apr 22 23:48:39 CDT 2013

    [ https://issues.asterisk.org/jira/browse/ASTERISK-21662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=205671#comment-205671 ] 

Dare Awktane commented on ASTERISK-21662:
-----------------------------------------

Hmm very interesting. We have pretty much the same setup and we're not seeing the same issue. We get a sip connection by our sip proxy to make sure we're up. The extensions table is also realtime odbc and therefore I can see in the mysql show processlist that the connection time is reset to 0 occasionally by this process. I took a machine effectively offline by firewalling it from its trunk for about an hour and the connection maintained. When I dropped the firewall rule and allowed the call through to it I did not see a notice about reconnecting when a call came in.

Things I would try for fun:
1. Perhaps obvious but should be mentioned nonetheless - check to make sure you don't have a wait_timeout specified in the mysql server's my.cnf and also check the mysql error log for anything of interest. You could from the mysql cli ask for "show variables like "%_timeout". Our wait_timeout is the mysql default which is 28800. A long time to go without any traffic.
2. Check the results of odbc show from the asterisk cli - does it think it's connected? Does this change?
3. Connection pooling - Likely of no use. Would still cause a delay because it still has to do the same steps if it loses a connection. Maybe worth a shot though nonetheless? Add a limit=5 under the database context and see what happens?

That's all I have. Hopefully someone with more knowledge than I comes along with a brilliant idea for you if those don't help.

> 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: Duane Larson
>         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