tuminoid / gitlab-installer Goto Github PK

Thanks for all your work on this! It's come in very handy for trying out GitLab without much hassle. I think this issue might be more related to GitLab than to this installer, but I wanted to make sure you were aware of it.

I tried to install GitLab 8 using this, but there were a variety of errors, the first of which is in the issue title. I copied gitlab.rb.example to gitlab.rb and ran vagrant up. Here's a link to the console log showing the first error encountered: https://gist.github.com/joseph-onsip/8c1fada84998b8b9e7b5#file-gistfile1-txt-L807

I tried simply creating the directory (mkdir -p /var/opt/gitlab/nginx/conf) and reprovisioning (vagrant provision), which appeared to complete successfully, but visiting https://127.0.0.1:8443 gives a 500 response:

500

Whoops, something went wrong on our end.

Try refreshing the page, or going back and attempting the action again.

Please contact your GitLab administrator if this problem persists.

I did try going back to the bento/ubuntu-14.04 basebox from #3, but experienced the same error, so I don't think this is related to the switch to ubuntu/trusty64.

Finally, pinning to GitLab 7.14.3-ce.1 works for me: https://gist.github.com/joseph-onsip/a92b4fe5d5cc2d34d4c3

I'll probably keep investigating, as I'm eager to get this working with GitLab 8. Thanks again!

getting below error while bootstrapping a node.

Creating new client for
Creating new node for
Connecting to xxxx
xxx -----> Existing Chef installation detected
xxx Starting the first Chef Client run...
xx Starting Chef Client, version 11.10.4
xxx resolving cookbooks for run list: []
xxx Synchronizing Cookbooks:
xxx Compiling Cookbooks...
xxx [2017-01-18T11:31:25-05:00] WARN: Node myapps-drp-dev has an empty run list.
xxx Converging 0 resources

xxxx Running handlers:
xxxx [2017-01-18T11:31:25-05:00] ERROR: Running exception handlers
xxxx Running handlers complete
xxxx
xxxx [2017-01-18T11:31:25-05:00] ERROR: Exception handlers complete
xxxx [2017-01-18T11:31:25-05:00] FATAL: Stacktrace dumped to /var/chef/cache/chef-stacktrace.out
xxxx Chef Client failed. 0 resources updated in 2.889895 seconds
xxxx [2017-01-18T11:31:26-05:00] ERROR: "\xC3" on US-ASCII
xxxx [2017-01-18T11:31:26-05:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsucces
sfully (exit code 1)

your project runs without problems

But I cannot reach either of the the links you provide.
What am I doing wrong?

jennifer

I was wondering if you had a recommended method for backups? The docs I've found online say I should SSH into the vagrant box and use sudo gitlab-rake gitlab:backup:create (GitLab with the Omnibus package) or sudo -u git -H bundle exec rake gitlab:backup:create RAILS_ENV=production (GitLab from source). Is there an easier way? Does the vagrant box has a synced folder on the guest machine?

It would be nice if this project could create backups regularly in a Vagrant synced folder.

Kept getting the following error when gitlab was being installed:

E: Failed to fetch https://packages.gitlab.com/gitlab/gitlab-ce/ubuntu/pool/trusty/main/g/gitlab-ce/gitlab-ce_7.13.2-ce.0_amd64.deb Hash Sum mismatch

Following the advice on the gitlab forums I ran the installer manually in the VM using the following command which worked:

apt-get -o 'Acquire::PDiffs="false"' install gitlab-ce

Not sure whether it was something local to my setup or if this is happening to others.

As of Gitlab 11.5.3, the basebox of this project was uplifted to Ubuntu 18.04.

VMware testing is not possibe for me (no VMware licences), but if someone has the interest to test it and report back, it would be great.

Failed to fetch https://packages.gitlab.com/gitlab/gitlab-ce/ubuntu/pool/trusty/main/g/gitlab-ce/gitlab-ce_8.1.0-ce.1_amd64.deb GnuTLS recv error (-9): A TLS packet with unexpected length was received.

This project looks great! Can you consider contributing the Vagrantfile and the gitlab-ci and gitlab-ci-runner scripts to the gitlab-ci repo?

For GitLab itself we recommend using the cookbook https://gitlab.com/gitlab-org/cookbook-gitlab/ It would be great if you could use the cookbook instead of a script to install GitLab itself, see https://gitlab.com/gitlab-org/cookbook-gitlab/blob/master/Vagrantfile

I have created a modification using the vagrant box "bento/ubuntu-16.04" which supports virtualbox, vmware (fusion and workstation) and parallels providers. (see https://github.com/agiletechnologist/gitlab-installer to clone for testing). I have tested 2 of 6 tested. LXC did not change.

Changes

• Vagrantfile - Changed default box to "bento/ubuntu-16.04"
• Vagrantfile - Changed vmware_fusion to be vmware_desktop which will work with both vmware_fusion and vmware_workstation providers and removed override of the box for vmware_desktop
• Vagrantfile - fixed default for GITLAB_CPUS to match Documentation default of 2
• README.md - for new minimum memory default for GITLAB_MEMORY of 3072
• install-gitlab.sh - Added apt-get upgrade before installation to apply updates and security updates before installing.

Providers checked:

• virtualbox on Windows (Completed)

• virtualbox Linux

• virtualbox Mac

• vmware_workstation Windows (Completed)

• vmware_workstation Linux

• vmware_fusion Mac

• Parallels Mac

• LXC Linux Containers

Thanks for any help.

I'm having this issue as described on the gitlab forum
https://gitlab.com/gitlab-org/gitlab-ce/issues/24572#note_18580331

interestingly, it's same issue reported here (at least the same error message): https://bugs.launchpad.net/ubuntu/+source/linux/+bug/665163

could it be an EXT3 vs EXT4 thing?

As of Gitlab 11.5.3, the basebox of this project was uplifted to Ubuntu 18.04.

LXC testing has been missing for a longer time already, but if someone has the interest to test it and report back, it would be great.

I'm having some issues. Any idea what's causing this?

==> gitlab: stdin: is not a tty
==> gitlab: fatal: gitlab.rb not found at /vagrant
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.

I use Vagrant 1.7.2 on Ubuntu 14.04.

% vagrant -v
Vagrant 1.7.2

When I run vagrant up, I get the following error:

% vagrant up
Bringing machine 'gitlab' up with 'virtualbox' provider...
There are errors in the configuration of this machine. Please fix
the following errors and try again:

shell provisioner:
* The following settings shouldn't exist: env

According to this issue thread in another repository, I need to update to Vagrant > 1.8.

Perhaps the README.md file should be updated to reflect this?

Hi sir

I install gitlab via gitlab-installer ,but i got below error and I don't understand what's happen

==> gitlab: [2015-10-19T06:01:35+00:00] INFO: execute[clear the gitlab-rails cache] ran successfully
==> gitlab: [2015-10-19T06:01:35+00:00] INFO: remote_file[/var/opt/gitlab/gitlab-rails/VERSION] sending run action to bashmigrate gitlab-rails database
==> gitlab:
==> gitlab: ================================================================================
==> gitlab: Error executing action run on resource 'bash[migrate gitlab-rails database]'
==> gitlab: ================================================================================
==> gitlab:
==> gitlab:
==> gitlab: Mixlib::ShellOut::ShellCommandFailed
==> gitlab: ------------------------------------
==> gitlab: Expected process to exit with [0], but received '1'
==> gitlab:
==> gitlab: ---- Begin output of "bash" "/tmp/chef-script20151019-11190-1p7cccb" ----
==> gitlab:
==> gitlab: STDOUT: rake aborted!
==> gitlab:
==> gitlab: PG::ConnectionBad: could not connect to server: No such file or directory
==> gitlab:
==> gitlab: Is the server running locally and accepting
==> gitlab:
==> gitlab: connections on Unix domain socket "/var/opt/gitlab/postgresql/.s.PGSQL.5432"?
==> gitlab:
==> gitlab: /opt/gitlab/embedded/service/gem/ruby/2.1.0/gems/activerecord-4.1.12/lib/active_record/connection_adapters/postgresql_adapter.rb:888:in initialize' ==> gitlab: ==> gitlab: /opt/gitlab/embedded/service/gem/ruby/2.1.0/gems/activerecord-4.1.12/lib/active_record/connection_adapters/postgresql_adapter.rb:888:innew'
==> gitlab:
==> gitlab: /opt/gitlab/embedded/service/gem/ruby/2.1.0/gems/activerecord-4.1.12/lib/active_record/connection_adapters/postgresql_adapter.rb:888:in connect' ==> gitlab: ==> gitlab: /opt/gitlab/embedded/service/gem/ruby/2.1.0/gems/activerecord-4.1.12/lib/active_record/connection_adapters/postgresql_adapter.rb:568:ininitialize'
==> gitlab:
==> gitlab: /opt/gitlab/embedded/service/gem/ruby/2.1.0/gems/activerecord-4.1.12/lib/active_record/connection_adapters/postgresql_adapter.rb:41:in new' ==> gitlab: /opt/gitlab/embedded/service/gem/ruby/2.1.0/gems/activerecord-4.1.12/lib/active_record/connection_adapters/postgresql_adapter.rb:41:inpostgresql_connection'
==> gitlab: /opt/gitlab/embedded/service/gem/ruby/2.1.0/gems/activerecord-4.1.12/lib/active_record/connection_adapters/abstract/connection_pool.rb:435:in new_connection' ==> gitlab: /opt/gitlab/embedded/service/gem/ruby/2.1.0/gems/activerecord-4.1.12/lib/active_record/connection_adapters/abstract/connection_pool.rb:445:incheckout_new_connection'
==> gitlab: /opt/gitlab/embedded/service/gem/ruby/2.1.0/gems/activerecord-4.1.12/lib/active_record/connection_adapters/abstract/connection_pool.rb:416:in acquire_connection' ==> gitlab: /opt/gitlab/embedded/service/gem/ruby/2.1.0/gems/activerecord-4.1.12/lib/active_record/connection_adapters/abstract/connection_pool.rb:351:inblock in checkout'
==> gitlab: /opt/gitlab/embedded/service/gem/ruby/2.1.0/gems/activerecord-4.1.12/lib/active_record/connection_adapters/abstract/connection_pool.rb:350:in checkout' ==> gitlab: /opt/gitlab/embedded/service/gem/ruby/2.1.0/gems/activerecord-4.1.12/lib/active_record/connection_adapters/abstract/connection_pool.rb:265:inblock in connection'
==> gitlab: /opt/gitlab/embedded/service/gem/ruby/2.1.0/gems/activerecord-4.1.12/lib/active_record/connection_adapters/abstract/connection_pool.rb:264:in connection' ==> gitlab: /opt/gitlab/embedded/service/gem/ruby/2.1.0/gems/activerecord-4.1.12/lib/active_record/connection_adapters/abstract/connection_pool.rb:541:inretrieve_connection'
==> gitlab: /opt/gitlab/embedded/service/gem/ruby/2.1.0/gems/activerecord-4.1.12/lib/active_record/connection_handling.rb:113:in retrieve_connection' ==> gitlab: /opt/gitlab/embedded/service/gem/ruby/2.1.0/gems/activerecord-4.1.12/lib/active_record/connection_handling.rb:87:inconnection'
==> gitlab: /opt/gitlab/embedded/service/gem/ruby/2.1.0/gems/activerecord-4.1.12/lib/active_record/migration.rb:916:in initialize' ==> gitlab: /opt/gitlab/embedded/service/gem/ruby/2.1.0/gems/activerecord-4.1.12/lib/active_record/migration.rb:814:innew'
==> gitlab: /opt/gitlab/embedded/service/gem/ruby/2.1.0/gems/activerecord-4.1.12/lib/active_record/migration.rb:814:in up' ==> gitlab: /opt/gitlab/embedded/service/gem/ruby/2.1.0/gems/activerecord-4.1.12/lib/active_record/migration.rb:792:inmigrate'
==> gitlab: /opt/gitlab/embedded/service/gem/ruby/2.1.0/gems/activerecord-4.1.12/lib/active_record/railties/databases.rake:34:in block (2 levels) in <top (required)>' ==> gitlab: Tasks: TOP => db:migrate ==> gitlab: (See full trace by running task with --trace) ==> gitlab: STDERR: ==> gitlab: ---- End output of "bash" "/tmp/chef-script20151019-11190-1p7cccb" ---- ==> gitlab: Ran "bash" "/tmp/chef-script20151019-11190-1p7cccb" returned 1 ==> gitlab: ==> gitlab: Resource Declaration: ==> gitlab: --------------------- ==> gitlab: # In /opt/gitlab/embedded/cookbooks/cache/cookbooks/gitlab/definitions/migrate_database.rb ==> gitlab: ==> gitlab: 19: bash "migrate #{params[:name]} database" do ==> gitlab: 20: code <<-EOH ==> gitlab: 21: set -e ==> gitlab: 22: log_file="/tmp/#{params[:name]}-db-migrate-$(date +%s)-$$/output.log" ==> gitlab: 23: umask 077 ==> gitlab: 24: mkdir $(dirname ${log_file}) ==> gitlab: 25: #{params[:command]} 2>& 1 | tee ${log_file} ==> gitlab: 26: exit ${PIPESTATUS[0]} ==> gitlab: 27: EOH ==> gitlab: 28: action params[:action] ==> gitlab: 29: params[:restarts].each do |svc| ==> gitlab: 30: notifies :restart, svc, :immediately ==> gitlab: 31: end ==> gitlab: 32: end ==> gitlab: 33: end ==> gitlab: ==> gitlab: Compiled Resource: ==> gitlab: ------------------ ==> gitlab: # Declared in /opt/gitlab/embedded/cookbooks/cache/cookbooks/gitlab/definitions/migrate_database.rb:19:inblock in from_file'
==> gitlab:
==> gitlab: bash("migrate gitlab-rails database") do
==> gitlab: params {:command=>"/opt/gitlab/bin/gitlab-rake db:migrate", :action=>:nothing, :restarts=>[], :name=>"gitlab-rails"}
==> gitlab: action [:nothing]
==> gitlab: retries 0
==> gitlab: retry_delay 2
==> gitlab: default_guard_interpreter :default
==> gitlab: command "migrate gitlab-rails database"
==> gitlab: backup 5
==> gitlab: returns 0
==> gitlab: code " set -e\n log_file="/tmp/gitlab-rails-db-migrate-$(date +%s)-$$/output.log"\n umask 077\n mkdir $(dirname ${log_file})\n /opt/gitlab/bin/gitlab-rake db:migrate 2>& 1 | tee ${log_file}\n exit ${PIPESTATUS[0]}\n"
==> gitlab: interpreter "bash"
==> gitlab: declared_type :bash
==> gitlab: cookbook_name "gitlab"
==> gitlab: recipe_name "database_migrations"
==> gitlab: end
==> gitlab:
==> gitlab:
==> gitlab: [2015-10-19T06:01:50+00:00] INFO: template[/var/log/gitlab/redis/config] sending create action to ruby_blockreload redis svlogd configuration
==> gitlab: [2015-10-19T06:01:50+00:00] INFO: ruby_block[reload redis svlogd configuration] called
==> gitlab: [2015-10-19T06:01:50+00:00] INFO: template[/var/log/gitlab/postgresql/config] sending create action to ruby_blockreload postgresql svlogd configuration
==> gitlab: [2015-10-19T06:01:50+00:00] INFO: ruby_block[reload postgresql svlogd configuration] called
==> gitlab: [2015-10-19T06:01:50+00:00] INFO: template[/var/log/gitlab/unicorn/config] sending create action to ruby_blockreload unicorn svlogd configuration
==> gitlab: [2015-10-19T06:01:50+00:00] INFO: ruby_block[reload unicorn svlogd configuration] called
==> gitlab: [2015-10-19T06:01:50+00:00] INFO: template[/var/log/gitlab/sidekiq/config] sending create action to ruby_blockreload sidekiq svlogd configuration
==> gitlab: [2015-10-19T06:01:50+00:00] INFO: ruby_block[reload sidekiq svlogd configuration] called
==> gitlab: [2015-10-19T06:01:50+00:00] INFO: template[/var/log/gitlab/gitlab-git-http-server/config] sending create action to ruby_blockreload gitlab-git-http-server svlogd configuration
==> gitlab: [2015-10-19T06:01:50+00:00] INFO: ruby_block[reload gitlab-git-http-server svlogd configuration] called
==> gitlab: [2015-10-19T06:01:50+00:00] INFO: template[/var/log/gitlab/nginx/config] sending create action to ruby_blockreload nginx svlogd configuration
==> gitlab: [2015-10-19T06:01:50+00:00] INFO: ruby_block[reload nginx svlogd configuration] called
==> gitlab: [2015-10-19T06:01:50+00:00] INFO: template[/var/log/gitlab/logrotate/config] sending create action to ruby_blockreload logrotate svlogd configuration
==> gitlab: [2015-10-19T06:01:50+00:00] INFO: ruby_block[reload logrotate svlogd configuration] called
==> gitlab: [2015-10-19T06:01:50+00:00] ERROR: Running exception handlers
==> gitlab: [2015-10-19T06:01:50+00:00] ERROR: Exception handlers complete
==> gitlab: [2015-10-19T06:01:51+00:00] FATAL: Stacktrace dumped to /opt/gitlab/embedded/cookbooks/cache/chef-stacktrace.out
==> gitlab: [2015-10-19T06:01:51+00:00] ERROR: bash[migrate gitlab-rails database](gitlab::database_migrations line 19) had an error: Mixlib::ShellOut::ShellCommandFailed: Expected process to exit with [0], but received '1'
==> gitlab: ---- Begin output of "bash" "/tmp/chef-script20151019-11190-1p7cccb" ----
==> gitlab: STDOUT: rake aborted!
==> gitlab: PG::ConnectionBad: could not connect to server: No such file or directory
==> gitlab: Is the server running locally and accepting
==> gitlab: connections on Unix domain socket "/var/opt/gitlab/postgresql/.s.PGSQL.5432"?
==> gitlab: /opt/gitlab/embedded/service/gem/ruby/2.1.0/gems/activerecord-4.1.12/lib/active_record/connection_adapters/postgresql_adapter.rb:888:in initialize' ==> gitlab: /opt/gitlab/embedded/service/gem/ruby/2.1.0/gems/activerecord-4.1.12/lib/active_record/connection_adapters/postgresql_adapter.rb:888:innew'
==> gitlab: /opt/gitlab/embedded/service/gem/ruby/2.1.0/gems/activerecord-4.1.12/lib/active_record/connection_adapters/postgresql_adapter.rb:888:in connect' ==> gitlab: /opt/gitlab/embedded/service/gem/ruby/2.1.0/gems/activerecord-4.1.12/lib/active_record/connection_adapters/postgresql_adapter.rb:568:ininitialize'
==> gitlab: /opt/gitlab/embedded/service/gem/ruby/2.1.0/gems/activerecord-4.1.12/lib/active_record/connection_adapters/postgresql_adapter.rb:41:in new' ==> gitlab: /opt/gitlab/embedded/service/gem/ruby/2.1.0/gems/activerecord-4.1.12/lib/active_record/connection_adapters/postgresql_adapter.rb:41:inpostgresql_connection'
==> gitlab: /opt/gitlab/embedded/service/gem/ruby/2.1.0/gems/activerecord-4.1.12/lib/active_record/connection_adapters/abstract/connection_pool.rb:435:in new_connection' ==> gitlab: /opt/gitlab/embedded/service/gem/ruby/2.1.0/gems/activerecord-4.1.12/lib/active_record/connection_adapters/abstract/connection_pool.rb:445:incheckout_new_connection'
==> gitlab: /opt/gitlab/embedded/service/gem/ruby/2.1.0/gems/activerecord-4.1.12/lib/active_record/connection_adapters/abstract/connection_pool.rb:416:in acquire_connection' ==> gitlab: /opt/gitlab/embedded/service/gem/ruby/2.1.0/gems/activerecord-4.1.12/lib/active_record/connection_adapters/abstract/connection_pool.rb:351:inblock in checkout'
==> gitlab: /opt/gitlab/embedded/service/gem/ruby/2.1.0/gems/activerecord-4.1.12/lib/active_record/connection_adapters/abstract/connection_pool.rb:350:in checkout' ==> gitlab: /opt/gitlab/embedded/service/gem/ruby/2.1.0/gems/activerecord-4.1.12/lib/active_record/connection_adapters/abstract/connection_pool.rb:265:inblock in connection'
==> gitlab: /opt/gitlab/embedded/service/gem/ruby/2.1.0/gems/activerecord-4.1.12/lib/active_record/connection_adapters/abstract/connection_pool.rb:264:in connection' ==> gitlab: /opt/gitlab/embedded/service/gem/ruby/2.1.0/gems/activerecord-4.1.12/lib/active_record/connection_adapters/abstract/connection_pool.rb:541:inretrieve_connection'
==> gitlab: /opt/gitlab/embedded/service/gem/ruby/2.1.0/gems/activerecord-4.1.12/lib/active_record/connection_handling.rb:113:in retrieve_connection' ==> gitlab: /opt/gitlab/embedded/service/gem/ruby/2.1.0/gems/activerecord-4.1.12/lib/active_record/connection_handling.rb:87:inconnection'
==> gitlab: /opt/gitlab/embedded/service/gem/ruby/2.1.0/gems/activerecord-4.1.12/lib/active_record/migration.rb:916:in initialize' ==> gitlab: /opt/gitlab/embedded/service/gem/ruby/2.1.0/gems/activerecord-4.1.12/lib/active_record/migration.rb:814:innew'
==> gitlab: /opt/gitlab/embedded/service/gem/ruby/2.1.0/gems/activerecord-4.1.12/lib/active_record/migration.rb:814:in up' ==> gitlab: /opt/gitlab/embedded/service/gem/ruby/2.1.0/gems/activerecord-4.1.12/lib/active_record/migration.rb:792:inmigrate'
==> gitlab: /opt/gitlab/embedded/service/gem/ruby/2.1.0/gems/activerecord-4.1.12/lib/active_record/railties/databases.rake:34:in `block (2 levels) in <top (required)>'
==> gitlab: Tasks: TOP => db:migrate
==> gitlab: (See full trace by running task with --trace)
==> gitlab: STDERR:
==> gitlab: ---- End output of "bash" "/tmp/chef-script20151019-11190-1p7cccb" ----
==> gitlab: Ran "bash" "/tmp/chef-script20151019-11190-1p7cccb" returned 1
==> gitlab: [2015-10-19T06:01:51+00:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1)
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.