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

Broken stdout and stderr logging in Amazon Linux #1178

Closed
thesame opened this issue Mar 7, 2024 · 4 comments · Fixed by #1326
Closed

Broken stdout and stderr logging in Amazon Linux #1178

thesame opened this issue Mar 7, 2024 · 4 comments · Fixed by #1326
Assignees

Comments

@thesame
Copy link

thesame commented Mar 7, 2024

Systemd unit in package unit-1.32.0-1.amzn2023.ngx.x86_64.rpm contains this line: /usr/sbin/unitd $UNITD_OPTIONS --no-daemon which renders stdout and stderr options of /config/applications/* objects useless, according to this line in the documentation:

When running in --no-daemon mode, application output is always redirected to Unit’s log file.

@thresheek
Copy link
Member

thresheek commented Mar 7, 2024

For the record, --no-daemon was introduced in #212

I'm not sure if we want to change this to daemonization; or rather provide documentation on how to edit the service file to override the ExecStart= line.

We do run unit on debian with daemonization, so this only applies to rpm-based distros.

Thoughts?

@ac000
Copy link
Member

ac000 commented Mar 7, 2024

This has been discussed here, and my feeling on it is here.

@thresheek
Copy link
Member

So I guess that's at least +2 for moving back to daemon/forking. I'll prepare a PR with the changes, if noone objects.

@thresheek thresheek self-assigned this Mar 7, 2024
@BwL1289
Copy link

BwL1289 commented Apr 28, 2024

Also interested.

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

Successfully merging a pull request may close this issue.

4 participants