MySQL return a "file not found error" when the file exists

[calsaverini]

Hi,

I'm having a problem with mysql.

When I try to load a file in a table like this:

LOAD DATA INFILE "/home/calsaverini/data.txt" INTO TABLE CMIG4;

It returns the error:

 ERROR 29 (HY000): File '/home/calsaverini/data.txt' not found (Errcode: 13)

But the file IS THERE!

Anyone have any clue what the problem could be?

[HalPomeranz]

Permissions problem perhaps? The file is going to be read in with the privs of the mysqld process, not your privs. Try this:

chmod o+rx /home/calsaverini
chmod o+r /home/calsaverini/data.txt

Then try to load your file as before.

[calsaverini]

Permissions are not the problem.

I've granted all permissions to the file and the same error still occurs.

[dwhitney67]

HalPomeranz recommended that you change the permissions on your user directory (that is /home/calsaverini). Did you change it?

The other thing you could try to do is place the file in /tmp to see if that makes a difference.

[4partee]

There is a workaround.

https://bugs.launchpad.net/ubuntu/+s....0/+bug/244406

I am trying to get this classified as a bug.

HTH;
John

[joculi]

I found that using LOAD DATA LOCAL INFILE worked for me. Without the LOCAL keyword it failed with the same error described above.

According to the MySQL doc, LOCAL causes the client to read the file and send it to the server. This seems to eliminate the question of whether the server can read the file.

[MattPhillips]

Hey joculi, thanks!! I had exactly calverini's problem and your solution worked.

[LaurentEdel]

That's the same thing for me.
However using LOCAL isn't a solution, it's just a bypass.

The problem can be resolved by configuring AppArmor, see this thread : http://stackoverflow.com/questions/2...t-into-outfile, or directly :

sudo vi /etc/apparmor.d/usr.sbin.mysqld

/usr/sbin/mysqld {
...
/var/log/mysql/ r,
/var/log/mysql/* rw,
/var/run/mysqld/mysqld.pid w,
/var/run/mysqld/mysqld.sock w,
/data/ r,
/data/* rw,
}

# sudo /etc/init.d/apparmor reload

[jdowdell]

I had a similar case, file was /tmp/test.infile, clearly existed /tmp has 777 permissions, file had 755 permissions. I did

sudo chown mysql:mysql /tmp/test.infile

And suddenly mysqld could see it.

(adding LOCAL didn't work in my case)

[BoynamedSue]

LaurentEdel - you are the man. Thank you to you. I can import from where ever now.

Toda raba