<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>rain010101 (rain010101)</title>
    <link>https://ruby-china.org/rain010101</link>
    <description/>
    <language>en-us</language>
    <item>
      <title>resque timeout 问题，求助大侠</title>
      <description>&lt;p&gt;无论是 resque 和 redis 在同一台机器上，还是跨网络，一段时间后（本机时间长点，跨网络不到一个小时就挂掉）都会僵死掉不能取 job 处理，下面是前台起 resque --trace 后看到的异常，但实际上 redis 都是可用的。
按道理 resque 会重连 redis 吧，redis 设置 timeout=0.
而且前台起 resque 一旦网络异常进程就退出了，不会这么脆弱吧。
后台起 resque 一段时间后，进程还在，但不工作了，重启才重新获取 job 处理。
各位有遇到过吗？&lt;/p&gt;

&lt;p&gt;rake aborted!
Connection timed out
/home/app/.rvm/gems/ruby-1.9.3-p125@rails-3.1.0/gems/redis-3.0.1/lib/redis/client.rb:198:in &lt;code&gt;rescue in io'
/home/app/.rvm/gems/ruby-1.9.3-p125@rails-3.1.0/gems/redis-3.0.1/lib/redis/client.rb:196:in&lt;/code&gt;io'
/home/app/.rvm/gems/ruby-1.9.3-p125@rails-3.1.0/gems/redis-3.0.1/lib/redis/client.rb:204:in &lt;code&gt;read'
/home/app/.rvm/gems/ruby-1.9.3-p125@rails-3.1.0/gems/redis-3.0.1/lib/redis/client.rb:78:in&lt;/code&gt;block in call'
/home/app/.rvm/gems/ruby-1.9.3-p125@rails-3.1.0/gems/redis-3.0.1/lib/redis/client.rb:177:in &lt;code&gt;block (2 levels) in process'
/home/app/.rvm/gems/ruby-1.9.3-p125@rails-3.1.0/gems/redis-3.0.1/lib/redis/client.rb:281:in&lt;/code&gt;ensure_connected'
/home/app/.rvm/gems/ruby-1.9.3-p125@rails-3.1.0/gems/redis-3.0.1/lib/redis/client.rb:167:in &lt;code&gt;block in process'
/home/app/.rvm/gems/ruby-1.9.3-p125@rails-3.1.0/gems/redis-3.0.1/lib/redis/client.rb:242:in&lt;/code&gt;logging'
/home/app/.rvm/gems/ruby-1.9.3-p125@rails-3.1.0/gems/redis-3.0.1/lib/redis/client.rb:166:in &lt;code&gt;process'
/home/app/.rvm/gems/ruby-1.9.3-p125@rails-3.1.0/gems/redis-3.0.1/lib/redis/client.rb:78:in&lt;/code&gt;call'
/home/app/.rvm/gems/ruby-1.9.3-p125@rails-3.1.0/gems/redis-3.0.1/lib/redis.rb:1195:in &lt;code&gt;block in smembers'
/home/app/.rvm/gems/ruby-1.9.3-p125@rails-3.1.0/gems/redis-3.0.1/lib/redis.rb:36:in&lt;/code&gt;block in synchronize'
/home/app/.rvm/rubies/ruby-1.9.3-p125/lib/ruby/1.9.1/monitor.rb:211:in &lt;code&gt;mon_synchronize'
/home/app/.rvm/gems/ruby-1.9.3-p125@rails-3.1.0/gems/redis-3.0.1/lib/redis.rb:36:in&lt;/code&gt;synchronize'
/home/app/.rvm/gems/ruby-1.9.3-p125@rails-3.1.0/gems/redis-3.0.1/lib/redis.rb:1194:in &lt;code&gt;smembers'
/home/app/.rvm/gems/ruby-1.9.3-p125@rails-3.1.0/gems/redis-namespace-1.2.0/lib/redis/namespace.rb:243:in&lt;/code&gt;method_missing'
/home/app/.rvm/gems/ruby-1.9.3-p125@rails-3.1.0/gems/resque-1.21.0/lib/resque.rb:184:in &lt;code&gt;queues'
/home/app/.rvm/gems/ruby-1.9.3-p125@rails-3.1.0/gems/resque-1.21.0/lib/resque/worker.rb:216:in&lt;/code&gt;block in queues'
/home/app/.rvm/gems/ruby-1.9.3-p125@rails-3.1.0/gems/resque-1.21.0/lib/resque/worker.rb:216:in &lt;code&gt;map'
/home/app/.rvm/gems/ruby-1.9.3-p125@rails-3.1.0/gems/resque-1.21.0/lib/resque/worker.rb:216:in&lt;/code&gt;queues'
/home/app/.rvm/gems/ruby-1.9.3-p125@rails-3.1.0/gems/resque-1.21.0/lib/resque/worker.rb:197:in &lt;code&gt;reserve'
/home/app/.rvm/gems/ruby-1.9.3-p125@rails-3.1.0/gems/resque-1.21.0/lib/resque/worker.rb:131:in&lt;/code&gt;block in work'
/home/app/.rvm/gems/ruby-1.9.3-p125@rails-3.1.0/gems/resque-1.21.0/lib/resque/worker.rb:128:in &lt;code&gt;loop'
/home/app/.rvm/gems/ruby-1.9.3-p125@rails-3.1.0/gems/resque-1.21.0/lib/resque/worker.rb:128:in&lt;/code&gt;work'
/home/app/.rvm/gems/ruby-1.9.3-p125@rails-3.1.0/gems/resque-1.21.0/lib/resque/tasks.rb:34:in &lt;code&gt;block (2 levels) in &amp;lt;top (required)&amp;gt;'
/home/app/.rvm/gems/ruby-1.9.3-p125@rails-3.1.0/gems/rake-0.9.2.2/lib/rake/task.rb:205:in&lt;/code&gt;call'
/home/app/.rvm/gems/ruby-1.9.3-p125@rails-3.1.0/gems/rake-0.9.2.2/lib/rake/task.rb:205:in &lt;code&gt;block in execute'
/home/app/.rvm/gems/ruby-1.9.3-p125@rails-3.1.0/gems/rake-0.9.2.2/lib/rake/task.rb:200:in&lt;/code&gt;each'
/home/app/.rvm/gems/ruby-1.9.3-p125@rails-3.1.0/gems/rake-0.9.2.2/lib/rake/task.rb:200:in &lt;code&gt;execute'
/home/app/.rvm/gems/ruby-1.9.3-p125@rails-3.1.0/gems/rake-0.9.2.2/lib/rake/task.rb:158:in&lt;/code&gt;block in invoke_with_call_chain'
/home/app/.rvm/rubies/ruby-1.9.3-p125/lib/ruby/1.9.1/monitor.rb:211:in &lt;code&gt;mon_synchronize'
/home/app/.rvm/gems/ruby-1.9.3-p125@rails-3.1.0/gems/rake-0.9.2.2/lib/rake/task.rb:151:in&lt;/code&gt;invoke_with_call_chain'
/home/app/.rvm/gems/ruby-1.9.3-p125@rails-3.1.0/gems/rake-0.9.2.2/lib/rake/task.rb:144:in &lt;code&gt;invoke'
/home/app/.rvm/gems/ruby-1.9.3-p125@rails-3.1.0/gems/rake-0.9.2.2/lib/rake/application.rb:116:in&lt;/code&gt;invoke_task'
/home/app/.rvm/gems/ruby-1.9.3-p125@rails-3.1.0/gems/rake-0.9.2.2/lib/rake/application.rb:94:in &lt;code&gt;block (2 levels) in top_level'
/home/app/.rvm/gems/ruby-1.9.3-p125@rails-3.1.0/gems/rake-0.9.2.2/lib/rake/application.rb:94:in&lt;/code&gt;each'
/home/app/.rvm/gems/ruby-1.9.3-p125@rails-3.1.0/gems/rake-0.9.2.2/lib/rake/application.rb:94:in &lt;code&gt;block in top_level'
/home/app/.rvm/gems/ruby-1.9.3-p125@rails-3.1.0/gems/rake-0.9.2.2/lib/rake/application.rb:133:in&lt;/code&gt;standard_exception_handling'
/home/app/.rvm/gems/ruby-1.9.3-p125@rails-3.1.0/gems/rake-0.9.2.2/lib/rake/application.rb:88:in &lt;code&gt;top_level'
/home/app/.rvm/gems/ruby-1.9.3-p125@rails-3.1.0/gems/rake-0.9.2.2/lib/rake/application.rb:66:in&lt;/code&gt;block in run'
/home/app/.rvm/gems/ruby-1.9.3-p125@rails-3.1.0/gems/rake-0.9.2.2/lib/rake/application.rb:133:in &lt;code&gt;standard_exception_handling'
/home/app/.rvm/gems/ruby-1.9.3-p125@rails-3.1.0/gems/rake-0.9.2.2/lib/rake/application.rb:63:in&lt;/code&gt;run'
/home/app/.rvm/gems/ruby-1.9.3-p125@rails-3.1.0/gems/rake-0.9.2.2/bin/rake:33:in &lt;code&gt;&amp;lt;top (required)&amp;gt;'
/home/app/.rvm/gems/ruby-1.9.3-p125@rails-3.1.0/bin/rake:19:in&lt;/code&gt;load'
/home/app/.rvm/gems/ruby-1.9.3-p125@rails-3.1.0/bin/rake:19:in `&lt;/p&gt;'
Tasks: TOP =&amp;gt; resque:work&lt;p&gt;&lt;/p&gt;</description>
      <author>rain010101</author>
      <pubDate>Wed, 09 Jan 2013 09:49:58 +0800</pubDate>
      <link>https://ruby-china.org/topics/7897</link>
      <guid>https://ruby-china.org/topics/7897</guid>
    </item>
    <item>
      <title>centos 环境下 thin 的生产环境访问报错</title>
      <description>&lt;p&gt;thin start -p3022  -eproduction
访问服务器报错
前台报错：
We're sorry, but something went wrong.
We've been notified about this issue and we'll take a look at it shortly.
后台报错：
Errno::EACCES (Permission denied
开发环境是好的。
各位大虾，有人遇到过吗？是否和 route 有关？  &lt;/p&gt;</description>
      <author>rain010101</author>
      <pubDate>Fri, 10 Feb 2012 17:14:23 +0800</pubDate>
      <link>https://ruby-china.org/topics/1132</link>
      <guid>https://ruby-china.org/topics/1132</guid>
    </item>
  </channel>
</rss>
