Accidental upgrade from 13.0.6 to 13.2.2 broke gitlab-ce

Our system update process accidentally upgraded our production gitlab-ce server from 13.0.6 to 13.2.2. Now, the web UI returns a 500 error, and command line operations get this response:

$ git pull
remote:
remote: ========================================================================
remote:
remote: rpc error: code = Unavailable desc = all SubConns are in TransientFailure, latest connection error: connection error: desc = “transport: Error while dialing dial unix /var/opt/gitlab/gitaly/gitaly.socket: connect: connection refused”
remote:
remote: ========================================================================
remote:
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

Our dev server was at 13.1.3, and was also upgraded to 13.3.3 at the same time, and that server seems to be fine.

Help - I’m not sure where to even start debugging this!

Problem solved… we were able to track this down to an ownership issue with the gitlab backup directory (thanks NFS4!) that prevented the post-upgrade scripts to run. Once I ran gitlab-ctl upgrade, everything worked ok.