SIGUSR1 killing running rails requests

Since tweaking our setup to get Rails running using dispatch.lsapi we are getting lots of SIGUSR1 errors messages produced in our app.

They appear to be produced whenever a request results in a large dataset being returned.

Can anyone point me in the direction of the configuration settings that can stop these errors occuring? My first thoughts were to raise the memory limits on our processes but this doesn't seem to have stopped them.

Is there any other information I can supply to help diagnose this problem?

Like mistwang said, we definitely recommend using our easy raills setup outlined in our wiki. It will make your life a lot easier.

From the looks of it, your Soft/hard memory limits are set way to low if you expect your scripts to return large buffered db data sets. If you are returning 30K rows containing blobs, I'm just throwing out a relative figure, you can easily exhaust this value. Remember, this is not a "Per Ruby/Rails Process" limit but the limit for all the ruby rail processed spawned total.