1.2.6 to 2.0.1 500 internal server error

Rails
1

Trying to upgrade from 1.2.6 to 2.0.1 and I am getting a 500 internal
server error after server start up and I try to make any request or
even click on ‘about your applications environment’. Am I missing
something simple?

2

On Dec 14, 2007 4:01 PM, Larry E. [email protected]
wrote:

Trying to upgrade from 1.2.6 to 2.0.1 and I am getting a 500 internal
server error after server start up and I try to make any request or
even click on ‘about your applications environment’. Am I missing
something simple?

What do the logs say about the error?

–
Greg D.
http://destiney.com/

3

On Dec 14, 5:10 pm, “Greg D.” [email protected] wrote:

On Dec 14, 2007 4:01 PM, Larry E. [email protected] wrote:

Trying to upgrade from 1.2.6 to 2.0.1 and I am getting a 500 internal
server error after server start up and I try to make any request or
even click on ‘about your applications environment’. Am I missing
something simple?

I was getting this. I read on a site that you needed to delete
everything in your tmp/sessions folder. I didn’t have anything in
there. But stopping and restarting the server fixed it for me. I was
going back and forth between 1.2.6 and 2.0.1 and each time I started
2.0.1 I had to start and restart it twice.

Greg DeVore

4

Hi, you’ll also need to be aware of the error messages that are
generated in
the shell. I had to make the following changes from memory:

a) remove config.breakpoints line in the development.rb
b) add the line that mongrel spits out to the config section within
environment.rb
Note: This will happen when you try to make a request.
c) 1.2.6 to 2.0.1 inside the environment.rb
d) execute “rake rails:update” in the root directory of your rails
application.
e) start mongrel and you should be good to go

-Conrad

5

Hi,
I had the same issue from my Ubuntu7.10, since like we need to
configure somewhere before starting, I have no idea what to do as
well.

Br,
Xi

6

Hi, you’ll also need to be aware of the error messages that are generated in
the shell. I had to make the following changes from memory:

f) set config.action_controller.session in config/environment.rb and
make
sure secret is at least 30 chars long.

The easiest is to do:

rake log:clear
tail -f log/development

and hit your homepage. The log is pretty good about what you need to
change.