• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Resolved I get 2000% CPU usage (Plesk mobile app readings)

TradePOS

New Pleskian
Server operating system version
Ubuntu server 20.04
Plesk version and microupdate number
Plesk Obsidian v18.0.46
Hi,
Today my system shows me error number (504 Gateway Time-Out nginx),
when I looked to the Plesk mobile app CPU load average, all the three bars shows over 2000% usage image attached
CPU_load_average.jpeg
after restarting the whole server the bars back to normal between 60 to 40 %
Server Specification:
CPU: Intel(R) Xeon(R) W-2295 CPU @ 3.00GHz (36 core(s))
Version : Plesk Obsidian v18.0.46_build1800220905.16 os_Ubuntu 20.04
OS: Ubuntu 20.04.5 LTS
Is there any log file I can get information from ?
I can use an advice.
thank you very much.
 
Actually I solved this by increasing the value of innodb_buffer_pool_size in the "/etc/mysql/my.cnf" file
I am experiencing high CPU usage and Load due to MySQL. How much memory did you add to the innodb_buffer_pool_size and query_cache_size?
 
I am experiencing high CPU usage and Load due to MySQL. How much memory did you add to the innodb_buffer_pool_size and query_cache_size?
Depending on your setup try doubling the innodb_buffer_pool_size that solved it for me before
 
Back
Top