MySQL standalone

MySQL

I have installed MySQL 5.5.27 on my MAC using the binary installer. I am able to run the mysql server with /Library/StartupItems/MySQLCOM/MySQLCOM start. But I am not able to run the mysqld with standalone option. I get the following error:

120821 17:28:03 [Note] Plugin 'FEDERATED' is disabled.
bin/mysqld: Can't find file: './mysql/plugin.frm' (errno: 13)
120821 17:28:03 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it.
120821 17:28:03 InnoDB: The InnoDB memory heap is disabled
120821 17:28:03 InnoDB: Mutexes and rw_locks use GCC atomic builtins
120821 17:28:03 InnoDB: Compressed tables use zlib 1.2.3
120821 17:28:03 InnoDB: Initializing buffer pool, size = 128.0M
120821 17:28:03 InnoDB: Completed initialization of buffer pool
120821 17:28:04  InnoDB: Operating system error number 13 in a file operation.
InnoDB: The error means mysqld does not have the access rights to
InnoDB: the directory.
InnoDB: File name ./ibdata1
InnoDB: File operation call: 'open'.
InnoDB: Cannot continue operation.

Could you please help me to run the mysqld –standalone ?

Best Answer

As it is saying, run "./mysql_upgrade -u -p" first to create the frm file. If you're not able to create it, try running the script as superuser. Then run "./mysqld -u ", in case as superuser too.

Hope this helps

Related Solutions

Mysql – Having Problems Installing 64-bit MySQL 5.5.8 x86 on OS X 10.6.6

Fixed it. Listening to /usr/local/mysql/support-files/mysql.server: line 256: my_print_defaults: command not found, I took a peek inside. Turns out this is the script that's called when the startup item or the preference pane want to start or stop MySQL. Unfortunately, it doesn't seem to work out of the box anymore.

The comments near the top of the script seem to know this, and give you a list of options to make the script work. I took the easiest and added the installation path to the basedir variable assignment.

MySQL – Troubleshooting Startup Issues After Increasing innodb_buffer_pool_size

The two answers given from @RickJames and @drogart are essentially the remedies. (+1 for each).

Right from the error log you present, the last two lines say:

InnoDB: Error: log file ./ib_logfile0 is of different size 0 134217728 bytes

InnoDB: than specified in the .cnf file 0 268435456 bytes! `

At that point, it was evident that you set innodb_log_file_size to 256M (268435456) in my.cnf while the InnoDB Transaction Logs (ib_logfile0,ib_logfile1) were respectively 128M (134217728) each. Looking back at the link to my StackOverflow answer in your question, you had to do the following:

Step 01) Add this to my.cnf:

[mysqld]
innodb_buffer_pool_size=4G
innodb_log_file_size=1G

Step 02) Run these command in the OS

mysql -u... -p... -e"SET GLOBAL innodb_fast_shutdown = 1"
service mysql stop
rm -f /var/lib/mysql/ib_logfile*
service mysql start

So as to have confidence in what is happening, run tail -f against the error log. You will see message telling you when each innodb log file is being created.

Related Question