Experiencing the same issue on CentOS 6.6, I have written it in the comment
section of the blog post about 7.10.

2015-04-23 0:51 GMT+02:00 Stack Kororā <i.am.st...@gmail.com>:

> Greetings,
>
> Just did an update from 7.9.1 to 7.10.0.
>
> # gitlab-ctl stop unicorn && gitlab-ctl stop sidekiq && gitlab-ctl stop
> nginx && gitlab-rake gitlab:backup:create && rpm -Uvh
> gitlab-ce-7.10.0~omnibus-1.x86_64.rpm && gitlab-ctl reconfigure &&
> gitlab-ctl restart
> ok: down: unicorn: 0s, normally up
> ok: down: sidekiq: 0s, normally up
> ok: down: nginx: 0s, normally up
> Dumping database ...
> Dumping PostgreSQL database gitlabhq_production ... [DONE]
> done
> Dumping repositories ...
> [snip]
> done
> Dumping uploads ...
> done
> Creating backup archive: 1429742349_gitlab_backup.tar ... done
> Uploading backup archive to remote storage  ... skipped
> Deleting tmp directories ... done
> Deleting old backups ... skipping
> Preparing...                ###########################################
> [100%]
>    1:gitlab-ce              ###########################################
> [100%]
> hostname: Unknown host
> gitlab postinstall: Thank you for installing GitLab!
> gitlab postinstall: Configure and start GitLab by running the following
> command:
> gitlab postinstall:
> gitlab postinstall: sudo gitlab-ctl reconfigure
> gitlab postinstall:
> gitlab postinstall: GitLab should be reachable at
> http://gitlab.example.com
> gitlab postinstall: Otherwise configure GitLab for your system by editing
> /etc/gitlab/gitlab.rb file
> gitlab postinstall: And running reconfigure again.
> gitlab postinstall:
> gitlab postinstall: For a comprehensive list of configuration options
> please see the Omnibus GitLab readme
> gitlab postinstall:
> https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/README.md
> gitlab postinstall:
> -bash: /usr/bin/gitlab-ctl: No such file or directory
> #
> # gitlab-ctl reconfigure && gitlab-ctl restart
> -bash: /usr/bin/gitlab-ctl: No such file or directory
> #
>
>
> This is on Scientific Linux 6.6 fully updated.
>
> None of the binaries are in the system path any more.
>
> This worked:
> # /opt/gitlab/bin/gitlab-ctl reconfigure && /opt/gitlab/bin/gitlab-ctl
> restart
>
>
> As far as I can tell, everything else is working too. No idea what
> happened. I can poke around in the RPM script later but I have to run to a
> dinner event and won't be back till really late. I thought I would report
> it in case anyone else had the issue.
>
> Thanks!
> ~Stack~
>
> --
> You received this message because you are subscribed to the Google Groups
> "GitLab" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to gitlabhq+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/gitlabhq/6d55a252-8f06-4c43-a97a-2504ea48f730%40googlegroups.com
> <https://groups.google.com/d/msgid/gitlabhq/6d55a252-8f06-4c43-a97a-2504ea48f730%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"GitLab" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to gitlabhq+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/gitlabhq/CALXQekvT%2B6RVCkC-DTV9O7ivTgvbyv3AVbx1XRVNYscsOhu%2BPQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to