Trevor Vaughan
2009-Mar-19 12:01 UTC
[Puppet Users] Possible bug in 0.24.6 -- crashing puppetmasterd.
So, for whatever insane reason, I tried to have Puppet set the permissions on some files in /etc/puppet such as autosign.conf and fileserver.conf. I had puppet set the perms to 640 and, when puppetmasterd looked at them again, it would set them back to 644. Eventually, the puppetmasterd crashed with no error message. Obviously, I shouldn''t be doing this, but it seems like puppetmasterd shouldn''t fail either. Anyone else have any experience with this? Thanks, Trevor --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
Andrew Shafer
2009-Mar-19 21:17 UTC
[Puppet Users] Re: Possible bug in 0.24.6 -- crashing puppetmasterd.
Can you reproduce? Were you running puppetmasterd with --debug --trace? On Thu, Mar 19, 2009 at 6:01 AM, Trevor Vaughan <peiriannydd@gmail.com>wrote:> > So, for whatever insane reason, I tried to have Puppet set the > permissions on some files in /etc/puppet such as autosign.conf and > fileserver.conf. > > I had puppet set the perms to 640 and, when puppetmasterd looked at > them again, it would set them back to 644. > > Eventually, the puppetmasterd crashed with no error message. > > Obviously, I shouldn''t be doing this, but it seems like puppetmasterd > shouldn''t fail either. > > Anyone else have any experience with this? > > Thanks, > > Trevor > > > >--~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
Trevor Hemsley
2009-Mar-19 21:56 UTC
[Puppet Users] Re: Possible bug in 0.24.6 -- crashing puppetmasterd.
I tried it because I wanted to change the perms on
/etc/puppet/puppet.conf to 600.
class puppetperms
{
file {"/etc/puppet/puppet.conf":
owner => root,
group => root,
mode => 600
}
}
I ran puppetd --test --tags puppetperms on the puppetmaster and got
this in syslog:
puppetd[6381]:
(//Node[infra]/puppetperms/File[/etc/puppet/puppet.conf]/mode) mode
changed ''644'' to ''600''
puppetd[6381]: Finished catalog run in 7.08 seconds
puppetmasterd[26866]: Reparsing /etc/puppet/puppet.conf
The next run of puppetd reported
puppetd[6562]: (/File[/var/lib/puppet/facts]) Failed to generate
additional resources during transaction: Could not connect to puppet on
port 8140
puppetd[6562]: (/File[/var/lib/puppet/facts]) Failed to retrieve current
state of resource: Could not connect to puppet on port 8140 Could not
describe /facts: Could not connect to puppet on port 8140
and puppetmasterd was dead.
A restart of puppetmaster and it seems fine with the corrected
permissions. But if I change the perms back to a more relaxed setting
and rerun puppetd --test --tags puppetperms then it corrects them again
then crashes.
Puppet 0.24.7 on RHEL 5.3 x86_64.
Andrew Shafer wrote:>
> Can you reproduce?
>
> Were you running puppetmasterd with --debug --trace?
>
>
>
> On Thu, Mar 19, 2009 at 6:01 AM, Trevor Vaughan <peiriannydd@gmail.com
> <mailto:peiriannydd@gmail.com>> wrote:
>
>
> So, for whatever insane reason, I tried to have Puppet set the
> permissions on some files in /etc/puppet such as autosign.conf and
> fileserver.conf.
>
> I had puppet set the perms to 640 and, when puppetmasterd looked at
> them again, it would set them back to 644.
>
> Eventually, the puppetmasterd crashed with no error message.
>
> Obviously, I shouldn''t be doing this, but it seems like
puppetmasterd
> shouldn''t fail either.
>
> Anyone else have any experience with this?
>
> Thanks,
>
> Trevor
>
>
>
>
> >
--
Trevor Hemsley
Infrastructure Engineer
.................................................
* C A L Y P S O
* 4th Floor, Tower Point,
44 North Road,
Brighton, BN1 1YR, UK
OFFICE +44 (0) 1273 666 350
FAX +44 (0) 1273 666 351
.................................................
www.calypso.com
This electronic-mail might contain confidential information intended
only for the use by the entity named. If the reader of this message is
not the intended recipient, the reader is hereby notified that any
dissemination, distribution or copying is strictly prohibited.
* P * /*/ Please consider the environment before printing this e-mail /*/
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
Luke Kanies
2009-Mar-19 22:33 UTC
[Puppet Users] Re: Possible bug in 0.24.6 -- crashing puppetmasterd.
On Mar 19, 2009, at 4:56 PM, Trevor Hemsley wrote:> > I tried it because I wanted to change the perms on > /etc/puppet/puppet.conf to 600. > > class puppetperms > { > file {"/etc/puppet/puppet.conf": > owner => root, > group => root, > mode => 600 > } > }You should be able to do this with something like: # puppet.conf configfile = /etc/puppet/puppet.conf{owner = root, group = ...} I''m typing from not-very-good memory here; I don''t remember if that''s the right param, or if you need ''='' or ''=>'' here. The ConfigurationReference should make both clear.> > I ran puppetd --test --tags puppetperms on the puppetmaster and got > this in syslog: > > puppetd[6381]: > (//Node[infra]/puppetperms/File[/etc/puppet/puppet.conf]/mode) mode > changed ''644'' to ''600'' > puppetd[6381]: Finished catalog run in 7.08 seconds > puppetmasterd[26866]: Reparsing /etc/puppet/puppet.conf > > The next run of puppetd reported > > puppetd[6562]: (/File[/var/lib/puppet/facts]) Failed to generate > additional resources during transaction: Could not connect to puppet > on > port 8140 > puppetd[6562]: (/File[/var/lib/puppet/facts]) Failed to retrieve > current > state of resource: Could not connect to puppet on port 8140 Could not > describe /facts: Could not connect to puppet on port 8140 > > and puppetmasterd was dead. > > A restart of puppetmaster and it seems fine with the corrected > permissions. But if I change the perms back to a more relaxed setting > and rerun puppetd --test --tags puppetperms then it corrects them > again > then crashes. > > Puppet 0.24.7 on RHEL 5.3 x86_64.Please file that as a bug. It''s crazy. Please include stack traces and debugging on the server if you can get them. -- Nothing is impossible for the man who doesn''t have to do it himself. -- A. H. Weiler --------------------------------------------------------------------- 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 -~----------~----~----~----~------~----~------~--~---
Trevor Hemsley
2009-Mar-19 23:05 UTC
[Puppet Users] Re: Possible bug in 0.24.6 -- crashing puppetmasterd.
Luke Kanies wrote:> You should be able to do this with something like: > > # puppet.conf > configfile = /etc/puppet/puppet.conf{owner = root, group = ...} > > I''m typing from not-very-good memory here; I don''t remember if that''s > the right param, or if you need ''='' or ''=>'' here. The > ConfigurationReference should make both clear. >I checked the ConfigurationReference and even cut and pasted the example it gives and amended the path to point to /etc/puppet/puppet.conf so it said myfile = /etc/puppet/puppet.conf {owner = root, mode = 644} but it does not work (also tried as configfile = as you suggested above). # puppetd --test --trace --tags puppetperms /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:1070:in `send'': undefined method `owner='' for nil:NilClass (NoMethodError) from /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:1070:in `set_metadata'' from /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:1069:in `each'' from /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:1069:in `set_metadata'' from /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:1068:in `each'' from /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:1068:in `set_metadata'' from /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:381:in `unsafe_parse'' from /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:379:in `each'' from /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:379:in `unsafe_parse'' from /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:344:in `parse'' from /usr/lib/ruby/1.8/sync.rb:229:in `synchronize'' from /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:343:in `parse'' from /usr/lib/ruby/site_ruby/1.8/puppet.rb:177:in `parse_config'' from /usr/sbin/puppetd:274 I''ll raise two bugs then :( -- Trevor Hemsley Infrastructure Engineer ................................................. * C A L Y P S O * 4th Floor, Tower Point, 44 North Road, Brighton, BN1 1YR, UK OFFICE +44 (0) 1273 666 350 FAX +44 (0) 1273 666 351 ................................................. www.calypso.com This electronic-mail might contain confidential information intended only for the use by the entity named. If the reader of this message is not the intended recipient, the reader is hereby notified that any dissemination, distribution or copying is strictly prohibited. * P * /*/ Please consider the environment before printing this e-mail /*/ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
Luke Kanies
2009-Mar-25 02:26 UTC
[Puppet Users] Re: Possible bug in 0.24.6 -- crashing puppetmasterd.
On Mar 19, 2009, at 6:05 PM, Trevor Hemsley wrote:> > > > Luke Kanies wrote: >> You should be able to do this with something like: >> >> # puppet.conf >> configfile = /etc/puppet/puppet.conf{owner = root, group = ...} >> >> I''m typing from not-very-good memory here; I don''t remember if that''s >> the right param, or if you need ''='' or ''=>'' here. The >> ConfigurationReference should make both clear. >> > I checked the ConfigurationReference and even cut and pasted the > example > it gives and amended the path to point to /etc/puppet/puppet.conf so > it > said > > myfile = /etc/puppet/puppet.conf {owner = root, mode = 644} > > but it does not work (also tried as configfile = as you suggested > above).Like I said, I wasn''t sure of the parameter - it''s ''config'', I just tried it and it works for me. Try that.> > # puppetd --test --trace --tags puppetperms > /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:1070:in `send'': > undefined method `owner='' for nil:NilClass (NoMethodError) > from /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb: > 1070:in > `set_metadata'' > from /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb: > 1069:in > `each'' > from /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb: > 1069:in > `set_metadata'' > from /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb: > 1068:in > `each'' > from /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb: > 1068:in > `set_metadata'' > from /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:381:in > `unsafe_parse'' > from /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:379:in > `each'' > from /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:379:in > `unsafe_parse'' > from /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:344:in > `parse'' > from /usr/lib/ruby/1.8/sync.rb:229:in `synchronize'' > from /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:343:in > `parse'' > from /usr/lib/ruby/site_ruby/1.8/puppet.rb:177:in > `parse_config'' > from /usr/sbin/puppetd:274 > > I''ll raise two bugs then :( > > -- > > Trevor Hemsley > Infrastructure Engineer > ................................................. > * C A L Y P S O > * 4th Floor, Tower Point, > 44 North Road, > Brighton, BN1 1YR, UK > > OFFICE +44 (0) 1273 666 350 > FAX +44 (0) 1273 666 351 > > ................................................. > www.calypso.com > > This electronic-mail might contain confidential information intended > only for the use by the entity named. If the reader of this message is > not the intended recipient, the reader is hereby notified that any > dissemination, distribution or copying is strictly prohibited. > > * P * /*/ Please consider the environment before printing this e- > mail /*/ > > > >-- He is indebted to his memory for his jests and to his imagination for his facts. --Richard Brinsley Sheridan --------------------------------------------------------------------- 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 -~----------~----~----~----~------~----~------~--~---