#108 Slow repo browsing

Zamknięty
otworzone 11 miesięcy temu przez dmz · 6 komentarzy
dmz skomentował 11 miesięcy temu

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 11 miesięcy temu
Uncled1023 skomentował 11 miesięcy temu
Właściciel

I’ll have to look into this.

I'll have to look into this.
dmz skomentował 8 miesięcy temu
Autor

Another 9h downtime yesterday. Are the servers OK?

Another 9h downtime yesterday. Are the servers OK?
Uncled1023 skomentował 8 miesięcy temu
Właściciel

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

@dmz Yea, it was just a network issue with the server.
dmz skomentował 8 miesięcy temu
Autor

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 skomentował 8 miesięcy temu
Właściciel

@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 skomentował 8 miesięcy temu
Autor

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.
Zaloguj się, aby dołączyć do tej rozmowy.
Brak kamienia milowego
Brak przypisanych
2 uczestników
Due Date

No due date set.

Zależności

This issue currently doesn't have any dependencies.

Ładowanie…
Anuluj
Zapisz
Nie ma jeszcze treści.