• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Another Plesk Update Nightmare

A

AndrewT

Guest
I was running 7.5.2 very nicely and then 7.5.3 comes out. I thought since upgrading to 7.5.2 was easy I 'll upgrade to 7.5.3.

But Got some problems - like everyone!!!

I have tried to update from the web, shell script and manually but I cannot get rid of the following error which appears when I access my plesk via web

ERROR Table 'psa.ControlVisibility' doesn't exist

What do I need to do to get this table added to the psa database?

Also can I roll this installation back?

Thanks in Advance!
 
You could copy & paste the stuff belot to a file named addcontrolvis.sql on your server.. it's just a dump of my addcontrolvis.sql from my 7.5.3 install.

PHP:
-- phpMyAdmin SQL Dump
-- version 2.6.2
-- Host: localhost
-- Generation Time: May 09, 2005 at 06:48 PM
-- Server version: 4.1.9
-- PHP Version: 4.3.10
-- 
-- Database: `psa`
-- 

-- 
-- Table structure for table `ControlVisibility`
-- 

CREATE TABLE IF NOT EXISTS `ControlVisibility` (
  `page` varchar(127) NOT NULL default '',
  `control` varchar(127) NOT NULL default '',
  `state` enum('hide','adminOnly','show') NOT NULL default 'hide',
  `control_type` enum('button','formControl') NOT NULL default 'button',
  PRIMARY KEY  (`page`,`control`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

-- 
-- Dumping data for table `ControlVisibility`
--

then you can import it like this:

PHP:
/usr/local/psa/mysql/bin/mysql -u admin -p`cat /etc/psa/.psa.shadow`
--database=psa < /path/to/addcontrolvis.sql

Hopefully that'll fix things up for you :\
 
Eureka! It works!!!

The problem was that upgrading the base package was taking an extremely long time thus causing me to think the server went and needed rebooting.

I found it was the quotachecks that are run that take a longgggg time.

But it works - thanks for your help!
 
Update problem ...

Tried via Web interface.. shell ...but nothing works.. **** with this problem...
-----
Trying to establish test connection... connected
Trying to backup MySQL database... done
MySQL databases are dumped to /usr/local/psa/var/dumps/mysql.preupgrade.dump.gz
Database integrity check failed: duplicate values of (upgrade_date) exist in table upgrade_history <-----


If some one help ...

Tia
 
Hi Spyder.. if you can save this part to a file on your server, named something like "test.sql" or whatever..

PHP:
SELECT *
FROM `upgrade_history`
LIMIT 0 , 30

And then call it from the commandline:

PHP:
www# /usr/local/psa/mysql/bin/mysql -u admin -p`cat /etc/psa/.psa.shadow` psa < ./test.sql

Anyway, it should only return one line, like this:

www# /usr/local/psa/mysql/bin/mysql -u admin -p`cat /etc/psa/.psa.shadow` psa < ./test.sql
upgrade_date version_info db_version
2005-05-09 16:32:32 7.5.2 FreeBSD 5.3 75050204.18 0752

If it returns more than one entry, you should delete one of them in SQL (phpMyAdmin really makes this easy; the data is stored in database "psa" -> table "upgrade_history" -> ... ).

Otherwise it's possible to do from the commandline too. Well, someone that knows much more about SQL could probably write a quick SQL statement to check for duplicate upgrade_date entries and delete them, but I'm not good at SQL.
 
Humm.....

here the output

===
/usr/local/psa/mysql/bin/mysql -u admin -p`cat /etc/psa/.psa.shadow`
psa < ./test.sql
upgrade_date version_info db_version
2004-09-11 00:41:31 7.1.3 FreeBSD 4.9 71040831.02 0713
2004-09-11 00:41:31 7.1.3 FreeBSD 4.9 71040831.02 0713
2004-09-24 09:58:49 7.1.3 FreeBSD 4.9 71040907.12 0713
2004-10-21 13:19:09 7.1.4 FreeBSD 4.9 71040916.21 0714
2004-11-24 09:10:50 7.1.5 FreeBSD 4.9 71041027.18 0715
2005-02-03 12:36:40 7.1.6 FreeBSD 4.9 71041125.15 0716
====


The problem is...

Like you can see in this machine I wass do other upgrades/updates... and everything is ok...

some Ideias ??

TIA
 
I've seen that on EVERY box (10) I've upgraded so far. Simply delete duplicated entries in upgrade_history table and you'll be fine ... there's quite a few duplicated entries in there on all of mine - I saw 7 duplicates for one server for every upgrade I've done since about PSA 5.0.
 
You have two of these:

2004-09-11 00:41:31 7.1.3 FreeBSD 4.9 71040831.02 0713
2004-09-11 00:41:31 7.1.3 FreeBSD 4.9 71040831.02 0713

I guess that's what the installer is crying about. Can you install phpMyAdmin and delete one of those two lines? (Or maybe someone that knows SQL syntax could write something to delete one of the two lines from the db.. I'm sorry, I dont know how to do that from the commandline).
 
Great,

Thank´s for orientatio...

Some one with SQL skills ???

Or I must try by hand .???

TIA.
 
SQL Command

Hello,

I was having this problem and found this post as the solution - Thank you!

For the record, the way to delete the duplicate records in command-line MySQL is using the LIMIT clause in the DELETE command. For example:

DELETE FROM upgrade_history WHERE upgrade_date = '2004-04-10 03:48:37' LIMIT 3;

If you have 4 records, you use LIMIT 3 to delete only 3. If you use 4 or more (in this example) you would delete all records, so be careful :p

Hope this is helpful for someone.

Cheers!

José
 
THANK´S...

With This I can delete the wrong information (the double update entrie) and go to upgrade...
 
Back
Top