• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

Starting Plesk Failed

S

Stephen_Davies

Guest
Last night I upgraded the version of Plesk from 9.3 to 9.5 and when the update was complete I was able to login to the plesk control panel. I have since tried to restart the plesk and I get back the messages

Starting xinetd service... done
Starting named service... done
Starting mysqld service... done
Starting postgresql service... not install ed
Starting psa-spamassassin service... done
Plesk: Starting Mail Server... already started
Starting mail handlers tmpfs storage
Starting Plesk... failed
Starting drwebd service... failed

When I check the /var/log/sw-cp-server/error_log file I have the following entries,

2010-05-05 11:09:50: (log.c.75) server started
2010-05-05 11:09:50: (network.c.345) SSL: error:140E6118:SSL routines:SSL_CIPHER_PROCESS_RULESTR:invalid command

I have tried appling the rpm file for the openssl breaks plesk. http://kb.odin.com/en/8338 but to not avail.

Any help to resovle this is greatly appreciated.
 
IgorG thank you for your quick response.

The output to the commands are as follows.

rpm -q sw-cp-server
sw-cp-server-1.0-6.201004011432.fc11.i386
rpm -V sw-cp-server (did not give and result).


Stephen
 
What is version of openssl you have there? Do you have updated it with yum?
 
I am running OpenSSL 0.9.8n-fips 24 Mar 2010. I don't use yum I use vzpkg update.
 
Ok I have been looking into this further and the issue seems to be with starting the sw-cp-server itself. Does anyone know where is network.c file is located?

I have created a fresh plesk server using the same iamges as before but instead of upgrading I installed plesk9.5 from scratch and it starts without an issue. both are running fesora core 11.
 
Try to reinstall sw-cp-server rpm package with force.
 
IgorG

thank you for you suggestion. When I try to install the package using rpm -if sw-cp-server-1.0-6.201004011432.fc11.i386.rpm I get package is already installed.
 
Ok,

I have tried the --force command and this is what I got back.

[root@lx1 ~]# rpm -i --force sw-cp-server-1.0-6.201004011432.fc11.i386.rpm
Stoppping SWsoft control panels server... stale pidfile. [ OK ]
Starting SWsoft control panels server... stale pidfile. [FAILED]
warning: %post(sw-cp-server-1.0-6.201004011432.fc11.i386) scriptlet failed, exit status 255


Reading through some of the other forum posts I found if I comment out the reference to starting the plesk control panel on port 8443 it works.
 
Very strange and seems specific issue. I think that it is require detailed investigation directly on your server. Therefore I suggest you contact support team if it is really important for you. As you wrote before - fresh installation works fine for you.
 
The issue has been fixed in support ticket.

Corresponding article was created:

http://kb.odin.com/en/8522

In a nut shell - make sure that configuration file for SSL-secured connection is valid and cipher list is consistent (/usr/local/psa/admin/conf/cipher.lst)
 
Back
Top