Resolved Unknown: open_basedir restriction

[calu]

Sorry, the explanation why is in the video, time out issues, so this is an alternative if the Plesk import does not work.

 

[calu]

Hi there followed the video, and everything is going well until import dump of database, then this error came up, anyone knows what it means and how to fix it?

Unable to import the xxxx_xx dump:

• ERROR: ASCII '\0' appeared in the statement, but this is not allowed unless option --binary-mode is enabled and mysql is run in non-interactive mode. Set --binary-mode to 1 if ASCII '\0' is expected. Query: 'backup/'.
• program 'mysql' finished with non-zero exit code: 1
• Unable to flush stdout: Broken pipe

 

[calu]

Hi there, when trying to import dump of database, I get this error. Anyone knows what this mean?

My .gz database file is 46 mb, has it something to do with the size of db?

Unable to import the database dump:

• ERROR: ASCII '\0' appeared in the statement, but this is not allowed unless option --binary-mode is enabled and mysql is run in non-interactive mode. Set --binary-mode to 1 if ASCII '\0' is expected. Query: 'backup/'.
• program 'mysql' finished with non-zero exit code: 1
• Unable to flush stdout: Broken pipe

 

[Kaspar]

The .gz extension of the database file means it is an compressed archive. You could try to 'unzip' (unpack it) with any archive program you have on your computer (WinRar, 7-zip, ect). Then try to import the unpacked file (with .sql extension) again. I am not 100% sure this will solve the error, but it's worth a try.

 

[Peter Debik]

https://support.plesk.com/hc/en-us/articles/360003106574-Unable-to-import-MySQL-database-from-tmp-file-in-Plesk-ERROR-ASCII-0-appeared-in-the-statement

 

[Kaspar]

@Peter, that only applies to Plesk for Windows.

 

[calu]

Hi Peter, thats what I did, but I think I found out what was wrong.

In the video, it is possible to download a cPanel backup of the DB, but in my version of cPanel, only a Jetbackup is possible.

I unpacked the .gz file as suggested by Kaspar and another .gz file appeared inside some Jetbackup folders, which I was able to upload.

 

[Maarten]

I don't know if this is possible, but it might be a good idea if the developers of the Site Import extension could take a look at this case. They could use this case to improve the extension because it shouldn't be this hard to import a WordPress website using that extension.

 

[Peter Debik]

I think the issue results from the fact the the source is not cPanel, but cPanel with some extras or a Wordpress installation that carries some special settings. cPanel import should work flawlessly, but here we're talking about a database dump that is most obviously not an authentic MySQL or MariaDB dump but some special configuration or the database that shall be imported has been managed by another system. The same might be true for the files. An import is normally straight forward like pack -> transfer -> unpack, but here we are seeing issues with paths inside Wordpress. How could an import software detect this correctly? Also, as I understand it, we're currently not talking about the site import, but a manual import of a database, and that database is not an authentic MySQL or MariaDB dump, but a backup made with a third-party software.

Also, if Snap Creeks's Duplicator plugin did not do the job right, I wonder what other software could. In a lifetime I've never seen a WP installation that could not be migrated with the Duplicator plugin. I am happy to discuss this, but at the moment don't really know how to file an issue other than "there were problems".

It is a challenge.

 

[Kaspar]

@maartenv although I do feel that there is certainly room for improvement on the Site Import extension, I am not sure this topic represents a useful use case for improvement. It's more of a testament on how much of a struggle it can be to migrate a (Wordpress) website. The Site Import extension is only one of the tried methodes and has a minor part in this topic imho.

My takeaway from this topic is that there are always unique scenarios on which common methodes don't work and require a more custom/bespoke approche.

 

[calu]

Hi Peter and Kaspar, thanks for this conclusion, I think you are right, it's not the migration tool or Plesk importer, but some incompatibility between the two servers or the databases even though the source db is MySQL as well.
.
I have tried all different kinds of migration possible, but I'm back where I started, with this WP error.

Fatal error: Uncaught TypeError: call_user_func_array(): Argument #1 ($callback) must be a valid callback, function "addmetawebcapablelinks" not found or invalid function name in /var/www/vhosts/domain/httpdocs/wp-includes/class-wp-hook.php:308 Stack trace: #0 /var/www/vhosts/domain/httpdocs/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters() #1 /var/www/vhosts/domain/httpdocs/wp-includes/plugin.php(517): WP_Hook->do_action() #2 /var/www/vhosts/domain/httpdocs/wp-includes/general-template.php(3043): do_action() #3 /var/www/vhosts/domain/httpdocs/wp-content/themes/generatepress/header.php(16): wp_head() #4 /var/www/vhosts/domain/httpdocs/wp-includes/template.php(783): require_once('...') #5 /var/www/vhosts/domain/httpdocs/wp-includes/template.php(718): load_template() #6 /var/www/vhosts/domain/httpdocs/wp-includes/general-template.php(48): locate_template() #7 /var/www/vhosts/domain/httpdocs/wp-content/themes/generatepress/page.php(17): get_header() #8 /var/www/vhosts/domain/httpdocs/wp-includes/template-loader.php(106): include('...') #9 /var/www/vhosts/domain/httpdocs/wp-blog-header.php(19): require_once('...') #10 /var/www/vhosts/domain/httpdocs/index.php(17): require('...') #11 {main} thrown in /var/www/vhosts/domain/httpdocs/wp-includes/class-wp-hook.php on line 308

 

[Kaspar]

@calu what Wordpress version are you using and what PHP version is used on your cPanel server?

 

[Maarten]

I understand the struggle with importing WP or other websites using the Site import extension, but it should at least give feedback on the rotating spinner, as shown in post #34. That's not unique and could happen in other cases as well. The extension should detect that something is wrong and give helpful feedback.

Why not let the developers decide if this case can be helpful to make the extension a bit smarter?

 

[calu]

WordPress 6.1.1 PHP Version 8.1.13

 

[calu]

Hello everyone, I'm pleased to announce that I finally located the issue which was causing me all the trouble. It turned out to be as banal as a plugin, and not all the migration tools I tried.

I did of course try to deactivate all plugins before, but it didn't make any difference, so I didn't suspect it to be a plugin issue.

I created another folder and copied all the plugins to this folder except for the most important plugins.
From the rest of the plugins, I finally I located the plugin which worked fine on the source site, but not on the new installation, deleted that plugin, and the site was working again.

Thanks to @Peter Debik , @Kaspar and @maartenv for your effort and persistant help in solving this issue.

Regards
Carsten