[Puppet Users] Re: using yum and puppet simultaneously
On Sat, May 9, 2009 at 5:04 PM, Nat wrote: > > Hi, > > once i have my puppet set up and installed how does updating occour, > if for example i have a package httpd instaledd on all my servers and > there is an update to this package will i still need to log into every > machine to run the updater or will puppet notice that the package is > not at the latest level and update acordingly? > > Thanks I am assuming you are ona RHEL/CENTOS/Fedora box. Use yum-cron or yum-updatesd to keep all installed packages up to date. Use puppet to be sure that the packages you want are installed. This is a classic example of the right tool for the right job. Yum to keep things up to date. Puppet to make sure the box is configured correctly. If you only want certain updates to be available or applied to your servers then use a local repo were you stage all okayed updates for your machines Evan --~--~-~--~~~---~--~~ 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+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~--~~~~--~~--~--~---
[Puppet Users] Re: using yum and puppet simultaneously
If you have ensure => latest puppet will check on each run to make sure that it's the latest available but this is intensive. I'd suggest using something like func to automate updating package sets. Once you've got func deployed you can, with one command, tell every machine to update packages. https://fedorahosted.org/func/ -- Scott On May 9, 6:04 pm, Nat wrote: > Hi, > > once i have my puppet set up and installed how does updating occour, > if for example i have a package httpd instaledd on all my servers and > there is an update to this package will i still need to log into every > machine to run the updater or will puppet notice that the package is > not at the latest level and update acordingly? > > 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+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~--~~~~--~~--~--~---
[Puppet Users] Re: using yum and puppet simultaneously
Nat wrote: > once i have my puppet set up and installed how does updating occour, > if for example i have a package httpd instaledd on all my servers and > there is an update to this package will i still need to log into every > machine to run the updater or will puppet notice that the package is > not at the latest level and update acordingly? If yum is anything like apt, you'd need two things: 1. ensure => latest for packages you want to auto-update 2. a cron job that checks the repositories for new packages (apt-get update, for example) -- Mike Renfro / R&D Engineer, Center for Manufacturing Research, 931 372-3601 / Tennessee Technological University -- ren...@tntech.edu --~--~-~--~~~---~--~~ 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+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~--~~~~--~~--~--~---
[Puppet Users] using yum and puppet simultaneously
Hi, once i have my puppet set up and installed how does updating occour, if for example i have a package httpd instaledd on all my servers and there is an update to this package will i still need to log into every machine to run the updater or will puppet notice that the package is not at the latest level and update acordingly? 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+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~--~~~~--~~--~--~---
[Puppet Users] Re: /etc/init.d/puppet on debian
2009/5/3 Russ Allbery
>
> Gary Law writes:
>
> > The init script is clearly trying to make the pid file appear in
> > /var/run/puppet... so I've little idea why this is happening.
> >
> > from the init script:
> > start_puppet() {
> > start-stop-daemon --start --quiet --pidfile
> > /var/run/puppet/$NAME.pid \
> > --startas $DAEMON -- $DAEMON_OPTS
> > }
>
> That flag doesn't say where to write the PID file. It tells
> start-stop-daemon where puppetd *will* write the PID file. You still
> have to configure puppetd elsewhere (in puppet.conf, specifically) to
> put the PID file there.
>
> Everyone seems to get confused about what the --pidfile option to
> start-stop-daemon does. It doesn't create anything at all. It just
> says where to find something that the daemon is creating.
>
Guess my Debian newbiness shining through there :)
Thanks for the explanation.
Gary
--
Gary Law
Email: gary...@garylaw.net
Chat googletalk/messenger: gary@gmail.com
iChat/jabber/AIM: gary@mac.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+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---
[Puppet Users] Re: SSL connection errors
On Sat, May 9, 2009 at 10:26 AM, Ryan Steele wrote: > Probably stating the obvious, but ditch webrick. I've increased my > runtimes by as much as 3800% (no, that's not a typo) after migrating to > Passenger. I have a few more nodes in my setup (83), but webrick was > downright non-functional after more than a couple of puppet runs got > going. Now I can run all my nodes in parallel, and the puppetmaster > doesn't so much as blink. Absolutely. Passenger is much faster and more robust than Mongrel which is much better than Webrick. -- Nigel Kersten nig...@google.com System Administrator Google, Inc. --~--~-~--~~~---~--~~ 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+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~--~~~~--~~--~--~---
[Puppet Users] Re: SSL connection errors
Nigel Kersten wrote: > Just pointing out that 0.24.8 (non RC) is available in debian testing. > > http://packages.debian.org/source/testing/puppet > > > > On Fri, May 8, 2009 at 9:09 PM, Robin Sheat wrote: >> My puppet setup has been working nicely for a while, but recently I get >> errors >> like this a lot: >> >> May 9 15:46:33 puppet puppetd[22423]: >> (//Node[basenode]/nagios::nrpe/File[/usr/local/nagios/plugins/check_apt]) >> Failed to retrieve current state of resource: Connection reset by peer - >> SSL_connect Could not describe /nagios/check_apt: Connection reset by peer - >> SSL_connect at /etc/puppet/modules/nagios/manifests/init.pp:163 >> >> The puppetmaster seems to stop logging anything by this point, although ps >> says that it's still there. >> >> I'm using 0.24.8 RC1 (the latest I've found .debs for), and am using the >> default connection handling thing (WebBrick I presume) with about a dozen >> clients, give or take. Restarting the puppetmaster gets it going for a while, >> but after a variable length of time (usually days, although today it was >> about 12 hours) it'll start happening again. >> >> Any ideas? >> >> -- >> Robin JabberID: >> >> Hostes alienigeni me abduxerunt. Qui annus est? >> >> PGP Key 0xA99CEB6D = 5957 6D23 8B16 EFAB FEF8 7175 14D3 6485 A99C EB6D >> > > > Probably stating the obvious, but ditch webrick. I've increased my runtimes by as much as 3800% (no, that's not a typo) after migrating to Passenger. I have a few more nodes in my setup (83), but webrick was downright non-functional after more than a couple of puppet runs got going. Now I can run all my nodes in parallel, and the puppetmaster doesn't so much as blink. HTH, Ryan --~--~-~--~~~---~--~~ 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+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~--~~~~--~~--~--~---
[Puppet Users] Re: SSL connection errors
Just pointing out that 0.24.8 (non RC) is available in debian testing. http://packages.debian.org/source/testing/puppet On Fri, May 8, 2009 at 9:09 PM, Robin Sheat wrote: > My puppet setup has been working nicely for a while, but recently I get errors > like this a lot: > > May 9 15:46:33 puppet puppetd[22423]: > (//Node[basenode]/nagios::nrpe/File[/usr/local/nagios/plugins/check_apt]) > Failed to retrieve current state of resource: Connection reset by peer - > SSL_connect Could not describe /nagios/check_apt: Connection reset by peer - > SSL_connect at /etc/puppet/modules/nagios/manifests/init.pp:163 > > The puppetmaster seems to stop logging anything by this point, although ps > says that it's still there. > > I'm using 0.24.8 RC1 (the latest I've found .debs for), and am using the > default connection handling thing (WebBrick I presume) with about a dozen > clients, give or take. Restarting the puppetmaster gets it going for a while, > but after a variable length of time (usually days, although today it was > about 12 hours) it'll start happening again. > > Any ideas? > > -- > Robin JabberID: > > Hostes alienigeni me abduxerunt. Qui annus est? > > PGP Key 0xA99CEB6D = 5957 6D23 8B16 EFAB FEF8 7175 14D3 6485 A99C EB6D > -- Nigel Kersten nig...@google.com System Administrator Google, Inc. --~--~-~--~~~---~--~~ 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+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~--~~~~--~~--~--~---
