unable to start the bootstrap: can't create new listener: listen unix /var/opt/gitlab/gitaly/gitaly.socket: protocol not available

Summary

After I upgraded from gitlab-ce-12.10.6 to 13.0.0, the gitaly server could not start after starting gitlab

As soon as I downgraded to 12.10.6, it returned to normal!

Relevant logs and/or screenshots

tail -f /var/log/gitlab/gitaly/current
{"gitaly":25176,"level":"info","msg":"monitoring gitaly","time":"2020-05-26T05:04:33Z","wrapper":25162}
time="2020-05-26T05:04:33Z" level=info msg="Starting Gitaly" version="Gitaly, version 13.0.0"
time="2020-05-26T05:04:33Z" level=warning msg="git path not configured. Using default path resolution" resolvedPath=/opt/gitlab/embedded/bin/git
time="2020-05-26T05:04:33Z" level=info msg="clearing disk cache object folder" path=/var/opt/gitlab/git-data/repositories
time="2020-05-26T05:04:33Z" level=info msg="moving disk cache object folder to /var/opt/gitlab/git-data/repositories/+gitaly/tmp/diskcache513287628" path=/var/opt/gitlab/git-data/repositories
time="2020-05-26T05:04:33Z" level=info msg="disk cache object folder doesn't exist, no need to remove" path=/var/opt/gitlab/git-data/repositories
time="2020-05-26T05:04:33Z" level=info msg="Starting file walker for /var/opt/gitlab/git-data/repositories/+gitaly/cache" path=/var/opt/gitlab/git-data/repositories/+gitaly/cache
time="2020-05-26T05:04:33Z" level=info msg="Starting file walker for /var/opt/gitlab/git-data/repositories/+gitaly/state" path=/var/opt/gitlab/git-data/repositories/+gitaly/state
time="2020-05-26T05:04:33Z" level=info msg="cleared all cache object files in /var/opt/gitlab/git-data/repositories/+gitaly/tmp/diskcache513287628 after 135.806µs" path=/var/opt/gitlab/git-data/repositories
{"error":"unable to start the bootstrap: can't create new listener: listen unix /var/opt/gitlab/gitaly/gitaly.socket: protocol not available","level":"error","msg":"shutting down","time":"2020-05-26T05:04:34.795Z"}
{"gitaly":25176,"level":"warning","msg":"forwarding signal","signal":17,"time":"2020-05-26T05:04:34Z","wrapper":25162}
{"error":"os: process already finished","gitaly":25176,"level":"error","msg":"can't forward the signal","signal":17,"time":"2020-05-26T05:04:34Z","wrapper":25162}
{"gitaly":25176,"level":"error","msg":"wrapper for gitaly shutting down","time":"2020-05-26T05:04:35Z","wrapper":25162}
{"level":"info","msg":"Wrapper started","time":"2020-05-26T05:04:35Z","wrapper":25191}
{"level":"info","msg":"finding gitaly","pid_file":"/var/opt/gitlab/gitaly/gitaly.pid","time":"2020-05-26T05:04:35Z","wrapper":25191}

The other components are normal. This log has been repeated repeatedly, how can I solve it!

gitlab.rb

external_url 'https://gitlab..com'
gitlab_rails['time_zone'] = ''
gitlab_rails['gitlab_email_enabled'] = true
gitlab_rails['gitlab_email_from'] = '.com'
gitlab_rails['gitlab_email_display_name'] = ''
gitlab_rails['gitlab_email_reply_to'] = 'noreply@.com'
gitlab_rails['smtp_enable'] = true
gitlab_rails['smtp_address'] = ".com"
gitlab_rails['smtp_port'] = 465
gitlab_rails['smtp_user_name'] = ".com"
gitlab_rails['smtp_password'] = ""
gitlab_rails['smtp_domain'] = ".com"
gitlab_rails['smtp_authentication'] = "login"
gitlab_rails['smtp_enable_starttls_auto'] = true
gitlab_rails['smtp_tls'] = true
registry_external_url 'https://registry..com:4443'
gitlab_rails['registry_enabled'] = true
gitlab_rails['registry_host'] = "registry..com"
unicorn['enable'] = false
puma['enable'] = true
puma['worker_processes'] = 4
puma['per_worker_max_memory_mb'] = 1024
nginx['enable'] = true
nginx['client_max_body_size'] = '250m'
nginx['redirect_http_to_https'] = false
nginx['ssl_client_certificate'] = "/etc/gitlab/ssl/ca.crt"
nginx['ssl_certificate'] = "/etc/gitlab/ssl/com.crt"
nginx['ssl_certificate_key'] = "/etc/gitlab/ssl/com.key"
nginx['ssl_ciphers'] = "ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256"
nginx['ssl_prefer_server_ciphers'] = "on"
nginx['ssl_protocols'] = "TLSv1.2 TLSv1.3"
registry_nginx['enable'] = true
registry_nginx['proxy_set_headers'] = {
  "Host" => "$http_host",
  "X-Real-IP" => "$remote_addr",
  "X-Forwarded-For" => "$proxy_add_x_forwarded_for",
  "X-Forwarded-Proto" => "https",
  "X-Forwarded-Ssl" => "on"
}

sql problem

After downgrading to 12.10.6, is there such an error in the startup log that it can be ignored?

==> /var/log/gitlab/postgresql/current <==
2020-05-26_06:17:02.58486 ERROR:  column "bot_type" does not exist at character 388
2020-05-26_06:17:02.58490 STATEMENT:  SELECT COUNT(*), admin, external, state, (COALESCE(u.access_level, 0)) AS access_level FROM users LEFT JOIN
2020-05-26_06:17:02.58493                     (
2020-05-26_06:17:02.58494                       SELECT
2020-05-26_06:17:02.58494                         members.user_id,
2020-05-26_06:17:02.58495                         MAX(access_level) as access_level
2020-05-26_06:17:02.58495                       FROM members
2020-05-26_06:17:02.58495                       GROUP BY members.user_id
2020-05-26_06:17:02.58496                     ) AS u
2020-05-26_06:17:02.58496                     ON users.id = u.user_id WHERE ghost IS NULL AND bot_type IS NULL GROUP BY admin, external, state, access_level;

env

cat /etc/redhat-release 
# Red Hat Enterprise Linux Server release 6.5 (Santiago)
CentOS release 6.7 (Final)

/label ~bug ~"🍎"