Jobs failing with Errno::ENOMEM Cannot allocate memory - fork(2)

[rafmagana]

I'm running some workers in an Ubuntu box, I'm using monit (but happens the same just by running workers from the command line), ruby 1.9.2, I'm using these workers to clone git repositories, I use RedisToGo (Heroku add-on). What other information would be useful for you guys to be able to help me?

[danivovich]

Is there anything in the Heroku logs like "Error R14 (Memory quota exceeded)"?

[rafmagana]

I don't use a Heroku app, I have a separate application in a linux box, but I use the RedisToGo DB provided by a Heroku app, I do that because I need Git installed and Heroku doesn't provide that. So I don't see this error in the Heroku log, but in the log of the app running in the linux box. Thanks.

[danivovich]

Sorry I missed that. I assume you can clone the repositories from the command line in the box the workers run as? Are the workers running as be same user with the same limits? I've had issues cloning large git repositories from java processes on memory constrained systems. What ruby version are you using?

[rafmagana]

• Well, I clone the repos in Ruby but doing something like this: [backtick]git clone url[/backtick].
• Yes, the workers runs with the same user and same limits.
• Ruby version is 1.9.2

The weird thing is that I have 2 servers, exactly the same hardware and Ubuntu version, same configuration, same ruby version, same code, same everything on both of them, one is staging, the other one us production, of course, different RedisToGo (via Heroku, it's the Mini one) DB, and in the staging server doesn't happen this :S

[steveklabnik]

This error comes from not having enough RAM, so I don't think it's actually a Resque issue. If you can help me reproduce it somehow, I can help investigate.