Re: ArgumentError when starting Unicorn on Heroku
Might I suggest using foreman locally for better dev/prod parity? Mark On May 26, 2013, at 8:43 AM, Jack R-G wrote: > Hi Guys, > > Thanks for the advice. Turned out the problem was in my Procfile. I had > "web: bundle exec unicorn start -p $PORT -c ./config/unicorn.rb" which is of > course incorrect - needed to remove the "start". And of course, the Procfile > was not in use in my development system so that explains why it worked there. > > Just to chronicle my adventures, once I found and fixed that problem, it then > ran, but all the workers immediately exited with status code "1", so the > master would continually start workers only to have them immediately exit. > After some playing around, I removed the "preload_app = true" command and the > workers started normally. So I think the problem was the amount of memory > consumed when preloading the entire app (fortunately, large portions of the > app are only used by the background worker, so they don't need to load at > all). So now we come to my next question: does anyone know a technique for > preloading **parts** of the application. I imagine that I could use some of > the techniques involved in thread safety to pre-load the rails framework. > But what's the best way to preload all the models? > > -- > -- > You received this message because you are subscribed to the Google > Groups "Heroku" group. > > To unsubscribe from this group, send email to > heroku+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/heroku?hl=en_US?hl=en > > --- > You received this message because you are subscribed to the Google Groups > "Heroku Community" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to heroku+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > > -- -- You received this message because you are subscribed to the Google Groups "Heroku" group. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en --- You received this message because you are subscribed to the Google Groups "Heroku Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: ArgumentError when starting Unicorn on Heroku
Hi Guys, Thanks for the advice. Turned out the problem was in my Procfile. I had "web: bundle exec unicorn start -p $PORT -c ./config/unicorn.rb" which is of course incorrect - needed to remove the "start". And of course, the Procfile was not in use in my development system so that explains why it worked there. Just to chronicle my adventures, once I found and fixed that problem, it then ran, but all the workers immediately exited with status code "1", so the master would continually start workers only to have them immediately exit. After some playing around, I removed the "preload_app = true" command and the workers started normally. So I think the problem was the amount of memory consumed when preloading the entire app (fortunately, large portions of the app are only used by the background worker, so they don't need to load at all). So now we come to my next question: does anyone know a technique for preloading **parts** of the application. I imagine that I could use some of the techniques involved in thread safety to pre-load the rails framework. But what's the best way to preload all the models? -- -- You received this message because you are subscribed to the Google Groups "Heroku" group. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en --- You received this message because you are subscribed to the Google Groups "Heroku Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: ArgumentError when starting Unicorn on Heroku
Does that command run locally "as is"? It's likely that you have a global
unicorn in /etc/init.d or something like that which supports those "start"
commands (like this one: https://gist.github.com/jaygooby/504875). Unicorn
by itself takes port and config via -p and -c. See the example in Procfile
here: https://devcenter.heroku.com/articles/rails-unicorn
Hope this helps.
On Sat, May 25, 2013 at 7:18 PM, Daniel Farina wrote:
> On Sat, May 25, 2013 at 2:33 AM, Jack Royal-Gordon
> wrote:
> > Switched my RoR (3.1.3, 1.9.2, Cedar Platform) app from Thin to Unicorn
> (4.6.2). It ran fine in development (Mac OSX), but when deploying to
> production on Heroku, it fails with the following messages:
> >
> > Starting process with command `bundle exec unicorn start -p 6069 -c
> ./config/unicorn.rb`
> >
> /app/vendor/bundle/ruby/1.9.1/gems/unicorn-4.6.2/lib/unicorn/configurator.rb:634:in
> `parse_rackup_file': rackup file (start) not readable (ArgumentError)
> > from
> /app/vendor/bundle/ruby/1.9.1/gems/unicorn-4.6.2/lib/unicorn/configurator.rb:77:in
> `reload'
> > from
> /app/vendor/bundle/ruby/1.9.1/gems/unicorn-4.6.2/lib/unicorn/configurator.rb:68:in
> `initialize'
> > from
> /app/vendor/bundle/ruby/1.9.1/gems/unicorn-4.6.2/lib/unicorn/http_server.rb:108:in
> `new'
> > from
> /app/vendor/bundle/ruby/1.9.1/gems/unicorn-4.6.2/lib/unicorn/http_server.rb:108:in
> `initialize'
> > from
> /app/vendor/bundle/ruby/1.9.1/gems/unicorn-4.6.2/bin/unicorn:126:in `new'
> > from
> /app/vendor/bundle/ruby/1.9.1/gems/unicorn-4.6.2/bin/unicorn:126:in ` (required)>'
> > from /app/vendor/bundle/ruby/1.9.1/bin/unicorn:19:in `load'
> > from /app/vendor/bundle/ruby/1.9.1/bin/unicorn:19:in `'
> > Process exited with status 1
> > State changed from starting to crashed
> >
> > config.ru:
> > require ::File.expand_path('../config/environment', __FILE__)
> > run NoveltyStats::Application
> >
> >
> > Procfile:
> > web: bundle exec unicorn start -p $PORT -c ./config/unicorn.rb
> > sidekiq: bundle exec sidekiq -c 10
> >
> > unicorn.rb:
> > worker_processes Integer(ENV["WEB_CONCURRENCY"] || 3)
> > timeout 15
> > preload_app true
> >
> > before_fork do |server, worker|
> >
> > Signal.trap 'TERM' do
> > puts 'Unicorn master intercepting TERM and sending myself QUIT
> instead'
> > Process.kill 'QUIT', Process.pid
> > end
> >
> > defined?(ActiveRecord::Base) and
> > ActiveRecord::Base.connection.disconnect!
> > end
> >
> > after_fork do |server, worker|
> >
> > Signal.trap 'TERM' do
> > puts 'Unicorn worker intercepting TERM and doing nothing. Wait
> for master to sent QUIT'
> > end
> >
> > defined?(ActiveRecord::Base) and
> > ActiveRecord::Base.establish_connection
> > end
> >
> > I have no idea where to even begin to troubleshoot this problem. Any
> thoughts?
>
> Well that sounds pretty bizarre. The way I'd go about solving this
> would be to us 'heroku run bash' and start poking around. Although
> the error message you see above can have multiple causes (says the
> web, I just ran some searching), the gist of your problem sounds like
> it could have to do with paths that may be different between Heroku
> and your personal computer (although there can be numerous other
> causes).
>
> --
> --
> You received this message because you are subscribed to the Google
> Groups "Heroku" group.
>
> To unsubscribe from this group, send email to
> heroku+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/heroku?hl=en_US?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Heroku Community" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to heroku+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>
--
dB. | Moscow - Geneva - Seattle - New York
dblock.org <http://www.dblock.org> -
@dblockdotorg<http://twitter.com/#!/dblockdotorg> -
artsy.net
--
--
You received this message because you are subscribed to the Google
Groups "Heroku" group.
To unsubscribe from this group, send email to
heroku+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/heroku?hl=en_US?hl=en
---
You received this message because you are subscribed to the Google Groups
"Heroku Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to heroku+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: ArgumentError when starting Unicorn on Heroku
On Sat, May 25, 2013 at 2:33 AM, Jack Royal-Gordon wrote:
> Switched my RoR (3.1.3, 1.9.2, Cedar Platform) app from Thin to Unicorn
> (4.6.2). It ran fine in development (Mac OSX), but when deploying to
> production on Heroku, it fails with the following messages:
>
> Starting process with command `bundle exec unicorn start -p 6069 -c
> ./config/unicorn.rb`
>
> /app/vendor/bundle/ruby/1.9.1/gems/unicorn-4.6.2/lib/unicorn/configurator.rb:634:in
> `parse_rackup_file': rackup file (start) not readable (ArgumentError)
> from
> /app/vendor/bundle/ruby/1.9.1/gems/unicorn-4.6.2/lib/unicorn/configurator.rb:77:in
> `reload'
> from
> /app/vendor/bundle/ruby/1.9.1/gems/unicorn-4.6.2/lib/unicorn/configurator.rb:68:in
> `initialize'
> from
> /app/vendor/bundle/ruby/1.9.1/gems/unicorn-4.6.2/lib/unicorn/http_server.rb:108:in
> `new'
> from
> /app/vendor/bundle/ruby/1.9.1/gems/unicorn-4.6.2/lib/unicorn/http_server.rb:108:in
> `initialize'
> from /app/vendor/bundle/ruby/1.9.1/gems/unicorn-4.6.2/bin/unicorn:126:in
> `new'
> from /app/vendor/bundle/ruby/1.9.1/gems/unicorn-4.6.2/bin/unicorn:126:in
> `'
> from /app/vendor/bundle/ruby/1.9.1/bin/unicorn:19:in `load'
> from /app/vendor/bundle/ruby/1.9.1/bin/unicorn:19:in `'
> Process exited with status 1
> State changed from starting to crashed
>
> config.ru:
> require ::File.expand_path('../config/environment', __FILE__)
> run NoveltyStats::Application
>
>
> Procfile:
> web: bundle exec unicorn start -p $PORT -c ./config/unicorn.rb
> sidekiq: bundle exec sidekiq -c 10
>
> unicorn.rb:
> worker_processes Integer(ENV["WEB_CONCURRENCY"] || 3)
> timeout 15
> preload_app true
>
> before_fork do |server, worker|
>
> Signal.trap 'TERM' do
> puts 'Unicorn master intercepting TERM and sending myself QUIT
> instead'
> Process.kill 'QUIT', Process.pid
> end
>
> defined?(ActiveRecord::Base) and
> ActiveRecord::Base.connection.disconnect!
> end
>
> after_fork do |server, worker|
>
> Signal.trap 'TERM' do
> puts 'Unicorn worker intercepting TERM and doing nothing. Wait for
> master to sent QUIT'
> end
>
> defined?(ActiveRecord::Base) and
> ActiveRecord::Base.establish_connection
> end
>
> I have no idea where to even begin to troubleshoot this problem. Any
> thoughts?
Well that sounds pretty bizarre. The way I'd go about solving this
would be to us 'heroku run bash' and start poking around. Although
the error message you see above can have multiple causes (says the
web, I just ran some searching), the gist of your problem sounds like
it could have to do with paths that may be different between Heroku
and your personal computer (although there can be numerous other
causes).
--
--
You received this message because you are subscribed to the Google
Groups "Heroku" group.
To unsubscribe from this group, send email to
heroku+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/heroku?hl=en_US?hl=en
---
You received this message because you are subscribed to the Google Groups
"Heroku Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to heroku+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
ArgumentError when starting Unicorn on Heroku
Switched my RoR (3.1.3, 1.9.2, Cedar Platform) app from Thin to Unicorn
(4.6.2). It ran fine in development (Mac OSX), but when deploying to
production on Heroku, it fails with the following messages:
Starting process with command `bundle exec unicorn start -p 6069 -c
./config/unicorn.rb`
/app/vendor/bundle/ruby/1.9.1/gems/unicorn-4.6.2/lib/unicorn/configurator.rb:634:in
`parse_rackup_file': rackup file (start) not readable (ArgumentError)
from
/app/vendor/bundle/ruby/1.9.1/gems/unicorn-4.6.2/lib/unicorn/configurator.rb:77:in
`reload'
from
/app/vendor/bundle/ruby/1.9.1/gems/unicorn-4.6.2/lib/unicorn/configurator.rb:68:in
`initialize'
from
/app/vendor/bundle/ruby/1.9.1/gems/unicorn-4.6.2/lib/unicorn/http_server.rb:108:in
`new'
from
/app/vendor/bundle/ruby/1.9.1/gems/unicorn-4.6.2/lib/unicorn/http_server.rb:108:in
`initialize'
from /app/vendor/bundle/ruby/1.9.1/gems/unicorn-4.6.2/bin/unicorn:126:in `new'
from /app/vendor/bundle/ruby/1.9.1/gems/unicorn-4.6.2/bin/unicorn:126:in
`'
from /app/vendor/bundle/ruby/1.9.1/bin/unicorn:19:in `load'
from /app/vendor/bundle/ruby/1.9.1/bin/unicorn:19:in `'
Process exited with status 1
State changed from starting to crashed
config.ru:
require ::File.expand_path('../config/environment', __FILE__)
run NoveltyStats::Application
Procfile:
web: bundle exec unicorn start -p $PORT -c ./config/unicorn.rb
sidekiq: bundle exec sidekiq -c 10
unicorn.rb:
worker_processes Integer(ENV["WEB_CONCURRENCY"] || 3)
timeout 15
preload_app true
before_fork do |server, worker|
Signal.trap 'TERM' do
puts 'Unicorn master intercepting TERM and sending myself QUIT instead'
Process.kill 'QUIT', Process.pid
end
defined?(ActiveRecord::Base) and
ActiveRecord::Base.connection.disconnect!
end
after_fork do |server, worker|
Signal.trap 'TERM' do
puts 'Unicorn worker intercepting TERM and doing nothing. Wait for
master to sent QUIT'
end
defined?(ActiveRecord::Base) and
ActiveRecord::Base.establish_connection
end
I have no idea where to even begin to troubleshoot this problem. Any thoughts?
--
--
You received this message because you are subscribed to the Google
Groups "Heroku" group.
To unsubscribe from this group, send email to
heroku+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/heroku?hl=en_US?hl=en
---
You received this message because you are subscribed to the Google Groups
"Heroku Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to heroku+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Malformed version number string mswin32 (ArgumentError)
Hey all... Problems with the way rails parses win32 gems I think. Found a workaround that has fixed locally. Had to change file --> vendor_gem_source_index.rb Getting: App failed to start An error happened during the initialization of your app. Partial Trace /usr/ruby1.8.7/lib/ruby/site_ruby/1.8/rubygems/version.rb:182:in `initialize': Malformed version number string mswin32 (ArgumentError) from /home/slugs/262237_5f6ad9f_de5f/mnt/.gems/gems/rails-2.3.4/lib/ rails/vendor_gem_source_index.rb:105:in `new' from /home/slugs/262237_5f6ad9f_de5f/mnt/.gems/gems/rails-2.3.4/lib/ rails/vendor_gem_source_index.rb:105:in `version_for_dir' from /home/slugs/262237_5f6ad9f_de5f/mnt/.gems/gems/rails-2.3.4/lib/ rails/vendor_gem_source_index.rb:47:in `refresh!' from /home/slugs/262237_5f6ad9f_de5f/mnt/.gems/gems/rails-2.3.4/lib/ rails/vendor_gem_source_index.rb:45:in `each' from /home/slugs/262237_5f6ad9f_de5f/mnt/.gems/gems/rails-2.3.4/lib/ rails/vendor_gem_source_index.rb:45:in `refresh!' from /home/slugs/262237_5f6ad9f_de5f/mnt/.gems/gems/rails-2.3.4/lib/ rails/vendor_gem_source_index.rb:29:in `initialize' I have used this workaround: (3rd post) http://groups.google.com/group/rubyonrails-talk/browse_thread/thread/2af3c2930bfb4bce also reference: https://rails.lighthouseapp.com/projects/8994/tickets/4295-rails-incorrectly-imposes-version-number-as-last-part-of-gem-directory-name - This workaround was done on my local machine. I don't believe I can change these files on Heroku? Is there any way to get my app up and running? Would love to deploy this app to Heroku as paid account. Thanks Shawn Lindsey -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: ArgumentError
Ah. Never mind. Turns out I overrode the method hash, which AR uses internally. D'oh! On Jun 2, 6:56 pm, Fat Lotus <[EMAIL PROTECTED]> wrote: > Hmmm... The app is jaggedhills2.heroku.com, and access is now public. > I'd wonder if perhaps it could be some sort of ActiveRecord problem? I > think that Heroku uses 2.0.2 AR, with the newest release being 2.1.0. > Wish I could figure out how to update gems... > > On Jun 2, 6:19 pm, justindz <[EMAIL PROTECTED]> wrote: > > > I was getting this for a while, but sadly I can't remember what I did > > to resolve the problem. Seeing as you're having the problem as > > Mongrel is loading, you might check any custom declarations in your > > environment files that might take arguments (even of the form "method > > argument, argument" that don't look as methody) to make sure you > > didn't omit anything there. Also, on any files you've recently edited > > just double check the syntax to make sure you don't have like a > > before_filter or something that's short on an arg. > > > Sorry. Thems be all I gots. > > > On Jun 2, 6:56 pm, Fat Lotus <[EMAIL PROTECTED]> wrote: > > > > Sorry, left out a detail. > > > > Here's the full trace: > > > /usr/lib/ruby/gems/1.8/gems/activerecord-2.0.2/lib/active_record/ > > > base.rb:1708:in `hash' > > > /usr/lib/ruby/gems/1.8/gems/activerecord-2.0.2/lib/active_record/ > > > base.rb:1708:in `[]' > > > /usr/lib/ruby/gems/1.8/gems/activerecord-2.0.2/lib/active_record/ > > > base.rb:1708:in `subclasses' > > > /usr/lib/ruby/gems/1.8/gems/activerecord-2.0.2/lib/active_record/ > > > base.rb:1709:in `subclasses' > > > /usr/lib/ruby/gems/1.8/gems/activesupport-2.0.2/lib/active_support/ > > > inflector.rb:257:in `inject' > > > /usr/lib/ruby/gems/1.8/gems/activerecord-2.0.2/lib/active_record/ > > > base.rb:1709:in `each' > > > /usr/lib/ruby/gems/1.8/gems/activerecord-2.0.2/lib/active_record/ > > > base.rb:1709:in `inject' > > > /usr/lib/ruby/gems/1.8/gems/activerecord-2.0.2/lib/active_record/ > > > base.rb:1709:in `subclasses' > > > /usr/lib/ruby/gems/1.8/gems/activerecord-2.0.2/lib/active_record/ > > > base.rb:366:in `reset_subclasses' > > > /usr/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/ > > > dispatcher.rb:158:in `cleanup_application' > > > /usr/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/ > > > dispatcher.rb:178:in `send!' > > > [...] > > > > None of it is actually inside my app. It goes all the way back to the > > > mongrel initializer... > > > > On Jun 1, 1:41 pm, Kevin Triplett <[EMAIL PROTECTED]> wrote: > > > > > Hi! > > > > > The "login" method in your users_controller.rb file must be > > > > taking an argument? It's complaining that login is defined > > > > as taking one argument but it's being called without any > > > > arguments. > > > > > If login is an action method (:action => 'login'), then > > > > there are no arguments passed to it. You can just refer to > > > > the params variable to get the data passed to your > > > > controller from the browser. > > > > > Hope this helps, I may be way off base on what's REALLy > > > > causes the error. :) > > > > > Kevin > > > > > Fat Lotus wrote: > > > > > Hello all. I've just been having trouble with strange ArgumentErrors > > > > > popping up at the bottom of every response. This can be seen on the > > > > > app at jaggedhills2.heroku.com/users/test. > > > > > > Here's what code is generated: > > > > > > > > > >www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> > > > > > http://www.w3.org/1999/xhtml";> > > > > > [ Normal page content ] > > > > > > > > > > > > > > > Action Controller: Exception caught > > > > > > [...] > > > > > > > > > > > ArgumentError > > > > > > in UsersController#login > > > > > > > > > > > wrong number of arguments (0 for 1) > > > > > > RAILS_ROOT: /mnt/home/userapps/19146 > > > > > > [...] > > > > > > /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.4/lib/mongrel.rb:268:in > > > > > `initialize' > > > > > /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.4/lib/mongrel.rb:268:in `new' > > > > > /usr/lib/ruby/gems/1.8/gems/mongr --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to heroku@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~--~~~~--~~--~--~---
Re: ArgumentError
Hmmm... The app is jaggedhills2.heroku.com, and access is now public. I'd wonder if perhaps it could be some sort of ActiveRecord problem? I think that Heroku uses 2.0.2 AR, with the newest release being 2.1.0. Wish I could figure out how to update gems... On Jun 2, 6:19 pm, justindz <[EMAIL PROTECTED]> wrote: > I was getting this for a while, but sadly I can't remember what I did > to resolve the problem. Seeing as you're having the problem as > Mongrel is loading, you might check any custom declarations in your > environment files that might take arguments (even of the form "method > argument, argument" that don't look as methody) to make sure you > didn't omit anything there. Also, on any files you've recently edited > just double check the syntax to make sure you don't have like a > before_filter or something that's short on an arg. > > Sorry. Thems be all I gots. > > On Jun 2, 6:56 pm, Fat Lotus <[EMAIL PROTECTED]> wrote: > > > Sorry, left out a detail. > > > Here's the full trace: > > /usr/lib/ruby/gems/1.8/gems/activerecord-2.0.2/lib/active_record/ > > base.rb:1708:in `hash' > > /usr/lib/ruby/gems/1.8/gems/activerecord-2.0.2/lib/active_record/ > > base.rb:1708:in `[]' > > /usr/lib/ruby/gems/1.8/gems/activerecord-2.0.2/lib/active_record/ > > base.rb:1708:in `subclasses' > > /usr/lib/ruby/gems/1.8/gems/activerecord-2.0.2/lib/active_record/ > > base.rb:1709:in `subclasses' > > /usr/lib/ruby/gems/1.8/gems/activesupport-2.0.2/lib/active_support/ > > inflector.rb:257:in `inject' > > /usr/lib/ruby/gems/1.8/gems/activerecord-2.0.2/lib/active_record/ > > base.rb:1709:in `each' > > /usr/lib/ruby/gems/1.8/gems/activerecord-2.0.2/lib/active_record/ > > base.rb:1709:in `inject' > > /usr/lib/ruby/gems/1.8/gems/activerecord-2.0.2/lib/active_record/ > > base.rb:1709:in `subclasses' > > /usr/lib/ruby/gems/1.8/gems/activerecord-2.0.2/lib/active_record/ > > base.rb:366:in `reset_subclasses' > > /usr/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/ > > dispatcher.rb:158:in `cleanup_application' > > /usr/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/ > > dispatcher.rb:178:in `send!' > > [...] > > > None of it is actually inside my app. It goes all the way back to the > > mongrel initializer... > > > On Jun 1, 1:41 pm, Kevin Triplett <[EMAIL PROTECTED]> wrote: > > > > Hi! > > > > The "login" method in your users_controller.rb file must be > > > taking an argument? It's complaining that login is defined > > > as taking one argument but it's being called without any > > > arguments. > > > > If login is an action method (:action => 'login'), then > > > there are no arguments passed to it. You can just refer to > > > the params variable to get the data passed to your > > > controller from the browser. > > > > Hope this helps, I may be way off base on what's REALLy > > > causes the error. :) > > > > Kevin > > > > Fat Lotus wrote: > > > > Hello all. I've just been having trouble with strange ArgumentErrors > > > > popping up at the bottom of every response. This can be seen on the > > > > app at jaggedhills2.heroku.com/users/test. > > > > > Here's what code is generated: > > > > > > > >www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> > > > > http://www.w3.org/1999/xhtml";> > > > > [ Normal page content ] > > > > > > > > > > > > Action Controller: Exception caught > > > > > [...] > > > > > > > > > ArgumentError > > > > > in UsersController#login > > > > > > > > > wrong number of arguments (0 for 1) > > > > > RAILS_ROOT: /mnt/home/userapps/19146 > > > > > [...] > > > > > /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.4/lib/mongrel.rb:268:in > > > > `initialize' > > > > /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.4/lib/mongrel.rb:268:in `new' > > > > /usr/lib/ruby/gems/1.8/gems/mongr --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to heroku@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~--~~~~--~~--~--~---
Re: ArgumentError
I was getting this for a while, but sadly I can't remember what I did to resolve the problem. Seeing as you're having the problem as Mongrel is loading, you might check any custom declarations in your environment files that might take arguments (even of the form "method argument, argument" that don't look as methody) to make sure you didn't omit anything there. Also, on any files you've recently edited just double check the syntax to make sure you don't have like a before_filter or something that's short on an arg. Sorry. Thems be all I gots. On Jun 2, 6:56 pm, Fat Lotus <[EMAIL PROTECTED]> wrote: > Sorry, left out a detail. > > Here's the full trace: > /usr/lib/ruby/gems/1.8/gems/activerecord-2.0.2/lib/active_record/ > base.rb:1708:in `hash' > /usr/lib/ruby/gems/1.8/gems/activerecord-2.0.2/lib/active_record/ > base.rb:1708:in `[]' > /usr/lib/ruby/gems/1.8/gems/activerecord-2.0.2/lib/active_record/ > base.rb:1708:in `subclasses' > /usr/lib/ruby/gems/1.8/gems/activerecord-2.0.2/lib/active_record/ > base.rb:1709:in `subclasses' > /usr/lib/ruby/gems/1.8/gems/activesupport-2.0.2/lib/active_support/ > inflector.rb:257:in `inject' > /usr/lib/ruby/gems/1.8/gems/activerecord-2.0.2/lib/active_record/ > base.rb:1709:in `each' > /usr/lib/ruby/gems/1.8/gems/activerecord-2.0.2/lib/active_record/ > base.rb:1709:in `inject' > /usr/lib/ruby/gems/1.8/gems/activerecord-2.0.2/lib/active_record/ > base.rb:1709:in `subclasses' > /usr/lib/ruby/gems/1.8/gems/activerecord-2.0.2/lib/active_record/ > base.rb:366:in `reset_subclasses' > /usr/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/ > dispatcher.rb:158:in `cleanup_application' > /usr/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/ > dispatcher.rb:178:in `send!' > [...] > > None of it is actually inside my app. It goes all the way back to the > mongrel initializer... > > On Jun 1, 1:41 pm, Kevin Triplett <[EMAIL PROTECTED]> wrote: > > > Hi! > > > The "login" method in your users_controller.rb file must be > > taking an argument? It's complaining that login is defined > > as taking one argument but it's being called without any > > arguments. > > > If login is an action method (:action => 'login'), then > > there are no arguments passed to it. You can just refer to > > the params variable to get the data passed to your > > controller from the browser. > > > Hope this helps, I may be way off base on what's REALLy > > causes the error. :) > > > Kevin > > > Fat Lotus wrote: > > > Hello all. I've just been having trouble with strange ArgumentErrors > > > popping up at the bottom of every response. This can be seen on the > > > app at jaggedhills2.heroku.com/users/test. > > > > Here's what code is generated: > > > > > >www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> > > > http://www.w3.org/1999/xhtml";> > > > [ Normal page content ] > > > > > > > > > Action Controller: Exception caught > > > > [...] > > > > > > > ArgumentError > > > > in UsersController#login > > > > > > > wrong number of arguments (0 for 1) > > > > RAILS_ROOT: /mnt/home/userapps/19146 > > > > [...] > > > > /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.4/lib/mongrel.rb:268:in > > > `initialize' > > > /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.4/lib/mongrel.rb:268:in `new' > > > /usr/lib/ruby/gems/1.8/gems/mongr --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to heroku@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~--~~~~--~~--~--~---
Re: ArgumentError
Sorry, left out a detail. Here's the full trace: /usr/lib/ruby/gems/1.8/gems/activerecord-2.0.2/lib/active_record/ base.rb:1708:in `hash' /usr/lib/ruby/gems/1.8/gems/activerecord-2.0.2/lib/active_record/ base.rb:1708:in `[]' /usr/lib/ruby/gems/1.8/gems/activerecord-2.0.2/lib/active_record/ base.rb:1708:in `subclasses' /usr/lib/ruby/gems/1.8/gems/activerecord-2.0.2/lib/active_record/ base.rb:1709:in `subclasses' /usr/lib/ruby/gems/1.8/gems/activesupport-2.0.2/lib/active_support/ inflector.rb:257:in `inject' /usr/lib/ruby/gems/1.8/gems/activerecord-2.0.2/lib/active_record/ base.rb:1709:in `each' /usr/lib/ruby/gems/1.8/gems/activerecord-2.0.2/lib/active_record/ base.rb:1709:in `inject' /usr/lib/ruby/gems/1.8/gems/activerecord-2.0.2/lib/active_record/ base.rb:1709:in `subclasses' /usr/lib/ruby/gems/1.8/gems/activerecord-2.0.2/lib/active_record/ base.rb:366:in `reset_subclasses' /usr/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/ dispatcher.rb:158:in `cleanup_application' /usr/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/ dispatcher.rb:178:in `send!' [...] None of it is actually inside my app. It goes all the way back to the mongrel initializer... On Jun 1, 1:41 pm, Kevin Triplett <[EMAIL PROTECTED]> wrote: > Hi! > > The "login" method in your users_controller.rb file must be > taking an argument? It's complaining that login is defined > as taking one argument but it's being called without any > arguments. > > If login is an action method (:action => 'login'), then > there are no arguments passed to it. You can just refer to > the params variable to get the data passed to your > controller from the browser. > > Hope this helps, I may be way off base on what's REALLy > causes the error. :) > > Kevin > > Fat Lotus wrote: > > Hello all. I've just been having trouble with strange ArgumentErrors > > popping up at the bottom of every response. This can be seen on the > > app at jaggedhills2.heroku.com/users/test. > > > Here's what code is generated: > > > >www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> > > http://www.w3.org/1999/xhtml";> > > [ Normal page content ] > > > > > > Action Controller: Exception caught > > > [...] > > > > > ArgumentError > > > in UsersController#login > > > > > wrong number of arguments (0 for 1) > > > RAILS_ROOT: /mnt/home/userapps/19146 > > > [...] > > > /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.4/lib/mongrel.rb:268:in > > `initialize' > > /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.4/lib/mongrel.rb:268:in `new' > > /usr/lib/ruby/gems/1.8/gems/mongr --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to heroku@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~--~~~~--~~--~--~---
Re: ArgumentError
Hi! The "login" method in your users_controller.rb file must be taking an argument? It's complaining that login is defined as taking one argument but it's being called without any arguments. If login is an action method (:action => 'login'), then there are no arguments passed to it. You can just refer to the params variable to get the data passed to your controller from the browser. Hope this helps, I may be way off base on what's REALLy causes the error. :) Kevin Fat Lotus wrote: > Hello all. I've just been having trouble with strange ArgumentErrors > popping up at the bottom of every response. This can be seen on the > app at jaggedhills2.heroku.com/users/test. > > Here's what code is generated: > > www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> > http://www.w3.org/1999/xhtml";> > [ Normal page content ] > > > Action Controller: Exception caught > > [...] > > > ArgumentError > > in UsersController#login > > > wrong number of arguments (0 for 1) > > > > RAILS_ROOT: /mnt/home/userapps/19146 > > [...] > > /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.4/lib/mongrel.rb:268:in > `initialize' > /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.4/lib/mongrel.rb:268:in `new' > /usr/lib/ruby/gems/1.8/gems/mongr > > --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to heroku@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~--~~~~--~~--~--~---
ArgumentError
Hello all. I've just been having trouble with strange ArgumentErrors popping up at the bottom of every response. This can be seen on the app at jaggedhills2.heroku.com/users/test. Here's what code is generated: http://www.w3.org/1999/xhtml";> [ Normal page content ] Action Controller: Exception caught [...] ArgumentError in UsersController#login wrong number of arguments (0 for 1) RAILS_ROOT: /mnt/home/userapps/19146 [...] /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.4/lib/mongrel.rb:268:in `initialize' /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.4/lib/mongrel.rb:268:in `new' /usr/lib/ruby/gems/1.8/gems/mongr --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to heroku@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~--~~~~--~~--~--~---
