Package: libmyodbc
Version: 5.1.10-2+deb7u1
Severity: normal

Dear Maintainer,

   * What led up to the situation?

I'm using odbc + libmyodbc to connect ejabberd (odbc) authentication to a mysql 
database.
The MySQL database can be provided by two machines using the same ip address 
with only one machine providing service at a time (HA setup).

   * What exactly did you do (or not do) that was effective (or
     ineffective)?

When the MySQL service ( including the ip ) migrates to the other machine, the 
mysql server closes all connections. I expect odbc to open connections to the 
new server.

   * What was the outcome of this action?

erlang reports "MySQL Server gone (SQLSTATE 0000)" errors and there are no 
connection (nor connection attemps) from odbcserver to mysql server anymore 
(after the service moved).
Restarting ejabberd (including odbcserver) fixes the problem, so this is not a 
database problem.
It also has nothing to do with wait_time (8h), as it can be triggered at any 
time by service migration.

   * What outcome did you expect instead?

I expected odbc to open a new connection to the new machine providing mysql 
service. But this does not happen, likely because the error is reported 
improperly from libmyodbc to odbcserver.

-- System Information:
Debian Release: 7.7
  APT prefers stable
  APT policy: (700, 'stable')
Architecture: i386 (x86_64)

Kernel: Linux 3.16-0.bpo.3-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libmyodbc depends on:
ii  debconf [debconf-2.0]  1.5.49
ii  libc6                  2.13-38+deb7u6
ii  libmysqlclient18       5.5.40+maria-1~wheezy
ii  odbcinst1debian2       2.2.14p2-5
ii  zlib1g                 1:1.2.7.dfsg-13

Versions of packages libmyodbc recommends:
ii  libodbc1  2.2.14p2-5

libmyodbc suggests no packages.

-- debconf information:
  libmyodbc/addtoodbc: false


-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to