Search results

that was it - thanks mistwang - thanks for the prompt reply - i was in fact running out of memory. which led me to realize the page was implemented inefficiently, rewrote for a 10x speed/resources optimization and it's working good now. chris

i have a particular rails page that consistently takes awhile to generate (as it's supposed to), but no matter what i have tried i have been unable to tweak the timeout settings properly to avoid a 503 error. (running rails via lsapi, manual setup). When I run a webrick server in the same...

thanks, that worked!! just had to go into the admin UI, click on my VHOST name, click "Edit" in the Access Log section, select "server's log file" from the log control drop down, and this created the needed section in my VHOST. on restart i got full logging for that vhost, now i will replicate...

thanks i will try that thanks i will try that - i forgot to add that this suddenly started happening a few months ago after working fine for several months (had vhosts before and after)

hi, my access.log now logs only 404's - no 200's or any other status code. Here is the <logging> section of my http_config.xml file: <logging> <log> <fileName>$SERVER_ROOT/logs/error.log</fileName> <logLevel>DEBUG</logLevel> <debugLevel>0</debugLevel>...

Thanks for such a rapid response! It turns out my problem was that I was running ruby 1.8.3, apparently rails 1.1 is not compatible with it. I upgraded to ruby 1.8.4 and that solved my problem. I checked out the LSAPI, that looks interesting, I will probably try it out. Just not today, i have...

Hi, I just installed Rails 1.1 into my production test environment and litespeed hung! it still serves static files fine but just spins its wheels for several minutes before giving a "service unavailable" message whenever I try to invoke a rails page. Anyone encountering this? Have any ideas...