• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Plesk database has been adopted for MySQL-4.1 or later

thewolf

Regular Pleskian
Hi,

We've upgraded a Plesk 7.5.4 installation running on Red Hat Enterprise Linux 4 to Plesk 8.1.1 using the autoinstaller.

The upgrade went fine, but we got the following email from Plesk:
Subject: <myserver.mydomain.com> Plesk database has been adopted for MySQL-4.1 or later
Date: 20 Sep 2007 02:03:03 -0400
From: My Company NOC <[email protected]>
Reply-To: My Company NOC <[email protected]>
To: [email protected]

A database engine mysql was upgraded to version 4.1 or above. This version
fully implements the national characters support. Since a number of values
in Plesk is restricted by case-insensitive unqueness, they became
conflicting in the new conditions. To follow the unqueness requirements,
they have been modified:
The message ends there, missing the list of the actual values that have been modified according to Plesk.

How can we get that info?

Also, there was no MySQL upgrade, the server was already running MySQL 4.1 (since it comes with RHEL4), we just upgraded Plesk.

Any ideas why we got that message?

Thanks.
 
Back
Top