pulp_container 1.1.0 is GA with the set of new features and bugfixes. It is
also compatible with pulpcore 3.1.
https://pulp-container.readthedocs.io/en/1.1/changes.html
https://pypi.org/project/pulp-container/1.1.0/
Regards,
Ina Panova
Senior Software Engineer| Pulp| Red Hat Inc.
"Do
This can be modified using the systemd unit file[0]. Gunicorn takes a -t
argument. It defaults to 30 seconds.
[0]
https://github.com/pulp/ansible-pulp/blob/master/roles/pulp/templates/pulpcore-api.service.j2#L13
On Fri, Jan 31, 2020 at 9:26 AM Bin Li (BLOOMBERG/ 120 PARK) <
Hi All,
Just noticed we continues get the following messages in the logs. Has anyone
seen this before? How can we fix this?
Jan 31 09:26:01 pulp gunicorn[147915]: 127.0.0.1 [31/Jan/2020:14:26:01 +]
"GET / HTTP/1.0" 404 172 "-" "-"
Jan 31 09:26:01 pulp gunicorn[147883]: pulp:
Thanks Brian.
It looks like the worker timeout.
Jan 31 09:19:30 pulpp-ob-581 gunicorn[147883]: [2020-01-31 09:19:30 -0500]
[147883] [CRITICAL] WORKER TIMEOUT (pid:147898)
Jan 31 09:19:30 pulpp-ob-581 gunicorn[147883]: [2020-01-31 14:19:30 +]
[147898] [INFO] Worker exiting (pid: 147898)
Jan
Pulpcore 3.1.0 is the first feature release of Pulp 3 and contains some
significant features and fixes. See the release notes for all the details.
https://docs.pulpproject.org/en/3.1.0/changes.html Here are some highlights:
* Azure support
* signing services for plugins to use
* restriction of
What do the logs say about why the gunicorn process serving pulp-api is
dying? Would you want to file an issue https://pulp.plan.io/issues/new so
we can do some testing?
As an aside, I recommend using paging when pulling so many items from an
API. You could decompose your large request to more,
