Need help with fcgi / engine

Rails Engines
1

I’ve been banging my head for a few days, appreciate any help.

I’m not seeing login_engine starting up.

I’m on commercial host, so I don’t have the capability of upgrading
myself. But, when I call, they were happy to upgrade me to rails 1.1.4.

I’m using login_engine, which I have working on my system here in the
past with webrick. But when I install it fresh to the commercial host, I
get the following errors:

[Thu Jul 6 08:28:08 2006] [warn] FastCGI: (dynamic) server
“/home/xxx/public_html/devel/dispatch.fcgi” (uid x, gid x) started (pid
9397) [Thu Jul 6 08:28:11 2006] [warn] FastCGI: (dynamic) server
“/home/xxx/public_html/devel/dispatch.fcgi” (uid x, gid x) started (pid
9450) [Thu Jul 6 08:28:14 2006] [warn] FastCGI: (dynamic) server
“/home/xxx/public_html/devel/dispatch.fcgi” (pid 9450) termination
signaled [Thu Jul 6 08:28:14 2006] [warn] FastCGI: (dynamic) server
“/home/xxx/public_html/devel/dispatch.fcgi” (pid 9450) terminated by
calling exit with status ‘0’

I’ve also seen some fopen errors, complaining about not being able to
open a log file. I’ve changed the entire log directory to 777, but no
luck.

On the web page itself, I just get a routing error. Inside the fcgi
crash log I get
…:9397] starting
…:9450] starting
…:9450] asked to terminate immediately
…:9450] terminated by explicit exit
…:9397] asked to terminate immediately
…:9397] terminated by explicit exit

In the suexec error log (another reload so it’s later), I get

[2006-07-06 08:42:00]: info: (target/actual) uid: (xx/xx) gid: (x/x)
cmd: dispatch.fcgi

In my development log I see (seems like a general error, nothing
specific about the engine)

Processing Base#index (for x.x.x.x at 2006-07-06 08:42:01) [GET]
Session ID: xxx
Parameters: {}

ActionController::RoutingError (Recognition failed for “/”):
/usr/lib/ruby/gems/1.8/gems/actionpack-1.12.1/lib/action_controller/routing.rb:488:in
recognition_failed' /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.1/lib/action_controller/routing.rb:478:in recognize!’
/usr/lib/ruby/gems/1.8/gems/rails-1.1.2/lib/dispatcher.rb:38:in
dispatch' /usr/lib/ruby/gems/1.8/gems/rails-1.1.2/lib/fcgi_handler.rb:150:in process_request’
/usr/lib/ruby/gems/1.8/gems/rails-1.1.2/lib/fcgi_handler.rb:54:in
process!' /usr/lib/ruby/gems/1.8/gems/fcgi-0.8.6.1/./fcgi.rb:600:in each_cgi’
/usr/lib/ruby/gems/1.8/gems/fcgi-0.8.6.1/./fcgi.rb:597:in each_cgi' /usr/lib/ruby/gems/1.8/gems/rails-1.1.2/lib/fcgi_handler.rb:53:in process!’
/usr/lib/ruby/gems/1.8/gems/rails-1.1.2/lib/fcgi_handler.rb:23:in
`process!’
dispatch.fcgi:23

Rendering
/usr/lib/ruby/gems/1.8/gems/actionpack-1.12.1/lib/action_controller/templates/rescues/layout.rhtml
(404 Page Not Found)

I’ve changed my .htaccess for the Rewrite. Any other recommendations on
how to troubleshoot this? It seems like login_engine isn’t starting, or
even being recognized.

The regular rails index.html works, by the way, and the unit tests for
the login_engine pass.

I’ve seen this mention about engines, but I’m not getting it started, so
something else is wrong:

ruby 1.8.4
rails 1.1.4
Apache version 1.3.36 (Unix)
mod_fastcgi 2.4.2

Note that the site was generated with 1.1.2, but 1.l.4 is running now.

I really appreciate any help.

2

Just saw Tim’s post from yesterday on failing engines, if that’s it, let
me know. I’ll read it more closely, it didn’t show up on the google
search, just noticed it from an iris search.

Joe

3

Joe,

Please try updating your copy of the engines plugin. I’ve just
released 1.1.3, with a minor fix for the issues that some people were
experiencing using Rails 1.1.4.

  • james
4

Hi James,

I have engines 1.1.3 installed, but still seeing the same error.

I’ve added a engine logger, but nothing shows up in it. Any thoughts,
please let me know, I see the same errors in the server logs, so it must
be more upstream.

Joe

James A. wrote:

Joe,

Please try updating your copy of the engines plugin. I’ve just
released 1.1.3, with a minor fix for the issues that some people were
experiencing using Rails 1.1.4.

  • james
5

Hmm… it seems like something more fundamental is going wrong with
your application’s environment. Have you double checked your routes.rb
file? Does it work under webrick?

  • james
6

The default index.html works fine.

I’ve setup login_engine before, and compared the two routes.rb, they’re
identical, but that was an older version of rails and login_engine.

In the README for login_engine, it mentions about setting up “default
routes”, but there is no specific information. I thought the before
filter requiring authentication would take care of redirects to the
login prompt. Are there routes I have to setup for login_engine? I
haven’t in the past, was I just lucky?

Anyways, shouldn’t the engine startup, and I should get some sort of log
file?

Joe

James A. wrote:

Hmm… it seems like something more fundamental is going wrong with
your application’s environment. Have you double checked your routes.rb
file? Does it work under webrick?

  • james
7

One more item - I’m using a commercial host, so I can’t use webrick.
Bummer.

Joe

Joe Kr wrote:

The default index.html works fine.

I’ve setup login_engine before, and compared the two routes.rb, they’re
identical, but that was an older version of rails and login_engine.

In the README for login_engine, it mentions about setting up “default
routes”, but there is no specific information. I thought the before
filter requiring authentication would take care of redirects to the
login prompt. Are there routes I have to setup for login_engine? I
haven’t in the past, was I just lucky?

Anyways, shouldn’t the engine startup, and I should get some sort of log
file?

Joe

James A. wrote:

Hmm… it seems like something more fundamental is going wrong with
your application’s environment. Have you double checked your routes.rb
file? Does it work under webrick?

  • james
8

It looks like the update did work, www.mydomain.com/user/login works,
but when I go to www.mydomain.com, it doesn’t automatically go to the
login page. Some kind of routing problem, I’ll beat it up a bit.

Thanks for all the help.