Your message dated Thu, 18 May 2023 22:48:29 +0000
with message-id <[email protected]>
and subject line Bug#1028325: Removed package(s) from unstable
has caused the Debian Bug report #770952,
regarding libmyodbc: Wrong error SQLSTATE on MySQL Server GONE
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
770952: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770952
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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

--- End Message ---
--- Begin Message ---
Version: 5.1.10-3+rm

Dear submitter,

as the package myodbc has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1028325

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
[email protected].

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

--- End Message ---

Reply via email to