Bad error handling with Drizzledump connect

Bug #652645 reported by m00dawg
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Drizzle
Fix Released
High
Andrew Hutchings
7.0
Fix Released
High
Andrew Hutchings

Bug Description

When trying to issue a dump from a MySQL database (5.1.41-3ubuntu2.6 specifically), I get the following:

root@mcp:/var/lib/drizzle/local/test# drizzledump -p3306 -uroot -Ppasswordomitted moocowproductions
Got error: 15 when trying to connect
terminate called without an active exception
Aborted
root@mcp:/var/lib/drizzle/local/test# perror 15
OS error code 15: Block device required

This is on Ubuntu 10.04 using "2010.09.1802-1ubuntu1~lucid1":

root@mcp:/var/log# apt-cache policy drizzle-server
drizzle-server:
  Installed: 2010.09.1802-1ubuntu1~lucid1
  Candidate: 2010.09.1802-1ubuntu1~lucid1
  Version table:
 *** 2010.09.1802-1ubuntu1~lucid1 0
        500 http://ppa.launchpad.net/drizzle-developers/ppa/ubuntu/ lucid/main Packages
        100 /var/lib/dpkg/status

Tags: drizzledump

Related branches

Changed in drizzle:
assignee: nobody → Andrew Hutchings (linuxjedi)
Revision history for this message
Andrew Hutchings (linuxjedi) wrote :

m00dawg: can you please try connecting with the 'drizzle' client app to the MySQL server?

Revision history for this message
Andrew Hutchings (linuxjedi) wrote :

ok, so I've done a bit of digging and in libdrizzle error 15 is auth failed. So:

1. I will fix the exception handling when connecting
2. I will make drizzledump give proper error messages instead of codes
3. I will do some more testing to make sure auth is working correctly and fix anything there if necessary.

summary: - "Block device required" error with Drizzledump
+ Bad error handling with Drizzledump connect
Changed in drizzle:
importance: Undecided → High
Changed in drizzle:
status: New → Triaged
milestone: none → 2010-10-11
Changed in drizzle:
status: Triaged → Fix Committed
Revision history for this message
m00dawg (tim-moocowproductions) wrote :

Aha so it was a permissions issue. Forgot to make a user for '127.0.0.1' which was ultimately the problem. Glad to hear you have already fixed the error reporting, thank you!

Revision history for this message
Andrew Hutchings (linuxjedi) wrote :

No problem, many thanks for reporting it :)

The fix now provides connection errors similar to those mysqldump does when it fails to connect.

Changed in drizzle:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.