• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS.

getting fedora core test page after plesk update

J

jcg76

Guest
Ok. after an update from 8.1.0. to 8.1.1. I got the following problems:

1. all my domains on this plesk server only showed the installation page of sitebuilder after the update.
If "fixed" this by de-install sitebuilder
yum remove siteuilder
see here http://forum.swsoft.com/showthread.php?s=&threadid=24529

2.but after all I saw only the "Fedora Core Test Page" instead of any other pages. so I found in the forum to try it with websrvmng
/usr/local/psa/admin/sbin/websrvmng -a -v
but I got an error message for one of the domains inside this server. I finally deleted this domain and did
/usr/local/psa/admin/sbin/websrvmng -a -v
again.

Now my plesk server is working again and my clients are moreless happy. :confused:
just to post this for the more clever people: update only after some time and reading the problems in the forum....
 
the error message from websrvmng was something with "missing directory" in the conf directory of one domain. Sorry but i forgot...
 
ok. the plesk server is working, but now autoupdater is not working... yeha


"Error: Unexpected 'St9bad_alloc' catched.."

to be continued...
 
I geht the same error

"Error: Unexpected 'St9bad_alloc' catched.."
 
I get same error also.

"Unexpected St9bad_alloc"

Have you managed to fix?
 
This is a problem of the memory put webserver mailserver off and restart the update then it should work
 
Thank you for your response druckgott. I have tried your suggestion via control panel but still the same error.

Just had response from ISP (1&1) who have also said it's probably a memory issue and to run autoinstaller from command line. Unbelievably instead of upping the memory allocation I'm told I have to upgrade my service (more memory) to get control panel updater to work even though I have only just started using the 1&1 VPS service.

The moral of this story is DO NOT USE 1&1.
 
Back
Top