Infrastructure/fedora-infrastructure

Fork 0

Anitya: I keep getting 504 Gateway Time-out when trying to edit #8479

New issue

Closed

opened 2019-12-23 19:21:01 +00:00 by eclipseo · 9 comments

eclipseo commented

2019-12-23 19:21:01 +00:00

I have a large set of projects to edit on Anitya to fix the homepages but when submitting the change I keep getting this error:

504 Gateway Time-out
The server didn't respond in time.

Is there anything that can be done to fix that?

Thank you and wishing you happy holidays.

I have a large set of projects to edit on Anitya to fix the homepages but when submitting the change I keep getting this error: ``` 504 Gateway Time-out The server didn't respond in time. ``` Is there anything that can be done to fix that? Thank you and wishing you happy holidays.

kevin commented

2019-12-23 20:29:12 +00:00

Does the timeout page have any other info on it?

Can you look at the page with the firefox or chrome inspector and see what exact ip address it came back from?

Does the timeout page have any other info on it? Can you look at the page with the firefox or chrome inspector and see what exact ip address it came back from?

kevin commented

2019-12-23 20:29:13 +00:00

Metadata Update from @kevin:

Issue priority set to: Waiting on Assignee (was: Needs Review)

**Metadata Update from @kevin**: - Issue priority set to: Waiting on Assignee (was: Needs Review)

eclipseo commented

2019-12-23 20:37:32 +00:00

Author

Does the timeout page have any other info on it?
Can you look at the page with the firefox or chrome inspector and see what exact ip address it came back from?

There's no other info on it. That's the Response I get from the server:

HTTP/2.0 504 Gateway Timeout
date: Mon, 23 Dec 2019 20:32:21 GMT
server: Apache
strict-transport-security: max-age=31536000; includeSubDomains; preload
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
referrer-policy: same-origin
cache-control: no-cache
content-type: text/html
apptime: D=30012077
x-fedora-proxyserver: proxy01.phx2.fedoraproject.org
x-fedora-requestid: XgEkVbThfs7M7h@ay1GrhQAAAA8
X-Firefox-Spdy: h2

> Does the timeout page have any other info on it? > Can you look at the page with the firefox or chrome inspector and see what exact ip address it came back from? There's no other info on it. That's the Response I get from the server: ``` HTTP/2.0 504 Gateway Timeout date: Mon, 23 Dec 2019 20:32:21 GMT server: Apache strict-transport-security: max-age=31536000; includeSubDomains; preload x-frame-options: SAMEORIGIN x-xss-protection: 1; mode=block x-content-type-options: nosniff referrer-policy: same-origin cache-control: no-cache content-type: text/html apptime: D=30012077 x-fedora-proxyserver: proxy01.phx2.fedoraproject.org x-fedora-requestid: XgEkVbThfs7M7h@ay1GrhQAAAA8 X-Firefox-Spdy: h2 ```

mizdebsk commented

2019-12-24 14:05:20 +00:00

Metadata Update from @mizdebsk:

Issue tagged with: release-monitoring

**Metadata Update from @mizdebsk**: - Issue tagged with: release-monitoring

cheese commented

2020-01-01 17:22:26 +00:00

maybe related: i try to add a package mapping
504 Gateway Time-out
The server didn't respond in time.

or via api:
HTTP/2 504
date: Wed, 01 Jan 2020 17:13:26 GMT
server: Apache
strict-transport-security: max-age=31536000; includeSubDomains; preload
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
referrer-policy: same-origin
cache-control: no-cache
content-type: text/html
apptime: D=30009382
x-fedora-proxyserver: proxy01.phx2.fedoraproject.org
x-fedora-requestid: XgzTNrIaII8Z3bEy7rhUSwAAAAE

<html>

504 Gateway Time-out

The server didn't respond in time. </html>

maybe related: i try to add a package mapping 504 Gateway Time-out The server didn't respond in time. or via api: HTTP/2 504 date: Wed, 01 Jan 2020 17:13:26 GMT server: Apache strict-transport-security: max-age=31536000; includeSubDomains; preload x-frame-options: SAMEORIGIN x-xss-protection: 1; mode=block x-content-type-options: nosniff referrer-policy: same-origin cache-control: no-cache content-type: text/html apptime: D=30009382 x-fedora-proxyserver: proxy01.phx2.fedoraproject.org x-fedora-requestid: XgzTNrIaII8Z3bEy7rhUSwAAAAE <html><body><h1>504 Gateway Time-out</h1> The server didn't respond in time. </body></html>

kevin commented

2020-01-21 19:01:40 +00:00

Is this still happening?

eclipseo commented

2020-01-21 20:42:27 +00:00

Author

Is this still happening?

Not right now, but it was happening after I edited several project in a row. I don't have anything to edit anymore so I can't check if it is still happening.

> Is this still happening? Not right now, but it was happening after I edited several project in a row. I don't have anything to edit anymore so I can't check if it is still happening.