我正在嘗試轉儲所有資料庫，但它給了我錯誤“轉儲表時查詢期間失去與 MySQL 伺服器的連線”並且文件始終達到781M。
我嘗試設定最大允許資料包 = 512M以下[mysqld]及以下[mysql轉儲]在/etc/mysql/my.cnf，但沒有成功。我也嘗試設定為1024M。沒有什麼。
我認為發生這種情況是因為 Apache 幾乎使用了我所有的 RAM，但我不太確定，因為當檔案大小為 781M 時，我的轉儲總是停止。
/etc/mysql/my.cnf：
#
# The MySQL database server configuration file.
#
# You can copy this to one of:
# - "/etc/mysql/my.cnf" to set global options,
# - "~/.my.cnf" to set user-specific options.
#
# One can use all long options that the program supports.
# Run program with --help to get a list of available options and with
# --print-defaults to see which it would actually understand and use.
#
# For explanations see
# http://dev.mysql.com/doc/mysql/en/server-system-variables.html
# This will be passed to all mysql clients
# It has been reported that passwords should be enclosed with ticks/quotes
# escpecially if they contain "#" chars...
# Remember to edit /etc/mysql/debian.cnf when changing the socket location.
[client]
port = 3306
socket = /var/run/mysqld/mysqld.sock
# Here is entries for some specific programs
# The following values assume you have at least 32M ram
# This was formally known as [safe_mysqld]. Both versions are currently parsed.
[mysqld_safe]
socket = /var/run/mysqld/mysqld.sock
nice = 0
log_error=/var/log/mysql/mysql_error.log
[mysqld]
#
# * Basic Settings
#
user = mysql
pid-file = /var/run/mysqld/mysqld.pid
socket = /var/run/mysqld/mysqld.sock
port = 3306
basedir = /usr
datadir = /var/lib/mysql
tmpdir = /tmp
language = /usr/share/mysql/english
skip-external-locking
log_error=/var/log/mysql/mysql_error.log
max_allowed_packet = 512M
# Replic
server-id=2
master-host=hostip
master-user=slaveusr
master-password=slavepass
master-port=3306
#
# Instead of skip-networking the default is now to listen only on
# localhost which is more compatible and is not less secure.
bind-address = 0.0.0.0
#
# * Fine Tuning
#
key_buffer = 16M
thread_stack = 192K
thread_cache_size = 8
# This replaces the startup script and checks MyISAM tables if needed
# the first time they are touched
myisam-recover = BACKUP
#max_connections = 100
#table_cache = 64
#thread_concurrency = 10
#
# * Query Cache Configuration
#
query_cache_limit = 1M
query_cache_size = 16M
#
# * Logging and Replication
#
# Both location gets rotated by the cronjob.
# Be aware that this log type is a performance killer.
# As of 5.1 you can enable the log at runtime!
#general_log_file = /var/log/mysql/mysql.log
#general_log = 1
#
# Error logging goes to syslog due to
/etc/mysql/conf.d/mysqld_safe_syslog.cnf.
#
# Here you can see queries with especially long duration
#log_slow_queries = /var/log/mysql/mysql-slow.log
#long_query_time = 2
#log-queries-not-using-indexes
#
# The following can be used as easy to replay backup logs or for replication.
# note: if you are setting up a replication slave, see README.Debian about
# other settings you may need to change.
#server-id = 1
#log_bin = /var/log/mysql/mysql-bin.log
expire_logs_days = 10
max_binlog_size = 100M
#binlog_do_db = include_database_name
#binlog_ignore_db = include_database_name
#
# * InnoDB
#
# InnoDB is enabled by default with a 10MB datafile in /var/lib/mysql/.
# Read the manual for more InnoDB related options. There are many!
#
# * Security Features
#
# Read the manual, too, if you want chroot!
# chroot = /var/lib/mysql/
#
# For generating SSL certificates I recommend the OpenSSL GUI "tinyca".
#
# ssl-ca=/etc/mysql/cacert.pem
# ssl-cert=/etc/mysql/server-cert.pem
# ssl-key=/etc/mysql/server-key.pem
[mysqldump]
quick
quote-names
max_allowed_packet = 512M
[mysql]
#no-auto-rehash # faster start of mysql but no tab completition
[isamchk]
key_buffer = 16M
#
# * IMPORTANT: Additional settings that can override those from this file!
# The files must end with '.cnf', otherwise they'll be ignored.
#
!includedir /etc/mysql/conf.d/
我試過mysqlcheck -A --自動修復也是，但過了一會兒我就得到了直流電（比運行時更多）mysql轉儲）。
有任何想法嗎？
編輯：
當嘗試轉儲某個表“bandeira”時，它會失去連接：
2073 Query SET SESSION character_set_results = 'binary'
2073 Query use `ct1222`
2073 Query select @@collation_database
2073 Query SHOW TRIGGERS LIKE 'baixa\_prod'
2073 Query SET SESSION character_set_results = 'utf8'
2073 Query show table status like 'bandeira'
2073 Query SET OPTION SQL_QUOTE_SHOW_CREATE=1
2073 Query SET SESSION character_set_results = 'binary'
2073 Query show create table `bandeira`
2073 Query SET SESSION character_set_results = 'utf8'
2073 Query show fields from `bandeira`
2073 Query SELECT /*!40001 SQL_NO_CACHE */ * FROM `bandeira`
我跑了mysql檢查它說沒關係：
# mysqlcheck ct1222 bandeira
ct1222.bandeira OK
mysql_error.log：
InnoDB: Error: tried to read 16384 bytes at offset 0 7290880.
InnoDB: Was only able to read -1.
180829 17:49:36 InnoDB: Operating system error number 5 in a file operation.
InnoDB: Error number 5 means 'Input/output error'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/operating-system-error-codes.html
InnoDB: File operation call: 'read'.
InnoDB: Cannot continue operation.
180829 17:49:38 mysqld_safe Number of processes running now: 0
180829 17:49:38 mysqld_safe mysqld restarted
180829 17:49:38 [Warning] 'for replication startup options' is deprecated and will be removed in a future release. Please use ''CHANGE MASTER'' instead.
180829 17:49:38 [Note] Plugin 'FEDERATED' is disabled.
180829 17:49:38 InnoDB: Initializing buffer pool, size = 8.0M
180829 17:49:38 InnoDB: Completed initialization of buffer pool
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
180829 17:49:38 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
180829 17:49:41 InnoDB: Started; log sequence number
答案1
您似乎遇到了硬體問題。
具體來說，它似乎是一個有故障的硬碟。當 InnoDB 嘗試從磁碟讀取頁面時，由於不可復原的 I/O 錯誤而無法讀取。這是致命的，所以伺服器實際上停止了，崩潰了，這就是你失去連接的原因。
之後的一切mysqld_safe Number of processes running now: 0都是 MySQL 重新啟動並從錯誤中恢復——所以實際的錯誤是在那條線之上。 （換句話說，不要因為接下來的事情而驚慌或分心。）
我推測您沒有備份，因為建立備份會遇到相同的錯誤。
但這本身似乎並不是「MySQL 問題」。您應該發現您也無法將 MySQL 的檔案複製到另一個磁碟，因為複製受影響的檔案會遇到相同的錯誤。哪個文件將取決於innodb_file_per_table.如果設定為0那麼恢復將會複雜得多。