CPU is maxing out at 88%

My hosting provider contacted me the other day to tell me that I’ve maxed out my resources on one of my sites. At the time there was no real reason why. The site doesn’t get a ton of traffic nor is it very heavy graphicwise. I disabled all of the plugins, reinstalled my theme and even deleted everything to reinstall a backup from Sept 1st.

Yet, I am still having the issue. My CPU is maxing out at 88%. Any ideas?

My host support team provided me with the following details:

We have checked into the current running processes from the user. There are 3-4 processes constantly running at any given time. The pattern we see with them all is constant system calls to files that do not exist but belong to the meta-box plugin.

access(“/home/…/public_html/wp-content/plugins/meta-box/inc/ltpress.php”, F_OK) = -1 ENOENT (No such file or directory)
access(“/home/…/public_html/wp-content/plugins/meta-box/inc/press.php”, F_OK) = -1 ENOENT (No such file or directory)
access(“/home/…/public_html/wp-content/plugins/meta-box/inc/walkers/.php”, F_OK) = -1 ENOENT (No such file or directory)
write(1, “]]></content:encoded>\n\t\t\t<wfw:co”…, 8450) = 8450
access(“/home/…/public_html/wp-content/plugins/meta-box/inc/ltpress.php”, F_OK) = -1 ENOENT (No such file or directory)
access(“/home/…/public_html/wp-content/plugins/meta-box/inc/press.php”, F_OK) = -1 ENOENT (No such file or directory)
access(“/home/…/public_html/wp-content/plugins/meta-box/inc/walkers/.php”, F_OK) = -1 ENOENT (No such file or directory)
write(1, “]]></content:encoded>\n\t\t\t<wfw:co”…, 8450) = 8450
access(“/home/…/public_html/wp-content/plugins/meta-box/inc/ltpress.php”, F_OK) = -1 ENOENT (No such file or directory)
access(“/home/…/public_html/wp-content/plugins/meta-box/inc/press.php”, F_OK) = -1 ENOENT (No such file or directory)
access(“/home/…/public_html/wp-content/plugins/meta-box/inc/walkers/.php”, F_OK) = -1 ENOENT (No such file or directory)

We do not see traffic requesting those files directly. You should contact the plugin developer about this behavior to see if there is a known issue or possibly setting change that can resolve this.