Http code 502 "Bad Gateway" when trying to upload a 2Gigs file to pulp

Support
#1

Problem:
When i try to upload a file over 1Gigs, I get a bad gateway. I can see in the journalctl via “journalctl -xeu docker-compose@pulp.service” that there is a “WORKER TIMEOUT” error, however either via settings.py or gunicorn.conf.py, I’m not able to get rid of the error, even tho the “dynaconf list” command shows my updated TIMEOUT via WORKER_TTL variable in settings.py
Expected outcome:
Upload the file to pulp
Pulpcore version:
3.17.1
Pulp plugins installed and their versions:
{
“component”: “rpm”,
“version”: “3.16.2”
},
{
“component”: “python”,
“version”: “3.6.0”
},
{
“component”: “maven”,
“version”: “0.3.2”
},
{
“component”: “file”,
“version”: “1.10.1”
},
{
“component”: “deb”,
“version”: “2.16.0”
},
{
“component”: “container”,
“version”: “2.10.0”
},
{
“component”: “certguard”,
“version”: “1.5.2”
},
{
“component”: “ansible”,
“version”: “0.11.1”
}
Operating system - distribution and version:
CentOS Linux 8

Other relevant data:

I’m using pulp in a docker container, the same found in “pulp in one container”.
I’ve added “client_max_body_size 4G;” to my nginx conf

#2

There is an api to upload files in chunks. Would that serve your usecase?

#3

I’ve been trying to upload via chunks, still get http 502.

#4

I would just like to change the gunicorn timeout

#5

Did you break down the file into smaller chunks?
Have you tried using the cli? pulp artifact upload --file <>

#6

I got it working with the API, it was a mistake on my part
Thanks a lot

1 Like
#7

If it’s not too embarrassing, would you mind summing up the mistake and the solution here?

#8

Default gunicorn worker timeout is set to 90 seconds, it can be bumped in case chunked upload does not help.

#9

Actually, we set it to 90 in our installer and operator, but @Joel_Toula seems to be using the single container, I’m bumping the timeout now: https://github.com/pulp/pulp-oci-images/pull/219

1 Like