#108 Slow repo browsing

Затворено
отворено пре 2 година од dmz · 6 коментара
dmz коментирира пре 2 година

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 пре 2 година
Uncled1023 коментирира пре 2 година
Власник

I’ll have to look into this.

I'll have to look into this.
dmz коментирира пре 2 година
Аутор

Another 9h downtime yesterday. Are the servers OK?

Another 9h downtime yesterday. Are the servers OK?
Uncled1023 коментирира пре 2 година
Власник

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

@dmz Yea, it was just a network issue with the server.
dmz коментирира пре 2 година
Аутор

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 коментирира пре 2 година
Власник

@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 коментирира пре 2 година
Аутор

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 затворено пре 2 година
Пријавите се да се прикључе у овом разговору.
Нема фазе
No Assignees
2 учесника
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
Откажи
Сачувај
Још нема садржаја.