-
Notifications
You must be signed in to change notification settings - Fork 150
Open
Description
After starting resque-pool via
bundle exec resque-pool --daemon --environment production
resque-pool.stdout.log is populated without issue, but resque-pool.stderr.log complains
log writing failed. can't be called from trap context
log writing failed. can't be called from trap context
log writing failed. can't be called from trap context
log writing failed. can't be called from trap context
log writing failed. can't be called from trap context
log writing failed. can't be called from trap context
It's related to logging inside a signal handler--resque and resque-scheduler have migrated to mono_logger to work around this issue.
resque/resque#1493
https://github.com/steveklabnik/mono_logger
Any help would be greatly appreciated, thanks!
PoojaKarande and tmedford
Metadata
Metadata
Assignees
Labels
No labels