Recent content by omkarmore

I found this piece regarding bad bots. [Sometimes, if you are experiencing poor performance, it is because you are being attacked by Internet bots. The reason for these attacks is that they are trying to find a security bug in your application code or in the software itself. An example of a bot...

In case it's the crawlers/bots then where can we start with?

It's just under 100mb. I tried optimizing database.

Error_log, access_ssl_log, proxy_error_log are present but access_log not present

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...

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" "-"'...

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.

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.

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

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...

yes 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

A)Not before the update as far as i remember, at max I may have changed php 7.3 to 7.4 version. B) After the issue, I tried using all possible combinations of php handlers with php versions and even tried to make nginx as primary server but in every combination I have been facing same issue.

@Dave W @john0001 @IgorG I just saw the changelog of 18.0.33 after which I am facing the 100% cpu spike due to php fpm processes. Can the changes below cause the issue? Change log related to php-fpm in 18.0.33 >>Plesk now preserves the following custom settings of the [php-fpm-pool-settings]...

No, I mean to say the multiple php-fpm processes are created and these processes causing 100% cpu spike. PFA screenshot

Yes these are the logs around time when cpu is high