ylecuyer / puma-status Goto Github PK

Hi

puma-monitor shows all workers as killed but they are working.

Status was displayed properly for couple of hours.

Ruby: 2.5.7p206
Puma 4.3.5

When I add this gem to my gemfile, a number of methods are introduced at the root level. In version 1.5 of this gem, this caused to overwrite the Kernel warn method.

Is there a reason this gem is set up this way? Would it be possible to put all methods in one or more Ruby classes?

I get the following when I install it:
Gem::RuntimeRequirementNotMetError: puma-status requires Ruby version >= 2.3.0

(I know Ruby 2.2 is EOL)

While trying to debug a puma server problem found your tool but I wasn't unable to use it in my server:

deploy@xxx:~/applications/xxx/shared/tmp/pids$ puma-status puma.state

puma.state doesn't exists
deploy@xxx:~/applications/xxx/shared/tmp/pids$ cat puma.state
---
pid: 1727
control_url: unix://tmp/sockets/pumactl.sock
control_auth_token: '12345'
deploy@xxx:~/applications/xxx/shared/tmp/pids$ ls -l puma.state
-rw-r--r-- 1 deploy sudo 87 May 18 01:52 puma.state
deploy@xxx:~/applications/xxx/shared/tmp/pids$

But I'm sure the file exists and is readable so I think that

Any ideas? Thanks

Colorize is released under GPL, which limits the use of puma-status.

Im a little confused, where i can find the .state file generated by rails (or sidekiq) to monitor it?