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

one-click-installer issue

N_Vas

Basic Pleskian
I used the one-click installer to install Plesk 12:

wget -O - http://autoinstall.plesk.com/one-click-installer | sh



The install ended up failing due to a hostname issue, and the installation said to fix that and then try installing again.

I fixed that issue, but the problem now is that I cannot run the installer because it says some things are already installed.


This was the tail end of the original installation (attached)


Now when I try to install again:


Detecting installed product components.
ERROR: You cannot select installation type for already installed products.



So, how does one attempt another installation after a failure?


I did try also running this:

./parallels_installer

which took me through a variety of command line pages and menus, and I completed that, but there is no service running on port 8443 and attempting to restart the plesk services failes on the sw_cp_server:


# /etc/init.d/psa stop
Stopping sw_engine service... done
# /etc/init.d/psa start
Starting sw_engine service... done
Starting sw_cp_server service... failed
Starting mysql service... already started
Starting named service... already started



Please advise.

Thank you
 

Attachments

  • 5-27-2015 10-51-31 AM.jpg
    5-27-2015 10-51-31 AM.jpg
    242.4 KB · Views: 2
Now try to repair your Plesk installation with bootstrapper repair procedure.
 
The bootstrapper repair failed with error:

---
Finishing up upgrade procedures and rerunning previously failed upgrade actions...
Trying to set up APS controller database... APS db accessibility check was skipped.
Unable to obtain secret key for passwords encryption.

ERROR while trying to store APS controller db connection parameters into product db
Check the error reason(see log file: /var/log/plesk/install/plesk_12.0.18_repair.log), fix and try again

***** problem report *****
ERROR while trying to store APS controller db connection parameters into product db
Check the error reason(see log file: /var/log/plesk/install/plesk_12.0.18_repair.log), fix and try again

---



The error repair log the above message references has the exact same output as was on the screen.

I google'd the error and found this KB and completed the steps here:
http://kb.odin.com/en/122885

Then I tried the repair again, it got further this time but still failed, this time with:

ERROR while trying to Unable to upgrade horde database 3.1 -> 3.2, see psa log for details
Check the error reason(see log file: /var/log/plesk/install/plesk_12.0.18_repair.log), fix and try again


(sitenote - this is a brand new Plesk installation that I started yesterday, so I don't even understand why it's trying to upgrade anything at this early point)




The repair log shows:


Can't handle upgrader critical failure - upgrader state is broken. Probably a programming error.

===> Restoring database from backup /var/lib/psa/dumps/mysql.preupgrade.-12.0.18.20150528-072623.dump.gz


**** Product repair failed.






This is pretty ridiculous considering the only issue during the initial installation was a missing hostname, and now it won't install or repair again and I'll probably have to start a new machine build.

Really your installer should be able to handle / resume a failed installation.



If anything, the installer should just roll completely back then if something fails (completely un-install) so that a fresh install can be performed again.

 
Back
Top