Details
-
Type:
Bug
-
Status: Closed
-
Resolution: Not a Bug
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: None
-
Labels:
Description
I'm on a fresh install of a daily build of Ubuntu 12.04. I initially tried to install mariadb from the Ubuntu 11.10 packages, but this failed due to unresolvable conflicts. The second option was to try to install Mariadb from generic linux packages. This went more or less smoothly, except that when I ran mysql_install_db it was unable to find the mysqld binary, the basedir option seems mandatory/musthave?
After fixing that however, I got the following output:
root@dolf-ThinkPad-T520:/usr/local/mysql# ./scripts/mysql_install_db --user=mysql --basedir=/usr/local/mysql
Installing MariaDB/MySQL system tables in '/var/lib/mysql' ...
120219 15:58:30 [Warning] option 'thread_stack': unsigned value 196608 adjusted to 245760
120219 15:58:30 [ERROR] /usr/local/mysql/bin/mysqld: unknown variable 'lc-messages-dir=/usr/share/mysql'
120219 15:58:30 [ERROR] Aborting
...
Problem: Unknown variable lc-messages-dir
Removing /etc/mysql resolved the issue.
Version used: mariadb-5.3.4-rc-Linux-x86_64/
Even though Ubuntu 12.04 is still alpha, it would of course be great if these issues could be fixed before it's released as GA.
If questions, I am also available on the IRCs.
TL
Gliffy Diagrams
Attachments
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
Re: Ubuntu 12.04 my.cnf contains unknown directive: lc-messages-dir
The full story is that MySQL 5.5 came along with Ubuntu 12.04 installation and was later uninstalled, but the configuration file was left behind. MariaDB 5.3 server started from the generic tarball picked up the config and, since lc-messages-dir is a 5.5-only option, failed to start. The solution would be either to remove MySQL 5.5 configuration file, or explicitely point MariaDB binary to another one, using --defaults-file.
Launchpad bug id: 936277
Re: Ubuntu 12.04 my.cnf contains unknown directive: lc-messages-dir
I was under the impression that Mysql 5.5 was backported to Mariadb 5.3. Was just told this is not the case, so this issue is probably a nonissue.