InnoDB: Operating system error number 13 in a file operation

--Apple-Mail-2--68472726
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
charset=US-ASCII;
format=flowed

Can not make mysql connection -

error log:
030708 08:53:48 mysqld started
030708 8:53:49 InnoDB: Operating system error number 13 in a file
operation.
InnoDB: See http://www.innodb.com/ibman.html for installation help.
InnoDB: The error means mysqld does not have the access rights to
InnoDB: the directory.
InnoDB: File name ./ibdata1



The http://www.innodb.com/ibman.html stated:

If something goes wrong in an InnoDB database creation,
you should delete all files created by InnoDB.
This means all data files, all log files, the small archived log file,
and in the case you already did create some InnoDB tables,
delete also the corresponding .frm files for these tables from the
MySQL database directories.
Then you can try the InnoDB database creation again. It is best to
start the MySQL server from a command prompt so that you see what is
happening.


Question:
Should I delete these files? and if so, how do you delete files from
the command line?


Please help,

Mark D
--Apple-Mail-2--68472726--

Re: InnoDB: Operating system error number 13 in a file operation

Mark Depenbrock wrote:
>
> Can not make mysql connection -
>
> error log:
> 030708 08:53:48 mysqld started
> 030708 8:53:49 InnoDB: Operating system error number 13 in a file
> operation.
> InnoDB: See http://www.innodb.com/ibman.html for installation help.
> InnoDB: The error means mysqld does not have the access rights to
> InnoDB: the directory.
> InnoDB: File name ./ibdata1
>
>
>
> The http://www.innodb.com/ibman.html stated:
>
> If something goes wrong in an InnoDB database creation,
> you should delete all files created by InnoDB.
> This means all data files, all log files, the small archived log file,
> and in the case you already did create some InnoDB tables,
> delete also the corresponding .frm files for these tables from the
> MySQL database directories.
> Then you can try the InnoDB database creation again. It is best to
> start the MySQL server from a command prompt so that you see what is
> happening.
>
>
> Question:
> Should I delete these files? and if so, how do you delete files from
> the command line?

No, you should set up permissions on the directory and file. Error 13 means "Permission denied".



--
For technical support contracts, goto https://order.mysql.com/?ref=ensita
This email is sponsored by Ensita.net http://www.ensita.net/
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Egor Egorov
/ /|_/ / // /\ \/ /_/ / /__ Egor.Egorov@ensita.net
/_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.net
<___/ www.mysql.com




--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=gcdmg-mysql@m.gmane.org

Re: InnoDB: Operating system error number 13 in a file operation

Hello Egor,

You give me hope but...
I attempted to set up permissions but it appears that I need to start
up MySQL in order to do that.
That brings me right back to my original problem of not being able to
connect.

I am thinking of reinstalling MySQL to see if I missed something in the
original install.

Any more suggestions please, I am at a loss.

Mark D.


On Wednesday, July 9, 2003, at 09:26 AM, Egor Egorov wrote:

> Mark Depenbrock wrote:
>>
>> Can not make mysql connection -
>>
>> error log:
>> 030708 08:53:48 mysqld started
>> 030708 8:53:49 InnoDB: Operating system error number 13 in a file
>> operation.
>> InnoDB: See http://www.innodb.com/ibman.html for installation help.
>> InnoDB: The error means mysqld does not have the access rights to
>> InnoDB: the directory.
>> InnoDB: File name ./ibdata1
>>
>>
>>
>> The http://www.innodb.com/ibman.html stated:
>>
>> If something goes wrong in an InnoDB database creation,
>> you should delete all files created by InnoDB.
>> This means all data files, all log files, the small archived log file,
>> and in the case you already did create some InnoDB tables,
>> delete also the corresponding .frm files for these tables from the
>> MySQL database directories.
>> Then you can try the InnoDB database creation again. It is best to
>> start the MySQL server from a command prompt so that you see what is
>> happening.
>>
>>
>> Question:
>> Should I delete these files? and if so, how do you delete files from
>> the command line?
>
> No, you should set up permissions on the directory and file. Error 13
> means "Permission denied".
>
>
>
> --
> For technical support contracts, goto
> https://order.mysql.com/?ref=ensita
> This email is sponsored by Ensita.net http://www.ensita.net/
> __ ___ ___ ____ __
> / |/ /_ __/ __/ __ \/ / Egor Egorov
> / /|_/ / // /\ \/ /_/ / /__ Egor.Egorov@ensita.net
> /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.net
> <___/ www.mysql.com
>
>
>
>
> --
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe:
> http://lists.mysql.com/mysql?unsub=mark@adventdesigns.com
>


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=gcdmg-mysql@m.gmane.org

RE: InnoDB: Operating system error number 13 in a file operation

If you got the error message during creation of the innoDB files (e.g.
during install) you HAVE TO DELETE all files and restart the
installation. There is no way around this!

However, if the file got corrupted after installation (e.g. you already
used it for days) you can repair it (maybe someone changed the file
permissions and/or ownership). You can change filepermissions on unix
(linux) with chmod (type 'man chmod') on the command line, and change
ownership with chown (man chown). You can delete files with 'rm' or
'unlink' (again, see the man pages for help)

Cheers
/rudy

-----Original Message-----
From: Mark Depenbrock [mailto:mark@adventdesigns.com]=20
Sent: woensdag 9 juli 2003 16:35
To: Egor Egorov
Cc: mysql@lists.mysql.com
Subject: Re: InnoDB: Operating system error number 13 in a file
operation

Hello Egor,

You give me hope but...
I attempted to set up permissions but it appears that I need to start=20
up MySQL in order to do that.
That brings me right back to my original problem of not being able to=20
connect.

I am thinking of reinstalling MySQL to see if I missed something in the=20
original install.

Any more suggestions please, I am at a loss.

Mark D.


On Wednesday, July 9, 2003, at 09:26 AM, Egor Egorov wrote:

> Mark Depenbrock wrote:
>>
>> Can not make mysql connection -
>>
>> error log:
>> 030708 08:53:48 mysqld started
>> 030708 8:53:49 InnoDB: Operating system error number 13 in a file
>> operation.
>> InnoDB: See http://www.innodb.com/ibman.html for installation help.
>> InnoDB: The error means mysqld does not have the access rights to
>> InnoDB: the directory.
>> InnoDB: File name ./ibdata1
>>
>>
>>
>> The http://www.innodb.com/ibman.html stated:
>>
>> If something goes wrong in an InnoDB database creation,
>> you should delete all files created by InnoDB.
>> This means all data files, all log files, the small archived log
file,
>> and in the case you already did create some InnoDB tables,
>> delete also the corresponding .frm files for these tables from the
>> MySQL database directories.
>> Then you can try the InnoDB database creation again. It is best to
>> start the MySQL server from a command prompt so that you see what is
>> happening.
>>
>>
>> Question:
>> Should I delete these files? and if so, how do you delete files from
>> the command line?
>
> No, you should set up permissions on the directory and file. Error 13=20
> means "Permission denied".
>
>
>
> --=20
> For technical support contracts, goto=20
> https://order.mysql.com/?ref=3Densita
> This email is sponsored by Ensita.net http://www.ensita.net/
> __ ___ ___ ____ __
> / |/ /_ __/ __/ __ \/ / Egor Egorov
> / /|_/ / // /\ \/ /_/ / /__ Egor.Egorov@ensita.net
> /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.net
> <___/ www.mysql.com
>
>
>
>
> --=20
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe: =20
> http://lists.mysql.com/mysql?unsub=3Dmark@adventdesigns.com
>


--=20
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:
http://lists.mysql.com/mysql?unsub=3Drudy.metzger@pareto.nl


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=3Dgcdmg-mysql@m.gmane.org

Re: InnoDB: Operating system error number 13 in a file operation

Rudy, Egor, Victoria,

Thank you for keeping an eye on me. I ended up doing a reinstall of
MySQL and have successfully connected.
I feel I have broken through a wall only to find an infinite number of
walls yet to break through.
Such is the adventure I have chosen.

Be at peace,

Mark Depenbrock

On Wednesday, July 9, 2003, at 11:13 AM, Rudy Metzger wrote:

> If you got the error message during creation of the innoDB files (e.g.
> during install) you HAVE TO DELETE all files and restart the
> installation. There is no way around this!
>
> However, if the file got corrupted after installation (e.g. you already
> used it for days) you can repair it (maybe someone changed the file
> permissions and/or ownership). You can change filepermissions on unix
> (linux) with chmod (type 'man chmod') on the command line, and change
> ownership with chown (man chown). You can delete files with 'rm' or
> 'unlink' (again, see the man pages for help)
>
> Cheers
> /rudy
>
> -----Original Message-----
> From: Mark Depenbrock [mailto:mark@adventdesigns.com]
> Sent: woensdag 9 juli 2003 16:35
> To: Egor Egorov
> Cc: mysql@lists.mysql.com
> Subject: Re: InnoDB: Operating system error number 13 in a file
> operation
>
> Hello Egor,
>
> You give me hope but...
> I attempted to set up permissions but it appears that I need to start
> up MySQL in order to do that.
> That brings me right back to my original problem of not being able to
> connect.
>
> I am thinking of reinstalling MySQL to see if I missed something in the
> original install.
>
> Any more suggestions please, I am at a loss.
>
> Mark D.
>
>
> On Wednesday, July 9, 2003, at 09:26 AM, Egor Egorov wrote:
>
>> Mark Depenbrock wrote:
>>>
>>> Can not make mysql connection -
>>>
>>> error log:
>>> 030708 08:53:48 mysqld started
>>> 030708 8:53:49 InnoDB: Operating system error number 13 in a file
>>> operation.
>>> InnoDB: See http://www.innodb.com/ibman.html for installation help.
>>> InnoDB: The error means mysqld does not have the access rights to
>>> InnoDB: the directory.
>>> InnoDB: File name ./ibdata1
>>>
>>>
>>>
>>> The http://www.innodb.com/ibman.html stated:
>>>
>>> If something goes wrong in an InnoDB database creation,
>>> you should delete all files created by InnoDB.
>>> This means all data files, all log files, the small archived log
> file,
>>> and in the case you already did create some InnoDB tables,
>>> delete also the corresponding .frm files for these tables from the
>>> MySQL database directories.
>>> Then you can try the InnoDB database creation again. It is best to
>>> start the MySQL server from a command prompt so that you see what is
>>> happening.
>>>
>>>
>>> Question:
>>> Should I delete these files? and if so, how do you delete files from
>>> the command line?
>>
>> No, you should set up permissions on the directory and file. Error 13
>> means "Permission denied".
>>
>>
>>
>> --
>> For technical support contracts, goto
>> https://order.mysql.com/?ref=ensita
>> This email is sponsored by Ensita.net http://www.ensita.net/
>> __ ___ ___ ____ __
>> / |/ /_ __/ __/ __ \/ / Egor Egorov
>> / /|_/ / // /\ \/ /_/ / /__ Egor.Egorov@ensita.net
>> /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.net
>> <___/ www.mysql.com
>>
>>
>>
>>
>> --
>> MySQL General Mailing List
>> For list archives: http://lists.mysql.com/mysql
>> To unsubscribe:
>> http://lists.mysql.com/mysql?unsub=mark@adventdesigns.com
>>
>
>
> --
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe:
> http://lists.mysql.com/mysql?unsub=rudy.metzger@pareto.nl
>
>


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=gcdmg-mysql@m.gmane.org