• 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.

mysql bug after upgrade

K

Kinghosting

Guest
My host provider did a upgrade from mysql 3.23.54 to 4.1.15

I asked them to cause I needed some funktions that 3.x not had.

now I got this bug explained here: http://bugs.mysql.com/bug.php?id=1398.
and my provider says because I asked for the upgrade that its my ow risk and that they can not be held responsible. and if they need to rollback this instalation that I would pay 150 euro per hour!!

they also say that there is no higher version availible for plesk but I see that other people have plesk running with higer versions of mysql

I rent this server its a RedHead enterprice server

my host is e plesk dealer but I do not get the support I would like to get for the price I pay.

is there a way to upgrade or rollback my mysql version?

maybe I could upgrade mysql to 4.1.21?

could my support desk forgot something? as far as I can see they only downloaded rpms and installed them, but I am not sure.

I hope that someone can help me I have 208 domains running on that server and I can not work properly on this server with this bug (I have a cron running at the moment that fixes every minit the table that gets affected by this bug over 100 databases. but this is not realy a solution)


Thanks for the support

Dimitri Hilverda

Webmaster Kinghosting.nl
 
Back
Top