Applicable to:
- Plesk for Linux
- Plesk for Windows
Symptoms
-
Any of the following operations in Plesk:
- Accessing Plesk inteface
- Opening WordPress Toolkit
- Opening an extension
- Running a scheduled task
- Installing updates for Plesk or extensions
- Let's Encrypt certificates are not updated automatically
fails with a blank page or one of the following error messages in Plesk:
PLESK_INFO: PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 16384 bytes) in /usr/local/psa/admin/plib/vendor/plesk/zf1/library/Zend/Db/Statement/Pdo.php on line 228
PLESK_INFO: Out of memory (allocated 23855104) (tried to allocate 12975879 bytes) (Abstract.php:41)
PLESK_INFO: Error 500
-
The following error messages appear in the Plesk logfile with debug mode enabled:
-
On Linux:
/var/log/plesk/panel.log -
On Windows Server:
%plesk_dir%\admin\log\php_error.log
CONFIG_TEXT: PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 52198551 bytes) in C:\Program Files (x86)\Parallels\Plesk\admin\plib\CommonPanel\Exception.php on line 58
ERR [1] ERROR: Allowed memory size of 268435456 bytes exhausted (tried to allocate 52198551 bytes) (Exception.php:58) -
Cause
Memory limit is exceeded by Plesk PHP back-end. This may happen if an object, over which the operation was performed, has a complex structure.
Resolution
-
Connect to the Plesk server via SSH.
-
Open the Plesk PHP configuration file php.ini in a text editor. In this example, we are using the vi editor:
# vi /usr/local/psa/admin/conf/php.ini
-
Increase the
memory_limitlimit to 512. -
Save the changes and close the file.
-
Restart the Plesk management service:
# service sw-engine restart && service sw-cp-server restart
-
Redo the previously failed operation. If it fails with the same error, increase the
memory_limitlimit to a greater value and restart the services. -
To prevent the changes from being reverted during Plesk update, replace the following line in
/etc/cron.daily/50plesk-daily:-
For Debian/Ubuntu:
CONFIG_TEXT: /usr/local/psa/bin/sw-engine-pleskrun /opt/psa/admin/plib/DailyMaintainance/script.php >/dev/null 2>&1
With:
CONFIG_TEXT: /usr/local/psa/bin/sw-engine-pleskrun /opt/psa/admin/plib/DailyMaintainance/script.php >/dev/null 2>&1 && sed -i '/memory_limit/c\memory_limit = 512M' /usr/local/psa/admin/conf/php.ini
-
For CentOS:
CONFIG_TEXT: /usr/local/psa/bin/sw-engine-pleskrun /usr/local/psa/admin/plib/DailyMaintainance/script.php >/dev/null 2>&1
With:
CONFIG_TEXT: /usr/local/psa/bin/sw-engine-pleskrun /usr/local/psa/admin/plib/DailyMaintainance/script.php >/dev/null 2>&1 && sed -i '/memory_limit/c\memory_limit = 512M' /usr/local/psa/admin/conf/php.ini
-
-
Connect to the Plesk server via RDP.
-
Open the Plesk PHP configuration file
%plesk_dir%admin\conf\php.iniin a text editor. -
Increase the
memory_limitlimit to 512. -
Save the changes and close the file.
-
Restart the Plesk management service:
Start PowerShell and run the commands one by one:
PS import-module WebAdministration
net stop "Plesk PopPass Service"
net stop "Plesk Management Service"
net start "Plesk Management Service"
net start "Plesk PopPass Service"
Restart-WebAppPool PleskControlPanel -
Redo the previously failed operation. If it fails with the same error, increase the
memory_limitlimit to a greater value and restart the services.
Comments
6 comments
I had this issue trying to delete a subscription, i followed this guide but it seems the restart of the Plesk management service does not "read" the new php.ini, in fact after the modification i tried again to delete the subscritpion but the error was the same.
Then i tried to restart Plesk services by "Plesk service monitor": i restarted the entire "Plesk run-time" and "Mail service" then tried to delete the subscription again, no luck.
Finally i restarted the server and finally i was able to delete the subscription.
@Gianluca, which limit have you specified when applying the solution?
There is a possibility that specified limit was not enough.
I have increased the limit from 256M to 512M.
@Gianluca, thank you for the provided info.
If the issue will reoccur, increase the limit further. In case it would not help, consider submitting a ticket to Plesk Technical Support.
Changes are lost after Plesk upgrade is performed (/usr/local/psa/admin/conf/php.ini is reset to default).
Please provide a persistent solution.
Hello Oleg Burca
To prevent the changes from being reverted during Plesk update, replace the following line in
/etc/cron.daily/50plesk-daily:For Debian/Ubuntu:
/usr/local/psa/bin/sw-engine-pleskrun /opt/psa/admin/plib/DailyMaintainance/script.php >/dev/null 2>&1
With:
/usr/local/psa/bin/sw-engine-pleskrun /opt/psa/admin/plib/DailyMaintainance/script.php >/dev/null 2>&1 && sed -i '/memory_limit/c\memory_limit = 512M' /usr/local/psa/admin/conf/php.ini
For CentOS:
/usr/local/psa/bin/sw-engine-pleskrun /usr/local/psa/admin/plib/DailyMaintainance/script.php >/dev/null 2>&1
With:
/usr/local/psa/bin/sw-engine-pleskrun /usr/local/psa/admin/plib/DailyMaintainance/script.php >/dev/null 2>&1 && sed -i '/memory_limit/c\memory_limit = 512M' /usr/local/psa/admin/conf/php.ini
Please sign in to leave a comment.