Yet another Plesk problem

[impleri]

So here's the background:
I thought it was about time to upgrade to Plesk 9 as it had been out for a while. The actual update went fine....except that incoming mail was silently rejected. Figured out it and got Courier working fine...with SpamAssassain and Clam, like a good program should.
Now, one of my clients got a "better" domain name and wanted to switch everything to it. Simple enough, right? Just use the rename domain feature. Well, it failed....halfway through because of crap script hooks left over by qmail. I thought the easy answer was to remove those hooks. The rename finally worked...except that both the old name and new name already existed (theoretically). Well, I got that working.
Now, however, the entire Plesk backend is completely borked. The only error I get is the skinned "This application sucks, died. Contact your administrator." That would be me. I went through all logs I could find and none report any error....anywhere. Except that the entire backend (:8443 and even the VZCP on :4643) is borked beyond belief. I can access by SSH, but I don't see anything wrong. Anyone got any hints/suggestions?

[JPC-Bilal]

It may be caused by some internal errors while upgrading Plesk to 9.x but cannot say anything with surety without checking the server and logs. Please open a support ticket and provide us details in it and we will look into it.

[impleri]

I highly doubt it was the update to Plesk 9, as that was done two weeks ago and those problems had been fixed then.
I'm still not sure what happened, but I tried logging into the backend today and all worked. The uptime on the VPS is concurrent with the last time I rebooted it. Was there any problem with JagPC's Virtuozzo node (since it seems to be external to the VPS)? The domains in question (both old and new) began working after reloading BIND and apache. Could this have been a terribly bad case of coincidences?

[JPC-Bilal]

I don't think so it is a coincidence. Also none of the Virtuozzo hardware nodes is facing any problem. Is there any QoS parameter of your VPS hitting its limit? It can be one of the causes as well and since you restarted the VPS, it may have refreshed the resources and memory usage that fixed this issue temporarily.

If you want technical support to check QoS parameters of your VPS then please open a support ticket.