"panic: runtime error" / SIGSEGV with gitlab-shell 13.16.1 (running 13.9.1-ee)

When attempting to clone a repo via ssh, receive this error:

panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x8fa379]

goroutine 1 [running]:
gitlab.com/gitlab-org/gitlab-shell/internal/logger.Configure(0xc0001a6280)
        /var/cache/omnibus/src/gitlab-shell/internal/logger/logger.go:26 +0x129
main.main()
        /var/cache/omnibus/src/gitlab-shell/cmd/gitlab-shell/main.go:48 +0x162

This can be reproduced on the gitlab host itself with the following command:

$ sudo -u git -- /opt/gitlab/embedded/service/gitlab-shell/bin/gitlab-shell
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x8fa379]

goroutine 1 [running]:
gitlab.com/gitlab-org/gitlab-shell/internal/logger.Configure(0xc0001bc280)
        /var/cache/omnibus/src/gitlab-shell/internal/logger/logger.go:26 +0x129
main.main()
        /var/cache/omnibus/src/gitlab-shell/cmd/gitlab-shell/main.go:48 +0x162

Only found this mention of it online: FS#69642 : [gitlab-shell] sigsegv

This was not happening when we were on GitLab13.8.0-ee with GitLab Shell 13.15.0.

We can’t be the only ones to experience this, can we?

Found the problem. Described here:

Upshot: the log dir was not writable by git. Fixed by updating the perms.