Guest User

Untitled

a guest
May 2nd, 2015
212
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 0.87 KB | None | 0 0
  1. Ever since moving my application from an Ubuntu 14.04 server on EC2 to Azure, I get timeouts from my unicorn workers when running longer queries
  2.  
  3. ```
  4. I, [2015-03-17T13:51:06.280175 #33828] INFO -- : worker=0 ready
  5. E, [2015-03-17T13:51:17.924711 #33824] ERROR -- : worker=1 PID:33831 timeout (11s > 10s), killing
  6. E, [2015-03-17T13:51:17.945216 #33824] ERROR -- : reaped #<Process::Status: pid 33831 SIGKILL (signal 9)> worker=1
  7. I, [2015-03-17T13:51:17.947956 #33867] INFO -- : worker=1 spawned pid=33867
  8. I, [2015-03-17T13:51:17.948471 #33867] INFO -- : Refreshing Gem list
  9. I, [2015-03-17T13:51:24.800618 #33867] INFO -- : worker=1 ready
  10. ```
  11.  
  12. Just wondering:
  13.  
  14. * is there a preferred config for unicorn (i have `preload_app` false right now)
  15. * is there a preferred config for mongoid
  16. * I have the unicorn timeout set to 60 now, but for long (unoptimized) queries, the issue would persist
Advertisement
Add Comment
Please, Sign In to add comment