Skip to content

log writing failed. can't be called from trap context #157

Description

@thenashfactor

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!

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions