#108 Slow repo browsing

Slēgta
dmz atvēra pirms 11 mēnešiem · 6 komentāri

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 pievienoja etiķeti
Bug
pirms 11 mēnešiem
Uncled1023 komentēja pirms 11 mēnešiem
Īpašnieks

I’ll have to look into this.

I'll have to look into this.
dmz komentēja pirms 8 mēnešiem
Autors

Another 9h downtime yesterday. Are the servers OK?

Another 9h downtime yesterday. Are the servers OK?
Uncled1023 komentēja pirms 8 mēnešiem
Īpašnieks

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

@dmz Yea, it was just a network issue with the server.
dmz komentēja pirms 8 mēnešiem
Autors

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 komentēja pirms 8 mēnešiem
Īpašnieks

@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 komentēja pirms 8 mēnešiem
Autors

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.
Pierakstieties, lai pievienotos šai sarunai.
Nav atskaites punktu
Nav atbildīgo
2 dalībnieki
Izpildes termiņš

Izpildes termiņš nav uzstādīts.

Atkarības

Šai problēmai pagaidām nav nevienas atkarības.

Notiek ielāde…
Atcelt
Saglabāt
Vēl nav satura.