I had disk storage issue on my AWS EC2 instance. To solve this problem, I wanted to increase the volume in my EC2 instance. To do so, I had to stop my instance. When I start it again, MySQL was not going back to live.
What I assume is that either I had lost some certain files or the settings has been changed after I stopped the instance. But I could not figure that out from the log file.
2019-04-15T17:47:01.859462Z 0 [Note] InnoDB: PUNCH HOLE support available
2019-04-15T17:47:01.859482Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC
atomic builtins
2019-04-15T17:47:01.859486Z 0 [Note] InnoDB: Uses event mutexes
2019-04-15T17:47:01.859490Z 0 [Note] InnoDB: GCC builtin
__sync_synchronize() is used for memory barrier
2019-04-15T17:47:01.859494Z 0 [Note] InnoDB: Compressed tables use zlib
1.2.3
2019-04-15T17:47:01.859498Z 0 [Note] InnoDB: Using Linux native AIO
2019-04-15T17:47:01.859718Z 0 [Note] InnoDB: Number of pools: 1
2019-04-15T17:47:01.859805Z 0 [Note] InnoDB: Using CPU crc32 instructions
2019-04-15T17:47:01.861207Z 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2019-04-15T17:47:01.862285Z 0 [Note] InnoDB: Completed initialization of buffer pool
2019-04-15T17:47:01.862812Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2019-04-15T17:47:01.874471Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2019-04-15T17:47:01.884703Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2019-04-15T17:47:01.884767Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2019-04-15T17:47:01.891352Z 0 [Warning] InnoDB: 1048576 bytes should have been written. Only 458752 bytes written. Retrying for the remaining bytes.
2019-04-15T17:47:01.891379Z 0 [Warning] InnoDB: Retry attempts for writing partial data failed.
2019-04-15T17:47:01.891391Z 0 [ERROR] 2019-04-15T17:47:02.494222Z 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2019-04-15T17:47:02.494267Z 0 [ERROR] Plugin 'InnoDB' init function returned error.
2019-04-15T17:47:02.494273Z 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2019-04-15T17:47:02.494279Z 0 [ERROR] Failed to initialize builtin plugins.
2019-04-15T17:47:02.494282Z 0 [ERROR] Aborting
2019-04-15T17:47:02.494287Z 0 [Note] Binlog end
2019-04-15T17:47:02.494324Z 0 [Note] Shutting down plugin 'MyISAM'
2019-04-15T17:47:02.494338Z 0 [Note] Shutting down plugin 'CSV'
2019-04-15T17:47:02.494542Z 0 [Note] /opt/bitnami/mysql/bin/mysqld.bin: Shutdown complete
Related
Our t3.micro RDS database somehow got restarted periodically without any interaction, graph from cloudwatch shown belom: https://snipboard.io/hHWmAv.jpg
MySQL error log only showing the crash, without telling the reason behind.
2019-09-10T16:17:49.424529Z 0 [Note] Giving 24 client threads a chance to die gracefully
2019-09-10T16:17:49.426015Z 0 [Note] Shutting down slave threads
2019-09-10T16:19:02.043381Z 0 [Warning] 'NO_AUTO_CREATE_USER' sql mode was not set.
2019-09-10T16:19:02.044006Z 0 [Warning] Insecure configuration for --secure-file-priv: Location is accessible to all OS users. Consider choosing a different directory.
2019-09-10T16:19:02.044772Z 0 [Note] /rdsdbbin/mysql/bin/mysqld (mysqld 5.7.16-log) starting as process 3697 ...
2019-09-10T16:19:02.066197Z 0 [Warning] Although a path was specified for the --slow-query-log-file option, log tables are used. To enable logging to files use the --log-output=file option.
2019-09-10T16:19:02.078166Z 0 [Note] InnoDB: PUNCH HOLE support available
2019-09-10T16:19:02.078194Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-09-10T16:19:02.078197Z 0 [Note] InnoDB: Uses event mutexes
2019-09-10T16:19:02.078201Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2019-09-10T16:19:02.078204Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.3
2019-09-10T16:19:02.078207Z 0 [Note] InnoDB: Using Linux native AIO
2019-09-10T16:19:02.080206Z 0 [Note] InnoDB: Number of pools: 1
2019-09-10T16:19:02.083495Z 0 [Note] InnoDB: Using CPU crc32 instructions
2019-09-10T16:19:02.085725Z 0 [Note] InnoDB: Initializing buffer pool, total size = 384M, instances = 1, chunk size = 128M
2019-09-10T16:19:02.114854Z 0 [Note] InnoDB: Completed initialization of buffer pool
2019-09-10T16:19:02.119186Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2019-09-10T16:19:02.140345Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2019-09-10T16:19:02.146556Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 4435206383
2019-09-10T16:19:02.146572Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 4435206392
2019-09-10T16:19:02.148891Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 4435206392
2019-09-10T16:19:02.148903Z 0 [Note] InnoDB: Database was not shutdown normally!
2019-09-10T16:19:02.148907Z 0 [Note] InnoDB: Starting crash recovery.
2019-09-10T16:19:02.781069Z 0 [Note] InnoDB: Last MySQL binlog file position 0 2011, file name mysql-bin-changelog.208136
2019-09-10T16:19:03.345253Z 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2019-09-10T16:19:03.345270Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2019-09-10T16:19:03.345301Z 0 [Note] InnoDB: Setting file '/rdsdbdata/db/innodb/ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2019-09-10T16:19:03.420337Z 0 [Note] InnoDB: File '/rdsdbdata/db/innodb/ibtmp1' size is now 12 MB.
2019-09-10T16:19:03.421137Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
2019-09-10T16:19:03.421148Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
2019-09-10T16:19:03.421347Z 0 [Note] InnoDB: Waiting for purge to start
2019-09-10T16:19:03.471811Z 0 [Note] InnoDB: 5.7.16 started; log sequence number 4435206392
2019-09-10T16:19:03.472007Z 0 [Note] InnoDB: Loading buffer pool(s) from /rdsdbdata/db/innodb/ib_buffer_pool
2019-09-10T16:19:03.473460Z 0 [Note] Plugin 'FEDERATED' is disabled.
2019-09-10T16:19:03.483168Z 0 [Note] Recovering after a crash using /rdsdbdata/log/binlog/mysql-bin-changelog
2019-09-10T16:19:03.483203Z 0 [Note] Starting crash recovery...
2019-09-10T16:19:03.483253Z 0 [Note] Crash recovery finished.
Is there a way to prevent this? Or is there anymore logs that I can dig through? I've asked similar question to aws forum, sadly with no response https://forums.aws.amazon.com/message.jspa?messageID=915571#915571
I have tried everything from every forum, still no love. Deleted temp files, even a totally clean re-install.
Even created a new user on my Mac.... same issue.
Here's the MySQL log file:
2018-12-15T09:47:47.6NZ mysqld_safe Logging to '/Applications/MAMP/logs/mysql_error.log'.
2018-12-15T09:47:47.6NZ mysqld_safe Starting mysqld daemon with databases from /Library/Application Support/appsolute/MAMP PRO/db/mysql57
2018-12-15T09:47:48.230415Z 0 [Warning] Insecure configuration for --secure-file-priv: Current value does not restrict location of generated files. Consider setting it to a valid, non-empty path.
2018-12-15T09:47:48.232313Z 0 [Note] /Applications/MAMP/Library/bin/mysqld (mysqld 5.7.23) starting as process 3631 ...
2018-12-15T09:47:48.249599Z 0 [Warning] Setting lower_case_table_names=2 because file system for /Library/Application Support/appsolute/MAMP PRO/db/mysql57/ is case insensitive
2018-12-15T09:47:48.266106Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2018-12-15T09:47:48.266181Z 0 [Note] InnoDB: Uses event mutexes
2018-12-15T09:47:48.266203Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2018-12-15T09:47:48.266221Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-12-15T09:47:48.266277Z 0 [Note] InnoDB: Adjusting innodb_buffer_pool_instances from 8 to 1 since innodb_buffer_pool_size is less than 1024 MiB
2018-12-15T09:47:48.269905Z 0 [Note] InnoDB: Number of pools: 1
2018-12-15T09:47:48.273776Z 0 [Note] InnoDB: Using CPU crc32 instructions
2018-12-15T09:47:48.279178Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2018-12-15T09:47:48.301106Z 0 [Note] InnoDB: Completed initialization of buffer pool
2018-12-15T09:47:48.335445Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2018-12-15T09:47:48.339844Z 0 [ERROR] InnoDB: Ignoring the redo log due to missing MLOG_CHECKPOINT between the checkpoint 72309002 and the end 72308736.
2018-12-15T09:47:48.339913Z 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
2018-12-15T09:47:48.642547Z 0 [ERROR] Plugin 'InnoDB' init function returned error.
2018-12-15T09:47:48.642595Z 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2018-12-15T09:47:48.642616Z 0 [ERROR] Failed to initialize builtin plugins.
2018-12-15T09:47:48.642631Z 0 [ERROR] Aborting
2018-12-15T09:47:48.643113Z 0 [Note] Binlog end
2018-12-15T09:47:48.644288Z 0 [Note] Shutting down plugin 'CSV'
2018-12-15T09:47:48.645917Z 0 [Note] /Applications/MAMP/Library/bin/mysqld: Shutdown complete
2018-12-15T09:47:48.6NZ mysqld_safe mysqld from pid file /Applications/MAMP/tmp/mysql/mysql.pid ended
2018-12-15T09:58:04.6NZ mysqld_safe Logging to '/Applications/MAMP/logs/mysql_error.log'.
2018-12-15T09:58:04.6NZ mysqld_safe Starting mysqld daemon with databases from /Library/Application Support/appsolute/MAMP PRO/db/mysql57
2018-12-15T09:58:05.259005Z 0 [Warning] Insecure configuration for --secure-file-priv: Current value does not restrict location of generated files. Consider setting it to a valid, non-empty path.
2018-12-15T09:58:05.261261Z 0 [Note] /Applications/MAMP/Library/bin/mysqld (mysqld 5.7.23) starting as process 4301 ...
2018-12-15T09:58:05.280531Z 0 [Warning] Setting lower_case_table_names=2 because file system for /Library/Application Support/appsolute/MAMP PRO/db/mysql57/ is case insensitive
2018-12-15T09:58:05.298055Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2018-12-15T09:58:05.298134Z 0 [Note] InnoDB: Uses event mutexes
2018-12-15T09:58:05.298163Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2018-12-15T09:58:05.298189Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-12-15T09:58:05.298249Z 0 [Note] InnoDB: Adjusting innodb_buffer_pool_instances from 8 to 1 since innodb_buffer_pool_size is less than 1024 MiB
2018-12-15T09:58:05.301851Z 0 [Note] InnoDB: Number of pools: 1
2018-12-15T09:58:05.306424Z 0 [Note] InnoDB: Using CPU crc32 instructions
2018-12-15T09:58:05.310212Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2018-12-15T09:58:05.334016Z 0 [Note] InnoDB: Completed initialization of buffer pool
2018-12-15T09:58:05.390575Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2018-12-15T09:58:05.395800Z 0 [ERROR] InnoDB: Ignoring the redo log due to missing MLOG_CHECKPOINT between the checkpoint 72309002 and the end 72308736.
2018-12-15T09:58:05.395949Z 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
2018-12-15T09:58:05.706951Z 0 [ERROR] Plugin 'InnoDB' init function returned error.
2018-12-15T09:58:05.707019Z 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2018-12-15T09:58:05.707057Z 0 [ERROR] Failed to initialize builtin plugins.
2018-12-15T09:58:05.707106Z 0 [ERROR] Aborting
2018-12-15T09:58:05.707807Z 0 [Note] Binlog end
2018-12-15T09:58:05.709523Z 0 [Note] Shutting down plugin 'CSV'
2018-12-15T09:58:05.711283Z 0 [Note] /Applications/MAMP/Library/bin/mysqld: Shutdown complete
2018-12-15T09:58:05.6NZ mysqld_safe mysqld from pid file /Applications/MAMP/tmp/mysql/mysql.pid ended
sudo killall -9 mysqld
Run the code in terminal and restart MAMP server.
I have phpMyAdmin installed on Ubuntu 16.04 Lamp Server on an Oracle VM. When I try to enter phpMyAdmin via http://localhost/phpmyadmin, I receive the following error:
Error: #2002 - No such file or directoryThe server is not responding
After reading previous threads, I have tried to unsuccessfully reinstall mysql-server to no avail. The MySQL error log in /var/log/... contains the following:
2017-01-22T16:18:06.214161Z 0 [Warning] Changed limits: max_open_files: 1024 (requested 5000)
2017-01-22T16:18:06.214326Z 0 [Warning] Changed limits: table_open_cache: 431 (requested 2000)
2017-01-22T16:18:06.536519Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2017-01-22T16:18:06.543467Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.17-0ubuntu0.16.04.1) starting as process 3647 ...
2017-01-22T16:18:06.571026Z 0 [Note] InnoDB: PUNCH HOLE support available
2017-01-22T16:18:06.571095Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-01-22T16:18:06.571106Z 0 [Note] InnoDB: Uses event mutexes
2017-01-22T16:18:06.571120Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2017-01-22T16:18:06.571130Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.8
2017-01-22T16:18:06.571139Z 0 [Note] InnoDB: Using Linux native AIO
2017-01-22T16:18:06.571731Z 0 [Note] InnoDB: Number of pools: 1
2017-01-22T16:18:06.571975Z 0 [Note] InnoDB: Using CPU crc32 instructions
2017-01-22T16:18:06.577202Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2017-01-22T16:18:06.625715Z 0 [Note] InnoDB: Completed initialization of buffer pool
2017-01-22T16:18:06.631873Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2017-01-22T16:18:06.647876Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2017-01-22T16:18:06.736500Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2017-01-22T16:18:06.736633Z 0 [Note] InnoDB: Setting file \'./ibtmp1\' size to 12 MB. Physically writing the file full; Please wait ...
2017-01-22T16:18:07.143892Z 0 [Note] InnoDB: File \'./ibtmp1\' size is now 12 MB.
2017-01-22T16:18:07.145163Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
2017-01-22T16:18:07.145188Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
2017-01-22T16:18:07.150769Z 0 [Note] InnoDB: Waiting for purge to start
2017-01-22T16:18:07.201406Z 0 [Note] InnoDB: 5.7.17 started; log sequence number 16765716
2017-01-22T16:18:07.207484Z 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
2017-01-22T16:18:07.208190Z 0 [Note] InnoDB: Buffer pool(s) load completed at 170122 17:18:07
2017-01-22T16:18:07.208412Z 0 [Note] Plugin \'FEDERATED\' is disabled.
2017-01-22T16:18:07.229256Z 0 [Warning] Failed to set up SSL because of the following SSL library error: SSL context is not usable without certificate and private key
2017-01-22T16:18:07.229286Z 0 [Note] Server hostname (bind-address): \'127.0.0.1\'; port: 3306
2017-01-22T16:18:07.229302Z 0 [Note] - \'127.0.0.1\' resolves to \'127.0.0.1\';
2017-01-22T16:18:07.229351Z 0 [Note] Server socket created on IP: \'127.0.0.1\'.
2017-01-22T16:18:07.230207Z 0 [ERROR] Fatal error: Can\'t open and lock privilege tables: Incorrect file format \'user\'
2017-01-22T16:18:07.230287Z 0 [ERROR] Aborting
');
I have tried to apply various solutions including this - MySQL Fatal error: Can't open and lock privilege tables: Incorrect file format 'user'
Unfortunately, I am not able to access Mysql and therefore unable to follow the solution. $ sudo mysqld --skip-grant-tables does not allow me to access it.
UPDATE: Solved! Here is my solution:
Todays systems are often running on a disk which is formatted in GPT. This is because Windows 10 needs such a partition to be installed. The problem is that MySql cant deal with this partition style and so it crashes. Here is my workaround:
Create a virtual disk: manual here
Format this VHD with MBR
Install MySql custom on your new VHD (dont forget to create a user
for DB)
This should be it! :)
I try to install MySql on my Dell XPS 13 9360 with Windows 10. When it comes to starting the server as a service, the service cannot start. As so far this problem is widely known and there are many attempts to solve this issue. Unfortunately non of these work for me. Here is what I tried:
insert innodb_flush_method=normal into my.ini
change service to register at local account
check firewall for port rules
So my question: Does anybody experience the same issue and knows a way to get it running? You would help me really so much :)
Here is my error log:
2017-01-23T14:11:44.458654Z 0 [Warning] option 'new': boolean value 't' wasn't recognized. Set to OFF.
2017-01-23T14:11:44.458654Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2017-01-23T14:11:44.458654Z 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
2017-01-23T14:11:44.459156Z 0 [Note] mysqld (mysqld 5.7.17) starting as process 5340 ...
2017-01-23T14:11:44.468178Z 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-01-23T14:11:44.469212Z 0 [Note] InnoDB: Uses event mutexes
2017-01-23T14:11:44.469713Z 0 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2017-01-23T14:11:44.470716Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-01-23T14:11:44.471217Z 0 [Note] InnoDB: Number of pools: 1
2017-01-23T14:11:44.471719Z 0 [Note] InnoDB: Not using CPU crc32 instructions
2017-01-23T14:11:44.474727Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2017-01-23T14:11:44.481212Z 0 [Note] InnoDB: Completed initialization of buffer pool
2017-01-23T14:11:44.546889Z 0 [ERROR] InnoDB: Header page consists of zero bytes in datafile: .\ibdata1, Space ID:0, Flags: 0. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2017-01-23T14:11:44.548924Z 0 [ERROR] InnoDB: Corrupted page [page id: space=0, page number=0] of datafile '.\ibdata1' could not be found in the doublewrite buffer.
2017-01-23T14:11:44.550425Z 0 [ERROR] InnoDB: Plugin initialization aborted with error Data structure corruption
2017-01-23T14:11:44.771283Z 0 [ERROR] Plugin 'InnoDB' init function returned error.
2017-01-23T14:11:44.772134Z 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2017-01-23T14:11:44.772635Z 0 [ERROR] Failed to initialize plugins.
2017-01-23T14:11:44.773135Z 0 [ERROR] Aborting
2017-01-23T14:11:44.773636Z 0 [Note] Binlog end
2017-01-23T14:11:44.774138Z 0 [Note] Shutting down plugin 'CSV'
2017-01-23T14:11:44.774640Z 0 [Note] mysqld: Shutdown complete
thank you in advance!
#Bill Karwin :
OK, so after removing the tablespace the result is this:
2017-01-23T15:39:39.874463Z 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
2017-01-23T15:39:39.874965Z 0 [Note] mysqld (mysqld 5.7.17) starting as process 624 ...
2017-01-23T15:39:39.880480Z 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-01-23T15:39:39.880980Z 0 [Note] InnoDB: Uses event mutexes
2017-01-23T15:39:39.881484Z 0 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2017-01-23T15:39:39.882022Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-01-23T15:39:39.882986Z 0 [Note] InnoDB: Number of pools: 1
2017-01-23T15:39:39.882986Z 0 [Note] InnoDB: Not using CPU crc32 instructions
2017-01-23T15:39:39.885491Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2017-01-23T15:39:39.891024Z 0 [Note] InnoDB: Completed initialization of buffer pool
2017-01-23T15:39:39.914631Z 0 [Note] InnoDB: The first innodb_system data file 'ibdata1' did not exist. A new tablespace will be created!
2017-01-23T15:39:39.915071Z 0 [ERROR] InnoDB: redo log file '.\ib_logfile1' exists. Creating system tablespace with existing redo log files is not recommended. Please delete all redo log files before creating new system tablespace.
2017-01-23T15:39:39.916074Z 0 [ERROR] InnoDB: InnoDB Database creation was aborted with error Generic error. You may need to delete the ibdata1 file before trying to start up again.
2017-01-23T15:39:40.132668Z 0 [ERROR] Plugin 'InnoDB' init function returned error.
2017-01-23T15:39:40.132668Z 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2017-01-23T15:39:40.134090Z 0 [ERROR] Failed to initialize plugins.
2017-01-23T15:39:40.134590Z 0 [ERROR] Aborting
2017-01-23T15:39:40.135594Z 0 [Note] Binlog end
2017-01-23T15:39:40.136094Z 0 [Note] Shutting down plugin 'CSV'
2017-01-23T15:39:40.136595Z 0 [Note] mysqld: Shutdown complete
new error after deleting logdata1 and 0:
2017-01-23T15:55:22.158765Z 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
2017-01-23T15:55:22.159266Z 0 [Note] mysqld (mysqld 5.7.17) starting as process 2880 ...
2017-01-23T15:55:22.165783Z 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-01-23T15:55:22.165783Z 0 [Note] InnoDB: Uses event mutexes
2017-01-23T15:55:22.165783Z 0 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2017-01-23T15:55:22.166284Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-01-23T15:55:22.166284Z 0 [Note] InnoDB: Number of pools: 1
2017-01-23T15:55:22.166786Z 0 [Note] InnoDB: Not using CPU crc32 instructions
2017-01-23T15:55:22.169292Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2017-01-23T15:55:22.178820Z 0 [Note] InnoDB: Completed initialization of buffer pool
2017-01-23T15:55:22.202407Z 0 [Note] InnoDB: The first innodb_system data file 'ibdata1' did not exist. A new tablespace will be created!
2017-01-23T15:55:22.203383Z 0 [Note] InnoDB: Setting file '.\ibdata1' size to 12 MB. Physically writing the file full; Please wait ...
2017-01-23T15:55:22.249691Z 0 [Note] InnoDB: File '.\ibdata1' size is now 12 MB.
2017-01-23T15:55:22.263685Z 0 [Note] InnoDB: Setting log file .\ib_logfile101 size to 48 MB
2017-01-23T15:55:22.342287Z 0 [Note] InnoDB: Setting log file .\ib_logfile1 size to 48 MB
2017-01-23T15:55:22.452340Z 0 [ERROR] InnoDB: Operating system error number 87 in a file operation.
2017-01-23T15:55:22.452842Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2017-01-23T15:55:22.453346Z 0 [ERROR] InnoDB: File .\ib_logfile101: 'aio write' returned OS error 187. Cannot continue operation
2017-01-23T15:55:22.453346Z 0 [ERROR] InnoDB: Cannot continue operation.
Found the solution:
Todays systems are often running on a disk which is formatted in GPT. This is because Windows 10 needs such a partition to be installed. The problem is that MySql cant deal with this partition style and so it crashes. Here is my workaround:
Create a virtual disk: manual here
Format this VHD with MBR
Install MySql custom on your new VHD (dont forget to create a user for DB)
This should be it! :)
I've a MySQL server which I'm writing to about every 10 minutes. It seems to work fine then when I go back to it a few hours later it has crashed.
From error.log I have
2017-01-17T13:47:35.315801Z 0 [Warning] Changed limits: max_open_files: 1024 (requested 5000)
2017-01-17T13:47:35.315905Z 0 [Warning] Changed limits: table_open_cache: 431 (requested 2000)
2017-01-17T13:47:35.495187Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp serv$
2017-01-17T13:47:35.497022Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.16-0ubuntu0.16.04.1) starting as process 18742 ...
2017-01-17T13:47:35.505459Z 0 [Note] InnoDB: PUNCH HOLE support available
2017-01-17T13:47:35.505530Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-01-17T13:47:35.505541Z 0 [Note] InnoDB: Uses event mutexes
2017-01-17T13:47:35.505549Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2017-01-17T13:47:35.505558Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.8
2017-01-17T13:47:35.505566Z 0 [Note] InnoDB: Using Linux native AIO
2017-01-17T13:47:35.506116Z 0 [Note] InnoDB: Number of pools: 1
2017-01-17T13:47:35.506338Z 0 [Note] InnoDB: Using CPU crc32 instructions
2017-01-17T13:47:35.508891Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2017-01-17T13:47:35.508951Z 0 [ERROR] InnoDB: mmap(137428992 bytes) failed; errno 12
2017-01-17T13:47:35.508973Z 0 [ERROR] InnoDB: Cannot allocate memory for the buffer pool
2017-01-17T13:47:35.508983Z 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
2017-01-17T13:47:35.508994Z 0 [ERROR] Plugin 'InnoDB' init function returned error.
2017-01-17T13:47:35.509002Z 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2017-01-17T13:47:35.509011Z 0 [ERROR] Failed to initialize plugins.
2017-01-17T13:47:35.509017Z 0 [ERROR] Aborting
2017-01-17T13:47:35.509026Z 0 [Note] Binlog end
2017-01-17T13:47:35.509098Z 0 [Note] Shutting down plugin 'CSV'
2017-01-17T13:47:35.509118Z 0 [Note] Shutting down plugin 'MyISAM'
2017-01-17T13:47:35.509507Z 0 [Note] /usr/sbin/mysqld: Shutdown complete
This is a database I'm running from Python/Django, not that I think that should make any difference. I do not know what is going wrong but if I reboot the server it starts up and works fine. Could you help please.
I increased the size of the server and it has been working fine. I'll live with it