try to change bin log directory: mysql-bin.index not found (Errcode: 13)

Question

MySQL 5.1.54 Ubuntu 11.04

I'am try to change bin log directory in my.conf as:

[mysqld]
log_bin=/home/developer/logs/mysql/mysql-bin.log

After this changes MySQL server can't start with error:

/usr/sbin/mysqld: File '/home/developer/logs/mysql/mysql-bin.index' 
not found (Errcode: 13)
111005 12:47:58 [ERROR] Aborting

Permission for directory /home/developer/logs/mysql/ is 0777

What's going on?

score 38 · Accepted Answer · answered Oct 06 '11 at 06:43

38

As usual, the solution was simple but not obvious: it needed to edit apparmor settings I just added to /etc/apparmor.d/usr.sbin.mysqld a new string with path to target directory: /home/developer/logs/* rw

It works!

answered Oct 06 '11 at 06:43

solo117

1,069
2
11
12

5

apparmor.d is not available in my server. – dharanbro Apr 11 '15 at 06:52
Note, for anyone getting to this. If you want the apparmor path to include all subfolders in the path as well, use two stars \*\*, for example(without quotes): "**/home/developer/logs/\*\* rw,**" – Nick Zinger Jul 29 '18 at 15:45
1

also don't forget a `service apparmor restart` afterwards – the_nuts May 17 '20 at 10:45
1

Ubuntu 20.04 MySQL 8 should append "/home/developer/logs/** rwk,"，grant permission to lock a file. – zhangke May 02 '22 at 14:59

score 27 · Answer 2 · edited Jun 02 '13 at 19:24

27

/usr/sbin/mysqld: File '/usr/binlogs/mysql-bin.index' not found (Errcode: 13)

It worked for me with:

chown -R mysql:mysql /usr/binlogs/

edited Jun 02 '13 at 19:24

Mzf

5,210
2
24
37

answered Jun 02 '13 at 19:02

Pradeep Jadhav

279
3
2

1

This is the most obvious solution after an accidental deletion of the mysql bin logs. Perfect ! – Maxx Jan 05 '14 at 11:04
@Maxx what would be its windows equivalent – mr.loop Apr 29 '21 at 00:02

score 14 · Answer 3 · edited Sep 18 '15 at 09:55

14

Just as an FYI for anyone who runs into a similar problem, the solution is basically the same, but the cause of the problem isn't obvious.

After upgrading Debian wheezy, mysql failed to start.

Somehow, I have no idea how, permissions on some of the files in /var/lib/mysql were not owned by the mysql user, thus preventing the server from firing up.

A chown -R mysql.mysql /var/lib/mysql fixed it.

I didn't do anything to mess up mysql, it was a standard:

apt-get update

apt-get upgrade

Something got hinky during the Debian upgrade and manual intervention was needed.

edited Sep 18 '15 at 09:55

atw

5,428
10
39
63

answered Feb 17 '14 at 03:45

Halfstop

1,710
17
34

Thank you @Halfstop, you saved my day. works perfect – shrawan_lakhe Dec 30 '21 at 00:10

score 3 · Answer 4 · answered Jan 04 '13 at 06:38

3

Selinux might enforce the rule that MySQL database files have to live in /var/lib/mysql and not anywhere else. Try turning off selinux (selinux=0 on kernel boot command line) if you moved mysql to another directory.

answered Jan 04 '13 at 06:38

Jim Ockers

31
1

score 3 · Answer 5 · edited Sep 18 '15 at 16:53

Option 1:

service mysqld stop

Copy the log files including the .index file to new location.

 cp mysql-bin.log* /path/to/binlogs
 cp mysql-bin.index /path/to/binlogs

Do Changes in the /etc/my.cnf file.

[mysqld]
log-bin=/path/to/newdirecory/mysql-bin

log-bin-index=/path/to/newdirectory/mysql-bin.index

service mysqld start

Option 2:

Use this utiltiy to relocate binary logs:

mysqlbinlogmove --binlog-dir=/server/data /new/binlog_dir

score 2 · Answer 6 · answered May 12 '16 at 07:00

2

You need to give user permissions to the directory as follows:

chown -R mysql:mysql /home/developer/logs/mysql/

answered May 12 '16 at 07:00

Sujit Devkar

1,195
3
12
22

score 1 · Answer 7 · answered Sep 24 '18 at 13:50

mysqld: File '/data/log/mysql/mysql-bin.index' not found (Errcode: 2 - No such file or directory)

I was really stuck in the middle of my MySQL Master - Slave setup. Finally the above was a permission issue, adding the below command solved my issue.

chown -R mysql:mysql /data/log/mysql/

score 1 · Answer 8 · answered Oct 05 '11 at 11:22

1

Does your user have access to all upper directories? In special, the /home/developer/ directory? Try to log in with the mysql server account and touch the log file.

answered Oct 05 '11 at 11:22

Andreas

2,211
1
18
36

i have copied permissions from /var/log/mysql directory. No results. – solo117 Oct 05 '11 at 12:26
and what happens if you su to the mysqld user and try to access the directory? – Andreas Oct 05 '11 at 12:28
i run "sudo -u mysql touch /home/developer/logs/test.txt", it succesfully created a file – solo117 Oct 05 '11 at 12:33
2

I believe in this case the error message and the error code are misleading ... When I hit this, I've even tried to create a new index file with the list of binary logs ..., this didn't work either. – Dimitre Radoulov Oct 05 '11 at 13:27

score 0 · Answer 9 · answered Jun 25 '16 at 03:23

0

Your config is wrong:

log_bin=/home/developer/logs/mysql/mysql-bin.log

You would use instead

log-bin=/home/developer/logs/mysql/mysql-bin.log

answered Jun 25 '16 at 03:23

user2648582

51
1

score 0 · Answer 10 · answered Jul 16 '16 at 13:07

During replication configuration in "my.cnf" file needs to mention

server-id=1 log_bin=/var/log/mysql/mysql-bin.log

you can make your own directory and give permission. create directory "mysql" in /var/log/

chmod 777 mysql

this is applicable with MySQL version 5.7

score 0 · Answer 11 · answered Nov 30 '16 at 07:05

You can also comment the line in my.cnf file which is defining the log location, so mysql will consider its default path and will start properly.

log-bin = /var/log/mysql/mysql-bin.log -> #log-bin = /var/log/mysql/mysql-bin.log.

This will be helpful if you are not concerned much about logs.

score 0 · Answer 12 · answered Apr 11 '19 at 15:00

0

As documentation in mysql say https://dev.mysql.com/doc/refman/5.7/en/replication-options-binary-log.html#sysvar_log_bin

The variable is log_bin and not log-bin at least in version 5.7

answered Apr 11 '19 at 15:00

Manteca

1

1

the original question shows the user is using MySQL version 5.1.54, so this would not apply – Derek Pollard Apr 11 '19 at 15:08

Dimitre Radoulov · Answer 13 · 2011-10-05T12:18:51.390

0

I had a similar problem when I was trying to change the datadir variable during a fresh install. The solution in my case was to run the first time start up with log-bin disabled. After that I was able to enable it again using the new path ...

edited Oct 05 '11 at 12:18

answered Oct 05 '11 at 11:40

Dimitre Radoulov

27,252
4
40
48

What do you mean? stop server -> disable log_bin ->start server ->...stop server->enable log_bin -> start server_ ??? unfortunately it's not worked for me – solo117 Oct 05 '11 at 12:46
Not exactly. Do you also change the datadir position? If yes, this is what I did in order to make it work: disable log-bin in the configuration file, mysql_install_db with the customized configuration file, at the end of the installation mysqld is started by the install script. After that: stop, enable log-bin, start. – Dimitre Radoulov Oct 05 '11 at 13:01
It should be noted that this was during a new setup. If you have an existing database, your situation is different. – Dimitre Radoulov Oct 05 '11 at 13:07

try to change bin log directory: mysql-bin.index not found (Errcode: 13)

13 Answers13

Linked