-
Notifications
You must be signed in to change notification settings - Fork 89
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to check if the worker killer is working? #67
Comments
tail log/unicorn.stderr.log
W, [2018-04-04T17:48:47.777003 #22771] WARN -- : #<Unicorn::HttpServer:0x0000000002558578>: worker (pid: 22771) exceeds memory limit (194912256 bytes > 418566 bytes)
W, [2018-04-04T17:48:47.777172 #22771] WARN -- : Unicorn::WorkerKiller send SIGQUIT (pid: 22771) alive: 3130 sec (trial 1)
I, [2018-04-04T17:48:48.023111 #22689] INFO -- : reaped #<Process::Status: pid 22771 exit 0> worker=11
I, [2018-04-04T17:48:48.193869 #25069] INFO -- : worker=11 ready |
So if that file does not exists, it means that the gem is not working? I am trying to understand if it is running on my project but this log is not beign generated. |
@ndlbass I am probably too late, but adding something like this line in your If you dont have a |
@johnnncodes - It looks like your issue was answered, can you close this issue? |
Not currently sure how to check if the worker killer is working. Also, where can I check the logs of unicorn worker killer?
The text was updated successfully, but these errors were encountered: