← Back to team overview

linux-traipu team mailing list archive

[Bug 528410] Re: drizzle_state_packet_read:bad packet number

 

Hi Andrew -

I've tried it via the drizzle-dev repo (which is my current
installation, see below) as well as from source (drizzle7-2011.08.25).
Same error.

If you think it would be helpful to the drizzle project, I can share my
screen (via Teamviewer) and help you try to find out what's causing this
to ensure it gets properly resolved.


Name       : libdrizzle
Arch       : x86_64
Version    : 2011.08.23
Release    : 1.el5
Size       : 84 k
Repo       : installed
Summary    : Drizzle Client & Protocol Library
URL        : http://launchpad.net/drizzle
License    : BSD and Public Domain
Description: libdrizzle is the the client and protocol library for the Drizzle project. The
           : server, drizzled, will use this as for the protocol library, as well as the
           : client utilities and any new projects that require low-level protocol
           : communication (like proxies). Other language interfaces (PHP extensions, SWIG,
           : ...) should be built off of this interface.

Name       : libdrizzle-devel
Arch       : x86_64
Version    : 2011.08.23
Release    : 1.el5
Size       : 137 k
Repo       : installed
Summary    : Drizzle Client & Protocol Library - Header Files
URL        : http://launchpad.net/drizzle
License    : GPLv2 and BSD
Description: Development files for the Drizzle Client & Protocol Library.

-- 
You received this bug notification because you are a member of UBUNTU -
AL - BR, which is subscribed to Drizzle.
https://bugs.launchpad.net/bugs/528410

Title:
  drizzle_state_packet_read:bad packet number

Status in A Lightweight SQL Database for Cloud Infrastructure and Web Applications:
  Opinion
Status in Drizzle Client & Protocol Library:
  Fix Released

Bug description:
  I am getting the following error when using libdrizzle 0.7 together
  with MySQL Ver 14.14 Distrib 5.1.38. The error occurs when using
  “drizzle_result_buffer”:

  drizzle_state_packet_read:bad packet number:213:223

  The error is reproduceable; it always occurs on the same query. This
  query works just fine when running it with the “mysql” commandline
  client.

To manage notifications about this bug go to:
https://bugs.launchpad.net/drizzle/+bug/528410/+subscriptions