Upgrade fails on ce appliance

[R N]

Hi,

I run upgrade script in ce appliance, it fails. Had to fix /var/www/gitorious/app/config/gitorious.yml, it complaint about depreciated options.

What is it complaining about now?

sudo ./upgrade.sh

Using will_paginate (3.0.5)
Your bundle is complete!
Gems in the groups development, test and postgres were not installed.
It was installed into ./vendor/bundle
Failed loading some test dependencies: cannot load such file -- ci/reporter/rake/minitest
/opt/rubies/ruby-1.9.3-p484/bin/ruby /var/www/gitorious/app/vendor/bundle/ruby/1.9.1/bin/rake assets:precompile:all RAILS_ENV=production RAILS_GROUPS=assets
Failed loading some test dependencies: cannot load such file -- ci/reporter/rake/minitest
Failed loading some test dependencies: cannot load such file -- ci/reporter/rake/minitest
Failed loading some test dependencies: cannot load such file -- ci/reporter/rake/minitest
rake aborted!
undefined method `new' for ExceptionNotifier:Module
/var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/actionpack-3.2.16/lib/action_dispatch/middleware/stack.rb:43:in `build'
/var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/actionpack-3.2.16/lib/action_dispatch/middleware/stack.rb:113:in `block in build'
/var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/actionpack-3.2.16/lib/action_dispatch/middleware/stack.rb:113:in `each'
/var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/actionpack-3.2.16/lib/action_dispatch/middleware/stack.rb:113:in `inject'
/var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/actionpack-3.2.16/lib/action_dispatch/middleware/stack.rb:113:in `build'
/var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/railties-3.2.16/lib/rails/engine.rb:475:in `app'
/var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/railties-3.2.16/lib/rails/application/finisher.rb:31:in `block in <module:Finisher>'
/var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/railties-3.2.16/lib/rails/initializable.rb:30:in `instance_exec'
/var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/railties-3.2.16/lib/rails/initializable.rb:30:in `run'
/var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/railties-3.2.16/lib/rails/initializable.rb:55:in `block in run_initializers'
/var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/railties-3.2.16/lib/rails/initializable.rb:54:in `each'
/var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/railties-3.2.16/lib/rails/initializable.rb:54:in `run_initializers'
/var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/railties-3.2.16/lib/rails/application.rb:136:in `initialize!'
/var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/railties-3.2.16/lib/rails/railtie/configurable.rb:30:in `method_missing'
/var/www/gitorious/app/config/environment.rb:5:in `<top (required)>'
/var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/activesupport-3.2.16/lib/active_support/dependencies.rb:251:in `require'
/var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/activesupport-3.2.16/lib/active_support/dependencies.rb:251:in `block in require'
/var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/activesupport-3.2.16/lib/active_support/dependencies.rb:236:in `load_dependency'
/var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/activesupport-3.2.16/lib/active_support/dependencies.rb:251:in `require'
/var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/railties-3.2.16/lib/rails/application.rb:103:in `require_environment!'
/var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/railties-3.2.16/lib/rails/application.rb:305:in `block (2 levels) in initialize_tasks'
Tasks: TOP => db:migrate => environment
(See full trace by running task with --trace)
Failed loading some test dependencies: cannot load such file -- ci/reporter/rake/minitest
rake aborted!
undefined method `new' for ExceptionNotifier:Module
/var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/actionpack-3.2.16/lib/action_dispatch/middleware/stack.rb:43:in `build'
/var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/actionpack-3.2.16/lib/action_dispatch/middleware/stack.rb:113:in `block in build'
/var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/actionpack-3.2.16/lib/action_dispatch/middleware/stack.rb:113:in `each'
/var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/actionpack-3.2.16/lib/action_dispatch/middleware/stack.rb:113:in `inject'
/var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/actionpack-3.2.16/lib/action_dispatch/middleware/stack.rb:113:in `build'
/var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/railties-3.2.16/lib/rails/engine.rb:475:in `app'
/var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/railties-3.2.16/lib/rails/application/finisher.rb:31:in `block in <module:Finisher>'
/var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/railties-3.2.16/lib/rails/initializable.rb:30:in `instance_exec'
/var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/railties-3.2.16/lib/rails/initializable.rb:30:in `run'
/var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/railties-3.2.16/lib/rails/initializable.rb:55:in `block in run_initializers'
/var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/railties-3.2.16/lib/rails/initializable.rb:54:in `each'
/var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/railties-3.2.16/lib/rails/initializable.rb:54:in `run_initializers'
/var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/railties-3.2.16/lib/rails/application.rb:136:in `initialize!'
/var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/railties-3.2.16/lib/rails/railtie/configurable.rb:30:in `method_missing'
/var/www/gitorious/app/config/environment.rb:5:in `<top (required)>'
/var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/activesupport-3.2.16/lib/active_support/dependencies.rb:251:in `require'
/var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/activesupport-3.2.16/lib/active_support/dependencies.rb:251:in `block in require'
/var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/activesupport-3.2.16/lib/active_support/dependencies.rb:236:in `load_dependency'
/var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/activesupport-3.2.16/lib/active_support/dependencies.rb:251:in `require'
/var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/railties-3.2.16/lib/rails/application.rb:103:in `require_environment!'
/var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/railties-3.2.16/lib/rails/application.rb:305:in `block (2 levels) in initialize_tasks'
Tasks: TOP => fix_dangling_comments => environment
(See full trace by running task with --trace)
/etc/init.d/gitorious-unicorn: line 26: kill: (27860) - No such process
Stopping [FAILED]
master failed to start, check stderr log for details
Starting unicorn [FAILED]
resque-worker start/running, process 32747
Starting nginx: [ OK ]

Please fix the following warnings in your config/gitorious.yml:

/var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/actionpack-3.2.16/lib/action_dispatch/middleware/stack.rb:43:in `build': undefined method `new' for ExceptionNotifier:Module (NoMethodError)
from /var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/actionpack-3.2.16/lib/action_dispatch/middleware/stack.rb:113:in `block in build'
from /var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/actionpack-3.2.16/lib/action_dispatch/middleware/stack.rb:113:in `each'
from /var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/actionpack-3.2.16/lib/action_dispatch/middleware/stack.rb:113:in `inject'
from /var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/actionpack-3.2.16/lib/action_dispatch/middleware/stack.rb:113:in `build'
from /var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/railties-3.2.16/lib/rails/engine.rb:475:in `app'
from /var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/railties-3.2.16/lib/rails/application/finisher.rb:31:in `block in <module:Finisher>'
from /var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/railties-3.2.16/lib/rails/initializable.rb:30:in `instance_exec'
from /var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/railties-3.2.16/lib/rails/initializable.rb:30:in `run'
from /var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/railties-3.2.16/lib/rails/initializable.rb:55:in `block in run_initializers'
from /var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/railties-3.2.16/lib/rails/initializable.rb:54:in `each'
from /var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/railties-3.2.16/lib/rails/initializable.rb:54:in `run_initializers'
from /var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/railties-3.2.16/lib/rails/application.rb:136:in `initialize!'
from /var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/railties-3.2.16/lib/rails/railtie/configurable.rb:30:in `method_missing'
from /var/www/gitorious/app/config/environment.rb:5:in `<top (required)>'
from /var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/activesupport-3.2.16/lib/active_support/dependencies.rb:251:in `require'
from /var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/activesupport-3.2.16/lib/active_support/dependencies.rb:251:in `block in require'
from /var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/activesupport-3.2.16/lib/active_support/dependencies.rb:236:in `load_dependency'
from /var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/activesupport-3.2.16/lib/active_support/dependencies.rb:251:in `require'
from /var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/railties-3.2.16/lib/rails/application.rb:103:in `require_environment!'
from /var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/railties-3.2.16/lib/rails/commands/runner.rb:44:in `<top (required)>'
from /var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/railties-3.2.16/lib/rails/commands.rb:64:in `require'
from /var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/railties-3.2.16/lib/rails/commands.rb:64:in `<top (required)>'
from script/rails:6:in `require'
from script/rails:6:in `<main>'
-

[Paweł Pierzchała]

Hi,

I've updated the ce-installer code to install a newer version of gitorious. Please update it and then run the upgrade again:

git fetch

git checkout origin/master

sudo ./upgrade

The bug you have faced was related to exception_recipients, but it is already fixed.

Cheers,

Pawel

--
--
To post to this group, send email to gito...@googlegroups.com
To unsubscribe from this group, send email to
gitorious+...@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+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[R N]

On Thursday, March 13, 2014 8:27:30 AM UTC-4, Paweł Pierzchała wrote:
> Hi,
> I've updated the ce-installer code to install a newer version of gitorious. Please update it and then run the upgrade again:
> git fetch
> git checkout origin/master
> sudo ./upgrade
>
> The bug you have faced was related to exception_recipients, but it is already fixed.
>
> Cheers,
> Pawel

Thank you, it let the upgrade script to finish without errors (few warnings about config)

However, unicorn fails at the start.
It starts only under user 'git', but then fails for other options.

[root@gitorious ~]# /etc/init.d/gitorious-unicorn start
Error: Set user in gitorious.yml or run this script as non-root user
Starting unicorn [FAILED]
[root@gitorious ~]# su - git
-bash-4.1$ /etc/init.d/gitorious-unicorn start
Starting unicorn [ OK ]
-bash-4.1$ /etc/init.d/gitorious-unicorn status
Unicorn status [FAILED]

/var/www/gitorious/app/config/gitorious.yml has user git

# User which is running git daemon
user: git

[Brian Glover]

I have the same issue. I was able to fix the status issue by adding the following to my config/unicorn.rb (after the listen directive): pid "/var/www/gitorious/app/tmp/pids/unicorn.pid"

Also, after the upgrade we're no longer receiving emails when comments are made, only push emails. It appears resque isn't running and fails to start.

[Roman Naumenko]

On Tuesday, March 18, 2014 6:41:44 PM UTC-4, Brian Glover wrote:
> I have the same issue. I was able to fix the status issue by adding the following to my config/unicorn.rb (after the listen directive): pid "/var/www/gitorious/app/tmp/pids/unicorn.pid"

Thanks, fixed.

> Also, after the upgrade we're no longer receiving emails when comments are made, only push emails. It appears resque isn't running and fails to start.

resque neeeds resque operation...
Not sure though if mine works, I'm not using this functionality yet.

--Roman

[Brian Glover]

This is the error I'm getting in regards to resque:

Starting worker code.xxxx.com:24242:*
Failed to start worker : #<NameError: uninitialized constant Processor>

[Roman Naumenko]

On Tuesday, March 18, 2014 7:43:03 PM UTC-4, Brian Glover wrote:
> On Tuesday, March 18, 2014 6:02:13 PM UTC-5, Roman Naumenko wrote:
> > On Tuesday, March 18, 2014 6:41:44 PM UTC-4, Brian Glover wrote:
> > > I have the same issue. I was able to fix the status issue by adding the following to my config/unicorn.rb (after the listen directive): pid "/var/www/gitorious/app/tmp/pids/unicorn.pid"
> >
> > Thanks, fixed.
> >

> This is the error I'm getting in regards to resque:
>
> Starting worker code.xxxx.com:24242:*
> Failed to start worker : #<NameError: uninitialized constant Processor>

Hey Brian,

Is the search working? Broken for me, prints for every search request
"Sorry, something went wrong Gitorious encountered an server error."

Also it doesn't display changes in some commits, relatively big (50 or so files). Although I don't have enough statistic to confirm if its because of the size or files number.

[Paweł Pierzchała]

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

[Roman Naumenko]

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.

[Paweł Pierzchała]

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

[Roman N]

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:

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+...@googlegroups.com.

[Paweł Pierzchała]

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

[Roman N]

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:

[Paweł Pierzchała]

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

[Roman N]

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:

[Paweł Pierzchała]

I'm glad I was able to help. Gitorious does not index code of repositories unfortunately.

Cheers,

Pawel

[Roman N]

Hi,

I have an issue with the links not working in "Commits" tab. If I open a commit, there is a list of files in "Summary" section, if I click on any of the links there - nothing happens.

app/design/frontend/base/default/layout/local.xml (18) ------------------

However, links futher below on the Commit tab are working ok

Here is the links:
broken: https://gitorious/ecomm_site/magento/commit/9cc48c01812f85ce32107779aa09fc1939b9aa2c#app/design/frontend/base/default/layout/local.xml_
works: https://gitorious/ecomm_site/magento/source/9cc48c01812f85ce32107779aa09fc1939b9aa2c:app/design/frontend/base/default/layout/local.xml

I just checked gitorious.org, it works the same way - links in the Summary don't go anywhere. Is there is a purpose files in a commit are shows as links? Here for example, https://qt.gitorious.org/qt/qt3d/commit/09c30e27ab6fee07346f23ac0814a940fb3e727a#src/render/backend/renderview.h

--Roman

[Paweł Pierzchała]

Hi Roman,

thanks for the report, I fixed that in the mainline, it will be released with version v3.0.3

Cheers,

Pawel

--