Atomicorp

Hi there,
I'm very new at administering a server so I am not clear on everything I am doing while running the server. However, awhile back I updated Plesk and it ruined my MYSQL. I ended up using ART to reinstall a Plesk-friendly new version of Mysql.

My question is: I see there are a number of updates in Plesk updater since I did this. Not for Plesk as a whole, but for various components. I know I can't use Plesk updater to update the entire Plesk platform, but what about for just various components of Plesk? Will it ruin the server?

Also, I'm very noob to Yum. The only time I used it was to install the ART Mysql, and I specifically only updated that one thing. The other day when I used Yum though, it looked like so many things could be upgraded. How is it supposed to be used? If I type "yum update" does it update everything that it can?

Any help or answers would be appreciated. I want to give a HUGE thank you to ART for doing the Plesk friendly MYSQL updates. It helped me out tremendously.

I see there are a number of updates in Plesk updater since I did this. Not for Plesk as a whole, but for various components. I know I can't use Plesk updater to update the entire Plesk platform,

Why not? Unless you're meaning "for the entire server", then, no it won't. It can update the Plesk version too.

but what about for just various components of Plesk?

I use the updater on mine without issue (yet).

Will it ruin the server?

Hasn't bothered mine.

The other day when I used Yum though, it looked like so many things could be upgraded. How is it supposed to be used? If I type "yum update" does it update everything that it can?

Yes. You may want to add "kernel*" to your "exclude=" line in yum.conf as updating the kernel will bork some boxes (notably those at 1&1.) Check with your provider.

Provided you're on a system that hasnt had major modifications away from the way the vendor put it together (1and1 in the previous example), its safe to run yum update/up2date -u frequently. On newer systems this is even automated to run nightly and at boot time by default.

Bruce and Scott - thanks for your replies.

The reason why I said "you can't use Plesk updater to update the entire Plesk platform" is because I remember reading, and experiencing, that if you let Plesk update itself it will reinstall MySQL too, to an older version.

Right now, my Yum subscriptions are for Plesk 7.5 and for ART. Does ART automatically check what needs to be updated?

Is using yum update better than using Plesk update? If I'm subscribed to Plesk, it will handle the Plesk updates too, yes?

Thank you for your help, both of you, it is very appreciated.

I remember reading, and experiencing, that if you let Plesk update itself it will reinstall MySQL too, to an older version

That's not been my experience, nor have I heard or read anything along that line. Not that I'm a definitive source, mind you.

my Yum subscriptions are for Plesk 7.5 and for ART. Does ART automatically check what needs to be updated?

That's a function of yum. It compares installed versions to available ones and if there's a newer one available, asks if you want it updated. I've added several other repositories to my yum.conf so that the whole system is kept shipshape. On a fresh FC3 install I did yesterday, it updated nearly 600 packages--not including when I installed Plesk with yum and the dependencies updated when it was installed.

Is using yum update better than using Plesk update?

It's not a question of which is "better" because they each do different things.

Remember, Plesk is only a nicely packaged set of programs and services that are added on to an existing server (hardware) and operating system (software). Referring a couple of notes back: It's not a "platform" in and of itself. Perhaps this is where your confusion arises.

Plesk updater will only update the two dozen or so things you see in Plesk updater. Yum will update all operating system packages (programs and services) installed on the server--generally hundreds or low thousands of packages.

Yum can also install or remove packages. For instance, say a client installs Gallery, which really needs ImageMagick. If it's not already on your server, and you have the appropriate repositores in your yum.conf, just "yum install ImageMagick" and Bob's yer uncle.

Plesk updater won't do that even if you have Gallery in the Application Vault. That doesn't make yum better or Plesk updater worse. They simply have different focuses.

I'll defer to Scott to answer the rest of your questions.

Bruce, you are very kind for giving your advice.

In Plesk, it lists my OS as this:
psa v7.5.4_build75051209.14 os_FedoraCore 2
So I see I'm running Fedora Core 2.

I currently have two servers set up for Yum:
Server: Atomic Rocket Turtle - 2 - Atomic PSA-Compatible RPMS
Server: Atomic Rocket Turtle - 2 - SW-Soft PSA 7.5 RPMS

Using those two, will I stay pretty much up-to-date (sufficiently)?

Thanks again.

Those will keep you in good shape with regard to Plesk, some essential packages it relies on, and Scott's stuff.

On my boxes, I also use the Fedora Legacy repositories http://www.fedoralegacy.org/download/ which have OS updates for FC3 and older, back to RH7.2.

An additional generally trusted repository is by Dag Wieers, whose repository is in the process of being combined with another and being renamed RPMforge. http://dag.wieers.com/home-made/apt/FAQ.php

At this point, I'd also like to advise setting up a test box. I try out all new stuff and yum-installed upgrades on my "crash-and-burn" unit first, just in case something breaks. Only when I'm satisfied that it works okay (almost all the time) do I update my production box at the hosting service.

A test box needn't be anything fancy or expensive. I spent $100 on a vintage 1999 P-III 500MHz with 256MB RAM and a 10GB disk. After installing Fedora, I install Plesk using yum and Scott's repositories. Without buying a license, Plesk lets you test using 1 each of client, domain, database, mailbox, etc., which I've found sufficient.

I also use Dag's repo on my systems, and if there are ever any issues with compatibilty, please give me a heads up and I will resolve it. Consider Dag's archive supported along side the Fedoralegacy and vendor channels.