Bug #9869 mysqld --set_variable / -O / max_allowed_packet not working
Submitted: 13 Apr 2005 12:59 Modified: 26 Apr 2005 9:21
Reporter: Dominik Laudanski Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Server: Command-line Clients Severity:S2 (Serious)
Version:4.1 in windows / 4.0.18 sun OS:Windows (windows/unix)
Assigned to: CPU Architecture:Any

[13 Apr 2005 12:59] Dominik Laudanski
Description:
commands for change max_allowed_packet do not working
command did not return error
max_allow_packet is still set 1M

it is possible to change it in my.cnf (it is working)

How to repeat:
stop mysql
mysqld --set_variable=max_allowed_packet=16MB

mysqld -O max_allowed_packet=16MB

i try ecverytning from mysql-tutorial on 3 different widows and  2 sun's

Suggested fix:
edit my.cnf
[13 Apr 2005 13:07] Dominik Laudanski
versions of mysql
[13 Apr 2005 17:58] MySQL Verification Team
Please see below:

c:\mysql\bin>mysqld-nt --standalone --console -O max-allowed-packet=20M
050413 14:56:19  InnoDB: Started; log sequence number 0 50602
mysqld-nt: ready for connections.
Version: '4.1.11-nt'  socket: ''  port: 3306  Source distribution

c:\mysql\bin>mysql -uroot
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 1 to server version: 4.1.11-nt

Type 'help;' or '\h' for help. Type '\c' to clear the buffer.

mysql> show variables like "%packet%";
+--------------------+----------+
| Variable_name      | Value    |
+--------------------+----------+
| max_allowed_packet | 20970496 |
+--------------------+----------+
1 row in set (0.00 sec)
[14 Apr 2005 7:07] Dominik Laudanski
C:\Program Files\MySQL\MySQL Server 4.1\bin>mysqld-nt --standalone --console -O
max_allowed_packet=5M
InnoDB: Error: log file .\ib_logfile0 is of different size 0 10485760 bytes
InnoDB: than specified in the .cnf file 0 5242880 bytes!
050414  9:04:52 [ERROR] Can't init databases
050414  9:04:52 [ERROR] Aborting

050414  9:04:52 [Note] mysqld-nt: Shutdown complete

and how can i change it on SUN
[26 Apr 2005 9:21] Michael Widenius
Your last error indicates that you have changed the size for some of the
innodb variables since you last started MySQL
(or that you previously started MySQL with different options).

To check the options MySQL is currently using from the defaults files do:

mysql-nt --print-defaults

You can easily check that mysqld recognices max_allowed_packet by doing:

mysqld-nt --max_allowed_packet=5M --help

and search for max_allowed_packet in the output
[4 Oct 2012 7:13] Marko Mäkelä
The log file size problem is Bug#13494.