Rails - Feb 2006 - Lighttpd segfaults on first access

I just got a new Debian Sarge server and followed the brainspl.at  
"Debian Lighttpd Rails Stack" tutorial.

The only place I deviated was the version of Lighty.  The page uses  
1.4.7 and I spotted that 1.4.10 was available.  I installed that and  
couldn''t get anywhere.  Lighty died on first access from the test  
rails app, and even from a ultra basic static config.   No log, no  
info, just dead.

I downloaded 1.4.7, installed it and everything is fine.   Great  
tutorial, works as advertised, but I''m not sure why there are  
problems with the later version of lighty... any ideas ?

I''ll stick with 1.4.7 for the moment, since it works.  If this  
segfault is a known bug, when was it introduced ?  Can I get a more  
recent version (.8 or .9)?  Obviously I''d like to be running as up-to- 
date a version as possible.

A.
--
mailto:alancfrancis@gmail.com
http://blog.alancfrancis.com/

On Feb 10, 2006, at 1:42 AM, Alan C Francis wrote:
> I just got a new Debian Sarge server and followed the brainspl.at  
> "Debian Lighttpd Rails Stack" tutorial.
>
> The only place I deviated was the version of Lighty.  The page uses  
> 1.4.7 and I spotted that 1.4.10 was available.  I installed that  
> and couldn''t get anywhere.  Lighty died on first access from the  
> test rails app, and even from a ultra basic static config.   No  
> log, no info, just dead.
>
> I downloaded 1.4.7, installed it and everything is fine.   Great  
> tutorial, works as advertised, but I''m not sure why there are  
> problems with the later version of lighty... any ideas ?
>
> I''ll stick with 1.4.7 for the moment, since it works.  If this  
> segfault is a known bug, when was it introduced ?  Can I get a more  
> recent version (.8 or .9)?  Obviously I''d like to be running as
up-
> to-date a version as possible.
>
> A.

Alan-

	Are you just using the lighttpd.conf file that gets generated by  
running script/server? The newer versions of lighty don''t work with  
relative paths that get generated in the script/server lighttpd.conf.  
If you edit that file and make all the paths absolute it should work  
fine. But there have been a few problems with the newsest releases of  
lighty. You are fine with 1.4.7 for now. I would just watch the  
releases of lighty and maybe try them when they are bug free. But  
there is nothing you are missing out on with 1.4.7 right now.

Cheers-
-Ezra Zygmuntowicz
WebMaster
Yakima Herald-Republic Newspaper
ezra@yakima-herald.com
509-577-7732

Thanks Ezra,

Exactly what I needed to hear :-)

I was using the default conf file, but as I said the same thing  
happens when I write my own super-basic static only /var/www server.   
I''ll stick with .7 :-)

A.
>
> 	Are you just using the lighttpd.conf file that gets generated by
> running script/server? The newer versions of lighty don''t work
with
> relative paths that get generated in the script/server lighttpd.conf.
> If you edit that file and make all the paths absolute it should work
> fine. But there have been a few problems with the newsest releases of
> lighty. You are fine with 1.4.7 for now. I would just watch the
> releases of lighty and maybe try them when they are bug free. But
> there is nothing you are missing out on with 1.4.7 right now.

--
mailto:alancfrancis@gmail.com
http://blog.alancfrancis.com/

I was bitten by the same default rails lighttpd.conf but I found all I
needed to add was:

"bin-path"  => CWD + "/public/dispatch.fcgi",

The CWD = Current Working Directory which is the root of the Rails app.

Again, this is the same thing as an absolute path but it uses the
variable CWD.  I suspect Rails will probably fix that some time soon.

The reason I elected to go with Lighttpd-1.4.10?  I saw that 1.4.8 has
a security hole!  "In lighttpd 1.4.8 and below is a CRITICAL bug which
allows
unauthenticated users to read all files from the documentation root if
the used file-system is case-insensitive."  Well HFS+ is case
insensitive under OS X.

Not that it''s a big issue for me on a development box.  But I like to
be as close to production as possible.


On 2/12/06, Alan C Francis <alancfrancis@gmail.com>
wrote:
> Thanks Ezra,
>
> Exactly what I needed to hear :-)
>
> I was using the default conf file, but as I said the same thing
> happens when I write my own super-basic static only /var/www server.
> I''ll stick with .7 :-)
>
> A.
>
> >
> >       Are you just using the lighttpd.conf file that gets generated by
> > running script/server? The newer versions of lighty don''t
work with
> > relative paths that get generated in the script/server lighttpd.conf.
> > If you edit that file and make all the paths absolute it should work
> > fine. But there have been a few problems with the newsest releases of
> > lighty. You are fine with 1.4.7 for now. I would just watch the
> > releases of lighty and maybe try them when they are bug free. But
> > there is nothing you are missing out on with 1.4.7 right now.
>
>
> --
> mailto:alancfrancis@gmail.com
> http://blog.alancfrancis.com/
>
>
>
> _______________________________________________
> Rails mailing list
> Rails@lists.rubyonrails.org
> http://lists.rubyonrails.org/mailman/listinfo/rails
>