Jonathan Jewell

Hmm, that’s odd. that plugin (QM), unless I have completely misunderstood it, generated this information relating to this plugin (Redis) and its performance. But if that is not right, I apologise.

The Redis page has this: 

Status:	 Not connected
Drop-in:	 Valid
Filesystem:	 Writeable

AND THEN, your diagnostics report this:

Status: Not connected
Client: 
Drop-in: Valid
Disabled: No
Ping: 
Connection Exception: Connection refused [tcp://127.0.0.1:6379] (Predis\Connection\ConnectionException)
Errors: [
    "Connection refused [tcp:\/\/127.0.0.1:6379]"
]
PhpRedis: Not loaded
Relay: Not loaded
Predis: 1.1.9
Credis: Not loaded
PHP Version: 8.1.3
Plugin Version: 2.0.23
Redis Version: Unknown
Multisite: No
Metrics: Disabled
Metrics recorded: null
Filesystem: Working
Global Prefix: "zcIwjRpM"
Blog Prefix: "zcIwjRpM"
WP_REDIS_PREFIX: "bpFkx7r: IVWt$l>SsbuX9$oL?mfCEA(Q*V*;FJ>d|}c1>Gv0yxYE_k8y7sf[2@j"
WP_CACHE_KEY_SALT: "bpFkx7r: IVWt$l>SsbuX9$oL?mfCEA(Q*V*;FJ>d|}c1>Gv0yxYE_k8y7sf[2@j"
Global Groups: [
    "blog-details",
    "blog-id-cache",
    "blog-lookup",
    "global-posts",
    "networks",
    "rss",
    "sites",
    "site-details",
    "site-lookup",
    "site-options",
    "site-transient",
    "users",
    "useremail",
    "userlogins",
    "usermeta",
    "user_meta",
    "userslugs",
    "redis-cache"
]
Ignored Groups: [
    "counts",
    "plugins",
    "themes",
    "blog-details",
    "blog-id-cache",
    "blog-lookup",
    "global-posts",
    "networks",
    "rss",
    "sites",
    "site-details",
    "site-lookup",
    "site-options",
    "site-transient",
    "users",
    "useremail",
    "userlogins",
    "usermeta",
    "user_meta",
    "userslugs",
    "redis-cache",
    "blog_meta"
]
Unflushable Groups: []
Drop-ins: [
    "Query Monitor Database Class v by ",
    "Redis Object Cache Drop-In v2.0.23 by Till Krüss"
]

—

The three here come from additional logging by the QM monitor, which, even if it is not due to your plugin, is attributing the problem to your plugin, and might be of interest to you. If not, no problem, I’m not blaming, just trying to figure out options.

—

Warning stream_socket_client(): Unable to connect to tcp://127.0.0.1:6379 (Connection refused) 1 –
wp-content/plugins/redis-cache/dependencies/predis/predis/src/Connection/StreamConnection.php:127
stream_socket_client()
wp-content/plugins/redis-cache/dependencies/predis/predis/src/Connection/StreamConnection.php:127
Predis\C\StreamConnection->createStreamSocket()
wp-content/plugins/redis-cache/dependencies/predis/predis/src/Connection/StreamConnection.php:178
Predis\C\StreamConnection->tcpStreamInitializer()
wp-content/plugins/redis-cache/dependencies/predis/predis/src/Connection/StreamConnection.php:100
Predis\C\StreamConnection->createResource()
wp-content/plugins/redis-cache/dependencies/predis/predis/src/Connection/AbstractConnection.php:81
Predis\C\AbstractConnection->connect()
wp-content/plugins/redis-cache/dependencies/predis/predis/src/Connection/StreamConnection.php:258
Predis\C\StreamConnection->connect()
wp-content/plugins/redis-cache/dependencies/predis/predis/src/Client.php:215
Predis\Client->connect()
wp-content/object-cache.php:802
WP_Object_Cache->connect_using_predis()
wp-content/object-cache.php:495
WP_Object_Cache->__construct()
wp-content/plugins/redis-cache/includes/diagnostics.php:32
Rhubarb\R\U\Tab->display()
wp-content/plugins/redis-cache/includes/ui/settings.php:59
Rhubarb\R\Plugin->show_admin_page()
wp-includes/class-wp-hook.php:307
do_action(‘settings_page_redis-cache’)
wp-admin/admin.php:259
Plugin: redis-cache
Warning Trying to access array offset on value of type null 1 –
wp-content/object-cache.php:2083
WP_Object_Cache->info()
wp-content/plugins/redis-cache/includes/class-qm-collector.php:55
Rhubarb\R\QM_Collector->process()
wp-content/plugins/query-monitor/classes/Collectors.php:86
do_action(‘shutdown’)
wp-includes/load.php:1100
shutdown_action_hook()
Unknown location`

—

Warning stream_socket_client(): Unable to connect to tcp://127.0.0.1:6379 (Connection refused) 1 –
wp-content/plugins/redis-cache/dependencies/predis/predis/src/Connection/StreamConnection.php:127
stream_socket_client()
wp-content/plugins/redis-cache/dependencies/predis/predis/src/Connection/StreamConnection.php:127
Predis\C\StreamConnection->createStreamSocket()
wp-content/plugins/redis-cache/dependencies/predis/predis/src/Connection/StreamConnection.php:178
Predis\C\StreamConnection->tcpStreamInitializer()
wp-content/plugins/redis-cache/dependencies/predis/predis/src/Connection/StreamConnection.php:100
Predis\C\StreamConnection->createResource()
wp-content/plugins/redis-cache/dependencies/predis/predis/src/Connection/AbstractConnection.php:81
Predis\C\AbstractConnection->connect()
wp-content/plugins/redis-cache/dependencies/predis/predis/src/Connection/StreamConnection.php:258
Predis\C\StreamConnection->connect()
wp-content/plugins/redis-cache/dependencies/predis/predis/src/Client.php:215
Predis\Client->connect()
wp-content/object-cache.php:802
WP_Object_Cache->connect_using_predis()
wp-content/object-cache.php:495
WP_Object_Cache->__construct()
wp-content/plugins/redis-cache/includes/diagnostics.php:32
Rhubarb\R\U\Tab->display()
wp-content/plugins/redis-cache/includes/ui/settings.php:59
Rhubarb\R\Plugin->show_admin_page()
wp-includes/class-wp-hook.php:307
do_action(‘settings_page_redis-cache’)
wp-admin/admin.php:259
Plugin: redis-cache

—

Warning Trying to access array offset on value of type null 1 –
wp-content/object-cache.php:2083
WP_Object_Cache->info()
wp-content/plugins/redis-cache/includes/class-qm-collector.php:55
Rhubarb\R\QM_Collector->process()
wp-content/plugins/query-monitor/classes/Collectors.php:86
do_action(‘shutdown’)
wp-includes/load.php:1100
shutdown_action_hook()
Unknown location`

Hiya,

Yes, everything is updated, and I think that the issue is simply that php8.1 has moved beyond where you are (maybe some more strict syntax). I do not think this is an inconvenience, except having to report it, I cannot see any issues arising from it except that they are identified. If you see any risks in the log that need to be addressed or that mean that I need to turn off the plugin or some function, let me know.

The issue is there in spite of the full updates of all technologies on the site and linked to it. By error log, are you referring to the WordPress or the RankMath or some other one, and if not the main WordPress one, then how do I generate that?

great thanks for replying – is there going to be any particular problem in the meantime with me using the plugin, or that I need to do anything to mitigate? or is this stuff merely a technical issue that will be addressed in time.

oh, I just noticed a whole load of these things too, listed as ‘deprecated’ rather than an big warning error, just in case this might be related (well, regardless of that, but I am putting it here in case they are linked):

Return type of Requests_Utility_CaseInsensitiveDictionary::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

OR the same thing, but with that CAseInsensitiveDictionary (kind of ironic there) with the Requests_Cookie_Jar (linked to the items below)

There are several of these, only difference being the page numbers (where the page numbers at the end of these are what I have put X or Y for):

wp-includes/Requests/Utility/CaseInsensitiveDictionary.php:X
wp-includes/Requests/Cookie/Jar.php:Y

where the page numbers for:

X are 40, 51, 68, 82, 91
Y are 63, 73, 89, 102, 111

Hope this is useful feedback for you, and keen to know if there’s anything deadly here that means I should switch some setting on/off or uninstalling the plugin.

Thanks, Jonathan

• This reply was modified 3 years ago by Jonathan Jewell. Reason: just noticed a small difference in the error that I needed to add

Thanks so much. Really appreciate you confirming that and that you’re on it and going to deal with it. And such a quick response.

Great work on a great plugin!

Jonathan

ah, thanks for letting me know. Well, I have gone through the entire list, looked for the plugins and reported the errors to everyone who ‘gets a mention’ there. So if they get onto their ones, I’ll let you know when these ones disappear and what is left over afterwards.

Presumably the easiest way to isolate it would be to turn off the plugins (or switch the theme) and see which ones disappear? Or is there a better (quicker, faster, more reliable, less disruptive) way to do it? Or is there a more useful set of data I could send you that will help you to identify it (or where I can look to find it myself) to isolate what is going on?

ah, okay my question is similiar in nature but seems to be slightly different ones appearing for me now, even with the latest one:

https://snipboard.io/vrpocI.jpg

Sorry, can’t find the button to put screenshot in, and just will not paste, so have to send you to the snipboard.io place (please scan it if you’re not sure about it!), or I can email it to you.

I actually think this appeared only after I got the more up to date version of query monitor, but maybe I’m wrong on that.

Really appreciate your thoughts and would also be interested in knowing in the meantime, what this might mean in terms of any risks/effects that might be relevant using it in the meantime.

Thank you!

Wait, sorry, there’s now a new thing showing (in addition) when I went back (not sure if I did anything in particular. The link on snipboard is here*:

https://snipboard.io/4lMKrp.jpg

IF there’s something in there that might add some value, let me know. I can send other log things if there’s a value in that, and you can tell me where I go to find them.

* also, just to also add, as I now see it, the Zend framework (in the line: Opcode cache in use: Zend OPcache) is mentioned but without any indication of an issue. Just in case it relates (and I have no idea), I know in the past I have had error pages show up on other WordPress installations – nothing on this one – but in case I’m doing something more generally relating to that, I’ll mention it. Could be a red herring though.

Thanks.