similar to: The real reason why Sync and Mutex behave differently

Hi One of the two mongrel processes has died in the middle of the night four times in the past 9 days, and I need help debugging this. Each time the symptoms are the same: * Each time I can restart the process via cap -a restart_app. * Before the restart, there is nothing unusual in production.log or mongrel.log. * During the restart, about 100 repetitions of an error message are generated in

Hi list, I''m seeing a couple of issues with Mongrel. I''m running FreeBSD 6.1 and have previously been told that there are known conflicts between this and Mongrel, yet I hope these issues will be resolved with time. I''m overloading Mongrel with httperf on my local workstation. Mongrel is started directly with the mongrel_rails command and there is only one mongrel

With Mongrel using Sync, are there any potential problems with actions that start threads and use Mutex? Steve

Is this the behavior that supposedly indicates a problem with a particular action? Mongrel in development mode randomly hangs on random actions. Further requests cause USR1 logs like: Mon Sep 18 13:04:03 PDT 2006: 0 threads sync_waiting for /, 2 still active in mongrel. Mon Sep 18 13:07:52 PDT 2006: 1 threads sync_waiting for /public/stylesheets/table.css, 3 still active in mongrel. Mon Sep 18

Hi, We are experiencing a problem with Samba 3.6.4 on Solaris 10 update 10. This problem has only recently started since an upgrade to v3.6.3 and was still present after rebuilding to 3.6.4. We are using the version of samba packaged by OpenCSW. >From a client perspective, the issue is manifested as intermittent very poor performance or intermittent inability to save a file to the share at

Morning Folks, As most of you know there were a few people who had the following three bugs: * CLOSE_WAIT: Lots of sockets in CLOSE_WAIT state. * 99% CPU: Mongrel''s getting "stuck" pegged at 99% CPU. * LEAK: Memory leak. I''ve successfully fixed these bugs or attributed them to one main cause: pstore. First, the memory leak was because of a bug in how the GC in Ruby

Hey Zed- I had a user with an app that was leaking memory with mongrel but not lighty/fcgi. I have been doing anything I can to track it down. I already did the Mutex patch to use unshitf and pop instead of shift and push and it didn''t really help much. The mem leak only really shows up when you use the wsess option to httperf. The other day I saw a ruby C extension that

Running Rails 2.3.5 I am new to Ruby and Rails. From the console I get the following ThreadError below. Any suggestions are very welcome. >> app.get "/slides" => 200 >> app.request.path_parameters => {"action"=>"index", "controller"=>"slides"} >> app.get "/slides/1" ThreadError: stopping only thread

Recently while i turned on USR1 debugging...mongrel running behind Apache2.2threw following debugging messages: Thu Sep 07 15:58:30 IST 2006: 0 threads sync_waiting for /charts/%5EBSESN, 1 still active in mongrel. Thu Sep 07 15:58:40 IST 2006: 0 threads sync_waiting for /images/tab_but_normal1.png, 3 still active in mongrel. Thu Sep 07 15:58:40 IST 2006: 0 threads sync_waiting for

Hello all, For the past couple of weeks I have been spending some time debugging a couple of issues I was having with Mongrel when I put load on it. I have seen two distinct issues: 1. Mongrel stopped responding as if in an endless loop. 2. Mongrel crashed when severely loaded. I believe to have resolved these two issues and have attached patches which shows the resolution (simple as it is).

Hi, I use Mongrel to serve my Rails applications on my server, but how can I serve more than one application with one mongrel server? Thanks. -jec -- Best regards / Salutations. Jean-Eric Cuendet Senior developer / Technical support Riskpro Technologies SA Av. Louis-Ruchonnet 2 CH-1003 Lausanne Switzerland Direct : +41 21 637 0123 Principal : +41 21 637 0110 Fax : +41 21 637 0111

Wht exactly does this mean? #<ActiveRecord::StatementInvalid: ThreadError: killed thread: That a thread was killed in the middle of a query? Thanks for your help. -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this

Hi there, I''ve just started using aaf for searching and it''s running well apart from one error I received: A ThreadError occurred in person#search: current thread not owner (druby:/localhost:9010) /usr/lib/ruby/1.8/monitor.rb:274:in `mon_check_owner'' (druby:/localhost:9010) /usr/lib/ruby/1.8/monitor.rb:274:in `mon_check_owner''

I have a periodically_call_remote call in a partial running at 0.20 times a second. <%= periodically_call_remote(:update => ''ack_distance_output'', :frequency => 0.2, :url=>{:action => :ackAdjustDistance}) %> the action looks like this def ackAdjustDistance @calMessage = Calibration.getMessage

The spinlock we use to protect the state of the simulator is sometimes held for a long time (for example, when devices handle requests). This also prevents us from calling functions that might sleep (such as kthread_flush_work() in the next patch), and thus having to release and retake the lock. For these reasons, let's replace the spinlock with a mutex that gives us more flexibility.

On Tue, 2014-06-03 at 00:30 +0300, Michael S. Tsirkin wrote: > All memory accesses are done under some VQ mutex. > So lock/unlock all VQs is a faster equivalent of synchronize_rcu() > for memory access changes. > Some guests cause a lot of these changes, so it's helpful > to make them faster. > > Reported-by: "Gonglei (Arei)" <arei.gonglei at huawei.com>

On Tue, 2014-06-03 at 00:30 +0300, Michael S. Tsirkin wrote: > All memory accesses are done under some VQ mutex. > So lock/unlock all VQs is a faster equivalent of synchronize_rcu() > for memory access changes. > Some guests cause a lot of these changes, so it's helpful > to make them faster. > > Reported-by: "Gonglei (Arei)" <arei.gonglei at huawei.com>

Hi all, I''ve been going through the various IPC modules for Win32Utils and converting them to pure Ruby. I''m almost done with win32-mutex, but I can''t get the example to work. I keep getting this error: C:/Documents and Settings/djberge/workspace/win32-mutex/examples/mutex_test.rb:41: undefined method `+'' for nil:NilClass (NoMethodError) from

Hello, CVS 07/31/03. Test with 130+ PSTN-to-SIP calls. Asterisk gets locked ... grep -e "Error" -e "eventually" p-console chan_sip.c line 1453 (sip_alloc): Error obtaining mutex: Device or resource busy chan_sip.c line 1453 (sip_alloc): Got it eventually... chan_sip.c line 1453 (sip_alloc): Error obtaining mutex: Device or resource busy chan_sip.c line 1453 (sip_alloc): Got

Howdy Folks, This release is after painstaking analysis of a memory leak that was reported by Bradley Taylor, reduced by myself, and then fixed after much work. You should all thank Bradley for finding the bizarre fix. It turns out the Ruby has a memory leak when you use pretty much any thread locking primitive other than Sync (Mutex, Monitor, etc.): http://pastie.caboo.se/10194 The fix (for