[Mongrel] problems with Mongrel + Pound
piyush.pr at gmail.com
Wed Feb 27 03:20:34 EST 2008
To install mysql gem you need to specify the mysql_config path(if it is not
installed then into mysql dev or devel package)
To install sudo gem install mysql --
--with-mysql-config=<path-to-mysql_config like on my ubuntu it is
And your problems are similar(not same) I used to encounter. I had these
problems with my mongrel handler when it used to write to database in
asynchronous queries by the users. Log file used to scream connection lost
to mysql. After spending a few days trying to boost up my mysql server I did
the gem install and since then it has handled 100K + queries (the mongrel
handler part of the app)each day without any problem whatsoever.
Also switch to apache/ngnix if you can. Pound could also be the trouble
maker though I am not very sure about this comment.
On Wed, Feb 27, 2008 at 1:29 PM, Dave Cheney <dave at cheney.net> wrote:
> I hacked our vendor tree to explode on startup if the mysql gem could not
> be found. IMHO this should be the default behavior, the built in mysql
> adapter is crap and its silent use is a ticking time bomb
> On 27/02/2008, at 6:42 PM, mohammed.a at aol.in wrote:
> Thank you for the replies.
> Here's what I found - mysql gem was not installed and that maybe a core
> source of problems as suggested by Zed. We've had too many problems when we
> tried to install this, and found that none of the solutions that are
> mentioned really work. We will try to install this gem again.
> Mongrel-users mailing list
> Mongrel-users at rubyforge.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Mongrel-users