hi any one cn solve this problem
We’re sorry, but something went wrong.
We’ve been notified about this issue and we’ll take a look at it
shortly.
Is this for a Rails App?
Dev T. wrote:
hi any one cn solve this problem
We’re sorry, but something went wrong.
We’ve been notified about this issue and we’ll take a look at it
shortly.
We’re on it.
On Tue, Nov 17, 2009 at 12:30:47AM +0900, Aldric G. wrote:
We’re on it.
Should be fixed now. I just had to replace the Flux capacitor and get
the server up to 88 miles per hour.
Dev T. wrote:
We’re sorry, but something went wrong.
We’ve been notified about this issue and we’ll take a look at it
shortly.
Look in log/production.log for the error. If you want to be notified by
E-mail about such issues, install and configure the
exception_notification plugin.
But this is a Ruby list, not the Rails list. Please follow the links
from www.rubyonrails.com to find the Rails list.
Brian C. wrote:
Dev T. wrote:
We’re sorry, but something went wrong.
We’ve been notified about this issue and we’ll take a look at it
shortly.Look in log/production.log for the error. If you want to be notified by
E-mail about such issues, install and configure the
exception_notification plugin.But this is a Ruby list, not the Rails list. Please follow the links
from www.rubyonrails.com to find the Rails list.
thanx for ur suggesiton …but cn u just tell me wt is
acutically problem ???
and how i cn soleve it…
Kevin S. wrote:
Is this for a Rails App?
ya whn i type in the url "localhost:3000/admin "at that time
this error occour…
This error is by your own fault, ruby on rails have some strange errors
and
it has nothing to do with the “rails website” or something, get used to
it
or go to java lol.
Make sure all your gems are up to date, including the rails gem. If you
are
using sqlite for you db, check that gem as well. You may then need to
do a
clean up to get rid of old gem versions using the “gem cleanup” command.
After all that, try restarting your server.
On Mon, Nov 16, 2009 at 9:31 PM, Dev T. [email protected] wrote:
thanx for ur suggesiton …but cn u just tell me wt is
acutically problem ???
No, nobody can… because you haven’t given us any information
whatsoever.
and how i cn soleve it…
Look at the logs, figure out where the error is, and then ask the good
people of the Rails list for help.
Ben
Dev T. wrote:
i m not using Sqlite db…and gems are updated…any other
suggesition???/
Yes: it’s called “debugging”.
Rails displays that page when an uncaught exception has been raised in
your code. So your program has an error. You have to find and fix your
error.
Look in the log file (or on the screen if you’re using script/server to
start Rails) and you’ll see a detailed description of the error with a
full backtrace. This will show you the line with the error in it, a
description of the error, and the method call chain which ended up at
this point in the program. Correct the error, and try again.
If you run rails in development rather than production mode, the
exception will be displayed in the browser too.
If you want help with debugging on this (or any other) mailing list, at
the very minimum you’ll have to post the exception you get, and the
relevant lines of your program which the exception refers to.
Kevin S. wrote:
Make sure all your gems are up to date, including the rails gem. If you
are
using sqlite for you db, check that gem as well. You may then need to
do a
clean up to get rid of old gem versions using the “gem cleanup” command.
After all that, try restarting your server.
=================
i m not using Sqlite db…and gems are updated…any other
suggesition???/
Brian C. wrote:
Dev T. wrote:
i m not using Sqlite db…and gems are updated…any other
suggesition???/Yes: it’s called “debugging”.
Rails displays that page when an uncaught exception has been raised in
your code. So your program has an error. You have to find and fix your
error.Look in the log file (or on the screen if you’re using script/server to
start Rails) and you’ll see a detailed description of the error with a
full backtrace. This will show you the line with the error in it, a
description of the error, and the method call chain which ended up at
this point in the program. Correct the error, and try again.If you run rails in development rather than production mode, the
exception will be displayed in the browser too.If you want help with debugging on this (or any other) mailing list, at
the very minimum you’ll have to post the exception you get, and the
relevant lines of your program which the exception refers to.
ok…
this problem occour when i run with …ruby scrit/server
wy this problem come …give me ur idea!!!
/!\ FAILSAFE /!\ Wed Nov 18 10:07:21 +0530 2009
Status: 500 Internal Server Error
no such file to load – sqlite3
/usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
gem_original_require' /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:inrequire’
/usr/lib64/ruby/gems/1.8/gems/activesupport-2.3.4/lib/active_support/dependencies.rb:156:in
require' /usr/lib64/ruby/gems/1.8/gems/activesupport-2.3.4/lib/active_support/dependencies.rb:521:innew_constants_in’
/usr/lib64/ruby/gems/1.8/gems/activesupport-2.3.4/lib/active_support/dependencies.rb:156:in
require' /usr/lib64/ruby/gems/1.8/gems/activesupport-2.3.4/lib/active_support/core_ext/kernel/requires.rb:7:inrequire_library_or_gem’
/usr/lib64/ruby/gems/1.8/gems/activesupport-2.3.4/lib/active_support/core_ext/kernel/reporting.rb:11:in
silence_warnings' /usr/lib64/ruby/gems/1.8/gems/activesupport-2.3.4/lib/active_support/core_ext/kernel/requires.rb:5:inrequire_library_or_gem’
/usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.4/lib/active_record/connection_adapters/sqlite3_adapter.rb:10:in
sqlite3_connection' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.4/lib/active_record/connection_adapters/abstract/connection_pool.rb:223:insend’
/usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.4/lib/active_record/connection_adapters/abstract/connection_pool.rb:223:in
new_connection' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.4/lib/active_record/connection_adapters/abstract/connection_pool.rb:245:incheckout_new_connection’
/usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.4/lib/active_record/connection_adapters/abstract/connection_pool.rb:188:in
checkout' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.4/lib/active_record/connection_adapters/abstract/connection_pool.rb:184:inloop’
/usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.4/lib/active_record/connection_adapters/abstract/connection_pool.rb:184:in
checkout' /usr/lib/ruby/1.8/monitor.rb:242:insynchronize’
/usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.4/lib/active_record/connection_adapters/abstract/connection_pool.rb:183:in
checkout' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.4/lib/active_record/connection_adapters/abstract/connection_pool.rb:98:inconnection’
/usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.4/lib/active_record/connection_adapters/abstract/connection_pool.rb:326:in
retrieve_connection' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.4/lib/active_record/connection_adapters/abstract/connection_specification.rb:123:inretrieve_connection’
/usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.4/lib/active_record/connection_adapters/abstract/connection_specification.rb:115:in
connection' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.4/lib/active_record/query_cache.rb:9:incache’
/usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.4/lib/active_record/query_cache.rb:28:in
call' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.4/lib/active_record/connection_adapters/abstract/connection_pool.rb:361:incall’
/usr/lib64/ruby/gems/1.8/gems/rack-1.0.1/lib/rack/head.rb:9:in
call' /usr/lib64/ruby/gems/1.8/gems/rack-1.0.1/lib/rack/methodoverride.rb:24:incall’
/usr/lib64/ruby/gems/1.8/gems/actionpack-2.3.4/lib/action_controller/params_parser.rb:15:in
call' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.3.4/lib/action_controller/session/cookie_store.rb:93:incall’
/usr/lib64/ruby/gems/1.8/gems/actionpack-2.3.4/lib/action_controller/failsafe.rb:26:in
call' /usr/lib64/ruby/gems/1.8/gems/rack-1.0.1/lib/rack/lock.rb:11:incall’
/usr/lib64/ruby/gems/1.8/gems/rack-1.0.1/lib/rack/lock.rb:11:in
synchronize' /usr/lib64/ruby/gems/1.8/gems/rack-1.0.1/lib/rack/lock.rb:11:incall’
/usr/lib64/ruby/gems/1.8/gems/actionpack-2.3.4/lib/action_controller/dispatcher.rb:114:in
call' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.3.4/lib/action_controller/reloader.rb:34:inrun’
/usr/lib64/ruby/gems/1.8/gems/actionpack-2.3.4/lib/action_controller/dispatcher.rb:108:in
call' /usr/lib64/ruby/gems/1.8/gems/rails-2.3.4/lib/rails/rack/static.rb:31:incall’
/usr/lib64/ruby/gems/1.8/gems/rack-1.0.1/lib/rack/urlmap.rb:46:in
call' /usr/lib64/ruby/gems/1.8/gems/rack-1.0.1/lib/rack/urlmap.rb:40:ineach’
/usr/lib64/ruby/gems/1.8/gems/rack-1.0.1/lib/rack/urlmap.rb:40:in
call' /usr/lib64/ruby/gems/1.8/gems/rails-2.3.4/lib/rails/rack/log_tailer.rb:17:incall’
/usr/lib64/ruby/gems/1.8/gems/rack-1.0.1/lib/rack/content_length.rb:13:in
call' /usr/lib64/ruby/gems/1.8/gems/rack-1.0.1/lib/rack/handler/webrick.rb:50:inservice’
/usr/lib/ruby/1.8/webrick/httpserver.rb:104:in service' /usr/lib/ruby/1.8/webrick/httpserver.rb:65:inrun’
/usr/lib/ruby/1.8/webrick/server.rb:173:in start_thread' /usr/lib/ruby/1.8/webrick/server.rb:162:instart’
/usr/lib/ruby/1.8/webrick/server.rb:162:in start_thread' /usr/lib/ruby/1.8/webrick/server.rb:95:instart’
/usr/lib/ruby/1.8/webrick/server.rb:92:in each' /usr/lib/ruby/1.8/webrick/server.rb:92:instart’
/usr/lib/ruby/1.8/webrick/server.rb:23:in start' /usr/lib/ruby/1.8/webrick/server.rb:82:instart’
/usr/lib64/ruby/gems/1.8/gems/rack-1.0.1/lib/rack/handler/webrick.rb:14:in
run' /usr/lib64/ruby/gems/1.8/gems/rails-2.3.4/lib/commands/server.rb:111 /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:ingem_original_require’
/usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
`require’
script/server:3
On 2009-11-18, Dev T. [email protected] wrote:
this problem occour when i run with …ruby scrit/server
wy this problem come …give me ur idea!!!
Okay.
Ideas:
- Using multiple exclamation points is, at best, going to make people
think you’re an idiot. Especially combined with horrible misspellings
like “wy” and “ur”. - But thinking you’re an idiot is probably preferable to them thinking
you’re an arrogant jerk with an entitlement complex who feels authorized
to demand that they devote time to solving your problem. - You need to read this:
How To Ask Questions The Smart Way
Basically, when you do a poor job of asking questions, you lead us to
suspect
that time spent answering you will be wasted. If you do clever things
like
misspell the name of the command you ran (hint: you did this), that
makes
it seem like it will be useless to debug your code. Why bother? Your
problem
is probably going to turn out to be that you typed something incorrectly
because you’re not bothering to pay attention. Even if it’s not, the
lack
of care and attention still comes across as some combination of
“arrogant”
and “lazy” – and there is no good combination of these.
Status: 500 Internal Server Error
no such file to load – sqlite3
/usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
`gem_original_require’
Maybe you don’t have sqlite3 installed.
Since you’re so friendly, and I’m bored, I’ll explain how I figured this
out:
- I read the VERY FIRST MESSAGE.
- Using my advanced knowledge of third grade English, I understood the
words in that message.
“no such file to load – sqlite3”.
Well, gee. That sounds like it could not find a file “sqlite3” which it
tried to load. Maybe that file is missing, hmm?
If you can’t be bothered to do even that much thinking, it is probably
a waste of for us to try to “help” you.
-s
Dev T. wrote:
this problem occour when i run with …ruby scrit/server
Use this : ruby script/serverwy this problem come …give me ur idea!!!
Maybe you meant ‘wx’ which is for graphical widgets. Here’s my idea :
what is essential is invisible to the eyes. It is only with the heart
that one can see rightly.
/!\ FAILSAFE /!\ Wed Nov 18 10:07:21 +0530 2009
Status: 500 Internal Server Error
no such file to load – sqlite3
Why are you bothering people in the Ruby on Rails forum AND this forum?
Your behavior is obnoxious, especially since the people in the RoR forum
are helping you.
Rails displays that page when an uncaught exception has been raised
description of the error, and the method call chain which ended up atok…
this problem occour when i run with …ruby scrit/server
wy this problem come …give me ur idea!!!
/!\ FAILSAFE /!\ Wed Nov 18 10:07:21 +0530 2009
Status: 500 Internal Server Error
no such file to load – sqlite3
It’s all in that line right there ^^^^^