📋

Description

This error indicates that MySQL attempted to access a file but could not locate it at the specified path. It typically occurs during operations like loading data, creating tables from external files, or accessing log files when the file has been moved, deleted, or its path is incorrect. The error provides the operating system's error number and description for more context.

💬

Error Message

File '%s' not found (OS errno %d - %s)

🔍

Known Causes

3 known causes

⚠️

File Missing or Moved

The required file, such as a data file, log file, or configuration file, does not exist at the expected location or has been relocated from its original path.

⚠️

Incorrect File Path

MySQL was instructed to look for the file using an incorrect, misspelled, or outdated path in a query, command, or configuration setting.

⚠️

Insufficient Permissions

The MySQL server process lacks the necessary read permissions for the directory containing the file or for the file itself.

🛠️

Solutions

3 solutions available

1. Verify File Path and Permissions easy

Ensure the specified file exists and MySQL has read permissions.

1

Identify the exact file path mentioned in the error message. This is represented by '%s' in the error message.

2

Manually navigate to the specified directory on the MySQL server's operating system.

3

Check if the file actually exists at that location. If not, you'll need to provide the correct path or ensure the file is created/copied there.

4

Verify that the MySQL server process user has read permissions for the file and execute permissions for all parent directories leading to the file. Use `ls -l` on Linux/macOS or check file properties on Windows.

ls -l /path/to/your/file

5

If permissions are insufficient, adjust them. For example, on Linux/macOS, you might use `chmod` or `chown`.

sudo chown mysql:mysql /path/to/your/file
sudo chmod 644 /path/to/your/file

2. Check MySQL Configuration for File Paths medium

Review MySQL configuration files for incorrect or missing file path settings.

1

Locate your MySQL configuration file. This is typically `my.cnf` on Linux/macOS or `my.ini` on Windows. Common locations include `/etc/mysql/my.cnf`, `/etc/my.cnf`, or the MySQL installation directory.

2

Open the configuration file in a text editor.

3

Look for configuration directives that specify file paths. Common directives include `datadir`, `log_error`, `pid-file`, `socket`, and paths related to plugins or UDFs.

[mysqld]
datadir=/var/lib/mysql
log_error=/var/log/mysql/error.log

4

Ensure these paths are correctly specified and that the files/directories referenced by these directives exist and have appropriate permissions for the MySQL server user.

5

If you made any changes, save the configuration file and restart the MySQL server for the changes to take effect.

sudo systemctl restart mysql

3. Investigate Specific Operations Triggering the Error medium

Determine which SQL statement or MySQL operation is causing the 'File Not Found' error.

1

Examine the MySQL error log (`log_error`) for more detailed information immediately preceding the 'File Not Found' error. This might indicate the specific SQL query or operation.

2

If the error occurs during a specific SQL query, review that query. For example, if it involves `LOAD DATA INFILE` or `SELECT ... INTO OUTFILE`, verify the path specified in the query.

LOAD DATA INFILE '/path/to/your/data.csv' INTO TABLE your_table;

3

If the error relates to a plugin or User-Defined Function (UDF), ensure the plugin/UDF library file is correctly installed and its path is properly configured in `my.cnf` or through `INSTALL PLUGIN`.

INSTALL PLUGIN your_plugin SONAME 'your_plugin.so';

4

If the error is related to the data directory, ensure the `datadir` setting in `my.cnf` is correct and the directory exists with proper ownership and permissions.

🔗

Related Errors

5 related errors

MySQL Error 29: File Not Found