Deploying Radiant on site5

I have been trying to deploy radiant on site5, and I think I am close to

However, when go to the frontpage it says:

Application error

Rails application failed to start properly

In the error log this is the message:

[Sat Jul 12 07:58:44 2008] [notice] mod_fcgid: process

/home/chainrea/public_html/dispatch.fcgi(24336) exit(communication
error), terminated by calling exit(), return code: 116

So i guess something is wrong with som fast cgi stuff? How can i fix it?

I only got this far by combining these two tutorials:


I have tried doing it over and over to recheck for typo’s and so on but
with no luck.

But maybe it was a bad idea to use two tutorials and jump to the other
one whenever I got stuck?

But when I only follow this tutorial:

I get stuck at:

Unpack the application using the radiant command into the directory
radapp (it will create the directory if it does not exist).

$ ~/gems/bin/radiant --database mysql radapp

I then get this error:

/usr/lib/site_ruby/1.8/rubygems.rb:578:in report_activate_error': Could not find RubyGem radiant (>= 0) (Gem::LoadError) from /usr/lib/site_ruby/1.8/rubygems.rb:134:inactivate’
from /usr/lib/site_ruby/1.8/rubygems.rb:49:in `gem’
from /home/chainrea/gems/bin/radiant:18

Please help. Right now I don’t need to deploy something specific - I
just want to get the basic radiant up and running remotely.

(I hove no problems with getting it up and running locally.)

OKAY now I got through to the end of the tutorial with:

Create the admin user (press enter for defaults).
Name (Administrator):
Username (admin):
Password (radiant):

Initializing configuration…OK

Select a database template:

  1. Empty
  2. Simple Blog
  3. Styled Blog
    [1-3]: 2

Creating Snippets…OK
Creating Pages…OK
Creating Layouts…OK
Creating Page parts…OK


But when I go to my site it stil says:

Application error

Rails application failed to start properly



Hello here are the results

gem env:

[[email protected] ~]$ gem env
RubyGems Environment:

  • RUBY VERSION: 1.8.5 (2006-08-25) [i386-linux]
  • INSTALLATION DIRECTORY: /home/chainrea/gems
  • RUBY EXECUTABLE: /usr/bin/ruby
  • EXECUTABLE DIRECTORY: /home/chainrea/gems/bin
    • ruby
    • x86-linux
    • /home/chainrea/gems
    • /usr/lib/ruby/gems/1.8
    • :update_sources => true
    • :verbose => true
    • :benchmark => false
    • :backtrace => false
    • :bulk_threshold => 1000
    • “gemhome” => “/home/chainrea/gems”
    • “gempath” => ["/home/chainrea/gems", “/usr/lib/ruby/gems/1.8”]

cd /path/to/radiant - I’m not shure about this one? Do you want to know
were radiant is installed or were my “radiant app” is?

ruby dispatch.fcgi:

[[email protected] ~]$ cd radapp
[[email protected] radapp]$ cd public
[[email protected] public]$ ruby dispatch.fcgi
Content-Type: text/html; charset=utf-8
Status: 200 OK
Last-Modified: Sun, 13 Jul 2008 12:18:47 GMT
X-Runtime: 0.00535
ETag: “d691833cfe4ba66ce222822f471049dd”
Content-Length: 980

Home Page

Home Page

<div id="content">

First Post Administrator

This post uses textile.

Second Post Administrator

This post uses Markdown.

  <div id="extended">

<hr />

Powered by Radiant CMS

Oh now I understand with regards to “cd path to radiant” - you just
meant that i had to go to my radiant app and execute ruby dispatch.fcgi:

Hi Jan,

Try this: Open an ssh terminal. Run the following commands and post

gem env
cd /path/to/radiant
ruby dispatch.fcgi

You can also run ruby with the debug flag on (-d) but i find that even a
working installation generates a lot of spurious complaints.

Good luck!

On Sat, Jul 12, 2008 at 4:45 PM, Jan frederik Poulsen [email protected]

I just want to crarify in case others run in to the same issue - all my
problems were due to wrong folder permissions.

For some reason the radiant command that builds the site/app gives the
folders a wrong permission (for running on site5). To get this working
simply change all the folder permissions to 755 (also the app folder it
self i think.)

Site5 helped me - kudos to their high level of service.

Apparently it was an issue with folder permissions “755”.

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs