Here is the traceback:
Oct 28 15:58:45 ipaddr gunicorn[165752]: 127.0.0.1 - admin
[28/Oct/2019:19:58:45 +] "GET /pulp/api/v3/status/ HTTP/1.0" 200 1366 "-"
"HTTPie/0.9.4"
Oct 28 15:58:50 ipaddr gunicorn[165752]: 127.0.0.1 - admin
[28/Oct/2019:19:58:50 +] "GET /pulp/api/v3/status/
DRF uses UTC because it expects whatever UI (CLI, web UI, etc) to convert
datetime fields to whatever timezone the user wants. It looks like there is
no out of the box solution for DRF or httpie to convert timezones. I think
we should file a story and look at it after the 3.0 GA.
David
On Mon,
Do you see anything in journalctl when the 500 response is generated? I
would expect a traceback in the pulp-api logs.
On Mon, Oct 28, 2019 at 3:16 PM Bin Li (BLOOMBERG/ 120 PARK) <
bli...@bloomberg.net> wrote:
> During a test to sync about 100 repositories, we suddenly got Error 500
> from
1. If you used the ansible-pulp installer, the systemd service file is
templated in such a way that you should be able to just start another
pulp-worker@{n} service. The worker name may be pulpcore-worker@{n} if you
are running a newer version of pulpcore.
2. I am not sure. Anyone else have a
During a test to sync about 100 repositories, we suddenly got Error 500 from
querying task status after first 20 sync tasks completed. Tried to restarted
all pulp daemons and still getting 500 errors. Both port 24816 and 24817 are
still listening and I am able to query postgres db with psql.
I have two questions1) By default there are 2 workers. I found many tasks are
in the waiting state. How I can increase the number of workers to reduce the
waiting time? What is the recommendation for number of workers?
2) Is it possible to use default os timezone for "pulp_created" time?
