Giters

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.

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

logging and monit start issue with puma-daemon

chandrapratapsingh007 opened this issue · comments

commented 
          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: #24
and giving "error : 'puma' failed to start (exit status 0)_"

Originally posted by @chandrapratapsingh007 in #11 (comment)

commented

Thanks for the report. I'm guessing workers must reopen these files to continue logging after forking.

commented

yes @kigster but that is not happening. Nothing is getting logged in the logfiles after the workers starts.