Thanks for the quick reply!
yes, I actually thought that feature got removed since it's not usuable and
> never really worked at all.
>
> Don't use it.
>
It seems to work okay most of the time, as far as I can tell. The trouble
comes
if it is used when the daemon is:
1) Still getting initial
- Original Message -
> From: "Lorcan Hamill"
> To: "puppet-users"
> Sent: Thursday, November 19, 2015 10:41:34 AM
> Subject: Re: [Puppet Users] mcollective reload-agents unreliable?
> Thanks for the quick reply!
>
> yes, I actually thought that feature got removed since it's not usuab
>
> it really doesn't, in ways you cant even see or debug and cannot work.
> Don't use it.
>
> Only option is to restart the daemon.
>
Okay, we'll just have to figure out a way to live with that, I guess.
Thanks.
--
This email and any files transmitted with it are confidential and intended
It works now. Thanks for your informative answers.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discus
Hi,
using Puppet4 together with a PostgreSQL-backed PuppetDB to store
reports. We have some exec resources that don't show up in the reports
stored in PuppetDB (but in the "puppet agent" output as well as
last_run_report.yaml).
These particular exec resources emit lots of console output. Could th
Hi Dirk-
Yes, the regular eyaml commands work,edit mode output is in the pastebin.
puppetserver.log entry below, which i see as consistent with what i see
with the puppet run.. that it sees a string. The sting would be an array if
only it got decrypted. :)
2015-11-18 11:49:40,481 ERROR [puppet-
Hello,
I am testing the puppet forge module hiera-mysql. It works well but if I
search for value that includes dots than parameter is truncated. See an
example below.
Here you can see my hiera.yaml config.
hiera.yaml
---
:backends:
- mysql
:mysql:
:host: dbserver
:user: dbusr
:pas
hello,
Does anyone know if puppet lookup is supposed to work in a non master
based setup?
Running puppet lookup --node some.node some::key results in messages about
Warning: Host is missing hostname and/or domain: some.node
This is as seen in https://tickets.puppetlabs.com/browse/PUP-5519 and
Yes, permissions are proper.
-thanks
On Thursday, November 19, 2015 at 2:07:01 AM UTC-5, Angel L. Mateo wrote:
>
> Does the user running puppet has permisissions for the certificate
> files?
>
> El 19/11/15 a las 00:19, raycharlesistheman escribió:
> > Hi and thanks for taking a look-
I have a beaker hosts file that looks like this:
HOSTS:
debian-8:
platform: debian/jessie
image: debian:8
hypervisor: docker
CONFIG:
type: foss
when I run beaker --hosts it chokes on every permutation of debian platform
designation I can think of with this sort of error message:
Thanks for the help it resolved now.
[root@abscpptm01p ~]# puppet agent -t
Info: Retrieving pluginfacts
Info: Retrieving plugin
Info: Loading facts
Info: Caching catalog for abscpptm01p.svmintranet.com
Info: Applying configuration version '1447968906'
Notice: Applied catalog in 0.10 seconds
The t
I think you need a dash in there, not a slash, like:
debian-jessie
The code is here:
https://github.com/puppetlabs/beaker/blob/master/lib/beaker/platform.rb
One thing that can help with Beaker stuff is looking at examples like the
modules in the puppetlabs space.
Rich
On Thu, Nov 19, 2015 at
On 11/19/15 6:25 AM, Dirk Heinrichs wrote:
Hi,
using Puppet4 together with a PostgreSQL-backed PuppetDB to store
reports. We have some exec resources that don't show up in the reports
stored in PuppetDB (but in the "puppet agent" output as well as
last_run_report.yaml).
These particular exe
Outage on apt.puppetlabs.com (and then yum.puppetlabs.com)
Timeline:
First reports of issues: 17 Nov 2015 1939GMT
Resolved at: 17 Nov 2015 2051GMT
Impact: users attempting to get packages from apt.puppetlabs.com were
unable to in a vast majority of cases for the duration of the outage.
Severa
Puppet Server 2.2.0 is now available.
This is a feature release which, based on contributions from Brice
Figureau, introduces a new Clojure-based auth.conf for Puppet Server. This
initiative was previously described in the "RFC 22: HTTP Authorization
Framework" thread here:
https://groups.goog
Am 19.11.2015 um 23:59 schrieb Wyatt Alt:
> do you have a shareable manifest that will reproduce the issue?
Unfortunately not. It installs our inhouse SW... What about a simple
manifest which exec's a script that just prints 1 or 2 thousand lines to
stdout.
Bye...
Dirk
--
*Dirk Heinrichs*
16 matches
Mail list logo
