4 ms·
Last one we had was because the ssh connection was lost during the apt upgrade (gitlab omnibus ce). Another one I remember was when some new configuration key
by gregoriol 6y ago
Last one we had was because the ssh connection was lost during the apt upgrade (gitlab omnibus ce).
Another one I remember was when some new configuration key was needed and prevented one of the components from starting (took ~2 hours to find what it was).
It doesn't happen often, don't worry that much though, gitlab omnibus works well, but is hard to investigate/fix because it's huge and not a tech stack we do understand well since we mostly use gitlab-ctl commands, so when something goes wrong it's hard