similar to: Problems with lighty

doing make -f Makewfile.win test-Internet in tests gave make[1]: Leaving directory `/cygdrive/d/Work/R-devel/tests' D:/Work/R-devel/bin/Rterm --vanilla LC_ALL=C --internet2 --vanilla < internet.R > internet.Rout2 diff internet.Rout internet.Rout2 99,100c99,100 < unable to resolve 'foo.bar'. < Error in url("http://foo.bar", "r") : cannot open URL

Rudolf Kollien email: Rudolf.Kollien@medas.de Rudolf.Kollien@kollien.de *************************************************************************** Never trust a operating system you have no sources for *************************************************************************** Buying an operating system without source is like buying a self-assembly Space Shuttle with no instructions.

Hi! I have just added login feature to my rails application (followed the instruction from (Agile Web Development with Rails) but now I am getting strange errors (looks to me like some kind of routing problem) under the passenger/apache. The error is: 500 Internal Server Error The server encountered an internal error or misconfiguration and was unable to complete your request. From the log:

I''m experiencing an issue where my get/submit calls to the Mechanize agent are leading to timeout exceptions when the ruby script has too many open file descriptors ( > 1000). However, I''m not seeing anything about an overstep violation sent anywhere to syslog, and no error message sent to stdout. The process has the large amount of open files because it''s

Just trying to run the example ***** require ''rubygems'' require ''mechanize'' a = WWW::Mechanize.new a.get(''http://rubyforge.org/'') do |page| # Click the login link login_page = a.click(page.links.text(/Log In/)) # Submit the login form my_page = login_page.form_with(:action => ''/account/login.php'')

"Select from a wide variety of brand name and generic rneds. It is legitimate to select licensed chemist-sites to place the or-der.,Customers have better selections for rnedicals on ereection dysfunction, pain, man's care, highcholesterol, stress and obesity. It is easier to stay healthier." [1]Embrace super value and check quality medicals on

I was using lighty+fastcgi before, and it was working pretty well, but I decided to move to Apache+mongrel because I really really like Mongrel. Well now I found out about lighty+pound+mongrel [1] and I think I''m going to give that a shot. I definitely prefer lighty to Apache - it''s pretty ridiculous how much fewer resources it uses. Anyway the only thing I''m going to

Hello all, I''m using Lighty-Win32 and Mongrel. I have one rails app working against http://hostname/. I want to know how to route lighty and my app to http://hostname/appname1. I have multiple apps that I would eventually want to route with http://hostname/appname2, http://hostname/appname3, etc. I am not trying to "productize", these are separate distinct apps that

On httpd I use ProxyPass and ProxyPassReverse to forward requests to webrick and mongrel. How can I do this same thing using Lighty and Mongrel? Thanks, Joe -- Posted via http://www.ruby-forum.com/.

I transferred a site from Lighty+SCGI to Lighty+Mongrel, and now I''m having problems with it becoming unresponsive. It works fine for about 10-15 minutes, but then attempts to access the site just stall forever. Nothing is written in any of lighty''s or mongrel''s logs. Here''s my lighty config: $HTTP["host"] =~ "www.xyz.com" {

Hi all I started to set up a rails stack on debian : debian sarge / XEN 3.0 / Ruby 1.8.4 / Postgresql 8.1.4 / Java 1.5 / Mongrel / Lighttpd Everything went well and worked as expected until I reached lighty. I could not get lighty working at all. I felt like the master of the disaster. I tried the debian backport for lighty 1.4.11, got the ligthy daemon running configured as proxy, but it did

I have a ton of these in my Lighty error log: 2006-02-15 15:55:53: (connections.c.1383) Warning: Either the error-handler returned status 404 or the error-handler itself was not found: /dispatch.scgi 2006-02-15 15:55:53: (connections.c.1385) returning the original status 404 2006-02-15 15:55:53: (connections.c.1387) If this is a rails app: check your production.log And I guess it''s

I''m not sure if it''s due to setting up multiple mongrel servers and proxying them with lighty, but something is keeping postgres connections around. I only have a couple Rails apps running on a new server, with not a whole lot of traffic, yet today I actually maxed out my connection limit of 100 for postgres. How do I turn off persistent connections in Mongrel? Joe --

> ./configure --with-openssl && sudo make install enabled: ... network-openssl ... disabled: ... > which openssl /usr/bin/openssl I get the following message from my lighty install: > SSL: ssl requested but openssl support is not compiled in What am I doing wrong? -Kyle

Hi all! Do we need to install fcgi separately on windows? I have tried scgi; i am not able to do the following: > ruby scgi_ctrl config this is throwing error(load error)... pl. help me in solving this problem... regards, Sivakumar __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

Hi, Do I need to configure something to get my custom public/500.html page showing on my production server (lighttpd)? My custom 404 page is showing but when I hit an exception I just see the default (Applcation Error) message. Also, is it possible to include some ERB in error404 and 500 pages? Jeroen

I''ve just spent a while chasing a false bug in lighttpd and load balancing among external fast cgi processes due to what I think is a documentation bug. Following the info on the wiki page <http://wiki.rubyonrails.com/rails/pages/LighttpdWithProcessScripts>, one would think that something like this works: fastcgi.debug = 1 fastcgi.server = ( ".fcgi" => (

I''m trying to get our app running on Lighty... I followed Ezra''s instructions: http://brainspl.at/pages/rails_stack... Currently the app runs fine with webrick, but with lighty I get 404 errors on everything. I found if I don''t edit the lighttpd.conf file to use absolute paths, it works fine. But this is not good for production because I need to run it with the -d

I''ve been trying to get fast cgi working for nearly a month now. Yes, an entire month! The application starts perfect, but it will die randomly after several hours. I have traced the problem back to /usr/lib/ruby/1.8/mysql.rb:1042:in `flush'' This happens when the app trys to query the database driver to see if it still has a connnection. This causes the app to crash. Here is

I have an action which requests another URL from the same site (for testing purposes), but it keeps timing out. If I use an off-site URL, the action works fine. I also notice that I''m only able to request one page at a time from my server - the rest just spin until the previous requests complete. Is this some setting in Lighty, Mongrel, or my browser (Firefox - I played around with