The files are not being updated/written at the time, some of these
errors occur at 2am when no one's about. So I'll assume it's because
we're using the default webrick. We currently have only a couple of
dozen clients but that will expand to over 200 in future so I'll look
at switching to mongrel o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bernhard Miklautz wrote:
> Hi,
>
> thanks for your answer.
>
> On 08/19/2010 01:21 AM, Rustler wrote:
>> Just to clarify - the "--onetime" is for testing.
>> On Aug 18, 4:16 pm, Rustler wrote:
>>> Add --onetime
>>>
>>> That works for me.
>
> Onetim
Hi Experts,
I'm trying to generate my own certificates (all of them, including certs for
CA, server and client) for puppet to use.
and I'm getting "Could not run: Could not retrieve certificate for puppetsrv
and not running on a valid certificate authority"
Just wondering what the problem could
On Aug 19, 4:04 am, Dennis Hoppe
wrote:
> Hello,
>
> i have written some modules for Puppet and would be thankful, if someone
> could take a look for quality enhancements.
>
> http://194.94.79.17/hotkey/puppet.tar.gz
>
> The only nasty part is, that i have defined some global variables at
I'm still having a big problem trying to get schedule{} and the --
onetime command-line option to play nice together. This is on 0.24.8,
but also seem to have the issue with 0.25.4.
I have a custom schedule in my manifest:
schedule { development:
range => "05:00 - 23:59", repeat => 12, p
I have a script that does it..
Looks like the script is from James Turnbull and you can find it in the ext
directory:
http://projects.reductivelabs.com/projects/puppet/repository/revisions/master/raw/ext/puppetstoredconfigclean.rb
I also added a wrapper that removes the certificates form the pupp
On Thu, Aug 19, 2010 at 4:39 AM, Tim wrote:
> The relevant definition from /etc/puppet/manifests/site.pp is:
> # Generic config file
> define config-file ($fullpath, $source, $mode = '644') {
>file { $fullpath:
>source => "puppet://puppet.hq.eso.org/modules/${source}",
>ba
Hi,
I have stored configs with a Postgresql back end - for some reason, one
host, and all it's associated resources, is duplicated. I haven't got a
clue how, but it's causing errors using exported resources.Is there a
safe way to remove a host from stored config? I note from
http://projects
I was getting errors like this before I switched from webrick to nginx/
mongrel.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
p
On Aug 19, 2010, at 4:04 AM, Dennis Hoppe wrote:
> Hello,
>
> i have written some modules for Puppet and would be thankful, if someone
> could take a look for quality enhancements.
>
> http://194.94.79.17/hotkey/puppet.tar.gz
>
> The only nasty part is, that i have defined some global v
On Aug 19, 2010, at 2:38 AM, Craig Dunn wrote:
>
> By any chance, does the "source" parameter supports HTTP URLs, if not
> then how can i do that in Puppet ?
>
>
> Source currently only supports the "file" and "puppet" URI types, you could
> accomplish a few ways, one is with a simple exec.
Instead of the case statements in init.pp, I do something like this:
if defined("foo::$release") { include "foo::$release" }
... not necessarily a "quality enhancement," but it saves on the
typing.
On Aug 19, 7:04 am, Dennis Hoppe
wrote:
> Hello,
>
> i have written some modules for Puppet and w
I'm using 2.6.1rc1 (source from github) for the puppetmaster and 0.25.5 (rpm
from epel) for my clients and haven't noticed any problems.
On Thu, Aug 19, 2010 at 2:55 AM, Darren Worrall wrote:
> Thanks Dan.
>
> Are people using 0.25.x clients with a 2.6 master in the wild ok? I'm
> open to trying
Hello,
i have written some modules for Puppet and would be thankful, if someone
could take a look for quality enhancements.
http://194.94.79.17/hotkey/puppet.tar.gz
The only nasty part is, that i have defined some global variables at the
site.pp, which i am using at several templates
> By any chance, does the "source" parameter supports HTTP URLs, if not
> then how can i do that in Puppet ?
>
>
Source currently only supports the "file" and "puppet" URI types, you could
accomplish a few ways, one is with a simple exec
exec { "wget http://myurl.com/file.txt -o /path/to/fil
Hi,
On Thu, Aug 19, 2010 at 6:39 PM, Tim wrote:
> puppetd[7303]: (//munin/Config-file[muninnode]/File[/etc/m
> unin/munin-node.conf]) Failed to retrieve current state of resource:
Are you using the built-in webrick server that comes with Puppet or
have you switched to either Mongrel or Passenger
I get errors like this randomly on some of my puppet clients:
puppetd[7303]: (//munin/Config-file[muninnode]/File[/etc/m
unin/munin-node.conf]) Failed to retrieve current state of resource:
Could not
retrieve file metadata for puppet://puppet.hq.eso.org/modules/munin/munin-node.c
onf: at /etc/pup
Hi,
thanks for your answer.
On 08/19/2010 01:21 AM, Rustler wrote:
> Just to clarify - the "--onetime" is for testing.
> On Aug 18, 4:16 pm, Rustler wrote:
>> Add --onetime
>>
>> That works for me.
Onetime doesn't help me. I want to use it in production with the agent
running in background.
Bas
Thanks Dan.
Are people using 0.25.x clients with a 2.6 master in the wild ok? I'm
open to trying 2.6 on the master(s) but maintaining 2.6 agents would
be a bridge too far at this stage.
On Aug 18, 5:33 pm, Dan Bode wrote:
> This feature is not supported until 2.6 (and I have seen some issues wit
19 matches
Mail list logo
