Frustration with dapper -> feisty

Rails Deployment
1

I updated my server from dapper drake to feisty fawn this weekend and
all seemed to go fine. However, I’m now getting nothing but Internal
Server Error 500 on my rails apps. Non-rails apps are fine…

It doesn’t seem to matter whether i boot webrick or lighttpd, it’s the
same error:

Couldn’t find any pid file in ‘/home/vince/myapp/tmp/pids’ matching
‘dispatch.[0-9]*.pid’
(also looked for processes matching
“/home/vince/myapp/public/dispatch.fcgi”)

It’s happening for brand new apps as well as the ones previously on the
server.

I’ve checked my dispatch.fastcgi and my permissions… it’s driving me
nuts! My logs are all blank so the above error is all I’ve got to run
with. Anyone know a solution?

2

Hi Vince,

My logs are all blank so the above error is all I’ve got to run
with. Anyone know a solution?

you sure this is the only error? Did you checked your webserver logs
(lighttpd), rails logs, syslogs?

Also, please check if rubygems is installed, or the environment
variables
pointing to it are correct. Check the “shebang” lines in
public/dispatch.cgi
/ dispatch.fcgi, if they are pointing to the ruby interpreter. You
should
check, if FastCGI support are available after the update and that you
have
the correct permissions on all your app’s structure. dispatch.cgi /
dispatch.fcgi should be executable and readable to the user running
lighttpd. Please check host definition in lighttpd config files. Please
check if the proper rails gem are installed.

If you can, please try mongrel if that working for you on a single app.
If
it does, you can narrow it down to your fcgi configuration.

Regards,
András

–
András Tarsoly
[email protected]

3

All good points… but all things I’ve looked at extensively.
Remember, even webrick doesn’t work for a new rails app.

Anyway, I scrapped the server and started over.

On 5/7/07, András Tarsoly [email protected] wrote:

/ dispatch.fcgi, if they are pointing to the ruby interpreter. You should
András

–
András Tarsoly
[email protected]

–
support independent business – http://www.buyindie.net/

4

Vince,

I think generally it’s better to only upgrade one ubuntu version at a
time. In your case you should have gone from Dapper to Edgy, and then
to Feisty. I’m not exactly sure why, but I’m guessing that it has to
do with the way that packages are managed.

Josh

5

On 5/9/07, [email protected] [email protected]
wrote:

Vince,

I think generally it’s better to only upgrade one ubuntu version at a
time. In your case you should have gone from Dapper to Edgy, and then
to Feisty. I’m not exactly sure why, but I’m guessing that it has to
do with the way that packages are managed.

Hi Josh,

Probably because they don’t test it. Still, Dapper was the LTS so
they should have. Plus, Dapper to Edgy was a nightmare for many which
is why I didn’t upgrade it. Overall, my enthusiasm for dpkg is down,
but even then it’s hard to beat Ubuntu…

-Vince

6

The state quite clearly on the Ubuntu website that the upgrade process
for Dapper to Feisty invloves upgrading to Edgy first. The only problems
I heard of for people upgrading dapper was when they had none standard
repositories or custome installed drivers (think nVidia/ATI).

Cheers,

Anthony