unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
* unicorn failing to start
@ 2010-05-28  8:55 Stefan Maier
  2010-05-28 18:49 ` Eric Wong
  2010-06-07 13:37 ` Stephan Kaag
  0 siblings, 2 replies; 5+ messages in thread
From: Stefan Maier @ 2010-05-28  8:55 UTC (permalink / raw)
  To: mongrel-unicorn

Hi,

i'm trying to start up unicorn_rails with a rails 3 beta3 project. All I
can get out of it is this:
I, [2010-05-28T08:54:45.770957 #17852]  INFO -- : reaped
#<Process::Status: pid 17854 exit 1> worker=0
I, [2010-05-28T08:54:45.771200 #17852]  INFO -- : worker=0 spawning...
I, [2010-05-28T08:54:45.774049 #17858]  INFO -- : worker=0 spawned pid=17858
I, [2010-05-28T08:54:45.774350 #17858]  INFO -- : Refreshing Gem list

/usr/local/lib/ruby/gems/1.9.1/gems/activesupport-3.0.0.beta3/lib/active_support/deprecation/proxy_wrappers.rb:17:in
`new': wrong number of arguments (1 for 2) (ArgumentError)
	from
/usr/local/lib/ruby/gems/1.9.1/gems/activesupport-3.0.0.beta3/lib/active_support/deprecation/proxy_wrappers.rb:17:in
`method_missing'
	from
/usr/local/lib/ruby/gems/1.9.1/gems/rack-1.1.0/lib/rack/builder.rb:54:in
`block in use'
	from
/usr/local/lib/ruby/gems/1.9.1/gems/rack-1.1.0/lib/rack/builder.rb:73:in
`call'
	from
/usr/local/lib/ruby/gems/1.9.1/gems/rack-1.1.0/lib/rack/builder.rb:73:in
`block in to_app'
	from
/usr/local/lib/ruby/gems/1.9.1/gems/rack-1.1.0/lib/rack/builder.rb:73:in
`each'
	from
/usr/local/lib/ruby/gems/1.9.1/gems/rack-1.1.0/lib/rack/builder.rb:73:in
`inject'
	from
/usr/local/lib/ruby/gems/1.9.1/gems/rack-1.1.0/lib/rack/builder.rb:73:in
`to_app'
	from
/usr/local/lib/ruby/gems/1.9.1/gems/rack-1.1.0/lib/rack/builder.rb:63:in
`map'
	from
/usr/local/lib/ruby/gems/1.9.1/gems/rack-1.1.0/lib/rack/builder.rb:66:in
`map'
	from
/usr/local/lib/ruby/gems/1.9.1/gems/unicorn-0.99.0/bin/unicorn_rails:173:in
`block (2 levels) in rails_builder'
	from
/usr/local/lib/ruby/gems/1.9.1/gems/rack-1.1.0/lib/rack/builder.rb:46:in
`instance_eval'
	from
/usr/local/lib/ruby/gems/1.9.1/gems/rack-1.1.0/lib/rack/builder.rb:46:in
`initialize'
	from
/usr/local/lib/ruby/gems/1.9.1/gems/unicorn-0.99.0/bin/unicorn_rails:156:in
`new'
	from
/usr/local/lib/ruby/gems/1.9.1/gems/unicorn-0.99.0/bin/unicorn_rails:156:in
`block in rails_builder'
	from
/usr/local/lib/ruby/gems/1.9.1/gems/unicorn-0.99.0/lib/unicorn.rb:816:in
`call'
	from
/usr/local/lib/ruby/gems/1.9.1/gems/unicorn-0.99.0/lib/unicorn.rb:816:in
`build_app!'
	from
/usr/local/lib/ruby/gems/1.9.1/gems/unicorn-0.99.0/lib/unicorn.rb:673:in
`init_worker_process'
	from
/usr/local/lib/ruby/gems/1.9.1/gems/unicorn-0.99.0/lib/unicorn.rb:688:in
`worker_loop'
	from
/usr/local/lib/ruby/gems/1.9.1/gems/unicorn-0.99.0/lib/unicorn.rb:605:in
`block (2 levels) in spawn_missing_workers'
	from
/usr/local/lib/ruby/gems/1.9.1/gems/unicorn-0.99.0/lib/unicorn.rb:602:in
`fork'
	from
/usr/local/lib/ruby/gems/1.9.1/gems/unicorn-0.99.0/lib/unicorn.rb:602:in
`block in spawn_missing_workers'
	from
/usr/local/lib/ruby/gems/1.9.1/gems/unicorn-0.99.0/lib/unicorn.rb:598:in
`each'
	from
/usr/local/lib/ruby/gems/1.9.1/gems/unicorn-0.99.0/lib/unicorn.rb:598:in
`spawn_missing_workers'
	from
/usr/local/lib/ruby/gems/1.9.1/gems/unicorn-0.99.0/lib/unicorn.rb:612:in
`maintain_worker_count'
	from
/usr/local/lib/ruby/gems/1.9.1/gems/unicorn-0.99.0/lib/unicorn.rb:408:in
`block in join'
	from
/usr/local/lib/ruby/gems/1.9.1/gems/unicorn-0.99.0/lib/unicorn.rb:396:in
`loop'
	from
/usr/local/lib/ruby/gems/1.9.1/gems/unicorn-0.99.0/lib/unicorn.rb:396:in
`join'
	from
/usr/local/lib/ruby/gems/1.9.1/gems/unicorn-0.99.0/lib/unicorn.rb:28:in
`run'
	from
/usr/local/lib/ruby/gems/1.9.1/gems/unicorn-0.99.0/bin/unicorn_rails:203:in
`<top (required)>'
	from /usr/local/bin/unicorn_rails:19:in `load'
	from /usr/local/bin/unicorn_rails:19:in `<main>'
I, [2010-05-28T08:54:49.301901 #17852]  INFO -- : reaped
#<Process::Status: pid 17858 exit 1> worker=0
I, [2010-05-28T08:54:49.302066 #17852]  INFO -- : master complete

Any ideas what's wrong?

Thanks,
Stefan Maier
_______________________________________________
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do not quote signatures (like this one) or top post when replying


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: unicorn failing to start
  2010-05-28  8:55 unicorn failing to start Stefan Maier
@ 2010-05-28 18:49 ` Eric Wong
  2010-05-28 19:19   ` Stefan Maier
  2010-06-07 13:37 ` Stephan Kaag
  1 sibling, 1 reply; 5+ messages in thread
From: Eric Wong @ 2010-05-28 18:49 UTC (permalink / raw)
  To: unicorn list; +Cc: Stefan Maier

Stefan Maier <stefanmaier@gmail.com> wrote:
> Hi,
> 
> i'm trying to start up unicorn_rails with a rails 3 beta3 project. All I
> can get out of it is this:
> I, [2010-05-28T08:54:45.770957 #17852]  INFO -- : reaped
> #<Process::Status: pid 17854 exit 1> worker=0
> I, [2010-05-28T08:54:45.771200 #17852]  INFO -- : worker=0 spawning...
> I, [2010-05-28T08:54:45.774049 #17858]  INFO -- : worker=0 spawned pid=17858
> I, [2010-05-28T08:54:45.774350 #17858]  INFO -- : Refreshing Gem list
> 
> /usr/local/lib/ruby/gems/1.9.1/gems/activesupport-3.0.0.beta3/lib/active_support/deprecation/proxy_wrappers.rb:17:in
> `new': wrong number of arguments (1 for 2) (ArgumentError)
> 	from
> /usr/local/lib/ruby/gems/1.9.1/gems/activesupport-3.0.0.beta3/lib/active_support/deprecation/proxy_wrappers.rb:17:in
> `method_missing'

<snip>

> Any ideas what's wrong?

Hi Stephan,

I've heard (but not confirmed myself) Rails 3 doesn't work well with
Ruby 1.9.1, but does with 1.9.2dev (trunk), and 1.8.7.  Can you give
either of those versions of Ruby a try?

Another thing that's probably not the issue here, but since config.ru is
present, give "unicorn" a shot instead of "unicorn_rails" as the latter
hasn't been tested heavily with Rails 3.  "unicorn_rails" was designed
with older Rails in mind.

Let us know what you find, thanks!

-- 
Eric Wong
_______________________________________________
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do not quote signatures (like this one) or top post when replying


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: unicorn failing to start
  2010-05-28 18:49 ` Eric Wong
@ 2010-05-28 19:19   ` Stefan Maier
  0 siblings, 0 replies; 5+ messages in thread
From: Stefan Maier @ 2010-05-28 19:19 UTC (permalink / raw)
  To: unicorn list

Am 28.05.10 20:49, schrieb Eric Wong:
> Stefan Maier <stefanmaier@gmail.com> wrote:
>> Hi,
>>
>> i'm trying to start up unicorn_rails with a rails 3 beta3 project. All I
>> can get out of it is this:
>> I, [2010-05-28T08:54:45.770957 #17852]  INFO -- : reaped
>> #<Process::Status: pid 17854 exit 1> worker=0
>> I, [2010-05-28T08:54:45.771200 #17852]  INFO -- : worker=0 spawning...
>> I, [2010-05-28T08:54:45.774049 #17858]  INFO -- : worker=0 spawned pid=17858
>> I, [2010-05-28T08:54:45.774350 #17858]  INFO -- : Refreshing Gem list
>>
>> /usr/local/lib/ruby/gems/1.9.1/gems/activesupport-3.0.0.beta3/lib/active_support/deprecation/proxy_wrappers.rb:17:in
>> `new': wrong number of arguments (1 for 2) (ArgumentError)
>> 	from
>> /usr/local/lib/ruby/gems/1.9.1/gems/activesupport-3.0.0.beta3/lib/active_support/deprecation/proxy_wrappers.rb:17:in
>> `method_missing'
> 
> <snip>
> 
>> Any ideas what's wrong?
> 
> Hi Stephan,
> 
> I've heard (but not confirmed myself) Rails 3 doesn't work well with
> Ruby 1.9.1, but does with 1.9.2dev (trunk), and 1.8.7.  Can you give
> either of those versions of Ruby a try?
> 
> Another thing that's probably not the issue here, but since config.ru is
> present, give "unicorn" a shot instead of "unicorn_rails" as the latter
> hasn't been tested heavily with Rails 3.  "unicorn_rails" was designed
> with older Rails in mind.
> 
> Let us know what you find, thanks!
> 

Hi Eric,
Using the config.ru with "unicorn" does indeed work.
If I have the time I'll investigate other ruby versions tomorrow.

Thanks,
Stefan Maier

_______________________________________________
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do not quote signatures (like this one) or top post when replying


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: unicorn failing to start
  2010-05-28  8:55 unicorn failing to start Stefan Maier
  2010-05-28 18:49 ` Eric Wong
@ 2010-06-07 13:37 ` Stephan Kaag
  2010-06-07 16:41   ` Eric Wong
  1 sibling, 1 reply; 5+ messages in thread
From: Stephan Kaag @ 2010-06-07 13:37 UTC (permalink / raw)
  To: mongrel-unicorn

Same issue overhere. Did someone investigate this?

Stefan Maier <stefanmaier <at> gmail.com> writes:

> 
> Hi,
> 
> i'm trying to start up unicorn_rails with a rails 3 beta3 project. All I
> can get out of it is this:
> I, [2010-05-28T08:54:45.770957 #17852]  INFO -- : reaped
> #<Process::Status: pid 17854 exit 1> worker=0
> I, [2010-05-28T08:54:45.771200 #17852]  INFO -- : worker=0 spawning...
> I, [2010-05-28T08:54:45.774049 #17858]  INFO -- : worker=0 spawned pid=17858
> I, [2010-05-28T08:54:45.774350 #17858]  INFO -- : Refreshing Gem list
> 
> /usr/local/lib/ruby/gems/1.9.1/gems/activesupport-
3.0.0.beta3/lib/active_support/deprecation/proxy_wrappers.rb:17:in
> `new': wrong number of arguments (1 for 2) (ArgumentError)
> 	from
> /usr/local/lib/ruby/gems/1.9.1/gems/activesupport-
3.0.0.beta3/lib/active_support/deprecation/proxy_wrappers.rb:17:in
> `method_missing'


_______________________________________________
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do not quote signatures (like this one) or top post when replying


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: unicorn failing to start
  2010-06-07 13:37 ` Stephan Kaag
@ 2010-06-07 16:41   ` Eric Wong
  0 siblings, 0 replies; 5+ messages in thread
From: Eric Wong @ 2010-06-07 16:41 UTC (permalink / raw)
  To: unicorn list; +Cc: Stephan Kaag

Stephan Kaag <stephan.gmane@ka.ag> wrote:
> Stefan Maier <stefanmaier <at> gmail.com> writes:
> > i'm trying to start up unicorn_rails with a rails 3 beta3 project. All I
> > can get out of it is this:
> > I, [2010-05-28T08:54:45.770957 #17852]  INFO -- : reaped
> > #<Process::Status: pid 17854 exit 1> worker=0
> > I, [2010-05-28T08:54:45.771200 #17852]  INFO -- : worker=0 spawning...
> > I, [2010-05-28T08:54:45.774049 #17858]  INFO -- : worker=0 spawned pid=17858
> > I, [2010-05-28T08:54:45.774350 #17858]  INFO -- : Refreshing Gem list
> > 
> > /usr/local/lib/ruby/gems/1.9.1/gems/activesupport-
> 3.0.0.beta3/lib/active_support/deprecation/proxy_wrappers.rb:17:in
> > `new': wrong number of arguments (1 for 2) (ArgumentError)
> > 	from
> > /usr/local/lib/ruby/gems/1.9.1/gems/activesupport-
> 3.0.0.beta3/lib/active_support/deprecation/proxy_wrappers.rb:17:in
> > `method_missing'
>
> Same issue overhere. Did someone investigate this?

(top posting corrected)

Hi Stephan, looks like Stefan worked around the problem
by using "unicorn".

I've made some changes in unicorn.git which _may_ fix the issues
and pushed out a pre-release gem here:

  http://unicorn.bogomips.org/files/unicorn-0.99.0.16.g59a625.gem

You can read about the actual changes to the above gem here:

  http://mid.gmane.org/20100604015838.GA21464@dcvr.yhbt.net

-- 
Eric Wong
_______________________________________________
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do not quote signatures (like this one) or top post when replying


^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2010-06-07 16:43 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-05-28  8:55 unicorn failing to start Stefan Maier
2010-05-28 18:49 ` Eric Wong
2010-05-28 19:19   ` Stefan Maier
2010-06-07 13:37 ` Stephan Kaag
2010-06-07 16:41   ` Eric Wong

Code repositories for project(s) associated with this public inbox

	https://yhbt.net/unicorn.git/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).