{"action":"opened","issue":{"url":"https://api.github.com/repos/appsignal/appsignal/issues/38","labels_url":"https://api.github.com/repos/appsignal/appsignal/issues/38/labels{/name}","comments_url":"https://api.github.com/repos/appsignal/appsignal/issues/38/comments","events_url":"https://api.github.com/repos/appsignal/appsignal/issues/38/events","html_url":"https://github.com/appsignal/appsignal/issues/38","id":71538971,"number":38,"title":"Long running (resque) processes trigger DRb Conn Error with Broken Pipe","user":{"login":"serioushaircut","id":533504,"avatar_url":"https://avatars.githubusercontent.com/u/533504?v=3","gravatar_id":"","url":"https://api.github.com/users/serioushaircut","html_url":"https://github.com/serioushaircut","followers_url":"https://api.github.com/users/serioushaircut/followers","following_url":"https://api.github.com/users/serioushaircut/following{/other_user}","gists_url":"https://api.github.com/users/serioushaircut/gists{/gist_id}","starred_url":"https://api.github.com/users/serioushaircut/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/serioushaircut/subscriptions","organizations_url":"https://api.github.com/users/serioushaircut/orgs","repos_url":"https://api.github.com/users/serioushaircut/repos","events_url":"https://api.github.com/users/serioushaircut/events{/privacy}","received_events_url":"https://api.github.com/users/serioushaircut/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-04-28T09:48:58Z","updated_at":"2015-04-28T09:48:58Z","closed_at":null,"body":"Hi Appsignal,\r\n\r\nwe use version 0.11.9 with Resque Plugin and a Worker runs sometimes longer than 45min. \r\nThe following error is reproducible:\r\n\r\n```\r\nException DRb::DRbConnError \r\nError Broken pipe\r\n/usr/lib/ruby/2.1.0/drb/drb.rb:611:in `write'\r\n/usr/lib/ruby/2.1.0/drb/drb.rb:611:in `send_request'\r\n/usr/lib/ruby/2.1.0/drb/drb.rb:921:in `send_request'\r\n/usr/lib/ruby/2.1.0/drb/drb.rb:1221:in `send_message'\r\n/usr/lib/ruby/2.1.0/drb/drb.rb:1110:in `block (2 levels) in method_missing'\r\n/usr/lib/ruby/2.1.0/drb/drb.rb:1197:in `open'\r\n/usr/lib/ruby/2.1.0/drb/drb.rb:1109:in `block in method_missing'\r\n/usr/lib/ruby/2.1.0/drb/drb.rb:1128:in `with_friend'\r\n/usr/lib/ruby/2.1.0/drb/drb.rb:1108:in `method_missing'\r\n/app/.bundle/ruby/2.1.0/gems/appsignal-0.11.9/lib/appsignal/ipc.rb:59:in `enqueue'\r\n/app/.bundle/ruby/2.1.0/gems/appsignal-0.11.9/lib/appsignal/transaction.rb:160:in `complete!'\r\n/app/.bundle/ruby/2.1.0/gems/appsignal-0.11.9/lib/appsignal/transaction.rb:26:in `complete_current!'\r\n/app/.bundle/ruby/2.1.0/gems/appsignal-0.11.9/lib/appsignal.rb:92:in `monitor_transaction'\r\n/app/.bundle/ruby/2.1.0/gems/appsignal-0.11.9/lib/appsignal/integrations/resque.rb:8:in `around_perform_resque_plugin'\r\n```\r\n\r\nWe think that looks like, that on completing the job finally, appsignal tries to enqueue the transaction into the transaction Drb server file 'drbunix:...' stream which is no longer opened for writing.\r\n\r\nIs that anything we can just configure anywhere in case we know our job might run quite some time? Or is it a bug?\r\n\r\nCheers,\r\nBastian\r\n"}}