/usr/local/ruby2/lib/ruby/gems/1.8/gems/bleak_house-3.6/lib/bleak_house/rails/dispatcher.rb:8: undefined local variable or method `callbacks' for Dispatcher:Class(NameError) from /usr/local/ruby2/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in `gem_original_require' from /usr/local/ruby2/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in `require'
解决方法:
作者如是说 :
Yeah, on my blog I mentioned that you need to stick with -v3.5.1if you still use Rails 1.2x.
/usr/local/ruby2/bin/ruby: symbol lookup error: /usr/local/ruby2/lib/ruby/gems/1.8/gems/bleak_house-3.5.1/ext/bleak_house/logger/snapshot.so: undefined symbol: rb_gc_heap_slots
让我们参考下面一段话来得到答案:
Matt says (May 06,2007): Is it possible to monitor a mongrel/rails process this way—or just webrick/rails? When I use the supplied starting command, I wind up with a ‘normal’ ruby process, not a ruby-bleak-house process. I suppose I could symlink my /usr/local/bin/ruby to my ruby-bleak-house. evansays (June 22,2007): There are various ways you can manually start the server, but the symlink is the easiest. The BleakHouse binary is just as reliable as regular Ruby.
Question #2 We really like the graphing, is it coming back ever? It seems even in your "Let me hit you with some knowledge" post that it was far faster to spot the leak with graphs. Is there a way to hack it onto 3.7? > Question 2 Dunno in my own work I thought the graphs were less useful than the text output, so I dropped them. If someone wanted to work on restoring them I would accept a patch (for example bleak --graph) to optionally have graphs too.