alriknijdam

I will do this somewhere in the middle of the night when most users are asleep since we’ve already experienced quite some downtime.

I will get back with the results as soon as I’ve done this!

Thank you, I’ll mark this one as resolved and continue in the topic I started earlier.

Placed the code at the bottom of this post inside my functions.php
That settles everything down.. So far…… Hoping it will stay this way..
Strange enough https://example.com/leden/user/activity/favorites/feed/ still shows a RSS feed though, but no longer produces server issues. It also still produces the same 3 php notices

PHP Notice:  Trying to get property of non-object in /wp-includes/class-wp-query.php on line 3736
PHP Notice:  Trying to get property of non-object in /wp-includes/class-wp-query.php on line 3738
PHP Notice:  Trying to get property of non-object in /wp-includes/class-wp-query.php on line 3740

Needless to say I’m still looking for a solution

function wpb_disable_feed() {
wp_die( __('No feed available,please visit our <a href="https://vespa-ciao.nl/">homepage</a>!') );
}
 
add_action('do_feed', 'wpb_disable_feed', 1);
add_action('do_feed_rdf', 'wpb_disable_feed', 1);
add_action('do_feed_rss', 'wpb_disable_feed', 1);
add_action('do_feed_rss2', 'wpb_disable_feed', 1);
add_action('do_feed_atom', 'wpb_disable_feed', 1);
add_action('do_feed_rss2_comments', 'wpb_disable_feed', 1);
add_action('do_feed_atom_comments', 'wpb_disable_feed', 1);
// onderstaande schakelt ook de RSS in de header links uit
remove_action( 'wp_head', 'feed_links_extra', 3 );
remove_action( 'wp_head', 'feed_links', 2 );

Very very happy with this full disclosure!!
I was able to delete everything, using a query containing LIKE '%ai1ec%'

This topic is resolved, thanks again!

Best regards,
Alrik

Is there anything I can do myself to get these notices figured out?
Or do I need to adress them somewhere else?

Best regards,
Alrik

Alright, it has almost been 2 days now so time for an update.
First of all, the advice of @rosehosting had a huge impact on the cpu load of the server, decreasing it more than 50%. Needless to say I’m happy with that!

After repairing ‘wp_options’ the server was stable for a little over 24 hours. During which it kept producing the same PHP Notices as before.

PHP Notice:  Trying to get property of non-object in /wp-includes/class-wp-query.php on line 3736
PHP Notice:  Trying to get property of non-object in /wp-includes/class-wp-query.php on line 3738
PHP Notice:  Trying to get property of non-object in /wp-includes/class-wp-query.php on line 3740

PHP Notice: get_wp_title_rss was called with an argument that is <strong>outdated</strong> since version 4.4.0. Use <code>document_title_separator</code>-filter instead. in /wp-includes/functions.php on line 4045

The query also being the same.

WordPress database error MySQL server has gone away bij query
SELECT l.ID, post_title, post_content, post_name, post_parent, post_author, post_modified_gmt, post_date, post_date_gmt
FROM (
	SELECT wp_posts.ID
	FROM wp_posts
	
	WHERE wp_posts.post_status = 'publish'
		AND wp_posts.post_type = 'reply'
		AND wp_posts.post_password = ''
		AND wp_posts.post_date != '0000-00-00 00:00:00'

	ORDER BY wp_posts.post_modified ASC LIMIT 100 OFFSET 30200
)
o JOIN wp_posts l ON l.ID = o.ID
made by require('wp-blog-header.php'), wp, WP->main, WP->query_posts, WP_Query->query, WP_Query->get_posts, do_action_ref_array, WP_Hook->do_action, WP_Hook->apply_filters, WPSEO_Sitemaps->redirect, WPSEO_Sitemaps->build_sitemap, WPSEO_Post_Type_Sitemap_Provider->get_sitemap_links, WPSEO_Post_Type_Sitemap_Provider->get_posts

Since I’m completely in the dark here and got curious I decided to run the query in phpMyAdmin. Leaving the JOIN part out because I didn’t know if it would make any changes. This gave the following error.
#1248 - Message: Every derived table must have its own alias

After the last server crash the cpu load again saw a huge drop. Earlier the load could easily exceed 200%, at this point it has been rather stable around 30% over 12 hours. Besides from repairing ‘wp_options’ I can’t think of anything that caused the second drop (no changes made).

Is it possible that somehow a bad query is injected. Either by accident or with malicious intend? Looking at the ‘mady by’ part of the query I see a lot of WPSEO Sitemap stuff, might a crawler be the cause?

As this exceeds my knowledge by a mile I might sound a bit stupid, but I’m just trying to understand it 😉

Thanks for the quick reply! I’m not worrying, it’s mainly to help you locate every little thing and fix them 🙂

Best regards,
Alrik