wmarcy Posted July 6, 2013 Share Posted July 6, 2013 After a server move, MAC os x 10.8.4 server, got mysql installed and copied over my databases (Imported only my IPB.Board ones presently, all was good. Ran the forum for a day, then, installed a drobo thunderbolt unit, had to reboot. Now I can not start MYSQL. ownership of mysql directory is root, ownership of the data subdir and all files under it is _mysql MYSQL was working before the restart. It is not now. Here is a bit from the Err log. 130706 18:13:48 mysqld_safe mysqld from pid file /usr/local/mysql/data/server.wetworx.com.pid ended 130706 18:16:57 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/data 2013-07-06 18:16:57 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details). 2013-07-06 18:16:57 3634 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/mysql/data/ is case insensitive 2013-07-06 18:16:57 3634 [Note] Plugin 'FEDERATED' is disabled. /usr/local/mysql/bin/mysqld: Table 'mysql.plugin' doesn't exist 2013-07-06 18:16:57 3634 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it. 2013-07-06 18:16:57 3634 [Note] InnoDB: The InnoDB memory heap is disabled 2013-07-06 18:16:57 3634 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2013-07-06 18:16:57 3634 [Note] InnoDB: Compressed tables use zlib 1.2.3 2013-07-06 18:16:57 3634 [Note] InnoDB: Using CPU crc32 instructions 2013-07-06 18:16:57 3634 [Note] InnoDB: Initializing buffer pool, size = 128.0M 2013-07-06 18:16:57 3634 [Note] InnoDB: Completed initialization of buffer pool 2013-07-06 18:16:57 3634 [Note] InnoDB: Highest supported file format is Barracuda. 2013-07-06 18:16:57 7fff77f77180 InnoDB: Operating system error number 2 in a file operation. InnoDB: The error means the system cannot find the path specified. InnoDB: If you are installing InnoDB, remember that you must create InnoDB: directories yourself, InnoDB does not create them. 2013-07-06 18:16:57 3634 [ERROR] InnoDB: Could not find a valid tablespace file for 'icorning/reputation_cache'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue. 2013-07-06 18:16:57 3634 [ERROR] InnoDB: Tablespace open failed for '"icorning"."reputation_cache"', ignored. 2013-07-06 18:16:57 7fff77f77180 InnoDB: Operating system error number 2 in a file operation. InnoDB: The error means the system cannot find the path specified. InnoDB: If you are installing InnoDB, remember that you must create InnoDB: directories yourself, InnoDB does not create them. 2013-07-06 18:16:57 3634 [ERROR] InnoDB: Could not find a valid tablespace file for 'mysql/slave_master_info'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue. 2013-07-06 18:16:57 3634 [ERROR] InnoDB: Tablespace open failed for '"mysql"."slave_master_info"', ignored. 2013-07-06 18:16:57 7fff77f77180 InnoDB: Operating system error number 2 in a file operation. InnoDB: The error means the system cannot find the path specified. InnoDB: If you are installing InnoDB, remember that you must create InnoDB: directories yourself, InnoDB does not create them. 2013-07-06 18:16:57 3634 [ERROR] InnoDB: Could not find a valid tablespace file for 'mysql/slave_relay_log_info'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue. 2013-07-06 18:16:57 3634 [ERROR] InnoDB: Tablespace open failed for '"mysql"."slave_relay_log_info"', ignored. 2013-07-06 18:16:57 7fff77f77180 InnoDB: Operating system error number 2 in a file operation. InnoDB: The error means the system cannot find the path specified. InnoDB: If you are installing InnoDB, remember that you must create InnoDB: directories yourself, InnoDB does not create them. 2013-07-06 18:16:57 3634 [ERROR] InnoDB: Could not find a valid tablespace file for 'mysql/slave_worker_info'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue. 2013-07-06 18:16:57 3634 [ERROR] InnoDB: Tablespace open failed for '"mysql"."slave_worker_info"', ignored. 2013-07-06 18:16:57 3634 [Note] InnoDB: 128 rollback segment(s) are active. 2013-07-06 18:16:57 3634 [Note] InnoDB: Waiting for purge to start 2013-07-06 18:16:57 3634 [Note] InnoDB: 5.6.11 started; log sequence number 221000222 2013-07-06 18:16:57 3634 [ERROR] /usr/local/mysql/bin/mysqld: unknown option '--skip-locking' 2013-07-06 18:16:57 3634 [ERROR] Aborting 2013-07-06 18:16:57 3634 [Note] Binlog end 2013-07-06 18:16:57 3634 [Note] Shutting down plugin 'partition' 2013-07-06 18:16:57 3634 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA' 2013-07-06 18:16:57 3634 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES' 2013-07-06 18:16:57 3634 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES' 2013-07-06 18:16:57 3634 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS' 2013-07-06 18:16:57 3634 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN' 2013-07-06 18:16:57 3634 [Note] Shutting down plugin 'INNODB_SYS_FIELDS' 2013-07-06 18:16:57 3634 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS' 2013-07-06 18:16:57 3634 [Note] Shutting down plugin 'INNODB_SYS_INDEXES' 2013-07-06 18:16:57 3634 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS' 2013-07-06 18:16:57 3634 [Note] Shutting down plugin 'INNODB_SYS_TABLES' 2013-07-06 18:16:57 3634 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE' 2013-07-06 18:16:57 3634 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE' 2013-07-06 18:16:57 3634 [Note] Shutting down plugin 'INNODB_FT_CONFIG' 2013-07-06 18:16:57 3634 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED' 2013-07-06 18:16:57 3634 [Note] Shutting down plugin 'INNODB_FT_DELETED' 2013-07-06 18:16:57 3634 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD' 2013-07-06 18:16:57 3634 [Note] Shutting down plugin 'INNODB_METRICS' 2013-07-06 18:16:57 3634 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS' 2013-07-06 18:16:57 3634 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU' 2013-07-06 18:16:57 3634 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE' 2013-07-06 18:16:57 3634 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET' 2013-07-06 18:16:57 3634 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX' 2013-07-06 18:16:57 3634 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET' 2013-07-06 18:16:57 3634 [Note] Shutting down plugin 'INNODB_CMPMEM' 2013-07-06 18:16:57 3634 [Note] Shutting down plugin 'INNODB_CMP_RESET' 2013-07-06 18:16:57 3634 [Note] Shutting down plugin 'INNODB_CMP' 2013-07-06 18:16:57 3634 [Note] Shutting down plugin 'INNODB_LOCK_WAITS' 2013-07-06 18:16:57 3634 [Note] Shutting down plugin 'INNODB_LOCKS' 2013-07-06 18:16:57 3634 [Note] Shutting down plugin 'INNODB_TRX' 2013-07-06 18:16:57 3634 [Note] Shutting down plugin 'InnoDB' 2013-07-06 18:16:57 3634 [Note] InnoDB: FTS optimize thread exiting. 2013-07-06 18:16:57 3634 [Note] InnoDB: Starting shutdown... 2013-07-06 18:16:58 3634 [Note] InnoDB: Shutdown completed; log sequence number 221000232 2013-07-06 18:16:58 3634 [Note] Shutting down plugin 'BLACKHOLE' 2013-07-06 18:16:58 3634 [Note] Shutting down plugin 'ARCHIVE' 2013-07-06 18:16:58 3634 [Note] Shutting down plugin 'MRG_MYISAM' 2013-07-06 18:16:58 3634 [Note] Shutting down plugin 'MyISAM' 2013-07-06 18:16:58 3634 [Note] Shutting down plugin 'MEMORY' 2013-07-06 18:16:58 3634 [Note] Shutting down plugin 'CSV' 2013-07-06 18:16:58 3634 [Note] Shutting down plugin 'sha256_password' 2013-07-06 18:16:58 3634 [Note] Shutting down plugin 'mysql_old_password' 2013-07-06 18:16:58 3634 [Note] Shutting down plugin 'mysql_native_password' 2013-07-06 18:16:58 3634 [Note] Shutting down plugin 'binlog' 2013-07-06 18:16:58 3634 [Note] /usr/local/mysql/bin/mysqld: Shutdown complete 130706 18:16:58 mysqld_safe mysqld from pid file /usr/local/mysql/data/server.wetworx.com.pid ended Link to comment Share on other sites More sharing options...
Dmacleo Posted July 7, 2013 Share Posted July 7, 2013 seems it matches my sql 5.6 horror story after I accidentally let it update from 5.5 to 5.6. many of those same errors. I was not able to fix it, was unstable. Link to comment Share on other sites More sharing options...
wmarcy Posted July 7, 2013 Author Share Posted July 7, 2013 What did you do? Link to comment Share on other sites More sharing options...
-RAW- Posted July 7, 2013 Share Posted July 7, 2013 this has to do with that error? http://stackoverflow.com/questions/10610875/mysql-pid-ended-cannot-start-mysql seems someone fixed by using a older version Link to comment Share on other sites More sharing options...
Dmacleo Posted July 7, 2013 Share Posted July 7, 2013 pointed everything to a vps rebuilt main server pointed stuff back. not recommended if it can be avoided. for the life of me I could never figure out why I even set the server to 5.6 as I knew there were issues with non-ipb stuff I have. all I can think of was I had maybe (I was using directadmin) accidentally uploaded the 5.6 custombuild file to the live server. so I installed cpanel as I hated directadmin anyways. so wasn't a total loss, just a huge PITA and I was more pissed that I could not figure out why the pid errors kept happening. I didn't get to spend a lot of time though before I pointed main stuff to the vps. heres the kicker, on the vps while testing I was able to roll back from 5.6 to 5.5 with no issues while on dedicated/live I could not. I also tried all the deleting .err stuff, checking files/folders/ownership/etc Link to comment Share on other sites More sharing options...
Machsterdaemon Posted July 7, 2013 Share Posted July 7, 2013 skip-locking is a deprecated option in the my.cnf configuration file for new versions. If you need something similar, then check out skip-external-locking Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.