Displaying 5 results from an estimated 5 matches for "sync_m".
Did you mean:
sync_mb
2006 Sep 18
2
Random(?) action hanging
...39;'t seem to happen in production mode, at least it hasn''t so
far. It happens every few minutes in development, and sending INT to
the process causes this:
Thread #<Thread:0x3388f10 sleep> is too old, killing.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...
2012 Sep 15
1
err: Could not request certificate: stack level too deep
...debug: Using cached certificate for ca
err: Could not request certificate: stack level too deep
debug: Using cached 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&...
2006 Oct 31
9
Problems with mongrel dying
...ach of the four crashes, one or two pdf files were downloaded from my
public directory - which I believe apache does bypassing mongrel.
Suggestions?
Thanks
Robert Vogel
Error messages in mongrel.log generated during 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/r...
2006 Oct 24
9
[WARN] Got 99% CPU?
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/
2006 Sep 13
7
Mongrel spewing backtraces and nanosleeping
...aping N threads for slow workers because of ''max processors''
Now this is fine, but sooner or later I start getting the following in
the mongrel.log:
Thread #<Thread:0x8f1a364 sleep> is too old, killing.
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...