Skip to content
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

Open
johnnncodes opened this issue Nov 25, 2016 · 4 comments
Open

How to check if the worker killer is working? #67

johnnncodes opened this issue Nov 25, 2016 · 4 comments

Comments

@johnnncodes
Copy link

Not currently sure how to check if the worker killer is working. Also, where can I check the logs of unicorn worker killer?

@passalini
Copy link

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

@ndlbass
Copy link

ndlbass commented Nov 12, 2018

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.

@tasos31
Copy link

tasos31 commented Mar 22, 2019

@ndlbass I am probably too late, but adding something like this line in your unicorn.rb config file would create the file and log the output:
stderr_path File.expand_path('../../log/unicorn_stderr.log', __FILE__)

If you dont have a unicorn.rb file under config folder in the first place, just create one.

@stevendaniels
Copy link

@johnnncodes - It looks like your issue was answered, can you close this issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants