slacknews.org

tification we would like to inform you that your account mini-z.ru consumes a very high percentage of the server resources and thus affects the performance of the whole shared server.

In order to maintain the stability of the server, we had to temporarily limit the shared server resources your account can use. Please note that this may result in occasional „Resource temporary unavailable“ error messages shown on your website.

We are very much aware of the inconvenience this issue may cause you, so we would like to take a moment and explain the reasons for our actions: as you know, your account is hosted on a shared hosting server and thus sharing the resources of the server with other customers’ accounts. Even though our shared servers are well optimized, the nature of the shared server is such that no matter how powerful or how well optimized the machine is, it is possible that one user and even one application consumes most of the server resources and overloads the machine. Thus all other accounts on the server stop responding and become inaccessible.

In order to prevent server overload, the source of the high load has to be isolated so that it cannot affect the overall server performance. This is a standard procedure used by all shared hosting providers.

We have conducted a detailed investigation of the reasons for the high resource consumption and it turned out that a script executes slow queries towards its database, which eventually hogs the server. The server tries to execute your slow queries while putting other processes in the queue until some memory is freed. While they are waiting however, they stack up and cause further problems.

We believe you are not causing high server load intentionally and we will do our best to assist you so that your site can be fully functional again as soon as possible.

As mentioned before, the problem is caused by slow queries executed towards your application’s database. There can be many reasons for slow database queries, but the following 3 are the most common ones:

1. Large database
2. Not well written scripts
3. Large number of internal links that query the database directly.

Here are some of the database queries that are slow and consume a lot of server resources:

Executed 1 min ago for 12 sec on Database –> miniz678_db.
SELECT * FROM wp_comments c LEFT JOIN wp_posts p ON c.comment_post_ID = p.ID WHERE p.post_status != ‘trash’ ORDER BY c.comment_date_gmt DESC LIMIT 2000, 50
Executed 1 min ago for 2 sec on Database –> miniz678_db.
SELECT * FROM wp_comments c LEFT JOIN wp_posts p ON c.comment_post_ID = p.ID WHERE p.post_status != ‘trash’ ORDER BY c.comment_date_gmt DESC LIMIT 2050, 50
Executed 1 min ago for 2 sec on Database –> miniz678_db.
SELECT * FROM wp_comments c LEFT JOIN wp_posts p ON c.comment_post_ID = p.ID WHERE p.post_status != ‘trash’ ORDER BY c.comment_date_gmt DESC LIMIT 2100, 50
Executed 1 min ago for 8 sec on Database –> miniz678_db.
SELECT * FROM wp_comments c LEFT JOIN wp_posts p ON c.comment_post_ID = p.ID WHERE p.post_status != ‘trash’ ORDER BY c.comment_date_gmt DESC LIMIT 2150, 50
Executed 1 min ago for 2 sec on Database –> miniz678_db.
SELECT * FROM wp_comments c LEFT JOIN wp_posts p ON c.comment_post_ID = p.ID WHERE p.post_status != ‘trash’ ORDER BY c.comment_date_gmt DESC LIMIT 2200, 50
Executed 0 min ago for 15 sec on Database –> miniz678_db.
SELECT * FROM wp_comments c LEFT JOIN wp_posts p ON c.comment_post_ID = p.ID WHERE p.post_status != ‘trash’ ORDER BY c.comment_date_gmt DESC LIMIT 2350, 5

=====> Databases owned by miniz678.
Databases found:
miniz678_2a3a 3Mb.
miniz678_db 18Mb.

From the queries above we can conclude that your issue is caused by not well written scripts. In order to have the limitations removed, you should optimize your script so that it consumes less server resources.

Having not well written scripts is a quite complex problem. It may be caused by an additionally installed extension/module that is not working properly, or it may be in the application itself.

If the reason is in an extension/module, the easiest solution would be to disable/remove it. This can usually be done from the application’s admin area.

Please disable the comments plugin of your application to resolve the issue.

If the problem is in the application itself, solving it may take much more time and effort and will probably require advanced programming skills. In such cases it would be best to contact the application’s developers and ask for further assistance. They should be able to examine the issue and offer a suitable solution for it.

There are some general things you can do to optimize your site (such as enable cache). More information on how to optimize your site can be found in our Website Performance Tutorial (http://www.siteground.com/tutorials/websiteperformance/index.htm).

If optimizing the application is not a suitable option for you, we can offer you one of our dedicated solutions (http://www.siteground.com/dedicated_solutions.htm) as an alternative. There all of the system’s resources will be dedicated to your account and using a more resource-demanding application will not be a problem.

SiteGround is experienced in providing dedicated hosting solutions and we are happy to inform you that as an existing and loyal SiteGround customer, we will offer you a beneficial upgrade package including:

-No set up fees
-Free website content transfer from the shared server to the dedicated machine
-No website downtime during the upgrade

The upgrade process is simple and straightforward and you can order your dedicated solution upgrade immediately. To do that, please log in your SiteGround User Area -> Order section-> Upgrade to Dedicated Solution option.

If the problem with your application is not resolved in 7 days, we will be forced to take further actions in order to ensure the stability of the shared server.

Thank you in advance for your understanding and cooperation!

Please do NOT reply to this email. You can add comments on this issue by logging to your Customer Area (https://www.siteground.com/login_page.htm) and comment the ticket that has been automatically open on your behalf in connection to this case.

Sincerely,
Dimitar
SiteGround System Administrator
SiteGround.com