Go to Qiita Advent Calendar 2024 Top
LoginSignup
mawarumarimo
@mawarumarimo (まる まる)

Are you sure you want to delete the question?

Leaving a resolved question undeleted may help others!

phpMyAdminに突然アクセスできなくなった

Q&A

Closed

PHPMySQLphpMyadminxampp

解決したいこと

数日前からxamppでphp、mySQLでプログラミングを始めた者です。
php,sqlの接続はうまくいっていましたが、突然mysqlへの接続が一切できなくなりました。

apache,mysqlともに起動していて、mysqlへの接続を伴わないページは実行できます。しかし、mysqlへの接続を書いているページはタイムアウトしてしまいます。

元通りphpMyAdminに接続し、phpでデータベースとの通信をしたいです。

●php,xampp_ver8.2.4

発生している問題・エラー

phpMyAdminへブラウザで接続した際

Fatal error: Maximum execution time of 120 seconds exceeded in C:\xampp\phpMyAdmin\libraries\classes\ErrorHandler.php on line 192

sqlへ接続していたページでのエラー


Warning: Uncaught PDOException: PDO::__construct(): Error while reading greeting packet. PID=19504 in C:\xampp\htdocs\imagePosting\dbConfig.php:6 Stack trace: #0 C:\xampp\htdocs\imagePosting\dbConfig.php(6): PDO->__construct('mysql:host=loca...', 'root') #1 C:\xampp\htdocs\imagePosting\html\index.php(36): include('C:\\xampp\\htdocs...') #2 {main} Next PDOException: SQLSTATE[HY000] [2006] MySQL server has gone away in C:\xampp\htdocs\imagePosting\dbConfig.php:6 Stack trace: #0 C:\xampp\htdocs\imagePosting\dbConfig.php(6): PDO->__construct('mysql:host=loca...', 'root') #1 C:\xampp\htdocs\imagePosting\html\index.php(36): include('C:\\xampp\\htdocs...') #2 {main} thrown in C:\xampp\htdocs\imagePosting\dbConfig.php on line 6

Fatal error: Maximum execution time of 120 seconds exceeded in C:\xampp\htdocs\imagePosting\dbConfig.php on line 8

これはxamppのコントロールパネルから見たエラーログです

2023-11-29 13:48:22 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=211] with future log sequence number 1633199
2023-11-29 13:48:22 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=348] with future log sequence number 1633199
023-11-29 13:48:22 0 [ERROR] InnoDB: Page [page id: space=0, page number=194] log sequence number 1633023 is in the future! Current system log sequence number 1632709.
2023-11-29 13:48:22 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2023-11-29 13:48:22 0 [ERROR] InnoDB: Page [page id: space=0, page number=331] log sequence number 1633023 is in the future! Current system log sequence number 1632709.
2023-11-29 13:48:22 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2023-11-29 13:48:22 0 [ERROR] InnoDB: Page [page id: space=0, page number=201] log sequence number 1633067 is in the future! Current system log sequence number 1632709.
2023-11-29 13:48:22 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2023-11-29 13:48:22 0 [ERROR] InnoDB: Page [page id: space=0, page number=338] log sequence number 1633067 is in the future! Current system log sequence number 1632709.
2023-11-29 13:48:22 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2023-11-29 13:48:22 0 [ERROR] InnoDB: Page [page id: space=0, page number=209] log sequence number 1633111 is in the future! Current system log sequence number 1632709.
2023-11-29 13:48:22 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2023-11-29 13:48:22 0 [ERROR] InnoDB: Page [page id: space=0, page number=346] log sequence number 1633111 is in the future! Current system log sequence number 1632709.
2023-11-29 13:48:22 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2023-11-29 13:48:22 0 [ERROR] InnoDB: Page [page id: space=0, page number=210] log sequence number 1633155 is in the future! Current system log sequence number 1632709.
2023-11-29 13:48:22 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2023-11-29 13:48:22 0 [ERROR] InnoDB: Page [page id: space=0, page number=347] log sequence number 1633155 is in the future! Current system log sequence number 1632709.
2023-11-29 13:48:22 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2023-11-29 13:48:22 0 [ERROR] InnoDB: Page [page id: space=0, page number=211] log sequence number 1633199 is in the future! Current system log sequence number 1632709.
2023-11-29 13:48:22 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2023-11-29 13:48:22 0 [ERROR] InnoDB: Page [page id: space=0, page number=348] log sequence number 1633199 is in the future! Current system log sequence number 1632709.
2023-11-29 13:48:22 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2023-11-29 13:48:22 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2023-11-29 13:48:22 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2023-11-29 13:48:22 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2023-11-29 13:48:22 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2023-11-29 13:48:22 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2023-11-29 13:48:22 0 [Note] InnoDB: Waiting for purge to start
2023-11-29 13:48:22 0 [Note] InnoDB: 10.4.28 started; log sequence number 1632700; transaction id 1054
2023-11-29 13:48:22 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2023-11-29 13:48:22 0 [Note] Plugin 'FEEDBACK' is disabled.
2023-11-29 13:48:22 0 [Note] Server socket created on IP: '::'.
2023-11-29 13:58:10 0 [Note] Starting MariaDB 10.4.28-MariaDB source revision c8f2e9a5c0ac5905f28b050b7df5a9ffd914b7e7 as process 61452
2023-11-29 13:58:10 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2023-11-29 13:58:10 0 [Note] InnoDB: Uses event mutexes
2023-11-29 13:58:10 0 [Note] InnoDB: Compressed tables use zlib 1.2.12
2023-11-29 13:58:10 0 [Note] InnoDB: Number of pools: 1
2023-11-29 13:58:10 0 [Note] InnoDB: Using SSE2 crc32 instructions
2023-11-29 13:58:10 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2023-11-29 13:58:10 0 [Note] InnoDB: Completed initialization of buffer pool
2023-11-29 13:58:10 0 [ERROR] InnoDB: Page [page id: space=0, page number=194] log sequence number 1633023 is in the future! Current system log sequence number 1632727.
2023-11-29 13:58:10 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2023-11-29 13:58:10 0 [ERROR] InnoDB: Page [page id: space=0, page number=331] log sequence number 1633023 is in the future! Current system log sequence number 1632727.
2023-11-29 13:58:10 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2023-11-29 13:58:10 0 [ERROR] InnoDB: Page [page id: space=0, page number=201] log sequence number 1633067 is in the future! Current system log sequence number 1632727.
2023-11-29 13:58:10 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2023-11-29 13:58:10 0 [ERROR] InnoDB: Page [page id: space=0, page number=338] log sequence number 1633067 is in the future! Current system log sequence number 1632727.
2023-11-29 13:58:10 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2023-11-29 13:58:10 0 [ERROR] InnoDB: Page [page id: space=0, page number=209] log sequence number 1633111 is in the future! Current system log sequence number 1632727.
2023-11-29 13:58:10 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2023-11-29 13:58:10 0 [ERROR] InnoDB: Page [page id: space=0, page number=346] log sequence number 1633111 is in the future! Current system log sequence number 1632727.
2023-11-29 13:58:10 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2023-11-29 13:58:10 0 [ERROR] InnoDB: Page [page id: space=0, page number=210] log sequence number 1633155 is in the future! Current system log sequence number 1632727.
2023-11-29 13:58:10 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2023-11-29 13:58:10 0 [ERROR] InnoDB: Page [page id: space=0, page number=347] log sequence number 1633155 is in the future! Current system log sequence number 1632727.
2023-11-29 13:58:10 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2023-11-29 13:58:10 0 [ERROR] InnoDB: Page [page id: space=0, page number=211] log sequence number 1633199 is in the future! Current system log sequence number 1632727.
2023-11-29 13:58:10 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2023-11-29 13:58:10 0 [ERROR] InnoDB: Page [page id: space=0, page number=348] log sequence number 1633199 is in the future! Current system log sequence number 1632727.
2023-11-29 13:58:10 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.

自分で試したこと

・mysql,apacheの再起動、pcの再起動もしましたが駄目でした。

・考えられる原因
自分では接続する直前にこのサーバー設定をいじった記憶はありませんが、別途同じネットワーク内のSynologyNASにapache,mysqlをインストールし、そちらでも一度localhostで実行したりしていました。そののちに再度pcのxamppを見たところ今回のような状況になっていました。

その際に、xamppで実行している.php等を実行したまままとめてNASへコピーしました。

0

1Answer

changkejun
@changkejun

実行しながら、DBのデータファイルをコピーしたせいでしょうかと思います。
復活のため、提示されるURLを見たほうがよいです。

11-29 13:48:22 0 [ERROR] InnoDB: Your database may be corrupt or you may 
have copied the InnoDB tablespace but not the InnoDB log files. 
Please refer to 
https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.

DBサーバは自分で頑張ろうとされていますが、ロールバックの一時ファイルの初期サイズが小さいから、断念されています。
こう見ると、コピー操作のとき、なにかサイズ大きい・時間長いDB処理をおこなっている最中かと思います。あるいは、プログラムにトランザクションのcommitを記載漏れかと思います。

2023-11-29 13:48:22 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2023-11-29 13:48:22 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2023-11-29 13:48:22 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2023-11-29 13:48:22 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2023-11-29 13:48:22 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2023-11-29 13:48:22 0 [Note] InnoDB: Waiting for purge to start
2023-11-29 13:48:22 0 [Note] InnoDB: 10.4.28 started; log sequence number 1632700; transaction id 1054
2023-11-29 13:48:22 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2023-11-29 13:48:22 0 [Note] Plugin 'FEEDBACK' is disabled.
2023-11-29 13:48:22 0 [Note] Server socket created on IP: '::'.
202
0Like

Comments

  1. @mawarumarimo

    Questioner

    お返事ありがとうございます。

    確かにhttps://mariadb.com/kb/en/innodb-recovery-modes/に詳細が載っていますね。ですが、今回は自分がプログラミング開始から数日でリカバリーモードを実行するだけの知識がないため、断念しました。せっかく教えていただいたのにすみません。

    幸いsqlを初めて数日でデータベースも作り直して構わない量だったので、phpのデータだけバックアップを取り、sqlは再インストールする形で復旧することにしました。

    次回もしまたデータベースが破損した際は今回教えていただいたページを参考にさせていただきます。

Your answer might help someone💌

LoginSign Up