Ruby on Rails glibc Exception on Shared Host

My site was down for about a week.  This happened before in Decemeber but at the time I was on vacation and was no where near troubleshooting mode.  Anyway, I wanted to get to the bottom of it this time and get it fixed.  It turns out I was getting the following exceptions from Mongrel on my shared host at DailyRazor:

*** glibc detected *** corrupted double-linked list: 0×08d949a0 ***
** Daemonized, any open files are closed.  Look at log/mongrel.pid and log/mongrel.log for info.
** Starting Mongrel listening at 0.0.0.0:120xx
** Starting Rails with development environment…
** Rails loaded.
** Loading any Rails specific GemPlugins
** Signals ready.  TERM => stop.  USR2 => restart.  INT => stop (no restart).
** Rails signals registered.  HUP => reload (without restart).  It might not work well.
** Mongrel 1.1.5 available at 0.0.0.0:120xx
** Writing PID file to log/mongrel.pid
*** glibc detected *** corrupted double-linked list: 0×4a45e858 ***
** Daemonized, any open files are closed.  Look at log/mongrel.pid and log/mongrel.log for info.
** Starting Mongrel listening at 0.0.0.0:120xx
** Starting Rails with development environment…
** Rails loaded.
** Loading any Rails specific GemPlugins
** Signals ready.  TERM => stop.  USR2 => restart.  INT => stop (no restart).
** Rails signals registered.  HUP => reload (without restart).  It might not work well.
** Mongrel 1.1.5 available at 0.0.0.0:120xx
** Writing PID file to log/mongrel.pid
*** glibc detected *** corrupted double-linked list: 0×08285630 ***

I spent hours trying to track down why this was happening but ended up asking my Technical Support folks that host the server for help.  After about a dozen emails and a number of days that came up with the following:

“It was because of bug in ruby code:

http://www.ruby-forum.com/topic/164574

We have applied patch and reinstalled ruby on the server. Please try to test your application now.

Best Regards,
Support-VS”

After this reinstall of ruby things have been working fine.



About this entry