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

Log is not working #8

Closed dirceu-jr closed 1 year ago

dirceu-jr commented 3 years ago

Daemonizing using both ways leads to log not to work. The file configured through --redirect-stdout stays with the content below:

=== puma startup: 2021-05-13 20:09:27 -0300 ===
[44739] *  Puma Daemon: Daemonizing (puma-daemon v0.1.2)...

Nothing more, and the file configured through --redirect-stderr with:

=== puma startup: 2021-05-13 22:19:47 +0000 ===
kigster commented 3 years ago

Can you please provide your puma config and the command line?

dirceu-jr commented 3 years ago

Can you please provide your puma config and the command line?

Yes,

Config: https://gist.github.com/dirceup/40cd59c9c6d579b03998ac54037b2ec6 Command line:

bundle exec dotenv puma -v -b \"unix:///var/project/shared/tmp/sockets/puma.sock\" -S /var/project/shared/tmp/sockets/puma.state --pidfile /var/project/shared/tmp/pids/puma.pid --control-url 'unix:///var/project/shared/tmp/sockets/pumactl.sock' --redirect-stdout \"/var/project/shared/log/puma.log\" --redirect-stderr \"/var/project/shared/log/puma-stderr.log\"
ujinius commented 2 years ago

Hello, I have same problem with logs. Is there any progress on it? Thanks.

kigster commented 1 year ago

Will take a look if I get a sense of the need for this gem....

kigster commented 1 year ago

Hopefully fixed with #11