Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am adding new projects to Redmine after transitioning it to a new server. The projects appear to add correctly. I can also add new CRs and DRs. However, after they are added, I can't actually browse to them. For example:

Gives me an Internal error. Same with the Calendar, Gantt charts and backlog. The issues are apparently added, though, because I can see a list of all issues by going to:

What is interesting is that I can still select the old issues and they work. The issues added to new projects do not work.

When I check my logs (both Apache and Redmine logs) there is no apparent problems being reported. I'm really not sure where to go next from here. Any suggestions?

Update for Apache Configuration

It looks like this:

LoadModule passenger_module /usr/local/lib/ruby/gems/1.8/gems/passenger-3.0.9/ext/apache2/
PassengerRoot /usr/local/lib/ruby/gems/1.8/gems/passenger-3.0.9
PassengerRuby /usr/local/bin/ruby

<VirtualHost *:80>
  DocumentRoot "/opt/redmine/latest/public"
  LogFormat "%h %l %u %t \"%r\" %>s %b" common
  LogLevel WARN
  ErrorLog "/var/log/httpd/redmine-error.log"
  CustomLog "/var/log/httpd/redmine-access.log" common

  <Directory /opt/redmine/latest/public>
    Options Indexes ExecCGI FollowSymlinks -MultiViews
    Order allow,deny
    Allow from all
    AllowOverride all

  <Location />
    Include conf.d/
    Require ldap-attribute objectclass=person
share|improve this question
What does Apache configuration for look like? – quanta Oct 11 '11 at 2:23
@quanta - Updated to answer your question. – JasCav Oct 11 '11 at 2:35
Are you sure redmine-error.log has nothing relate to 500 error? – quanta Oct 11 '11 at 2:40
@quanta - Yeah. It's 0 bytes. Absolutely nothing in it. The only thing I have is in my Apache error log, I have: /opt/redmine/1.1.3/vendor/rails/railties/lib/rails/gem_dependency.rb:119:Warning‌​: Gem::Dependency#version_requirements is deprecated and will be removed on or after August 2010. Use #requirement – JasCav Oct 11 '11 at 2:48
Turn LogLevel to debug, comment out ErrorLog in virtual host as a temporary to see if there is something in main Apache error log. – quanta Oct 11 '11 at 2:52

Have you tried doing this ?

rake db:migrate RAILS_ENV=production
share|improve this answer
up vote 0 down vote accepted

Turns out there was an installation issue and backlogs was not working. If I disable the backlogs module in the projects, everything works. I'll look into the deeper issue later, but the immediate need was met.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.