I have workling/starling setup and working for both production and development to send a welcome email after a user signs up. However, in the production environment, it refuses to output to the log file production.log, however in development environment, everything outputs fine in development.log I have the workling_client started as the same uid and gid as the application and made sure it has the same permission as the production.log file. Has anyone else experienced this before? Thanks! -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
Finally figured this out, and posting it incase anyone else runs into this issue. It has to do with logger buffers everything sent to is and does not auto flush in production environment. So a quick fix is to call logger.flush whenever the worker completes, probably a better way to do this by putting it in some after filter, but not sure if workling has such a filter... -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
Albert, thank you so much for this info. I have posted this quation twice and not received a response. Tried it and it is the solution. It has been irritating me for a while, but I just haven''t had time to investigate it. Many thanks Tonypm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
Thanks for posting this. It really should be explained in the Workling documentation. On Apr 10, 3:11 am, Albert Wong <rails-mailing-l...-ARtvInVfO7ksV2N9l4h3zg@public.gmane.org> wrote:> Finally figured this out, and posting it incase anyone else runs into > this issue. > > It has to do with logger buffers everything sent to is and does not auto > flush in production environment. > > So a quick fix is to call logger.flush whenever the worker completes, > probably a better way to do this by putting it in some after filter, but > not sure if workling has such a filter... > -- > Posted viahttp://www.ruby-forum.com/.