Opcache activ, but “0octet no files” on plugin stats + bug

Hi there,

From the error display, seems “opcache_get_status” has been disabled. Docket Cache use this function to get OPcache stats.

I didn’t test it much with PHP 8, since it should not throw any error if failed to get the configuration data.

You may try to check in php.ini directive “disable_functions” if contains “opcache_get_status”. Remove it if you have permission to do it and restart the apache web server.

Otherwise, I will fix this “error” issue in the next release.

Thanks.

• This reply was modified 2 years, 10 months ago by Nawawi Jamili.
• This reply was modified 2 years, 10 months ago by Nawawi Jamili.

Hi,

It seems like I found what the issue is, you may have “opcache.file_cache_only=1” in your opcache configuration. You may try to set it to 0 “opcache.file_cache_only=0”, to make it only caching in shared memory.

I will fix it in the next release to make it compatible with the “opcache.file_cache_only=1” configuration.

Thanks.

@nawawijamili : indeed, passing the setting to 0 makes the admin page of the plugin work again, on the other hand the button flush OPcache does not remove the totality of the files in the folder “.opcache”, is it normal?

@jibsoux

The button only works if OPcache is in shared memory. Docket Cache uses the “opcache_reset” function to reset the OPcache usage. It may not remove the OPcache file in a local directory. You need to remove it manually and restart the php-fpm and apache services.

Thanks.

Hello !
Thank you for the quick response as always.
Would it be possible to have the possibility to indicate a local opcache folder to change the behavior of the Flush Opcache button and thus empty the opcache folder via a php request?

Hi,

It is possible, but Docket Cache does not work properly when OPcache is not operating in shared memory. The reason is, Docket Cache store the cache as a php file, any changes require restarting the php-fpm service.

This is next release file https://docketcache.com/devtest/docket-cache-21.08.xx-dev1.zip, you can try it first.

Thanks.

Hi,

I’m marking this thread as resolved. Feel free to open a new topic if you have further questions.

Thanks.

Hi @nawawijamili !
Thanks for the beta update, this update is made to make Docket cache complient with opcache.file_cache_only=1 if opcache is in local ?

@jibsoux

No, it only fixes the error notice. Currently, we had some issues with login/authentication and I don’t have a timeframe for how long this can be fixed. For time being, Docket Cache can’t be used and is not compatible with opcache.file_cache_only=1.

I hope this answers the question.

Thanks.

Update:

Ok, this is a quick fix, you may try bypass “user_meta” groups from caching to fix the login issue. Place this code in the wp-config.php file.

define('DOCKET_CACHE_IGNORED_GROUPS',
  [
    'counts',
    'plugins',
    'themes',
    'user_meta'
  ]
);

Thanks.

• This reply was modified 2 years, 10 months ago by Nawawi Jamili.

@jibsoux

This is the latest dev file: https://docketcache.com/devtest/docket-cache-21.08.xx-dev2.zip

This will fix “Flush OPcache”. Since OPcache will regenerate cache files quickly, you need to compare file timestamps. Or “Disable Object Cache” before flushing opcache and the “wp-content/cache/docket-cache” folder in the “.opcache” folder should be empty.

No need to define DOCKET_CACHE_IGNORED_GROUPS constant as mentioned earlier.

Thanks.

@jibsoux

This is the latest dev file that makes Docket Cache compatible with opcache.file_cache_only=1

https://docketcache.com/devtest/docket-cache-21.08.xx-dev3.zip

Thanks.

Wow Thanks !
Everything works perfectly at all levels for the local opcache and opcache.file_cache_only=1; !

Thanks !

Thanks for your feedback!