#108 Slow repo browsing

Chiuso
aperto 11 mesi fa da dmz · 6 commenti
dmz 11 mesi fa ha commentato

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 mesi fa
Uncled1023 11 mesi fa ha commentato
Proprietario

I’ll have to look into this.

I'll have to look into this.
dmz 8 mesi fa ha commentato
Autore

Another 9h downtime yesterday. Are the servers OK?

Another 9h downtime yesterday. Are the servers OK?
Uncled1023 8 mesi fa ha commentato
Proprietario

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

@dmz Yea, it was just a network issue with the server.
dmz 8 mesi fa ha commentato
Autore

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 8 mesi fa ha commentato
Proprietario

@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 8 mesi fa ha commentato
Autore

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 chiuso 8 mesi fa
Effettua l'accesso per partecipare alla conversazione.
Nessuna milestone
No Assignees
2 Partecipanti
Data di scadenza

Nessuna data di scadenza impostata.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
Annulla
Salva
Non ci sono ancora contenuti.