Hi, I'm just testing gitlab and run into some problems that are not widely
discussed.
1. Apache web server is running on this system. I realized that Apache
httpd is blocking the omnibus nginx server. As soon as I turned off httpd,
I could get gitlab to open in browser.
Seems like gitlab-ombibus should raise an error or warning when Apache
httpd is already running in port 80. Don't you think so? Its fatal otherwise
What do gitlab users do when they have pre-existing projects that depend on
Apache. Is this where the re-configure gitlab to use Apache instructions
come into play?
I've been trying to figure out what's needed to have gitlab show up as one
of many services. Right now, it wants to answer at main server address, not
something like myserver.com/gitlab.
2. Gitlab seems to be working, but I am baffled by these warnings/errors at
beginning of reconfigure output.
# sudo gitlab-ctl reconfigure
the ffi-yajl and yajl-ruby gems have incompatible C libyajl libs and should
not be loaded in the same Ruby VM
falling back to ffi which might work (or might not, no promises)
Starting Chef Client, version 11.12.2
Compiling Cookbooks...
Recipe: gitlab::default
* directory[/etc/gitlab] action create
- change mode from '0755' to '0775'
- restore selinux security context
[2015-02-22T14:21:25-06:00] WARN: Cloning resource attributes for
directory[/var/opt/gitlab] from prior resource (CHEF-3694)
[2015-02-22T14:21:25-06:00] WARN: Previous directory[/var/opt/gitlab]:
/opt/gitlab/embedded/cookbooks/gitlab/recipes/default.rb:40:in `from_file'
[2015-02-22T14:21:25-06:00] WARN: Current directory[/var/opt/gitlab]:
/opt/gitlab/embedded/cookbooks/gitlab/recipes/users.rb:23:in `from_file'
[2015-02-22T14:21:26-06:00] WARN: Cloning resource attributes for
directory[/var/opt/gitlab/gitlab-rails/etc] from prior resource (CHEF-3694)
[2015-02-22T14:21:26-06:00] WARN: Previous
directory[/var/opt/gitlab/gitlab-rails/etc]:
/opt/gitlab/embedded/cookbooks/gitlab/recipes/gitlab-rails.rb:41:in `block
in from_file'
- execute initctl status gitlab-runsvdir
* execute[initctl start gitlab-runsvdir] action run (skipped due to
only_if)
Recipe: gitlab::redis
* group[gitlab-redis] action create (up to date)
* user[gitlab-redis] action create (up to date)
* directory[/var/opt/gitlab/redis] action create (up to date)
* directory[/var/log/gitlab/redis] action create (up to date)
* template[/var/opt/gitlab/redis/redis.conf] action create (up to date)
* directory[/opt/gitlab/sv/redis] action create (up to date)
* directory[/opt/gitlab/sv/redis/log] action create (up to date)
* directory[/opt/gitlab/sv/redis/log/main] action create (up to date)
* template[/opt/gitlab/sv/redis/run] action create (up to date)
* template[/opt/gitlab/sv/redis/log/run] action create (up to date)
* template[/var/log/gitlab/redis/config] action create (up to date)
* ruby_block[reload redis svlogd configuration] action nothing (skipped
due to action :nothing)
* file[/opt/gitlab/sv/redis/down] action delete (up to date)
* link[/opt/gitlab/init/redis] action create (up to date)
* link[/opt/gitlab/service/redis] action create (up to date)
* ruby_block[supervise_redis_sleep] action run (skipped due to not_if)
* service[redis] action nothing (skipped due to action :nothing)
Recipe: gitlab::ci-redis_disable
* link[/opt/gitlab/service/ci-redis] action delete (up to date)
Recipe: gitlab::postgresql
* group[gitlab-psql] action create (up to date)
* user[gitlab-psql] action create (up to date)
* directory[/var/opt/gitlab/postgresql] action create (up to date)
* directory[/var/opt/gitlab/postgresql/data] action create (up to date)
* directory[/var/log/gitlab/postgresql] action create (up to date)
* link[/var/opt/gitlab/postgresql/data] action create (skipped due to
not_if)
* file[/var/opt/gitlab/postgresql/.profile] action create (up to date)
* execute[sysctl] action nothing (skipped due to action :nothing)
* bash[add shm settings] action run (skipped due to not_if)
* execute[/opt/gitlab/embedded/bin/initdb -D
/var/opt/gitlab/postgresql/data -E UTF8] action run (skipped due to not_if)
* template[/var/opt/gitlab/postgresql/data/postgresql.conf] action create
(up to date)
* template[/var/opt/gitlab/postgresql/data/pg_hba.conf] action create (up
to date)
* template[/var/opt/gitlab/postgresql/data/pg_ident.conf] action create
(up to date)
* directory[/opt/gitlab/sv/postgresql] action create (up to date)
* directory[/opt/gitlab/sv/postgresql/log] action create (up to date)
* directory[/opt/gitlab/sv/postgresql/log/main] action create (up to date)
* template[/opt/gitlab/sv/postgresql/run] action create (up to date)
* template[/opt/gitlab/sv/postgresql/log/run] action create (up to date)
* template[/var/log/gitlab/postgresql/config] action create (up to date)
* ruby_block[reload postgresql svlogd configuration] action nothing
(skipped due to action :nothing)
* file[/opt/gitlab/sv/postgresql/down] action delete (up to date)
* directory[/opt/gitlab/sv/postgresql/control] action create (up to date)
* template[/opt/gitlab/sv/postgresql/control/t] action create (up to date)
* link[/opt/gitlab/init/postgresql] action create (up to date)
* link[/opt/gitlab/service/postgresql] action create (up to date)
[snip some pages of output]
Running handlers:
Running handlers complete
Chef Client finished, 15/164 resources updated in 21.013299863 seconds
gitlab Reconfigured!
# sudo gitlab-ctl status
run: logrotate: (pid 20041) 767s; run: log: (pid 488) 274372s
run: nginx: (pid 5931) 246160s; run: log: (pid 416) 274378s
run: postgresql: (pid 32684) 274416s; run: log: (pid 32683) 274416s
run: redis: (pid 32555) 274427s; run: log: (pid 32554) 274427s
run: sidekiq: (pid 21294) 129s; run: log: (pid 362) 274384s
run: unicorn: (pid 21373) 115s; run: log: (pid 313) 274390s
That means it is running, yes?
3. When I try to follow along with the instructions for interacting with
gitlab, using functions like "gem" and "bundle", I get error messages
saying those programs are not found. Have you seen that too?
--
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/89aac229-8387-4038-a713-58ca23fb7963%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
