Unable to configure GitLab in our local server.

While migrating GitLab version 9.0, I couldn't able to access GitLab via browser due to the nginx service entered FATAL state. The detailed log is given below

2017-03-29T18:46:11.555207000Z 2017-03-30 00:16:11,554 CRIT Supervisor running as root (no user in config file)
2017-03-29T18:46:11.555599000Z 2017-03-30 00:16:11,554 WARN Included extra file "/etc/supervisor/conf.d/cron.conf" during parsing
2017-03-29T18:46:11.555908000Z 2017-03-30 00:16:11,554 WARN Included extra file "/etc/supervisor/conf.d/gitlab-workhorse.conf" during parsing
2017-03-29T18:46:11.556216000Z 2017-03-30 00:16:11,554 WARN Included extra file "/etc/supervisor/conf.d/mail_room.conf" during parsing
2017-03-29T18:46:11.556536000Z 2017-03-30 00:16:11,554 WARN Included extra file "/etc/supervisor/conf.d/nginx.conf" during parsing
2017-03-29T18:46:11.556835000Z 2017-03-30 00:16:11,554 WARN Included extra file "/etc/supervisor/conf.d/sidekiq.conf" during parsing
2017-03-29T18:46:11.557144000Z 2017-03-30 00:16:11,554 WARN Included extra file "/etc/supervisor/conf.d/sshd.conf" during parsing
2017-03-29T18:46:11.557456000Z 2017-03-30 00:16:11,554 WARN Included extra file "/etc/supervisor/conf.d/unicorn.conf" during parsing
2017-03-29T18:46:11.557755000Z 2017-03-30 00:16:11,554 WARN Included extra file "/etc/supervisor/conf.d/gitlab-pages.conf" during parsing
2017-03-29T18:46:11.589807000Z 2017-03-30 00:16:11,589 INFO RPC interface 'supervisor' initialized
2017-03-29T18:46:11.590115000Z 2017-03-30 00:16:11,589 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2017-03-29T18:46:11.590453000Z 2017-03-30 00:16:11,589 INFO supervisord started with pid 1
2017-03-29T18:46:12.592865000Z 2017-03-30 00:16:12,592 INFO spawned: 'sidekiq' with pid 3207
2017-03-29T18:46:12.594703000Z 2017-03-30 00:16:12,593 INFO spawned: 'unicorn' with pid 3208
2017-03-29T18:46:12.596944000Z 2017-03-30 00:16:12,596 INFO spawned: 'gitlab-workhorse' with pid 3209
2017-03-29T18:46:12.598545000Z 2017-03-30 00:16:12,597 INFO spawned: 'cron' with pid 3210
2017-03-29T18:46:12.600138000Z 2017-03-30 00:16:12,599 INFO spawned: 'nginx' with pid 3211
2017-03-29T18:46:12.602225000Z 2017-03-30 00:16:12,601 INFO spawned: 'gitlab-pages' with pid 3212
2017-03-29T18:46:12.604253000Z 2017-03-30 00:16:12,603 INFO spawned: 'sshd' with pid 3213
2017-03-29T18:46:12.621378000Z 2017-03-30 00:16:12,620 INFO exited: nginx (exit status 1; not expected)
2017-03-29T18:46:14.522376000Z 2017-03-30 00:16:14,521 INFO success: sidekiq entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2017-03-29T18:46:14.522657000Z 2017-03-30 00:16:14,521 INFO success: unicorn entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2017-03-29T18:46:14.522873000Z 2017-03-30 00:16:14,521 INFO success: gitlab-workhorse entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2017-03-29T18:46:14.523092000Z 2017-03-30 00:16:14,521 INFO success: cron entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2017-03-29T18:46:14.523319000Z 2017-03-30 00:16:14,522 INFO spawned: 'nginx' with pid 3227
2017-03-29T18:46:14.523561000Z 2017-03-30 00:16:14,523 INFO success: gitlab-pages entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2017-03-29T18:46:14.523773000Z 2017-03-30 00:16:14,523 INFO success: sshd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2017-03-29T18:46:14.538679000Z 2017-03-30 00:16:14,538 INFO exited: nginx (exit status 1; not expected)
2017-03-29T18:46:16.541456000Z 2017-03-30 00:16:16,540 INFO spawned: 'nginx' with pid 3228
2017-03-29T18:46:16.565919000Z 2017-03-30 00:16:16,553 INFO exited: nginx (exit status 1; not expected)
2017-03-29T18:46:19.570145000Z 2017-03-30 00:16:19,569 INFO spawned: 'nginx' with pid 3229
2017-03-29T18:46:19.583358000Z 2017-03-30 00:16:19,582 INFO exited: nginx (exit status 1; not expected)
2017-03-29T18:46:20.584889000Z 2017-03-30 00:16:20,584 INFO gave up: nginx entered FATAL state, too many start retries too quickly

kindly help me to fix this issue.

Start by reproducing the GitLab 9.0 migration and checking nginx's own error output alongside the Supervisor log; the payload only shows repeated exit status 1. Investigate the local Dockerized GitLab configuration until nginx stays running and GitLab is reachable through the browser.