Shulou(Shulou.com)06/01 Report--

2014.9.25

If you want to do some experiments on MySQL, you can report an error when you log in (ps:mysql service is already enabled):

Window 7 64 bit

MySQL 5.7

Log:

Click (here) to collapse or open

2014-09-25T04:19:53.971570Z 0 [Note] Plugin\ 'FEDERATED\' is disabled.

2014-09-25T04:19:53.974570Z 0 [Warning] InnoDB: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB\'s internal memory allocator.

2014-09-25T04:19:53.977570Z 0 [Note] InnoDB: The InnoDB memory heap is disabled

2014-09-25T04:19:53.978570Z 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions

2014-09-25T04:19:53.979570Z 0 [Note] InnoDB: Uses system mutexes

2014-09-25T04:19:53.980570Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.3

2014-09-25T04:19:53.982571Z 0 [Warning] InnoDB: Adjusting innodb_buffer_pool_instances from 8 to 1 since innodb_buffer_pool_size is less than 1024 MiB

2014-09-25T04:19:53.987571Z 0 [Note] InnoDB: Number of pools: 1

2014-09-25T04:19:53.988571Z 0 [Note] InnoDB: Not using CPU crc32 instructions

2014-09-25T04:19:54.003572Z 0 [Note] InnoDB: Initializing buffer pool, total size = 57.0m, instances = 1

2014-09-25T04:19:54.012572Z 0 [Note] InnoDB: Completed initialization of buffer pool

2014-09-25T04:19:54.016573Z 0 [ERROR] InnoDB:.\\ ibdata1 must be writable

2014-09-25T04:19:54.017573Z 0 [ERROR] InnoDB: The system tablespace must be writable

2014-09-25T04:19:54.218584Z 0 [ERROR] Plugin\ 'InnoDB\' init function returned error.

2014-09-25T04:19:54.219584Z 0 [ERROR] Plugin\ 'InnoDB\' registration as a STORAGE ENGINE failed.

2014-09-25T04:19:54.220584Z 0 [ERROR] mysqld: unknown option\'- p\'

2014-09-25T04:19:54.221584Z 0 [ERROR] Aborting

2014-09-25T04:19:54.222584Z 0 [Note] Binlog end

2014-09-25T04:19:54.223584Z 0 [Note] Shutting down plugin\ 'partition\'

2014-09-25T04:19:54.224584Z 0 [Note] Shutting down plugin\ 'PERFORMANCE_SCHEMA\'

2014-09-25T04:19:54.225584Z 0 [Note] Shutting down plugin\ 'INNODB_SYS_DATAFILES\'

2014-09-25T04:19:54.227585Z 0 [Note] Shutting down plugin\ 'INNODB_SYS_TABLESPACES\'

2014-09-25T04:19:54.228585Z 0 [Note] Shutting down plugin\ 'INNODB_SYS_FOREIGN_COLS\ but oddly enough, this is an error under cmd. I used Navicat for Mysql to connect to MySQL, and I can connect properly.

There are a lot of articles on the Internet, and there are several solutions that may suit your situation:

1. Delete the ib_logfile0 and ib_logfile1 files in the data directory, and restart MySQL.

-this often happens when the MySQL service is started, and the MySQL service cannot be started. But my service can be turned on and off normally:

2. Add explicit_defaults_for_timestamp=true under my.ini mysqld

-after I added it, it was still the same mistake.

3. Manually restart the MySQL service in the service.

This possibility is doubtful. Manual and command line, it should be the same.

Come back from lunch and continue to solve the problem.

But it is found that the wrong report is different.

Then comment out the added parameters.

When I log in again, I can log in.

I really don't understand. Just came into contact with MySQL, a lot of problems will not, only through du Niang and the acquaintance of Daniu.

Haha, I'm going to get off work now. I just encountered the same problem in the Linux environment:

Click (here) to collapse or open

[root@BIDEVEDW_DB bin] #. / mysqld-uroot-p

2014-09-25 17:29:05 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use-explicit_defaults_for_timestamp server option (see documentation for more details).

2014-09-25 17:29:05 24368 [Note] Plugin\ 'FEDERATED\' is disabled.

2014-09-25 17:29:05 24368 [Note] InnoDB: Using atomics to ref count buffer pool pages

2014-09-25 17:29:05 24368 [Note] InnoDB: The InnoDB memory heap is disabled

2014-09-25 17:29:05 24368 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins

2014-09-25 17:29:05 24368 [Note] InnoDB: Compressed tables use zlib 1.2.3

2014-09-25 17:29:05 24368 [Note] InnoDB: Using Linux native AIO

2014-09-25 17:29:05 24368 [Note] InnoDB: Using CPU crc32 instructions

2014-09-25 17:29:05 24368 [Note] InnoDB: Initializing buffer pool, size = 9.0G

2014-09-25 17:29:07 24368 [Note] InnoDB: Completed initialization of buffer pool

2014-09-25 17:29:08 24368 [ERROR] InnoDB: Unable to lock. / ibdata1, error: 11

2014-09-25 17:29:08 24368 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

But then you can log in:

Click (here) to collapse or open

[root@BIDEVEDW_DB bin] #. / mysql-uroot-p

Enter password:

Welcome to the MySQL monitor. Commands end with; or\\ g.

Your MySQL connection id is 19445

Server version: 5.6.19 Source distribution

Copyright (c) 2000, 2014, Oracle and/or its affiliates. All rights reserved.

Oracle is a registered trademark of Oracle Corporation and/or its

Affiliates. Other names may be trademarks of their respective

Owners.

Type\ 'help;\' or\'\ h\ 'for help. Type\'\ c\'to clear the current input statement.

Mysql > du Niang is still those, this time ask Daniel. This is a conversation with Daniel:

I finally understand how it happened!

Go home!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.