CF push times out after exactly five minutes with 502 Bad Gateway
389 views
Skip to first unread message
Tony Perrin
Sep 26, 2014, 6:42:32 AM9/26/14
to vcap...@cloudfoundry.org
Hi guys.
I'm trying to push a war file to my CF space. The file I'm pushing weighs in at 240MB. Each time I push it it times out after exactly five minutes. I've set CF_TRACE=true and can see 502 Bad Gateway: Registered endpoint failed to handle the request. I've tried adding -m to define the memory size, increased CF_STAGING_TIMEOUT=10 but nothing I try makes any difference. There nothing in the log file to indicate any error. Ive pushed a small web service app from Spring.io to confirm everything works correctly which it does but it seems to me that the push is timing out at exactly five minutes on the larger files.
Are there any suggestions as to how I can successfully push a larger sized file?
Thank you.
Tony Perrin
For info, here's the command I'm using:
cf push AppName -p root.war -m 256M
Part of the response:
RESPONSE: [2014-09-26T11:31:19+01:00]
HTTP/1.1 502 Bad Gateway
Content-Length: 67
Connection: keep-alive
Content-Type: text/plain; charset=utf-8
Date: Fri, 26 Sep 2014 10:31:18 GMT
X-Cf-Requestid: 248b1d8e-aea4-4a21-67cb-6a2aa157d6af
X-Cf-Routererror: endpoint_failure
502 Bad Gateway: Registered endpoint failed to handle the request.
I'm trying to push a war file to my CF space. The file I'm pushing weighs in at 240MB. Each time I push it it times out after exactly five minutes. I've set CF_TRACE=true and can see 502 Bad Gateway: Registered endpoint failed to handle the request. I've tried adding -m to define the memory size, increased CF_STAGING_TIMEOUT=10 but nothing I try makes any difference. There nothing in the log file to indicate any error. Ive pushed a small web service app from Spring.io to confirm everything works correctly which it does but it seems to me that the push is timing out at exactly five minutes on the larger files.
Are there any suggestions as to how I can successfully push a larger sized file?
Thank you.
Tony Perrin
For info, here's the command I'm using:
cf push AppName -p root.war -m 256M
Part of the response:
RESPONSE: [2014-09-26T11:31:19+01:00]
HTTP/1.1 502 Bad Gateway
Content-Length: 67
Connection: keep-alive
Content-Type: text/plain; charset=utf-8
Date: Fri, 26 Sep 2014 10:31:18 GMT
X-Cf-Requestid: 248b1d8e-aea4-4a21-67cb-6a2aa157d6af
X-Cf-Routererror: endpoint_failure
502 Bad Gateway: Registered endpoint failed to handle the request.
Daniel Mikusa
Sep 26, 2014, 8:51:17 AM9/26/14
to vcap...@cloudfoundry.org
Tony,
As I understand it, gorouter will only wait so long for a request to be processed (I believe it's hard limit of five minutes by default).
If the request doesn't finish in that time, you'll get a 502. Since everything goes through gorouter, including api requests they are subject to that limit as well.
What is your target for cf? If it's a system you control, you could increase this value to give yourself more time to upload.
Dan
--
You received this message because you are subscribed to the Google Groups "Cloud Foundry Developers" group.
To view this discussion on the web visit https://groups.google.com/a/cloudfoundry.org/d/msgid/vcap-dev/4242a6b8-780c-46bd-b49c-5df03659c531%40cloudfoundry.org.
To unsubscribe from this group and stop receiving emails from it, send an email to vcap-dev+u...@cloudfoundry.org.
Reply all
Reply to author
Forward
0 new messages