Num 1. MySQL5.7 prompt --secure-file-priv solution to export data:
problem analysis
In the official document of secure_file_priv it has been described, it is used to limit the export data.
- When secure_file_priv is NULL, indicating that mysqld is not allowed to import or export restrictions.
- When secure_file_priv to / tmp, express import and export restrictions mysqld can only be executed in the / tmp directory, other directories can not be executed.
- When secure_file_priv no value, not to limit the introduction of any mysqld Export directory.
In Mysql command input show variables like '% secure_file_priv%'; see the default secure_file_priv = NULL.
mysql> show global variables like '%secure_file_priv%';
+------------------+-------+
| Variable_name | Value |
+------------------+-------+
| secure_file_priv | NULL |
+------------------+-------+
Solution
1. Check the support-files folder (path / usr / local / mysql / support-files Mac which is hidden in folders, shift + command + g then enter the path at the Finder), whether there my.cnf configuration file, on a Mac seems to be the default file (specifically unknown), we need to manually configure Mysql does not exist.
2. (Mysql closed) needs to be configured in the / etc my.cnf, first cd / etc, and then manually configure, vim my.cnf, enter the following configuration information.
# Example MySQL config file for medium systems. # # This is for a system with little memory (32M - 64M) where MySQL plays # an important part, or systems up to 128M where MySQL is used together with # other programs (such as a web server) # # MySQL programs look for option files in a set of # locations which depend on the deployment platform. # You can copy this option file to one of those # locations. For information about these locations, see: # http://dev.mysql.com/doc/mysql/en/option-files.html # # In this file, you can use all long options that a program supports. # If you want to know which options a program supports, run the program # with the "--help" option. # The following options will be passed to all MySQL clients [client] default-character-set=utf8 #password = your_password port = 3306 socket = /tmp/mysql.sock # Here follows entries for some specific programs # The MySQL server [mysqld] character-set-server=utf8 init_connect='SET NAMES utf8 port = 3306 socket = /tmp/mysql.sock skip-external-locking key_buffer_size = 16M max_allowed_packet = 1M table_open_cache = 64 sort_buffer_size = 512K net_buffer_length = 8K read_buffer_size = 256K read_rnd_buffer_size = 512K myisam_sort_buffer_size = 8M character-set-server=utf8 init_connect='SET NAMES utf8' secure_file_priv= # Don't listen on a TCP/IP port at all. This can be a security enhancement, # if all processes that need to connect to mysqld run on the same host. # All interaction with mysqld must be made via Unix sockets or named pipes. # Note that using this option without enabling named pipes on Windows # (via the "enable-named-pipe" option) will render mysqld useless! # #skip-networking # Replication Master Server (default) # binary logging is required for replication log-bin=mysql-bin # binary logging format - mixed recommended binlog_format=mixed # required unique id between 1 and 2^32 - 1 # defaults to 1 if master-host is not set # but will not function as a master if omitted server-id = 1 # Replication Slave (comment out master section to use this) # # To configure this host as a replication slave, you can choose between # two methods : # # 1) Use the CHANGE MASTER TO command (fully described in our manual) - # the syntax is: # # CHANGE MASTER TO MASTER_HOST=<host>, MASTER_PORT=<port>, # MASTER_USER=<user>, MASTER_PASSWORD=<password> ; # # where you replace <host>, <user>, <password> by quoted strings and # <port> by the master's port number (3306 by default). # # Example: # # CHANGE MASTER TO MASTER_HOST='125.564.12.1', MASTER_PORT=3306, # MASTER_USER='joe', MASTER_PASSWORD='secret'; # # OR # # 2) Set the variables below. However, in case you choose this method, then # start replication for the first time (even unsuccessfully, for example # if you mistyped the password in master-password and the slave fails to # connect), the slave will create a master.info file, and any later # change in this file to the variables' values below will be ignored and # overridden by the content of the master.info file, unless you shutdown # the slave server, delete master.info and restart the slaver server. # For that reason, you may want to leave the lines below untouched # (commented) and instead use CHANGE MASTER TO (see above) # # required unique id between 2 and 2^32 - 1 # (and different from the master) # defaults to 2 if master-host is set # but will not function as a slave if omitted #server-id = 2 # # The replication master for this slave - required #master-host = <hostname> # # The username the slave will use for authentication when connecting # to the master - required #master-user = <username> # # The password the slave will authenticate with when connecting to # the master - required #master-password = <password> # # The port the master is listening on. # optional - defaults to 3306 #master-port = <port> # # binary logging - not required for slaves, but recommended #log-bin=mysql-bin # Uncomment the following if you are using InnoDB tables #innodb_data_home_dir = /usr/local/mysql/data #innodb_data_file_path = ibdata1:10M:autoextend #innodb_log_group_home_dir = /usr/local/mysql/data # You can set .._buffer_pool_size up to 50 - 80 % # of RAM but beware of setting memory usage too high #innodb_buffer_pool_size = 16M #innodb_additional_mem_pool_size = 2M # Set .._log_file_size to 25 % of buffer pool size #innodb_log_file_size = 5M #innodb_log_buffer_size = 8M #innodb_flush_log_at_trx_commit = 1 #innodb_lock_wait_timeout = 50 [mysqldump] quick max_allowed_packet = 16M [mysql] no-auto-rehash # Remove the next comment character if you are not familiar with SQL #safe-updates default-character-set=utf8 [myisamchk] key_buffer_size = 20M sort_buffer_size = 20M read_buffer = 2M write_buffer = 2M [mysqlhotcopy] interactive-timeout
3. sudo chmod 644 my.cnf, the read and write permissions to perform the configuration file changed 644. (644 permissions are reset after each modification to the configuration file is recommended)
4. Open Mysql, input show variables like '% secure_file_priv%'; see secure_file_priv = empty.
mysql> show variables like '%secure_file_priv%';
+------------------+-------+
| Variable_name | Value |
+------------------+-------+
| secure_file_priv | |
+------------------+-------+
1 row in set (0.00 sec)
. Num2 MySQL data import "Error code:. 13 Can not get stat of '' (Permission denied)" Solution:
Solution:
After solving "secure-file-priv" problem, again ran into an error when importing data. To find a solution after google.
The load data infile changed to load data local infile. Error can be solved (the specific reasons unknown)
. Num3 MySQL Export data "Can not create / write to file 'Users / ***' (Errcode: 13)" Solution:
problem analysis:
This should be a question about MySQL temporary files directory, as do a lot of attempts to solve this problem, configure temporary files directory in my.cnf, and give the file 777, and so did not solve the problem.
Solution:
Last but not least find a solution on google. As shown below
This is due to a permissions problem, because trying to get mysql users to write data to a private home directory. We can create a folder in the usr / local, to save the exported data from mysql.
2019-06-30 18:03:14