I'm glad I was able to help. Gitorious does not index code of repositories unfortunately.
Cheers, Pawel On 10 April 2014 13:52, Roman N <datainfo...@gmail.com> wrote: > Great, it works now. Thank you! > > Also question about indexing. > I noticed that code content is not indexed, is it by design? github > indexes it for example. > > --Roman > > Paweł Pierzchała said the following, on 10-04-14, 5:06 AM: > > Who is the owner of files under /var/www/gitorious/app/db ? Please make > sure that they are owned by git: > > sudo chown git:git -R /var/www/gitorious/app/db > > If this doesn't help, please clear the sphinx indexes, rebuild them and > restart it: (bin/rake is a shortcut for 'RAILS_ENV=production bundle exec > rake' run as a git user) > > cd /var/www/gitorious/app > bin/rake ts:clear > bin/rake ts:rebuild > > Cheers, > Pawel > > On 10 April 2014 04:26, Roman N <datainfo...@gmail.com> wrote: > >> I've refreshed and re-run upgrade.sh once again, there were some changed >> after last time I checked. >> >> Run ts as git user, getting this: >> >> -bash-4.1$ cd /var/www/gitorious/app >> -bash-4.1$ RAILS_ENV=production bundle exec rake ts:start >> >> WARNING! No value set for exception_recipients in gitorious.yml. >> Will not be able to send email regarding unhandled exceptions >> Failed to start searchd daemon. Check >> /var/www/gitorious/app/log/production.searchd.log. >> Failed to start searchd. Check the log files for more information. >> >> Log: >> [Wed Apr 9 22:22:47.929 2014] [ 1618] WARNING: id32 index loaded by id64 >> binary; attributes converted >> [Wed Apr 9 22:22:47.929 2014] [ 1618] WARNING: index 'project_core': lock: >> failed to lock /var/www/gitorious/app/db/sphinx/production/project_core.spl: >> Resource temporarily unavailable; NOT SERVING >> [Wed Apr 9 22:22:47.929 2014] [ 1618] WARNING: id32 index loaded by id64 >> binary; attributes converted >> [Wed Apr 9 22:22:47.929 2014] [ 1618] WARNING: index 'repository_core': >> lock: failed to lock >> /var/www/gitorious/app/db/sphinx/production/repository_core.spl: Resource >> temporarily unavailable; NOT SERVING >> [Wed Apr 9 22:22:47.929 2014] [ 1618] FATAL: no valid indexes to serve >> [Wed Apr 9 22:22:47.929 2014] [ 1617] Child process 1618 has been finished, >> exit code 1. Watchdog finishes also. Good bye! >> >> -bash-4.1$ ls -al >> /var/www/gitorious/app/db/sphinx/production/repository_core.spl >> -rw------- 1 git git 0 Apr 9 22:23 >> /var/www/gitorious/app/db/sphinx/production/repository_core.spl >> >> Thanks, >> Roman >> >> Paweł Pierzchała said the following, on 09-04-14, 8:52 AM: >> >> Hi Roman, >> you need to run this command from the gitorious location: >> >> cd /var/www/gitorious/app >> RAILS_ENV=production bundle exec rake ts:start >> >> Cheers, >> Pawel >> >> On 9 April 2014 14:44, Roman N <datainfo...@gmail.com> wrote: >> >>> I run updated script few weeks ago, everything else seems to be fixed >>> except search. >>> >>> -bash-4.1$ bundle exec rake ts:start >>> Could not locate Gemfile >>> -bash-4.1$ export RAILS_ENV=production >>> -bash-4.1$ bundle exec rake ts:start >>> Could not locate Gemfile >>> >>> --Roman >>> >>> Paweł Pierzchała said the following, on 09-04-14, 8:40 AM: >>> >>> Hi Roman, >>> I've run into this error when my searchd daemon was down. Please make >>> sure you have this process running. Have you run the upgrade script? It >>> should start it automatically.You can try starting by hand with: >>> >>> bundle exec rake ts:start >>> >>> Cheers, >>> Pawel >>> >>> >>> On 31 March 2014 02:19, Roman Naumenko <roman.naume...@gmail.com> wrote: >>> >>>> On Friday, March 28, 2014 10:48:15 AM UTC-4, Paweł Pierzchała wrote: >>>> > Hi Brian and Roman, >>>> > Thank you Brain for spotting the missing pid directive, I've added it >>>> to the config/unicorn.rb template and I've updated the upgrade script to >>>> regenerate it and related monit task. >>>> > >>>> > The problems you have experienced were most likely caused by the old >>>> gitorious configuration. Please run the following command from application >>>> directory as a git user. Upgrade script now suggests that as well. >>>> > >>>> > bin/upgrade-gitorious3-config config/gitorious.yml >>>> config/gitorious.yml >>>> > >>>> > Roman, the upgrade script, now updates sphinx and regenerates the >>>> configs, please run it again, it should fix your problem. >>>> > >>>> > Finally, about the resque issue, I wasn't able to reproduce this one, >>>> please tell me if this still happens after the upgrade and resque-wroker >>>> restart. >>>> > >>>> > Cheers, >>>> > Pawel >>>> >>>> Thank you, Pawel. >>>> Startup script works fine. >>>> >>>> I also wanted to check why search is not working. Search for anything >>>> prints error "Gitorious encountered an server error. We are automatically >>>> notified of errors and will look into it." >>>> >>>> Related error in the /var/www/gitorious/app/log/production.log >>>> >>>> ThinkingSphinx::ConnectionError (Can't connect to MySQL server on >>>> '127.0.0.1' (111)): >>>> app/controllers/searches_controller.rb:38:in `block in show' >>>> lib/gitorious/authorized_filter.rb:35:in `call' >>>> lib/gitorious/authorized_filter.rb:35:in `block in filter_paginated' >>>> lib/gitorious/authorized_filter.rb:34:in `filter_paginated' >>>> app/controllers/searches_controller.rb:30:in `show' >>>> app/middlewares/dolt_cache_middleware.rb:24:in `call' >>>> app/middlewares/dolt_auth_middleware.rb:26:in `call' >>>> >>>> >>>> Checked pass in /var/www/gitorious/app/config/database.yml, seems >>>> correct since /etc/init.d/gitorious-unicorn starts app fine. >>>> >>>> -- >>>> -- >>>> To post to this group, send email to gitorious@googlegroups.com >>>> To unsubscribe from this group, send email to >>>> gitorious+unsubscr...@googlegroups.com >>>> >>>> --- >>>> You received this message because you are subscribed to the Google >>>> Groups "Gitorious" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to gitorious+unsubscr...@googlegroups.com. >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> -- >>> -- >>> To post to this group, send email to gitorious@googlegroups.com >>> To unsubscribe from this group, send email to >>> gitorious+unsubscr...@googlegroups.com >>> >>> --- >>> You received this message because you are subscribed to a topic in the >>> Google Groups "Gitorious" group. >>> To unsubscribe from this topic, visit >>> https://groups.google.com/d/topic/gitorious/WpDZpe1qSd8/unsubscribe. >>> To unsubscribe from this group and all its topics, send an email to >>> gitorious+unsubscr...@googlegroups.com. >>> >>> For more options, visit https://groups.google.com/d/optout. >>> >>> >>> -- >>> -- >>> To post to this group, send email to gitorious@googlegroups.com >>> To unsubscribe from this group, send email to >>> gitorious+unsubscr...@googlegroups.com >>> >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "Gitorious" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to gitorious+unsubscr...@googlegroups.com. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- >> -- >> To post to this group, send email to gitorious@googlegroups.com >> To unsubscribe from this group, send email to >> gitorious+unsubscr...@googlegroups.com >> >> --- >> You received this message because you are subscribed to a topic in the >> Google Groups "Gitorious" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/gitorious/WpDZpe1qSd8/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> gitorious+unsubscr...@googlegroups.com. >> For more options, visit https://groups.google.com/d/optout. >> >> >> -- >> -- >> To post to this group, send email to gitorious@googlegroups.com >> To unsubscribe from this group, send email to >> gitorious+unsubscr...@googlegroups.com >> >> --- >> You received this message because you are subscribed to the Google Groups >> "Gitorious" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to gitorious+unsubscr...@googlegroups.com. >> For more options, visit https://groups.google.com/d/optout. >> > > -- > -- > To post to this group, send email to gitorious@googlegroups.com > To unsubscribe from this group, send email to > gitorious+unsubscr...@googlegroups.com > > --- > You received this message because you are subscribed to a topic in the > Google Groups "Gitorious" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/gitorious/WpDZpe1qSd8/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > gitorious+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > > > -- > -- > To post to this group, send email to gitorious@googlegroups.com > To unsubscribe from this group, send email to > gitorious+unsubscr...@googlegroups.com > > --- > You received this message because you are subscribed to the Google Groups > "Gitorious" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to gitorious+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- -- To post to this group, send email to gitorious@googlegroups.com To unsubscribe from this group, send email to gitorious+unsubscr...@googlegroups.com --- You received this message because you are subscribed to the Google Groups "Gitorious" group. To unsubscribe from this group and stop receiving emails from it, send an email to gitorious+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
