• Resolved Vanderlindemedia

    (@jvanderlinde)


    Hi,

    An update struck one of my servers for some reason killing the Redis instance, or at least, it’s a nasty bug where some redis instances simply do no longer work that are within CageFS it seems. We’re actively trying to resolve this with Cloudlinux. It seems a update from RHEL caused issues with the above.

    But – this caused approx 15+ websites to crash – due to non existing Redis service not being available, and the websites that where running litespeed Caching and using object cache still proceeded to work (just without redis). It means that for whatever reason Redis is not available, the site simply won’t start using this plugin.

    I would suggest a fail-safe fallback, because i had to plunge into hundreds of sites to learn i had approx 15 running with above plugin that failed to start.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Till Krüss

    (@tillkruess)

    The object cache in WordPress must be online at all times, just like SQL. Otherwise the cache data will go stale and will cause data loss.

    Thread Starter Vanderlindemedia

    (@jvanderlinde)

    Yes,

    In a fortunate update, that either happened through Directadmin or REL through Cloudlinux, Redis instance got nuked from multiple to a single one, making every website that used to run Redis crash that where using the Redis Object Cache plugin. Sites with Litespeed only did not crash – thus making it still operate but without the use of Redis.

    I would suggest there is a fallback once the Redis is no longer available (for whatever reason).

    Plugin Author Till Krüss

    (@tillkruess)

    No, Litespeed is vulnerable to data corrupting.

    I suggest you set up supervisord and monitoring service to keep an eye on your infrastructure if it’s that critical.

    Thread Starter Vanderlindemedia

    (@jvanderlinde)

    Well, at least it works,

    And it won’t crash the complete website after Redis seems to fail.

    So i assume your not taking this bug request then.

Viewing 4 replies - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.