8.2 Upgrade Fails

[CFHCOMP]

Can we get some help.
Plesk 8.2 upgrade fails from 8.1
Now plesk will not start.

 

[JoaoCorreia]

Plesk upgrade ! Rules

**** ... I hope you have a good backup !

Here's my advice for every Plesk user.

1st - Use XEN (www.xensource.com) . I have been using it and Plesk runs very nice on virtual machines with near native performace. For two years now. This is very good for backing up full machines (with downtime) but usefull in situations like a Plesk upgrade gone bad.

2nd - Never upgrade as soon as an Update is out. This will most certain lead to bad things. Wait at least 6 months or until 8.2.1 is out. I learned this in my 4 years using Plesk.


Regards
Joao Correia

 

[DCoats]

I must say that I'm quite impressed. I have been using Plesk since 6x and have never had an upgrade complete 100% without error until now. 8.1 to 8.2 was flawless for me. Currently using FreeBSD5.5 , Plesk8.2, apache2.2.4, mysql5.0.45, and php5.2.3

CFHCOMP Can we get some help.
Plesk 8.2 upgrade fails from 8.1
Now plesk will not start.

There is no way anyone can help you without knowing what the error actually was.

 

[CFHCOMP]

I was talking about help for everyone. I have been seeing that a lot of peoples update failed and have not heard anything from some one at SWSOFT about it.

My error is plesk just will not start at startup.

If I do a
service psa start
Starting xinetd service... done
Starting named service... done
Starting mysqld service... done
Starting qmail service... done
Starting courier-imap service... done
Starting postgresql service... done
Starting psa-spamassassin service... done
Starting Plesk... failed
Starting drwebd service... failed

I have tried auto installer and manual

Any help would be apreciated.

 

[robotterror]

Originally posted by CFHCOMP
I was talking about help for everyone. I have been seeing that a lot of peoples update failed and have not heard anything from some one at SWSOFT about it.

My error is plesk just will not start at startup.

If I do a
service psa start
Starting xinetd service... done
Starting named service... done
Starting mysqld service... done
Starting qmail service... done
Starting courier-imap service... done
Starting postgresql service... done
Starting psa-spamassassin service... done
Starting Plesk... failed
Starting drwebd service... failed

I have tried auto installer and manual

Any help would be apreciated.

Well, help for everyone starts with everyone providing the details as to what the error is. In /tmp you should find a file called autoinstaller3.log. That will contain pertinent information regarding your upgrade/update to 8.2.0.

It could be anything. So, to narrow the field of options... please provide specific error details.

As a bonus, when others come looking for help with their problem they most likely will search for a phrase in an error message. This way everyone benefits. Without the details there is no way to know where to start -- unless you just post your IP address and the root password for your server for everyone to go an take a look (this would not be recommended, by the way).

 

[CFHCOMP]

I have no specific details that I can see.

The log says.
Autoinstaller 3.2.0 (build at 2007-07-05 20:25 svn rev. 86947) started at (timezone EST) Sat Jul 14 18:32:30 2007
Command line args: ./psa_installer_v3.2.0_build070705.20_os_RedHat_el4_i386

Try to find rcfile...
Autoinstaller rcfile not found.
Environment locale name is 'en_US.UTF-8'
Sources page: source=http://autoinstall.plesk.com/, target_dir=/root/swsoft
Proxy page: proxy.host=, proxy.port=0
FileFetcher new object: target_dir=/root/swsoft/, main_source_url=http://autoinstall.plesk.com/
Opsys detected as: os_name=Linux os_vendor=RedHat version=el4 arch=i686 environment=
Final opsys (with overriding) is: os_name=Linux os_vendor=RedHat version=el4 arch=i686 environment=
repository: Get brief packages info for all sources
Checking for installed packages... readSystemPackagesBrief: execute rpm -qa --queryformat 'F:system_installed_brief_%{NAME}-%{VERSION}-%{RELEASE}.rpm\nN:%{N\
AME}\nE:%{EPOCH}\nV:%{VERSION}\nL:%{RELEASE}\nA:%{ARCH}\nf:%{INSTALLTIME}\nB:%{BUILDTIME}\nX:\n'
done
Downloading the file products.inf3: Filefetcher: get file products.inf3
100% done.
Downloading the file plesk.inf3: Filefetcher: get file plesk.inf3
100% done.
Downloading the file sitebuilder.inf3: Filefetcher: get file sitebuilder.inf3
100% done.
Remove not actual releases
(update package names cache) build for Linux RedHat el4 i386 (PSA_8.2.0/plesk-8.2.0-rhel4-i386.inf3) is fit
release PLESK_8_2_0 is actual
build for Linux RedHat el4 i386 (SiteBuilder/SiteBuilder_3.0.0/sitebuilder-3.0.0-rhel4-i386.inf3) is fit
release SB_3_0_0 is actual
build for Linux RedHat el4 i386 (SiteBuilder/SiteBuilder_3.0.1/sitebuilder-3.0.1-rhel4-i386.inf3) is fit
release SB_3_0_1 is actual
build for Linux RedHat el4 i386 (SiteBuilder/SiteBuilder_3.0.2/sitebuilder-3.0.2-rhel4-i386.inf3) is fit
release SB_3_0_2 is actual
build for Linux RedHat el4 i386 (SiteBuilder/SiteBuilder_4.0.0/sitebuilder-4.0.0-rhel4-i386.inf3) is fit
release SB_4_0_0 is actual
Product page: release.prod_id=plesk, release.id=PLESK_8_2_0
Select best build of PLESK_8_2_0 for current OS
build for Linux RedHat el4 i386 (PSA_8.2.0/plesk-8.2.0-rhel4-i386.inf3) is fit
First fit build is current best: PSA_8.2.0/plesk-8.2.0-rhel4-i386.inf3
Select best build: finally choised PSA_8.2.0/plesk-8.2.0-rhel4-i386.inf3
FileFetcher new object: target_dir=/root/swsoft/, main_source_url=http://autoinstall.plesk.com/
Downloading the file PSA_8.2.0/plesk-8.2.0-rhel4-i386.inf3: Filefetcher: get file PSA_8.2.0/plesk-8.2.0-rhel4-i386.inf3
100% done.
build for Linux RedHat el4 i386 (/root/swsoft/PSA_8.2.0/plesk-8.2.0-rhel4-i386.inf3) is fit
Notice: seems up2date is configured and ready to use.
repository: Get brief packages info for all sources
Detecting installed product components.
Component base: mode up2date, installed=1183715294, available=1183715294
Component base have no older version, so keyupdate not needed
Component psa-autoinstaller: mode up2date, installed=1183642295, available=1183642295
Component asp: mode up2date, installed=1183715289, available=1183715289
Component mailman: mode up2date, installed=1183715246, available=1183715246
Component postgresql: mode up2date, installed=1177449721, available=1148333522
Component java: mode up2date, installed=1183714999, available=1183714999
Component spamassassin: mode up2date, installed=1183715290, available=1183715290
Component rblsmtpd: mode up2date, installed=1183715001, available=1183715001
Component mod_python: mode up2date, installed=1107186370, available=1107186370
Component ruby: mode up2date, installed=1183715256, available=1183715256
Component fcgi: mode up2date, installed=1160390519, available=1160390519
Component vault: mode up2date, installed=1183708774, available=1183708774
Component horde-comps: mode up2date, installed=1183715203, available=1183715203
Component docs: mode up2date, installed=1183715187, available=1183715187
Component backup-ded: mode up2date, installed=1183715253, available=1183715253
Component drweb: mode up2date, installed=1183714953, available=1183714953
Component kav: mode install, installed=0, available=1183990831
Component ppwse: mode up2date, installed=1183715223, available=1183715223
Component api: mode up2date, installed=1183714984, available=1183714984
Component sshterm: mode up2date, installed=1183714900, available=1183714900
Component pmm: mode up2date, installed=1183715235, available=1183715235
Component psa-firewall: mode up2date, installed=1183714993, available=1183714993
Component cs-gs: mode install, installed=0, available=1183714989
Component psa-vpn: mode up2date, installed=1183715179, available=1183715179
Component battlefield: mode install, installed=0, available=1183715208
Component bf2: mode install, installed=0, available=1183715250
Component psa-fileserver: mode up2date, installed=1183714978, available=1183714978
Component watchdog: mode up2date, installed=1183715232, available=1183715232
Component sitebuilder: mode install, installed=0, available=1182877783
Component sitebuilder have no older version, so keyupdate not needed
Component sb-publish: mode install, installed=0, available=1160553070
Component cf-support: mode up2date, installed=1183715251, available=1183715251
Component atis: mode up2date, installed=1167889488, available=1167889488
Component miva: mode install, installed=0, available=1183715260
Component sso: mode install, installed=0, available=1183715275
Component de-DE-locale: mode install, installed=0, available=1183701798
Component ja-JP-locale: mode install, installed=0, available=1183701814
Component de-DE-locale: mode install, installed=0, available=1183701798
Component ja-JP-locale: mode install, installed=0, available=1183701814
Component es-ES-locale: mode up2date, installed=1183701805, available=1183701805
Component ru-RU-locale: mode install, installed=0, available=1183701827
Component fr-FR-locale: mode install, installed=0, available=1183701809
Component it-IT-locale: mode install, installed=0, available=1183701812
Component zh-CN-locale: mode install, installed=0, available=1183701833
Component zh-TW-locale: mode install, installed=0, available=1183701835
Can't select component base: already up-to-date
Can't select component base: already up-to-date
Can't select component base: already up-to-date
Can't select component psa-autoinstaller: already up-to-date
Can't select component atis: already up-to-date
Can't select component es-ES-locale: already up-to-date
Filefetcher: get file PSA_8.2.0/plesk-8.2.0-rhel4-i386.inf3

 

[dasmo]

Do this:


[plesk-root]/admin/bin/httpsdctl start

It'll probably complain about the key being for 8.1.


If it complains about that, you might need to get an updated key from swsoft.

 

[dasmo]

Re: Plesk upgrade ! Rules

Originally posted by JoaoCorreia
Never upgrade as soon as an Update is out. This will most certain lead to bad things. Wait at least 6 months or until 8.2.1 is out. I learned this in my 4 years using Plesk.

If you know your way around linux, you can fix the issues plesk updates cause. Using Debian helps too.

 

[trevordurity]

hmmm, we've got the exact same issue after an 8.1.1 to 8.2 upgrade on a Startlogic VPS (FC4).

i.e.service psa start
Starting xinetd service... done
Starting named service... done
Starting mysqld service... done
Starting qmail service... done
Starting courier-imap service... done
Starting postgresql service... done
Starting psa-spamassassin service... done
Starting Plesk... failed
Starting drwebd service... failed

The reply from out hoster was that this occurs if any changes were made to the Plesk control panel before the update was made. Surely that can't be correct. Anyway, the only changes that were made were adding domains and users and configuring those.

Looking at the autoinstall logs I saw this.

mysqld (pid 3773) is running...
Trying to establish test connection... ERROR 1045 (28000): Access denied for user 'admin'@'localhost' (using password: NO)
ERROR 1045 (28000): Access denied for user 'admin'@'localhost' (using password: NO)
ERROR 1045 (28000): Access denied for user 'admin'@'localhost' (using password: NO)
ERROR 1045 (28000): Access denied for user 'admin'@'localhost' (using password: NO)

ERROR while trying to establish test connection

Aborting...

STOP psa-8.2.0-fc4.build82070706.15 upgrading AT Tue Jul 17 16:03:22 PDT 2007

OK, bad enough that that happens but how on Earth would it kill 8.1.1 if the install failed.

oh, almost forgot, we also had the error in the previous post like so

Autoinstaller 3.2.0 (build at 2007-07-05 20:25 svn rev. 86947) started at (timezone EST) Sat Jul 14 18:32:30 2007
Command line args: ./psa_installer_v3.2.0_build070705.20_os_RedHat_el4_i386

Try to find rcfile...
Autoinstaller rcfile not found.

Anyone find a workaround for this? The only option given by StartLogic was to reinstall the system in it's entirety after backing up all files.

Thanks for reading my rant

Trev

 

[dasmo]

Originally posted by trevordurity
hmmm, we've got the exact same issue after an 8.1.1 to 8.2 upgrade on a Startlogic VPS (FC4).

i.e.service psa start
Starting xinetd service... done
Starting named service... done
Starting mysqld service... done
Starting qmail service... done
Starting courier-imap service... done
Starting postgresql service... done
Starting psa-spamassassin service... done
Starting Plesk... failed
Starting drwebd service... failed

Do this:


[plesk-root(probably /opt/psa)]/admin/bin/httpsdctl start

It'll probably complain about the key being for 8.1.


If it complains about that, you might need to get an updated key from swsoft.

 

[trevordurity]

Hey Dasmo, thanks for the reply.

Unfortunately service starts but psa is still unavailable. It was in

I'm going to try this instead once our server has been completely backed up.

1) remove 'caching-nameserver' package if it is installed:
# rpm -e caching-nameserver
2) alter the database of Plesk adding the field if it is missing:
# mysql -uadmin -p`cat /etc/psa/.psa.shadow`
mysql> ALTER TABLE psa.subdomains ADD INDEX dom_id_2 (`dom_id`);
3) rename 'root' MySQL user if it exists to other name before upgrade
and rename it back to 'root' after:
mysql> UPDATE mysql.user SET user='ROOT' WHERE user='root';

then perform the following command (please correct the path if needed)
cd /root/psa/PSA_8.2.0/dist-rpm-FedoraCore-2-i386/base/
rpm -Uvh *

and then rename ROOT back to root:
mysql> UPDATE mysql.user SET user='root' WHERE user='ROOT';

Or if my customer prefers (which I hope will be the case) I'll try to revert to 8.1.1 by using the following which I spotted on another thread here.

cd /root/swsoft/PSA_8.1.1/dist-rpm-FedoraCore-4-i386/base/
rpm -U --force *.rpm

I'd prefer to go back to 8.1.1 as I don't really trust 8.2.0 anymore I think this should work but if anyone knows differently it would be great to hear from ye.

Thanks again,

Trev

 

[jerleung]

I tried to revert back to 8.1.1 but it is not quite working

--------------------------------------------------------------
error: Failed dependencies:
psa = 8.2.0 is needed by (installed) psa-migration-manager-8.2.0-fc5.build82070706.15.i586
psa-api = 8.2.0-fc5.build82070706.15 is needed by (installed) psa-migration-manager-8.2.0-fc5.build82070706.15.i586

--------------------------------------------------------------

Hope someone can help! Thanks!

 

[DCoats]

That answer seems quite simple...

psa = 8.2.0 is needed by (installed) psa-migration-manager-8.2.0-fc5.build82070706.15.i586

remove psa-migration-manager-8.2.0-fc5.build82070706.15.i586
and

psa-api = 8.2.0-fc5.build82070706.15 is needed by (installed) psa-migration-manager-8.2.0-fc5.build82070706.15.i586

so remove psa-migration-manager-8.2.0-fc5.build82070706.15.i586

at that point your 8.1.1 installer should be happy to install the correct deps.

 

[adspace]

can not file the file to remove

I get the same error and try to locate the files in the post to be removed

quote
That answer seems quite simple...

quote: psa = 8.2.0 is needed by (installed) psa-migration-manager-8.2.0-fc5.build82070706.15.i586


remove psa-migration-manager-8.2.0-fc5.build82070706.15.i586
and

quote: psa-api = 8.2.0-fc5.build82070706.15 is needed by (installed) psa-migration-manager-8.2.0-fc5.build82070706.15.i586


so remove psa-migration-manager-8.2.0-fc5.build82070706.15.i586

at that point your 8.1.1 installer should be happy to install the correct deps.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Here is the error when I try to rollback to 8.1.1

[root@buy4less-hosting base]# rpm -U --force *.rpm
/etc/selinux/targeted/contexts/files/file_contexts: Multiple same specifications for /usr/local/sitebuilder/tmp(/.*)?.
error: Failed dependencies:
psa-security = 8.2 is needed by (installed) cs-gs-2.0.0-fc6.build82070706.15.i586
psa-security = 8.2 is needed by (installed) psa-watchdog-2.0.2-fc6.build82070706.15.i586
psa-security = 8.2 is needed by (installed) psa-vpn-2.0.1-fc6.build82070706.15.i586
psa-security = 8.2 is needed by (installed) psa-bf1942-1.0.0-fc6.build82070706.15.i586
psa-security = 8.2 is needed by (installed) psa-fileserver-1.0.0-fc6.build82070706.15.i586
psa-security = 8.2 is needed by (installed) psa-firewall-1.0.1-fc6.build82070706.15.i586
psa-security = 8.2 is needed by (installed) psa-bf2-1.0.0-fc6.build82070706.15.i586
psa = 8.2.0 is needed by (installed) psa-migration-manager-8.2.0-fc6.build82070706.15.i586
psa = 8.2.0 is needed by (installed) psa-backup-manager-8.2.0-fc6.build82070706.15.i586
psa = 8.2.0 is needed by (installed) psa-api-rpc-8.2.0-fc6.build82070706.15.noarch
psa >= 8.2.0 is needed by (installed) cs-gs-2.0.0-fc6.build82070706.15.i586
psa >= 8.2.0 is needed by (installed) psa-watchdog-2.0.2-fc6.build82070706.15.i586
psa >= 8.2.0 is needed by (installed) psa-vpn-2.0.1-fc6.build82070706.15.i586
psa = 8.2.0 is needed by (installed) psa-manual-custom-skin-guide-8.2.0-fc6.build82070706.15.noarch
psa >= 8.2.0 is needed by (installed) psa-bf1942-1.0.0-fc6.build82070706.15.i586
psa >= 8.2.0 is needed by (installed) psa-fileserver-1.0.0-fc6.build82070706.15.i586
psa >= 8.2.0 is needed by (installed) psa-firewall-1.0.1-fc6.build82070706.15.i586
psa >= 8.2.0 is needed by (installed) psa-bf2-1.0.0-fc6.build82070706.15.i586
psa = 8.2.0 is needed by (installed) psa-updates-8.2.0-fc6.build82070807.17.noarch
psa >= 8.2.0 is needed by (installed) psa-tomcat-configurator-8.2.0-fc6.build82070706.15.noarch
psa >= 8.2 is needed by (installed) Drupal-4.6.3-82039.noarch
psa >= 8.2 is needed by (installed) Mambo-4.6.2-82003.noarch
psa >= 8.2 is needed by (installed) PHProjekt-5.0-82038.noarch
psa >= 8.2 is needed by (installed) PostNuke-0.761a-82048.noarch
psa >= 8.2 is needed by (installed) WebCalendar-1.0-82041.noarch
psa >= 8.2 is needed by (installed) anyinventory-2.0-82018.noarch
psa >= 8.2 is needed by (installed) brim-2.0.0-82023.noarch
psa >= 8.2 is needed by (installed) eGroupWare-1.2.104-82041.noarch
psa >= 8.2 is needed by (installed) joomla-1.0.12-82031.noarch
psa >= 8.2 is needed by (installed) mantis-1.0.6-82019.noarch
psa >= 8.2 is needed by (installed) mediawiki-1.8.2-82032.noarch
psa >= 8.2 is needed by (installed) moodle-1.8-82022.noarch
psa >= 8.2 is needed by (installed) myorgbook-2.8-82019.noarch
psa >= 8.2 is needed by (installed) noahclass-1.3-82048.noarch
psa >= 8.2 is needed by (installed) osCommerce-2.2ms2-82050.noarch
psa >= 8.2 is needed by (installed) phpAds-2.0.8-82029.noarch
psa >= 8.2 is needed by (installed) phpBB-2.0.22-82016.noarch
psa >= 8.2 is needed by (installed) phpmyvisites-2.3-82017.noarch
psa >= 8.2 is needed by (installed) serendipity-1.1.2-82022.noarch
psa >= 8.2 is needed by (installed) smf-1.1.2-82025.noarch
psa >= 8.2 is needed by (installed) tikiwiki-1.9.7-82029.noarch
psa >= 8.2 is needed by (installed) xoops-2.2-82041.noarch
psa >= 8.2.0 is needed by (installed) SSHTerm-0.2.2-fc6.build82070706.15.noarch
psa >= 8.2 is needed by (installed) psa-sbm3-4.0-46.noarch
psa >= 8.2.0 is needed by (installed) psa-miva-8.2.0-fc6.build82070706.15.i586
psa-api = 8.2.0-fc6.build82070706.15 is needed by (installed) psa-migration-manager-8.2.0-fc6.build82070706.15.i586
psa-api = 8.2.0-fc6.build82070706.15 is needed by (installed) psa-api-rpc-8.2.0-fc6.build82070706.15.noarch
psa-hotfix3 = 8.2.0 is needed by (installed) psa-updates-8.2.0-fc6.build82070807.17.noarch
psa-locale-base-en-US >= 8.2.0-fc6.build82070807.17 is needed by (installed) psa-updates-8.2.0-fc6.build82070807.17.noarch
[root@buy4less-hosting base]#

Thanks in advance for your help in this matter.

AdSpace

 

[DCoats]

Why are you so intent on rolling back? Just get 8.2 to finish successfully. What is the error in that case?

 

[Group One Sales]

8.2 Fails

I too have tried upgrading from 8.1.1 to 8.2 and now I cannot get into server to add new domains and cpanel no longer is accessible.

I too, have repeatedly contacted SWSoft and always told the same story... pay us and we will look at it. They are accepting no responsibility for this.

I have contacted my hosting company and they tell me either I have to fix it or they will move it to a new VPS. But they will still use Plesk and I am not sure if Plesk does not support or defend their products that Plesk is a good choice.

Anyone know how to fix this for a novice person? The error I am getting after trying the auto update is:

Service is not available now, probably your Plesk is misconfigured.
Contact Your provider for details.

Internal Plesk error occurred: MySQL query failed: Unknown column 'uid' in 'field list'


Any help would be appreciated.
Thanks
Dave

 

[tiramisu]

Hi Dave,

looks like your db was not upgraded properly
did you try manual upgrade with packages with --force option,

also try to check it in your mysql db with
mysql -uadmin -p'password of plesk admin'

check tables and their columns, i suppose there is no such one.

 

[Group One Sales]

I do not know how to do all of that as I am a novice. I know I clicked on auto update feature and all of this happened. I cannot log in to DB on server as I get this same error.

Is there a way to login to DB or to fix this without?

Thanks
Dave

 

[phoenixisp]

I had the same problem. Log into mysql and do:

mysql> ALTER TABLE clients ADD uid VARCHAR(36);

This thread is all about that uid error:

http://forum.swsoft.com/showthread.php?s=&threadid=45729&highlight=Unknown+column+uid+in+field+list

 

[Group One Sales]

Thank you so much. I need to find out how to log in to MYSql but I can find out how and thank you so much. I usually log in using the server link but because of this error, I am not able to log in that way. But I will figure out how and do this. I want to thank you so much for responding.

Plesk aka SWSoft is not so helpful on this but I finally got someone there who said they would "look into it"

But for now, I hope this is the issue and I will figure out how to get into the mysql. Thanks again

Dave