Hi guys,
I've a problem with the uptime on server. It's always high and drush refuse to start:

load on system too heavy (5.52 5.13 4.89), aborting                                                                  [error]
Drush command terminated abnormally due to an unrecoverable error.                                     [error]

It's possible to bypass the control of uptime of the server?

Thanks.
hachreak :)

Comments

greg.1.anderson’s picture

Category: feature » support
Status: Active » Fixed

Run top and see what is using so much cpu time. Kill runaway processes. Run fewer services. Get a bigger host.

hachreak’s picture

Sorry,
but I'm on a shared server. I can't kill process.. :)
Where is in code of drush the uptime check?

greg.1.anderson’s picture

Sorry, that abort message is from your server, not Drush.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

mrfelton’s picture

Status: Closed (fixed) » Active

Hmm. I get this quite frequently on my macbook pro with 8GB of RAM and very little else running. Before running drush make system load was below one, by the time it gets half way through, load is upto +5, and it fails with the error about system load. I understand that the message is coming from my system and not drush, but it seems apparent that drush is causing this.

moshe weitzman’s picture

Status: Active » Fixed

In drush5, try with --concurrency=1. drush make for drush 4 is no longer supported.

mrfelton’s picture

It worked with --concurrency=1, although it still pushed my system load from a 15 minute average of 0.85 to 4.5+. Should it really that resource intensive to download a buch of files and apply patches?

dmmd’s picture

Someone correct me if I'm wrong, but I think this message comes from drupal's server...

Steven Jones’s picture

For those using Drush 5 and seeing crazy high CPU load this issue is aiming to solve that: #1554092: drush_invoke_process uses 100% CPU

Steven Jones’s picture

@hachreak do you have Aegir/Provision installed, it includes something that will not let Drush execute if the system load is too high.

mrfelton’s picture

@Steven Jones - I do on my system where I have the problem.

Steven Jones’s picture

@mrfelton sadly this is in a hook_drush_init in provision: http://drupalcode.org/project/provision.git/blob/refs/heads/6.x-1.x:/pro... So hacking that file to remove it may 'solve' the problem for you, ideally this would only affect provision commands or be overrideable.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.