Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Ruby Enterprise Edition
Home
+ new post
About this group
Join this group
SIGVTALRM (Virtual timer expired)
Options
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
   3 messages - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Gleb Pomykalov  
View profile  
 More options Oct 17 2010, 7:17 am
From: Gleb Pomykalov <gleb...@gmail.com>
Date: Sun, 17 Oct 2010 04:17:42 -0700 (PDT)
Local: Sun, Oct 17 2010 7:17 am
Subject: SIGVTALRM (Virtual timer expired)
Print | Individual message | Show original | Report this message | Find messages by this author
Hi!

I've posted bug report http://code.google.com/p/rubyenterpriseedition/issues/detail?id=55

The issue is quite critical. There are a lot of dead processess on
production servers. Can you please comment out the problem?

Thank you


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Wayne E. Seguin  
View profile  
 More options Oct 18 2010, 2:47 pm
From: "Wayne E. Seguin" <wayneeseg...@gmail.com>
Date: Mon, 18 Oct 2010 14:47:48 -0400
Local: Mon, Oct 18 2010 2:47 pm
Subject: Re: SIGVTALRM (Virtual timer expired)
Print | Individual message | Show original | Report this message | Find messages by this author

My guess is that you are using Mysql gem. Try downgrading the version.

  ~Wayne


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Jordan Ritter  
View profile  
 More options Oct 18 2010, 3:57 pm
From: Jordan Ritter <j...@darkridge.com>
Date: Mon, 18 Oct 2010 12:57:17 -0700
Local: Mon, Oct 18 2010 3:57 pm
Subject: Re: SIGVTALRM (Virtual timer expired)
Print | Individual message | Show original | Report this message | Find messages by this author
I don't see how the strace itself indicates a problem on its own.  SIGVTALRM is what Ruby uses for signaling/interrupting the "thread of execution" (to context switch between threads, etc),

What does your app do?  What are its gem dependencies (more importantly, what are its natively-compiled extension gem dependencies)?  Does the patch you incorporated solve your hung-ruby problem reliably?  

Reading through the current release-2010.02 codebase, I see there's already a START_TIMER() a few lines above the diff you reference in the ticket.  It doesn't make sense offhand how a second call to START_TIMER() would solve a hung-ruby problem (I believe all it would do is just reset the itimer countdown).

--jordan

On Oct 17, 2010, at 4:17 AM, Gleb Pomykalov wrote:


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google