Ha ha, take that 1and1, I fixed it myself, nyarr .
This is what I had to do, for anybody who finds themselves in a similar situation of having had an rpm -e psa happen
[list=1][*] First, get the 6.02 psa rpm from
(arg, can't post a url on the BB, sucky, remove the obvious space yourself) www .atomicrocketturtle.com/atomic/psa/9/RPMS/[*] Then, because the plesk postinstall doesn't know how to handle reinstalling after an rpm -e you have to do a little fixing. Log into your database as admin user, and 'select * from psa.upgrade_history' what you're looking for is the latest version_info string, copy that string. Now echo that string into /usr/local/psa/version[*] Now you want to do 'rpm -Uvh <the rpm file> --nopre' (the nopre is because of another problem with the rpm's after havign done an rpm -e), cross your fingers and pray to Dog whilst closing your eyes out of fear for a few minutes.[*] Ok, almost there, go into /etc/psa, you have to find the right psa.key file as the psa install scripts seem to put in a new one without the correct info. I found that psa.key.default worked correctly, your milage may vary. Just try any that are there until you can log in at the plesk admin again (you have to restart plesk between changing keys - /etc/init.d/psa restart (or maybe stop then start is required). I guess if you can't find one it's time to grovel to 1and1 to send the correct one (or get the to drop it in place, surely wouldn't be too much trouble for them).[/list=1]
I think that has fixed it, I'm not 100%, but I think it's right.
Note : The problem is initially that plesk doesn't support mysql4 because of a new reserved word ('ssl') introduced in mysql. The rpm downloaded above, apparently (seemingly) has been patched to work with mysql4.