Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionJoniel Pasqualetto
2022-10-17 17:58:55 UTC
Description of problem:
Currently, we can't configure the worker_timeout used by puma workers. The default of 60s is used.
Changing the worker_timeout would allow users to workaround specific issues happening during peak moments. Here's an example where increasing the timeout would help:
~~~
Oct 14 06:08:45 satellite.example.com foreman: [1290] ! Terminating timed out worker (worker failed to check in within 60 seconds): 2420
~~~
Version-Release number of selected component (if applicable):
Actual results:
Not possible to change the default 60s timeout in a supported way.
Expected results:
Have an installer option to define the worker_timeout.
Additional info:
The timeout can be defined with the following line on the file /usr/share/foreman/config/puma/production.rb
~~~
worker_timeout 120
~~~
My suggestion is to add a line on the file /usr/share/foreman/config/puma/production.rb that will read a variable to be defined on the systemd unit, like we do for the number of workers, and min/max threads.
Like this:
~~~
worker_timeout ENV.fetch('FOREMAN_PUMA_WORKER_TIMEOUT', 60).to_i
~~~
Then, setting the value FOREMAN_PUMA_WORKER_TIMEOUT on the systemd unit would be enough:
~~~
# cat /etc/systemd/system/foreman.service.d/installer.conf
[Service]
User=foreman
Environment=FOREMAN_ENV=production
Environment=FOREMAN_HOME=/usr/share/foreman
Environment=FOREMAN_PUMA_THREADS_MIN=5
Environment=FOREMAN_PUMA_THREADS_MAX=5
Environment=FOREMAN_PUMA_WORKERS=6
Environment=FOREMAN_PUMA_WORKER_TIMEOUT=120 <============ new variable to define the timeout
~~~
Verified in 6.14 snap 2
Code change is in the snap. Full verification of this BZ is unnecessary and the changes here are only meant for debugging purposes.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Important: Satellite 6.14 security and bug fix update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2023:6818
Description of problem: Currently, we can't configure the worker_timeout used by puma workers. The default of 60s is used. Changing the worker_timeout would allow users to workaround specific issues happening during peak moments. Here's an example where increasing the timeout would help: ~~~ Oct 14 06:08:45 satellite.example.com foreman: [1290] ! Terminating timed out worker (worker failed to check in within 60 seconds): 2420 ~~~ Version-Release number of selected component (if applicable): Actual results: Not possible to change the default 60s timeout in a supported way. Expected results: Have an installer option to define the worker_timeout. Additional info: The timeout can be defined with the following line on the file /usr/share/foreman/config/puma/production.rb ~~~ worker_timeout 120 ~~~ My suggestion is to add a line on the file /usr/share/foreman/config/puma/production.rb that will read a variable to be defined on the systemd unit, like we do for the number of workers, and min/max threads. Like this: ~~~ worker_timeout ENV.fetch('FOREMAN_PUMA_WORKER_TIMEOUT', 60).to_i ~~~ Then, setting the value FOREMAN_PUMA_WORKER_TIMEOUT on the systemd unit would be enough: ~~~ # cat /etc/systemd/system/foreman.service.d/installer.conf [Service] User=foreman Environment=FOREMAN_ENV=production Environment=FOREMAN_HOME=/usr/share/foreman Environment=FOREMAN_PUMA_THREADS_MIN=5 Environment=FOREMAN_PUMA_THREADS_MAX=5 Environment=FOREMAN_PUMA_WORKERS=6 Environment=FOREMAN_PUMA_WORKER_TIMEOUT=120 <============ new variable to define the timeout ~~~