MySQL重启端口被占用处理
1,查看日志的ERROR
2018-05-23T01:26:59.230382Z 0 [Warning] 'NO_AUTO_CREATE_USER' sql mode was not set.
2018-05-23T01:26:59.230409Z 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
2018-05-23T01:26:59.230457Z 0 [Note] /usr/bin/mysqld (mysqld 5.7.18-log) starting as process 1274 ...
2018-05-23T01:26:59.232456Z 0 [Warning] Using pre 5.5 semantics to load error messages from /usr/share/.
2018-05-23T01:26:59.232467Z 0 [Warning] If this is not intended, refer to the documentation for valid usage of --lc-messages-dir and --language parameters.
2018-05-23T01:26:59.338644Z 0 [Warning] InnoDB: Using innodb_large_prefix is deprecated and the parameter may be removed in future releases. See http://dev.mysql.com/doc/refman/5.7/en/innodb-file-format.html
2018-05-23T01:26:59.338778Z 0 [Note] InnoDB: PUNCH HOLE support not available
2018-05-23T01:26:59.338797Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2018-05-23T01:26:59.338811Z 0 [Note] InnoDB: Uses event mutexes
2018-05-23T01:26:59.338820Z 0 [Note] InnoDB: GCC builtin __sync_synchronize() is used for memory barrier
2018-05-23T01:26:59.338841Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-05-23T01:26:59.338849Z 0 [Note] InnoDB: Using Linux native AIO
2018-05-23T01:26:59.343415Z 0 [Note] InnoDB: Number of pools: 1
2018-05-23T01:26:59.343606Z 0 [Note] InnoDB: Using CPU crc32 instructions
2018-05-23T01:26:59.351180Z 0 [Note] InnoDB: Initializing buffer pool, total size = 16G, instances = 8, chunk size = 128M
2018-05-23T01:27:01.144704Z 0 [Note] InnoDB: Completed initialization of buffer pool
2018-05-23T01:27:01.805956Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2018-05-23T01:27:01.869612Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2018-05-23T01:27:02.161447Z 0 [Note] InnoDB: The log sequence number 463085832558 in the system tablespace does not match the log sequence number 527415094655 in the ib_logfiles! --表示磁盘lsn和共享表空间中lsn不一致
2018-05-23T01:27:02.161487Z 0 [Note] InnoDB: Database was not shutdown normally! --显示没有正常关机
2018-05-23T01:27:02.161500Z 0 [Note] InnoDB: Starting crash recovery.
2018-05-23T01:27:03.342445Z 0 [Note] InnoDB: Last MySQL binlog file position 0 835316239, file name slave1-bin.000662
2018-05-23T01:27:14.727716Z 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2018-05-23T01:27:14.727757Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2018-05-23T01:27:14.735961Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2018-05-23T01:27:14.779905Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2018-05-23T01:27:14.781644Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
2018-05-23T01:27:14.781675Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
2018-05-23T01:27:14.783034Z 0 [Note] InnoDB: Waiting for purge to start
2018-05-23T01:27:14.833225Z 0 [Note] InnoDB: page_cleaner: 1000ms intended loop took 13028ms. The settings might not be optimal. (flushed=0 and evicted=0, during the time.)
2018-05-23T01:27:14.844368Z 0 [Note] InnoDB: 5.7.18 started; log sequence number 527415094655
2018-05-23T01:27:14.844947Z 0 [Note] InnoDB: Loading buffer pool(s) from /r2/mysqldata/ib_buffer_pool
2018-05-23T01:27:14.845201Z 0 [Note] InnoDB: Buffer pool(s) load completed at 180523 9:27:14 (/r2/mysqldata/ib_buffer_pool was empty)
2018-05-23T01:27:14.850829Z 0 [Note] Plugin 'FEDERATED' is disabled.
2018-05-23T01:27:31.198380Z 0 [Warning] Failed to set up SSL because of the following SSL library error: SSL context is not usable without certificate and private key
2018-05-23T01:27:31.198414Z 0 [Note] Server hostname (bind-address): '*'; port: 3306
2018-05-23T01:27:31.198460Z 0 [Note] IPv6 is available.
2018-05-23T01:27:31.198473Z 0 [Note] - '::' resolves to '::';
2018-05-23T01:27:31.198521Z 0 [Note] Server socket created on IP: '::'.
2018-05-23T01:27:31.198551Z 0 [ERROR] Can't start server: Bind on TCP/IP port: Address already in use
2018-05-23T01:27:31.198557Z 0 [ERROR] Do you already have another mysqld server running on port: 3306 ? --显示端口被占用
2018-05-23T01:27:31.198569Z 0 [ERROR] Aborting
2018-05-23T01:27:31.201402Z 0 [Note] Binlog end
2018-05-23T01:27:31.202398Z 0 [Note] Shutting down plugin 'ngram'
2018-05-23T01:27:31.202428Z 0 [Note] Shutting down plugin 'partition'
2018-05-23T01:27:31.202434Z 0 [Note] Shutting down plugin 'ARCHIVE'
2018-05-23T01:27:31.202439Z 0 [Note] Shutting down plugin 'BLACKHOLE'
2018-05-23T01:27:31.202447Z 0 [Note] Shutting down plugin 'MRG_MYISAM'
2018-05-23T01:27:31.202453Z 0 [Note] Shutting down plugin 'MyISAM'
2018-05-23T01:27:31.203867Z 0 [Note] Shutting down plugin 'INNODB_SYS_VIRTUAL'
2018-05-23T01:27:31.203880Z 0 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'
2018-05-23T01:27:31.203885Z 0 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'
2018-05-23T01:27:31.203890Z 0 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
2018-05-23T01:27:31.203895Z 0 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
2018-05-23T01:27:31.203899Z 0 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'
2018-05-23T01:27:31.203904Z 0 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
2018-05-23T01:27:31.203909Z 0 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
2018-05-23T01:27:31.203913Z 0 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'
2018-05-23T01:27:31.203923Z 0 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
2018-05-23T01:27:31.203927Z 0 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
2018-05-23T01:27:31.203932Z 0 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE'
2018-05-23T01:27:31.203936Z 0 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
2018-05-23T01:27:31.203940Z 0 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'
2018-05-23T01:27:31.203945Z 0 [Note] Shutting down plugin 'INNODB_FT_DELETED'
2018-05-23T01:27:31.203950Z 0 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'
2018-05-23T01:27:31.203954Z 0 [Note] Shutting down plugin 'INNODB_METRICS'
2018-05-23T01:27:31.203959Z 0 [Note] Shutting down plugin 'INNODB_TEMP_TABLE_INFO'
2018-05-23T01:27:31.203963Z 0 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS'
2018-05-23T01:27:31.203968Z 0 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
2018-05-23T01:27:31.203972Z 0 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE'
2018-05-23T01:27:31.203984Z 0 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
2018-05-23T01:27:31.203989Z 0 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'
2018-05-23T01:27:31.203993Z 0 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'
2018-05-23T01:27:31.203997Z 0 [Note] Shutting down plugin 'INNODB_CMPMEM'
2018-05-23T01:27:31.204002Z 0 [Note] Shutting down plugin 'INNODB_CMP_RESET'
2018-05-23T01:27:31.204006Z 0 [Note] Shutting down plugin 'INNODB_CMP'
2018-05-23T01:27:31.204010Z 0 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'
2018-05-23T01:27:31.204015Z 0 [Note] Shutting down plugin 'INNODB_LOCKS'
2018-05-23T01:27:31.204019Z 0 [Note] Shutting down plugin 'INNODB_TRX'
2018-05-23T01:27:31.204024Z 0 [Note] Shutting down plugin 'InnoDB'
2018-05-23T01:27:31.204097Z 0 [Note] InnoDB: FTS optimize thread exiting.
2018-05-23T01:27:31.204234Z 0 [Note] InnoDB: Starting shutdown...
2018-05-23T01:27:31.304450Z 0 [Note] InnoDB: Dumping buffer pool(s) to /r2/mysqldata/ib_buffer_pool
2018-05-23T01:27:31.305044Z 0 [Note] InnoDB: Buffer pool(s) dump completed at 180523 9:27:31
2018-05-23T01:27:33.817117Z 0 [Note] InnoDB: Shutdown completed; log sequence number 527415094683
2018-05-23T01:27:33.817469Z 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2018-05-23T01:27:33.817494Z 0 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
2018-05-23T01:27:33.817618Z 0 [Note] Shutting down plugin 'MEMORY'
2018-05-23T01:27:33.817632Z 0 [Note] Shutting down plugin 'CSV'
2018-05-23T01:27:33.817642Z 0 [Note] Shutting down plugin 'sha256_password'
2018-05-23T01:27:33.817659Z 0 [Note] Shutting down plugin 'mysql_native_password'
2018-05-23T01:27:33.817898Z 0 [Note] Shutting down plugin 'binlog'
2018-05-23T01:27:33.819411Z 0 [Note] /usr/bin/mysqld: Shutdown complete
2,查看3306端口的进程情况
[root@slave1 mysqldata]# netstat -an |grep 3306
tcp 0 0 192.168.102.131:52090 192.168.102.130:3306 ESTABLISHED
tcp 0 0 192.168.102.131:54416 192.168.102.130:3306 ESTABLISHED
tcp 0 0 192.168.102.131:32214 192.168.102.137:3306 TIME_WAIT
tcp 0 0 192.168.102.131:60596 192.168.102.137:3306 TIME_WAIT
tcp 0 0 127.0.0.1:3306 127.0.0.1:3306 ESTABLISHED --ESTABLISHED的意思是建立连接。表示两台机器正在通信。
tcp 0 0 192.168.102.131:26186 192.168.102.130:3306 ESTABLISHED
tcp 0 0 192.168.102.131:54528 192.168.102.130:3306 ESTABLISHED
tcp 0 0 192.168.102.131:52587 192.168.102.130:3306 ESTABLISHED
unix 3 [ ] STREAM CONNECTED 23306
[root@slave1 mysqldata]# ps -ef |grep mysql
root 874 1 0 5月21 ? 00:00:00 /bin/sh -c /usr/local/percona/qan-agent/bin/percona-qan-agent >> /var/log/pmm-mysql-queries-0.log 2>&1
root 23208 1977 0 09:34 pts/1 00:00:00 grep --color=auto mysql
root 27712 1 0 5月21 ? 00:00:00 /bin/sh -c /usr/local/percona/pmm-client/mysqld_exporter -collect.auto_increment.columns=false -collect.binlog_size=true -collect.global_status=true -collect.global_variables=true -collect.info_schema.innodb_metrics=true -collect.info_schema.processlist=true -collect.info_schema.query_response_time=true -collect.info_schema.tables=false -collect.info_schema.tablestats=false -collect.info_schema.userstats=true -collect.perf_schema.eventswaits=true -collect.perf_schema.file_events=true -collect.perf_schema.indexiowaits=false -collect.perf_schema.tableiowaits=false -collect.perf_schema.tablelocks=false -collect.slave_status=true -web.listen-address=192.168.101.131:42002 -web.auth-file=/usr/local/percona/pmm-client/pmm.yml -web.ssl-cert-file=/usr/local/percona/pmm-client/server.crt -web.ssl-key-file=/usr/local/percona/pmm-client/server.key >> /var/log/pmm-mysql-metrics-42002.log2>&1
root 27714 27712 5 5月21 ? 02:45:30 /usr/local/percona/pmm-client/mysqld_exporter -collect.auto_increment.columns=false -collect.binlog_size=true -collect.global_status=true -collect.global_variables=true -collect.info_schema.innodb_metrics=true -collect.info_schema.processlist=true -collect.info_schema.query_response_time=true -collect.info_schema.tables=false -collect.info_schema.tablestats=false -collect.info_schema.userstats=true -collect.perf_schema.eventswaits=true -collect.perf_schema.file_events=true -collect.perf_schema.indexiowaits=false -collect.perf_schema.tableiowaits=false -collect.perf_schema.tablelocks=false -collect.slave_status=true -web.listen-address=192.168.101.131:42002 -web.auth-file=/usr/local/percona/pmm-client/pmm.yml -web.ssl-cert-file=/usr/local/percona/pmm-client/server.crt -web.ssl-key-file=/usr/local/percona/pmm-client/server.key
root 29857 1 0 5月22 ? 00:00:00 /bin/sh -c [ `ps -ef |grep orzdba_mysql|grep -v grep|wc -l` -eq 0 ] && source /etc/profile && /scripts/db/orzdba -i 10 -t -mysql -innodb_rows -L /r2/monitor/orzdba_mysql.log -logfile_by_day > /dev/null 2>&1 &
root 29928 29857 0 5月22 ? 00:00:00 /usr/bin/perl -w /scripts/db/orzdba -i 10 -t -mysql -innodb_rows -L /r2/monitor/orzdba_mysql.log -logfile_by_day
root 29937 29928 0 5月22 ? 00:00:00 mysql -s --skip-column-names -h127.0.0.1 -umonitor -px xxxxxxxxxxxxxxxxxx -P3306 -e show variables where Variable_name in ("sync_binlog","max_connections","max_user_connections","max_connect_errors","table_open_cache","table_definition_cache","thread_cache_size","binlog_format","open_files_limit","max_binlog_size","max_binlog_cache_size")
3,获取进程的名称
[root@slave1 mysqldata]# lsof -i:3306
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
tsg.exe 27014 root 10u IPv4 28164389 0t0 TCP（ secondmaster:54416->master:mysql ）(ESTABLISHED) --ESTABLISHED的意思是建立连接。表示两台机器mysql正在通信。
tsg.exe 27014 root 21u IPv4 28148523 0t0 TCP secondmaster:54528->master:mysql (ESTABLISHED)
mysql 29937 root 3u IPv4 14731893 0t0 TCP localhost:mysql->localhost:mysql (ESTABLISHED) --ESTABLISHED的意思是建立连接。表示本地mysql正在通信。要kill掉
iacs.exe 45909 root 10u IPv4 3015961 0t0 TCP secondmaster:26186->master:mysql (ESTABLISHED)
iacs.exe 45909 root 21u IPv4 2996694 0t0 TCP secondmaster:52090->master:mysql (ESTABLISHED)
iacs.exe 45909 root 65u IPv4 23893332 0t0 TCP secondmaster:52587->master:mysql (ESTABLISHED)
COMMAND：进程的名称
PID：进程标识符
USER：进程所有者
FD：文件描述符，应用程序通过文件描述符识别该文件。如cwd、txt等
TYPE：文件类型，如DIR、REG等
DEVICE：指定磁盘的名称
SIZE：文件的大小
NODE：索引节点（文件在磁盘上的标识）
NAME：打开文件的确切名称
4,kill掉进程
[root@slave1 mysqldata]# ps -aux | grep 29937
root 29937 0.0 0.0 133488 1924 ? S 5月22 0:00 mysql -s --skip-column-names -h127.0.0.1 -umonitor -px xxxxxxxxxxxxxxxxxx -P3306 -e show variables where Variable_name in("sync_binlog","max_connections","max_user_connections","max_connect_errors","table_open_cache","table_definition_cache","thread_cache_size","binlog_format","open_files_limit","max_binlog_size","max_binlog_cache_size")
root 34694 0.0 0.0 112684 988 pts/1 S+ 09:35 0:00 grep --color=auto 29937
[root@slave1 mysqldata]# kill -9 29937
5,重启MySQL,先关闭连接
[root@slave1 mysqldata]# vim /etc/my.cnf --更改日志时区
[root@slave1 mysqldata]# > error.log
[root@slave1 mysqldata]# systemctl stop mysql --先执行关闭，kill掉两台机器mysql连接（ secondmaster:54416->master:mysql ）
[root@slave1 mysqldata]# systemctl start mysql
[root@slave1 mysqldata]# tailf -500 error.log
2018-05-23T09:38:31.396150+08:00 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2018-05-23T09:38:31.396251+08:00 0 [Warning] 'NO_AUTO_CREATE_USER' sql mode was not set.
2018-05-23T09:38:31.396284+08:00 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
2018-05-23T09:38:31.396326+08:00 0 [Note] /usr/bin/mysqld (mysqld 5.7.18-log) starting as process 12884 ...
2018-05-23T09:38:31.397974+08:00 0 [Warning] Using pre 5.5 semantics to load error messages from /usr/share/.
2018-05-23T09:38:31.397983+08:00 0 [Warning] If this is not intended, refer to the documentation for valid usage of --lc-messages-dir and --language parameters.
2018-05-23T09:38:31.439195+08:00 0 [Warning] InnoDB: Using innodb_large_prefix is deprecated and the parameter may be removed in future releases. See http://dev.mysql.com/doc/refman/5.7/en/innodb-file-format.html
2018-05-23T09:38:31.439324+08:00 0 [Note] InnoDB: PUNCH HOLE support not available
2018-05-23T09:38:31.439343+08:00 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2018-05-23T09:38:31.439352+08:00 0 [Note] InnoDB: Uses event mutexes
2018-05-23T09:38:31.439361+08:00 0 [Note] InnoDB: GCC builtin __sync_synchronize() is used for memory barrier
2018-05-23T09:38:31.439370+08:00 0 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-05-23T09:38:31.439379+08:00 0 [Note] InnoDB: Using Linux native AIO
2018-05-23T09:38:31.442855+08:00 0 [Note] InnoDB: Number of pools: 1
2018-05-23T09:38:31.443024+08:00 0 [Note] InnoDB: Using CPU crc32 instructions
2018-05-23T09:38:31.445355+08:00 0 [Note] InnoDB: Initializing buffer pool, total size = 16G, instances = 8, chunk size = 128M
2018-05-23T09:38:32.980649+08:00 0 [Note] InnoDB: Completed initialization of buffer pool
2018-05-23T09:38:33.207935+08:00 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2018-05-23T09:38:33.241437+08:00 0 [Note] InnoDB: Highest supported file format is Barracuda.
2018-05-23T09:38:34.034327+08:00 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2018-05-23T09:38:34.034431+08:00 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2018-05-23T09:38:34.043708+08:00 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2018-05-23T09:38:34.044716+08:00 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
2018-05-23T09:38:34.044745+08:00 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
2018-05-23T09:38:34.045637+08:00 0 [Note] InnoDB: Waiting for purge to start
2018-05-23T09:38:34.095960+08:00 0 [Note] InnoDB: 5.7.18 started; log sequence number 527415094702
2018-05-23T09:38:34.096530+08:00 0 [Note] InnoDB: Loading buffer pool(s) from /r2/mysqldata/ib_buffer_pool
2018-05-23T09:38:34.097285+08:00 0 [Note] Plugin 'FEDERATED' is disabled.
2018-05-23T09:38:34.160270+08:00 0 [Note] InnoDB: Buffer pool(s) load completed at 180523 9:38:34
2018-05-23T09:38:34.171769+08:00 0 [Warning] Failed to set up SSL because of the following SSL library error: SSL context is not usable without certificate and private key
2018-05-23T09:38:34.171815+08:00 0 [Note] Server hostname (bind-address): '*'; port: 3306
2018-05-23T09:38:34.171876+08:00 0 [Note] IPv6 is available.
2018-05-23T09:38:34.171900+08:00 0 [Note] - '::' resolves to '::';
2018-05-23T09:38:34.171963+08:00 0 [Note] Server socket created on IP: '::'.
2018-05-23T09:38:34.297995+08:00 0 [Warning] 'user' entry 'root@localhost' ignored in --skip-name-resolve mode.
2018-05-23T09:38:34.298227+08:00 0 [Warning] 'user' entry 'operator@localhost' ignored in --skip-name-resolve mode.
2018-05-23T09:38:34.305132+08:00 0 [Warning] 'db' entry 'sys mysql.sys@localhost' ignored in --skip-name-resolve mode.
2018-05-23T09:38:34.312612+08:00 0 [Warning] 'proxies_priv' entry '@ root@localhost' ignored in --skip-name-resolve mode.
2018-05-23T09:38:34.414747+08:00 0 [Warning] 'tables_priv' entry 'sys_config mysql.sys@localhost' ignored in --skip-name-resolve mode.
2018-05-23T09:38:34.497898+08:00 0 [Warning] Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a slave and has his hostname changed!! Please use '--relay-log=slave1-relay-bin' to avoid this problem.
2018-05-23T09:38:46.589637+08:00 1 [Warning] Slave SQL for channel '': If a crash happens this configuration does not guarantee that the relay log info will be consistent, Error_code: 0
2018-05-23T09:38:46.589652+08:00 2 [Warning] Storing MySQL user name or password information in the master info repository is not secure and is therefore not recommended. Please considerusing the USER and PASSWORD connection options for START SLAVE; see the 'START SLAVE Syntax' in the MySQL Manual for more information.
2018-05-23T09:38:46.589735+08:00 1 [Note] Slave SQL thread for channel '' initialized, starting replication in log 'slave1-bin.000461' at position 1035528252, relay log './slave1-relay-bin.000079' position: 1035528467
2018-05-23T09:38:46.591039+08:00 2 [Note] Slave I/O thread for channel '': connected to master 'repl@192.168.102.130:3306',replication started in log 'slave1-bin.000461' at position 1035528252
2018-05-23T09:38:46.717702+08:00 0 [Note] Event Scheduler: Loaded 0 events
2018-05-23T09:38:46.718462+08:00 0 [Note] /usr/bin/mysqld: ready for connections.
Version: '5.7.18-log' socket: '/r2/mysqldata/mysql.sock' port: 3306 MySQL Community Server (GPL)
2018-05-23T09:38:46.718484+08:00 0 [Note] Executing 'SELECT * FROM INFORMATION_SCHEMA.TABLES;' to get a list of tables using the deprecated partition engine. You may use the startup option '--disable-partition-engine-check' to skip this check.
2018-05-23T09:38:46.718491+08:00 0 [Note] Beginning of list of non-natively partitioned tables
2018-05-23T09:38:58.533297+08:00 0 [Note] End of list of non-natively partitioned tables
MySQL重启端口被占用处理的更多相关文章
- XAMPP启动MySQL时报端口被占用错误
1 问题描述 启动XAMPP中的mysql时宝凑,错误信息是:3306端口被占用 2 问题诊断 2.1 可能是在安装XAMPP之前安装了MySQL,这样电脑中就有两个MySQL啦,如果我们在安装时都采 ...
- 解决：xampp中Apache, MySql, Filezilla端口占用问题
读 静觅 的python博客,学到requests库的用法,看到“”如果想请求JSON文件,可以利用 json() 方法解析 ”这里迷惑了: 我写了a.json文件放在本地,却不能被python调用, ...
- 使用phpstuby时，Apache或mysql无法启动，端口被占用
使用phpstuby时,Apache或mysql无法启动,端口被占用,怎么办? 原因: 其它程序占用了80或3306端口. 如果占用了80端口则Apache无法启动: 如果占用了3306端口则mysq ...
- Apache 80 端口被占用无法重启解决办法
原文出处 Apache 80 端口被占用无法重启解决办法 www.111cn.net 编辑:tiger 来源:转载使用WEB服务器的朋友都知道80端口是一个用来对外让用户访问的一个端口了,像apach ...
- 【MYSQL】安装MySQL端口被占用
出现问题: 安装mysql时,发现端口被占用 解决方法: 方法一: 修改端口号:3308,3309等都可以 方法二: 按键盘"win+r" → 打开 cmd → 输入netstat ...
- 3306端口被占用导致MySQL无法启动
报错:mysql服务无法启动1067 发现WINDOWS下面没有MYSQL的服务在MYSQL的安装目录bin下面安装MYSQL服务:C:\Program Files\MySQL\MySQL Serve ...
- phpstudy80端口被占用时的解决方案
1.适合人群? 之前笔记本单独安装过Apache.php.mysql环境,但是后期想用集成开发环境phpstudy的,安装完phpstudy后(之前的单独环境依然存在),发现启动时,总是显示80端口被 ...
- MYSQL连接端口被占引入文件路径错误
今天早上打算本地win7机器上用Wampserver搭建PHP环境,把自己的程序配置上去.下载最新的wampserver 3.0.6版本安装后,发现mysql一直无法运行,以为是wampserver版 ...
- xampp 80端口被占用解决办法
很多朋友安装xampp之后,启用服务器或者数据库失败,发现端口已经被占用.因为每台电脑占用端口的软件不一样,要如何解决这个问题. 第一种解决方法: 检查软件安装路径中是否有中文,如下图: 解决方法: ...
随机推荐
- 记 fastjson泛型转对象 第一次可以正常转，第二次就变成JSONArray 问题
在解析json数据的时候,在使用泛型对象的时候即: public class ResultMsgDto<E> implements Serializable { private stati ...
- vue.js 源代码学习笔记 ----- $watcher
/* @flow */ import { queueWatcher } from './scheduler' import Dep, { pushTarget, popTarget } from '. ...
- DOM2级事件处理程序
DOM2级时间定义了两个方法:addEventListener() 和removeEventListener() 他们都接受3个参数:1)要处理的事件名 2)作为事件处理程序的函数 3)一个布尔值 ...
- 使用编译时注解简单实现类似 ButterKnife 的效果
这篇文章是学习鸿洋前辈的 Android 如何编写基于编译时注解的项目 的笔记,用于记录我的学习收获. 读完本文你将了解: 什么是编译时注解 APT 编译时注解如何使用与编写 举个例子 思路 创建注解 ...
- oracle数据库导入导出09192255
1.导入数据库(dmp) Linux系统中: 1. 用root账号登录服务器,然后切换到oracle账号(安装oracle数据库的时候用的用的账号) 2. 切换到oralce的安装目录下的bin下 3 ...
- 关于HTTPS理论和实践
Summary: HTTP 通信时,可能信息被监听.服务器或客户端身份伪装等安全问题,HTTPS 则能有效解决这些问题. 原始的HTTP连接的时候,因服务器与用户之间是直接进行明文传输,导致用户面临着 ...
- 细说C语言的优先级和结合性
Table0. 为什么要掌握优先级1. 优先级1.1 优先级图表1.2 运算符实例1.3 优先级顺口溜2. 结合性3. 参考资料 写代码的时候,常会翻看的一个表就是“c语言运算符优先级表”.c的运算符 ...
- ssm异常；
问题:Invalid bound statement (not found): com.itq.mapper.TbItemMapper.selectByExample 解决:修改pom.xml文件中添 ...
- {Notes}{Latex}{multirow}
这个文章写的真的太牛比了! ============================================================ 在latex文件最前面用这个包\usepackag ...
- matlab中卷积编码参数的理解
poly2trellis(7, [171 133])代表什么意思呢?首先是7,他是1*k的vector,此处k为1,[171 133]是k*n的vector,此处n就是2,那么这个编码就是1/2码率的 ...