Your message dated Sat, 12 Nov 2005 21:28:11 +0100
with message-id <[EMAIL PROTECTED]>
and subject line mysql-server package has trouble with server-side prepapered
statements
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 7 Nov 2005 12:56:39 +0000
>From [EMAIL PROTECTED] Mon Nov 07 04:56:39 2005
Return-path: <[EMAIL PROTECTED]>
Received: from mail3b.westend.com (mail3b2.westend.com) [212.117.79.78]
by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
id 1EZ6YA-0005fX-00; Mon, 07 Nov 2005 04:56:39 -0800
Received: from localhost (localhost [127.0.0.1])
by mail3b2.westend.com (Postfix) with ESMTP id C44DF12127F;
Mon, 7 Nov 2005 13:56:36 +0100 (CET)
Received: from mail3b2.westend.com ([127.0.0.1])
by localhost (mail3b [127.0.0.1]) (amavisd-new, port 20024)
with ESMTP id 14297-04; Mon, 7 Nov 2005 13:56:33 +0100 (CET)
Received: from xeniac.intern (office-gw.westend.com [212.117.64.2])
by mail3b2.westend.com (Postfix) with ESMTP id 8C4A812127D;
Mon, 7 Nov 2005 13:56:33 +0100 (CET)
Date: Mon, 7 Nov 2005 13:56:33 +0100
From: Christian Hammers <[EMAIL PROTECTED]>
To: Marc Portier <[EMAIL PROTECTED]>,
Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: Re: mysql-server package has trouble with server-side prepapered
statements
Message-ID: <[EMAIL PROTECTED]>
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
Organization: www.debian.org
X-Mailer: Sylpheed-Claws 1.0.4 (GTK+ 1.2.10; i386-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
Package: mysql-server-4.1
Severity: normal
thanks
Hello Marc
On 2005-11-07 Marc Portier wrote:
> >>sorry for accessing you directly, but your name was listed as the
> >>package-maintainer of the mysql-server-4.1 package I'm using on my
> >>ubuntu distribution.
> >>
> >>I've been running around a bit with this value-binding issue I've
> >>spotted recently and got some answer from mysql peeps:
> >>* http://forums.mysql.com/read.php?39,49989,49989#msg-49989
> >
> >
> > From quickly taking a look at it, it seems to be a bug in MySQL itself and
> > not the Debian/Ubunto specific scripts around it. In this case, please file
>
> the first reaction from the mysql person was that they can't reproduce
> this on their own builds...
The first response of every supporter is to blame the next one nearby :-)
> additionally they hinted about (considering the amount of debian
> complaints they get) suspecting some incompatibility in the used gcc
> libs on debian (I assume the ones used when building the package? but
> have no idea how things actually work out there)
I won't rule out it until tried. Do the mails you referenced already contain
an easy to reproduce example? I don't use JDBC etc, so if you just give me
a .java/.class file and the necessary .sql database that I can use to
reproduce the bug I will make some backtraces and file the bug report
(if I can reproduce it :))
> I suppose there is some compilation involved when the binary packages
> are build?
> do you see area's where a mismatch in libraries could be causing values
> passed between systems to get converted/interpreted in a wrong way
> (as an example all ints passed to the prepared statements get one added
> and then shifted left for 16 positions)
Sounds not very probable, indeed :)
> well, I've guessed as much after seeing the reaction over at ubuntu
> (which was something like: "we don't do that package, go yell there")
mysql offers some prebuild binary packages on their website. Maybe you
can check those, just substituting /usr/sbin/mysqld might be enough.
Oh, and maybe try mysql-server-5.0 - if it's a bug then we know that we
have to fix it in both packages :)
As Debian and Ubunto uses the same source but maybe different builds, you
might want to check out the Debian builds at
http://packages.debian.org/mysql-server-4.1
http://packages.debian.org/mysql-server-5.0
bye,
-christian-
---------------------------------------
Received: (at 337941-done) by bugs.debian.org; 12 Nov 2005 20:28:17 +0000
>From [EMAIL PROTECTED] Sat Nov 12 12:28:17 2005
Return-path: <[EMAIL PROTECTED]>
Received: from mail3b.westend.com ([212.117.79.78] helo=mail3b2.westend.com)
by spohr.debian.org with esmtp (Exim 4.50)
id 1Eb1yz-0001cL-5l
for [EMAIL PROTECTED]; Sat, 12 Nov 2005 12:28:17 -0800
Received: from localhost (localhost [127.0.0.1])
by mail3b2.westend.com (Postfix) with ESMTP id 7863F121270;
Sat, 12 Nov 2005 21:28:15 +0100 (CET)
Received: from mail3b2.westend.com ([127.0.0.1])
by localhost (mail3b [127.0.0.1]) (amavisd-new, port 20024)
with ESMTP id 16583-09; Sat, 12 Nov 2005 21:28:12 +0100 (CET)
Received: from app109.intern (gate.lathspell.de [212.117.68.82])
by mail3b2.westend.com (Postfix) with ESMTP id 0709712126A;
Sat, 12 Nov 2005 21:28:12 +0100 (CET)
Date: Sat, 12 Nov 2005 21:28:11 +0100
From: Christian Hammers <[EMAIL PROTECTED]>
To: Marc Portier <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
Subject: Re: mysql-server package has trouble with server-side prepapered
statements
Message-ID: <[EMAIL PROTECTED]>
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
X-Mailer: Sylpheed-Claws 1.0.5 (GTK+ 1.2.10; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-3.0 required=4.0 tests=BAYES_00 autolearn=no
version=2.60-bugs.debian.org_2005_01_02
Hello Marc
> PS: I noticed, a bit late, that an additional To: in your previous
> message reply logged the issue in http://bugs.debian.org/337941, but I
> can't work out how I could comment on that directly.
To reply to a Debian bug report just Cc <bugnumber>@bugs.debian.org.
I will close the bug with this mail as you reported that the issue is
not a Debian problem :)
bye,
-christian-
On 2005-11-09 Marc Portier wrote:
> Christian,
>
> good news:
>
> I just took the remaining step and tried out the debian package directly
> via these
> steps:
> -----
> $ cd ~/MyDownloads/packages.debian.org/
> $ wget
> http://ftp.us.debian.org/debian/pool/main/m/mysql-dfsg-4.1/mysql-server-4.1_4.1.14-6_i386.deb
> $ wget
> http://ftp.us.debian.org/debian/pool/main/m/mysql-dfsg-4.1/mysql-client-4.1_4.1.14-6_i386.deb
> $ wget
> http://ftp.us.debian.org/debian/pool/main/m/mysql-dfsg-4.1/libmysqlclient14_4.1.14-6_i386.deb
> $ wget
> http://ftp.us.debian.org/debian/pool/main/m/mysql-dfsg-5.0/mysql-common_5.0.13rc-1_all.deb
>
> $ dpkg -i mysql-common..._all.deb
> $ dpkg -i libmysqlclient14..._i386.deb
> $ dpkg -i mysql-client-..._i386.deb
> $ dpkg -i mysql-server-..._i386.deb
>
> doublecheck:
> -----------
> $ echo "show variables like 'version'" |mysql -uroot
>
> Variable_name Value
> version 4.1.14-Debian_6-log
>
> which shows the ubuntu package has been correctly replaced
>
> my test
> -------
> when running my test mentioned earlier: I get correct behaviour on all
> cases! (so no trouble exploiting the server sider prepared statements,
> I've even enabled logging to verify that server side prepared statements
> are effectively used)
>
>
> So since the 4.1.14-6 is ok I didn't go further into testing the 5.0
>
>
> You might want to correct me on jumping to conclusions but this kinda
> closes the issue on your side and suggests I should be going back to
> looking for whoeever at ubuntu was building the package, right?
>
> To them the story is of course a bit double: their 4.1.12 is bogus
> compared to your 4.1.14
>
> So I think I'll advise them to upgrade to the 4.1.14 and double-check
> their next build carefully since the way they build the package might
> very well be the couse of trouble (rather then just the .12 to .14 diff)
>
> (unless you know off glibc/gcc related changes in the package source
> between 4.1.12 and 4.1.14)
>
>
> Well, this kinda looks like I've been bugging you without much reason
> after all, nevertheless thanx a lot for doing more then just blaming the
> next in line :-)
>
> regards,
> -marc=
> PS: I noticed, a bit late, that an additional To: in your previous
> message reply logged the issue in http://bugs.debian.org/337941, but I
> can't work out how I could comment on that directly.
>
>
>
> Marc Portier wrote:
> > Hello Christian,
> >
> > Christian Hammers wrote:
> >
> >>Package: mysql-server-4.1
> >>Severity: normal
> >>thanks
> >>
> >>
> >>Hello Marc
> >>
> >>On 2005-11-07 Marc Portier wrote:
> >>
> >>
> >>>>>sorry for accessing you directly, but your name was listed as the
> >>>>>package-maintainer of the mysql-server-4.1 package I'm using on my
> >>>>>ubuntu distribution.
> >>>>>
> >>>>>I've been running around a bit with this value-binding issue I've
> >>>>>spotted recently and got some answer from mysql peeps:
> >>>>>* http://forums.mysql.com/read.php?39,49989,49989#msg-49989
> >>>>
> >>>>
> >>>>From quickly taking a look at it, it seems to be a bug in MySQL itself
> >and >>
> >>>>not the Debian/Ubunto specific scripts around it. In this case, please
> >file >>
> >>>the first reaction from the mysql person was that they can't reproduce
> >>>this on their own builds...
> >>
> >>
> >>The first response of every supporter is to blame the next one nearby :-)
> >>
> >
> >
> > indeed, but hey, there must be someone we can blame for that?
> >
> >
> >>>additionally they hinted about (considering the amount of debian
> >>>complaints they get) suspecting some incompatibility in the used gcc
> >>>libs on debian (I assume the ones used when building the package? but
> >>>have no idea how things actually work out there)
> >>
> >>
> >>I won't rule out it until tried. Do the mails you referenced already
> >contain >an easy to reproduce example? I don't use JDBC etc, so if you just
> >give me >a .java/.class file and the necessary .sql database that I can use
> >to >reproduce the bug I will make some backtraces and file the bug report
> >>(if I can reproduce it :))
> >>
> >
> >
> > sure
> > here goes the test-sequence (requires java jre and a spinning mysqld)
> >
> > $ wget http://outerthought.net/~mpo/sqltest.tgz
> > $ tar -zxvf sqltest.tgz
> > $ cd sqltest
> >
> > $ mysql -uroot
> > mysql> use test;
> > mysql> create table brol ( id integer primary key, content varchar(255));
> > mysql> grant all on test.* to [EMAIL PROTECTED] identified by 'sql';
> > mysql> grant all on test.* to dba@'%' identified by 'sql';
> >
> > $ ./run.sh
> >
> > the output should mention all checks ok with the different combinations
> > in my case 3.1.x driver versus 4.1.12 mysqld it 'll produce something
> > like below to indicate the mentioned bug when attempting to use server
> > side prepared statements:
> >
> >
> >>unexpected data row id=65536, cntnt=
> >>unexpected data row id=131072, cntnt=
> >>unexpected data row id=196864, cntnt=
> >
> >
> >
> >>>I suppose there is some compilation involved when the binary packages
> >>>are build?
> >>>do you see area's where a mismatch in libraries could be causing values
> >>>passed between systems to get converted/interpreted in a wrong way
> >>>(as an example all ints passed to the prepared statements get one added
> >>>and then shifted left for 16 positions)
> >>
> >>Sounds not very probable, indeed :)
> >>
> >>
> >>
> >>>well, I've guessed as much after seeing the reaction over at ubuntu
> >>>(which was something like: "we don't do that package, go yell there")
> >>
> >>
> >>mysql offers some prebuild binary packages on their website. Maybe you
> >>can check those, just substituting /usr/sbin/mysqld might be enough.
> >>
> >
> >
> > yep, did that, (unpacked the tgz from mysql in ~/local/ and then
> > symlinked /usr/sbin/mysqld to that new one + checked with [show variable
> > like 'version';] to see that it shows 4.1.15-standard, not the
> > 4.1.12-debian_ubuntu...)
> >
> > and then running my test shows that everything is ok with the binary
> > 4.1.15 distro from mysql themselves
> >
> >
> >>Oh, and maybe try mysql-server-5.0 - if it's a bug then we know that we
> >>have to fix it in both packages :)
> >
> >
> > well, didn't know it was there (haven't seen it in my listed packages yet)
> >
> >
> >>As Debian and Ubunto uses the same source but maybe different builds, you
> >>might want to check out the Debian builds at
> >> http://packages.debian.org/mysql-server-4.1
> >> http://packages.debian.org/mysql-server-5.0
> >>
> >
> >
> > fwiw: the mysql version on my box mentions ubuntu explicitely (maybe
> > that means that they are using different builds?)
> >
> > as for installing the packages you mention: well, to be honest, I've
> > never ventured much under the hood of apt-get and adding lines to
> > /etc/apt/sources.list is kind of the most daring thing I've done in
> > package-land
> >
> > So: sorry for not being more self-sufficient here, but if you can throw
> > in some dpkg commands I should use to install/remove during this test
> > then that would help me produce these results faster
> >
> > hm, and here and now the URL's you've mentioned above seem to yield a
> > (110) Connection timed out (according to the squid proxy on the network
> > here)
> >
> >
> >>bye,
> >>
> >>-christian-
> >
> >
> > regards,
> > -marc=
>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
