Forum: Ruby on Rails Problem on Dreamhost: engine for rails 1.1.6

Announcement (2017-05-07): is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see and for other Rails- und Ruby-related community platforms.
Ca0b18ec9e11dc777b2b8084fe5d5f90?d=identicon&s=25 Sam Kong (ssk)
on 2007-04-09 10:39
(Received via mailing list)

I'm trying to set up Substruct (shopping cart engine) on Dreamhost.
I failed several times and tracked down to the problem area.

I can reproduce the problem with these steps:

1. install rails
2. change public/.htaccess for fcgi
3. change public/dispatch.fcgi for RailsFCGIHandler

At this step, I can execute public/dispatch.fcgi without error.

4. svn co vendor/

I get

Status: 500 Internal Server Error
Content-Type: text/html

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"

<html xmlns="" xml:lang="en" lang="en">

  <meta http-equiv="content-type" content="text/html; charset=UTF-8" /
  <title>We're sorry, but something went wrong</title>
        <style type="text/css">
                body { background-color: #fff; color: #666; text-
align: center; font-family: arial, sans-serif; }
                div.dialog {
                        width: 25em;
                        padding: 0 4em;
                        margin: 4em auto 0 auto;
                        border: 1px solid #ccc;
                        border-right-color: #999;
                        border-bottom-color: #999;
                h1 { font-size: 100%; color: #f00; line-height:
1.5em; }

  <!-- This file lives in public/500.html -->
  <div class="dialog">
    <h1>We're sorry, but something went wrong.</h1>
    <p>We've been notified about this issue and we'll take a look at
it shortly.</p>

What's wrong with that?


5030981121b21bed8aee074f68bd5074?d=identicon&s=25 Russell Norris (Guest)
on 2007-04-09 16:44
(Received via mailing list)
Two things. I presume there's nothing being logged in the Rails log
directory, right? Okay. Good. First, try firing up the old
and see if/what errors you get from that. Second, look at the Apache
logs [usually found in ~/logs/YOUR_DOMAIN_NAME/http/ ] Sometimes [but
rarely!] there's actually useful information in there. But usually the
console will reveal the nasties breaking your code. Hope that helps.

This topic is locked and can not be replied to.