Well, you may be right.
Thanks for the explanations. I will now ignore the message.
Well, you may be right.
Thanks for the explanations. I will now ignore the message.
I have upgrated to V23.0.3 and same problem.
Since upgrade from 22.2.6 to 23.0.3 same problem on sahred hosting.
Seems to be a bug.
nano /etc/php/8.1/cli/php.ini
添加以下代码:
opcache.enable=1
opcache.enable_cli=1
opcache.interned_strings_buffer=8
opcache.max_accelerated_files=10000
opcache.memory_consumption=128
opcache.save_comments=1
opcache.revalidate_freq=1
Hope it’s ok to also ask on this thread, same error msg/hint.
I’m running Nexctcloud as/within an Apache VHOST. In the vhost’s config, I’ve set (aside to several other, Apache specific values):
<IfModule mod_php.c>
php_value upload_max_filesize 15G
php_value memory_limit 512M
php_flag opcache.save_comments 1
php_flag opcache.revalidate_freq 60
php_value opcache.interned_strings_buffer 128
</IfModule>
This entries have “fixed” the a long while ago “PHP limit below recommended 256M” or similar warning. But OPcache warning about “opcache.interned_strings_buffer” is quite “sticky”…
As I assume that another Apache config, maybe Apache’s general PHP settings, or whatever, is overriding my VHOST setting: Any hints how to get the real current value for opcache.interned_strings_buffer for my Nextcloud’s VHOST?
Remark: Changing from php_flag … to php_value … as Apache directive leads Nextcloud’s scan to say “Everything fine” one time, but warning is now back again