Killed
Contents |
The Problem
If you are running a script from a command line, for example, adding perl modules or running an install script, your script may quit prematurely with "killed". There is a "tyrannical, but good-natured, procwatch daemon" that kills processes that consume too much processor power and/or memory.
What To Do
First, try some solutions at the Slow Site Troubleshooting page.
If you're on a DreamHost shared server (e.g, not on a DreamHost VPS), your options include the following:
- Use less memory
- This should go without saying, but the easiest way to avoid having your processes killed for excessive memory usage is to make them use less memory! One common process which causes problems is the Perl module installer CPAN, for instance, as it often uses over 100 MB of memory just to load an index of all available modules. A less memory-hungry alternative is cpanminus, which can do the same job in a much smaller footprint.
- Stop unnecessary processes
- The procwatch daemon monitors memory usage across all processes you are running, not just one individual process, so you may run into memory limits prematurely if you (for instance) have a number of PHP processes running at the same time. Temporarily disabling busy sites on the same user may help, if applicable.
- Ask Support for help
- If nothing else works, your best bet is to contact DreamHost Support and ask them for assistance. They can temporarily disable procwatch to allow you to complete occasional memory-hungry tasks. If you need to use more memory on a frequent basis, however, your best bet is to…
- Upgrade to DreamHost VPS
- DreamHost VPS allows you to pick your own memory allocation, starting at 300 MB. You can enable it from the Panel at Enable DreamHost PS.
DreamHost VPS
If you're on a DreamHost VPS, matters become much easier! The memory available to your DreamHost VPS can be changed any time from the Panel at Manage Resources. Just turn the slider up to make room for whatever you need to do! If you only need the memory temporarily, you can adjust your memory allocation back down afterwards, and you'll only be charged for the time you used the extra memory!