Forum: Ruby on Rails Workling not outputting to production.log

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
0ae0992959bca4a68a222b583f161c33?d=identicon&s=25 Francis Wong (frenzy)
on 2009-04-09 00:33
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!
0ae0992959bca4a68a222b583f161c33?d=identicon&s=25 Francis Wong (frenzy)
on 2009-04-10 09:11
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...
Db7238007950074e9e73b76a81910406?d=identicon&s=25 Tonypm (Guest)
on 2009-04-11 08:47
(Received via mailing list)
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
4834e7e562a98aad85406feee1a4ff65?d=identicon&s=25 Ralph Haygood (Guest)
on 2009-05-04 09:44
(Received via mailing list)
Thanks for posting this.  It really should be explained in the
Workling documentation.

On Apr 10, 3:11 am, Albert Wong <rails-mailing-l...@andreas-s.net>
This topic is locked and can not be replied to.