• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Plesk 11.0 is bouncing

hedera

New Pleskian
I have a Linux virtual server running CentOS 6, managed by Plesk 11.0. The web site is lifering.org, it's hosted at GoDaddy. For the last few days, our site has been crashing unexpectedly, and when we investigated, we found that Plesk is spiking the CPU usage and crashing. I haven't been able to bring Plesk up for over an hour.

The Plesk error log shows this error, several times:

2016-04-12 09:23:06: (server.c.1543) server stopped by UID = 0 PID = 13922

The PID varies. I Googled this and found https://kb.plesk.com/en/120079, KB Plesk: Daily maintenance script stops PSA service. This sure looks like my problem, but the instructions confuse me:
  1. Remove the package:

    rpm -e <package_name> --noscripts --nodeps --justdb

  2. Start components upgrade

    #/usr/local/psa/admin/bin/autoinstaller --select-product-id plesk --select-release-current --upgrade-installed-components
I'm sorry to be so ignorant, but I never had to deal with Plesk before. What <package_name> do I remove? It looks like I remove Plesk entirely and then autoinstall the current release, but that is so drastic I'd like someone to confirm that I'm reading it correctly. I did an rpm --qa on components including the string "plesk" and found all this, which doesn't help me with which package name to remove:

plesk-l10n-11.0.9-cos6.build110120827.16.noarch Sun Nov 11 15:20:50 2012
plesk-core-11.0.9-cos6.build110120608.16.x86_64 Sun Nov 11 15:20:19 2012
plesk-mail-qc-driver-11.0.9-cos6.build110120608.16.x86_64 Sun Nov 11 15:20:10 2012
psa-pylibplesk-11.0.9-cos6.build110120608.16.x86_64 Sun Nov 11 15:20:08 2012
psa-libpam-plesk-11.0.9-cos6.build110120608.16.x86_64 Sun Nov 11 15:20:08 2012
plesk-base-11.0.9-cos6.build110120608.16.x86_64 Sun Nov 11 15:20:08 2012
log4cpp-plesk-0.3.5rc2-10.12051715.x86_64 Sun Nov 11 15:20:00 2012
plesk-skins-11.0.8-12051419.noarch Sun Nov 11 15:19:59 2012
drweb-updater-5.0.1-0plesk.i386 Sun Nov 11 15:19:54 2012
drweb-daemon-5.0.1-0plesk.i386 Sun Nov 11 15:19:50 2012
drweb-common-5.0.1-0plesk.i386 Sun Nov 11 15:19:48 2012

I also don't understand why my system is crashing in April if it was last updated in November, since the KB suggests this was a problem with the autoinstaller.
 
I suppose that article talks about psa-mod_fcgid package. Look:

# rpm -qa | grep mod_fcgid
psa-mod_fcgid-2.3.9.1-centos6.15072015.i386

# rpm -qf /etc/httpd/conf.d/fcgid.conf
psa-mod_fcgid-2.3.9.1-centos6.15072015.i386
 
Thanks for clarifying that. After I wrote this I realized that, since I'm running a backleveled version of Plesk, it might not be totally smart to run an autoinstall with --select-release-current. As it happened, starting the dead Plesk from the SSH command line seems to have solved the problem - at least, nothing has bounced since I did that. Thanks again for your help.
 
Back
Top