• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

10.3.1 to 11.0.9 update: bootstrapper ServiceNodes Error

twwheeler

New Pleskian
I just submitted this as a bug to Parallels, but I thought I'd include it here for anyone with the same issue:

Upgrading from Plesk 10.3.1 to 11.0.9 via either /usr/local/psa/admin/bin/autoinstaller or via the panel, everything goes OK until the bootstrapper is run, and a database error occurs:

ERROR while trying to execute SQL query, the query was: REPLACE INTO ServiceNodes (uid=0(root) gid=0(root) groups=0(root), , ) VALUES (1, 'local', 'local');

The issue is line 2286 in /opt/psa/bootstrapper/pp11.0.9-bootstrapper/bootstrapper.sh, function db_upgrade_local_service_node_1012 - the line:

db_do_if "DESC ServiceNodes" "\$1 == \"name\"" "REPLACE INTO ServiceNodes (`id`, `name`, `transport`) VALUES (1, 'local', 'local');"

The backticks in that REPLACE INTO statement are being expanded in Debian, and I would suspect other distros as well, because the string is double-quoted. This causes the `id` to be replaced with the output of the 'id' command and create an invalid SQL statement. If the backticks are removed or escaped (\`), and I rerun bootstrapper.sh with the repair option, it proceeds and finishes.

This has happened on four servers, so it's consistent across all of my installs. Strangely, when I originally tested the upgrade, this worked fine - but I suspect that it was an earlier version of 11.

I suspect that I'm not the only person with this issue, so I thought I'd report.
 
The same here, thanks for the solution

Thanks for sharing. This happened to me, too (Debian Squeeze), and your solution is good.
Regards
Michael
 
Back
Top