• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • 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.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Error running autoinstaller: .

fabbrica

New Pleskian
I have recently updated my Parallels Plesk Panel from 9.5.4 to v11.5.30_build115130819.13 os_CentOS 5
OS CentOS 5.9 (Final)

Apparently the panel works fine, but I have experienced this problem:

while trying to launch the plesk installer from the panel (I was trying to add more components, but I can't...) I see this error:

Errore: Impossibile avviare l'Installer di Prodotti Parallels. Si è verificato il seguente errore: Error running autoinstaller: .
(i use the italian interface)

update_error.jpg

This is my repos list:

repo id repo name status
addons CentOS-5 - Addons 0
base CentOS-5 - Base 2,770
c5-testing CentOS-5 Testing 0+71
extras CentOS-5 - Extras 276
kbs-CentOS-Extras CentOS.Karan.Org-EL5 - Stable 0
updates CentOS-5 - Updates 483
repolist: 3,529

I'm afraid that, when a new version will become available, upgrading the panel could be a problem...

What can I do?
 
Last edited:
Likely you already have a copy of Autoinstaller running. They usually quit after 30 minutes of inactivity. Check ps aux | grep installer to confirm. You may also check tail of /tmp/autoinstaller3.log.

Alternatively, some other process has occupied 8447 port. Check with netstat -tulnap | grep 8447.
 
Back
Top