> 2014-11-07 10:17:01 2224 [ERROR] InnoDB: ./ibdata1 can't be opened in > read-write mode
Are the permissions correct on the mysql DB files and directories? Do you have SELinux enabled? -Jonh On Nov 7, 2014, at 10:43 AM, dan moylan <j...@moylan.us> wrote: > > john hall writes: >> I'm still figuring this out too. MariaDB is the >> version/branch included with Fedora 19, 20 and RHEL 7. I >> believe you will find an additional repository like >> repo.mysql.com is enabled in the list from: #yum repolist > > moylan ~[1025] yum repolist > Loaded plugins: langpacks, refresh-packagekit > repo id repo name > status > fedora/20/x86_64 Fedora 20 - x86_64 > 38,597 > !mysql-connectors-community/20/x86_64 MySQL Connectors Community > 19 > !mysql-tools-community/20/x86_64 MySQL Tools Community > 13 > !mysql56-community/20/x86_64 MySQL 5.6 Community Server > 89 > !updates/20/x86_64 Fedora 20 - x86_64 - Updates > 20,178 > repolist: 58,896 > >> I suspect it may be smoother to use MariaDB since that is >> what the rest of the packages in the distro will be tuned >> for, but it really might not make much difference in the >> long run. Please share differences if you learn about any. > >> To find your logs you might type >> # ps aux | egrep mysql >> as root and look at the command line for the main process >> which will might list the log file path as an option. > > root ~[404] ps -au root | egrep mysql > 27517 0 Ss 12:35 /bin/bash /usr/bin/mysql-systemd-start post > 28358 0 S+ 12:39 egrep --color=auto mysql > >> This works for mariadb - the error logs are by default at: >> /var/log/mariadb/mariadb.log >> and the service name is mariadb.service. The mysql name is >> used by mariadb in some seemingly random places - I imagine >> for backward compatibility with some tools. ( I think the >> socket file is one example.) It seems at least that the >> database and connections work the same way. > > /var/log/mariadb/ does not exist. > this from /var/log/mysqld.log: > > 141107 10:17:00 mysqld_safe Starting mysqld daemon with databases from > /var/lib/mysql > 2014-11-07 10:17:01 0 [Warning] TIMESTAMP with implicit DEFAULT value is > deprecated. Please use --explicit_defaults_for_timestamp server option (see > documentation for more details). > 2014-11-07 10:17:01 2224 [Warning] Buffered warning: Changed limits: > max_open_files: 1024 (requested 5000) > > 2014-11-07 10:17:01 2224 [Warning] Buffered warning: Changed limits: > table_cache: 431 (requested 2000) > > 2014-11-07 10:17:01 2224 [Note] Plugin 'FEDERATED' is disabled. > /usr/sbin/mysqld: Can't find file: './mysql/plugin.frm' (errno: 13 - > Permission denied) > 2014-11-07 10:17:01 2224 [ERROR] Can't open the mysql.plugin table. Please > run mysql_upgrade to create it. > > 2014-11-07 10:17:01 2224 [Note] InnoDB: Using atomics to ref count buffer > pool pages > 2014-11-07 10:17:01 2224 [Note] InnoDB: The InnoDB memory heap is disabled > 2014-11-07 10:17:01 2224 [Note] InnoDB: Mutexes and rw_locks use GCC atomic > builtins > 2014-11-07 10:17:01 2224 [Note] InnoDB: Memory barrier is not used > 2014-11-07 10:17:01 2224 [Note] InnoDB: Compressed tables use zlib 1.2.3 > 2014-11-07 10:17:01 2224 [Note] InnoDB: Using Linux native AIO > 2014-11-07 10:17:01 2224 [Note] InnoDB: Not using CPU crc32 instructions > 2014-11-07 10:17:01 2224 [Note] InnoDB: Initializing buffer pool, size = > 128.0M > 2014-11-07 10:17:01 2224 [Note] InnoDB: Completed initialization of buffer > pool > 2014-11-07 10:17:01 2224 [ERROR] InnoDB: ./ibdata1 can't be opened in > read-write mode > 2014-11-07 10:17:01 2224 [ERROR] InnoDB: The system tablespace must be > writable! > 2014-11-07 10:17:01 2224 [ERROR] Plugin 'InnoDB' init function returned error. > 2014-11-07 10:17:01 2224 [ERROR] Plugin 'InnoDB' registration as a STORAGE > ENGINE failed. > 2014-11-07 10:17:01 2224 [ERROR] Unknown/unsupported storage engine: InnoDB > 2014-11-07 10:17:01 2224 [ERROR] Aborting > > 2014-11-07 10:17:01 2224 [Note] Binlog end > 2014-11-07 10:17:01 2224 [Note] Shutting down plugin 'partition' > . > . > . > 2014-11-07 10:17:01 2224 [Note] /usr/sbin/mysqld: Shutdown complete > > 141107 10:17:01 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid > ended > > root ~[420] mysql_upgrade > Looking for 'mysql' as: mysql > Looking for 'mysqlcheck' as: mysqlcheck > FATAL ERROR: Upgrade failed > > (both mysql and mysqlcheck exist in /usr/bin) > > ugh. > > david kramer writes: >> This may be old information, but it at USED TO be the case that: > >> - mysql could be configured to listen on a socket or listen >> to a IP address and port. >> - mysql, as shipped, would only respond to localhost >> I would check that in the configuration. > >> You might also want to try "mysql -h localhost" to try to connect over >> IP instead of socket. > > root ~[422] mysql -h localhost > ERROR 2002 (HY000): Can't connect to local MySQL server > through socket '/var/lib/mysql/mysql.sock' (2) > > i also tried: > > root ~[423] mysql --bind-address=127.0.0.1 > ERROR 2002 (HY000): Can't connect to local MySQL server > through socket '/var/lib/mysql/mysql.sock' (2) > > thanks, still fumbling, struggling. > > ole dan > > j. daniel moylan > 84 harvard ave > brookline, ma 02446-6202 > 617-777-0207 (cel) > j...@moylan.us > www.moylan.us > [avoid html waste.] > _______________________________________________ > Discuss mailing list > Discuss@blu.org > http://lists.blu.org/mailman/listinfo/discuss _______________________________________________ Discuss mailing list Discuss@blu.org http://lists.blu.org/mailman/listinfo/discuss
