Recently I updated my instance of Next Cloud to version 23.0.3, in the process of doing so, I received this warning:

The OPcache interned strings buffer is nearly full. To assure that repeating strings can be effectively cached, it is recommended to apply opcache.interned_strings_buffer to your PHP configuration with a value higher than 8.

So, I took a little stroll online and checked into it a bit. Several people were reporting it as a bug [1], but in reality, this isn’t the case. NC 23 now just checks to see if your opcache.interned_strings_buffer is more than 90% full. If it is, it flags this warning. I looked through the documentation for NC, and at this time, it doesn’t include any info for recommended strings_buffer settings [2].

But, in either event, I know that my server is running NC, and a Piwigo photo server, and a WordPress instance. These three combined could certainly overtake the amount of default memory assigned to the strings_buffer for PHP. With that in mind, I went ahead and increased it.

I went to /etc/php/7.4/apache2/php.ini and made the following edit:

;opcache.interned_strings_buffer=8
opcache.interned_strings_buffer=32

After saving the file, a quick “# systemctl restart apache2” was all that was needed, and the warning went away. I’ll have to check back on it over time, as I know sometimes it takes a while for the buffer to get full. If I don’t post about it again, assume that it worked just fine.

Linux – keep it simple.

References:

[1] https://github.com/nextcloud/server/issues/31223

[2] https://docs.nextcloud.com/server/23/admin_manual/installation/server_tuning.html#enable-php-opcache

Leave a Reply

Your email address will not be published.