Am Donnerstag, 27. November 2014 14:40:04 UTC+1 schrieb Ken Barber:
> > i know that PuppetDB is the way to go for the future but currently i am
> > forced to use Puppet 2.7 with the Stored Configuration feature.
> > So the problem is that whenever i restart the PostgreSQL database or the
> > networ
On 2014-22-11 22:11, Felix Frank wrote:
On 11/21/2014 04:16 PM, Larry Liu wrote:
Hi everyone,
According to puppetlab's doc, parser=future is supposed to work with
puppet version 3.5 or higher. I'm on 3.7.1 which falls under
https://docs.puppetlabs.com/puppet/latest/reference/experiments_future.
> i know that PuppetDB is the way to go for the future but currently i am
> forced to use Puppet 2.7 with the Stored Configuration feature.
> So the problem is that whenever i restart the PostgreSQL database or the
> network service, the Puppet Master running under Apache with Passenger does
> not
Hello,
Nearly everything is in the title.
When I manually run a puppet agent --test on a host (let's say "host1")
that export @@something, I can get "something" on another host (let's say
host2) and I'm happy.
Later, when the daemon on host1 runs, it still exports @@something but
custom facts
hi,
i know that PuppetDB is the way to go for the future but currently i am
forced to use Puppet 2.7 with the Stored Configuration feature.
So the problem is that whenever i restart the PostgreSQL database or the
network service, the Puppet Master running under Apache with Passenger does
not re
Thanks for the reply ,
After 3 days I think it working ,I just use command line "puppet agent -t"
and it does not shows any error.
Info: Retrieving pluginfacts
Info: Retrieving plugin
Info: Caching catalog for pupagent.kollect.my
Info: Applying configuration version ''
Notice: Finished catalog ru
