国产 无码 综合区,色欲AV无码国产永久播放,无码天堂亚洲国产AV,国产日韩欧美女同一区二区

MySQL報(bào)錯(cuò):The server quit without updating PID file 我的解決思路和方法

這篇具有很好參考價(jià)值的文章主要介紹了MySQL報(bào)錯(cuò):The server quit without updating PID file 我的解決思路和方法。希望對(duì)大家有所幫助。如果存在錯(cuò)誤或未考慮完全的地方,請(qǐng)大家不吝賜教,您也可以點(diǎn)擊"舉報(bào)違法"按鈕提交疑問。

今天在學(xué)習(xí)mysql 二進(jìn)制日志的時(shí)候需要在編輯my.cnf的文件,產(chǎn)生的一系列報(bào)錯(cuò),個(gè)人的排錯(cuò)思路和方法,僅供參考。

the server quit without updating pid file,mysql,mysql,數(shù)據(jù)庫,服務(wù)器

重啟damon、重啟mysql 發(fā)現(xiàn)報(bào)錯(cuò)

Starting MySQL. ERROR! The server quit without updating PID file (/usr/local/mysql/data/mysqld.pid).
the server quit without updating pid file,mysql,mysql,數(shù)據(jù)庫,服務(wù)器

發(fā)現(xiàn)注釋這三行配置之后發(fā)現(xiàn)可以正常啟動(dòng),那么問題就出現(xiàn)在這三行代碼上

log-bin = mysql-bin??
#binlog_expire_logs_seconds = 600
#max_binlog_size = 200M

the server quit without updating pid file,mysql,mysql,數(shù)據(jù)庫,服務(wù)器?查詢?nèi)罩景l(fā)現(xiàn)報(bào)錯(cuò):You have enabled the binary log, but you haven't provided the mandatory server-id. Please refer to the proper server start-up parameters documentation#您已經(jīng)啟用了二進(jìn)制日志,但是沒有提供必需的服務(wù)器id。請(qǐng)參考適當(dāng)?shù)姆?wù)器啟動(dòng)參數(shù)文檔

?經(jīng)過百度發(fā)現(xiàn):MySQL 5.7.3以后版本必須配置server-id,否則無法啟用MySQL二進(jìn)制日志
?嘗試啟動(dòng) 在my.cnf中添加 server-id = 1 ? 唯一的服務(wù)辨識(shí)號(hào),數(shù)值位于 1 到 2^32-1之間。此值在master和slave上都需要設(shè)置。
如果 “master-host” 沒有被設(shè)置,則默認(rèn)為1, 但是如果忽略此選項(xiàng),MySQL不會(huì)作為master生效

添加參數(shù),并嘗試啟動(dòng)。?

發(fā)現(xiàn)又報(bào)錯(cuò):Can't connect to local MySQL server through socket '/tmp/mysql.sock'

the server quit without updating pid file,mysql,mysql,數(shù)據(jù)庫,服務(wù)器

mysql的連接方式有兩種:一種是TCP/IP、一種是socket連接

mysql.sock的作用是程序與mysqlserver處于同一臺(tái)機(jī)器,發(fā)起本地連接時(shí)可用。?
連接localhost通常通過一個(gè)Unix域套接字文件進(jìn)行,一般是/tmp/mysql.sock。
如果套接字文件被刪除了,本地客戶就不能連接。/tmp 文件夾屬于臨時(shí)文件,隨時(shí)可能被刪除。
每次mysql 啟動(dòng)的時(shí)候,都會(huì)生成一個(gè)mysql.sock 的文件,

socket = /var/lib/mysql/mysql.sock???建議將sock文件移動(dòng)至下var/lib/mysql/??

嘗試重新啟動(dòng) 發(fā)現(xiàn)還是報(bào)錯(cuò)?Starting MySQL. ERROR! The server quit without updating PID file

排錯(cuò):

?1.?檢查目錄權(quán)限 ? ?

?2. selinux是否關(guān)閉??

?3. 檢查my.cnf參數(shù) port,datadir,basedir,socket 是否配置正常

排錯(cuò)發(fā)現(xiàn)是我配置sock目錄時(shí)候,并沒有給予權(quán)限

chown -R mysql:mysql?/var/lib/mysql/? ?#設(shè)置權(quán)限,并查看
ls -alh | grep mysql
drwxr-xr-x.  2 mysql   mysql      6 Sep 14 16:19 mysql

再次嘗試啟動(dòng)mysql 發(fā)現(xiàn)還是報(bào)錯(cuò):Starting MySQL. ERROR! The server quit without updating PID file (/usr/local/mysql/data/mysqld.pid).

1. tail -f /usr/local/mysql/data/mysql.err? /查詢MySQL自帶的日志文件mysql.err

?#發(fā)現(xiàn)沒有關(guān)鍵錯(cuò)誤信息

the server quit without updating pid file,mysql,mysql,數(shù)據(jù)庫,服務(wù)器

?2.?tail /var/log/messages? #記錄了絕大多數(shù)的系統(tǒng)日志?

?2022-09-15T06:32:03.776090Z 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
2022-09-15T06:32:03.776188Z 0 [Note] /usr/local/mysql/bin/mysqld (mysqld 5.7.33-log) starting as process 57901 ...
2022-09-15T06:32:03.780168Z 0 [Note] InnoDB: PUNCH HOLE support available
2022-09-15T06:32:03.780229Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2022-09-15T06:32:03.780253Z 0 [Note] InnoDB: Uses event mutexes
2022-09-15T06:32:03.780278Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2022-09-15T06:32:03.780411Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2022-09-15T06:32:03.780419Z 0 [Note] InnoDB: Using Linux native AIO
2022-09-15T06:32:03.780605Z 0 [Note] InnoDB: Number of pools: 1
2022-09-15T06:32:03.780695Z 0 [Note] InnoDB: Using CPU crc32 instructions
2022-09-15T06:32:03.781783Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2022-09-15T06:32:03.787253Z 0 [Note] InnoDB: Completed initialization of buffer pool
2022-09-15T06:32:03.789167Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2022-09-15T06:32:03.800452Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2022-09-15T06:32:03.805695Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2022-09-15T06:32:03.805865Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2022-09-15T06:32:03.819123Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2022-09-15T06:32:03.820045Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
2022-09-15T06:32:03.820088Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
2022-09-15T06:32:03.821153Z 0 [Note] InnoDB: Waiting for purge to start
2022-09-15T06:32:03.872143Z 0 [Note] InnoDB: 5.7.33 started; log sequence number 2980979
2022-09-15T06:32:03.872679Z 0 [Note] InnoDB: Loading buffer pool(s) from /usr/local/mysql/data/ib_buffer_pool
2022-09-15T06:32:03.872896Z 0 [Note] Plugin 'FEDERATED' is disabled.
2022-09-15T06:32:03.873741Z 0 [Note] InnoDB: Buffer pool(s) load completed at 220915 14:32:03
2022-09-15T06:32:03.875555Z 0 [ERROR] unknown variable 'binlog_expire_logs_seconds=600'
2022-09-15T06:32:03.875596Z 0 [ERROR] Aborting

2022-09-15T06:32:03.875610Z 0 [Note] Binlog end
2022-09-15T06:32:03.875666Z 0 [Note] Shutting down plugin 'ngram'
2022-09-15T06:32:03.875678Z 0 [Note] Shutting down plugin 'partition'
2022-09-15T06:32:03.875681Z 0 [Note] Shutting down plugin 'BLACKHOLE'
2022-09-15T06:32:03.875684Z 0 [Note] Shutting down plugin 'ARCHIVE'
2022-09-15T06:32:03.875687Z 0 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
2022-09-15T06:32:03.875727Z 0 [Note] Shutting down plugin 'MRG_MYISAM'
2022-09-15T06:32:03.875730Z 0 [Note] Shutting down plugin 'MyISAM'
2022-09-15T06:32:03.875738Z 0 [Note] Shutting down plugin 'INNODB_SYS_VIRTUAL'
2022-09-15T06:32:03.875741Z 0 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'
2022-09-15T06:32:03.875742Z 0 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'
2022-09-15T06:32:03.875744Z 0 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
2022-09-15T06:32:03.875745Z 0 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
2022-09-15T06:32:03.875746Z 0 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'
2022-09-15T06:32:03.875748Z 0 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
2022-09-15T06:32:03.875749Z 0 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
2022-09-15T06:32:03.875751Z 0 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'
2022-09-15T06:32:03.875752Z 0 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
2022-09-15T06:32:03.875754Z 0 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
2022-09-15T06:32:03.875755Z 0 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE'
2022-09-15T06:32:03.875757Z 0 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
2022-09-15T06:32:03.875758Z 0 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'
2022-09-15T06:32:03.875760Z 0 [Note] Shutting down plugin 'INNODB_FT_DELETED'
2022-09-15T06:32:03.875761Z 0 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'
2022-09-15T06:32:03.875763Z 0 [Note] Shutting down plugin 'INNODB_METRICS'
2022-09-15T06:32:03.875764Z 0 [Note] Shutting down plugin 'INNODB_TEMP_TABLE_INFO'
2022-09-15T06:32:03.875766Z 0 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS'
2022-09-15T06:32:03.875767Z 0 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
2022-09-15T06:32:03.875769Z 0 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE'
2022-09-15T06:32:03.875770Z 0 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
2022-09-15T06:32:03.875772Z 0 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'
2022-09-15T06:32:03.875773Z 0 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'
2022-09-15T06:32:03.875775Z 0 [Note] Shutting down plugin 'INNODB_CMPMEM'
2022-09-15T06:32:03.875777Z 0 [Note] Shutting down plugin 'INNODB_CMP_RESET'
2022-09-15T06:32:03.875778Z 0 [Note] Shutting down plugin 'INNODB_CMP'
2022-09-15T06:32:03.875780Z 0 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'
2022-09-15T06:32:03.875781Z 0 [Note] Shutting down plugin 'INNODB_LOCKS'
2022-09-15T06:32:03.875782Z 0 [Note] Shutting down plugin 'INNODB_TRX'
2022-09-15T06:32:03.875784Z 0 [Note] Shutting down plugin 'InnoDB'
2022-09-15T06:32:03.875854Z 0 [Note] InnoDB: FTS optimize thread exiting.
2022-09-15T06:32:03.876196Z 0 [Note] InnoDB: Starting shutdown...
2022-09-15T06:32:03.976840Z 0 [Note] InnoDB: Dumping buffer pool(s) to /usr/local/mysql/data/ib_buffer_pool
2022-09-15T06:32:03.977146Z 0 [Note] InnoDB: Buffer pool(s) dump completed at 220915 14:32:03
2022-09-15T06:32:05.488923Z 0 [Note] InnoDB: Shutdown completed; log sequence number 2980998
2022-09-15T06:32:05.490187Z 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2022-09-15T06:32:05.490231Z 0 [Note] Shutting down plugin 'MEMORY'
2022-09-15T06:32:05.490243Z 0 [Note] Shutting down plugin 'CSV'
2022-09-15T06:32:05.490246Z 0 [Note] Shutting down plugin 'sha256_password'
2022-09-15T06:32:05.490248Z 0 [Note] Shutting down plugin 'mysql_native_password'
2022-09-15T06:32:05.490337Z 0 [Note] Shutting down plugin 'binlog'
2022-09-15T06:32:05.490478Z 0 [Note] /usr/local/mysql/bin/mysqld: Shutdown complete

?發(fā)現(xiàn)關(guān)鍵字?unknown variable 未知的變量? binlog_expire_logs_seconds

?我照著視頻里面的單詞一個(gè)個(gè)敲,不是我敲錯(cuò)。嘗試尋找度娘

在mysql 8.0版本中新增了binlog_expire_logs_seconds,該參數(shù)表示binlog的失效日期單位秒。
8.0之前的版本,binlog的失效日志用expire_logs_days來配置,單位是天。

參考鏈接:mysql 8 新特性之binlog_expire_logs_seconds - 墨天輪??????

因?yàn)槲沂菍W(xué)習(xí)了8.0和5.7版本的Mysql都有在學(xué)習(xí),win端使用的是8.0 linux安裝的是5.7

所以是我mysql版本的問題導(dǎo)致。更改參數(shù)?

[mysqld]
user = mysql
port = 3306
basedir = /usr/local/mysql  
# 創(chuàng)建目錄
datadir = /usr/local/mysql/data   
# 數(shù)據(jù)庫目錄
pid-file = /usr/local/mysql/data/mysqld.pid 
# mysql進(jìn)程
log-error = /usr/local/mysql/data/mysql.err   
# 錯(cuò)誤日志
socket = /var/lib/mysql/mysql.sock
# 可以socket文件方式登錄mysql
log-bin = /usr/local/mysql/data/bin-log/mysql-bin.log
server-id = 1
#binlog_expire_logs_seconds = 600
max_binlog_size = 200M
#Disabling symbolic-links is recommended to prevent assorted security risks
symbolic-links = 0
#禁止符號(hào)鏈接以防各種安全風(fēng)險(xiǎn)
# Settings user and group are ignored when systemd is used.
# If you need to run mysqld under a different user or group,
# customize your systemd unit file for mariadb according to the
# instructions in http://fedoraproject.org/wiki/Systemd

# [mysqld_safe]

#
# include all files from the config directory
#
!includedir /etc/my.cnf.d
explicit_defaults_for_timestamp=true

再再再再次嘗試啟動(dòng)MySQL?

[root@master lib]# ps -aux | grep mysql
root      53523  0.0  0.0 108096   620 pts/1    S+   14:00   0:00 tail -f /usr/local/mysql/data/mysql.err
root      54867  0.0  0.0  11820  1612 pts/0    S    14:05   0:00 /bin/sh /usr/local/mysql/bin/mysqld_safe --datadir=/usr/local/mysql/data --pid-file=/usr/local/mysql/data/mysqld.pid
mysql     55106  1.1  2.2 1145048 176116 pts/0  Sl   14:05   0:00 /usr/local/mysql/bin/mysqld --basedir=/usr/local/mysql --datadir=/usr/local/mysql/data --plugin-dir=/usr/local/mysql/lib/plugin --user=mysql --log-error=/usr/local/mysql/data/mysql.err --pid-file=/usr/local/mysql/data/mysqld.pid --socket=/var/lib/mysql/mysql.sock --port=3306
root      55162  0.0  0.0 112816   976 pts/0    S+   14:05   0:00 grep --color=auto mysql
[root@master lib]# netstat -anptu | grep :3306
tcp6       0      0 :::3306                 :::*                    LISTEN      55106/mysqld   

嘗試登錄MySQL 發(fā)現(xiàn)又報(bào)錯(cuò):錯(cuò)誤2002 (HY000):無法通過套接字'/tmp/ MySQL連接到本地MySQL服務(wù)器

[root@master lib]# mysql -u root -p
Enter password:?
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2)

ln -s /var/lib/mysql/mysql.sock /tmp/mysql.sock #設(shè)置軟連接

the server quit without updating pid file,mysql,mysql,數(shù)據(jù)庫,服務(wù)器

mysql> show databases;
+--------------------+
| Database           |
+--------------------+
| information_schema |
| atguigudb          |
| #mysql50#bin-log   |
| mysql              |
| performance_schema |
| sys                |
| test               |
| test_u             |
+--------------------+
8 rows in set (0.00 sec)

?登錄成功?。?! 繼續(xù)繼續(xù)MySQL!??!沖文章來源地址http://www.zghlxwxcb.cn/news/detail-815756.html

到了這里,關(guān)于MySQL報(bào)錯(cuò):The server quit without updating PID file 我的解決思路和方法的文章就介紹完了。如果您還想了解更多內(nèi)容,請(qǐng)?jiān)谟疑辖撬阉鱐OY模板網(wǎng)以前的文章或繼續(xù)瀏覽下面的相關(guān)文章,希望大家以后多多支持TOY模板網(wǎng)!

本文來自互聯(lián)網(wǎng)用戶投稿,該文觀點(diǎn)僅代表作者本人,不代表本站立場(chǎng)。本站僅提供信息存儲(chǔ)空間服務(wù),不擁有所有權(quán),不承擔(dān)相關(guān)法律責(zé)任。如若轉(zhuǎn)載,請(qǐng)注明出處: 如若內(nèi)容造成侵權(quán)/違法違規(guī)/事實(shí)不符,請(qǐng)點(diǎn)擊違法舉報(bào)進(jìn)行投訴反饋,一經(jīng)查實(shí),立即刪除!

領(lǐng)支付寶紅包贊助服務(wù)器費(fèi)用

相關(guān)文章

  • mysql啟動(dòng)時(shí)報(bào)錯(cuò):Starting MySQL... ERROR! The server quit without updating PID file快速解決

    1、可能是/opt/mysql/data/數(shù)據(jù)目錄mysql用戶沒有權(quán)限(修改數(shù)據(jù)目錄的權(quán)限) 解決方法 :給予權(quán)限,執(zhí)行 “chown -R mysql.mysql /opt/mysql/data” 然后重新啟動(dòng)mysqld 2、可能進(jìn)程里已經(jīng)存在mysql進(jìn)程 解決方法:用命令“ps -ef|grep mysqld”查看是否有mysqld進(jìn)程,如果有使用“kill -9 進(jìn)程號(hào)”

    2024年02月08日
    瀏覽(94)
  • 【填坑向】MySQL常見報(bào)錯(cuò)及處理系列(ERROR! The server quit without updating PID file)

    【填坑向】MySQL常見報(bào)錯(cuò)及處理系列(ERROR! The server quit without updating PID file)

    本系列其他文章 【填坑向】MySQL常見報(bào)錯(cuò)及處理系列(Communications link failure Access denied for user ‘root‘@‘localhost‘)_AQin1012的博客-CSDN博客 翻一下大致的意思就是默認(rèn)會(huì)按照如下的順序讀取配置文件,我上面貼出的配置文件就是第一個(gè)/etc/my.cnf,但顯然目前在運(yùn)行的MySQL并不是

    2024年02月11日
    瀏覽(16)
  • mac m2停止mysql報(bào)錯(cuò):ERROR! MySQL server PID file could not be found!

    出現(xiàn)這個(gè)問題的原因有很多,我只說下我是怎么解決的。 首先看一下,你的mysql服務(wù),有沒有指定配置文件。 執(zhí)行完之后,會(huì)輸出幾個(gè)可能的目錄,你可以到各個(gè)目錄下看看有沒有my.cnf文件。如果沒有,那就需要新建一個(gè)。 進(jìn)入/etc目錄,可能需要root權(quán)限,使用如下命令切換

    2024年02月09日
    瀏覽(47)
  • 【BUG解決】sudo apt-get update 報(bào)錯(cuò) E: The repository ‘http://xxx Release‘ does not have a Release file.

    【BUG解決】sudo apt-get update 報(bào)錯(cuò) E: The repository ‘http://xxx Release‘ does not have a Release file.

    前兩天在虛擬機(jī)Vmware中安裝了Ubuntu18.04操作系統(tǒng),因?yàn)樾枰惭b其他工具。所以想著執(zhí)行命令 更新一下系統(tǒng),以便進(jìn)行安裝。結(jié)果出現(xiàn) “E: The repository ‘http://xxx Release‘ does not have a Release file.” 以及 “E: Problem executing scripts APT::Update::Post-Invoke-Success \\\'if /usr/bin/test -w /var/cache

    2023年04月10日
    瀏覽(22)
  • ERROR 1290 (HY000): The MySQL server is running with the --secure-file-priv option 解決辦法

    ERROR 1290 (HY000): The MySQL server is running with the --secure-file-priv option 解決辦法

    情景 當(dāng)我導(dǎo)入大數(shù)據(jù)量時(shí),使用 LOAD DATA INFILE 進(jìn)行導(dǎo)入,出現(xiàn)了錯(cuò)誤 ERROR 1290 (HY000): The MySQL server is running with the --secure-file-priv option so it cannot execute this statement 表明你的 MySQL 服務(wù)器啟用了 --secure-file-priv 選項(xiàng),這個(gè)選項(xiàng)限制了 MySQL 可以執(zhí)行文件操作的目錄。這通常出現(xiàn)在嘗

    2024年04月28日
    瀏覽(25)
  • ERROR 1290 (HY000): The MySQL server is running with the --secure-file-priv option so it cannot exec

    MySQL在進(jìn)行導(dǎo)出全表數(shù)據(jù)的時(shí)候提示ERROR 1290 出現(xiàn)這個(gè)問題的原因是mysql的secure_file_prive這個(gè)選項(xiàng)沒有開啟,或者這個(gè)選擇了特定的文件路徑,只有在這個(gè)文件路徑下的文件才能導(dǎo)入導(dǎo)出mysql 首先在mysql環(huán)境下查詢secure_file_priv參數(shù)。 參數(shù)secure_file_priv的值及含義如下: secure_fil

    2024年02月10日
    瀏覽(24)
  • 講解nginx.pid“ failed (2: The system cannot find the file specified

    目錄 講解 \\\"nginx.pid\\\" failed (2: The system cannot find the file specified 1. Nginx配置文件錯(cuò)誤 2. Nginx配置文件權(quán)限問題 3. Nginx啟動(dòng)失敗 解決問題 示例代碼:處理 \\\"nginx.pid\\\" failed (2: The system cannot find the file specified 在使用Nginx時(shí),你可能會(huì)遇到以下錯(cuò)誤消息之一: 這個(gè)錯(cuò)誤消息通常出現(xiàn)在啟

    2024年01月19日
    瀏覽(14)
  • Hadoop安裝MySQL報(bào)錯(cuò)The GPG keys listed for the “MySQL 5.7 Community Server“ repository are already......

    Hadoop安裝MySQL報(bào)錯(cuò)The GPG keys listed for the “MySQL 5.7 Community Server“ repository are already......

    目錄 一、報(bào)錯(cuò)描述: 二、問題分析: 三、問題解決: 四、命令運(yùn)行: 五、總結(jié)? ? ????????沒有配置正確的密鑰URL,可能是由于密鑰過期導(dǎo)致。在安裝MySQL服務(wù)之前,先導(dǎo)入正確的密鑰URL。記住是在安裝之前導(dǎo)入!??! ? ? ? ? ?下面命令2022表示年份。先導(dǎo)入正確的密

    2024年02月12日
    瀏覽(25)
  • 解決MySQL報(bào)錯(cuò):“The last packet sent successfully to the server was 0 milliseconds ago.”

    com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure?The?last?packet sent successfully?to?the server was?0?milliseconds ago. The driver has?not?received?any?packets?from?the server. 問題原因: 之所以出現(xiàn)異常,是由于數(shù)據(jù)庫回收了連接,而系統(tǒng)的緩沖池不知道,繼續(xù)使用被回收的連

    2024年02月08日
    瀏覽(27)
  • [已解決]ERROR 1290 (HY000): The MySQL server is running with the --skip-grant-tables 成功解決報(bào)錯(cuò)

    [已解決]ERROR 1290 (HY000): The MySQL server is running with the --skip-grant-tables 成功解決報(bào)錯(cuò)

    在mysql中創(chuàng)建新用戶、給數(shù)據(jù)庫授權(quán)用戶及配置服務(wù)器IP時(shí)發(fā)生的這個(gè)報(bào)錯(cuò):ERROR 1290 (HY000): The MySQL server is running with the --skip-grant-tables option so it cannot execute this statement。 報(bào)錯(cuò)說mysql服務(wù)器正在運(yùn)行不能添加,但是關(guān)閉mysql服務(wù)器重新登錄時(shí)會(huì)有這個(gè)報(bào)錯(cuò):ERROR 2002 (HY000): Can‘

    2024年04月15日
    瀏覽(21)

覺得文章有用就打賞一下文章作者

支付寶掃一掃打賞

博客贊助

微信掃一掃打賞

請(qǐng)作者喝杯咖啡吧~博客贊助

支付寶掃一掃領(lǐng)取紅包,優(yōu)惠每天領(lǐng)

二維碼1

領(lǐng)取紅包

二維碼2

領(lǐng)紅包