RG, typically the Duplication declaration message is followed by some
indicator of the file where it is duplicated and the line number. Are you
receiving that information and maybe snipped it off the end of the message
you included? An alternative might be any sort of `hiera_include()` or
>Henrik Lindberg writes:
>> On 03/10/16 15:48, jcbollinger wrote:
>> The behavior you describe seems buggy to me, but your manifests are also
>> unusual. Specifically, it is strange for test/manifests/init.pp to
>> contain a top-scope declaration. It is especially
I installed the puppet module saz-rsyslog from puppet forge.
I use The Foreman to configure nodes. The Foreman is used by puppet via
configuration [master] "external_nodes" "/etc/puppet/node.rb"
Since the saz-rsyslog module install, I have been receiving the following
error off and on (not
Puppet Server is currently using JRuby from its 1.7.x release line, fixed
to emulate MRI Ruby version 1.9. Eventually, we hope to be able to have
Puppet Server use the JRuby 9000 line, which intends to be compatible with
MRI Ruby 2.x. SERVER-1586
for the code manager replacement we use r10k, nfs share, ssync, and
gitlab-ce with webhooks. we stopped using mcollective
On 26 April 2016 at 14:08, Geoff Galitz wrote:
>
> Thanks for your replies.. much appreciated.
>
> -G
>
>
>
> On Thu, Apr 21, 2016 at 3:40 PM, Ryan
On Tuesday, October 4, 2016 at 6:55:36 AM UTC-5, Prunk Dump wrote:
>
> Hello puppet users !
>
> My problem is simple. I use the following classes in three different
> stages (setup/main/runtime) :
>
> class { 'apt::client':
> stage => 'setup',
> }
> ...
> ...
> class { 'hostpkg': }
> ...
I need to set up a PXP Agent and i have few questions:
- Is any good documentation online for pxp agent?
- what doing in pxp agent pcp broker and pcp client is the pcp broker
something like middleware in mcollective and pcp client is something like
mcollective client?
- what is required for set
I forgot to say I'm on CentOS 6.8
Op woensdag 5 oktober 2016 11:08:03 UTC+2 schreef yamaka...@gmail.com:
>
> Hi Guys,
>
> I have updated my 3.8 to the 4.0 packages and all seems to go quite smooth
> unless the puppetdb pid file
>
> Anyone a clue why this happens ?
>
> [root@foreman-01 puppetdb]#
Hi Guys,
I have updated my 3.8 to the 4.0 packages and all seems to go quite smooth
unless the puppetdb pid file
Anyone a clue why this happens ?
[root@foreman-01 puppetdb]# /etc/init.d/puppetdb restart
Stopping puppetdb: [ OK ]
Starting puppetdb: