log writing failed. can't be called from trap context
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 456
- Forks
- 149
- Avg merge
- 9d 7h
- Merged PRs (30d)
- 3
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.
https://github.com/resque/resque/issues/1493
https://github.com/steveklabnik/mono_logger
Any help would be greatly appreciated, thanks!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by running bundle exec resque-pool --daemon --environment production and compare resque-pool.stdout.log with resque-pool.stderr.log. Read the linked resque issue and mono_logger project for the signal-handler logging context, then trace the pool's logging path. Done means daemon startup no longer produces “log writing failed. can't be called from trap context” errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100