Cannot Initialize Database and Activate Advanced Features for PostgreSQL using with v11.0.3 from source code.

Summary

Cannot Initialize Database and Activate Advanced Features for PostgreSQL using with v11.0.3 from source code.

Steps to reproduce

Following the step in 'Installation from source' (https://docs.gitlab.com/ee/install/installation.html)， and checkout the source code from 'v11.0.3' tag. When excute sudo -u git -H bundle exec rake gitlab:setup RAILS_ENV=production as Step 8. Initialize Database and Activate Advanced Features(https://docs.gitlab.com/ee/install/installation.html#initialize-database-and-activate-advanced-features)` in command line, return 'Failed to connect to Gitaly...Error: 14:Connect Failed' as the attachments.

Example Project

(If possible, please create an example project here on GitLab.com that exhibits the problematic behaviour, and link to it here in the bug report)

(If you are using an older version of GitLab, this will also determine whether the bug has been fixed in a more recent version)

What is the current bug behavior?

Cannot Initialize Database and Activate Advanced Features for PostgreSQL using with v11.0.3 from source code. 'Failed to connect to Gitaly...Error: 14:Connect Failed'

What is the expected correct behavior?

Can Initialize Database and Activate Advanced Features for PostgreSQL using with v11.0.3 from source code and complete the installation.

Relevant logs and/or screenshots

Output of checks

(If you are reporting a bug on GitLab.com, write: This bug happens on GitLab.com)

Results of GitLab environment info

Expand for output related to GitLab environment info

(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:env:info)
(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production)
as the env.log in the attachments.

Results of GitLab application Check

Expand for output related to the GitLab application check

(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)
(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)
as the check.log in attachments.

Possible fixes

(If you can, link to the line of code that might be responsible for the problem)