search for: sync_unlock

...when severely loaded. I believe to have resolved these two issues and have attached patches which shows the resolution (simple as it is). Explanation of the patches is given below. The first problem is handled by the patch to sync.rb from the standard library. What is happening here is that when sync_unlock is called Thread.critical is set to true. Now if the thread is not the sync_ex_locker an exception is thrown without Thread.critical being set to false. This in turn resulted in a situation where the mongrel_sleeper_thread (configurator.rb:270) was the only thread getting back on the cpu and Thread...

...ems brought into Puppet. I installed it on several this morning without incident, but there are two (more or less identical RHEL 5.3 systems) that throw horrible errors. These systems did not have Puppet or Ruby installed prior to today. # puppet --version /usr/lib/ruby/1.8/sync.rb:214:in `sync_unlock'': stack level too deep (SystemStackError) from /usr/lib/ruby/1.8/sync.rb:231:in `synchronize'' from /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:290:in `name'' from /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:288:in `each'' from /u...

...certificate for ca debug: Using cached certificate for ca /usr/lib/ruby/1.8/sync.rb:58:in `Fail'': Thread(#<Thread:0x2af83efcd378 run>) not locked. (Sync_m::Err::UnknownLocker) from /usr/lib/ruby/1.8/sync.rb:64:in `Fail'' from /usr/lib/ruby/1.8/sync.rb:184:in `sync_unlock'' from /usr/lib/ruby/1.8/sync.rb:232:in `synchronize'' from /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:650:in `uninterpolated_value'' from /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:800:in `each_source'' from /usr/lib/ruby/site_rub...

....Mon Sep 18 13:16:44 PDT 2006: Error calling Dispatcher.dispatch #<Sync_m::Err::UnknownLocker: Thread(#<Thread:0x3388f10 run>) not locked.> /usr/local/lib/ruby/1.8/sync.rb:57:in `Fail'' /usr/local/lib/ruby/1.8/sync.rb:63:in `Fail'' /usr/local/lib/ruby/1.8/sync.rb:183:in `sync_unlock'' /usr/local/lib/ruby/1.8/sync.rb:231:in `synchronize'' /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/lib/mongrel/rails.rb:83:in `process'' /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/lib/mongrel.rb:580:in `process_client'' /usr/local/lib/ruby/gems/1.8/ge...

...ng restart: Tue Oct 31 07:26:30 PST 2006: Error calling Dispatcher.dispatch #<Sync_m::Err::UnknownLocker: Thread(#<Thread:0xb7544c58 aborting>) not locked.> /usr/lib/ruby/1.8/sync.rb:57:in `Fail'' /usr/lib/ruby/1.8/sync.rb:63:in `Fail'' /usr/lib/ruby/1.8/sync.rb:183:in `sync_unlock'' /usr/lib/ruby/1.8/sync.rb:231:in `synchronize'' /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.5/lib/mongrel/rails.rb:81:in `process'' /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.5/lib/mongrel.rb:583:in `process_client'' /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.5/lib/...

Hey folks, I ran into a few people at RubyConf who were having 99% CPU issues. Please contact me if you meet the following criteria: 1. You are running a production site. 2. You are experiencing 99% CPU errors. 3. This is frequent enough that you cannot manage it. Thank you. Please contact me off-list about it. -- Zed A. Shaw, MUDCRAP-CE Master Black Belt Sifu http://www.zedshaw.com/

...Wed Sep 13 00:34:42 CEST 2006: Error calling Dispatcher.dispatch #<Sync_m::Err::UnknownLocker: Thread(#<Thread:0x8f1a364 run>) not locked.> /usr/local/lib/ruby/1.8/sync.rb:57:in `Fail'' /usr/local/lib/ruby/1.8/sync.rb:63:in `Fail'' /usr/local/lib/ruby/1.8/sync.rb:183:in `sync_unlock'' /usr/local/lib/ruby/1.8/sync.rb:231:in `synchronize'' /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/lib/mongrel/rails.rb:83:in `process'' /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/lib/mongrel.rb:580:in `process_client'' /usr/local/lib/ruby/gems/1.8/ge...