Puppet users - Sep 2009 - error starting puppetmaster after upgrade to 0.25.0

After an upgrade to 0.25.0 I get the following error:
/usr/local/lib/site_ruby/1.8/rubygems.rb:383:in `bin_path'':
can''t find
executable puppetmasterd for puppet-0.25.0 (Gem::Exception)
from /usr/bin/puppetmasterd:19

Uninstall just 0.25.0 and returning to .0.24.8 and it startup works.  I also
uninstalled all puppet gems and just tried to install 0.25.0 by itself.
 When I did this no executables were created in the /usr/bin directory for
puppet.

I am using hardy as the OS and installing via gem.  Bug or is something
whack in my environment?

Chris

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

see the thread "New 2.5 gem does not create entries into /usr/sbin"

<http://groups.google.com/group/puppet-users/browse_thread/thread/56ca66eee45bcb16?hl=en#
 >


---
Thanks,

Allan Marcus
505-667-5666



On Sep 14, 2009, at 10:54 AM, Chris Blumentritt wrote:
> After an upgrade to 0.25.0 I get the following error:
>
> /usr/local/lib/site_ruby/1.8/rubygems.rb:383:in `bin_path'':
can''t
> find executable puppetmasterd for puppet-0.25.0 (Gem::Exception)
> 	from /usr/bin/puppetmasterd:19
>
> Uninstall just 0.25.0 and returning to .0.24.8 and it startup  
> works.  I also uninstalled all puppet gems and just tried to install  
> 0.25.0 by itself.  When I did this no executables were created in  
> the /usr/bin directory for puppet.
>
> I am using hardy as the OS and installing via gem.  Bug or is  
> something whack in my environment?
>
> Chris
>
>
> >

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

I overcame this issue by uninstalling all instances of puppet, re installing
0.25.0 and then changing into the gem directory and running install.rb by
hand.  I agree with the need for rubygems to distinguish between bin and
sbin but I also need the executables :)

On Mon, Sep 14, 2009 at 12:21 PM, Allan Marcus <allan@lanl.gov> wrote:
>
> see the thread "New 2.5 gem does not create entries into
/usr/sbin"
>
> <
>
http://groups.google.com/group/puppet-users/browse_thread/thread/56ca66eee45bcb16?hl=en#
>  >
>
>
> ---
> Thanks,
>
> Allan Marcus
> 505-667-5666
>
>
>
> On Sep 14, 2009, at 10:54 AM, Chris Blumentritt wrote:
>
> > After an upgrade to 0.25.0 I get the following error:
> >
> > /usr/local/lib/site_ruby/1.8/rubygems.rb:383:in `bin_path'':
can''t
> > find executable puppetmasterd for puppet-0.25.0 (Gem::Exception)
> >       from /usr/bin/puppetmasterd:19
> >
> > Uninstall just 0.25.0 and returning to .0.24.8 and it startup
> > works.  I also uninstalled all puppet gems and just tried to install
> > 0.25.0 by itself.  When I did this no executables were created in
> > the /usr/bin directory for puppet.
> >
> > I am using hardy as the OS and installing via gem.  Bug or is
> > something whack in my environment?
> >
> > Chris
> >
> >
> > >
>
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

2009/9/16 Chris Blumentritt <cblument@gmail.com>:
> I overcame this issue by uninstalling all instances of puppet, re
installing
> 0.25.0 and then changing into the gem directory and running install.rb by
> hand.  I agree with the need for rubygems to distinguish between bin and
> sbin but I also need the executables :)
>
And since this is an upstream issue with RubyGems I am tempted to say
we don''t bother to continue to package Gems until it''s fixed. 
Of
course I am sure that is not going to be a popular decision.  Ideas
about how to overcome this issue are most welcome.

Regards

James Turnbull

-- 
Author of:
* Pro Linux Systems Administration (http://tinyurl.com/linuxadmin)
* Pulling Strings with Puppet (http://tinyurl.com/pupbook)
* Pro Nagios 2.0 (http://tinyurl.com/pronagios)
* Hardening Linux (http://tinyurl.com/hardeninglinux)

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