• 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.

Issue Autoinstaller unexpected exception

Agnilor

New Pleskian
For the last couple of days the update process does not work anymore I get the following error in the panel:

Execution failed. Command: autoinstaller Arguments: Array ( [0] => --service-mode [1] => --enable-xml-output [2] => --ssl-cert [3] => /usr/local/psa/admin/conf/httpsd.pem [4] => --branch [5] => release,stable ) Details: ERROR: Internal error: unexpected exception caught

I've tried running the installer from the command line:
# plesk installer --debug
Code:
ERROR: Internal error: unexpected exception caught
exit status 1

Nothing is logged to /vim/autoinstaller3.log, so I have no idea what the problem is.
Anybody have any ideas?


OS: Centos 7.5.1804
Plesk version: 12.5.30#76
 

I've tried that solution, but it didn't work.

Log file permissions:
# ls -las /tmp/autoinstaller3.log
0 lrwxrwxrwx. 1 root root 41 May 8 03:39 /tmp/autoinstaller3.log -> /var/log/plesk/install/autoinstaller3.log

# ls -la /var/log/plesk/install/autoinstaller3.log
-rw-------. 1 root root 9756141 May 14 03:16 /var/log/plesk/install/autoinstaller3.log

I have also reinstalled the autoinstaller package.
The installer still gives the same error and still nothing gets logged.

Any other ideas?
 
This issue still exists...

Does anyone have any ideas about how to fix this or even how to find more information about it?
 
Back
Top