Looks like 5.1.61 mac installer messed up the privilege setting... But how to fix it? I remember the server account is mysql, not _mysql
What do you got? And how to fix it? Thanks On Wed, Feb 29, 2012 at 2:20 PM, Elim Qiu <elim....@gmail.com> wrote: > I created (or activated) the root account and now I see the error log: > > sh-3.2# cat miniMac.local.err > 120229 10:36:09 mysqld_safe Starting mysqld daemon with databases from > /usr/local/mysql/data > 120229 10:36:09 [Warning] Setting lower_case_table_names=2 because file > system for /usr/local/mysql/data/ is case insensitive > 120229 10:36:09 [Note] Plugin 'FEDERATED' is disabled. > /usr/local/mysql/bin/mysqld: Table 'plugin' is read only > 120229 10:36:09 [ERROR] Can't open the mysql.plugin table. Please run > mysql_upgrade to create it. > 120229 10:36:09 InnoDB: Initializing buffer pool, size = 8.0M > 120229 10:36:09 InnoDB: Completed initialization of buffer pool > InnoDB: The first specified data file ./ibdata1 did not exist: > InnoDB: a new database to be created! > 120229 10:36:09 InnoDB: Setting file ./ibdata1 size to 10 MB > InnoDB: Database physically writes the file full: wait... > 120229 10:36:09 InnoDB: Log file ./ib_logfile0 did not exist: new to be > created > InnoDB: Setting log file ./ib_logfile0 size to 5 MB > InnoDB: Database physically writes the file full: wait... > 120229 10:36:09 InnoDB: Log file ./ib_logfile1 did not exist: new to be > created > InnoDB: Setting log file ./ib_logfile1 size to 5 MB > InnoDB: Database physically writes the file full: wait... > InnoDB: Doublewrite buffer not found: creating new > InnoDB: Doublewrite buffer created > InnoDB: Creating foreign key constraint system tables > InnoDB: Foreign key constraint system tables created > 120229 10:36:10 InnoDB: Started; log sequence number 0 0 > 120229 10:36:10 [ERROR] /usr/local/mysql/bin/mysqld: Can't create/write to > file '/usr/local/mysql/data/miniMac.local.pid' (Errcode: 13) > 120229 10:36:10 [ERROR] Can't start server: can't create PID file: > Permission denied > 120229 10:36:10 mysqld_safe mysqld from pid file > /usr/local/mysql/data/miniMac.local.pid ended > > > On Wed, Feb 29, 2012 at 12:35 PM, Darryle Steplight > <dstepli...@gmail.com>wrote: > >> If you are going to use "su" to officially switch to the root users >> just make sure you do "su -" with the dash. >> >> On Wed, Feb 29, 2012 at 2:10 PM, Reindl Harald <h.rei...@thelounge.net> >> wrote: >> > >> > >> > Am 29.02.2012 19:20, schrieb Larry Martell: >> >> Is the sudo succeeding? If it is, then there's no reason you shouldn't >> >> be able to cd into that dir. If not, then you're going to have to be >> >> able to get root privileges on your own machine. >> >> >> >> Alternatively, you could explicitly set the location of the error log >> >> in your mysql config file (my.cnf) , to a location you can access, >> >> e.g. >> >> >> >> log-error=/tmp/mysqld.log >> >> >> >> put it under [mysqld] and [mysqld_safe] >> > >> > but you would have still NO PERMISSIONS to that logfile >> > because it is owned by mysqld and a normal user has >> > usually no permissions to daemon-logs especially >> > because /tmp has normally 1777 -> everybody can >> > write but after create a file only the owner is >> > allowed to access it >> > >> > why not using "su" to REALLY switch to root? >> > >> >> >> >> -- >> ---------------------------------------------- >> "May the Source be with you." >> >> -- >> MySQL General Mailing List >> For list archives: http://lists.mysql.com/mysql >> To unsubscribe: http://lists.mysql.com/mysql >> >> >
