• Resolved schevetosti

    (@schevetosti)


    Since the last update this plugin is generating a debug log. We got notified by our website monitor.

    The log says;

    07/25/24 07:20:51 - ? Failed to connect Memcached server!
    07/25/24 07:21:52 - ? Failed to connect Memcached server!
    07/25/24 07:21:52 - ? Failed to connect Memcached server!
    07/25/24 07:21:52 - ? Failed to connect Memcached server!
    07/25/24 07:23:53 - ? Failed to connect Memcached server!
    07/25/24 07:23:53 - ? Failed to connect Memcached server!
    07/25/24 07:23:53 - ? Failed to connect Memcached server!
    07/25/24 07:25:54 - ? Failed to connect Memcached server!
    07/25/24 07:25:54 - ? Failed to connect Memcached server!
    07/25/24 07:25:54 - ? Failed to connect Memcached server!
    07/25/24 07:27:42 - ? Failed to connect Memcached server!
    07/25/24 07:27:42 - ? Failed to connect Memcached server!
    07/25/24 07:27:42 - ? Failed to connect Memcached server!
    07/25/24 07:27:55 - ? Failed to connect Memcached server!
    07/25/24 07:27:55 - ? Failed to connect Memcached server!
    07/25/24 07:27:55 - ? Failed to connect Memcached server!
    07/25/24 07:28:53 - ? Failed to connect Memcached server!
    07/25/24 07:28:53 - ? Failed to connect Memcached server!
    07/25/24 07:28:54 - ? Failed to connect Memcached server!
    07/25/24 07:28:56 - ? Failed to connect Memcached server!
    07/25/24 07:28:56 - ? Failed to connect Memcached server!
    07/25/24 07:29:56 - ? Failed to connect Memcached server!

    And some other litespeed lines.

    Toolbox -> Debug Settings -> Debug Log is off

    I don’t want this log to be generated.

Viewing 15 replies - 1 through 15 (of 16 total)
  • Plugin Support qtwrk

    (@qtwrk)

    please disable object cache, since you can not connect to Memcached anyway.

    Thread Starter schevetosti

    (@schevetosti)

    @qtwrk Thanks for your reply.

    I apologize if my previous message was unclear. Before the last update, either Memcache or the Toolbox -> Debug Settings -> Debug Log setting was functioning correctly.

    However, since the update, I’ve noticed numerous similar posts on this forum, and in each case, you seem to dismiss the issue. It seems highly unlikely that many random website owners coincidentally encountered the same problem simultaneously. This suggests that something in the plugin update may have caused this issue.

    It’s also likely that the posts we’re seeing are from users with external monitoring enabled. Others might only realize there’s a problem once their disk space is exhausted.

    Please reconsider and re-evaluate the last update. Thank you.

    Plugin Support qtwrk

    (@qtwrk)

    please do me a full screenshot on Cache ->Object Cache

    Thread Starter schevetosti

    (@schevetosti)

    Hereby: https://imgur.com/a/4awitR5

    I did turn of tje object cache as you requested.

    Plugin Support qtwrk

    (@qtwrk)

    it still generates log with object cache off ? please check the timestamp on the log , verify it is generated after you turned it off.

    Thread Starter schevetosti

    (@schevetosti)

    @qtwrk The debug log is no longer being generated, but that’s not the core issue. The recent update either broke Memcached or enabled logging even when the debug log setting is turned off.

    Before the latest update, there was no debug log being generated with object cache enabled and debug log set to off. I am using the Digital Ocean pre-configured LiteSpeed image.

    I’m getting this notice in a debug file too. And debug and debug log are disabled in wp-config.

    I still have Object Cache on and the status show Memcached Extension: Enabled.

    Plugin Support litetim

    (@litetim)

    @schevetosti please create a ticket by sending a email to: support at litespeedtech.com
    There were some changes linked to Object cache. By sending this email our dev team will look into.

    ottomek

    (@ottomek)

    @schevetosti Did you receive any solutions when you submitted a help ticket?

    Plugin Support litetim

    (@litetim)

    @ottomek
    The memcache debug will appear only if Litespeed debug is turned on: https://docs.litespeedtech.com/lscache/lscwp/toolbox/#debug-log

    ottomek

    (@ottomek)

    @litetim starting 7/22/24 the sites of mine using Litespeed all have a debug log appearing with ../wp-content/debug.log many entries for:
    Failed to connect Memcached server!

    Toolbox -> Debug Settings -> Debug Log is “OFF”
    wp-config: ( ‘log_errors’, ‘Off’ ); and ( ‘WP_DEBUG’, false );

    Litespeed >> Object Cache
    Status
    Memcached Extension: Enabled
    Redis Extension: Enabled
    Connection Test: Failed

    Maybe it would be better if I open a support ticket with the email you provided above?

    Plugin Support qtwrk

    (@qtwrk)

    yes please

    Plugin Support litetim

    (@litetim)

    Do you have option: https://docs.litespeedtech.com/lscache/lscwp/cache/#object-cache turned ON?

    • This reply was modified 3 months ago by litetim. Reason: spelling fix
    ottomek

    (@ottomek)

    Hi,

    Good news from my end. I opened a support ticket with my web host (A2 Hosting) and they confirmed that there was a misconfiguration on the web hosting server. “After reviewing your site’s configuration, it appears that Memcached was set up incorrectly. Our shared and reseller servers use a socket for Redis and Memcached, but your configuration was set to use localhost on port 11211”

    So they updated some settings and now Litespeed Object Cache is working and no more debug log errors appearing.

    Plugin Support litetim

    (@litetim)

    @ottomek Good that the issue was resolved

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