Fatal error Uncaught RedisException

  • Resolved saens

    (@saens)


    4 years, 7 months ago

    I’m on 2.1.9.
    Using only the page caching with Redis.

    [Mon Jan 10 10:23:15.371829 2022] [lsapi:error] [pid 4148085:tid 140492356359936] [client 109.37.147.9:20430] [host domain.xyz] Backend fatal error: PHP Fatal error: Uncaught RedisException: LOADING Redis is loading the dataset in memory in /home/deb130999/domains/domain.xyz/public_html/wp-content/plugins/w3-total-cache/Cache_Redis.php:91\nStack trace:\n#0 /home/deb130999/domains/domain.xyz/public_html/wp-content/plugins/w3-total-cache/Cache_Redis.php(91): Redis->get('w3tc_753224224_...')\n#1 /home/deb130999/domains/domain.xyz/public_html/wp-content/plugins/w3-total-cache/PgCache_ContentGrabber.php(281): W3TC\\Cache_Redis->get_with_old('c062d65900c1627...', '')\n#2 /home/deb130999/domains/domain.xyz/public_html/wp-content/plugins/w3-total-cache/PgCache_ContentGrabber.php(216): W3TC\\PgCache_ContentGrabber->_extract_cached_page(false)\n#3 /home/deb130999/domains/domain.xyz/public_html/wp-content/advanced-cache.php(37): W3TC\\PgCache_ContentGrabber->process()\n#4 /home/deb130999/domains/domain.xyz/public_html/wp-settings.php(95): include('/home/deb130999...')\n#5 /home/deb130999/domains/domain.xyz/public_html/wp-config.php(131): require_once('/home/deb1309 in /home/deb130999/domains/domain.xyz/public_html/wp-content/plugins/w3-total-cache/Cache_Redis.php on line 91\n

    • This topic was modified 4 years, 7 months ago by saens.
Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Contributor Marko Vasiljevic

    (@vmarko)

    4 years, 7 months ago

    Hello @saens

    Thank you for reaching out and I am happy to assist you with this.
    It seems like there is a problem with Redis Keys and fetching the cached data.
    When have you started experiencing the problem, I.E. Have you taken any steps before the issue occurred?
    Have you tried restarting the redis server?
    Thanks!

    Thread Starter saens

    (@saens)

    4 years, 7 months ago

    Hi, thanks for the quick response.

    I was able to go back to december 15th in my logging. There I also found this error.
    REDIS server is restarted quite frequently, so there’s definitely been a restart since then (dec 15th).

    The config of W3TC is not changed since a few months. I don’t know about the REDIS-server.

    Is this something I should take up with my hosting?

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    4 years, 7 months ago

    Hello @saens

    Thank you for yoru feedback.
    Please check the configuration of the Redis server with your hosting provider and try to restart the Redis server again.
    Thanks!

    Thread Starter saens

    (@saens)

    4 years, 7 months ago

    “Please check the configuration of the Redis server ”
    This is a bit generic to me. What specific properties or settings should they check?

    • This reply was modified 4 years, 7 months ago by saens.
    Thread Starter saens

    (@saens)

    4 years, 7 months ago

    I’ve contacted my hosting. They say this error (LOADING Redis is loading the dataset in memory ) is caused when Redis is reloading or a slave reconnects.

    Is it possible to have a graceful handling of this situation in w3tc? Maybe skip the cache for this request?

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    4 years, 7 months ago

    Hello @saens

    I’ve never seen this before and looking at the comment of the hosting support, it appears that the redis server is initializing and the error will disappear later, once done.
    I’ll see if I can make more tests and get back to you.
    Thanks!

    Thread Starter saens

    (@saens)

    4 years, 6 months ago

    “it appears that the redis server is initializing and the error will disappear later, once done.”
    That’s kinda obvious.

    It seems only logical that if the redis server is not available, then the redis page caching isn’t available and a fresh non-cached page should be served. The current situation leads to a page 500 1-2-3 times a day.

    I’m sure it can be avoided by the w3tc plugin to handle this scenario (=redis is initializing) properly?

Viewing 7 replies - 1 through 7 (of 7 total)

The topic ‘Fatal error Uncaught RedisException’ is closed to new replies.