Do you know where I might be able to change where it's looking for the 
specific rack version for 1.1.0?

Thanks,
Tom


On Friday, February 22, 2013 5:29:59 PM UTC-8, Matt wrote:
>
> It looks like its trying to use a specific rack gem version but you do 
> not have that version installed or you have two versions installed and 
> its picking up the latest. It could be that you also have another 
> passenger application where the versions conflict? 
>
> (can't activate rack (~> 1.1.0, runtime) for [], already activated 
> rack-1.5.2 for []) (process 8729, thread #<Thread:0x7fed2a6fc358>): 
>
> On Fri, Feb 22, 2013 at 7:17 PM, Tom Blich <bunk...@gmail.com<javascript:>> 
> wrote: 
> > Had puppet-dashboard-1.2.21 running via instructions provided here: 
> > 
> > http://docs.puppetlabs.com/dashboard/passenger.html 
> > 
> > Upgraded to puppet-dashboard-1.2.22 and now get the following error: 
> > 
> >   [ pid=8729 thr=70328297972140 file=utils.rb:176 time=2013-02-22 
> > 19:12:17.188 ]: *** Exception RuntimeError in 
> > PhusionPassenger::Rack::ApplicationSpawner (can't activate rack (~> 
> 1.1.0, 
> > runtime) for [], already activated rack-1.5.2 for []) (process 8729, 
> thread 
> > #<Thread:0x7fed2a6fc358>): 
> > from ./config/../vendor/rails/railties/lib/initializer.rb:271:in 
> > `require_frameworks' 
> > from ./config/../vendor/rails/railties/lib/initializer.rb:134:in 
> `process' 
> > from ./config/../vendor/rails/railties/lib/initializer.rb:113:in `send' 
> > from ./config/../vendor/rails/railties/lib/initializer.rb:113:in `run' 
> > from ./config/environment.rb:14 
> > from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in 
> > `gem_original_require' 
> > from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in 
> `require' 
> > from config.ru:4 
> > from /usr/lib/ruby/gems/1.8/gems/rack-1.5.2/lib/rack/builder.rb:55:in 
> > `instance_eval' 
> > from /usr/lib/ruby/gems/1.8/gems/rack-1.5.2/lib/rack/builder.rb:55:in 
> > `initialize' 
> > from config.ru:1:in `new' 
> > from config.ru:1 
> > [Fri Feb 22 19:12:46 2013] [notice] caught SIGTERM, shutting down 
> > [Fri Feb 22 19:13:37 2013] [warn] Init: Session Cache is not configured 
> > [hint: SSLSessionCache] 
> > [Fri Feb 22 19:13:37 2013] [notice] suEXEC mechanism enabled (wrapper: 
> > /usr/sbin/suexec) 
> > [Fri Feb 22 19:13:37 2013] [warn] module php5_module is already loaded, 
> > skipping 
> > [Fri Feb 22 19:13:37 2013] [notice] Digest: generating secret for digest 
> > authentication ... 
> > [Fri Feb 22 19:13:37 2013] [notice] Digest: done 
> > [Fri Feb 22 19:13:37 2013] [notice] Apache/2.2.15 (Unix) DAV/2 
> > Phusion_Passenger/3.0.19 PHP/5.3.20 mod_ssl/2.2.15 OpenSSL/1.0.0-fips 
> > configured -- resuming normal operations 
> > 
> > Not sure how to fix it. 
> > 
> > Thanks, 
> > Tom 
> > 
> > -- 
> > You received this message because you are subscribed to the Google 
> Groups 
> > "Puppet Users" group. 
> > To unsubscribe from this group and stop receiving emails from it, send 
> an 
> > email to puppet-users...@googlegroups.com <javascript:>. 
> > To post to this group, send email to 
> > puppet...@googlegroups.com<javascript:>. 
>
> > Visit this group at http://groups.google.com/group/puppet-users?hl=en. 
> > For more options, visit https://groups.google.com/groups/opt_out. 
> > 
> > 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to