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

RPM upgrade Plesk -> wrong explaination in release notes ?

B

BoXie

Guest
Hi,

Just upgraded Plesk from 7.5.2 to 7.5.3 on Fedora Core 2. First time i did it myself.

The release-notes say 'first of all run /etc/init.d/psa stopall'.

I did that. But then .. when i run 'rpm -Uvh * in the 'base' directory, i get LOT's of mysql.lock error's (failed connection to database).

After some investigation that was obvious because 'psa stopall' stops MySQL.

I also couldn't install the main psa - rpm because of a failure resolving the hostname (psa stopall also stops BIND .. that's why THAT happened).

So why do the release notes say 'run /etc/init.d/psa stopall' first ... and not 'psa stop' .... ??

How do YOU guys upgrade from rpm ??

Please explain me the process.
 
Which version of mysql are you using? Did you download it from mysql.com or elsewhere?
 
The standard Fedora Core 2 MySQL .. from the official Fedora repositories ..

It's 3.23.58.

But i really wonder whether you should use 'psa stopall' before installation.

I think it should be 'psa stop' ... so that things like MySQL and BIND keep on running.

Or am i wrong?

Nevertheless ... the release-notes are pretty unclear about that .. (also unclear about what packages do have to be installed simultaneously .. and what packages can be installed afterwards .. one by one).
 
Don't worry about stopping services, Plesk upgrader will stop services as required. You need to install all RPM's in the 'base' directory simultaneously, anything else can be installed individually or collectiviely as you wish.
 
Aaah ok .. so actually i don't really HAVE TO stop anything at all ? Even if i DO NOT use the Upgrader (never trusted that one ;) .. but install with rpm's ?

I understand that the 'base' stuff must be installed simultaneously. But there was also a section about that if you use psa-bu and psa-agent .. they have to be installed simultaneously also ... so i copied those rpm's to the 'base' dir and installed them together with the others in one rpm -Uvh command.

But i wished the release-notes where a bit more simple and clear about it.

The other stuff i installed afterwards.
 
I think that's probably just to avoid dependency errors which won't actually be a problem if you upgrade later. I've installed them manually on the boxes I've upgraded so far and haven't seen any problems because of it yet. Your solution should be fine though.
 
Back
Top