Setup: Parallels VM (Version 9 on OS X 10.8.5). 8 GB Ram to the VM & 4 CPUs.
CentOS 6.5 with latest Updates. Static IP Address assigned to the VM with a 
host name of gitorious.bluequartz.net which resolves internally to 
192.168.1.119 through our internal DNS server (BIND9 running on another Linux 
VM instance).

went to getgitorious.com/install and followed the instructions. Added a user. 
Went to http://gitorious.bluequartz.net and the Gitorious instance shows up. 
Try to log in and the error message "Sorry, something went wrong" message when 
I try to log in - what's up?" pops up. If I click on the "contact us" link 
another page actually shows up and says that I logged in correctly. I can sit 
here and do this for things like adding my ssh keys and such. Is this a known 
bug in the production system? Does anyone have any ideas how to fix it? Or 
track it down? WHere are the logs at? /var/www/gitorious/app/logs? Which log to 
look at?  Looking at production.log I see this error:


ActionController::RoutingError (No route matches [GET] 
"/assets/issues/application.css"):
  
vendor/bundle/ruby/1.9.1/gems/actionpack-3.2.16/lib/action_dispatch/middleware/debug_exceptions.rb:21:in
 `call'
  
vendor/bundle/ruby/1.9.1/gems/actionpack-3.2.16/lib/action_dispatch/middleware/show_exceptions.rb:56:in
 `call'
  vendor/bundle/ruby/1.9.1/gems/railties-3.2.16/lib/rails/rack/logger.rb:32:in 
`call_app'
  vendor/bundle/ruby/1.9.1/gems/railties-3.2.16/lib/rails/rack/logger.rb:16:in 
`block in call'
  
vendor/bundle/ruby/1.9.1/gems/activesupport-3.2.16/lib/active_support/tagged_logging.rb:22:in
 `tagged'
  vendor/bundle/ruby/1.9.1/gems/railties-3.2.16/lib/rails/rack/logger.rb:16:in 
`call'
  
vendor/bundle/ruby/1.9.1/gems/actionpack-3.2.16/lib/action_dispatch/middleware/request_id.rb:22:in
 `call'
  vendor/bundle/ruby/1.9.1/gems/rack-1.4.5/lib/rack/methodoverride.rb:21:in 
`call'
  vendor/bundle/ruby/1.9.1/gems/rack-1.4.5/lib/rack/runtime.rb:17:in `call'
  
vendor/bundle/ruby/1.9.1/gems/activesupport-3.2.16/lib/active_support/cache/strategy/local_cache.rb:72:in
 `call'
  vendor/bundle/ruby/1.9.1/gems/rack-1.4.5/lib/rack/lock.rb:15:in `call'
  vendor/bundle/ruby/1.9.1/gems/railties-3.2.16/lib/rails/engine.rb:484:in 
`call'
  vendor/bundle/ruby/1.9.1/gems/railties-3.2.16/lib/rails/application.rb:231:in 
`call'
  
vendor/bundle/ruby/1.9.1/gems/railties-3.2.16/lib/rails/railtie/configurable.rb:30:in
 `method_missing'
  vendor/bundle/ruby/1.9.1/gems/rack-1.4.5/lib/rack/lint.rb:48:in `_call'
  vendor/bundle/ruby/1.9.1/gems/rack-1.4.5/lib/rack/lint.rb:36:in `call'
  vendor/bundle/ruby/1.9.1/gems/rack-1.4.5/lib/rack/showexceptions.rb:24:in 
`call'
  vendor/bundle/ruby/1.9.1/gems/rack-1.4.5/lib/rack/commonlogger.rb:33:in `call'
  vendor/bundle/ruby/1.9.1/gems/sinatra-1.4.4/lib/sinatra/base.rb:217:in `call'
  vendor/bundle/ruby/1.9.1/gems/rack-1.4.5/lib/rack/chunked.rb:43:in `call'
  vendor/bundle/ruby/1.9.1/gems/rack-1.4.5/lib/rack/content_length.rb:14:in 
`call'
  vendor/bundle/ruby/1.9.1/gems/unicorn-4.6.3/lib/unicorn/http_server.rb:552:in 
`process_client'
  vendor/bundle/ruby/1.9.1/gems/unicorn-4.6.3/lib/unicorn/http_server.rb:632:in 
`worker_loop'
  vendor/bundle/ruby/1.9.1/gems/unicorn-4.6.3/lib/unicorn/http_server.rb:500:in 
`spawn_missing_workers'
  vendor/bundle/ruby/1.9.1/gems/unicorn-4.6.3/lib/unicorn/http_server.rb:142:in 
`start'
  vendor/bundle/ruby/1.9.1/gems/unicorn-4.6.3/bin/unicorn:126:in `<top 
(required)>'
  vendor/bundle/ruby/1.9.1/bin/unicorn:23:in `load'
  vendor/bundle/ruby/1.9.1/bin/unicorn:23:in `<main>'


And in fact that file does not exist under the gitorious/app tree. Was there a 
different branch to clone from possibly?


Thanks for any help
Mike Jackson
BlueQuartz Software

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

--- 
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 [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to