My database (mysql) server (google cloud SQL) keeps crashing / restarting and I am at a loss of what to do.
Version: '5.5.46' socket: '' port: 0 (34, 36) (Google)
160427 7:20:12 [Note] : ready for connections.
160427 7:20:12 [Note] Event Scheduler: scheduler thread started with id 1
160427 7:20:12 [Note] Event Scheduler: Loaded 0 events
160427 7:20:11 InnoDB: 5.5.46 started; log sequence number 718527543
InnoDB: buffer...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Starting crash recovery.
160427 7:20:06 InnoDB: Database was not shut down normally!
InnoDB: the log sequence number in the ib_logfiles!
InnoDB: The log sequence number in ibdata files does not match
160427 7:20:06 InnoDB: highest supported file format is Barracuda.
160427 7:20:06 InnoDB: Completed initialization of buffer pool
160427 7:20:06 InnoDB: Initializing buffer pool, size = 96.0M
160427 7:20:06 InnoDB: Compressed tables use zlib 1.2.8
160427 7:20:06 InnoDB: Mutexes and rw_locks use InnoDB's own implementation
160427 7:20:06 InnoDB: The InnoDB memory heap is disabled
160427 7:20:06 [Note] (mysqld 5.5.46) starting as process 392594 ...
160427 7:20:06 [Warning] options --log-slow-admin-statements, --log-queries-not-using-indexes and --log-slow-slave-statements have no effect if
Related
i have been trying to turn on mysql on xampp but it wouldn't turn on. i went to mysql logs and to the errorlog file and here are the things they gave.
2015-11-23 10:54:20 d274 InnoDB: Warning: 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.
151123 10:54:20 [Note] InnoDB: Using mutexes to ref count buffer pool pages
151123 10:54:20 [Note] InnoDB: The InnoDB memory heap is disabled
151123 10:54:20 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
151123 10:54:20 [Note] InnoDB: Memory barrier is not used
151123 10:54:20 [Note] InnoDB: Compressed tables use zlib 1.2.3
151123 10:54:20 [Note] InnoDB: Not using CPU crc32 instructions
151123 10:54:20 [Note] InnoDB: Initializing buffer pool, size = 16.0M
151123 10:54:20 [Note] InnoDB: Completed initialization of buffer pool
151123 10:54:20 [Note] InnoDB: Highest supported file format is Barracuda.
151123 10:54:20 [Note] InnoDB: Log scan progressed past the checkpoint lsn 1735623
151123 10:54:20 [Note] InnoDB: Database was not shutdown normally!
151123 10:54:20 [Note] InnoDB: Starting crash recovery.
151123 10:54:20 [Note] InnoDB: Reading tablespace information from the .ibd files...
151123 10:54:20 [Note] InnoDB: Restoring possible half-written data pages
151123 10:54:20 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 1735633
151123 10:54:20 [Note] InnoDB: 128 rollback segment(s) are active.
151123 10:54:20 [Note] InnoDB: Waiting for purge to start
151123 10:54:20 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.22-72.0 started; log sequence number 1735633
151123 10:54:20 [Note] Plugin 'FEEDBACK' is disabled.
151123 10:54:20 [Note] Server socket created on IP: '::'.
The log seems ok for me. Maybe you have permission problem, try (right click) run as Administrator the Xampp
try check your active port, maybe used by another program. Mysql use 3306 as default port. go to your xampp folder try find "portcheck.exe" or something like that. see if your mysql port used or free.
I am experiencing regular MySQL server crashes (on Linux). After running
sudo /etc/init.d/mysql restart
the problem goes away, but temporary. It might be one day or couple, but the crash will happen anyway. Here's an excerpt from the error log file, after the crash and before the daemon restart. I am not sure it reflects any useful information though.
140511 0:11:06 [Note] Plugin 'FEDERATED' is disabled.
140511 0:11:37 InnoDB: Initializing buffer pool, size = 8.0M
140511 0:11:38 InnoDB: Completed initialization of buffer pool
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
140511 0:11:52 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
140511 0:14:26 InnoDB: Started; log sequence number 1 3968482280
140511 0:16:46 [Note] Event Scheduler: Loaded 0 events
140511 0:16:46 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.1.69-0ubuntu0.11.10.1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)
140511 0:22:00 [Note] Plugin 'FEDERATED' is disabled.
140511 0:22:46 InnoDB: Initializing buffer pool, size = 8.0M
140511 0:22:46 InnoDB: Completed initialization of buffer pool
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
140511 0:22:52 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
140511 0:24:41 InnoDB: Started; log sequence number 1 3968482290
140511 0:26:55 [Note] Event Scheduler: Loaded 0 events
140511 0:26:56 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.1.69-0ubuntu0.11.10.1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)
The problem did not disappear after reinstalling the server.
Perhaps it's time to install the database on clean OS install, and bring all my databases there, but before such time-consuming solution I'd like to try some less-involving ones, if there are any.
I am trying to install multiple instances of MySQL on a Windows Server 2003 using this link.
First instance which is on port 6699 get configured and working successfully. But when I try to install another instance on default port (3306) MySQL service gets hung on "Starting" status. This is the log
140210 17:13:20 [Note] Plugin 'FEDERATED' is disabled.
140210 17:13:20 InnoDB: The InnoDB memory heap is disabled
140210 17:13:20 InnoDB: Mutexes and rw_locks use Windows interlocked functions
140210 17:13:20 InnoDB: Compressed tables use zlib 1.2.3
140210 17:13:20 InnoDB: Initializing buffer pool, size = 128.0M
140210 17:13:20 InnoDB: Completed initialization of buffer pool
InnoDB: The first specified data file .\ibdata1 did not exist:
InnoDB: a new database to be created!
140210 17:13:21 InnoDB: Setting file .\ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
140210 17:13:21 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...
140210 17:13:23 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: 127 rollback segment(s) active.
InnoDB: Creating foreign key constraint system tables
InnoDB: Foreign key constraint system tables created
140210 17:13:26 InnoDB: Waiting for the background threads to start
140210 17:13:27 InnoDB: 1.1.8 started; log sequence number 0
140210 17:13:27 [Note] Server hostname (bind-address): '0.0.0.0'; port: 6699
140210 17:13:27 [Note] - '0.0.0.0' resolves to '0.0.0.0';
140210 17:13:27 [Note] Server socket created on IP: '0.0.0.0'.
140210 17:13:27 [Note] Event Scheduler: Loaded 0 events
140210 17:13:27 [Note] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld.exe: ready for connections.
Version: '5.5.25' socket: '' port: 6699 MySQL Community Server (GPL)
140210 17:42:18 [Note] Plugin 'FEDERATED' is disabled.
140210 17:42:18 InnoDB: The InnoDB memory heap is disabled
140210 17:42:18 InnoDB: Mutexes and rw_locks use Windows interlocked functions
140210 17:42:18 InnoDB: Compressed tables use zlib 1.2.3
140210 17:42:19 InnoDB: Initializing buffer pool, size = 128.0M
140210 17:42:19 InnoDB: Completed initialization of buffer pool
140210 17:42:19 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
Observe line 140210 17:42:19 InnoDB: Database was not shut down normally!
InnoDB: The log sequence number in ibdata files does not match
Double check your configuration!
Make a binay backup or entire /var/lib/mysql.
If you don't need most recent data, delete the log files and try to start.
If you need your data, try the followling:
Try innodb_force_recovery = 1 to 6 all six options in an increasing order.
Assume the worst -- innodb disk image corrupted.
If you are lucky you can salvage most of your data, perhaps mysql starts in one of recovery modes, run checksum on each table, see what tables are still ok.
If mysql refuses to start up to certain recovery mode N and crashes on startup with recovery mode N, then go looking for those daily/weekly backups I hope you system was configured to take.
Mysql craches almost every day and I need to restart MYSQL..
Own VPS 512MB ram, mysql logs :
131115 10:03:36 [Note] Plugin 'FEDERATED' is disabled.
131115 10:03:36 InnoDB: The InnoDB memory heap is disabled
131115 10:03:36 InnoDB: Mutexes and rw_locks use GCC atomic builtins
131115 10:03:36 InnoDB: Compressed tables use zlib 1.2.3.4
131115 10:03:36 InnoDB: Initializing buffer pool, size = 128.0M
131115 10:03:36 InnoDB: Completed initialization of buffer pool
131115 10:03:36 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
131115 10:03:36 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
Is this log about shutting down or starting?
I suppose your machine was abnormally shut down which caused damage of logs. So, your db files are inconsistent because of mysqld was not stopped gracefully and your log-files (durability records) are inconsistent too because of physical storage damage.
In my Moodle database, everytime I select the mdl_certificate table, the MySQL server goes down. I thought it could be a problem with the PHPMyAdmin, but I installed the MySQL Workbench and the same still happens.
So I tried the console. The problem persists. I got two prints:
I've never seen this. How can I solve it?
Thanks!
UPDATE:
This is the log around the time the error was showed:
130411 8:51:20 [Note] Plugin 'FEDERATED' is disabled.
130411 8:51:20 InnoDB: The InnoDB memory heap is disabled
130411 8:51:20 InnoDB: Mutexes and rw_locks use Windows interlocked functions
130411 8:51:20 InnoDB: Compressed tables use zlib 1.2.3
130411 8:51:20 InnoDB: Initializing buffer pool, size = 128.0M
130411 8:51:20 InnoDB: Completed initialization of buffer pool
130411 8:51:20 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
130411 8:51:20 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
130411 8:51:20 InnoDB: Operating system error number 1392 in a file operation.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/operating-system-error-codes.html
InnoDB: File name .\prestashopprod
InnoDB: File operation call: 'readdir_next_file'.
InnoDB: Error: os_file_readdir_next_file() returned -1 in
InnoDB: directory .\prestashopprod
InnoDB: Crash recovery may have failed for some .ibd files!
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Last MySQL binlog file position 0 4793, file name .\mysql-bin.000062
130411 8:51:33 InnoDB: Waiting for the background threads to start
130411 8:51:34 InnoDB: 1.1.8 started; log sequence number 795429719
130411 8:51:34 [Note] Recovering after a crash using mysql-bin
130411 8:51:34 [Note] Starting crash recovery...
130411 8:51:34 [Note] Crash recovery finished.
130411 8:51:34 [Note] Event Scheduler: Loaded 0 events
130411 8:51:34 [Note] wampmysqld: ready for connections.
Version: '5.5.20-log' socket: '' port: 3306 MySQL Community Server (GPL)
The solution was drop the tables and re-create them. Luckly, they were empty.