[Puppet Users] ANNOUNCE: Puppet 0.24.9 is available

2010-01-07 Thread James Turnbull
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Puppet 0.24.9 - no codename The 0.24.9 release is a security release in the legacy 0.24.x branch. It addresses a potential security vulnerability in the temporary files used by Puppet. Thanks to Till Mass for reporting the error and the Red Hat and

Re: [Puppet Users] Install gem packages behind a proxy

2010-01-07 Thread James Turnbull
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 seph wrote: > Hi all. My particular environment doesn't allow most of the machines to > make direct external connections, so I send a lot of things through > proxies. And now, I'm trying to figure out how to use puppet to install > gems, via proxy. >

Re: [Puppet Users] Re: puppet logging with passenger

2010-01-07 Thread Joshua Anderson
Adding --logdest /path/to/your/log to your config.ru file should work. Here's what I'm using with 0.25.1 and Passenger 2.2.7: # a config.ru, for use with every rack-compatible webserver. # SSL needs to be handled outside this, though. # if puppet is not i

[Puppet Users] (Module custom(/custom)) using the deprecated 'plugins' directory for ruby extensions; please move to 'lib'

2010-01-07 Thread chakkerz
Hello there I'm missing something: i get these error messages: (Module custom(/opt/USG/USG_Puppet/modules/custom)) using the deprecated 'plugins' directory for ruby extensions; please move to 'lib' and after hunting around for what the corrective action is i am still coming up blank. I'm guessing

[Puppet Users] Install gem packages behind a proxy

2010-01-07 Thread seph
Hi all. My particular environment doesn't allow most of the machines to make direct external connections, so I send a lot of things through proxies. And now, I'm trying to figure out how to use puppet to install gems, via proxy. The gem command itself has a command line option, or honors the http

Re: [Puppet Users] puppet packaging in Debian

2010-01-07 Thread Steve Wray
Quoting Nigel Kersten : On Wed, Jan 6, 2010 at 6:16 PM, Steve Wray wrote: Hi there I am about to embark on a project to implement puppet for server management and I'm noticing that the version currently in Debian testing is 0.25.1-3 while the latest stable version is 0.25.2 I'm not seeing an

Re: [Puppet Users] Reloading puppet client after nss change

2010-01-07 Thread Silviu Paragina
Check this out: http://groups.google.com/group/puppet-users/browse_thread/thread/23644c7a25661a2a/91b87703009f851d Silviu On 06.01.2010 17:35, Doug Warner wrote: I'm using puppet to push around nss-db updates but I'm having problems where the currently running puppet instance doesn't see the

Re: [Puppet Users] strange problem with RHEL 4 and 0.25.2

2010-01-07 Thread James Turnbull
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Matthew Delves wrote: > Hey All, > I've just updated one of my servers from 0.24.8 (I know, slack that I'm that > far behind) to 0.25.2 though have found that when trying to run puppet I get > the following errors: > > Could not autoload rpm: undefi