Hello, On our not-so-small GitLab instance (2k projects; 1k8 users), we encounter a "lock" issue since few days. GitLab version: 7.9.4 b10de29, omnibus package
When we open a Merge Request by example, GitLab try to put a "lock" on the corresponding satellite; but GitLab fails to acquire this lock and we have the following error in production.log : *Errno::ENOLCK (No locks available @ rb_file_flock - /DATA/scm/gitlab-satellites*/tmp/satellite_1327.lock): lib/gitlab/satellite/satellite.rb:59:in `flock' lib/gitlab/satellite/satellite.rb:59:in `block in lock' lib/gitlab/satellite/satellite.rb:57:in `open' lib/gitlab/satellite/satellite.rb:57:in `lock' lib/gitlab/satellite/action.rb:23:in `block in in_locked_and_timed_satellite' lib/gitlab/satellite/action.rb:22:in `in_locked_and_timed_satellite' lib/gitlab/satellite/compare_action.rb:15:in `result' app/services/compare_service.rb:24:in `execute' app/services/merge_requests/build_service.rb:19:in `execute' app/controllers/projects/merge_requests_controller.rb:64:in `new' The same issue appends when someone add a new SSH Key in his profile. The key is well added in the GUI and GitLab DB, but when GitLab wants to write this key in /var/opt/gitlab/.ssh/authorized_keys, it first try to put a "lock" on this file but fail (with the same error as above). The "authorized_keys.lock" file is well created, but GitLab fails to write the newly created SSH key. Note that both our satellites and the directory "/var/opt/gitlab/.ssh" are stored in a NFS drive. Have you ever encountered this "Errno::ENOLCK" error ? If so, do you have any tracks for us ? Regards, Pierre -- 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/95defe06-ff4a-42f6-a183-c5c2d48cc426%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
