Redmine 500 Error when trying to create a new user
An error occurred on the page you were trying to access.
If you continue to experience problems please contact your Redmine administrator for assistance.
If you are the Redmine administrator, check your log files for details about the error.
In my apache access log:
::1 - - [09/Feb/2013:17:38:41 -0500] "GET /redmine/users/new HTTP/1.1" 500 674
No production.log file in the redmine-2.2 folder.
apache config settings, I'm running in a sub-uri, I created a link to the redmine-2.2/public folder called redmine.
# Passenger Modules # LoadModule passenger_module /usr/local/rvm/gems/ruby-1.9.3-p385/gems/passenger-3.0.19/ext/apache2/mod_passenger.so PassengerRoot /usr/local/rvm/gems/ruby-1.9.3-p385/gems/passenger-3.0.19 PassengerRuby /usr/local/rvm/wrappers/ruby-1.9.3-p385/ruby # <VirtualHost *:80> ServerName myserver # !!! Be sure to point DocumentRoot to 'public'! DocumentRoot /var/www/html <Directory /var/www/html> Allow from all </Directory> Errorlog /var/www/html/redmine/log/apache_error.log Customlog /var/www/html/redmine/log/apache_access.log common #PassengerAppRoot /var/www/redmine-2.2 #RailsBaseURI /redmine #Alias /redmine /var/www/redmine-2.2/public RailsBaseURI /redmine RailsEnv production <Directory /var/www/html/redmine> # This relaxes Apache security settings. AllowOverride all # MultiViews must be turned off. Options -MultiViews </Directory> </VirtualHost>
Added piece of information, I placed the following line of code to make sure that redmine knows about the sub-uri:
Redmine::Utils::relative_url_root = "/redmine"
ended up being a permissions issue for the apache user not owning the link and files within or the redmine-2.2 folder where I checked out the project from svn.
I upgraded the redmine from 102 to 223 on Ubuntu Lucid, but I have a very similar problem.
What do you mean that apache user not owning the link? How can I get a more detailed error message?
I had to chown -R apache:apache link to redmine-2.2 as well as the redmine-2.2 folder. Once I did that my issue went away. Once I did that then the production.log was written to the redmine-2.2 logs folder.
Thank you Scott! It helped me too!
you save me dude. tnx