I would see a principle whereby nodes should not ever be defined within
the manifest code at all. To me the manifests should be written to be very
generic, and then use ENC's to modify their behaviour at a "user" level.
There is still a lot of inconsistency within Puppet as to how device
specific d
Hi,
I've seen some weird behaviour using extlookup, and wondered if anyone has
seen it too...
Basically it seems that if the $extlookup_* variables are defined in site.pp
then an early stage use of extlookup doesn't see these variables at all, yet
main stage ones do. I added some debug statements
Well that's odd, I was looking at the exact same issue this morning for
sysctl.conf / oracle stuff.
But why are people writing new facts?? Why not just take a copy of the
original function and simply not run the function that normalizes the
number? It seems very odd to make a more limited version
l =~ /^(?:Buffers|Cached):\s+(\d+)\s+\S+/
memsize_raw += $1.to_i
end
end
end
memsize_raw
end
end
end
Thanks
Chris
On 30 June 2011 13:29, Chris Phillips wrote:
>
> Well that's odd, I was looking at the
Hi,
I've a puppet module running which ensures the puppet service is not running
and not starting on boot. A few times a few different nodes have become
stuck, apparently always thinking that the service is running when it is
not. The following below excerpt just goes round and round run after run
I wasn't aware of that layout of the syntax, that's a really interesting way
of writing it. The OP would seem to want "blocks" added to this though. This
is all very reminiscent of Stages though, so surely if there IS a solution
that satisfies the original need it would be an adjustment to stages.
is absolutely fine, it's just getting implemented wrong sometimes.
Thanks
Chris
On 5 July 2011 10:42, Ken Barber wrote:
> What does your service {} block look like? Are you using hasstatus =>
> true? For example:
>
> service { "puppet":
> ensure => running,
>
On 5 July 2011 14:24, Martin Alfke wrote:
> On 07/05/2011 03:19 PM, Brian Gallew wrote:
> > I was seeing the behavior on my Solaris boxes when running Puppet under
> > SMF. The issue, in my case, was that I was trying to work around an SMF
> > bug. My "workaround" was to "svcadm disable puppetd
Hi,
I was just searching for all systems where "selinux is true" on Dashboard
and firstly I got no results, despite there being some (any clues?) but that
search also seems to have resurrected some nodes I deleted a few weeks ago.
7 systems instantly appeared under "Never reported". I just deleted
On 5 July 2011 16:26, Chris Phillips wrote:
>
>
> On 5 July 2011 14:24, Martin Alfke wrote:
>
>> On 07/05/2011 03:19 PM, Brian Gallew wrote:
>> > I was seeing the behavior on my Solaris boxes when running Puppet under
>> > SMF. The issue, in my case, was tha
On 11 July 2011 14:54, Dominic Cleal wrote:
> On 11/07/11 09:18, Chris Phillips wrote:
> > Coming into work this morning I've seen a bunch of func processes have
> > stopped and puppet is doing nothing at all about it, despite a manifest
> > advising something e
On 14 July 2011 15:00, Todd Zullinger wrote:
> rvlinden wrote:
> > I used to download the Puppet and Facter RHEL5 rpm packages from
> > http://people.fedoraproject.org/~tmz/repo/puppet/epel/
> >
> > but the latest version on that site is puppet 2.6.9 and facter
> > 1.5.9.
> >
> > Does anyone know
This doesn't seem to have been done yet any progress? I'd like to look
at a 2.7.2 upgrade fairly soon and there seems no properly consistent way to
get the RPM's for this.
Thanks
Chris
On 15 July 2011 21:35, Michael Stahnke wrote:
> I'd like to reorganize yum.puppetlabs.com.
>
> As it is,
Our approach is to combine the monitoring and the execution. Totally ditch
the puppet client service and use nagios to run a "check_puppet" script
which does the puppet run and reports the exit codes. This also covers
things like having a defined retry interval, so if puppet runs and there are
no c
My take on it is to run it from our nagios server. What better way to
monitor the puppet runs than by executing that run as part of the check?
retry intervals also help push changes out much quicker if they could take
multiple runs etc.
We also run a single daily cron job.
Chris
On 8 October 201
On 10 October 2011 13:05, Jonathan Gazeley
wrote:
> On 08/10/11 21:22, Chris Phillips wrote:
>
>> What better way to monitor the puppet runs than by executing that run as
>> part of the check?
>>
>
> I assume your Nagios plugin execution timeout must be insanely l
Howdy,
I've been getting this issue for about a month in dashboard. All our
nodes poll on a cronjob between 00:00 and 01:00 daily, but one node
has been getting this as a failed task for a while, with the yaml
files building up on the server. Outside of this one cronjob, other
puppet runs on the s
Hi,
I don't know if I'm just not getting it, but I'm struggling to find
"the" way to elegantly disable a class in its entirety. I am aware of
the foo::disabled conventions, but these are about the disabling of
the end service defined by the class, not the class itself. I'm
looking to have an most
On 5 May 2011 14:04, jcbollinger wrote:
>
>
> On May 3, 3:56 pm, Chris Phillips wrote:
> > Hi,
> >
> > I don't know if I'm just not getting it, but I'm struggling to find
> > "the" way to elegantly disable a class in its entirety. I am
On 5 May 2011 14:52, Felix Frank wrote:
>
>
> Sort of funky, I like it!
First and last time for everything!
It may work, but $exclude_classes should not be a vairable, but a
> parameter to your define instead.
>
> This way, you can override the include_class in a subclass of baseclass
> to set
On 5 May 2011 17:22, Nan Liu wrote:
> On Thu, May 5, 2011 at 9:14 AM, Chris Phillips wrote:
> >
> >
> > On 5 May 2011 14:04, jcbollinger wrote:
> >>
> >>
> >> On May 3, 3:56 pm, Chris Phillips wrote:
> >> > Hi,
> >> >
&g
Howdy,
Can someone enlighten me as to how I can disable a service *IF* it is
installed? I want to ensure rsyslog is installed and running, which requires
syslogd to not be running, but the only way I can see to enforce this in
Puppet is to remove the sysklogd package, which I'd rather not do, I'd
Hi,
I've got a 2.6.7 server and client setup running pretty nicely in a single
site on a few rhel5 and 6 boxes, and today branched out with a RHEL4 node on
a remote site. This was installing 2.6.7 (and facter 1.5.8) from source due
to the lack of el4 rpms (el5's from yum.puppetlabs.com on all othe
On 12 May 2011 08:01, Ohad Levy wrote:
>
>
>> Anyone using it at all?
>>
> I used too.. but the alternatives were much more appalling...
>
That's quite an impressive typo!
Chris
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this
Howdy,
I've just built a VM where the system clock was 2 hours off. Part of the
puppet manifest is to get NTP going, so the system itself takes care of
itself OK. However I just noticed on Dashboard that the report listed for
the build phase was also two hours off. As such I'm given to assume that
On 13 May 2011 18:46, Patrick wrote:
>
> On May 13, 2011, at 8:36 AM, Chris Phillips wrote:
>
> > Why would you ever want to trust a time stamp from the client instead of
> just using your own time as you receive the report?
>
> In my case, when I run the import rake
On 15 May 2011 20:27, Matthias Saou <
th...@spam.spam.spam.spam.spam.spam.spam.egg.and.spam.freshrpms.net> wrote:
> Dan Bode wrote:
>
> > I have an implementation question:
> >
> > 1. Why are you doing the chkconfig exec:
> >
> > exec { "chkconfig ${title} on":
> > notify => S
Hi,
Is there a general feel on whether puppet should look after its own
client configuration files and service status? I'd not foresee problems
about a "service ensure enabled" for puppetd and a file object for the
puppet.conf but clearly wouldn't want to risk locking ourselves out of the
clients
On 16 May 2011 20:14, Jonathan Gazeley wrote:
> Hi Chris,
>
> We have configured puppet to manage its own puppet.conf on clients, and to
> ensure that puppetd is running on all hosts. However it does not manage
> puppet.conf on the puppetmaster, so if we accidentally mess up the config,
> we won't
On 16 May 2011 20:26, Adam Heinz wrote:
I just refer to the puppetmaster as 'puppet' everywhere and drop an
> entry in /etc/hosts for it. Then if I wanted to migrate off a server,
> I would just hardcode away $servername and $serverip on the old
> puppetmaster to point to the new one, and copy t
On 16 May 2011 21:05, Chris Phillips wrote:
>
>
> On 16 May 2011 20:14, Jonathan Gazeley wrote:
>
>> Hi Chris,
>>
>> We have configured puppet to manage its own puppet.conf on clients, and to
>> ensure that puppetd is running on all hosts. However it d
On 19 May 2011 18:48, Gabriel Filion wrote:
> Hi,
>
> I'm using puppet 0.25.5 and a puppetlast script [1].
>
> [1] : http://humangenomeinfo.com.ar/1.txt/usr/share/puppet/ext/puppetlast
>
> I get a negative checkin time from one node..
>
> UNKNOWN: somenode.fqdn checked in -16 minutes ago
>
> how
On 19 May 2011 20:29, hyzhang wrote:
> We are trying to make puppet to do the some of the kickstart part for
> CentOS installation. The kickstart will prompt for hostname, IP, etc,
> then install the puppet client to the client. From then on, puppet
> would take over.
>
> My question is, how can
Hi,
I've successfully hooked up func to use the puppet certs, mostly nicely. I'm
now looking at using func to perform nagios checks (instead of installing
nrpe, which is more pants than func). Here the nagios service runs as the
nagios user, and so func also runs as that user, I thought I was sort
Sounds like it can't resolve "puppet" from your DNS.
On 27 May 2011 09:14, Sumith Sudhakaran wrote:
> Hi,
>
> When I am trying update from puppet client, getting error like blow
>
> err: Could not request certificate: getaddrinfo: Name or service not known
>
> Please help to solve the same..
>
>
On 8 June 2011 13:30, Martijn Grendelman wrote:
> Hi,
>
> > i want to archive the following:
> >
> > i define an exported ressource for HostX to be monitored in nagios:
> >
> > @@nagios_host { $fqdn:
> > ensure => present,
> > alias => $hostname,
>
generated a list of hostgroups based on that.
>
> On Wed, Jun 8, 2011 at 6:47 AM, Chris Phillips wrote:
>
>>
>>
>> On 8 June 2011 13:30, Martijn Grendelman wrote:
>>
>>> Hi,
>>>
>>> > i want to archive the following:
>&g
vention in the modules to be followed.
On 8 June 2011 15:00, Brian Gallew wrote:
> I solved this in a similar manner. I wrote a custom fact (which
> essentially returned /var/lib/puppet/state/classes.txt) and then a custom
> function that generated a list of hostgroups based on that.
&g
file.each { |line|
if line =~ /^(.+)::nagios-client/
bp_nagios_hostgroups << $1 + " "
end
}
}
next bp_nagios_hostgroups if bp_nagios_hostgroups
end
nil
end
end
On 10 June 2011 02:50, Jacob Helwig wrote:
> On Thu, 09 Jun 2011 18:42:54 -0700, Nigel Kersten wrote:
> >
> > https://projects.puppetlabs.com/issues/7697
> >
> > One problem people producing modules that make use of stages are hitting
> is
> > that it's difficult to create something reusable that
On 10 Jun 2011 07:52, "Jacob Helwig" wrote:
>
> Chris Phillips wrote:
>>
>>
>>
>> On 10 June 2011 02:50, Jacob Helwig wrote:
>>>
>>> On Thu, 09 Jun 2011 18:42:54 -0700, Nigel Kersten wrote:
>>> >
>>> > https://pr
On 10 June 2011 09:06, Brice Figureau wrote:
> On Thu, 2011-06-09 at 18:50 -0700, Jacob Helwig wrote:
> > On Thu, 09 Jun 2011 18:42:54 -0700, Nigel Kersten wrote:
> > >
> > > https://projects.puppetlabs.com/issues/7697
> > >
> > > One problem people producing modules that make use of stages are
>
Hi,
I'm happily aware of the way that there is no concept of unmanaging
something and when this is in the context of a file ownership or whatever,
then that makes sense. But when this is applied to things like nagios
configuration data the principle seems to come unstuck. Or at least, it
seems so
I am using Puppet v5.5.13 and am receiving the following error. Any help
would be appreciated.
*Error: /Stage[main]/Profiles::Base/File[/etc/bashrc]: Could not evaluate:
Could not retrieve file metadata for puppet:///files/etcbashrc: Error 500
on SERVER: Server Error: Not authorized to call fi
pet.com/docs/puppet/6.4/modules_fundamentals.html#files-in-modules>
>
> On Thursday, May 23, 2019 at 10:13:38 PM UTC+2, Chris Phillips wrote:
> I am using Puppet v5.5.13 and am receiving the following error. Any help
> would be appreciated.
>
> Error: /Stage[main]/Profiles::Bas
45 matches
Mail list logo
