使用 XAMPP 在 phpmyadmin 上访问被拒绝
Access denied on phpmyadmin using XAMPP
当我尝试导航到此 URL http:///localhost/phpmyadmin/（使用 XAMPP）时，我得到 Access denied!。
这件事发生在今天。昨天它运行良好，从那以后我没有更改 xampp 文件夹中的任何内容。
下面是我的 mysq.log 文件输出。
2022-03-21 15:39:35 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2022-03-21 15:39:35 0 [Note] InnoDB: Uses event mutexes
2022-03-21 15:39:35 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2022-03-21 15:39:35 0 [Note] InnoDB: Number of pools: 1
2022-03-21 15:39:35 0 [Note] InnoDB: Using SSE2 crc32 instructions
2022-03-21 15:39:35 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2022-03-21 15:39:35 0 [Note] InnoDB: Completed initialization of buffer pool
2022-03-21 15:39:39 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2022-03-21 15:39:39 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2022-03-21 15:39:39 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2022-03-21 15:39:39 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2022-03-21 15:39:39 0 [Note] InnoDB: Waiting for purge to start
2022-03-21 15:39:39 2 [ERROR] InnoDB: Page [page id: space=647, page number=1] log sequence number 3470890319 is in the future! Current system log sequence number 598292042.
2022-03-21 15:39:39 2 [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.
2022-03-21 15:39:39 2 [ERROR] InnoDB: Page [page id: space=615, page number=1] log sequence number 3339553304 is in the future! Current system log sequence number 598292042.
2022-03-21 15:39:39 2 [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.
2022-03-21 15:39:39 4 [ERROR] InnoDB: Page [page id: space=618, page number=0] log sequence number 3462892962 is in the future! Current system log sequence number 598292042.
2022-03-21 15:39:39 1 [ERROR] InnoDB: Page [page id: space=579, page number=1] log sequence number 3262714642 is in the future! Current system log sequence number 598292042.
2022-03-21 15:39:39 4 [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.
2022-03-21 15:39:39 1 [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.
2022-03-21 15:39:39 4 [ERROR] InnoDB: Page [page id: space=618, page number=1] log sequence number 3462891605 is in the future! Current system log sequence number 598292042.
2022-03-21 15:39:39 4 [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.
2022-03-21 15:39:39 1 [ERROR] InnoDB: Page [page id: space=616, page number=1] log sequence number 3426045456 is in the future! Current system log sequence number 598292042.
2022-03-21 15:39:39 1 [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.
2022-03-21 15:39:39 0 [Note] InnoDB: 10.4.14 started; log sequence number 598292033; transaction id 2595064
2022-03-21 15:39:39 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2022-03-21 15:39:39 0 [Note] Plugin 'FEEDBACK' is disabled.
2022-03-21 15:39:39 0 [Note] InnoDB: Buffer pool(s) load completed at 220321 15:39:39
2022-03-21 15:39:39 0 [Note] Server socket created on IP: '::'.
下面是我的 phpmyadmin 用户界面错误。
我不确定这个问题，可能由于多种原因而发生。但我想建议你 -
- 单击 MySQL 旁边的 Xammp 控制面板中的配置。
- 编辑my.ini文件
- skip-grant-tables这行必须写在[mysqld]之后。
- 将port=3306更改为port=3307
- 打开 Xammp 文件夹 -> PhpMyAdmin。您将在 phpMyAdmin 文件夹中看到 config.inc.php 文件。在此文件中，找到 $cfg['Servers'][$i]['host'] = '127.0.0.1';
并将其更改为 $cfg['Servers'][$i]['host'] = 'localhost:3307';
保存这些更改。可以找到端口号如下：打开Xammp控制面板->config->服务端口设置->mySql.
现在您将能够访问 Phpmyadmin。
我解决了问题。
我做了什么：
第 1 步：我已将 xampp/mysql/data 中的所有文件复制到备份文件夹（只需在桌面上创建一个文件夹并将文件放在那里）
第 2 步：然后我卸载了 XAMPP，然后重新安装（最新版本，我的版本我认为它是很久以前的 - 我想 - ）
第 3 步：之后，我将备份文件夹中名为 ibdata1 的文件复制到 xampp/mysql/data，并且我还复制了包含我的数据库名称的文件夹（从备份从步骤 1) 到 xampp/mysql/data
的文件夹
此外，我阅读了关于以下问题的第一个 post：来自@Senthilnadhan Ramasamy 的 MySql stops unexpectedly
我前段时间做了 2-3 次，然后它不再工作了，就像今天一样，所以我不得不重新安装并执行上述所有步骤。
当我尝试导航到此 URL http:///localhost/phpmyadmin/（使用 XAMPP）时，我得到 Access denied!。
这件事发生在今天。昨天它运行良好，从那以后我没有更改 xampp 文件夹中的任何内容。
下面是我的 mysq.log 文件输出。
2022-03-21 15:39:35 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2022-03-21 15:39:35 0 [Note] InnoDB: Uses event mutexes
2022-03-21 15:39:35 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2022-03-21 15:39:35 0 [Note] InnoDB: Number of pools: 1
2022-03-21 15:39:35 0 [Note] InnoDB: Using SSE2 crc32 instructions
2022-03-21 15:39:35 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2022-03-21 15:39:35 0 [Note] InnoDB: Completed initialization of buffer pool
2022-03-21 15:39:39 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2022-03-21 15:39:39 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2022-03-21 15:39:39 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2022-03-21 15:39:39 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2022-03-21 15:39:39 0 [Note] InnoDB: Waiting for purge to start
2022-03-21 15:39:39 2 [ERROR] InnoDB: Page [page id: space=647, page number=1] log sequence number 3470890319 is in the future! Current system log sequence number 598292042.
2022-03-21 15:39:39 2 [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.
2022-03-21 15:39:39 2 [ERROR] InnoDB: Page [page id: space=615, page number=1] log sequence number 3339553304 is in the future! Current system log sequence number 598292042.
2022-03-21 15:39:39 2 [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.
2022-03-21 15:39:39 4 [ERROR] InnoDB: Page [page id: space=618, page number=0] log sequence number 3462892962 is in the future! Current system log sequence number 598292042.
2022-03-21 15:39:39 1 [ERROR] InnoDB: Page [page id: space=579, page number=1] log sequence number 3262714642 is in the future! Current system log sequence number 598292042.
2022-03-21 15:39:39 4 [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.
2022-03-21 15:39:39 1 [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.
2022-03-21 15:39:39 4 [ERROR] InnoDB: Page [page id: space=618, page number=1] log sequence number 3462891605 is in the future! Current system log sequence number 598292042.
2022-03-21 15:39:39 4 [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.
2022-03-21 15:39:39 1 [ERROR] InnoDB: Page [page id: space=616, page number=1] log sequence number 3426045456 is in the future! Current system log sequence number 598292042.
2022-03-21 15:39:39 1 [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.
2022-03-21 15:39:39 0 [Note] InnoDB: 10.4.14 started; log sequence number 598292033; transaction id 2595064
2022-03-21 15:39:39 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2022-03-21 15:39:39 0 [Note] Plugin 'FEEDBACK' is disabled.
2022-03-21 15:39:39 0 [Note] InnoDB: Buffer pool(s) load completed at 220321 15:39:39
2022-03-21 15:39:39 0 [Note] Server socket created on IP: '::'.
下面是我的 phpmyadmin 用户界面错误。
我不确定这个问题，可能由于多种原因而发生。但我想建议你 -
- 单击 MySQL 旁边的 Xammp 控制面板中的配置。
- 编辑my.ini文件
- skip-grant-tables这行必须写在[mysqld]之后。
- 将port=3306更改为port=3307
- 打开 Xammp 文件夹 -> PhpMyAdmin。您将在 phpMyAdmin 文件夹中看到 config.inc.php 文件。在此文件中，找到 $cfg['Servers'][$i]['host'] = '127.0.0.1'; 并将其更改为 $cfg['Servers'][$i]['host'] = 'localhost:3307';
保存这些更改。可以找到端口号如下：打开Xammp控制面板->config->服务端口设置->mySql.
现在您将能够访问 Phpmyadmin。
我解决了问题。
我做了什么：
第 1 步：我已将 xampp/mysql/data 中的所有文件复制到备份文件夹（只需在桌面上创建一个文件夹并将文件放在那里）
第 2 步：然后我卸载了 XAMPP，然后重新安装（最新版本，我的版本我认为它是很久以前的 - 我想 - ）
第 3 步：之后，我将备份文件夹中名为 ibdata1 的文件复制到 xampp/mysql/data，并且我还复制了包含我的数据库名称的文件夹（从备份从步骤 1) 到 xampp/mysql/data
此外，我阅读了关于以下问题的第一个 post：来自@Senthilnadhan Ramasamy 的 MySql stops unexpectedly 我前段时间做了 2-3 次，然后它不再工作了，就像今天一样，所以我不得不重新安装并执行上述所有步骤。