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

Upgraded and now PSA service will no longer start

how much ram u have? an how much is in use?
I have 2gb ram and 300mb are used. plesk used 512mb ram up to 768mb than must be 2gb more than enough

Mines the same, around 300mb of ram used out of 2gb. Wasn't watching htop when running Plesk Autoupdate so don't know what the resources were like.

I believe the Plesk update uses more resources than the VPS can handle and essentially crashes the server mid-update, which in turn causes all kinds of backlash.
 
Mines the same, around 300mb of ram used out of 2gb. Wasn't watching htop when running Plesk Autoupdate so don't know what the resources were like.

I believe the Plesk update uses more resources than the VPS can handle and essentially crashes the server mid-update, which in turn causes all kinds of backlash.

ok, I've got it. comment out that line: zend_extension = "/usr/lib64/php/modules/sw-engine/opcache.so"
;zend_extension = "/usr/lib64/php/modules/sw-engine/opcache.so"
and
set opcache.enabled = 0

or set
opcache.memory_consumption=64
works 4 me too :)
 
Last edited:
Thanks it works for my 1und1 VServer


ok, I've got it. comment out that line: zend_extension = "/usr/lib64/php/modules/sw-engine/opcache.so"
;zend_extension = "/usr/lib64/php/modules/sw-engine/opcache.so"
and
set opcache.enabled = 0

or set
opcache.memory_consumption=64
works 4 me too :)
 
ok, I've got it. comment out that line: zend_extension = "/usr/lib64/php/modules/sw-engine/opcache.so"
;zend_extension = "/usr/lib64/php/modules/sw-engine/opcache.so"
and
set opcache.enabled = 0

or set
opcache.memory_consumption=64
works 4 me too :)

Actually, just setting

opcache.memory_consumption=64

is enough.
opcache seems to get used by startup even if

opcache.enabled=0

And this IS a 1&1 problem obviously. Having the same issues after upgrading to v12.
Seems like 1&1 needs to allow more resources for their virtual servers!
 
Just replying to confirm that setting opcache.memory_consumption=64 worked for me as well on a 1&1 VPS. Thanks guys!!
 
Hi all,

I just updated my 1and1 VPS server to Pleask 12 and hit the same problem (PSA service not restarting, error 502, etc)...so at least 1and1 haven't 'fixed' the error, or made customers aware before updating.

Thank God this thread exists! The opcache.memory_comsumption=64 setting seemed to free up some memory so the PSA could auto restart on the next reboot.

Thank you, thank you, thank you, thank you, thank you, thank you, thank you, thank you, thank you, thank you, thank you, thank you, thank you, thank you, thank you, thank you, thank you!!!

cheers,
Matt
 
Just a simple beginner question in this context... i never used plesk command line tool before the upgrade failed. so how do i close and save my changes in the tool (plesk conf php.ini) ?
 
Back
Top