Wednesday, December 26, 2007

REDMINE RUBY ON RAILS at SERVAGE HOSTING 2nd

Dec 25 - 01:27 GMT
Customer
Hi Servage

We are receiving the following error on our Redmine installayion in "-redmine" folder
_________________
Application error
Rails application failed to start properly
_________________

This is happening as we can't execute the needed ruby on rails commands to build up the database as recommended on redmines and your FAQ.

We can't execute the next tasks on servage -
How will this work without ssh access?
How is it possible to get redmine running on Servage?
Will you be able assist in this problem?
How can I execute a "rake" command?

STEP 1 - 3 were successfully configured.
_______________________________
4. Create the database structure, by running the following command under the application root directory:

rake db:migrate RAILS_ENV="production"

It will create tables and an administrator account.

5. Insert default configuration data in database, by running the following command:

rake redmine:load_default_data RAILS_ENV="production"

This step is optional but highly recommended, as you can define your own configuration from scratch. It will load default roles, trackers, statuses, workflows and enumerations.

6. Test the installation by running WEBrick web server:

ruby script/server -e production

Once WEBrick has started, point your browser to http://localhost:3000/. You should now see the application welcome page.
_________________________________

I hope you will answer on time.

For your information:
To satisfy the needs of our customers we will publish our correspondence online available for public. We think it is very important for our customers to see how hard we are working and that they also see where problems and solutions get stuck.

Thanks a lot for your help.

Andi
Dec 25 - 01:50 GMT
Josh
Hello Andreas,

Thank you for submitting a ticket.

We would suggest you that please check the Simple installation of RoR application should be as follows:

Virtual host path to mount your root is yourapp/public.

permissions:

chmod 755 to the all folders/files in your application

change ownership of: yourapp/log/ yourapp/tmp/ (recusive, to 'webserver')

Paths:

change the path in yourapp/public/dispatch.cgi|fcgi|rb

to #!/usr/bin/ruby, from your local path.

.htaccess corrections: (to enable fast cgi)
This will enable your application, to use fcgi, with is about x10 faster then normal cgi

# General Apache options
AddHandler fcgid-script .fcgi
#AddHandler fastcgi-script .fcgi
AddHandler cgi-script .cgi
Options +FollowSymLinks +ExecCGI

# If you don't want Rails to look in certain directories,
# use the following rewrite rules so that Apache won't rewrite certain requests
#
# Example:
# RewriteCond %{REQUEST_URI} ^/notrails.*
# RewriteRule .* - [L]

# Redirect all requests not available on the filesystem to Rails
# By default the cgi dispatcher is used which is very slow
#
# For better performance replace the dispatcher with the fastcgi one
#
# Example:
#RewriteRule ^(.*)$ dispatch.fcgi [QSA,L]
RewriteEngine On

# If your Rails application is accessed via an Alias directive,
# then you MUST also set the RewriteBase in this htaccess file.
#
# Example:
# Alias /myrailsapp /path/to/myrailsapp/public
# RewriteBase /myrailsapp

RewriteRule ^$ index.html [QSA]
RewriteRule ^([^.]+)$ $1.html [QSA]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteRule ^(.*)$ dispatch.fcgi [QSA,L]
#RewriteRule ^(.*)$ dispatch.cgi [QSA,L]

# In case Rails experiences terminal errors
# Instead of displaying this message you can supply a file here which will be rendered instead
#
# Example:
# ErrorDocument 500 /500.html

ErrorDocument 500 "

Application error

Rails application failed to start properly"

Once everything is perfect update this ticket and we will run following command for you,

rake db:migrate RAILS_ENV="production"

I hope this helps :)

Kind regards,
Josh, Support
Servage Hosting
Dec 25 - 02:38 GMT
Customer
Hi Josh
What is the actual path for this - I asked before and your support told me it is

usr/bin/ruby - it seems that this is NOT the right path FROM MY LOCAL PATH. Can you please send me the right path how it should be written into .htaccess

The domain is http://www.t3log.info
and the redmine installation is in the folder -redmine

http://www.t3log.info has its starting folder -redmine

Thanks
Andi
Dec 25 - 02:55 GMT
Customer
Hi Josh

Thats how the dispatch.fcgi looks like

------------------
usr/bin/ruby
#
# You may specify the path to the FastCGI crash log (a log of unhandled
# exceptions which forced the FastCGI instance to exit, great for debugging)
# and the number of requests to process before running garbage collection.
#
# By default, the FastCGI crash log is RAILS_ROOT/log/fastcgi.crash.log
# and the GC period is nil (turned off). A reasonable number of requests
# could range from 10-100 depending on the memory footprint of your app.
#
# Example:
# # Default log path, normal GC behavior.
# RailsFCGIHandler.process!
#
# # Default log path, 50 requests between GC.
# RailsFCGIHandler.process! nil, 50
#
# # Custom log path, normal GC behavior.
# RailsFCGIHandler.process! '/var/log/myapp_fcgi_crash.log'
#
require File.dirname(__FILE__) + "/../config/environment"
require 'fcgi_handler'

RailsFCGIHandler.process!
------------------------

Andi

Is this OK like this? or does the path be different?
Dec 25 - 02:57 GMT
Customer
Hi Josh

and that's the .htaccess in /public

-------------------
# General Apache options

AddHandler fastcgi-script .fcgi


AddHandler fcgid-script .fcgi


AddHandler cgi-script .cgi

Options +FollowSymLinks +ExecCGI

# If you don't want Rails to look in certain directories,
# use the following rewrite rules so that Apache won't rewrite certain requests
#
# Example:
# RewriteCond %{REQUEST_URI} ^/notrails.*
# RewriteRule .* - [L]

# Redirect all requests not available on the filesystem to Rails
# By default the cgi dispatcher is used which is very slow
#
# For better performance replace the dispatcher with the fastcgi one
#
# Example:
RewriteRule ^(.*)$ dispatch.fcgi [QSA,L]
RewriteEngine On

# If your Rails application is accessed via an Alias directive,
# then you MUST also set the RewriteBase in this htaccess file.
#
# Example:
# Alias /myrailsapp /path/to/myrailsapp/public
# RewriteBase /myrailsapp

RewriteRule ^$ index.html [QSA]
RewriteRule ^([^.]+)$ $1.html [QSA]
RewriteCond %{REQUEST_FILENAME} !-f

RewriteRule ^(.*)$ dispatch.fcgi [QSA,L]


RewriteRule ^(.*)$ dispatch.fcgi [QSA,L]


RewriteRule ^(.*)$ dispatch.cgi [QSA,L]


# In case Rails experiences terminal errors
# Instead of displaying this message you can supply a file here which will be rendered instead
#
# Example:
# ErrorDocument 500 /500.html

ErrorDocument 500 "

Application error

Rails application failed to start properly"

--------------------
I think it should be OK like this

Can you please try to execute the command?

Thanks

Andi
Dec 25 - 04:04 GMT
Servage - Bob
Hello Andreas,

Thanks for updating the ticket.

Our senior admins will test the command for you and inform you the result.

Thanks for your patience and co-operation.

Kind regards,
Bob, Support
Servage Hosting
Dec 25 - 05:22 GMT
Customer
Hi Bob

Any Updates as we need to get redmine running BEFORE the money back 5 day expires ;-)

Thanks
Andi
Dec 25 - 11:56 GMT
Support - Jakob
Hello Andreas,

This has not been done yet, however, you can use this as a refund reason even after the money back period (because you have mentioned it within the money back period). So, as soon as the module is available, you can test.

Kind regards,
Jakob, Support
Servage Hosting
Dec 26 - 02:27 GMT
Customer
Hi Servage

I still got the Application Error due to the fact that the commands havened been executed to create the database like mentioned before.

We need to continue working here and are completely stuck because of this since 2 days now. PLEASE execute the command and get redmine working as REDMINE is needed for our work we are doing for our Customer and we have to match their timelines!!!

Thanks
Andi
Dec 26 - 08:00 GMT
Customer
For your Notice:
THIS TICKET WILL BE TEMPORARILY CLOSED AND PUBLISHED ONLINE IF NO FURTHER ASSISTANCE IS GIVEN IN THE NEXT 30 MINUTES.

We need to get Ruby on Rails Applications running on your server as you are advertising RoR Support. This ticket is open since 2 days now without any solution HOW to get a Ruby on Rails Application running on your servers. Probably it isn't possible at all and you are only advertising RoR support. Who knows? At the moment it looks like this - sorry!

Andi


No comments: