Marten,
I replied today to your earlier email with the message pasted below.
Regards,
Heikki
........
Marten,
can you email the complete .err log from the server to
[EMAIL PROTECTED]
I am interested in what caused the very first crash in the server. Now your
database seems to be seriously corrupt, since the log sequence number in the
log files is only 14 MB, while it is >= 153 MB in a data file!
Did you move around or delete ib_logfiles or ibdata files or .ibd files, or
edit my.cnf while mysqld was running?
Are you using some exotic file system?
The output looks like ib_logfiles and data files from different servers
would be mixed.
Best regards,
Heikki
Oracle Corp./Innobase Oy
InnoDB - transactions, row level locking, and foreign keys for MySQL
InnoDB Hot Backup - a hot backup tool for InnoDB which also backs up MyISAM
tables
http://www.innodb.com/order.php
----- Original Message -----
From: "Marten Lehmann" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Tuesday, March 28, 2006 7:49 PM
Subject: innodb errors on startup
Hello,
I'm getting this in my errorlog:
060328 18:43:45 mysqld ended
060328 18:43:46 mysqld started
060328 18:43:46 InnoDB: Operating system error number 2 in a file
operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
060328 18:43:46 InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file './db16041/intradv_cms_websites.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a table created with
InnoDB: CREATE TEMPORARY TABLE, and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB:
http://dev.mysql.com/doc/mysql/en/InnoDB_troubleshooting_datadict.html
InnoDB: how to resolve the issue.
060328 18:43:46 InnoDB: Operating system error number 2 in a file
operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
060328 18:43:46 InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file
'./db16041/intradv_cms_wsepgmerchant.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a table created with
InnoDB: CREATE TEMPORARY TABLE, and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB:
http://dev.mysql.com/doc/mysql/en/InnoDB_troubleshooting_datadict.html
InnoDB: how to resolve the issue.
060328 18:43:46 InnoDB: Started; log sequence number 0 18831221
/vrmd/mysql/mysql-4.1.18/libexec/mysqld: ready for connections.
Version: '4.1.18-log' socket: '/tmp/mysql.sock' port: 3306 Source
distribution
How do I get rid of these messages / the errors? The page for
troubleshooting didn't help.
Regards
Marten
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:
http://lists.mysql.com/[EMAIL PROTECTED]
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
