search

kigster / puma-daemon

Puma (starting version 5) removed automatic demonization from the gem itself. This functionality was extracted to this gem, which supports Puma v5 and v6.
MIT License
37 stars 6 forks source link

Hopefully fixing demonization for Puma v5 and v6 #11

Closed kigster closed 1 year ago

kigster commented 1 year ago

Hopefully fixes #1, #8, #9, #10

chandrapratapsingh007 commented 7 months ago

This issue is still not fixed. I am passing the log file path as follows in the puma.rb file:

stdout_redirect "/tmp/puma.stdout.log", "/tmp/puma.stderr.log", true

But in the puma.stdout.log only puma start logs are getting logged and no entries after that:

=== puma startup: 2024-02-21 14:23:59 +0000 ===
I, [2024-02-21T14:23:59.020812 #28027]  INFO -- : Installing Puma worker loop.
[27929] - Worker 0 (PID: 28027) booted in 0.02s, phase: 0
I, [2024-02-21T14:23:59.043596 #28035]  INFO -- : Installing Puma worker loop.
[27929] - Worker 1 (PID: 28035) booted in 0.01s, phase: 0

Also, monit is failing to start the service as described here: https://github.com/kigster/puma-daemon/issues/24 and giving "error : 'puma' failed to start (exit status 0)_"