Wierd... The issue seems to have fixed itself with the update to Gitlab-ce 8.9.6 via cron-daily.
On 12 July 2016 at 15:27, Arno Slatius <a.slat...@gmail.com> wrote: > I'm encountering an issue with my GitLab. It has been passively sitting > for ~1 month but I now suddenly run problems accessing my repositories. The > web interface tells me: > > *No repository* > The repository for this project does not exist. > This means you can not push code until you create an empty repository or > import existing one. > > My situation; > I run CentOS 7 with gitlab-ce installation from the yum repository, > currently running Gitlab 8.9.5. Repositories are mounted via NFS. > First thing I did was run yum update which gave me Gitlab-ce 8.9.5, the > previous version was 8.7.0. > > Running gitlab-rake gitlab:check gives me: > > Checking GitLab Shell ... > > GitLab Shell version >= 3.0.0 ? ... OK (3.0.0) > 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 > hooks directories in repos are links: ... > Arno Slatius / TestProject1 ... repository is empty > Arno Slatius / pfsense-captive-portal ... repository is empty > [... stripped a few...] > Running /opt/gitlab/embedded/service/gitlab-shell/bin/check > Check GitLab API access: OK > Check directories and files: > /var/opt/gitlab/git-data/repositories: OK > /var/opt/gitlab/.ssh/authorized_keys: OK > Send ping to redis server: gitlab-shell self-check successful > > Checking GitLab Shell ... Finished > > Checking Sidekiq ... > > Running? ... yes > Number of Sidekiq processes ... 1 > > Checking Sidekiq ... Finished > > Checking Reply by email ... > > Reply by email is disabled in config/gitlab.yml > > Checking Reply by email ... Finished > > Checking LDAP ... > > LDAP is disabled in config/gitlab.yml > > Checking LDAP ... Finished > > Checking GitLab ... > > Git configured with autocrlf=input? ... yes > Database config exists? ... yes > All migrations up? ... yes > Database contains orphaned GroupMembers? ... no > GitLab config exists? ... yes > GitLab config outdated? ... no > Log directory writable? ... yes > Tmp directory writable? ... yes > Uploads directory setup correctly? ... yes > Init script exists? ... skipped (omnibus-gitlab has no init script) > Init script up-to-date? ... skipped (omnibus-gitlab has no init script) > projects have namespace: ... > Arno Slatius / TestProject1 ... yes > Arno Slatius / pfsense-captive-portal ... yes > [... stripped a few...] > Redis version >= 2.8.0? ... yes > Ruby version >= 2.1.0 ? ... yes (2.1.8) > Your git bin path is "/opt/gitlab/embedded/bin/git" > Git version >= 2.7.3 ? ... yes (2.7.4) > Active users: 6 > > Checking GitLab ... Finished > > The repositories are said to be empty. > However if I su- git, cd ~, > cd /var/opt/gitlab/git-data/repositories/[insert any repo].git and run git > log it'll show me the correct last commit messages in the repository. > > Does anyone have suggestions on how to determine why Gitlab doesn't see > the repository and/or how to fix? > > -- > You received this message because you are subscribed to a topic in the > Google Groups "GitLab" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/gitlabhq/f-9pRjf6XkM/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > gitlabhq+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/gitlabhq/9320acfb-d141-434a-9d1a-a933f7932ebd%40googlegroups.com > <https://groups.google.com/d/msgid/gitlabhq/9320acfb-d141-434a-9d1a-a933f7932ebd%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/CAH8Uf3rB0TP4%3DOqVKAPavh_5B_p30nC2vhW%2BJ2dz-PJAvnKASw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
