Atomicorp

Hi,

I've just got a 1and1 VPS and decided to follow the instructions here to update php - http://www.atomicorp.com/wiki/index.php/PHP

It all went fine and everything is running fine apart from one thing, when trying to start the psa service i get this message

Operation start with the VPS(s) VEID58580026 service "psa" is finished with errors: #703 Can not start/stop/restart service: service "psa" status is not "running" after command "start".

The other services all start fine though. Does anyone know why this might be?

If i run rpm -q psa i get this back: psa-9.0.1-cos5.build90090127.18

Thank you!!

Remember that the Plesk apache or lighttpd is different to the client apache, so a php update, no matter how badly it goes wrong, should not affect plesk itself.

So could it be that other components were updated at the same time? For example mod_ssl if you use Centos 5? If so, it might be that you are running into the bug where Plesk 9.5 at least, and maybe 9.x, would not start with it installed?

If so then there's a hotfix available to solve it.

Take a look in /var/log/messages and also in the https log file somewhere in /usr/local/psa/admin to see if there's something obvious mentioned.

But this is all just a guess/shot in the dark. Sorry if it is nothing to do with any of this.

Faris.

Ah right yes. I updated everything, not just php, no wonder it didn't like it!

What i did next was to re-image the server and then update php on it's own and it seems to be running fine now.

The last remaining question is how to update it to centos 5.4, at the moment it's 5.2 with an updated php only, surely that"s not massively secure?

Would it be very difficult to update everything else? Why does plesk have to be so damn invasive!

Thanks for your reply BTW, very much appreciated!

The 5.2 to 5.4 upgrade is painless, apart from this ssl issue.

Take a look here: http://kb.parallels.com/en/8338 regarding the probably cause.

There's a nice thread about it all here: http://www.atomicorp.com:8080/forum/vie ... =18&t=4007

It is a shame you reimaged already because ideally you should look at your logs (which are not where I said they were - look at location in the first link I pasted above) to confirm the problem is the ssl thing, and, knowing that that's all it was, you can then install the patch and upgrade without too much worry.

As it is I may be totally wrong and something else is the matter.

Also if you're using 9.5 it would just drop right in. You dont need to do anything about the openssl changes.

So what should i do then, just yum upgrade now that i'm on 9.5 and say yes to everything?

That would be cool.

If you are on 9.5.2 (not earlier) then all should be OK. But I can't guarantee anything and could be wrong!

I assume you were on an earlier version when you had your problem?

Yes i was on 9.0 when i first did it. Stupidly i presumed a brand new server would come with plesk fully uptodate. Silly me...

It must be a license through the server vendor not your own plesk license direct?

If so that is normal for a reseller.

That's right yes, the plesk license is from 1and1.

You might have to contact them directly for a key then.

I don't need a key, plesk is updating fine!