Re: mysql crash - innodb not starting

[Heikki Tuuri]

Mel,

do

ps -fA

Do you see more mysqld processes?

If the ibdata1 file stays locked even though there is no mysqld process, 
then this is a bug in Linux.

If you do not use InnoDB, you can delete ibdata1 and ib_logfiles.

Best regards,

Heikki
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

Order MySQL Network from http://www.mysql.com/network/

----- Alkuperäinen viesti ----- 
Lähettäjä: "mel list_php" <list_php@stripped>
Vastaanottaja: <mysql@stripped>
Kopio: <Heikki.Tuuri@stripped>
Lähetetty: Friday, March 04, 2005 12:00 PM
Aihe: Re: mysql crash - innodb not starting


>I did ps -aux
> I see one mysqld running (mine, launched with --skip-innodb).
> I shut it down.
> ps -aux: nothing
> I tried to start it again, doesn't work.
>
> As it is running on a machine managed by the system service I went to see 
> them after shutting it down again, they have no mysql process running. 
> (still using ps-aux, but as root on that machine)
>
> From that I think it means I don't have any mysql running  there, and I 
> still get that error 11.
>
> Or is there an other to see if a file is already used by a mysql process?
>
> Do you think replacing the ibdata1 file by an empty file is possible?
> Or doing a new install , copying my isam tables from the data directory 
> and not touching the innodb files?
> Doing a new install and setting up my tables (isam) with a backup dump is 
> better?
>
> I would prefer to repair the existing installation, but have no idea where 
> to begin....
>
> Thanks a lot for your time.
>
>
>
>>From: "Heikki Tuuri" <Heikki.Tuuri@stripped>
>>To: <mysql@stripped>
>>Subject: Re: mysql crash - innodb not starting
>>Date: Thu, 3 Mar 2005 23:20:56 +0200
>>
>>Hi!
>>
>>Error 11 means that you already have a mysqld process running on the same 
>>files.
>>
>>Best regards,
>>
>>Heikki Tuuri
>>Innobase Oy
>>Foreign keys, transactions, and row level locking for MySQL
>>InnoDB Hot Backup - a hot backup tool for InnoDB which also backs up 
>>MyISAM tables
>>http://www.innodb.com/order.php
>>
>>------------------------------------------
>>Save the Pacific Northwest Tree Octopus! |
>>http://zapatopi.net/treeoctopus.html     |
>>------------------------------------------
>>
>>----- Original Message ----- From: ""mel list_php"" 
>><list_php@stripped>
>>Newsgroups: mailing.database.myodbc
>>Sent: Thursday, March 03, 2005 2:25 PM
>>Subject: mysql crash - innodb not starting
>>
>>
>>>Hi,
>>>I just have a crash of my mysql 4.1.5 .(the machine where it was running
>>>just shutdown)
>>>
>>>Tried to restart it, and problem with innodb:
>>>050303 11:58:46  [WARNING] Asked for 196608 thread stack, but got 126976
>>>InnoDB: Unable to lock ./ibdata1, error: 11InnoDB: Error in opening
>>>./ibdata1
>>>050303 11:58:46  InnoDB: Operating system error number 11 in a file
>>>operation.
>>>InnoDB: Error number 11 means 'Resource temporarily unavailable'.
>>>InnoDB: See also section 13.2 at http://www.innodb.com/ibman.php
>>>InnoDB: about operating system error numbers.
>>>InnoDB: Could not open or create data files.
>>>InnoDB: If you tried to add new data files, and it failed here,
>>>InnoDB: you should now edit innodb_data_file_path in my.cnf back
>>>InnoDB: to what it was, and remove the new ibdata files InnoDB created
>>>InnoDB: in this failed attempt. InnoDB only wrote those files full of
>>>InnoDB: zeros, but did not yet use them in any way. But be careful: do 
>>>not
>>>InnoDB: remove old data files which contain your precious data!
>>>050303 11:58:46  [ERROR] Can't init databases
>>>050303 11:58:46  [ERROR] Aborting
>>>
>>>050303 11:58:46  [NOTE] ./bin/mysqld: Shutdown complete
>>>
>>>
>>>I'm sure I already saw that kind of problem, tried to go through the list
>>>but didn't find the thread again. In addition I'm not very familiar with
>>>that kind of thing.
>>>I don't use innodb at all, only myisam, so I was able to restart with
>>>--skip-innodb.
>>>
>>>About the error code "ressource unavailable" I tried later on no 
>>>difference,
>>>the file ibdata1 is there with adequate permissions, I don't think that I
>>>have a my.cnf...
>>>
>>>To sum up I have no idea what to do, and I'm not a system guru!
>>>My first ideas:
>>>- removing the ibdata1 file and recreating an empty one
>>>- I saw a force-recovery option but have no idea how it works
>>>
>>>Hope somebody here can help me....
>>>Thanks a lot
>>>
>>>_________________________________________________________________
>>>It's fast, it's easy and it's free. Get MSN Messenger today!
>>>http://www.msn.co.uk/messenger
>>>
>>>
>>>--
>>>MySQL General Mailing List
>>>For list archives: http://lists.mysql.com/mysql
>>>To unsubscribe: 
>>>http://lists.mysql.com/mysql?unsub=1
>>>
>>
>>
>>--
>>MySQL General Mailing List
>>For list archives: http://lists.mysql.com/mysql
>>To unsubscribe: 
>>http://lists.mysql.com/mysql?unsub=1
>>
>
> _________________________________________________________________
> Want to block unwanted pop-ups? Download the free MSN Toolbar now! 
> http://toolbar.msn.co.uk/
>