php - Importbuddy 内部 500 服务器错误步骤 3

Question

出于测试目的，我正在尝试将网站复制到单独的域中。然而，当我运行 importbuddy.php 时，一切都很好，直到我到达第三步。第三步涉及输入您的数据库详细信息。我输入详细信息并单击“测试”，一切都会显示“通过”，然后我单击“下一步”......

等待 5 - 10 分钟后，页面会抛出 500 内部服务器错误。我尝试增加内存限制和最大执行时间，但没有成功。

我尝试备份另一个网站并将其移动到上面所述的域，它工作完美。

以下是日志:

Importing database content with ImportBuddy v4.2.15.3 (downloaded 2014-04-16T07:38:49+00:00)... Powered by BackupBuddy.

Apr 16, 2014 10:12:51 am 0.01 0.97 details Maximum PHP execution time was not modified

Apr 16, 2014 10:12:51 am 0.01 0.97 details Reported PHP execution time - Configured: 600; Original: 7200; Current: 7200

Apr 16, 2014 10:12:51 am 0.01 0.97 details Reported PHP memory limits - Configured: 512M; Original: 512M; Current: 512M

Apr 16, 2014 10:12:51 am 0.01 0.97 message Migrating .htaccess.bb_temp file...

Apr 16, 2014 10:12:51 am 0.01 0.97 message Checking .htaccess.bb_temp file.

Apr 16, 2014 10:12:51 am 0.01 0.97 message URL directory has changed. Updating from `` to /mariesa.

Apr 16, 2014 10:12:51 am 0.01 0.97 details .htaccess ^index/.php$ detected. Leaving as is.

Apr 16, 2014 10:12:51 am 0.01 0.97 message Migrated .htaccess.bb_temp file. It will be renamed back to .htaccess on the final step.

Apr 16, 2014 10:12:51 am 0.01 0.97 message Verifying database connection and settings...

Apr 16, 2014 10:12:51 am 0.01 0.97 message Database connection and settings verified. Connected to database inbc_marie.

Apr 16, 2014 10:12:51 am 0.01 0.97 details Determining SQL file location...

Apr 16, 2014 10:12:51 am 0.01 0.97 details Looking for SQL file at backupbuddy_dat.php/db_1.sql.

Apr 16, 2014 10:12:51 am 0.01 0.97 details Looking for SQL file at /usr/www/users/inbccbtvgs/mariesa/wp-content/uploads/temp_vnb9u43goi/db.sql.

Apr 16, 2014 10:12:51 am 0.01 0.97 details Looking for SQL file at /usr/www/users/inbccbtvgs/mariesa/db.sql.

Apr 16, 2014 10:12:51 am 0.01 0.97 details Looking for SQL file at /usr/www/users/inbccbtvgs/mariesa/wp-content/uploads/backupbuddy_temp/vnb9u43goi/db_1.sql.

Apr 16, 2014 10:12:51 am 0.01 0.97 details Found SQL file as /usr/www/users/inbccbtvgs/mariesa/wp-content/uploads/backupbuddy_temp/vnb9u43goi/db_1.sql.

Apr 16, 2014 10:12:51 am 0.01 1.03 details Compatibility mysqldump (if applicable) max rows per select set to 2000.

Apr 16, 2014 10:12:51 am 0.01 1.04 details Database host for dumping: dedi498.jnb1.host-h.net

Apr 16, 2014 10:12:51 am 0.01 1.04 details Loading mysqldump library.

Apr 16, 2014 10:12:51 am 0.01 1.04 details Mysql server default directories: /usr/bin/,/usr/bin/mysql/,/usr/local/bin/

Apr 16, 2014 10:12:51 am 0.01 1.04 details mysqlbuddy: Force method of 0 passed.

Apr 16, 2014 10:12:51 am 0.01 1.04 message mysqlbuddy: Method not forced. About to detect directory and available methods.

Apr 16, 2014 10:12:51 am 0.01 1.04 details mysqlbuddy: Attempting to calculate exact mysql directory.

Apr 16, 2014 10:12:51 am 0.01 1.04 details mysqlbuddy: Mysql reported its directory. Reported: /usr; Adding binary location to beginning of mysql directory list: /usr/bin/

Apr 16, 2014 10:12:51 am 0.01 1.04 details mysqldump test: Testing available mysql database dump methods.

Apr 16, 2014 10:12:51 am 0.01 1.04 details mysqldump test: exec() function exists. Testing running mysqldump via exec().

Apr 16, 2014 10:12:51 am 0.01 1.04 details mysqldump test running next.

Apr 16, 2014 10:12:51 am 0.01 1.04 details exec_dir not detected. Proceeding normally.

Apr 16, 2014 10:12:51 am 0.01 1.04 details exec() command PATH=$PATH:/usr/bin/:/usr/local/bin/:usr/local/bin:/usr/local/sbin/:/usr/sbin/:/sbin/:/usr/:/bin/; /usr/bin/mysqldump --version 2>&1 (with path definition).

Apr 16, 2014 10:12:51 am 0.02 1.05 details exec() command output: mysqldump Ver 10.13 Distrib 5.5.35, for debian-linux-gnu (i686); Exit code: 0; Exit code description: Command completed & returned normally.

Apr 16, 2014 10:12:51 am 0.02 1.05 details mysqldump test: Command appears to be accessible and returns expected response.

Apr 16, 2014 10:12:51 am 0.02 1.05 message mysqlbuddy: Detected database dump methods: commandline,php.

Apr 16, 2014 10:12:51 am 0.02 1.05 details If applicable, breaking up with max execution time 30 seconds.

Apr 16, 2014 10:12:51 am 0.02 1.05 message Restoring database dump. This may take a moment...

Apr 16, 2014 10:12:51 am 0.02 1.05 error Error #9014: Database import halted to prevent overwriting existing WordPress data. The database already contains a WordPress installation with this prefix ms_ (21 tables). Restore has been stopped to prevent overwriting existing data.

如果需要更多信息，请询问。有什么想法吗？

Answer 1

Apr 16, 2014 10:12:51 am 0.02 1.05 error Error #9014: Database import halted to prevent overwriting existing WordPress data. The database already contains a WordPress installation with this prefix ms_ (21 tables). Restore has been stopped to prevent overwriting existing data.

该表已经存在并且在此处损坏？