This is a weird one. If I run `rake gitlab:backup:restore`, the gitlab-puma service will fail to start with the error above. But if I copy the file from /etc to /usr (overwriting the symlink), then Puma starts fine. So far as expected given the error. But then I can delete the copy of the config in /usr and put the symlink back and everything still works fine! I think this symlink check is only being run during some sort of first-run phase, perhaps while it updates some database keys or something. It does not attempt to write the config.yml file, my original one is fine. Once it does whatever else it does, it no longer cares if the config is symlinked.