Hi there everybody,
We''re having mongrel processes slowly die on us, with a segmentation
fault. I''ve seen a few other people mention similar issues. Any info
or suggestions would be nice:
Error:
/var/www/apps/heritage/current/config/../vendor/plugins/file_column/
lib/magick_file_column.rb:7: [BUG] Segmentation fault
ruby 1.8.4 (2005-12-24) [i386-linux]
Server:
Railsmachine.com standard setup, I think it''s CentOS.
Mongrel:
I just updated _yesterday_ to 0.3.13.4, before that I was on 0.3.13.3
but I wasn''t getting this error. I was instead getting the very
occasional mongrel going way out of control and taking over enough
memory to force a hard reboot to get back to it. (which is why I
upgraded)
Do you think the problem is in file_column somewhere? The line it
mentions is where it is calling ImageMagick:
def transform_with_magick
if needs_transform?
begin
img = ::Magick::Image::read(absolute_path).first <--
This is line 7
Thanks in advance for any ideas!!
Cameron
On Wed, 18 Oct 2006 16:20:59 -0500 Cameron Booth <cameron at theworkinggroup.ca> wrote:> Hi there everybody, > > We''re having mongrel processes slowly die on us, with a segmentation > fault. I''ve seen a few other people mention similar issues. Any info > or suggestions would be nice:<snip>> Do you think the problem is in file_column somewhere? The line it > mentions is where it is calling ImageMagick:Looks like a bug in ImageMagick that''s probably made worse by something Mongrel does (threads or IO possibly). I''d suggest that if you can''t keep it running solid then hook up a monit process on the mongrel machine(s) to keep them going. There''s a monit sample in the mongrel gem''s source under examples you can use as a start. -- Zed A. Shaw, MUDCRAP-CE Master Black Belt Sifu http://www.zedshaw.com/ http://mongrel.rubyforge.org/ http://www.lingr.com/room/3yXhqKbfPy8 -- Come get help.
On 19-Oct-06, at 3:11 AM, Zed A. Shaw wrote:>> Hi there everybody, >> >> We''re having mongrel processes slowly die on us, with a segmentation >> fault. I''ve seen a few other people mention similar issues. Any info >> or suggestions would be nice: > > <snip> > >> Do you think the problem is in file_column somewhere? The line it >> mentions is where it is calling ImageMagick: > > Looks like a bug in ImageMagick that''s probably made worse by > something Mongrel does (threads or IO possibly). I''d suggest that > if you can''t keep it running solid then hook up a monit process on > the mongrel machine(s) to keep them going. There''s a monit sample > in the mongrel gem''s source under examples you can use as a start.Thanks for the very quick response Zed. Setting up montoring makes perfect sense... I think I was so embedded in trying to figure things out it didn''t cross my mind at all. However, here''s my next question - maybe I''m just not understanding it properly, but I don''t see the monit(or) script you mention in the / examples dir of the mongrel-0.3.13.4 gem. There is mongrel_simple_ctrl.rb and mongrel_simple_service.rb, but I''m not sure that those are what you meant. Can anybody point me in the right direction? And as other people have mentioned Zed....thanks so much for all the hard work you''re putting into this! Cameron -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/mongrel-users/attachments/20061019/63fd9dd3/attachment.html
Monit is here: http://www.tildeslash.com/monit/ It''s an external program you can use for monitoring (and relaunching) other processes as well. Search this list for earlier examples on using monit with mongrel. Vish On 10/19/06, Cameron Booth <cameron at theworkinggroup.ca> wrote:> > On 19-Oct-06, at 3:11 AM, Zed A. Shaw wrote: > > Hi there everybody, > > > We''re having mongrel processes slowly die on us, with a segmentation > > fault. I''ve seen a few other people mention similar issues. Any info > > or suggestions would be nice: > > > <snip> > > > Do you think the problem is in file_column somewhere? The line it > > mentions is where it is calling ImageMagick: > > > Looks like a bug in ImageMagick that''s probably made worse by something > Mongrel does (threads or IO possibly). I''d suggest that if you can''t keep > it running solid then hook up a monit process on the mongrel machine(s) to > keep them going. There''s a monit sample in the mongrel gem''s source under > examples you can use as a start. > > > Thanks for the very quick response Zed. Setting up montoring makes perfect > sense... I think I was so embedded in trying to figure things out it didn''t > cross my mind at all. > > However, here''s my next question - maybe I''m just not understanding it > properly, but I don''t see the monit(or) script you mention in the /examples > dir of the mongrel-0.3.13.4 gem. There is mongrel_simple_ctrl.rb and > mongrel_simple_service.rb, but I''m not sure that those are what you meant. > > Can anybody point me in the right direction? > > And as other people have mentioned Zed....thanks so much for all the hard > work you''re putting into this! > > Cameron > > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users > >-------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/mongrel-users/attachments/20061019/76c5148d/attachment.html
Vish, thanks for clearing that up. Monit looks to be nicely done (at a quick glance), I''ll definitely look at setting it up. I found your earlier posts explaining the setup process to, so I should be good! Cameron On 19-Oct-06, at 12:33 PM, Vishnu Gopal wrote:> Monit is here: http://www.tildeslash.com/monit/ It''s an external > program you can use for monitoring (and relaunching) other > processes as well. Search this list for earlier examples on using > monit with mongrel. > > Vish >-------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/mongrel-users/attachments/20061019/8474354d/attachment.html