• 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!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    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. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.

Plesk 9.3.1->9.5.1 upgrade fails

C

Chris Magnuson

Guest
It's time once again for that fun game we like to call "Why can't I upgrade from one version to the next version on Plesk without spending time resolving errors?"

In this case, the error after upgrading is:

Error: Error: An internal error occured in auto-installer, rev.290701 Options.h, line 93.
Not all packages were installed.
Please, contact product technical support.

Any ideas?
 
Did you tried upgrade with autoinstaller via CLI? What is OS version you have?
How this issue can be reproduced? Any details?
 
Last edited:
Upgrade 9.3.1 to 9.5.1 caused problems

Upgraded system on Friday and then tried to add new applications via Plesk and now Plesk is down.
This is what I get when I start Plesk:
Customer is getting error:
Problems found
Failed to run the pleskctl utility
Error code:
Error description:

I get this error when viewing /var/log/sw-cp-server/error_log
File downloading PSA_9.5.1/plesk-9.5.1-deb4.0-i386.inf3: 12%..25%..30%..42%..50%..66%..76%..86%..100% was finished.
Parallels Containers were detected. Trying to connect to VZAgent...Warning! Failed to connect to VZAgent: ioctl: Transport endpoint is not connected

Any suggestions. Reinstalling Plesk is out of the question.

Thanks
 
"Trying to connect to VZAgent...Warning! Failed to connect to VZAgent: ioctl: Transport endpoint is not connected"

It is not error but warning and it is caused when server Cannot allocate memory i.e. error means that there are can be not enough resources for your Virtuozzo container to run installer. I can recommend you to increase it to resolve the issue. Also you can try to restart Service container on node.
 
Back
Top