Innodb Operating System Error Number 13
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about docker innodb operating system error number 13 in a file operation Stack Overflow the company Business Learn more about hiring developers or posting ads
Innodb Operating System Error Number 13 In A File Operation Ubuntu
with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow innodb: os_file_get_status() failed on './ibdata1'. can't determine file permissions is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up InnoDB: Operating system error number 13 in a file operation not fixed after
Can't Find File: './mysql/plugin.frm' (errno: 13)
changing permissions in /var/lib/mysql/ or disabling selinux up vote 2 down vote favorite When I run mysql, I get the error of ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2). mysqld gives the error of 150101 12:08:19 [Warning] Can't create test file /var/lib/mysql/lamp-update.lower-test 150101 12:08:19 [Warning] Can't create test file /var/lib/mysql/lamp-update.lower-test 150101 12:08:19 [Warning] One can only use the --user switch if running as root can't create test file /var/lib/mysql/ 150101 12:08:19 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead. 150101 12:08:19 [Note] Plugin 'FEDERATED' is disabled. mysqld: Can't find file: './mysql/plugin.frm' (errno: 13) 150101 12:08:19 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it. 150101 12:08:19 InnoDB: The InnoDB memory heap is disabled 150101 12:08:19 InnoDB: Mutexes and rw_locks use GCC atomic builtins 150101 12:08:19 InnoDB: Compressed tables use zlib 1.2.8 150101 12:08:19 InnoDB: Using Linux native AIO 150101 12:08:19 InnoDB: Initializing buffer pool, size = 128.0M 150101 12:08:19 InnoDB: Completed initialization of buffer pool 150101 12:08:19 InnoDB: Operating system error number 13 in a file operation. InnoDB: The error means mysqld does not have the access rights to InnoDB: the directory. InnoDB: File name ./ibdata1 InnoDB: File operation call: 'open'. InnoDB: Cannot continue operation. sudo mysqld gives the output of 150101 12:11:59 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead. I am running a virtual ubuntu linux server. Mysql has worked without a problem until yesterday, when I got this error. I have tried to set the permissions
starting MySQL server on a new machine that you've copied over the databases folder from another server? 140612 21:38:29 mysqld started 140612 21:38:29 InnoDB: Operating system error number
Docker Mysql Operating System Error Number 13 In A File Operation
13 in a file operation. InnoDB: The error means mysqld does not have
Innodb: Operating System Error Number 2 In A File Operation.
the access rights to InnoDB: the directory. InnoDB: File name ./ibdata1 InnoDB: File operation call: ‘open'. InnoDB: Cannot continue fatal error: can't open and lock privilege tables: table 'mysql.host' doesn't exist operation. 140612 21:38:29 mysqld ended Even though the permissions are correct as followed : MySQL data directory [/var/lib] Shell output Shell drwxr-xr-x 32 mysql mysql 4096 Jun 12 21:38 http://stackoverflow.com/questions/27733269/innodb-operating-system-error-number-13-in-a-file-operation-not-fixed-after-cha mysql 1 drwxr-xr-x 32 mysql mysql 4096 Jun 12 21:38 mysql MySQL databases folder /var/lib/mysql Shell output Shell -rw-rw---- 1 mysql mysql 85983232 Jun 12 20:12 ibdata1 -rw-rw---- 1 mysql mysql 5242880 Jun 12 20:12 ib_logfile0 -rw-rw---- 1 mysql mysql 5242880 Jun 12 20:10 ib_logfile1 drwx------ 2 mysql mysql 4096 Nov 30 2008 mysql 1234 -rw-rw---- 1 mysql mysql 85983232 Jun 12 http://www.itechlounge.net/2014/07/linux-mysql-innodb-operating-system-error-number-13-in-a-file-operation/ 20:12 ibdata1-rw-rw---- 1 mysql mysql 5242880 Jun 12 20:12 ib_logfile0-rw-rw---- 1 mysql mysql 5242880 Jun 12 20:10 ib_logfile1drwx------ 2 mysql mysql 4096 Nov 30 2008 mysql MySQL database [/var/lib/mysql/mysql] Shell output Shell [...] -rw-rw---- 1 mysql mysql 9494 Nov 30 2008 db.frm -rw-rw---- 1 mysql mysql 23652 Jan 10 2013 db.MYD -rw-rw---- 1 mysql mysql 4096 Jan 11 2013 db.MYI -rw-rw---- 1 mysql mysql 10330 Nov 30 2008 user.frm -rw-rw---- 1 mysql mysql 1972 May 3 13:11 user.MYD -rw-rw---- 1 mysql mysql 2048 May 5 00:00 user.MYI [...] 12345678 [...]-rw-rw---- 1 mysql mysql 9494 Nov 30 2008 db.frm-rw-rw---- 1 mysql mysql 23652 Jan 10 2013 db.MYD-rw-rw---- 1 mysql mysql 4096 Jan 11 2013 db.MYI-rw-rw---- 1 mysql mysql 10330 Nov 30 2008 user.frm-rw-rw---- 1 mysql mysql 1972 May 3 13:11 user.MYD-rw-rw---- 1 mysql mysql 2048 May 5 00:00 user.MYI[...] This issue is probably caused by SELinux. You may disable it… Edit SELinux configuration file : Configuration Shell /etc/selinux/config 1 /etc/selinux/config And set the following : Configuration Shell SELINUX=disabled 1 SELINUX=disabled Reboot your server and start MySQL daemon again : Command Shell service mysqld start 1 service mysqld start Be Sociable, Share! Tweet Ca
wolf Email Updates: Status: No Feedback Impact on me: None Category:MySQL Server: DDL Severity:S3 (Non-critical) Version:5.6 OS:Linux (CentOS, Fedora) Assigned to: Tags: data https://bugs.mysql.com/bug.php?id=70717 directory View Add Comment Files Developer Edit Submission View Progress Log Contributions [24 Oct 2013 1:22] wolf wolf Description: I had set the access right for this directory to http://serverfault.com/questions/473789/mysql-doesnt-start-after-relocating-data-dir 777 using the following command: chown -R 777 mysql:mysql /home/mysqldata And the right description is "drwxrwxrwx" for the directory /home/mysqldata after I use the linux command "ll". Now, I want operating system to locate my table data file to the directory /home/mysqldata, and the test script to create table is: create table tb1(id int, title varchar(100), primary key(id)) engine = innodb, data directory = '/home/mysqldata'; The mysql server returns: ERROR 1030 (HY000): Got error -1 from storage engine And the error log shows: InnoDB: Operating system error number 13 in a file operating system error operation. InnoDB: The error means mysqld does not have the access rights to InnoDB: the directory. InnoDB: File /home/mysqldata/test: 'mkdir' returned OS error 113. Why have no access right to the directory? I had set all the right for the directory to all users! How to repeat: hemowolf@hotmail.com [12 Nov 2013 19:10] Miguel Solorzano Check for SELinux Issue. Thanks. [13 Dec 2013 1:00] Bugs System No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open". Legal Policies Your Privacy Rights Terms of Use Contact Us Portions of this website are copyright © 2001, 2002 The PHP Group Page generated in 0.021 sec. using MySQL 5.7.12-enterprise-commercial-advanced-log 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. © 2016, Oracle Corporation and/or its affiliates
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top mysql doesn't start after relocating data dir up vote 3 down vote favorite 1 I have a web-server where the default installation of mysql places all its database files in /var/lib/mysql. The partition where /var is mounted has only 2GB of space, so after running in space problems, I decided to relocate mysql's data directory. My naive approach was to copy the /var/lib/mysql directory completely to /web/dbs/mysql, and change /etc/mysql/my.cnf so that it reads datadir = /web/dbs/mysql However, after restarting, I get the following errors in the mysql error log, and the server won't start up. 130130 9:59:23 [Note] Plugin 'FEDERATED' is disabled. /usr/sbin/mysqld: Can't find file: './mysql/plugin.frm' (errno: 13) 130130 9:59:23 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it. 130130 9:59:23 InnoDB: Initializing buffer pool, size = 8.0M 130130 9:59:23 InnoDB: Completed initialization of buffer pool 130130 9:59:23 InnoDB: Operating system error number 13 in a file operation. InnoDB: The error means mysqld does not have the access rights to InnoDB: the directory. InnoDB: File name ./ibdata1 InnoDB: File operation call: 'open'. InnoDB: Cannot continue operation. All files and directories belong to mysql:mysql. For testing, I even changed the access rights for /web/dbs/mysql are rwxrwxrw