We are using puppet from ruby gems and the help isn''t working. For example: 178 # puppetmasterd --help This file was generated by RubyGems. The application ''puppet'' is installed as part of a gem, and this file is here to facilitate running it. But when we had the tarball version, puppetmasterd --help printed all the switch options. Unfortunately, the tarball version didn''t working properly in our environment, but the gems version is an improvement. (Although we can''t get it to log anywhere but /var/log/messages Jeff --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
On May 12, 2008, at 9:03 AM, Jeff wrote:> > We are using puppet from ruby gems and the help isn''t working. For > example: > > 178 # puppetmasterd --help > This file was generated by RubyGems. > > The application ''puppet'' is installed as part of a gem, and this file > is > here to facilitate running it. > > > But when we had the tarball version, puppetmasterd --help printed all > the switch options.Gems are stupid and replace puppet''s executables with stubs, and rdoc::Usage isn''t smart enough to figure that out. It''s basically an upstream problem, and we''re kind of foolish for continuing to use rdoc::usage, considering how much it, um, sucks. I''ve been meaning to replace it for ages, but I haven''t really gotten around to it.> > Unfortunately, the tarball version didn''t working properly in our > environment, but the gems version is an improvement. (Although we > can''t get it to log anywhere but /var/log/messagesHow isn''t the tarball working? And the only-logging-to-syslog is a filed bug. -- A little government and a little luck are necessary in life, but only a fool trusts either of them. -- P. J. O''Rourke --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
On May 12, 12:08 pm, Luke Kanies <l...@madstop.com> wrote:> On May 12, 2008, at 9:03 AM, Jeff wrote: > > > We are using puppet from ruby gems and the help isn''t working. For > > example: > > > 178 # puppetmasterd --help > > This file was generated by RubyGems. > > > The application ''puppet'' is installed as part of a gem, and this file > > is > > here to facilitate running it. > > > But when we had the tarball version, puppetmasterd --help printed all > > the switch options. > > Gems are stupid and replace puppet''s executables with stubs, and > rdoc::Usage isn''t smart enough to figure that out. > > It''s basically an upstream problem, and we''re kind of foolish for > continuing to use rdoc::usage, considering how much it, um, sucks. > I''ve been meaning to replace it for ages, but I haven''t really gotten > around to it. > > > > > Unfortunately, the tarball version didn''t working properly in our > > environment, but the gems version is an improvement. (Although we > > can''t get it to log anywhere but /var/log/messages > > How isn''t the tarball working? > > And the only-logging-to-syslog is a filed bug. >This is the thread in which I covered that problem. We "fixed" it by moving to the gems install: http://groups.google.com/group/puppet-users/browse_frm/thread/ff9c60c750df0194 Which version do you recommend, the tarball or the gems? Jeff --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
On May 12, 2008, at 12:17 PM, Jeff wrote:> This is the thread in which I covered that problem. We "fixed" it by > moving to the gems install: > http://groups.google.com/group/puppet-users/browse_frm/thread/ff9c60c750df0194 > > Which version do you recommend, the tarball or the gems?Um, dpkg? Really, I recommend native packages. Either other one should work, but natives are best. -- Of the thirty-six ways of avoiding disaster, running away is best. -- Chinese Proverb --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
On May 12, 1:25 pm, Luke Kanies <l...@madstop.com> wrote:> On May 12, 2008, at 12:17 PM, Jeff wrote: > > > This is the thread in which I covered that problem. We "fixed" it by > > moving to the gems install: > >http://groups.google.com/group/puppet-users/browse_frm/thread/ff9c60c... > > > Which version do you recommend, the tarball or the gems? > > Um, dpkg? > > Really, I recommend native packages. Either other one should work, > but natives are best. >The behavior of the pkgs matched the behavior of the gems with one exception: The package didn''t include a config.rb and it barfed when it tried to parse puppetd.conf Jeff --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
On May 12, 2:00 pm, Jeff <joesi...@gmail.com> wrote:> On May 12, 1:25 pm, Luke Kanies <l...@madstop.com> wrote: > > > On May 12, 2008, at 12:17 PM, Jeff wrote: > > > > This is the thread in which I covered that problem. We "fixed" it by > > > moving to the gems install: > > >http://groups.google.com/group/puppet-users/browse_frm/thread/ff9c60c... > > > > Which version do you recommend, the tarball or the gems? > > > Um, dpkg? > > > Really, I recommend native packages. Either other one should work, > > but natives are best. > > The behavior of the pkgs matched the behavior of the gems with one > exception: The package didn''t include a config.rb and it barfed when > it tried to parse puppetd.conf >Sorry. config.rb *is* installed. The rpm placed it below /usr/lib/ site_ruby. When I run puppetd or puppetmasterd, it can''t find that object. I assume I have to add /usr/lib/site_ruby to a path variable somewhere. I''m a complete ruby noob so some guidance would be appreciated. Jeff --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
On May 12, 2008, at 11:00 AM, Jeff wrote:> > > > On May 12, 1:25 pm, Luke Kanies <l...@madstop.com> wrote: >> On May 12, 2008, at 12:17 PM, Jeff wrote: >> >>> This is the thread in which I covered that problem. We "fixed" it by >>> moving to the gems install: >>> http://groups.google.com/group/puppet-users/browse_frm/thread/ff9c60c >>> ... >> >>> Which version do you recommend, the tarball or the gems? >> >> Um, dpkg? >> >> Really, I recommend native packages. Either other one should work, >> but natives are best. >> > > The behavior of the pkgs matched the behavior of the gems with one > exception: The package didn''t include a config.rb and it barfed when > it tried to parse puppetd.confThis is because config.rb is no longer used, it and puppetd.conf (as well as namespaceuath.conf) were deprecated in 0.23.0. Move your configuration over to puppet.conf (no d). This is documented here: http://reductivelabs.com/trac/puppet/wiki/UPGRADE#id25 The package upgrade should probably be smart enough to deal with this. With that said, the OS packages are definitely the best way to go. -Blake --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
On May 12, 2008, at 1:00 PM, Jeff wrote:> The behavior of the pkgs matched the behavior of the gems with one > exception: The package didn''t include a config.rb and it barfed when > it tried to parse puppetd.confSame version? And --help still doesn''t work? -- This space intentionally has nothing but text explaining why this space has nothing but text explaining that this space would otherwise have been left blank, and would otherwise have been left blank. --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
On May 12, 3:01 pm, Luke Kanies <l...@madstop.com> wrote:> On May 12, 2008, at 1:00 PM, Jeff wrote: > > > The behavior of the pkgs matched the behavior of the gems with one > > exception: The package didn''t include a config.rb and it barfed when > > it tried to parse puppetd.conf > > Same version? And --help still doesn''t work? >Luke, It works now. Here''s the story. At first we tried the tarball version. As noted above, that failed when we ran --mkusers. So we tried the gems version and mkusers worked. Life was grand except for the whole lack of --help thing. Based on this conversation we decided to remove everything and start anew with the rpms. We did. --mkusers works and so does --help. Thanks. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
On May 12, 2008, at 3:43 PM, Jeff wrote:> Luke, It works now. Here''s the story. At first we tried the tarball > version. As noted above, that failed when we ran --mkusers. So we > tried the gems version and mkusers worked. Life was grand except for > the whole lack of --help thing. Based on this conversation we decided > to remove everything and start anew with the rpms. We did. --mkusers > works and so does --help.Great. Cleaning up old installs definitely matters. -- Levy''s Law: The truth is always more interesting than your preconception of what it might be. --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---