charlie bowman
2006-Apr-01 15:34 UTC
[Rails] my app broke this morning on with this error.
Like I said, my app suddenly stoped working in the last few minutes. I''m on dreamhost but I''m running rdge rails locked in on the 1.1 release. Stale NFS file handle - ../config/../log/production.log /usr/lib/ruby/1.8/logger.rb:520:in `write'' /usr/lib/ruby/1.8/logger.rb:520:in `write'' /usr/lib/ruby/1.8/logger.rb:318:in `add'' /usr/lib/ruby/1.8/logger.rb:372:in `info'' ../config/../vendor/rails/actionpack/lib/action_controller/base.rb:900:in `log_processing'' ../config/../vendor/rails/actionpack/lib/action_controller/base.rb:378:in `process_without_filters'' ../config/../vendor/rails/actionpack/lib/action_controller/filters.rb:364:in `process_without_session_management_support'' ../config/../vendor/rails/actionpack/lib/action_controller/session_management.rb:117:in `process'' ../config/../vendor/rails/railties/lib/dispatcher.rb:38:in `dispatch'' ../config/../vendor/rails/railties/lib/fcgi_handler.rb:150:in `process_request'' ../config/../vendor/rails/railties/lib/fcgi_handler.rb:54:in `process!'' ../config/../vendor/rails/railties/lib/fcgi_handler.rb:53:in `each_cgi'' /usr/lib/ruby/1.8/fcgi.rb:597:in `each'' /usr/lib/ruby/1.8/fcgi.rb:597:in `each_cgi'' ../config/../vendor/rails/railties/lib/fcgi_handler.rb:53:in `process!'' ../config/../vendor/rails/railties/lib/fcgi_handler.rb:23:in `process!'' dispatch.fcgi:34 -- Posted via http://www.ruby-forum.com/.
Joshua Schairbaum
2006-Apr-01 16:47 UTC
[Rails] my app broke this morning on with this error.
Has anything changed with permissions or something with the production.log file. It seems that it''s looking for that file and it''s not there and not creating it. Another thought, complete stab in the dark is checking enviroment.rb to see if something concerning logging occured. I''m assuming this problem is solely because logging stopped working. On Saturday, April 01, 2006, at 5:34 PM, charlie bowman wrote:>Like I said, my app suddenly stoped working in the last few minutes. >I''m on dreamhost but I''m running rdge rails locked in on the 1.1 >release. > >Stale NFS file handle - ../config/../log/production.log >/usr/lib/ruby/1.8/logger.rb:520:in `write'' >/usr/lib/ruby/1.8/logger.rb:520:in `write'' >/usr/lib/ruby/1.8/logger.rb:318:in `add'' >/usr/lib/ruby/1.8/logger.rb:372:in `info'' >../config/../vendor/rails/actionpack/lib/action_controller/base.rb:900:in >`log_processing'' >../config/../vendor/rails/actionpack/lib/action_controller/base.rb:378:in >`process_without_filters'' >../config/../vendor/rails/actionpack/lib/action_controller/ >filters.rb:364:in >`process_without_session_management_support'' >../config/../vendor/rails/actionpack/lib/action_controller/ >session_management.rb:117:in >`process'' >../config/../vendor/rails/railties/lib/dispatcher.rb:38:in `dispatch'' >../config/../vendor/rails/railties/lib/fcgi_handler.rb:150:in >`process_request'' >../config/../vendor/rails/railties/lib/fcgi_handler.rb:54:in `process!'' >../config/../vendor/rails/railties/lib/fcgi_handler.rb:53:in `each_cgi'' >/usr/lib/ruby/1.8/fcgi.rb:597:in `each'' >/usr/lib/ruby/1.8/fcgi.rb:597:in `each_cgi'' >../config/../vendor/rails/railties/lib/fcgi_handler.rb:53:in `process!'' >../config/../vendor/rails/railties/lib/fcgi_handler.rb:23:in `process!'' >dispatch.fcgi:34 > >-- >Posted via http://www.ruby-forum.com/. >_______________________________________________ >Rails mailing list >Rails@lists.rubyonrails.org >http://lists.rubyonrails.org/mailman/listinfo/rails-- Posted with http://DevLists.com. Sign up and save your mailbox.
charlie bowman
2006-Apr-02 04:02 UTC
[Rails] Re: my app broke this morning on with this error.
It must of been a dreamhost issue because the app started working again without my intervention. Joshua Schairbaum wrote:> Has anything changed with permissions or something with the > production.log file. It seems that it''s looking for that file and it''s > not there and not creating it. Another thought, complete stab in the > dark is checking enviroment.rb to see if something concerning logging > occured. > > I''m assuming this problem is solely because logging stopped working.-- Posted via http://www.ruby-forum.com/.