Bug #1055 my-medium.cnf has incorrect value under [mysqldump]
Submitted: 15 Aug 2003 8:56 Modified: 25 Jun 2004 17:40
Reporter: Thomas Abthorpe Email Updates:
Status: Closed Impact on me:
Category:MySQL Server: Installing Severity:S3 (Non-critical)
Version:4.0.13-log OS:FreeBSD (FreeBSD 5.1-RELEASE #0)
Assigned to: CPU Architecture:Any

[15 Aug 2003 8:56] Thomas Abthorpe
When performing

mysqldump --user=mysqladmin --password=secret --host=hostname --all-databases

got the error

unrecognized option `--max_allowed_packet=16M'

How to repeat:
rerun mysqldump

Suggested fix:
Edit my.cnf

locate [mysqldump]

and change

max_allowed_packet = 16M


set-variable    = max_allowed_packet = 16M
[15 Aug 2003 10:00] Thomas Abthorpe
caught a spelling mistake.
[20 Aug 2003 19:43] MySQL Verification Team
I tested with a server built with the current 4.0 bk tree
and with the Windows release 4.0.14.
The max_allowed_packet = 16M syntax is supported.
[21 Aug 2003 12:01] Lenz Grimmer
This should not happen with never versions of mysqldump. Are you absolutely 
sure, that mysqldump is of version 4.0.13 as well? Please run "mysqldump 
--version" to make sure, that this is not the case. We were not able to 
reproduce this problem here.
[21 Aug 2003 12:54] Thomas Abthorpe
I have sinced ramped up to 4.0.14. Fortunately, I have some of the old sql dumps. It would appear to be the wrong version of mysqldump.

-- MySQL dump 8.22
-- Host: localhost    Database:
-- Server version       4.0.13-log