Project

General

Profile

Actions
Copy link

Bug #32112

closed

configure gunicorn worker timeout for pulpcore-api.service

Added by William Clark almost 4 years ago. Updated almost 4 years ago.

Status:
Closed
Priority:
High
Assignee:
William Clark
Category:
Foreman modules
Target version:
-
Difficulty:
easy
Triaged:
No
Bugzilla link:
1940657
Pull request:
https://github.com/theforeman/puppet-pulpcore/pull/178, https://github.com/theforeman/puppet-pulpcore/pull/179
Fixed in Releases:
Found in Releases:
Foreman - 2.3.3
Red Hat JIRA:

Description

While syncing several large repositories, I faced the issue

```
pulpcore-api: [2021-03-16 18:25:37 -0400] [10699] [CRITICAL] WORKER TIMEOUT (pid:10746)
pulpcore-api: [2021-03-16 22:25:38 +0000] [10746] [INFO] Worker exiting (pid: 10746)
pulpcore-api: [2021-03-16 18:25:39 -0400] [12522] [INFO] Booting worker with pid: 12522
```

This should be alleviated by increasing the gunicorn worker timeout for the pulpcore-api.service from the default 30 seconds

Actions
Copy link
 #1

Updated by The Foreman Bot almost 4 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/puppet-pulpcore/pull/178 added
Actions
Copy link
 #2

Updated by Justin Sherrill almost 4 years ago

  • Bugzilla link set to 1940657
Actions
Copy link
 #3

Updated by William Clark almost 4 years ago

  • Status changed from Ready For Testing to Closed
Actions
Copy link
 #4

Updated by The Foreman Bot almost 4 years ago

  • Pull request https://github.com/theforeman/puppet-pulpcore/pull/179 added
Actions
Copy link

Also available in: Atom PDF