• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Issue PHP memory limit of service plan does not sync to subscriptions on update

Bitpalast

Plesk addicted!
Plesk Guru
Plesk 12.5.30, CentOS 7.1, 64 bit

A change of the PHP memory limit in the service plan does not sync to unlocked, syncable subscriptions when the new service plan settings are stored. Other updated service plan values sync.

Example: A service plan has a PHP memory limit of 128 MB and disk space of 1 GB. It has five subscriptions, all of which are in sync with the plan and unlocked. In the service plan change the disk space from 1 GB to 2 GB and the PHP memory limit from 128M to 256M. Plesk will apply the service plan changes to the subscriptions, but it will only apply the new disk space setting, not the new PHP memory limit setting.

This behavior can also be reproduced when changing memory limit only. The only way to update the PHP memory limit in existing subscriptions seems to be to update each subscription separately. Why is that?
 
Hi Peter,
It won't sync the PHP settings and handlers if the Service Plans can control PHP handlers and settings.
Regards

Lloyd
 
@Peter Debik

In essence, your question has been answered by @Lloyd_mcse.

Note that it is a "design fluke" or a least a strange design choice.

In the light of your test case, the following applies:

1 - Plesk will not change anything in existing subscriptions, unless "Permissions > Hosting Settings Management" is unchecked in "Service Plans > Hosting Plans", AND

2 - leaving "Permissions > PHP version and handler management checked", given settings as mentioned in part 1, results in (FPM related) errors when changing the PHP version.

Naturally, the first part seems to suggest a "design choice", the second part clearly indicates a "design fluke".

It does not matter from which perspective we are analyzing your question, the answer more or less hints a potential bug, one way or another.

Thanks for pointing that out!

Regards.....
 
Back
Top