Hello,
when I run my puppet agent with --summarize it shows this at the end:
Notice: Finished catalog run in 72.68 seconds
Changes:
Events:
Resources:
Total: 2217
Time:
Filebucket: 0.00
Resources: 0.00
Schedule: 0.00
Apt key: 0.00
Group: 0
gp.net
gpg: keyserver timed out
gpg: keyserver receive failed: keyserver error
This is because the /usr/bin/apt-key command can't connect to the keyserver
without the proxy.
Am Donnerstag, 8. Januar 2015 14:41:21 UTC+1 schrieb jcbollinger:
>
>
>
> On Wednesday, January 7, 2015 3:28:30
Hello,
I have to use a proxy to connect to the internet.
My puppet works fine when I call it manually as root (with http_proxy set).
But the "normal" agent doesn't seem to use the proxy. I always get a
timeout when I try to get a pgp key. Getting the package itself works fine
(but I guess that
Hello,
I'm running a puppetmaster in version 3.7.1 and most of my puppet agents
are kept in the Debian wheezy version (2.7.23-1~deb7u3). This works fine
for me, so from my point of view there is no need to immediately upgrade my
agents, but when I do I would like a way to do this with puppet.
S
e reason the icinga service
doesn't get reloaded. Do I need to add something else to the manifest? The
notification works fine when I add a host.
Thank you,
-- Kai Timmer / em...@kaitimmer.de
--
You received this message because you are subscribed to the Google Groups
"Puppet Users"
2014-10-09 15:20 GMT+02:00 Ken Barber :
>
> No not necessarily, you need to enable resource purging with resources
> like nagios_host:
>
> resources { "nagios_host":
> purge => true,
> }
>
Oh, I just did not now that. My manifest now looks like this:
resources { ["nagios_host", "nagios_servic
What happens if I manually add a (fake) host to my hosts.cfg file. The host
doesn't exist in the puppetdb, because it was never "alive". On the next
puppet run, puppet should remove this "false" entry in my hosts.cfg, right?
Best Regards,
-- Kai Timmer / em...@kaitimmer.de
Am Donnerstag, 9. Oktober 2014 14:10:49 UTC+2 schrieb Ken Barber:
>
> Nope it should work in theory, are you using PuppetDB for this? If so
> in the puppetdb.log you should see a corresponding log entry for the
> deactivate command for that node. Can you grep against your
> puppetdb.log to see
Hello,
I'm using this snippet to build my icinga configuration out of my exported
facts
#Collect the nagios_host resources
Nagios_host <<||>> {
target => "/etc/icinga/puppet.d/hosts.cfg",
require => File["/etc/icinga/puppet.d/hosts.cfg"],
notify => Service[icinga],
}
If I now
