i've found the reason of my case:
crontab job was created for root user, not git. So, I change to git, it's 
fine.

Also I need to check and change owner to git for file/dir in gitorious dir 
(repositories dir was own by root, this is serious issue)

On Friday, August 17, 2012 2:43:09 PM UTC+7, Phuong Doan wrote:
>
> On Tuesday, March 6, 2012 5:49:25 AM UTC+7, v2k wrote: 
> > I followed this guide 
> > 
> > 
> > 
> > Thanks for the guide. I’ve got this setup and running on 11.10 
> > 
> > 
> > I had to do this to get it running:  
> > 
> > 
> > vi /var/www/gitorious/config/ultrasphinx/production.conf # replace 
> base_tags with tags 
> > bundle exec rake ultrasphinx:index RAILS_ENV=production 
> > 
> > 
> > 
> > It’s working now, but when I create repositories, it doesn’t work. It 
> sits on “This repository is being created” forever and doesn’t do anything. 
> > 
> > 
> > I then have to run “script/poller run” manually. I then get spammed 
> with:  
> > 
> > 
> > NOTE: Gem::SourceIndex#add_spec is deprecated, use 
> Specification.add_spec. It will be removed on or after 2011-11-01.  
> > Gem::SourceIndex#add_spec called from 
> /usr/local/lib/site_ruby/1.8/rubygems/source_index.rb:127. 
> > 
> > 
> > The webpage then updates with: Sorry, something went wrong 
> > 
> > 
> > Gitorious encountered an server error. We are automatically notified of 
> errors and will look into it. If the error persists beyond what’s 
> reasonable, let us know. 
> > 
> > 
> > Files do get created in /var/www/gitorious/repositories; however, if I 
> try to view a repository via gitorious, I get the same “something went 
> wrong” error. 
> > 
> > 
> > How do I actually find out what it’s failing on? Why do I have to run 
> the poller manually? 
> > 
> > 
> > My crontab is: 
> > 
> > 
> > * * * * * cd /var/www/gitorious && /usr/bin/bundle exec rake 
> ultrasphinx:index RAILS_ENV=production 
> > 
> > 
> > Thanks. 
>
> exactly the same problem here :-(

-- 
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]

Reply via email to