rekor: 504 Gateway timeout on large file

Description

We are trying to use rekor to store our GH releases for Scorecard https://github.com/ossf/scorecard/issues/1201.

I ran into an issue with cosign that didn’t support timeout on sign-blob https://github.com/sigstore/cosign/issues/990 and am in the process of fixing that issue I ran into another issue with rekor.

HTTP/2.0 504 Gateway Timeout
Content-Length: 160
Content-Type: text/html
Date: Thu, 04 Nov 2021 17:59:15 GMT
Strict-Transport-Security: max-age=15724800; includeSubDomains

<html>
<head><title>504 Gateway Time-out</title></head>
<body>
<center><h1>504 Gateway Time-out</h1></center>
<hr><center>nginx</center>
</body>
</html>

Error: signing ./cosign: &{0 } (*models.Error) is not supported by the TextConsumer, can be resolved by supporting TextUnmarshaler interface
main.go:48: error during command execution: signing ./cosign: &{0 } (*models.Error) is not supported by the TextConsumer, can be resolved by supporting TextUnmarshaler interface

The size of the binary that I am trying to upload is 81M.

About this issue

Original URL
State: closed
Created 3 years ago
Comments: 18 (18 by maintainers)

Most upvoted comments

I was able to run the rekor server locally

Here is the server log after it is uploaded

rekor-rekor-server-1         | 2021-11-09T02:05:37.443Z	INFOrestapi/configure_rekor_server.go:144	[56593d4bf6fe/6kNG8UdoVI-000099] "POST http://172.19.0.4:3000/api/v1/log/entries HTTP/1.1" from 172.19.0.1:43450 - 409 153B in 1m44.88365215s

The 409 error code returned here after 104 seconds feels like the upload must have completed in order for us to have confirmed that there was an entry already in the log for this.

I will try to recreate this locally and see if I can run it down.

bobcallaway on Nov 9, 2021