Today i came to office to find that my Server has crashed with this:
/usr/local/lib/site_ruby/1.8/eventmachine.rb:260: [BUG] Segmentation fault
2 ruby 1.8.4 (2005-12-24) [i486-linux]
I guess, its going to be difficult to track down from here, so I would
try to provide as much as information possible.
Its a Ubuntu Dapper machine, 64bit hardware but the OS is 32bit.
I think this, first or second time I am getting this. Since, it
happens very rarely, how do we debug this?
--
gnufied
-----------
There was only one Road; that it was like a great river: its springs
were at every doorstep, and every path was its tributary.
http://people.inxsasia.com/~hemant
Francis Cianfrocca
2007-Feb-11 06:21 UTC
[Eventmachine-talk] Segmentation fault in Eventmachine
On 2/11/07, hemant <gethemant at gmail.com> wrote:> > Today i came to office to find that my Server has crashed with this: > > /usr/local/lib/site_ruby/1.8/eventmachine.rb:260: [BUG] Segmentation fault > 2 ruby 1.8.4 (2005-12-24) [i486-linux] > > I guess, its going to be difficult to track down from here, so I would > try to provide as much as information possible. > > Its a Ubuntu Dapper machine, 64bit hardware but the OS is 32bit. > > I think this, first or second time I am getting this. Since, it > happens very rarely, how do we debug this?In the first place, you should update Ruby to a version more recent than May 2006. EM uses the nonblocking I/O changes that were made at that time. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/eventmachine-talk/attachments/20070211/7bb63a2d/attachment.html
On 2/11/07, Francis Cianfrocca <garbagecat10 at gmail.com> wrote:> On 2/11/07, hemant <gethemant at gmail.com> wrote: > > Today i came to office to find that my Server has crashed with this: > > > > /usr/local/lib/site_ruby/1.8/eventmachine.rb:260: [BUG] > Segmentation fault > > 2 ruby 1.8.4 (2005-12-24) [i486-linux] > > > > I guess, its going to be difficult to track down from here, so I would > > try to provide as much as information possible. > > > > Its a Ubuntu Dapper machine, 64bit hardware but the OS is 32bit. > > > > I think this, first or second time I am getting this. Since, it > > happens very rarely, how do we debug this? > > > In the first place, you should update Ruby to a version more recent than May > 2006. EM uses the nonblocking I/O changes that were made at that time. >Franics, sorry to bother you. but is it essential, because currently Ruby 1.8.5-p2 hasn''t made into Ubuntu Dapper apt tree. Its generally easier to manage the ruby installation with whatever package system comes with our system. In the past I i did try to build entire ruby stack from source, but the experience wasn''t very pleasant. I had to compile everything and some libs were really pain to compile. -- gnufied ----------- There was only one Road; that it was like a great river: its springs were at every doorstep, and every path was its tributary. http://people.inxsasia.com/~hemant
Francis Cianfrocca
2007-Feb-11 07:33 UTC
[Eventmachine-talk] Segmentation fault in Eventmachine
On 2/11/07, hemant <gethemant at gmail.com> wrote:> > On 2/11/07, Francis Cianfrocca <garbagecat10 at gmail.com> wrote: > > On 2/11/07, hemant <gethemant at gmail.com> wrote: > > > Today i came to office to find that my Server has crashed with this: > > > > > > /usr/local/lib/site_ruby/1.8/eventmachine.rb:260: [BUG] > > Segmentation fault > > > 2 ruby 1.8.4 (2005-12-24) [i486-linux] > > > > > > I guess, its going to be difficult to track down from here, so I would > > > try to provide as much as information possible. > > > > > > Its a Ubuntu Dapper machine, 64bit hardware but the OS is 32bit. > > > > > > I think this, first or second time I am getting this. Since, it > > > happens very rarely, how do we debug this? > > > > > > In the first place, you should update Ruby to a version more recent than > May > > 2006. EM uses the nonblocking I/O changes that were made at that time. > > > > Franics, sorry to bother you. but is it essential, because currently > Ruby 1.8.5-p2 hasn''t made into Ubuntu Dapper apt tree. Its generally > easier to manage the ruby installation with whatever package system > comes with our system. In the past I i did try to build entire ruby > stack from source, but the experience wasn''t very pleasant. I had to > compile everything and some libs were really pain to compile.Hmm. I guess if things work for you with 1.8.4 then it may not be essential. But I''m still wondering about the Segfault. The expectation with that error is a problem in the C code (generally reading or writing an invalid pointer), but I''m aware of any such problems in EM. I run it day and night under heavy loads, and the C code hasn''t significantly changed in months. Is there any way you could set up a stress test or a high-load test to get the segfault to occur more frequently so we can debug it? Running on multicores probably won''t change the behavior because EM is non-threaded. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/eventmachine-talk/attachments/20070211/93d1b3b2/attachment.html