• Resolved wildwuchs123

    (@wildwuchs123)


    Hello,
    After invalidating I get the following message “OPcache is not enabled on this site.”

    My host is IONOS and the opcache is activated via php.ini. I have already read the same error messages here in the forum, but could not fix the “problem”.

    After installing the plugin, I also got the following message about the health of the website:

    
    ### wp-core ###
    
    version: 6.1.1
    site_language: de_DE
    user_language: de_DE
    timezone: Europe/Berlin
    permalink: /%postname%/
    https_status: true
    multisite: false
    user_registration: 0
    blog_public: 0
    default_comment_status: undefined
    environment_type: production
    user_count: 1
    dotorg_communication: true
    
    ### wp-paths-sizes ###
    
    wordpress_path: /homepages/38/d780433205/htdocs/imago
    wordpress_size: 266,03 MB (278951475 bytes)
    uploads_path: /homepages/38/d780433205/htdocs/imago/wp-content/uploads
    uploads_size: 16,53 MB (17332502 bytes)
    themes_path: /homepages/38/d780433205/htdocs/imago/wp-content/themes
    themes_size: 26,49 MB (27781905 bytes)
    plugins_path: /homepages/38/d780433205/htdocs/imago/wp-content/plugins
    plugins_size: 130,53 MB (136866557 bytes)
    database_size: 16,70 MB (17514496 bytes)
    total_size: 456,28 MB (478446935 bytes)
    
    ### wp-dropins (1) ###
    
    advanced-cache.php: true
    
    ### wp-active-theme ###
    
    name: OceanWP (oceanwp)
    version: 3.3.6
    author: OceanWP
    author_website: https://oceanwp.org/about-oceanwp/
    parent_theme: none
    theme_features: core-block-patterns, widgets-block-editor, align-wide, wp-block-styles, responsive-embeds, editor-styles, editor-style, menus, post-formats, title-tag, automatic-feed-links, post-thumbnails, custom-header, custom-logo, html5, woocommerce, wc-product-gallery-zoom, wc-product-gallery-lightbox, wc-product-gallery-slider, customize-selective-refresh-widgets, widgets
    theme_path: /homepages/38/d780433205/htdocs/imago/wp-content/themes/oceanwp
    auto_update: Deaktiviert
    
    ### wp-themes-inactive (1) ###
    
    Twenty Twenty-Two: version: 1.3, author: WordPress-Team, Automatische Aktualisierungen deaktiviert
    
    ### wp-plugins-active (19) ###
    
    All In One WP Security: version: 5.1.2, author: All In One WP Security & Firewall Team, Automatische Aktualisierungen deaktiviert
    Antispam Bee: version: 2.11.1, author: pluginkollektiv, Automatische Aktualisierungen deaktiviert
    Autoptimize: version: 3.1.4, author: Frank Goossens (futtta), Automatische Aktualisierungen deaktiviert
    Broken Link Checker: version: 1.11.21, author: WPMU DEV, Automatische Aktualisierungen deaktiviert
    Coming Soon Page, Maintenance Mode, Landing Pages & WordPress Website Builder by SeedProd: version: 6.15.6, author: SeedProd, Automatische Aktualisierungen deaktiviert
    Contact Form 7: version: 5.6.4, author: Takayuki Miyoshi, Automatische Aktualisierungen deaktiviert
    Elementor: version: 3.9.0, author: Elementor.com, Automatische Aktualisierungen deaktiviert
    Envato Elements: version: 2.0.11, author: Envato, Automatische Aktualisierungen deaktiviert
    Headers Security Advanced & HSTS WP: version: 5.0.06, author: ??  Andrea Ferro, Augusto Bombana, Automatische Aktualisierungen deaktiviert
    Honeypot for Contact Form 7: version: 2.1.1, author: Nocean, Automatische Aktualisierungen deaktiviert
    MailPoet: version: 4.1.1, author: MailPoet, Automatische Aktualisierungen deaktiviert
    Ocean Extra: version: 2.0.6, author: OceanWP, Automatische Aktualisierungen deaktiviert
    OPcache Manager: version: 2.8.0, author: Pierre Lannoy / PerfOps One, Automatische Aktualisierungen deaktiviert
    Real Cookie Banner: version: 3.4.7, author: devowl.io, Automatische Aktualisierungen aktiviert
    Two Factor: version: 0.7.3, author: Plugin Contributors, Automatische Aktualisierungen deaktiviert
    UpdraftPlus - Backup/Restore: version: 1.22.23, author: UpdraftPlus.Com, DavidAnderson, Automatische Aktualisierungen deaktiviert
    WP-Optimize - Clean, Compress, Cache: version: 3.2.9, author: David Anderson, Ruhani Rabin, Team Updraft, Automatische Aktualisierungen deaktiviert
    WP-Sweep: version: 1.1.5, author: Lester 'GaMerZ' Chan, Automatische Aktualisierungen deaktiviert
    WPS Hide Login: version: 1.9.6, author: WPServeur, NicolasKulka, wpformation, Automatische Aktualisierungen deaktiviert
    
    ### wp-media ###
    
    image_editor: WP_Image_Editor_GD
    imagick_module_version: Nicht verfügbar
    imagemagick_version: Nicht verfügbar
    imagick_version: Nicht verfügbar
    file_uploads: File uploads is turned off
    post_max_size: 256M
    upload_max_filesize: 256M
    max_effective_size: 256 MB
    max_file_uploads: 20
    gd_version: 2.2.5
    gd_formats: GIF, JPEG, PNG, WebP, BMP, XPM
    ghostscript_version: 9.27
    
    ### wp-server ###
    
    server_architecture: Linux 4.4.302-icpu-088 x86_64
    httpd_software: Apache
    php_version: 7.4.33 64bit
    php_sapi: cgi-fcgi
    max_input_variables: 1000
    time_limit: 30
    memory_limit: 912M
    max_input_time: -1
    upload_max_filesize: 256M
    php_post_max_size: 256M
    curl_version: 7.64.0 OpenSSL/1.1.1n
    suhosin: false
    imagick_availability: false
    pretty_permalinks: true
    htaccess_extra_rules: true
    
    ### wp-database ###
    
    extension: mysqli
    server_version: 5.7.38-log
    client_version: mysqlnd 7.4.33
    max_allowed_packet: 67108864
    max_connections: 3000
    
    ### wp-constants ###
    
    WP_HOME: undefined
    WP_SITEURL: undefined
    WP_CONTENT_DIR: /homepages/38/d780433205/htdocs/imago/wp-content
    WP_PLUGIN_DIR: /homepages/38/d780433205/htdocs/imago/wp-content/plugins
    WP_MEMORY_LIMIT: 40M
    WP_MAX_MEMORY_LIMIT: 912M
    WP_DEBUG: false
    WP_DEBUG_DISPLAY: true
    WP_DEBUG_LOG: false
    SCRIPT_DEBUG: false
    WP_CACHE: true
    CONCATENATE_SCRIPTS: undefined
    COMPRESS_SCRIPTS: undefined
    COMPRESS_CSS: undefined
    WP_ENVIRONMENT_TYPE: Nicht definiert
    DB_CHARSET: utf8
    DB_COLLATE: undefined
    
    ### wp-filesystem ###
    
    wordpress: writable
    wp-content: writable
    uploads: writable
    plugins: writable
    themes: writable
    
    ### perfopsone_objectcache ###
    
    product: Database transients
    
    ### perfopsone_opcache ###
    
    product: Zend OPcache 7.4.33
    directive_opcache.enable: true
    directive_opcache.enable_cli: false
    directive_opcache.use_cwd: true
    directive_opcache.validate_timestamps: true
    directive_opcache.validate_permission: false
    directive_opcache.validate_root: false
    directive_opcache.dups_fix: false
    directive_opcache.revalidate_path: false
    directive_opcache.log_verbosity_level: 1
    directive_opcache.memory_consumption: 33554432
    directive_opcache.interned_strings_buffer: 8
    directive_opcache.max_accelerated_files: 3000
    directive_opcache.max_wasted_percentage: 0.05
    directive_opcache.consistency_checks: undefined
    directive_opcache.force_restart_timeout: 180
    directive_opcache.revalidate_freq: 180
    directive_opcache.preferred_memory_model: undefined
    directive_opcache.blacklist_filename: undefined
    directive_opcache.max_file_size: undefined
    directive_opcache.error_log: undefined
    directive_opcache.protect_memory: false
    directive_opcache.save_comments: true
    directive_opcache.enable_file_override: false
    directive_opcache.optimization_level: 2147401727
    directive_opcache.lockfile_path: /tmp
    directive_opcache.file_cache: /kunden/homepages/38/d780433205/htdocs/.opcache
    directive_opcache.file_cache_only: true
    directive_opcache.file_cache_consistency_checks: true
    directive_opcache.file_update_protection: 2
    directive_opcache.opt_debug_level: undefined
    directive_opcache.restrict_api: undefined
    directive_opcache.huge_code_pages: false
    directive_opcache.preload: undefined
    directive_opcache.preload_user: undefined
    status_opcache_enabled: false
    status_file_cache: /kunden/homepages/38/d780433205/htdocs/.opcache
    status_file_cache_only: true
    
    ### opcache-manager ###
    
    version: 2.8.0
    use_cdn: undefined
    use_apcu: 1
    script_in_footer: undefined
    display_nag: undefined
    reset_frequency: never
    analytics: 1
    history: 21
    metrics: undefined
    warmup: 1
    flash_invalidate: undefined
    flash_warmup: undefined
    adminbar: 1
    
    

    Your website uses transient databases. You should consider using a dedicated object caching mechanism like APCu, Memcached or Redis to improve your website speed.

    Is there a connection? I would be very happy about support. The website is still in maintenance mode. Here is the website health report.

    Many thanks and greetings
    Annett

    The page I need help with: [log in to see the link]

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author Pierre Lannoy

    (@pierrelannoy)

    Hello Annett!
    Sorry to hear that…
    May I ask you if you have activated opcache analytics and, if so, if you can share with me some screenshots of this.

    Thanks.
    Pierre

    btw, the sentence about caching mechanism is not relevant on your issue, for now I will considerate it as “uncorrelated”.

    Thread Starter wildwuchs123

    (@wildwuchs123)

    Hallo Pierre.
    Yes, I have enabled Opcache Analytics. Unfortunately, I can’t find a way to insert a screenshot here in the forum. I am trying to paste text here and hope the display works for you..
    Thank you for your support.

    Obtaining statistics about OPcache usage
    You can get OPcache analytics for today (compared with yesterday). To do that, use the?wp opcache analytics?command.
    By default, the outputted format is a simple table. If you want to customize the format, just use?--format=<format>. Note if you choose?json?or?yaml?as format, the output will contain full data and metadata for the current day.
    Examples
    To display OPcache analytics, type the following command:
    pierre@dev:~$ wp opcache analytics
    +--------------+-----------------------------------------------+-------+--------+-----------+
    | kpi          | description                                   | value | ratio  | variation |
    +--------------+-----------------------------------------------+-------+--------+-----------+
    | Hits         | Successful calls to the cache.                | 1.9M  | 99.9%  | +0.02%    |
    | Total memory | Total memory available for OPcache.           | 192MB | 42.42% | -5.53%    |
    | Keys         | Keys allocated by OPcache.                    | 3K    | 15.45% | +9.14%    |
    | Buffer       | Buffer size.                                  | 6MB   | 99.08% | +0.84%    |
    | Availability | Extrapolated availability time over 24 hours. | 24 hr | 100%   | 0%        |
    | Scripts      | Scripts currently present in cache.           | 2.3K  | -      | -9.44%    |
    +--------------+-----------------------------------------------+-------+--------+-----------+
    
    Getting OPcache Manager status
    To get detailed status and operation mode, use the?wp opcache status?command.
    Note this command may tell you OPcache is not activated for command-line even if it's available for WordPress itself. It is due to the fact that PHP configuration is often different between command-line and web server.
    Nevertheless, if OPcache is available for WordPress, other OPcache Manager commands are operational.
    Managing main settings
    To toggle on/off main settings, use?wp opcache settings <enable|disable> <analytics|metrics>.
    If you try to disable a setting, wp-cli will ask you to confirm. To force answer to yes without prompting, just use?--yes.
    Available settings
    	?	analytics: analytics feature
    	?	metrics: metrics collation feature
    Example
    To disable analytics without confirmation prompt, type the following command:
    pierre@dev:~$ wp opcache settings disable analytics --yes
    Success: analytics are now deactivated.
    Forced invalidation
    To initiate a forced invalidation, use?wp opcache invalidate.
    This invalidation will be done at the next scheduled cron.
    Example
    To invalidate files without confirmation prompt, type the following command:
    pierre@dev:~$ wp opcache invalidate --yes
    Success: invalidation scheduled to start in less than 5 minutes.
    Forced warm-up
    To initiate a forced invalidation followed by a warm-up, use?wp opcache warmup.
    The invalidation and warm-up will be done at the next scheduled cron.
    Example
    To invalidate and warm-up files without confirmation prompt, type the following command:
    pierre@dev:~$ wp opcache warmup --yes
    Success: invalidation and warmup scheduled to start in less than 5 minutes.
    Misc flags
    For most commands, OPcache Manager lets you use the following flags:
    	?	--yes: automatically answer "yes" when a question is prompted during the command execution.
    	?	--stdout: outputs a clean STDOUT string so you can pipe or store result of command execution.
    It's not mandatory to use?--stdout?when using?--format=count?or?--format=ids: in such cases?--stdout?is assumed.
    Note OPcache Manager sets exit code so you can use?$??to write scripts.?To know the meaning of OPcache Manager exit codes, just use the command?wp opcache exitcode list.
    Plugin Author Pierre Lannoy

    (@pierrelannoy)

    OK. So it’s working as expected.
    May I ask you where (and after what operation) you get the message “OPcache is not enabled on this site.”?
    Thanks

    Thread Starter wildwuchs123

    (@wildwuchs123)

    Thank you very much for the quick reply and the patient support.
    
    The message "OPcache is not enabled on this site. There's nothing to see here." was shown to me in OPcache Management after I invalidated the page. The message persists.
    I'm happy about your message that the OPCache obviously works despite the error message.
    
    What confuses me as a layman is the message about the health of the website. "A persistent object cache makes your site's database more efficient, resulting in faster load times because WordPress can retrieve your site's content and settings much faster.
    
    Your hosting provider can tell you if a persistent object cache can be enabled for your site."
    
    and
    
    "Your site uses database transient. You should consider using a dedicated object caching mechanism, like APCu, Memcached or Redis, to improve your site's speed."
    
    
    Doesn't that contradict a working OP cache?
    
    Thank you and Happy Christmas Holidays.
    Plugin Author Pierre Lannoy

    (@pierrelannoy)

    Hello @wildwuchs123 !

    No, it doesn’t contradict:
    – OPCache is a (PHP) code cache: it precompiles your PHP files to accelerate PHP execution
    – APCu / Memcached / Redis are objects cache: it accelerate access to objects handled by PHP (and so, SQL queries too)

    They are different types of caches. Both are recommended, because their “effects” are cumulative…

    Hope it helps ??

    Thread Starter wildwuchs123

    (@wildwuchs123)

    
    Then I'm relieved that everything works and close the topic.
    Many thanks for the great support and all the best for the future.
Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘OPcache is not enabled on this site.’ is closed to new replies.