• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Question Some OPcache settings are overridden by handler-level files

WebHostingAce

Silver Pleskian
Server operating system version
AlmaLinux 8.10 (Cerulean Leopard)
Plesk version and microupdate number
Plesk Obsidian 18.0.70 Update #3
Hi,

In Tools & Settings > PHP Settings, I have configured:

opcache.revalidate_path = 0

This setting is correctly reflected in the Loaded Configuration File located at:

/var/www/vhosts/system/domain.tld/etc/php.ini

However, when checking the PHP info page for the domain, it still shows:

opcache.revalidate_path = 1

This appears to be overridden by the default configuration in:

/opt/plesk/php/8.3/etc/php.d/10-opcache.ini

As a workaround, I commented out the line opcache.revalidate_path = 1 in that file, and now the value from Tools & Settings > PHP Settings is applied correctly.

My question is:

How can I ensure this change is preserved after a future Plesk or PHP update?

We prefer not to manage this configuration at the individual domain level, as we have over 50 multistore setups and it would be difficult to maintain consistency that way.

Thank you.
 
You could create an additional configuration file in /opt/plesk/php/8.3/etc/php.d/, in which you define the opcache.revalidate_path, and as long a you name that file to something that's comes alphabetically after "10-opcache", it gets loaded later and will overwrite whatever setting is configured in there.

Edit: you'll have to restart the PHP-FPM service afterwards for the change to take effect.
 
Last edited:
Back
Top