我们使用master(5.5.32版本)作为一个名为Layer7的API管理器。保存这些实例的两个主机位于相同的ESX中。
我们不时地让mysql做一个干净的关闭,因为现在的原因
我们检查cron作业,它们都是空的。在这段时间里,我们检查了主机或实例的登录,但是没有
除了手动关机、从脚本或应用程序关机或由于杀死可能导致主主配置中的干净关机而关闭之外。
下面是实例停止的主机的日志
谢谢
问候
150605 18:59:32 [Note] /usr/sbin/mysqld: Normal shutdown
150605 18:59:32 [Note] Event Scheduler: Purging the queue. 0 events
150605 18:59:32 [Note] Error reading relay log event: slave SQL thread was killed
150605 18:59:32 [ERROR] Error reading packet from server: Lost connection to MySQL server during query ( server_errno=2013)
150605 18:59:32 [Note] Slave I/O thread killed while reading event
150605 18:59:32 [Note] Slave I/O thread exiting, read up to log 'ssgbin-log.000351', position 91210654
150605 18:59:34 [Warning] /usr/sbin/mysqld: Forcing close of thread 21360878 user: 'gateway'
150605 18:59:34 [Warning] /usr/sbin/mysqld: Forcing close of thread 21360872 user: 'gateway'
150605 18:59:34 [Warning] /usr/sbin/mysqld: Forcing close of thread 21360871 user: 'gateway'
150605 18:59:34 [Warning] /usr/sbin/mysqld: Forcing close of thread 21360864 user: 'gateway'
150605 18:59:34 [Warning] /usr/sbin/mysqld: Forcing close of thread 21360860 user: 'gateway'
150605 18:59:34 [Warning] /usr/sbin/mysqld: Forcing close of thread 21360859 user: 'gateway'
150605 18:59:34 [Warning] /usr/sbin/mysqld: Forcing close of thread 21360858 user: 'gateway'
150605 18:59:34 [Warning] /usr/sbin/mysqld: Forcing close of thread 21360857 user: 'gateway'
150605 18:59:34 [Warning] /usr/sbin/mysqld: Forcing close of thread 21360855 user: 'gateway'
150605 18:59:34 [Warning] /usr/sbin/mysqld: Forcing close of thread 21360854 user: 'gateway'
150605 18:59:34 [Warning] /usr/sbin/mysqld: Forcing close of thread 21360853 user: 'gateway'
150605 18:59:34 [Warning] /usr/sbin/mysqld: Forcing close of thread 21360851 user: 'gateway'
150605 18:59:34 [Warning] /usr/sbin/mysqld: Forcing close of thread 21360849 user: 'gateway'
150605 18:59:34 [Warning] /usr/sbin/mysqld: Forcing close of thread 21360848 user: 'gateway'
150605 18:59:34 [Warning] /usr/sbin/mysqld: Forcing close of thread 21360847 user: 'gateway'
150605 18:59:34 [Warning] /usr/sbin/mysqld: Forcing close of thread 21360846 user: 'gateway'
150605 18:59:36 InnoDB: Starting shutdown...
150605 18:59:36 InnoDB: Waiting for 76 pages to be flushed
150605 18:59:37 InnoDB: Shutdown completed; log sequence number 5077358548454
150605 18:59:37 [Note] /usr/sbin/mysqld: Shutdown complete
150605 18:59:37 mysqld_safe mysqld from pid file /var/lib/mysql/mtllnl7.mtl.cbc.ca.pid ended
150605 18:59:38 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
150605 18:59:38 [Note] Plugin 'FEDERATED' is disabled.
150605 18:59:38 [Note] Plugin 'partition' is disabled.
150605 18:59:38 InnoDB: The InnoDB memory heap is disabled
150605 18:59:38 InnoDB: Mutexes and rw_locks use GCC atomic builtins
150605 18:59:38 InnoDB: Compressed tables use zlib 1.2.3
150605 18:59:38 InnoDB: Using Linux native AIO
150605 18:59:38 InnoDB: Initializing buffer pool, size = 512.0M
150605 18:59:38 InnoDB: Completed initialization of buffer pool
150605 18:59:38 InnoDB: highest supported file format is Barracuda.
150605 18:59:38 InnoDB: Waiting for the background threads to start
150605 18:59:39 InnoDB: 5.5.32 started; log sequence number 5077358548454
150605 18:59:39 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
150605 18:59:39 [Note] - '0.0.0.0' resolves to '0.0.0.0';
150605 18:59:39 [Note] Server socket created on IP: '0.0.0.0'.
150605 18:59:39 [Note] Slave SQL thread initialized, starting replication in log 'ssgbin-log.000351' at position 91210654, relay log '/var/lib/mysql/ssgrelay-bin.000635' position: 854358
150605 18:59:39 [Note] Slave I/O thread: connected to master 'repluser@mtllnl7.mtl.cbc.ca:3307',replication started in log 'ssgbin-log.000351' at position 91210654
150605 18:59:39 [Note] Event Scheduler: Loaded 0 events
150605 18:59:39 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.32-enterprise-commercial-advanced-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Enterprise Server - Advanced Edition (Commercial)
150605 19:05:09 [Note] Slave: received end packet from server, apparent master shutdown:
150605 19:05:09 [Note] Slave I/O thread: Failed reading log event, reconnecting to retry, log 'ssgbin-log.000351' at position 94453851
150605 19:05:09 [ERROR] Slave I/O: error reconnecting to master 'repluser@mtllnl7.mtl.cbc.ca:3307' - retry-time: 10 retries: 86400, Error_code: 2003
150605 19:05:29 [Note] Slave: connected to master 'repluser@mtllnl7.mtl.cbc.ca:3307',replication resumed in log 'ssgbin-log.000351' at position 94453851发布于 2015-06-17 18:45:32
The 关闭特权只能在运行mysqladmin时使用.
Apr 22, 2013:/usr/libexec/mysqld:正常关闭,但我的团队不这样做?Mar 06, 2013:如何正确地杀死MySQL?Feb 28, 2013:mysql重新启动不会杀死CentOS上的子进程取消停工授权将阻止用户运行mysqladmin shutdown。
问题中显示的错误日志是重新启动mysqld。
150605 18:59:32 [Note] /usr/sbin/mysqld: Normal shutdown
.
.
.
150605 18:59:36 InnoDB: Starting shutdown...
150605 18:59:36 InnoDB: Waiting for 76 pages to be flushed
150605 18:59:37 InnoDB: Shutdown completed; log sequence number 5077358548454
150605 18:59:37 [Note] /usr/sbin/mysqld: Shutdown complete
150605 18:59:37 mysqld_safe mysqld from pid file /var/lib/mysql/mtllnl7.mtl.cbc.ca.pid ended
150605 18:59:38 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysqlmysqladmin无法启动或重新启动mysqld。
有人或其他人正在运行service mysql restart
首先运行历史
# history | grep restart如果在您看到的重新启动过程中没有出现任何问题,则需要在正在执行service mysql restart的DB Server上找到一个cron作业。在某些情况下,它可能是远程服务器上的一个无人记得的任务。
https://dba.stackexchange.com/questions/104343
复制相似问题