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

Add support for EXTEND_TIMEOUT_USEC to systemd notification support #3234

Open
behrmann opened this issue Sep 26, 2023 · 1 comment
Open

Comments

@behrmann
Copy link

Is your feature request related to a problem? Please describe.

Using puma in GitLab and running puma as a systemd service with type notify I ran into startup issues because preloading the application took longer than the default service start timeout of 90s.

Describe the solution you'd like

It would be great if puma could write EXTEND_TIMEOUT_USEC= with some integer value regularly to the notification socket before signaling READY=1 and before running into the timeout to extend its startup time.

Describe alternatives you've considered

The issue can be easily worked around on a case by case basis by giving puma more time to start in the service file, i.e. setting TimeoutStartSec= to a higher value

@nateberkopec
Copy link
Member

Makes sense, I think we'd be willing to include this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants