-
Notifications
You must be signed in to change notification settings - Fork 117
not able to create initial repository #237
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hi! Thanks for your feedback!
Nothing :) Which version of I think the bug comes from here. More details here. Can you test with the By the way, you can keep using Gitolite 3 ;) |
Hi, Thanks a lot! I installed the new version and It works now - also with gitolitev3! :) Sadly there is another weird issue now: I start redis-server and then execute When a request is "lost" I can see it now in the sidekiq "enqueued" queue. But it just stays there and is never executed? Next i tried using you script contrib/service_sidekiq.sh
Not sure what I am doing wrong here :( |
This is not normal... Do you have logs?
What do you mean? Do you mean when you push code in a repo or when you create a repo? In both case this is not normal too. Can you enable hook debug? (in Administration -> Redmine Git Hosting -> Hooks) and retry to push code?
To be more precise, actually it does not cache the request but put every request in Redis in a FIFO style so the worker can execute them later one by one. |
Can you please try with this new version of the script : https://github.com/jbox-web/redmine_git_hosting/blob/devel/contrib/scripts/service_sidekiq.sh ? |
The link https://github.com/jbox-web/redmine_git_hosting/blob/devel/contrib/scripts/service_sidekiq.sh does not work for me :( It behaves now really weird. I disabled sidekiq. I activated the debug hooks. I restarted apache. git_hosting.log:
Anyways now I can not clone any repository anymore (DENIED by fallthru) :( git_hosting.log
gitolite.log:
Via SmartHTTP I can clone the repo though (git_hosting.log):
Any ideas what's causing this? |
by reinstalling gitolite i always mean following all the steps in the step-by-step ('.*', repo @ALL ..., etc) setup and deleting /tmp/redmine_git_hosting |
The script starts now without error. Problem is that no repository is created now, instead the task is enqueued in Sidekiq: GithostingShellWorker All git_hosting.log says now is: 2014-07-17 23:27:40 +0200 INFO [GitHosting] User 'peter' created a new repository 'redmine/test' I checked and the repository is not existant in gitolite. |
If the worker is running it should do something... even a crash... and you should have output in logs. Be sure that the worker is really running with a Can you also check the worker's log in |
You are right. There is no worker running. Redis-Server is started with standard conf in daemonized mode. ps ax shows that server is running and a pid file exists at /var/run/redis/redis-server.pid I execute service_sidekiq.sh start worker.log
directory /usr/local/redmine/redmine/tmp is set to 776 (but I also tried 777), so the write permissions to this directory should not be an issue |
You must create the |
nah ok. sry that was very stupid of me.... but thanks a lot for helping out! Sidekiq is working now. The worker is processing the requests perfectly. Now I still have the problem with the repo cloning. I enter my public key and everything seems to work fine: git_hosting.log
key is in gitolite authorized_keys:
Still when trying to clone i get: gitolite.log
The repository redmine/xaxa.git exits in gitolite. It is also declared in gitolite.conf. |
Can you please post your |
in git user $HOME/.gitolite/conf/gitolite.conf
|
You must add members to your project. These members must have permissions to create ssh keys, commit and maybe view changesets. This is done in Administration -> Roles. |
-,- so sorry. I reinstalled, readded and deleted so many times that at some point I completely skipped adding myself to the project... With Sidekiq running now it seems to work perfectly. I am still not sure why before I sometimes got an error message when pushing (remote: Notifying Redmine about changes...), but since everything works now, it was most likely another stupid mistake of mine somewhere. In case the error occurs again, I will write. Thanks a lot for the awesome support!!! :) |
You're welcome :) |
By the way, I've updated the worker startup script : https://github.com/jbox-web/redmine_git_hosting/blob/devel/contrib/scripts/sidekiq_git_hosting.sh It avoids creation of duplicated processus. For example, with the previous version, if you do :
you've got 2 running workers plugged to the same queue : I don't think this is good :/ With the new version the script fires up Sidekiq and wait until it's started. On my server it takes between 10 and 15 seconds for Sidekiq to be fully loaded. So there is a default timeout of 15 seconds. You can override it by passing the timeout as an environment variable to the script :
You can also start the worker in development mode by passing another environment variable :
This will let the worker hang on the console instead of forking with the log redirected to the stdout. Happy testing! |
Hi,
I installed redmine_git_hosting plugin v0.7.3 following https://github.com/jbox-web/redmine_git_hosting/wiki/Step-by-step-installation-instructions and the Plugin's 'Config Test' shows that everything (should) work fine.
I also set GIT_CONFIG_KEYS => '.*',
I disabled Sidekiq.
I activated initial repository creation with README.
When I create a new project, git_hosting.log says that a new project was created. But when I check in gitolite v3, no project is there.
I read in previous issues, that it helped to remove /tmp/redmine_git_hosting and to reinstall gitolite, but after doing so I still got the same error. Further I tried using gitolitev2, but that also returned the same error. I also tried redmine_git_hosting dev version 0.7.5 -> same problem.
To me it seems, that the hooks are not properly set (though the admin panel 'Config Test' claims, that everything is fine).
git_hosting.log
gitolitev2 log (gitolitev3 looks similiar...):
Any idea what I am doing wrong?
Reinold
The text was updated successfully, but these errors were encountered: