#108 Slow repo browsing

Gesloten
10 maanden geleden werd geopend door dmz · 6 opmerkingen

A couple of weeks ago, Teknik was offline for several hours, not sure what happened but, since then, accessing git repos, browsing folders and committing changes became slower than usual. Maybe some caching issue.

A couple of weeks ago, Teknik was offline for several hours, not sure what happened but, since then, accessing git repos, browsing folders and committing changes became slower than usual. Maybe some caching issue.
Uncled1023 added the
Bug
label 10 maanden geleden
Uncled1023 reageerde 10 maanden geleden
Eigenaar

I’ll have to look into this.

I'll have to look into this.
dmz reageerde 8 maanden geleden
Poster

Another 9h downtime yesterday. Are the servers OK?

Another 9h downtime yesterday. Are the servers OK?
Uncled1023 reageerde 8 maanden geleden
Eigenaar

@dmz Yea, it was just a network issue with the server.

@dmz Yea, it was just a network issue with the server.
dmz reageerde 8 maanden geleden
Poster

Just a follow-up, committing changes can take up to ~2 min and since the last downtime, it’s always returning the error message below. Nonetheless, hitting the browser back button returns to the editing page and by cancelling, I realize the changes have been successfully committed.

502 - Web server received an invalid response while acting as a gateway or proxy server. There is a problem with the page you are looking for, and it cannot be displayed. When the Web server (while acting as a gateway or proxy) contacted the upstream content server, it received an invalid response from the content server.

Just a follow-up, committing changes can take up to ~2 min and since the last downtime, it's always returning the error message below. Nonetheless, hitting the browser back button returns to the editing page and by cancelling, I realize the changes have been successfully committed. > 502 - Web server received an invalid response while acting as a gateway or proxy server. There is a problem with the page you are looking for, and it cannot be displayed. When the Web server (while acting as a gateway or proxy) contacted the upstream content server, it received an invalid response from the content server.
Uncled1023 reageerde 7 maanden geleden
Eigenaar

@dmz This should now be fixed. Can you give it a whirl and see if you notice the slowdowns anymore?

@dmz This should now be fixed. Can you give it a whirl and see if you notice the slowdowns anymore?
dmz reageerde 7 maanden geleden
Poster

Thanks a lot @Uncled1023.
I tested it and it seems back to normal speed.
Cheers.

Thanks a lot @Uncled1023. I tested it and it seems back to normal speed. Cheers.
dmz gesloten om 7 maanden geleden
Sign in to join this conversation.
Geen mijlpaal
Niet toegewezen
2 deelnemers
Vervaldatum

Geen vervaldatum ingesteld.

Afhankelijkheden

This issue currently doesn't have any dependencies.

Laden…
Annuleren
Opslaan
Er is nog geen inhoud.