Facebook
Twitteryes in my current settings server is non functional. As soon as i turn on my server or turn off the maintenance mode the cpu reaches 100% within 2-5 minutes
-
Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
-
We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies! -
The BIND DNS server has already been deprecated and removed from Plesk for Windows.
If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release. -
The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
Issue Huge load average, uninterruptible state
- Thread starter MMagnani
- Start date
Last edited:
Thanks! I thought the changelog he posted was from 18.0.34, so was a bit frustrated when it didn't work.
Works like a charm on 35. Cheers to the Plesk team.
Hello guys @Dave W @john0001
I am still facing cpu spike issue even after the updating to 18.0.35.
Do I need to change any other configuration after increasing innodb_log_file_size as I have increased that. I kind of feel like it's some kind of bottleneck between mysql and php. Mysql processes are consumed around 20-24% and remaining 70% occupied by php-fpm processes.
I am still facing cpu spike issue even after the updating to 18.0.35.
Do I need to change any other configuration after increasing innodb_log_file_size as I have increased that. I kind of feel like it's some kind of bottleneck between mysql and php. Mysql processes are consumed around 20-24% and remaining 70% occupied by php-fpm processes.
It should be a bug in plesk. Many people are saying the same that after 18.0.33 update the site just got slow.
I am not able to keep site live for more than a month, I want to use plesk but this issue/bug is making me think about migrating.
Please help.
Just now checked here bug
What "bug" are other people reporting? The thread list you linked doesn't have anyone with similar issues. I've gone through .35 extensively and run .34 on production. There are no performance issues that I know of.
No bug here either. It's definitely an issue with the site(s).
@omkarmore What steps have you taken to analyze your scripts, e.g. what exactly they are doing and where they are spending their cpu time?
@omkarmore What steps have you taken to analyze your scripts, e.g. what exactly they are doing and where they are spending their cpu time?
It's the php-fpm and mysql processes that accumulate cpu resources.
I tried plesk repair all
I tried to increase hardware configuration.
I tried to setup a fresh plesk install and migrate the site back but same issue persists.
Because it is the same site. It has nothing to do with the services. PHP is not a Plesk invention, neither is the PHP-FPM service. The problem is a script that is consuming a lot of cpu power. You'll for sure find entries in your access_log or error_log that point you to the right source.
Yes, you are right, I read somewhere that some scheduled cron jobs might be causing the cpu power consumption. But how can I check which scripts are causing that.
I am getting all of this over the error log (70007) the timeout specified has expired.
I am getting following entries during the time cpu usage is high:
127.0.0.1 - - [27/Apr/2021:00:51:01 +0530] "POST /modules/monitoring/public/index.php/EloR
CGx39312US-m3QvZVQfFDxCxgRRUe5BVV-W4/query HTTP/1.1" 200 116 "-" "Go-http-client/1.1" "-"'
/modules/monitoring/public/index.php/EloRCGx39312US-m3QvZVQfFDxCxgRRUe5BVV-W4/query' '' '/
opt/psa/admin/htdocs'
127.0.0.1 - - [27/Apr/2021:00:51:01 +0530] "POST /modules/monitoring/public/index.php/EloR
CGx39312US-m3QvZVQfFDxCxgRRUe5BVV-W4/query HTTP/1.1" 200 123 "-" "Go-http-client/1.1" "-"'
/modules/monitoring/public/index.php/EloRCGx39312US-m3QvZVQfFDxCxgRRUe5BVV-W4/query' '' '/
opt/psa/admin/htdocs'
127.0.0.1 - - [27/Apr/2021:00:51:03 +0530] "POST /modules/monitoring/public/index.php/EloR
CGx39312US-m3QvZVQfFDxCxgRRUe5BVV-W4/query HTTP/1.1" 200 117 "-" "Go-http-client/1.1" "-"'
/modules/monitoring/public/index.php/EloRCGx39312US-m3QvZVQfFDxCxgRRUe5BVV-W4/query' '' '/
opt/psa/admin/htdocs'
127.0.0.1 - - [27/Apr/2021:00:51:09 +0530] "POST /modules/monitoring/public/index.php/EloR
CGx39312US-m3QvZVQfFDxCxgRRUe5BVV-W4/query HTTP/1.1" 200 124 "-" "Go-http-client/1.1" "-"'
/modules/monitoring/public/index.php/EloRCGx39312US-m3QvZVQfFDxCxgRRUe5BVV-W4/query' '' '/
opt/psa/admin/htdocs'
I tried using it but no luck.
Just in case can deleting access log cause any such issues, as I may have by mistakenly deleted the access log from filemanager. I don't see any access log present in logs folder. I have access ssl log present.
The one I shared above was present at location /var/log/plesk/httpsd_access_log
Error_log, access_ssl_log, proxy_error_log are present but access_log not present
That's normal if you have everything on https.
How big is your database? Have you tried mysqltuner?
It sounds to me like you just started getting more traffic that coincided with a Plesk update. If you don't believe that is the case, I'd look at hiring an external developer/sysadmin to take a look.
