| Summary: | dev-db/mysql-5.6.20 fails to start with old default config | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Patrick Lauer <patrick> |
| Component: | New packages | Assignee: | Gentoo Linux MySQL bugs team <mysql-bugs> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Patrick Lauer
2014-08-18 06:15:27 UTC
# /usr/sbin/mysqld --defaults-file=/etc/mysql/my.cnf 2014-08-18 14:17:30 0 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead. 2014-08-18 14:17:30 0 [Warning] The syntax '--language/-l' is deprecated and will be removed in a future release. Please use '--lc-messages-dir' instead. 2014-08-18 14:17:30 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details). 2014-08-18 14:17:30 2997 [Warning] Using pre 5.5 semantics to load error messages from /usr/share/mysql/english/. 2014-08-18 14:17:30 2997 [Warning] If this is not intended, refer to the documentation for valid usage of --lc-messages-dir and --language parameters. ... oh, just found this gem in the mysqld.err: 2014-08-18 14:17:30 2997 [ERROR] /usr/sbin/mysqld: unknown variable 'table_cache=64' 2014-08-18 14:17:30 2997 [ERROR] Aborting So it quietly kills itself! And OpenRC keeps waiting for it a looooong time, so the init script looks like it hangs. The config variable change was reported and fixed 2.5 years ago with bug 403425. This originated with MySQL 5.1.3 but was not updated until the bug report. Upstream regularly changes variable names and we try to keep pace in our default my.cnf. I cannot help when config updates are simply zapped away. There should also have been deprecation warnings in the /var/log/mysql/mysqld.err It is part of the admin's job to read release notes and deprecation warnings each upgrade. *** This bug has been marked as a duplicate of bug 403425 *** |