# Modrails - rogue instances using 100% cpu

**URL:** <https://www.ruby-forum.com/t/modrails-rogue-instances-using-100-cpu/162281>\
**Category:** Deployment\
**Created:** [March 8, 2009, 2:12am UTC](https://www.ruby-forum.com/t/modrails-rogue-instances-using-100-cpu/162281 "2009-03-08T02:12:07Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![lamplighter](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/l/f475e1/32.png) [@lamplighter](https://www.ruby-forum.com/u/lamplighter)\
**Post date:** [March 8, 2009, 2:12am UTC](https://www.ruby-forum.com/t/modrails-rogue-instances-using-100-cpu/162281/1 "2009-03-08T02:12:07Z")

</div>

I am using modrails and have been randomly getting rogue ruby instances  
utilizing 100% cpu (4 cpus on server). The pid is not listed in  
passenger-status so passenger can’t take care of it.

Any ideas on how to fix this, or even just to debug this more? I don’t  
see anything unusual in the logs.