Bug #4399 | mysql_install_db fails | ||
---|---|---|---|
Submitted: | 3 Jul 2004 19:32 | Modified: | 13 Nov 2004 17:49 |
Reporter: | Thomas Dähling | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Server: Installing | Severity: | S1 (Critical) |
Version: | 4.1.3-Beta | OS: | Linux (Debian) |
Assigned to: | Assigned Account | CPU Architecture: | Any |
[3 Jul 2004 19:32]
Thomas Dähling
[14 Jul 2004 5:13]
MySQL Verification Team
I downloaded the source package and I wasn't able to repeat the behavior reported: miguel@hegel:~/download/mysql-4.1.3-beta> scripts/mysql_install_db Installing all prepared tables Fill help tables To start mysqld at boot time you have to copy support-files/mysql.server to the right place for your system PLEASE REMEMBER TO SET A PASSWORD FOR THE MySQL root USER ! To do so, start the server, then issue the following commands: /home/miguel/dbs/bug4399/bin/mysqladmin -u root password 'new-password' /home/miguel/dbs/bug4399/bin/mysqladmin -u root -h hegel password 'new-password' See the manual for more instructions. You can start the MySQL daemon with: cd /home/miguel/dbs/bug4399 ; /home/miguel/dbs/bug4399/bin/mysqld_safe & You can test the MySQL daemon with the benchmarks in the 'sql-bench' directory: cd sql-bench ; perl run-all-tests Please report any problems with the /home/miguel/dbs/bug4399/bin/mysqlbug script! The latest information about MySQL is available on the web at http://www.mysql.com Support MySQL by buying support/licenses at https://order.mysql.com miguel@hegel:~/download/mysql-4.1.3-beta>
[21 Jul 2004 20:10]
Wei Wu
I had the same problem when I ran mysql_install_db. Error: 1153 Got a packet bigger than 'max_allowed_packet' bytes 040721 ... Aborting.
[21 Jul 2004 21:31]
Sam Hulick
This error occurs for me as well. I'm running a very clean install of Slackware 10.
[8 Sep 2004 11:31]
[ name withheld ]
I encountered the same error. I'm using Red Hat 8.
[23 Sep 2004 16:59]
Yann Neuhaus
I had exactly the same issue. I copied the my.cnf templates to ~ and the mysql_install_db fails. However mysql_install_db works without .cnf file. mysqlsu@dune:~> mysql_install_db Installing all prepared tables 040923 18:44:32 [WARNING] Asked for 196608 thread stack, but got 126976 Fill help tables 040923 18:44:33 [WARNING] Asked for 196608 thread stack, but got 126976 ERROR: 1153 Got a packet bigger than 'max_allowed_packet' bytes 040923 18:44:33 [ERROR] Aborting
[23 Sep 2004 17:00]
Yann Neuhaus
Sorry, one more info, I've got this bug with release 4.1.5
[29 Sep 2004 5:02]
Lionel Morrison
I also got a similar error message Installing all prepared tables Fill help tables ERROR: 1153 Got a packet bigger than 'max_allowed_packet' bytes 040929 0:57:58 [ERROR] Aborting 040929 0:57:58 [NOTE] /usr/local/mysql/libexec/mysqld: Shutdown complete WARNING: HELP FILES ARE NOT COMPLETELY INSTALLED! The "HELP" command might not work properly If I delete '/etc/my.cnf' mysql_install_db the script seems to run fine, however I am unable to start the mysql daemon. Exits with the following error message [root@Dublin mysql-4.1.5-gamma]# STOPPING server from pid file /usr/local/mysql/var/Dublin.pid 040929 00:59:52 mysqld ended [1]+ Done /usr/local/mysql/bin/mysqld_safe Mandrake 10.0 MySQL-4.1.5-gamma
[4 Oct 2004 0:37]
Piotrek Maj
I've got the same problem - slackware-current, upgraded daily. I've tried diffrent values of max_allowed_packet but the problem didn't disappear.
[13 Oct 2004 17:49]
Matthew Lord
Hi, I've run into this with the icc builds before due to differences in glibc versions. Can any of you who've encountered the problem try using our max release which is dynamically linked? I suspect this is the same problem I ran into wherein even though the build is done statically there are still some dynamic glibc calls made and in this case it causes the net_buffer not to grow to the max_allowed_packet size. To test this you can increase the size of the net_buffer and run mysql_install_db. Best Regards
[14 Feb 2005 22:54]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".