I recently upgraded my gitlab from ~7.4 to 7.9. Now, some jobs that get passed to sidekiq seem to never run.
More specifically, I have a new user trying to add an SSH key. The interface reports that it's been added successfully but the key does not get added to the ~/.ssh/authorized_keys file. While debugging this, I found a file named ~/.ssh/authorized_keys.lock. Assuming this was the issue, I deleted the file. I've since restarted gitlab and sidekiq but this did not fix anything. Looking at the Admin area under "Background Jobs", I see many (~7) "Enqueued" jobs. There are 3 queues on this tab and under "gitlab_shell" I see the key I was trying to add: GitlabShellWorker ["add_key", "key-57", "ssh-rsa AAAAB3Nz... There are other failed jobs as well. I recently deleted a project and have these two "Enqueued" jobs still: GitlabShellWorker ["remove_repository", "GROUP/PROJ.wiki"] > GitlabShellWorker ["remove_repository", "GROUP/PROJ"] And the matching folders in my "repositories" folder are still there. Is there a way to force these jobs to run? Is there some other lock file that I haven't found? Other jobs are running as I see over 100 jobs that have been run today in the sidekiq dashboard. Email is also not getting sent, but I know the reason for this: Exim needs one small config change that I haven't done yet. I just wanted to mention this in case others thought this is causing the issues I'm seeing. (I see some email jobs are still enqueued as well) Thanks in advance! Cheers, - Cameron -- 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/9550a63c-ed0f-4d9d-bb41-1d8e59111512%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
