I found the cause of the problem. The process of creating/updating the ssh keys in the gitolite.conf file, authorized_keys, etc. was timing out. Increasing the timeout from 20s to 200s in the gitolite.rb file allowed us to work around the problem.
On Monday, April 28, 2014 12:03:39 PM UTC-7, Susan Makay wrote: > > We migrated our entire gitlab setup (gitlab 2.4, gitolite 2.2-11) to a VM > (VMWare ESX) and everything works ok EXCEPT we can no longer add or remove > ssh keys. We get the infamous "Application cant get access to your > gitolite system" and leftover /tmp/ gitlabhq-gitolite* directories. The ssh > keys do appear to be modified in the .gitolite/keydir. Removing the > /tmp/gitlabhq* files doesn't help - they just get recreated. Any ideas on > how to fix this? > > -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
