uploaded ssh key is not copied to correct place with debian package

I can see the new key in the web interface but not present in /usr/share/gitlab/.ssh/authorized_keys (/usr/share/gitlab is home of gitlab user)

Added ~152823 label

Is there a permission issue where GitLab can't write to that file?

@stanhu gitlab user has rw permission.

$ sudo -u gitlab ls -lad /usr/share/gitlab/.ssh
drwx------ 2 gitlab gitlab 4096 Feb  7 05:35 /usr/share/gitlab/.ssh
$ sudo -u gitlab ls -l /usr/share/gitlab/.ssh
total 4
-rw------- 1 gitlab gitlab  0 Feb  7 05:35 authorized_keys
-rw-r--r-- 1 gitlab gitlab 86 Feb  7 05:35 environment

I can give access to my test environment if you want to have a look.

@stanhu we got to fix #13245 (closed) before we can grab more details on this bug.

praveen@pod:/usr/share/gitlab$ RAILS_ENV=production DB=postgres sudo -E -u gitlab bundle e
xec rake gitlab:check
fatal: Not a git repository (or any of the parent directories): .git
Checking GitLab Shell ...

GitLab Shell version >= 2.6.10 ? ... OK (2.6.10)
Repo base directory exists? ... yes
Repo base directory is a symlink? ... no
Repo base owned by gitlab:gitlab? ... yes
Repo base access is drwxrws---? ... yes
hooks directories in repos are links: ...
Administrator / test ... repository is empty
Administrator / new ... repository is empty
Administrator / newtest ... repository is empty
Running /usr/share/gitlab-shell/bin/check
Check GitLab API access: OK
Check directories and files:   
        /var/lib/gitlab/repositories/: OK
        /usr/share/gitlab/.ssh/authorized_keys: OK
Test redis-cli executable: redis-cli 3.0.7
Send ping to redis server: PONG
gitlab-shell self-check successful

Checking GitLab Shell ... Finished

Checking Sidekiq ...

Running? ... no
  Try fixing it:
  sudo -u gitlab -H RAILS_ENV=production bin/background_jobs start
  For more information see:
  doc/install/installation.md in section "Install Init Script"
  see log/sidekiq.log for possible errors
  Please fix the error above and rerun the checks.

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? ... Trying to fix Git error automatically. ...Failed
  Try fixing it:
  sudo -u gitlab -H "/usr/bin/git" config --global core.autocrlf "input"
  For more information see:
  doc/install/installation.md in section "GitLab"
Database config exists? ... yes
Database is SQLite ... no
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? ... skipped (no tmp uploads folder yet)
Init script exists? ... yes
Init script up-to-date? ... yes
projects have namespace: ...   
Administrator / test ... yes
Administrator / new ... yes
Administrator / newtest ... yes
Redis version >= 2.8.0? ... yes
Ruby version >= 2.1.0 ? ... yes (2.2.4)
Your git bin path is "/usr/bin/git"
Git version >= 1.7.10 ? ... yes (2.1.4)
Active users: 1

Checking GitLab ... Finished

Let me check sidekiq status, may be because of that.

yes, sidekiq was not running, will dig deeper to find the root cause.

$ sudo /etc/init.d/gitlab status
The GitLab Unicorn web server with pid 30927 is running.
The GitLab Sidekiq job dispatcher is not running.

I can see the new key in the web interface but not present in /usr/share/gitlab/.ssh/authorized_keys (/usr/share/gitlab is home of gitlab user)

If Sidekiq is not running the key will never make it from GitLab's SQL DB to authorized_keys.

Its working on a clean install now. The only possibility I can think of is another sidekiq running for diaspora that might have cause sidekiq to die.

Status changed to closed

uploaded ssh key is not copied to correct place with debian package

Designs

Child items ...

Activity