[SOLVED] No troubleshooting seems to help

my repositories are not being created, at least that is what appears to be. Further investigations show
a) my git user account was “lock”, no password
b) running all those rails checking tasks would fail because ‘bundle’ was not found
c) when I unlocked git account and added a password, things still wouldn’t work because /opt/gitlab/embedded/bin wasn’t in any path
d) fixed the path issue with a custom .bashrc, now things run, but “GemFile” not found
e) troubleshooting suggest GemFile is in /opt/bitnami, but I don’t have one of those.
f) I don’t have a “/home/gitlab” or "/home/git’ but rather used the Omnibus install which created home directory in “var/opt/gitlab”.

Every troubleshoot guide suggest using some tool or something which is neither installed, configured or working… :smile:

SOOOOO… What to do? Can I just back everything up and repave the system and reinstall? I tried that before, but the reinstall / restore is what got me to this mess… Basically Omnibus 6.8.1 was working, and the upgrade to 7.8.4 failed. Then the restore from 7.8.4 to 6.8.1 whacked everything back out ---- but I didn’t lose any data, just the ability to create new repos.

You’re in a mess :smile:

You mention 3 kind of installations in your post:

  1. Manual (/home/git)
  2. Omnibus (/opt/gitlab)
  3. Bitnami (/opt/bitnami)

Once you figure out what is the one, follow only the documentation for that installation. Ditch the others.

Since you are using omnibus, the README and the docs should be the definitve places to seek help from.

In your case I would first install omnibus 6.8.1, restore from backup and work my way from there (again).

Well, I KNOW I installed Omnibus 6.8.1. It is just that troubleshooting guides that I can find via Google all talk about different installations, therefore none of my troubleshooting attempts work.

For instance a search on why I have a missing GemFile only refers to Bitnami installs. Searches of why my “bundle” doesn’t work only refer to Manual installs, you get the idea.

I guess I really want to know that if I got a good backup (which appeared to work), will my problems follow me? Of course, I would probably try the CE install on a fresh Ubuntu Server install.

Okay, new Ubuntu 14.04 server. Installed old omnibus 6.8.1. When I did the reconfigure got the following (and I don’t even have a user gitlab).

================================================================================
Error executing action `run` on resource 'execute[migrate database]'
================================================================================


Mixlib::ShellOut::ShellCommandFailed
------------------------------------
Expected process to exit with [0], but received '1'
---- Begin output of /opt/gitlab/bin/gitlab-rake db:migrate ----
STDOUT:
STDERR: WARNING: Nokogiri was built against LibXML version 2.8.0, but has dynamically loaded 2.7.8
rake aborted!
FATAL:  password authentication failed for user "gitlab"
FATAL:  password authentication failed for user "gitlab"

Tasks: TOP => db:migrate
(See full trace by running task with --trace)
---- End output of /opt/gitlab/bin/gitlab-rake db:migrate ----
Ran /opt/gitlab/bin/gitlab-rake db:migrate returned 1


Resource Declaration:
---------------------
# In /opt/gitlab/embedded/cookbooks/gitlab/recipes/database_migrations.rb

 26: execute "migrate database" do
 27:   command "/opt/gitlab/bin/gitlab-rake db:migrate"
 28: end



Compiled Resource:
------------------
# Declared in /opt/gitlab/embedded/cookbooks/gitlab/recipes/database_migrations.rb:26:in `from_file'

execute("migrate database") do
  action "run"
  retries 0
  retry_delay 2
  guard_interpreter :default
  command "/opt/gitlab/bin/gitlab-rake db:migrate"
  backup 5
  returns 0
  cookbook_name :gitlab
  recipe_name "database_migrations"
end



Recipe: gitlab::gitlab-shell
  * execute[bin/install] action run
    - execute bin/install


Running handlers:
[2015-05-25T15:34:50-04:00] ERROR: Running exception handlers
Running handlers complete

[2015-05-25T15:34:50-04:00] ERROR: Exception handlers complete
[2015-05-25T15:34:50-04:00] FATAL: Stacktrace dumped to /opt/gitlab/embedded/cookbooks/cache/chef-stacktrace.out
Chef Client failed. 108 resources updated in 119.700993547 seconds
[2015-05-25T15:34:50-04:00] ERROR: execute[migrate database] (gitlab::database_migrations line 26) had an error: Mixlib::ShellOut::ShellCommandFailed: Expected process to exit with [0], but received '1'
---- Begin output of /opt/gitlab/bin/gitlab-rake db:migrate ----
STDOUT:
STDERR: WARNING: Nokogiri was built against LibXML version 2.8.0, but has dynamically loaded 2.7.8
rake aborted!
FATAL:  password authentication failed for user "gitlab"
FATAL:  password authentication failed for user "gitlab"

Tasks: TOP => db:migrate
(See full trace by running task with --trace)
---- End output of /opt/gitlab/bin/gitlab-rake db:migrate ----
Ran /opt/gitlab/bin/gitlab-rake db:migrate returned 1
[2015-05-25T15:34:50-04:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1)

Okay, my bad… I mistakenly installed postgresql from the Ubuntu Server install. Seems like I finally have a fully functional 6.8.1. After I did a dpkg removal of postgresql, the upgrade worked. (not the first time, though, I copied my backup tar to a windows desktop to move between server instances. Got an unexpected EOF on the tar. Did it with sftp to make it all happy.

Probably going to leave it alone and skip the upgrade to 7.11… :smile:
At least this week.

axil - thanks for your responses, made me feel like I wasn’t totally alone.

–Ken

Glad you got it working :smiley: