Hi coffeeaddict: Do you know what passenger kills and causing problem for ruote worker? Is it db connection to the database killed? The ruote worker starts working again after restarting nginx. Usually after 5min idle time, there will be problem for ruote worker.
Setting up min instances in passenger is not enough to keep ruote worker working. Best Regards -emclab On Friday, December 13, 2013 1:07:33 AM UTC-6, coffeeaddict wrote: > > Passenger is notoriously know for reaping it's children and forking new > ones when the demand rises. > > You need to hook in some stuff into passenger to let it re-connect to your > database(s) > > Look at > https://encrypted.google.com/search?hl=en&q=passenger%20starting_worker_processto > get some inspiration ;) > > > On Fri, Dec 13, 2013 at 4:57 AM, John Mettraux <[email protected]<javascript:> > > wrote: > >> >> On Thu, Dec 12, 2013 at 07:03:42PM -0800, emc_lab wrote: >> > >> > We have the current setting in window7: Ruote worker is started within >> > rails on its own thread, all is good. We moved our deployment to a linux >> > box and we are using nginx and passenger to host our rails app. We >> > configured passenge to keep at least 1 instance of a rails app, and >> > therefore not killing the apps and the ruote worker. >> >> Hello, >> >> OK, well done with the passenger settings. >> >> > What we have noticed >> > after some inactivity about 15 minutes, the >> Ruote.storage_participant.all >> > will retunr no workitems, if I bounce nginx, the sames call will return >> the >> > workitems. We thought may the passenger config is wrong, but double >> check >> > (see below) but we also record the ruby pid, prior to the incativty >> period >> > and after and the ruby pid is the same. Any way you can help us figuring >> > out the issue?. >> > >> > snippet of the nginx config: >> > >> > #biz-tools >> > location ~ ^/bt/*$ { >> > return 301 /bt/authentify/signin; >> > passenger_min_instances 1; >> > } >> >> I'm not a nginx expert, I tend to use "proxy_pass" when I put nginx in >> front >> of Ruby (and Thin). >> >> Does your setup without nginx work? >> >> You should probably add some debug output to the nginx setup (and to the >> passenger config as well if possible) to determine if the problem is on >> the >> nginx or the passenger side. >> >> By bouncing Nginx, I guess you mean restarting Nginx. When Nginx returns >> an >> empty result list, does hitting directly passenger return the up-to-date >> list? >> >> >> Good luck, >> >> -- >> John Mettraux - http://lambda.io/jmettraux >> >> -- >> -- >> you received this message because you are subscribed to the "ruote users" >> group. >> to post : send email to [email protected] <javascript:> >> to unsubscribe : send email to [email protected]<javascript:> >> more options : http://groups.google.com/group/openwferu-users?hl=en >> --- >> You received this message because you are subscribed to the Google Groups >> "ruote" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> For more options, visit https://groups.google.com/groups/opt_out. >> > > -- -- you received this message because you are subscribed to the "ruote users" group. to post : send email to [email protected] to unsubscribe : send email to [email protected] more options : http://groups.google.com/group/openwferu-users?hl=en --- You received this message because you are subscribed to the Google Groups "ruote" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
