MySQL Forums
Forum List  »  InnoDB

Re: InnoDB error
Posted by: lg
Date: March 16, 2005 09:48AM

Sorry for the late reply, missed your message.

"
Restarting MySql in these case didn't help, I had to restart the whole machine to get it up and
running again.
"

Our MySql server is installed as a service and configured to restart automatically. In this case restarting the server didn't work ( it just didn't restart ). Only after restarting machine ( without doing anything else! ) restarting the MySql server worked.

Attached is the log. You'll notice that it happened twice, first on the 3rd of march, and second time today. The second time ( today ), the MySQL server automatically restarted without having to reboot the machine.

You won't notice in the log that I tried to restart the MySql server multiple times the morning of the 4th of march. There are however some event logs ( in the application part ) that said:
------------
Do you already have another mysqld server running on port: 3100 ?

For more information, see Help and Support Center at http://www.mysql.com.
------------

Which was strange, because that mysqld-nt server was not in the process list, nor did netstat -a
reveal a process listening on port 3100.

I'm not sure if the InnoDB errors play a part in this error?

We only have 3 or 4 programs connected on this db server, and they keep their connection open. What we do have running is:
- a backup script
- a cleanup script
- nagios monitors ( 24x7, 8 checks, each 5 minutes ), including a TCP port check on 3100.

It happens to be that when the Mysql server shut down the evening of the 3rd, that was exactly at the same time the cleanup script was running.

regards,

Lieven.


dev9.err:
-----------------------------------------------------------------------------------------------
050226 3:10:21 InnoDB: Started
MySql: ready for connections.
Version: '4.0.22-nt' socket: '' port: 3100 Source distribution
050226 22:57:56 InnoDB: ERROR: the age of the last checkpoint is 9433641,
InnoDB: which exceeds the log group capacity 9433498.
InnoDB: If you are using big BLOB or TEXT rows, you must set the
InnoDB: combined size of log files at least 10 times bigger than the
InnoDB: largest such row.
050301 22:59:53 InnoDB: ERROR: the age of the last checkpoint is 9433819,
InnoDB: which exceeds the log group capacity 9433498.
InnoDB: If you are using big BLOB or TEXT rows, you must set the
InnoDB: combined size of log files at least 10 times bigger than the
InnoDB: largest such row.
050302 22:59:54 InnoDB: ERROR: the age of the last checkpoint is 9433709,
InnoDB: which exceeds the log group capacity 9433498.
InnoDB: If you are using big BLOB or TEXT rows, you must set the
InnoDB: combined size of log files at least 10 times bigger than the
InnoDB: largest such row.
050303 22:59:53 InnoDB: ERROR: the age of the last checkpoint is 9433676,
InnoDB: which exceeds the log group capacity 9433498.
InnoDB: If you are using big BLOB or TEXT rows, you must set the
InnoDB: combined size of log files at least 10 times bigger than the
InnoDB: largest such row.
050303 23:00:09 InnoDB: ERROR: the age of the last checkpoint is 63107665,
InnoDB: which exceeds the log group capacity 9433498.
InnoDB: If you are using big BLOB or TEXT rows, you must set the
InnoDB: combined size of log files at least 10 times bigger than the
InnoDB: largest such row.
050303 23:00:25 InnoDB: ERROR: the age of the last checkpoint is 70018230,
InnoDB: which exceeds the log group capacity 9433498.
InnoDB: If you are using big BLOB or TEXT rows, you must set the
InnoDB: combined size of log files at least 10 times bigger than the
InnoDB: largest such row.
050303 23:00:41 InnoDB: ERROR: the age of the last checkpoint is 76332696,
InnoDB: which exceeds the log group capacity 9433498.
InnoDB: If you are using big BLOB or TEXT rows, you must set the
InnoDB: combined size of log files at least 10 times bigger than the
InnoDB: largest such row.
050303 23:00:58 InnoDB: ERROR: the age of the last checkpoint is 83398387,
InnoDB: which exceeds the log group capacity 9433498.
InnoDB: If you are using big BLOB or TEXT rows, you must set the
InnoDB: combined size of log files at least 10 times bigger than the
InnoDB: largest such row.
050303 23:01:14 InnoDB: ERROR: the age of the last checkpoint is 90464995,
InnoDB: which exceeds the log group capacity 9433498.
InnoDB: If you are using big BLOB or TEXT rows, you must set the
InnoDB: combined size of log files at least 10 times bigger than the
InnoDB: largest such row.
050303 23:01:30 InnoDB: ERROR: the age of the last checkpoint is 99820658,
InnoDB: which exceeds the log group capacity 9433498.
InnoDB: If you are using big BLOB or TEXT rows, you must set the
InnoDB: combined size of log files at least 10 times bigger than the
InnoDB: largest such row.
050303 23:01:46 InnoDB: ERROR: the age of the last checkpoint is 105403507,
InnoDB: which exceeds the log group capacity 9433498.
InnoDB: If you are using big BLOB or TEXT rows, you must set the
InnoDB: combined size of log files at least 10 times bigger than the
InnoDB: largest such row.
050303 23:03:58 InnoDB: Operating system error number 995 in a file operation.
InnoDB: See http://dev.mysql.com/doc/mysql/en/InnoDB.html
InnoDB: for installation help.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/mysql/en/Operating_System_error_codes.html
InnoDB: File name .\ibdata1
InnoDB: File operation call: 'Windows aio'.
InnoDB: Cannot continue operation.
050304 8:59:02 InnoDB: Database was not shut down normally.
InnoDB: Starting recovery from log files...
InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 1 3152118222
InnoDB: Doing recovery: scanned up to log sequence number 1 3157360640
InnoDB: Doing recovery: scanned up to log sequence number 1 3159006334
InnoDB: 2 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 60502 row operations to undo
InnoDB: Trx id counter is 0 23796992
050304 8:59:06 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
InnoDB: Starting rollback of uncommitted transactions
InnoDB: Rolling back trx with id 0 23796608, 2 rows to undo
InnoDB: Rolling back of trx id 0 23796608 completed
InnoDB: Rolling back trx with id 0 23796377, 60500 rows to undo
InnoDB: Progress in percents: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100
InnoDB: Rolling back of trx id 0 23796377 completed
InnoDB: Rollback of uncommitted transactions completed
050304 8:59:52 InnoDB: Flushing modified pages from the buffer pool...
050304 9:00:36 InnoDB: Started
MySql: ready for connections.
Version: '4.0.22-nt' socket: '' port: 3100 Source distribution
050308 17:12:32 InnoDB: ERROR: the age of the last checkpoint is 9433811,
InnoDB: which exceeds the log group capacity 9433498.
InnoDB: If you are using big BLOB or TEXT rows, you must set the
InnoDB: combined size of log files at least 10 times bigger than the
InnoDB: largest such row.
050315 17:29:59 InnoDB: ERROR: the age of the last checkpoint is 9433586,
InnoDB: which exceeds the log group capacity 9433498.
InnoDB: If you are using big BLOB or TEXT rows, you must set the
InnoDB: combined size of log files at least 10 times bigger than the
InnoDB: largest such row.
050315 17:30:15 InnoDB: ERROR: the age of the last checkpoint is 61465656,
InnoDB: which exceeds the log group capacity 9433498.
InnoDB: If you are using big BLOB or TEXT rows, you must set the
InnoDB: combined size of log files at least 10 times bigger than the
InnoDB: largest such row.
050315 17:30:31 InnoDB: ERROR: the age of the last checkpoint is 67080783,
InnoDB: which exceeds the log group capacity 9433498.
InnoDB: If you are using big BLOB or TEXT rows, you must set the
InnoDB: combined size of log files at least 10 times bigger than the
InnoDB: largest such row.
050315 17:30:47 InnoDB: ERROR: the age of the last checkpoint is 73591799,
InnoDB: which exceeds the log group capacity 9433498.
InnoDB: If you are using big BLOB or TEXT rows, you must set the
InnoDB: combined size of log files at least 10 times bigger than the
InnoDB: largest such row.
050315 17:31:03 InnoDB: ERROR: the age of the last checkpoint is 79831109,
InnoDB: which exceeds the log group capacity 9433498.
InnoDB: If you are using big BLOB or TEXT rows, you must set the
InnoDB: combined size of log files at least 10 times bigger than the
InnoDB: largest such row.
050315 17:31:19 InnoDB: ERROR: the age of the last checkpoint is 85510668,
InnoDB: which exceeds the log group capacity 9433498.
InnoDB: If you are using big BLOB or TEXT rows, you must set the
InnoDB: combined size of log files at least 10 times bigger than the
InnoDB: largest such row.
050315 17:31:37 InnoDB: ERROR: the age of the last checkpoint is 91581726,
InnoDB: which exceeds the log group capacity 9433498.
InnoDB: If you are using big BLOB or TEXT rows, you must set the
InnoDB: combined size of log files at least 10 times bigger than the
InnoDB: largest such row.
050316 16:15:35 InnoDB: Operating system error number 995 in a file operation.
InnoDB: See http://dev.mysql.com/doc/mysql/en/InnoDB.html
InnoDB: for installation help.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/mysql/en/Operating_System_error_codes.html
InnoDB: File name .\ibdata1
InnoDB: File operation call: 'Windows aio'.
InnoDB: Cannot continue operation.
050316 16:17:36 InnoDB: Database was not shut down normally.
InnoDB: Starting recovery from log files...
InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 2 734799023
InnoDB: Doing recovery: scanned up to log sequence number 2 734847239
050316 16:17:36 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
050316 16:17:37 InnoDB: Flushing modified pages from the buffer pool...
050316 16:17:37 InnoDB: Started
MySql: ready for connections.
Version: '4.0.22-nt' socket: '' port: 3100 Source distribution
-----------------------------------------------------------------------------------------------

Options: ReplyQuote


Subject
Views
Written By
Posted
5045
January 24, 2005 08:48AM
3917
January 24, 2005 01:13PM
3151
January 27, 2005 07:33AM
3468
lg
March 04, 2005 02:52AM
3178
March 05, 2005 01:57AM
Re: InnoDB error
13010
lg
March 16, 2005 09:48AM
6387
April 19, 2005 02:22PM
5496
April 25, 2005 07:21AM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.