Rails - May 2005 - Printing a directory listing in Rails

im trying to access a folder in my public directory and print all the 
files in it.  i''ve got the Ruby libary for Dir, but I keep hitting Bad 
Gateway errors.  Anyone doing this already with some pointers?

Jason,

On 25.5.2005, at 10:11, jason lynes :: senyl.com wrote:
> im trying to access a folder in my public directory and print all the 
> files in it.  i''ve got the Ruby libary for Dir, but I keep hitting
Bad
> Gateway errors.  Anyone doing this already with some pointers?
Bad Gateway errors typically occur when you''re using Apache proxy in 
front of a lighttpd server. It only means that there is some error in 
your rails code and lighttpd doesn''t therefore respond correctly. You 
should take a look at your error log (development or production, 
depending on which environment you''re talking about) and see what the 
real error is.

You also get this error when the lighttpd instance is not running at 
all.

//jarkko

--
Jarkko Laine
http://jlaine.net
http://odesign.fi


_______________________________________________
Rails mailing list
Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
http://lists.rubyonrails.org/mailman/listinfo/rails

On 25.5.2005, at 21:29, jason lynes :: senyl.com wrote:
> Jarkko,
>
> thanks for the response.  you seem to know a bit about lighttpd- 
i''m
> having a problem (unrelated to dir listing, which i fixed, thanks), in 
> which lighttpd either crashes or freezes. I have daedalus running to 
> keep an eye on it, both when lighttpd isnt running and also when a 
> test call to the DB isnt responding. it crashes about once a day, but 
> it is freezing, when a call to the db times out, about 5-6 times a 
> day.  any experience with this?  i am very new to lighttpd, so i''m
at
> a loss as to what could be making it freeze or crash.  any ideas would 
> help a ton.
I have experienced something similar but have yet to dig any deeper to 
it. I have two rails instances running under one lighttpd process. They 
share a single database but I don''t know if it''s got anything
to do
with the problem. Anyway, sometimes the fcgi processes of one of these 
instances just die. Like said, I haven''t taken a closer look at it yet 
but the db connection might well be the source of the problem. However, 
my current daedalus setup doesn''t work perfectly in this case because 
lighttpd (and the other rails instance) is running just fine. Of course 
the external curl-powered test fails so daedalus tries to kick in every 
five minutes. However, Johan''s lighttpdctrl.sh script doesn''t
seem to
work always because the pid file sometimes just disappears.

So at the moment I''m out in the blue. But let''s keep this
thread alive
if anyone finds any source or cures for this problem.

//jarkko

--
Jarkko Laine
http://jlaine.net
http://odesign.fi


_______________________________________________
Rails mailing list
Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
http://lists.rubyonrails.org/mailman/listinfo/rails