Installation/upgrade success stories.

[IgorG]

Guys,

According to my investigation the main problem of installation/upgrade is problem with different unresolved dependences. It is caused by absolutely different reasons and it is really annoyed our clients who wants to install or upgrade Plesk and can't do it due to these dependences problems.

Therefore I have created this thread for gathering all your installation 'success stories'. I need to know when and with which conditions Plesk can be installed without any dependences problems.
Please share your experience here. For example, you have installed fresh Ubuntu or CentOS and you have not started yum or apt-get for updating system and after that you run Plesk installation and it goes fine. Or vice versa. Or something else.

Please describe your conditions and details for success installation/upgrade here. It will help us make Plesk better.
Thank you very much.

 

[atomicturtle]

Test Case #1: Fully updated CentOS, and the autoinstaller (Unsuccessful)
1) CentOS 5 i386, all updates applied (yum upgrade)
2) run autoinstaller, which fails on
No suitable solutions were found for the "bind >= 9.2.1" dependency.
inf file is attempting to install: bind-9.3.6-4.P1.el5_4.1.i386 which no longer exists,
latest is now: bind-9.3.6-4.P1.el5_4.2.i386

Test Case #2: Fully updated CentOS, installing plesk through yum (Successful)
1) (reverted to clean image) CentOS 5 i386, all updates applied
2) Add plesk repo
3) yum install psa*

The problem is the hardcoded dependency version in the .inf file in case #1, which might be my fault.... When I prototyped the original autoinstaller I used hard coded version numbers in there Anyway, a solution would be to drop all version information completely in inf files and reference only the named packages (rpm --queryformat=%{name} <packagename>) to pass on to something external for dependency resolution (yum, apt, etc). For conditions where a conflict would occur between two packages, you could either use Conflicts: tags or Requires: to force a version requirement. For example, Conflicts: bind-chroot in the psa rpm, or Requires: bind >= 9.2.1

 

[IgorG]

atomicturtle,

Thank you very much for your detailed description. It is very valuable information for us. It will be forwarded to developers.

I hope that anybody else will share installation/upgrade experience with different OSes.

 

[SacAutos]

Ironically, I just posted a note with a similar problem. Fresh install of CentOS 5.4, ran all the system updates. Plesk won't install. Grrr....

 

[fabrizioi]

Test case: Centos 5.4 32bit
From Plesk 8.6 to plesk 9.3.

My upgrade is ok. (was made yesterday night)

But I haven't made the upgrade personally. My provider is a parallels partner, so the upgrade was made by my provider with collaboration of parallels team.

It seem to work very well, no errors at the present day.

Anyway there are many point that remain strange (FTP over SSL , horde mail etc...) but there is not the correct thread to speak about it.

Sorry for my english

Bye

 

[nedry]

Test Case #1: CentOS 5.4 x86_64
1) Install CentOS 5.4 (core and base)
2) yum upgrade
3) Install Plesk 9.3 using parallels_installer
failure

Test Case #2: CentOS 5.4 x86_64
1) Install CentOS 5.4 (core and base)
2) Install Plesk 9.3 using parallels_installer
3) yum upgrade
success

 

[Michael MacDonald]

Unfortunately at this writing, I don't have specific examples of either a failed upgrade or failed installation. This thread seems to ask for success stories. I have some of those. Of more interest to me are the installation/upgrade failures. In sum total, I have had for more failures or - 'partial successes' if I was an optimist . During the years I have worked with Plesk my single biggest complaint is the rate of failure during an upgrade.

I am certainly interested in helping improve the product.

 

[Paul Chung]

What should I do for this error?

Hi,

I have downloaded plesk panel installation (rpm) file:

wget http://download1.parallels.com/Plesk/PPP9/CentOS5/psa-9.5.1-cos5.build95100413.19.x86_64.rpm.tar.gz .

and tried to install by

yum install psa*

And got the error below:

No package psa-9.5.1-cos5.build95100413.19.x86_64.rpm.tar.gz available.
Nothing to do

It seems like that I need to let the program know where to look, because I have the exact file in the directory but the yum doesn't look the directory where I am. Any idea how to solve this?

Thank you.

 

[Paul Chung]

Hi,

I have tried to install Plesk by following and got an error. Can you help me to resolve, please?

1) Get the file:
wget http://download1.parallels.com/Plesk/PPP9/CentOS5/psa-9.5.1-cos5.build95100413.19.x86_64.rpm.tar.gz .

2) Install:
yum install psa*

Error Message:
No package psa-9.5.1-cos5.build95100413.19.x86_64.rpm.tar.gz available.
Nothing to do

Thank you!!

 

[IgorG]

Hi,

I have tried to install Plesk by following and got an error. Can you help me to resolve, please?

1) Get the file:
wget http://download1.parallels.com/Plesk/PPP9/CentOS5/psa-9.5.1-cos5.build95100413.19.x86_64.rpm.tar.gz .

2) Install:
yum install psa*

Error Message:
No package psa-9.5.1-cos5.build95100413.19.x86_64.rpm.tar.gz available.
Nothing to do

Thank you!!

Did you unpack downloaded archive package before installation? And why you do not use autoinstaller instead?

 

[MauroV]

I installed Debian 5.0.8, I ran the installation of plesk 9.5.4 by the book but the error messages are many: "ERROR: autoinstaller: Error in execution of DEBIAN_FRONTEND = noninteractive"and the software is not installed .. . how can I fix it?

 

[dheemH]

Prohibit users to send email to another domain.

Hi all,

I am new to this forum as well as to plesk.

I installed parallel plesk 9.3x in my cent OS server. Here I have few equations.

1. how can I deny email accounts to send mails to another domain.

e.g- [email protected] should not send any mails to [email protected] or
[email protected] should not send any mails to [email protected]

How can I make these setting using parallel plesk / SSH terminal

Please I need your help

sorry for my English

 

[Tearde]

I don't have specific examples of either a failed upgrade or failed installation. This thread seems to ask for success stories. I have some of those. Of more interest to me are the installation/upgrade failures. In sum total, I have had for more failures or - 'partial successes' if I was an optimist .

http://www.trustedlocksmith-baltimore.com/

 

[DanPad]

Hello,

this is a pretty delicate matter, as my upgrade attempt was a real disaster.
I was trying to upgrade a 9.5 Plesk Server, and the updater told me to remove the packet php53.x86_64 0:5.3.3-1.el5_7.6

I ran yum remove php53.x86_64 0:5.3.3-1.el5_7.6, and that erased nearly every dependency!
Following all dependencies yum removed:

Removed:
php53.x86_64 0:5.3.3-1.el5_7.6

Dependency Removed:
PPWSE.x86_64 0:1.1-cos5.build95101209.08
plesk-billing.noarch 0:6.0.4-20090625.11
psa.x86_64 0:9.5.4-cos5.build95101209.08
psa-api-rpc.noarch 0:9.5.4-cos5.build95110630.14
psa-atmail.noarch 1:1.02-cos5.build95101209.08
psa-awstats-configurator.noarch 0:1.0.0-cos5.build95101209.08
psa-backup-manager.x86_64 0:9.5.4-cos5.build95110630.14
psa-firewall.x86_64 0:1.0.1-cos5.build95101209.08
psa-horde.noarch 0:3.3.6-cos5.build95101209.08
psa-hotfix1-9.5.4.x86_64 0:9.5.4-cos5.build95110630.14
psa-imp.noarch 0:4.3.6-cos5.build95100504.10
psa-ingo.noarch 0:1.2.3-cos5.build95101209.08
psa-kav.i386 0:1.0.0-cos5.build95101209.08
psa-kronolith.noarch 0:2.3.3-cos5.build95101209.08
psa-libpam-plesk.x86_64 0:9.5.4-cos5.build95101209.08
psa-locale-de-DE.noarch 0:9.5.4-2010110115
psa-locale-es-ES.noarch 0:9.5.4-2010110115
psa-locale-fr-FR.noarch 0:9.5.4-2010110115
psa-locale-it-IT.noarch 0:9.5.4-2010110115
psa-locale-nl-NL.noarch 0:9.5.4-2010110115
psa-migration-agents.x86_64 0:9.5.4-cos5.build95101209.08
psa-migration-manager.x86_64 0:9.5.4-cos5.build95110630.14
psa-mimp.noarch 0:1.1.3-cos5.build95101209.08
psa-mnemo.noarch 0:2.2.3-cos5.build95101209.08
psa-passwd.noarch 0:3.1.2-cos5.build95101209.08
psa-php53-configurator.noarch 0:1.5.3-cos5.build95110708.13
psa-sbm3.noarch 0:5.0-36
psa-spamassassin.x86_64 0:9.5.4-cos5.build95101209.08
psa-turba.noarch 0:2.3.3-cos5.build95101209.08
psa-updates.noarch 0:9.5.4-cos5.build95110630.14
psa-vpn.x86_64 0:2.0.1-cos5.build95101209.08
psa-watchdog.x86_64 0:2.0.3-cos5.build95101209.08
sb-publish.noarch 0:3.0.1-200705230938

What yum repository can I use to reinstall the previous packets?

Are there other ways to reinstall Plesk to upgrade the software using SSH, hoping that this will reinstall the dependencies without causing data loss?

I have another server with the same Plesk version (9.5): is it possible to copy the dependencies from the other Plesk server to the damaged one?

Your help is very much appreciated.
Thanks in advance for your help!

*EDIT


I installed the atomicorp plesk repository, and ran:
yum install PPWSE.x86_64 plesk-billing.noarch psa.x86_64psa-api-rpc.noarchpsa-atmail.noarch psa-awstats-configurator.noarch psa-backup-manager.x86_64 psa-firewall.x86_64 psa-horde.noarchpsa-hotfix1-9.5.4.x86_64psa-imp.noarch psa-ingo.noarchpsa-kav.i386 psa-kronolith.noarchpsa-libpam-plesk.x86_64 psa-locale-de-DE.noarchpsa-locale-es-ES.noarch psa-locale-fr-FR.noarch psa-locale-it-IT.noarch psa-locale-nl-NL.noarch psa-migration-agents.x86_64psa-migration-manager.x86_64 psa-mimp.noarch psa-mnemo.noarch psa-passwd.noarch psa-php53-configurator.noarch psa-sbm3.noarch psa-spamassassin.x86_64psa-turba.noarch psa-updates.noarchpsa-vpn.x86_64psa-watchdog.x86_64 sb-publish.noarch

Unfourtunately it installed only a few packages, many were not touched.

As I was trying to start Plesk, etc/init.d/psa does not exist any more, and doing yum install psa --skip-broken or yum install plesk-core --skip-broken does not work due to dependencies errors.

Is there a secure way to reinstall/upgrade the entire plesk package using SSH without losing any data? (mail, domains, etc..) It looks like the only solution.


Thanks for you help, it is greatly appreciated.

 

[Sarteck]

I'm unsure if this should go here or not.

We have a VPS running CentOS 5.3, with PHP version 5.1.6 on Plesk version 9.5.4 (Build CentOS 5 95110630.14 if it matters).

The customer wished to upgrade to PHP 5.4.

I read and attempted the instructions here: http://kb.parallels.com/en/115833 (instructions from PHP 5.2 to 5.4.)

Got the following error:

mysql-5.5.34-1.el5.remi.x86_64 from remi has depsolving problems
  --> mysql conflicts with mysql
mysql-devel-5.5.34-1.el5.remi.x86_64 from remi has depsolving problems
  --> mysql-devel conflicts with mysql-devel
Error: mysql conflicts with mysql
Error: mysql-devel conflicts with mysql-devel

Googled a bit. I then edited /etc/yum.repos.d/atomic.repo to disable the Atomic repo (figuring the MySQL from Remi was having a fit with the MySQL from Atomic).

This solved my issue.

THought I would share here in case anyone else had a similar issue. (Maybe you guys can include some kind of note on the KB for people upgrading from 5.1.6?)

Also figures I would ask, should I now re-enable the Atomic repo, or make any other adjustments?


EDIT:
I should note that, after performing the above, your MySQL seems to get upgraded as well. You will have to run the following command in order for it to get everything kosher:

mysql_upgrade -uadmin -p`< /etc/psa/.psa.shadow`

(Please note that on Plesk versions above 9.5, you can't just cat out the password from that .psa.shadow file.)