• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Parallels Plesk Panel 9.0.0 won't upgrade to Parallels Plesk Panel 9.0.0.2

Does anyone have any idea why I'm not able to get my machine beyond Parallels Plesk Panel v9.0.0_build90081222.11? The autoinstaller tells me the latest version is already installed. Do I dare run the rpm? Do I have to have to have it up to build90081222.17 before I can run the much talked about patch? Or does the patch upgrade the machine to 1222.17?

I've had more help from other users than I get from the KB or even support. Thanks to everyone who has been responding to my questions!
 
Hi!

My Plesk is trying to tell me that 9.0.0-suse10.2.build90081117.15 is currently installed. I also can't get build90081222.17 by any method via the GUI or via console. It always reports that the most uptodate components are installed.

Does this possibly mean that for our distributions there isn't such a patch available?
Do we need to manually install the 570MB big patch from http://www.parallels.com/download/plesk/patches/. Somhow sounds weired to me.

Thanks for you help!
G
 
Hi!

My Plesk is trying to tell me that 9.0.0-suse10.2.build90081117.15 is currently installed. I also can't get build90081222.17 by any method via the GUI or via console. It always reports that the most uptodate components are installed.

Does this possibly mean that for our distributions there isn't such a patch available?
Do we need to manually install the 570MB big patch from http://www.parallels.com/download/plesk/patches/. Somhow sounds weired to me.

Thanks for you help!
G

Run a `rpm -qa | grep psa-hotfix`

The package that "upgrades" things to 9.0.0.2 looks to be "psa-hotfix4-9.0.0-9.0.0-{arch}-build90081222-xx"

Component manager doesn't show the hotfix package, just the psa package which is the package from 9.0, in your case "psa-9.0.0-suse10.2.build90081117.15"

You can do a `rpm -qa |grep psa-9` to verify.

I noticed all this after I downloaded and unpacked the hotfix. It looks like the package versions there match up with what's already installed so nothing to do. Just another glitch in Plesk that keeps thinking it needs to be updated.
 
Hi,

I've typed this in my cli

[root@vpsxxxxx ~]# rpm -qa | grep psa-hotfix
psa-hotfix3-9.0.0-9.0.0-cos5.build90081208.07
psa-hotfix4-9.0.0-9.0.0-cos5.build90081222.11
[root@vpsxxxxx ~]# rpm -qa |grep psa-9
psa-9.0.0-cos5.build90081117.17
[root@vpsxxxxx ~]#


Does this means my server is up to date now?
 
Hi,

I've typed this in my cli

[root@vpsxxxxx ~]# rpm -qa | grep psa-hotfix
psa-hotfix3-9.0.0-9.0.0-cos5.build90081208.07
psa-hotfix4-9.0.0-9.0.0-cos5.build90081222.11
[root@vpsxxxxx ~]# rpm -qa |grep psa-9
psa-9.0.0-cos5.build90081117.17
[root@vpsxxxxx ~]#


Does this means my server is up to date now?

From what I understand, yes. I'm 99% sure and would love for someone from Parallels to verify but the chances of that happening are about as good as seeing a pig fly!
 
I am concern about my mail server as i run multiple domains, how can i ceck this?
I have sent mail from my main account and its working i belive
 
Problem with mailing to mailboxes that are domain aliases

I have hotfix psa-hotfix4-9.0.0-9.0.0-fc8.build90081222.11 installed but I saw the newest build would be
psa-hotfix4-9.0.0-9.0.0-fc8.build90081222.17


The problem I have is that emails to Domain aliases won't reach the recipient.
e.g.:
Domain google.com has a domain alias gogle.com.
Mailbox [email protected] exists and can be sent to but emails to [email protected] are lost and not forwarded to [email protected].



Should I really install the whole 600 MB rpm package available from the patches/install website?
http://www.parallels.com/download/plesk/patches/

whats the command? only chmod +x and then execute it

Autoinstaller did not upgrade it to build90081222.17 but finished successfully.
 
Some components are upgraded, some not.
How to deal with this?
Running autoinstaller (command line) doesn't fix the problem.


psa9.0.0-cos5.build90081117.17
psa-drweb-configurator 9.0.0-cos5.build90081117.17
psa-manual-custom-skin-guide 9.0.0-cos5.build90081117.17
psa-api-rpc 9.0.0-cos5.build90081208.07
psa-backup-manager 9.0.0-cos5.build90081208.07
psa-migration-manager 9.0.0-cos5.build90081208.07
psa-spamassassin 9.0.0-cos5.build90081222.11
psa-qmail 1.03-cos5.build90081222.11
psa-proftpd 1.3.1-cos5.build90081117.17
courier-imap 3.0.8-cos5.build90081222.11
psa-atmail 5.3-cos5.build90081222.11

Someone correct me if I am wrong, but that looks right for a 9.0.0.2 system. The Plesk updates don't update every single package, just those which are out of date (so in when you update from 8.3 to 8.6, some of the packages will still show the old 8.3 version numbers and dates). Clearly there is no point updating components which haven't had any changes made to them. So although your main psa9 package is still 1117, you will notice some of the components are 1222 or 1208.
 
Back
Top