Actually, I've had to do both... So my problem was actually solved by
adding LD_LIBRARY_PATH to the mongrel_rails script.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Deploying Rails group.
To post to this group,
On Oct 3, 12:27 am, gers32 [EMAIL PROTECTED] wrote:
Actually, I've had to do both... So my problem was actually solved by
adding LD_LIBRARY_PATH to the mongrel_rails script.
Sorry, I got behind in reading this group, or I could have helped
earlier. On my staging and production servers we have
Jodi wrote:
I too am seeing this -
any ideas?
Well the obvious real solution is to examine the HTTP requests which
cause mongrel to bork and find a way to either prevent the malformed
requests or fix mongrel to properly understand them.
If you just want to reduce the cpu/io load from the
I too am seeing this -
any ideas?
On Aug 17, 8:48 am, Stanislav Bozhkov [EMAIL PROTECTED]
s.net wrote:
Hello,
I'm considering to replace our production server Apache with Enginx.
Behind them there are a dozen of mongrel_rails instances. Some of the
features that I like very much in Nginx