Receiving 502 error after new install

I have read over all the other issues related to this error but all of them took into consideration that nginx was installed separately from GitLab. I followed the instructions for installing to an Oracle 7 vm but when I open a browser on my host and point to the external URL I configured in GitLab, I get a 502 - GitLab is taking too much time to respond.I checked the error log and traced it to the one nginx writes out:

2018/03/27 07:01:56 [crit] 11972#0: *65 connect() to unix:/var/opt/gitlab/gitlab-workhorse/socket failed (13: Permission denied) while connecting to upstream, client: 10.27.10.182, server: ####gitprweb1, request: "GET / HTTP/1.1", upstream: "http://unix:/var/opt/gitlab/gitlab-workhorse/socket:/", host: "####gitprweb1"

This is on a new install following the instructions and using the bundled nginx. I've spent the past day trying various solutions but nothing works. The only thing I can think of is IT setup this VM in a way that invalidates this install. I do remember the gitlab directories were already available. Maybe them being root/root is causing the problem? I ran the reconfigure to see if GitLab would reset anything but that didn't work either. The folder permissions look fine:

total 92
drwx------+ 3 git               root         25 Mar 26 09:43 git-data
drwxr-xr-x+ 3 git               root         19 Mar 26 09:43 gitlab-ci
drwx------+ 2 git               root          6 Mar 26 09:43 backups
-rw-rw-r--+ 1 root              root         40 Mar 26 09:43 trusted-certs-directory-hash
drwxr-x---+ 9 root              gitlab-www 4096 Mar 26 09:45 nginx
-rw-------+ 1 root              root         38 Mar 26 09:45 bootstrapped
drwxrwxr-x+ 3 root              root         31 Mar 26 09:45 node-exporter
drwx------+ 2 git               root         23 Mar 27 06:59 gitlab-shell
drwxr-xr-x+ 9 git               root       4096 Mar 27 07:00 gitlab-rails
drwxr-xr-x+ 3 gitlab-psql       root         77 Mar 27 07:00 postgresql
drwx------+ 3 root              root         68 Mar 27 07:00 logrotate
drwxr-x---+ 2 git               gitlab-www   51 Mar 27 07:00 gitlab-workhorse
drwx------+ 2 git               root         44 Mar 27 07:00 gitaly
drwxr-xr-x+ 2 git               root         31 Mar 27 07:00 gitlab-monitor
drwxr-x---+ 3 gitlab-prometheus root         38 Mar 27 07:00 prometheus
drwx------+ 2 gitlab-psql       root         25 Mar 27 07:00 postgres-exporter
-rw-r--r--+ 1 root              root        191 Mar 27 07:00 public_attributes.json
drwxr-x---+ 2 gitlab-redis      git          57 Mar 27 07:43 redis

Here's the output from list-all:

[####user@####gitprweb1 gitlab]$ sudo firewall-cmd --list-all
public (active)
  target: default
  icmp-block-inversion: no
  interfaces: ens160
  sources:
  services: dhcpv6-client ssh http
  ports:
  protocols:
  masquerade: no
  forward-ports:
  source-ports:
  icmp-blocks:
  rich rules:

Here's the contents of the /opt/gitlab/sv/gitlab-workhorse/run:

#!/bin/sh
set -e # fail on errors

# Redirect stderr -> stdout
exec 2>&1



cd /var/opt/gitlab/gitlab-workhorse

exec chpst -e /opt/gitlab/etc/gitlab-workhorse/env -P \
  -U git \
  -u git \
  /opt/gitlab/embedded/bin/gitlab-workhorse \
    -listenNetwork unix \
    -listenUmask 0 \
    -listenAddr /var/opt/gitlab/gitlab-workhorse/socket \
    -authBackend http://localhost:8080 \
    -authSocket /var/opt/gitlab/gitlab-rails/sockets/gitlab.socket \
    -documentRoot /opt/gitlab/embedded/service/gitlab-rails/public \
    -pprofListenAddr ''\
    -prometheusListenAddr localhost:9229 \
    -secretPath /opt/gitlab/embedded/service/gitlab-rails/.gitlab_workhorse_secret \
    -config config.toml \

# Do not remove this line; it prevents trouble with the trailing backslashes above.

I've ran status on gitlab and everything looks fine:

run: gitaly: (pid 12625) 82435s; run: log: (pid 12136) 82483s
run: gitlab-monitor: (pid 12640) 82434s; run: log: (pid 12356) 82471s
run: gitlab-workhorse: (pid 12613) 82435s; run: log: (pid 11908) 82501s
run: logrotate: (pid 483) 3288s; run: log: (pid 12030) 82489s
run: nginx: (pid 11970) 82495s; run: log: (pid 11969) 82495s
run: node-exporter: (pid 12302) 82477s; run: log: (pid 12301) 82477s
run: postgres-exporter: (pid 12676) 82433s; run: log: (pid 12526) 82452s
run: postgresql: (pid 11472) 82550s; run: log: (pid 11471) 82550s
run: prometheus: (pid 12660) 82433s; run: log: (pid 12458) 82458s
run: redis: (pid 11343) 82556s; run: log: (pid 11342) 82556s
run: redis-exporter: (pid 12405) 82464s; run: log: (pid 12404) 82464s
run: sidekiq: (pid 11850) 82507s; run: log: (pid 11849) 82507s
run: unicorn: (pid 11786) 82513s; run: log: (pid 11785) 82513s

Here's the outout to the rake info command:

sudo gitlab-rake gitlab:env:info
<main>: warning: pthread_create failed for timer: Invalid argument, scheduling broken

System information
System:
Current User:   git
Using RVM:      no
Ruby Version:   2.3.6p384
Gem Version:    2.6.13
<main>: warning: pthread_create failed for timer: Invalid argument, scheduling broken
Bundler Version:1.13.7
Rake Version:   12.3.0
Redis Version:  3.2.11
Git Version:    2.14.3
Sidekiq Version:5.0.5
Go Version:     unknown

GitLab information
Version:        10.6.0
Revision:       8f82e53
Directory:      /opt/gitlab/embedded/service/gitlab-rails
DB Adapter:     postgresql
URL:            http://####gitprweb1
HTTP Clone URL: http://####gitprweb1/some-group/some-project.git
SSH Clone URL:  git@####gitprweb1:some-group/some-project.git
Using LDAP:     no
Using Omniauth: no

GitLab Shell
Version:        6.0.4
Repository storage paths:
- default:      /var/opt/gitlab/git-data/repositories
Hooks:          /opt/gitlab/embedded/service/gitlab-shell/hooks
Git:            /opt/gitlab/embedded/bin/git

And for kicks ran the rake check command:

sudo gitlab-rake gitlab:check
<main>: warning: pthread_create failed for timer: Invalid argument, scheduling broken
Checking GitLab Shell ...

GitLab Shell version >= 6.0.4 ? ... OK (6.0.4)
Repo base directory exists?
default... yes
Repo storage directories are symlinks?
default... no
Repo paths owned by git:root, or git:git?
default... yes
Repo paths access is drwxrws---?
default... yes
hooks directories in repos are links: ... can't check, you have no projects
Running /opt/gitlab/embedded/service/gitlab-shell/bin/check
<main>: warning: pthread_create failed for timer: Invalid argument, scheduling broken
Check GitLab API access: OK
Redis available via internal API: OK

Access to /var/opt/gitlab/.ssh/authorized_keys: <main>: warning: pthread_create failed for timer: Invalid argument, scheduling broken
OK
gitlab-shell self-check successful

Checking GitLab Shell ... Finished

Checking Sidekiq ...

Running? ... yes
Number of Sidekiq processes ... 1

Checking Sidekiq ... Finished

Reply by email is disabled in config/gitlab.yml
Checking LDAP ...

LDAP is disabled in config/gitlab.yml

Checking LDAP ... Finished

Checking GitLab ...

Git configured correctly? ... yes
Database config exists? ... yes
All migrations up? ... yes
Database contains orphaned GroupMembers? ... no
GitLab config exists? ... yes
GitLab config up to date? ... yes
Log directory writable? ... yes
Tmp directory writable? ... yes
Uploads directory exists? ... yes
Uploads directory has correct permissions? ... yes
Uploads directory tmp has correct permissions? ... skipped (no tmp uploads folder yet)
Init script exists? ... skipped (omnibus-gitlab has no init script)
Init script up-to-date? ... skipped (omnibus-gitlab has no init script)
Projects have namespace: ... can't check, you have no projects
Redis version >= 2.8.0? ... yes
Ruby version >= 2.3.5 ? ... yes (2.3.6)
Git version >= 2.9.5 ? ... yes (2.14.3)
Git user has default SSH configuration? ... yes
Active users: ... 1

Checking GitLab ... Finished

Any ideas? Hate to abandon GitLab but I need to build a code repo this week since our GitLab 7.10 has gone haywire over the past 3 months. This build is on a new VM, not the one where are currently running 7.10.

Thanks, PJ