The following memcached servers are not responding or not running

Hello @bcvcbhqyxcgakhh

Thank you for reaching out and I am happy to help!

Check the service at the CLI/SSH: memcached-tool 127.0.0.1:11211 display and memcached-tool 127.0.0.1:11211 stats.

telnet 127.0.0.1 11211

should communicate with memcache and respond to status commands etc

Look if the service is running: ps afux | grep memc

restart the service if needed (as root/sudo): service memcached restart.

Thanks!

When we executed your code:

Ssl Jul04 0:13 /usr/bin/memcached -p 11211 -u memcached -m 64 -c 1024 -l 127.0.0.1 -U 0

Our memcached configuration seems to be set up to listen only on the local interface 127.0.0.1 and to disable UDP (-U 0). This setup is generally secure for most use cases since it limits access to the memcached server to only local connections, preventing external access.

Is this an issue as your plugin reports:

The following memcached servers are not responding or not running:

• Object Cache: 127.0.0.1:11211.
• Page Cache: 127.0.0.1:11211.

• This reply was modified 4 months, 2 weeks ago by bcvcbhqyxcgakhh.

Hello @bcvcbhqyxcgakhh

Thank you for your feedback.
Have you tried restartin the memcached service and can you please share the screenshot of the memcached setup in Object Cache settings or Page Cache section?
Thanks!

Sorry, support is not enabled in this forum as it does not contain any image attachment.
Memcached hostname:port / IP:port: 127.0.0.1:11211
Test: Request failed
Which value should be due to mentioned secured ports?
/usr/bin/memcached -p 11211 -u memcached -m 64 -c 1024 -l 127.0.0.1 -U 0
Our memcached configuration seems to be set up to listen only on the local interface 127.0.0.1 and to disable UDP (-U 0). This setup is generally secure for most use cases since it limits access to the memcached server to only local connections, preventing external access.

Is this an issue as your plugin reports failed request but

Page caching via Memcache is currently enabled.

Object caching via Memcache is currently enabled.

• This reply was modified 4 months, 2 weeks ago by bcvcbhqyxcgakhh.
• This reply was modified 4 months, 2 weeks ago by bcvcbhqyxcgakhh.

Thank you for the message! When we check and verify, all is working on the server:

Memcached is running correctly and listening on the expected port (11211) with TCP enabled.

• The -U 0 option is not an issue in this context as it simply disables UDP support, which is common in many configurations to avoid unnecessary network traffic.
• It is a plugin issue.

Hello @bcvcbhqyxcgakhh

Can you please check and confirm that the phpmemcached extension is used?

Also, pelase restart the memcached service. If this was plugin issue, then the issue will be presenting on all websites using memcached whic is not the case.

Please make sure to check this video for more details.

Thanks!

We have installed a plugin. It reports now Plugin could not be activated because it triggered a fatal error. Which permission folder causes this fatal error? Where is pushed error_log, specifically for WP Total Cache as we are using CloudLinux 8?

We have tested and all plugins were inactive.

Due to security, folders are moved to another path using WordPress codex inside a config PHP file:

//define(‘WP_CONTENT_DIR’, $_SERVER[‘DOCUMENT_ROOT’] . ‘/content’);
//define(‘WP_CONTENT_URL’, ‘https://example.com/content’);

Your plugin does not support and detect moved folders and errors are not shown as your plugin pushes FATAL ERROR message without any track of errors.

• This reply was modified 3 months, 1 week ago by bcvcbhqyxcgakhh.