Модуль opcache подсистемы php настроен некорректно

[Bug]: PHP OPcache module is not properly configured: OPcache interned strings buffer is nearly full

The PHP OPcache module is not properly configured. See the documentation ↗ for more information.
The OPcache buffer is nearly full. To assure that all scripts can be hold in cache, it is recommended to apply opcache.memory_consumption to your PHP configuration with a value higher than 1024.

So I am running version 25.0.5. Been encountering this error for a while. Kept increasing the limit but it always comes back. Even pushed the limit to 10gb, still would return the error. There seems to be something wrong with OPcache and Nextcloud Hub 25.

Note that I have several large network shares connected using external storage.

Steps to reproduce

1. Install a LAMP server with PHP 8.1 and all the required module
2. Add the recommended OPcache settings to php.ini
3. Login on Nextcloud and go to Administration — Overview

Expected behavior

Cache should regenerate according to demand.

Installation method

Community Manual installation with Archive

Nextcloud Server version

Operating system

PHP engine version

Web server

Database engine version

Is this bug present after an update or on a fresh install?

Are you using the Nextcloud Server Encryption module?

What user-backends are you using?

Configuration report

< "system": < "passwordsalt": "***REMOVED SENSITIVE VALUE***", "secret": "***REMOVED SENSITIVE VALUE***", "trusted_domains": [ "cloud.albcie.com", "cloud.albgroupe.com", "cloud.albcustoms.com", "cloud.alblogistique.com", "192.168.20.253" ], "datadirectory": "***REMOVED SENSITIVE VALUE***", "overwrite.cli.url": "http:\/\/cloud.albcie.com", "dbtype": "mysql", "version": "25.0.5.1", "dbname": "***REMOVED SENSITIVE VALUE***", "dbhost": "***REMOVED SENSITIVE VALUE***", "dbport": "", "dbtableprefix": "oc_", "dbuser": "***REMOVED SENSITIVE VALUE***", "dbpassword": "***REMOVED SENSITIVE VALUE***", "enable_previews": false, "logtimezone": "GMT-5", "installed": true, "maintenance": false, "theme": "", "log_type": "owncloud", "logfile": "\/var\/www\/cloud.albcie.com\/log\/nextcloud.log", "loglevel": "2", "logdateformat": "F d, Y H:i:s", "ldapIgnoreNamingRules": false, "ldapProviderFactory": "\\OCA\\User_LDAP\\LDAPProviderFactory", "default_phone_region": "CA", "allow_local_remote_servers": true, "mail_from_address": "***REMOVED SENSITIVE VALUE***", "mail_smtpmode": "smtp", "mail_smtpauthtype": "LOGIN", "mail_domain": "***REMOVED SENSITIVE VALUE***", "mail_smtpname": "***REMOVED SENSITIVE VALUE***", "mail_smtppassword": "***REMOVED SENSITIVE VALUE***", "mail_smtpauth": 1, "mail_sendmailmode": "smtp", "mail_smtphost": "***REMOVED SENSITIVE VALUE***", "mysql.utf8mb4": true, "simpleSignUpLink.shown": false, "app_install_overwrite": [ "keeweb", "nextant", "uploaddetails", "documentserver_community", "passman", "apporder", "drawio", "user_external", "limit_login_to_ip" ], "instanceid": "***REMOVED SENSITIVE VALUE***", "memcache.locking": "\\OC\\Memcache\\Redis", "memcache.local": "\\OC\\Memcache\\Redis" > >

List of activated Apps

Enabled: - apporder: 0.15.0 - bookmarks: 12.1.0 - bruteforcesettings: 2.5.0 - calendar: 4.3.1 - camerarawpreviews: 0.8.1 - circles: 25.0.0 - cloud_federation_api: 1.8.0 - comments: 1.15.0 - contacts: 5.2.0 - contactsinteraction: 1.6.0 - dashboard: 7.5.0 - dav: 1.24.0 - documentserver_community: 0.1.13 - drawio: 2.1.0 - external: 5.0.2 - externalportal: 1.1.0 - federatedfilesharing: 1.15.0 - files: 1.20.1 - files_external: 1.17.0 - files_pdfviewer: 2.6.0 - files_retention: 1.14.1 - files_rightclick: 1.4.0 - files_sharing: 1.17.0 - files_texteditor: 2.15.0 - files_trashbin: 1.15.0 - files_versions: 1.18.0 - groupfolders: 13.1.1 - groupquota: 0.1.10 - integration_github: 1.0.15 - keeweb: 0.6.12 - logreader: 2.10.0 - lookup_server_connector: 1.13.0 - notes: 4.7.2 - notifications: 2.13.1 - oauth2: 1.13.0 - onlyoffice: 7.8.0 - password_policy: 1.15.0 - photos: 2.0.1 - polls: 4.1.8 - previewgenerator: 5.2.2 - privacy: 1.9.0 - provisioning_api: 1.15.0 - quota_warning: 1.16.0 - related_resources: 1.0.4 - settings: 1.7.0 - sharebymail: 1.15.0 - smb_test: 0.3.6 - spreed: 15.0.5 - suspicious_login: 4.3.0 - systemtags: 1.15.0 - tasks: 0.14.5 - text: 3.6.0 - theming: 2.0.1 - theming_customcss: 1.13.0 - twofactor_backupcodes: 1.14.0 - user_external: 3.1.0 - user_ldap: 1.15.0 - user_status: 1.5.0 - viewer: 1.9.0 - weather_status: 1.5.0 - workflowengine: 2.7.0 Disabled: - activity: 2.6.1 - admin_audit: 1.8.0 - announcementcenter: 6.5.1 - appointments: 1.14.13 - audioplayer: 3.3.1 - browser_warning: 1.0.0 - checksum: 1.2.1 - emlviewer: 1.0.7 - encryption - epubreader: 1.4.7 - event_update_notification: 2.1.0 - extract: 1.3.5 - federation: 1.8.0 - files_accesscontrol: 1.15.1 - files_automatedtagging: 1.15.3 - files_frommail: 0.4.0 - files_fulltextsearch: 25.0.0 - files_fulltextsearch_tesseract: 25.0.0 - files_trackdownloads: 1.7.0 - firstrunwizard: 2.2.1 - forms: 3.2.0 - fulltextsearch: 25.0.0 - impersonate: 1.12.0 - integration_mattermost: 1.0.3 - limit_login_to_ip: 3.1.0 - mail: 2.2.5 - nextant: 1.0.10 - nextcloud_announcements: 1.7.0 - ocr: 6.0.58 - passman: 2.4.4 - phonetrack: 0.7.4 - radio: 0.6.6 - rainloop: 7.2.6 - ransomware_detection: 0.10.0 - recommendations: 0.6.0 - serverinfo: 1.8.0 - socialsharing_email: 2.5.0 - support: 1.0.1 - survey_client: 1.5.0 - talk_matterbridge: 1.26.0 - twofactor_totp - updatenotification: 1.8.0 - w2g2: 3.3.9 - workflow_pdf_converter: 1.10.1

Nextcloud Signing status

No errors have been found.

Источник

Saved searches

Use saved searches to filter your results more quickly

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Netxcloud 23.0.2snap1 — error message PHP OPcache module is not properly configured: #2024

Update Netxcloud 23.0.2snap1 — error message PHP OPcache module is not properly configured: #2024

Comments

After snap update to Netxcloud 23.0.2snap1

an error message appears in settings/overview

The PHP OPcache module is not properly configured:

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.

How can this be corrected in cofig.php?
Which value is suggested?

The text was updated successfully, but these errors were encountered:

Thanks, will keep an eye on it and give you feedback.

Restarted nextcloud-snap # snap restart nextcloud to see message disappear!
Please close and forget

Right, this is a cache in PHP— restarting clears it. As you use Nextcloud, it fills up and swaps strings out. If it gets pretty full, the new release of Nextcloud warns you about it. If you see a warning constantly, it means you would benefit with slightly improved performance if you increased the cache size (something that is not configurable in the snap today). So please still keep an eye on it— if you see it often, I’m willing to make that configurable.

Thanks, I’ll keep an eye on it nonetheless and give you feedback.
Configurable is great!

you are right, the message reappears minutes after restart.
I’ll keep you updated in a clouple of days.

warning message continues.
I have several (4) systems running the same snap with almost identical setups.
Only one system displays the warning message;

Please make configurable.

after comparing installed apps on all instances, I found that the «CODE» and «Nextcloud Office» was installed on the error instance. «CODE» and «Nextcloud Office» has stopped working since upgrade!

I assume that OPcache module needs to be configured for Nextcloud Office? This is not confirmed!

Same issue here.
Please allow us to set

opcache.memory_consumption opcache.interned_strings_buffer 

Alright, I’m on board with this, just need to find time to do it unless someone else wants to take a crack at it.

Hi to all,
I see the same warning message :
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.

on my two snap instance: Nextcloud Hub II (23.0.3)

Only one of them instance have CODE installed.
It is possible to update/change php.ini configuration manually but persistently?
We have to waiting for next upgrade?

@kyrofa , may i bump this. as a friendly reminder? 🙂

Message is present also in a 24.0.1 snap version.

Hi to all, I see the same warning message : 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.

on my two snap instance: Nextcloud Hub II (23.0.3)

Only one of them instance have CODE installed. It is possible to update/change php.ini configuration manually but persistently? We have to waiting for next upgrade?

Thank you.

I tend to sync a lot of files and share them with others. I have several family members using my server so it sees a lot of traffic. Having the ability to set this value would be awesome. I’m looking through the code right now to see I can figure out how to add it and then do a PR, but I’m likely to take a while to get it done since this snap is new to me.

Refer to how the PHP memory limit works to get a leg up.

Do I need to be looking at this file: src/php/utilities/php-utilities ? Just want to be sure I’m thinking along the right lines before I invest a ton of time barking up the wrong tree. It seems like you’re using this script to get user input to then set values within the snap using snapctl .

Yes that’s one piece. Look also at src/hooks/bin/configure and the PHP configs in src/php/config . Finally, the integration tests in tests/integration/change_php_memory_limit_spec.rb .

@kyrofa I’ve got a rough draft of the code needed to do this (I think). I need a sanity check on what I’ve done and wondering which branch you’d like me to do a PR in?

Please note: I am unable to build the snap locally, so I’m hoping your review of my code and potentially a test-build on your end will result in a good outcome.

Make a PR into develop, please.

Hi,
I have the same issue in Snap Nextcloud 24.0.6.
And actually to complete what has been said before, I think it would be nice if we could have access to modify any opcache.* parameters if possible.

If this isn’t possible, here is a non-exhaustive list of parameters I believe nextcloud admin may want to play with once it will be possible:

• opcache.interned_strings_buffer
• opcache.revalidate_freq
• opcache.fast_shutdown
• opcache.save_comments
• opcache.validate_timestamps
• opcache.enable
• opcache.enable_cli
• opcache.max_accelerated_files
• opcache.memory_consumption

I also would like to share additionnal sources for those who would like to read more about opcache teaking and find how to tune it properly for your own server:

Looking forward to get this available. Thank you 🙂 !

Making most of those parameters configurable would be a footgun. For example, Nextcloud requires opcache.save_comments . If we made it configurable, and you turned it off, you’d break Nextcloud. There’s no upside to that. The PHP shipped in the snap is not generically useful to you: it’s entire purpose is to run Nextcloud. Because of that, for the most part, we can have a configuration that works for everyone instead of exposing knobs.

Making most of those parameters configurable would be a footgun. For example, Nextcloud requires opcache.save_comments . If we made it configurable, and you turned it off, you’d break Nextcloud. There’s no upside to that. The PHP shipped in the snap is not generically useful to you: it’s entire purpose is to run Nextcloud. Because of that, for the most part, we can have a configuration that works for everyone instead of exposing knobs.

Thank you for the information, I didn’t know that.
Then it make sense to keep the list of configurable options short.

As mentionned before, opcache.memory_consumption and opcache.interned_strings_buffer should be made configurable, and as I have read, it is already done.
opcache.revalidate_freq could also be of primary interest.
As for the remaining parameters, I admit I don’t know to which extend they could cause issues to Nextcloud.

Источник