Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Issues
  • #3519

Closed
Open
Created Apr 04, 2013 by Administrator@rootOwner

Upgrade issues.

Created by: hardikdangar

Hi guys,

I have tried to update my gitlab from 2.8 to 5.0 incrementally so first 2.6 to 3.0 then 3.0 to 3.1 ... 4.2 to 5.0 at all updates my gitlab app was working fine. i was able to push and pull code via accounts. but after updating to 5.0 there is major problem i can't add my gitlab public keys via gitlab. it gives me 500 error page. although other pages are working fine.

Now check status command returns following code

$ sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production

Rails Error: Unable to access log file. Please ensure that /home/gitlab/gitlab/log/production.log exists and is chmod 0666. The log level has been raised to WARN and the output directed to STDERR until the problem is fixed. Creating scope :public. Overwriting existing method Project.public.

Warning You are running as user git, we hope you know what you are doing. Things may work/fail for the wrong reasons. For correct results you should run this as user gitlab.

Checking Environment ...

gitlab user is in git group? ... yes Has no "-e" in ~git/.profile ... yes Git configured for gitlab user? ... no Try fixing it: sudo -u gitlab -H git config --global user.name "GitLab" sudo -u gitlab -H git config --global user.email "gitlab@localhost" For more information see: doc/install/installation.md in section "GitLab" Please fix the error above and rerun the checks. Has python2? ... yes python2 is supported version? ... yes

Checking Environment ... Finished

Checking Gitolite ...

Using recommended version ... no Try fixing it: We strongly recommend using the version pointed out in the installation guide. For more information see: doc/install/installation.md in section "Gitolite" Repo umask is 0007 in .gitolite.rc? ... yes Allow all Git config keys in .gitolite.rc ... yes Config directory exists? ... yes Config directory owned by git:git ... yes Config directory access is drwxr-x---? ... yes Repo base directory exists? ... yes Repo base directory is a symlink? ... no Repo base owned by git:git? ... yes Repo base access is drwxrws---? ... yes Can clone gitolite-admin? ... Warning: Permanently added 'localhost' (ECDSA) to the list of known hosts. git@localhost's password:

There's definitely something went wrong as its asking password at last and from v5.0 we need to use git user but gitlab status seems to asking for git user.

What's the best way to deal with this? is there something like i could do db backup and repository's backup and install v5.0 fresh and just migrate the data somehow cause i believe the long chain of upgrades could have failed somewhere....

Assignee
Assign to
Time tracking