Hi there, I''m trying to figure out how to decrease the runinterval from its default of 1800 seconds (30 mins) to 300 seconds (5 mins). I''ve added: runinterval=300 to puppetmasterd.conf on the server and restarted puppetmaster. Nothing changed. I added it to puppetd.conf and restarted puppetmaster and puppetd. Nothing changed. I can find no documentation on how or where to use this parameter, other than that it exists... Please advise 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 -~----------~----~----~----~------~----~------~--~---
Steve Wray wrote:> Hi there, > > I''m trying to figure out how to decrease the runinterval from its > default of 1800 seconds (30 mins) to 300 seconds (5 mins). > > I''ve added: > > runinterval=300 > > to puppetmasterd.conf on the server and restarted puppetmaster. Nothing > changed. >This is a puppetd section configuration value> I added it to puppetd.conf and restarted puppetmaster and puppetd. > Nothing changed. >puppetd.conf is deprecated, please shift to puppet.conf with [main], [puppetd], [puppetmasterd] sections> I can find no documentation on how or where to use this parameter, other > than that it exists... >puppetd --genconfig|less ... # How often puppetd applies the client configuration; in seconds. # The default value is ''1800''. # runinterval = 1800 Regards, AJ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
AJ wrote:> Steve Wray wrote: >> Hi there, >> >> I''m trying to figure out how to decrease the runinterval from its >> default of 1800 seconds (30 mins) to 300 seconds (5 mins). >> >> I''ve added: >> >> runinterval=300 >> >> to puppetmasterd.conf on the server and restarted puppetmaster. Nothing >> changed. >> > This is a puppetd section configuration value>> I added it to puppetd.conf and restarted puppetmaster and puppetd. >> Nothing changed. >> > puppetd.conf is deprecated, please shift to puppet.conf with [main], > [puppetd], [puppetmasterd] sectionsah well... my distro has the 3 seperate files... I''m not sure if they are compiled in or what. This is Debian Etch. I know how they love to tinker... root@puppet1:/var/log# puppetd --version 0.20.1 so I have a puppetd.conf file and no idea whether having these sections in the main puppet.conf file is going to work or explode so heres my puppetd.conf: [puppetd] server=puppet1.xxx.yyy.zzz logdir=/var/log/puppet vardir=/var/lib/puppet rundir=/var/run runinterval=300 should this work? Because it doesn''t... I guess that I''ll go against what my distro has packaged for me and try out putting this into a [puppetd] section in the puppet.conf file.>> I can find no documentation on how or where to use this parameter, other >> than that it exists... >> > puppetd --genconfig|less > ... > # How often puppetd applies the client configuration; in seconds. > # The default value is ''1800''. > # runinterval = 1800 > > Regards, > > AJ > > >--~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
Hang on a moment... does this parameter go on the *clients*? Or the puppetmaster server? Is it the *client* which governs how often it runs?? (thats what I meant about ''documentation'' btw) Steve Wray wrote:> AJ wrote: >> Steve Wray wrote: >>> Hi there, >>> >>> I''m trying to figure out how to decrease the runinterval from its >>> default of 1800 seconds (30 mins) to 300 seconds (5 mins). >>> >>> I''ve added: >>> >>> runinterval=300 >>> >>> to puppetmasterd.conf on the server and restarted puppetmaster. Nothing >>> changed. >>> >> This is a puppetd section configuration value > >>> I added it to puppetd.conf and restarted puppetmaster and puppetd. >>> Nothing changed. >>> >> puppetd.conf is deprecated, please shift to puppet.conf with [main], >> [puppetd], [puppetmasterd] sections > > ah well... my distro has the 3 seperate files... I''m not sure if they > are compiled in or what. This is Debian Etch. I know how they love to > tinker... > > root@puppet1:/var/log# puppetd --version > 0.20.1 > > so I have a puppetd.conf file and no idea whether having these sections > in the main puppet.conf file is going to work or explode so heres my > puppetd.conf: > > [puppetd] > server=puppet1.xxx.yyy.zzz > logdir=/var/log/puppet > vardir=/var/lib/puppet > rundir=/var/run > runinterval=300 > > should this work? Because it doesn''t... > > I guess that I''ll go against what my distro has packaged for me and try > out putting this into a [puppetd] section in the puppet.conf file. > > >>> I can find no documentation on how or where to use this parameter, other >>> than that it exists... >>> >> puppetd --genconfig|less >> ... >> # How often puppetd applies the client configuration; in seconds. >> # The default value is ''1800''. >> # runinterval = 1800 >> >> Regards, >> >> AJ >> > > > >--~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
Steve Wray wrote:> Hang on a moment... > > does this parameter go on the *clients*? Or the puppetmaster server? > > Is it the *client* which governs how often it runs?? > > (thats what I meant about ''documentation'' btw) > >Aye, on the client. Sorry. 0.20.1 is ancient - i''m not sure it even supported runinterval, let alone the sectioned configuration files - might I suggest backporting 0.24.4? The BootstrappingWithPuppet wiki page (shameless plug) and the DebianPuppet go into this :) Regards, AJ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
AJ wrote:> Steve Wray wrote: >> Hang on a moment... >> >> does this parameter go on the *clients*? Or the puppetmaster server? >> >> Is it the *client* which governs how often it runs?? >> >> (thats what I meant about ''documentation'' btw) >> >> > > Aye, on the client. Sorry.I see. Coming from cfengine this does seem a bit wierd; putting the client in charge of when it gets updated...> 0.20.1 is ancient - i''m not sure it even supported runinterval, let > alone the sectioned configuration files - might I suggest backporting > 0.24.4?Yeah well... there doesn''t seem to be an ''official'' backport yet and I tend to stick with the distribution version wherever possible when I''m dealing with production systems. I''ll see how it goes.> The BootstrappingWithPuppet wiki page (shameless plug) and the > DebianPuppet go into this :) > > Regards, > > AJ--~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
> > Yeah well... there doesn''t seem to be an ''official'' backport yet and I > tend to stick with the distribution version wherever possible when I''m > dealing with production systems. I''ll see how it goes. > >Official as in ''debian''? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
AJ wrote:> >> Yeah well... there doesn''t seem to be an ''official'' backport yet and I >> tend to stick with the distribution version wherever possible when I''m >> dealing with production systems. I''ll see how it goes. >> >> > Official as in ''debian''?''official'' in quotes as in: deb http://www.backports.org/debian etch-backports main contrib non-free Semi-official... these are backports from unstable if I recall correctly. So if you use them, as opposed to ''unofficial'' backports, when time comes to upgrade to the next release it should be relatively straightforward. My experience has been that using ''third party'' backports inevitably ends in tears. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
Steve Wray wrote:> AJ wrote: > >>> Yeah well... there doesn''t seem to be an ''official'' backport yet and I >>> tend to stick with the distribution version wherever possible when I''m >>> dealing with production systems. I''ll see how it goes. >>> >>> >>> >> Official as in ''debian''? >> > > ''official'' in quotes as in: > > deb http://www.backports.org/debian etch-backports main contrib non-free >You could also pin the packages.. http://reductivelabs.com/trac/puppet/wiki/PuppetDebian#InstallPuppetpackagesfromTestingonDebian avoiding backporting altogether. Many people on the list use 0.24.4 with Etch Regards, AJ --~--~---------~--~----~------------~-------~--~----~ 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 Thu, Jun 12, 2008 at 4:07 PM, Steve Wray <steve.wray@cwa.co.nz> wrote:> > AJ wrote: >> >>> Yeah well... there doesn''t seem to be an ''official'' backport yet and I >>> tend to stick with the distribution version wherever possible when I''m >>> dealing with production systems. I''ll see how it goes. >>> >>> >> Official as in ''debian''? > > ''official'' in quotes as in: > > deb http://www.backports.org/debian etch-backports main contrib non-free > > Semi-official... these are backports from unstable if I recall correctly. > > So if you use them, as opposed to ''unofficial'' backports, when time > comes to upgrade to the next release it should be relatively > straightforward. > > My experience has been that using ''third party'' backports inevitably > ends in tears. > > > > >Steve, I highly recommend going another route and doing a "first party" backport. Puppet is dead-easy to roll your own package for, and you will run into a lot of troubles if you insist on sticking with the dinosaur you are using :-) --Paul --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
AJ wrote:> Steve Wray wrote: >> AJ wrote: >> >>>> Yeah well... there doesn''t seem to be an ''official'' backport yet and I >>>> tend to stick with the distribution version wherever possible when I''m >>>> dealing with production systems. I''ll see how it goes. >>>> >>>> >>>> >>> Official as in ''debian''? >>> >> ''official'' in quotes as in: >> >> deb http://www.backports.org/debian etch-backports main contrib non-free >> > You could also pin the packages.. > http://reductivelabs.com/trac/puppet/wiki/PuppetDebian#InstallPuppetpackagesfromTestingonDebian > avoiding backporting altogether. Many people on the list use 0.24.4 with > EtchOh well this is reassuring: <quote> The current stable release of Debian (codenamed "Etch") comes with Puppet version 0.20.1, but the latest versions of Puppet are available from the unstable repositories. It is an explicit goal of the package maintainer that uploaded packages should work acceptably on the current stable release of Debian. </quote> Thanks for the tip. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
Steve Wray
2008-Jun-13 00:42 UTC
[Puppet Users] host alias changed? Was Re: [Puppet Users] Re: setting runinterval?
AJ wrote:> Steve Wray wrote: >> AJ wrote: >> >>>> Yeah well... there doesn''t seem to be an ''official'' backport yet and I >>>> tend to stick with the distribution version wherever possible when I''m >>>> dealing with production systems. I''ll see how it goes. >>>> >>>> >>>> >>> Official as in ''debian''? >>> >> ''official'' in quotes as in: >> >> deb http://www.backports.org/debian etch-backports main contrib non-free >> > You could also pin the packages.. > http://reductivelabs.com/trac/puppet/wiki/PuppetDebian#InstallPuppetpackagesfromTestingonDebian > avoiding backporting altogether. Many people on the list use 0.24.4 with > EtchI''ve given this a go but have lost the ability to set aliases in the /etc/hosts file... I have structures like this: host { testhost: alias => "testhost", ip => "192.168.0.101", name => "testhost.xxx.yyy.zzz" } which were working just great... now I get this error: warning: Configuration could not be instantiated: Duplicate definition: Host[testhost] is already defined in file /etc/puppet/manifests/classes/hosts.pp at line 94; cannot redefine the really interesting thing is that it seems to be non-deterministic. I have several host definitions. Every run of puppetd -vt I get a different host reported as already being defined. And, no, the given host definition really does occur only once in hosts.pp If I comment out the ''alias'' line its fine... but I don''t get an alias set in /etc/hosts http://reductivelabs.com/trac/puppet/wiki/TypeReference#host tells me: <quote> Any alias the host might have. Multiple values must be specified as an array. Note that this state has the same name as one of the metaparams; using this state to set aliases will make those aliases available in your Puppet scripts and also on disk. </quote> and leaves me baffled as to why it is no longer working... Is this a regression bug or something? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
Steve Wray wrote:> Yeah well... there doesn''t seem to be an ''official'' backport yet and I > tend to stick with the distribution version wherever possible when I''m > dealing with production systems. I''ll see how it goes. >No need to do a backport anything; the package in Debian unstable/sid works fine on stable/Etch (at least for me). It isn''t compiled code, so it doesn''t depend on a specific version of libc6. Brian May --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
Brian May wrote:> Steve Wray wrote: > >> Yeah well... there doesn''t seem to be an ''official'' backport yet and I >> tend to stick with the distribution version wherever possible when I''m >> dealing with production systems. I''ll see how it goes. >> >> > No need to do a backport anything; the package in Debian unstable/sid > works fine on stable/Etch (at least for me). It isn''t compiled code, so > it doesn''t depend on a specific version of libc6. > >You may run into issues with older version of Ruby with parts built against specific versions of libc (SSL, for example) Everything works great on Etch though /me lets thread die Regards, AJ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---