p.s. I was running an old version (frozen rails 1.0)... so I backed up and updated to HEAD of trunk and am still getting the same problems... with frozen rails 1.1.
Jake Good wrote: > I'm having trouble as of today on DH. Blog was running fine yesterday... > > When I try to run script/console I get > > [scagnetti]$ ./script/console > ./script/../config/boot.rb:7:in `require': no such file to load -- > pathname (LoadError) > from ./script/../config/boot.rb:7 > from ./script/console:2:in `require' > from ./script/console:2 > > And in my access.log I get this. > > [Fri May 19 08:04:20 2006] [error] [client 71.39.198.114] FastCGI: comm > with (dynamic) server > "/home/thoughtstoblog/sites/thoughtstoblog.com/public/dispatch.fcgi" > aborted: (first read) idle timeout (120 sec) > [Fri May 19 08:04:20 2006] [error] [client 71.39.198.114] FastCGI: > incomplete headers (0 bytes) received from server > "/home/thoughtstoblog/sites/thoughtstoblog.com/public/dispatch.fcgi" > > > Mike Purvis wrote: > >> Hi Scott, >> >> Thanks for your reply. How would I determine if Rails is frozen? >> >> I observe that when I run the svn upgrade, it pulls in a specific >> revision of Rails and places it in that directory, but how do I check >> if that's what's actually being used? >> >> I know that at various times, I've installed my own ruby *and* rails, >> although I was fairly sure I'd been running Dreamhost's ruby and >> Dreamhost's rails. Indeed a "whereis rails" from my shell shows >> "/usr/bin/rails". On the other hand, when I navigate to /usr/bin, >> there's no rails to be found... >> >> Is it just a matter of (somewhere) pointing that missing pathname >> variable to vendor/rails? >> >> Mike >> >> >> On 5/19/06, *Scott Bronson* < [EMAIL PROTECTED] >> <mailto:[EMAIL PROTECTED]>> wrote: >> >> On Fri, 2006-05-19 at 09:40 -0400, Mike Purvis wrote: >> > I was on the typo mailing list about a year ago, but I seem to be >> > having problems again. I'm not sure if it's just that Dreamhost is >> > crappy for RoR, but on the whole, I've found running Typo a very >> > frustrating experience. (you know, apart from the occasional periods >> > where it would run perfectly fine and be terrific... I really >> > appreciate all the hard work the devs have put into making Typo >> great, >> > I just wish I could get it going more reliably for myself.) >> >> Just checking: rails is frozen in vendor/ right? If not, then that's >> why it's so unstable. Other than the latency from their machines >> being >> so drastically overcommitted, personally I don't find DH to be too >> bad. >> >> I feel your pain. I'm wondering if Typo is starting to pull a >> Debian...? The stable version is hopelessly out of date and the >> development version is often breaking in new and strange ways, >> leaving >> no version suitable for production usage. Just a thought. >> >> - Scott >> >> >> >> _______________________________________________ >> Typo-list mailing list >> [email protected] <mailto:[email protected]> >> http://rubyforge.org/mailman/listinfo/typo-list >> >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> Typo-list mailing list >> [email protected] >> http://rubyforge.org/mailman/listinfo/typo-list >> > _______________________________________________ > Typo-list mailing list > [email protected] > http://rubyforge.org/mailman/listinfo/typo-list > > _______________________________________________ Typo-list mailing list [email protected] http://rubyforge.org/mailman/listinfo/typo-list
