paul

It was actually even simpler…I was in the visual editor, not the text editor. The semicolon was an issue for sure, so thanks for that.

Inconclusive. The dashboard showed three critical errors but when the detail page loaded it was all clear.

It was slow before I installed the caching methods so I will assume it will still be slow if I remove them. If I see the error again, I can try it. I just looked and Site Health passed all tests. Unusual.

Interesting…I see some traffic/page requests.

grep -c wordpress /var/log/httpd/httpd-access.log
255

Is this variant on cron a new thing? Seems like cron, read as a function of time for the execution of jobs, is not a great name. System cron runs even w no users logged in where this is driven by user interaction and not all that accurately even then. Not sure this explains why the site health page loads to slowly or why I needed to install two different caching methods to turn off warnings about them. On the one hand WP is not running jobs due to what it perceives as a low page requests but on the other, it squawks about the need for caching to improve performance/responsiveness?

I think the performance/responsiveness issues are baked in. These are new with 6.x. This system is lightly loaded and shouldn’t have any issues returning pages. If there are issues in the stack (maybe php-fpm or mariadb or nginx need some tuning?) it would be useful to have some tips in resolving those.

https://paulbeard.org/wordpress will do it. Site health is very slow to load, another artifact of 6.x.

My server is very lightly loaded and the wordpress stack (php-fpm, mariadb, nginx) is the main thing it runs. Something happened in this latest release that’s not right and I wonder why it’s taking so long to find it/figure it out. I have been seeing a lot of these errors:

[02-Dec-2022 20:49:28] WARNING: [pool www] child 9811, script '/usr/local/www/wordpress/index.php' (request: "GET /wordpress/index.php") executing too slow (10.738534 sec), logging
[02-Dec-2022 23:27:20] WARNING: [pool www] child 10035, script '/usr/local/www/wordpress/index.php' (request: "GET /wordpress/index.php") executing too slow (10.893408 sec), logging

Adding caching seems to have helped but I never needed that before. Not sure why I need to now add a redis process for a low traffic site just to get pages to load.

Seeing this also…something in the 6.x code base isn’t right, because I never saw these errors and warning about caching before. No one wants to see errors on their site health page they can’t resolve or understand. I know cron is working fine on my site (I self-host and many other jobs that use cron work fine). Not sure how wp-cron works or how it interacts with system cron.

it’s known issue as health tool doesn’t check our hesaders

Is there a reason why WP hasn’t pushed out an update to resolve this? I have been seeing repeated errors about object and page caching and cron jobs that never existed before 6.1 shipped and it all seems to come back to issues w/in WP core, like this one. Pretty disappointing that a site with no issues is now throwing errors that either don’t exist or don’t matter, all due to some poorly designed or implemented poetry. Bad rhymes, weak scansion, whatever language the WP teams chooses to use, it needs work.

can this “feature” be removed or made optional in the next release of WP? It’s not helpful to see errors on your Site Health screen that aren’t really errors that you can’t turn off.

Fatal error: Cannot redeclare wp_cache_add() (previously declared in /usr/local/www/wordpress/wp-content/object-cache.php:60) in /usr/local/www/wordpress/wp-content/plugins/memcached/object-cache.php on line 19

Same error here. Can’t say I like the Site Health screen telling me I need an object cache when none of the ones I have tried are detected or install cleanly. Can that test be disabled?

Not any time soon, after all this. Jetpack was the reason everything went pear-shaped, as described above. Not in a hurry to gamble on a repeat of that.

I was able to recover by exporting to a WXR file and importing into a new wordpress instance. Not ideal but it works. One of the benefits of self-hosting is that you get full control but you’re also in full control.

Not gonna install jetpack and friends just yet. Once bitten, twice shy…

• This reply was modified 2 years, 4 months ago by paul.

Kind of at a loss here…I just downloaded and installed a frech copy of WP 6.0.3 and I still see the same issues. The actual site is fine but anything to do with wp-admin spews a ton of errors to the console, I can’t load plugins, the site health screen never finishes loading. I wonder if there is something in the database from the repeated install/remove cycles that has gotten messed up. wp_options had 73 lines that contain “jet” in option_name (308 rows total). Why would the wp-admin pages be so messed up while the site pages are fine?

UPDATE: I have installed a fresh 6.0.2, same issues. I have tested a new install of 6.0.3 in the latest versions of Chrome and Firefox as well as Safari. Same issues recur.

The errors, to recap:
wp-admin’s site health page never finishes loading
adding the jetpack plugin causes all the CSS for wp-admin to be ignored
many javascript errors about jQuery or 404 error for files that are accessible.

Anything else I can try? Kind of annoyed to have just purchased mpl-publisher and between the time I paid for it and trying to use it, these issues are making it inoperable, as well as all the other issues noted.

• This reply was modified 2 years, 4 months ago by paul.

I think this is bigger than jetpack…my javascript console is full of 404 errors that make no sense. The files are where they are referenced. No plugins are loaded. Site health check never completes loading its status.

I think something has gone very wrong here but I don’t see any recent medication dates on files and wp-cli sees no checksum issues. nginx and pgh-fpm config files haven’t changed, based on their modification times.

Also, I added the code block above to create a debug log and none appeared after a few page loads. Not sure I see where the log file is defined unless it’s in the core somewhere.

How can I get jetpack 11.3.x so I can see if it makes any difference?