:
>
>
> On Mon, Feb 10, 2020 at 1:44 AM Martijn Grendelman
> mailto:mart...@grendelman.net>> wrote:
>
> Hi Kevin and others who have responded,
>
> Thanks all for your tips. Unfortunately, no breakthroughs yet.
>
> The current state is this:
>
>
, seems to confirm this.
So:
- enough CPU power (I would think)
- enough memory
- no significant garbage collection
- Puppetserver causing a load of 5
Any more tips? Would it make sense to run PuppetDB and PostgreSQL on a
different VM?
Thanks,
Martijn Grendelman.
Op 6-2-2020 om 17:43
,
Martijn Grendelman
--
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 discussion on the web vi
Since a recent Puppet update, my logs contain a lot of these warnings:
2017-08-21 14:03:20,146 WARN [qtp2051525912-14813] [puppetserver] Puppet
> Attempt to override an already evaluated resource, defined at
>
Hi Henrik and Wil,
Is there ANY way that the notifys in the apache::vhost type would
display a different value? Shouldn't $apache::params::priority and
$priority not be the same?
I have a case where on /some/ nodes, $priority (and other parameters
that have defaults from
On Thursday, December 4, 2014 9:50:56 AM UTC+1, Martijn Grendelman wrote:
Hi Henrik and Wil,
Is there ANY way that the notifys in the apache::vhost type would
display a different value? Shouldn't $apache::params::priority and
$priority not be the same?
I have a case where
Hi,
Please consider the following simplified code:
class apache::params {
$priority = 25
}
define apache::vhost (
$priority = $::apache::params::priority
) {
include apache::params
notify { $name prio 1: $apache::params::priority: }
notify { $name prio 2: $priority: }
}
apache::vhost {
which suggests to do something like
% aliases.sort_by {|key, value| key}.each_pair do |key, val| -%
% end -%
Will it work? Is that a proper solution?
Thanks!
Martijn Grendelman
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post
No one? Is my question not clear (TL;DR, perhaps?), or doesn't anyone have
an answer?
Best regards,
Martijn.
On 17-11-11 17:18, Martijn Grendelman wrote:
Hi,
A small addition at the bottom...
I was looking at the basic example for exporting and collecting resources
at http
to virtualize vhost in vhost.pp with @
and realize them in the node config, but seems i cant get a working
solution to use vhost resource type more than 1.
Can you point me to the right direction? How can i create 100 vhost with
that defined class or something like this
Best regards,
Martijn
of
having hostgroups is, that multiple hosts can be a member :-) So, the
collection would lead to duplicate definitions. Is there a way to avoid that?
Best regards,
Martijn Grendelman
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post
by looking at the database). So does
collecting, only not from the local node. What am I doing wrong?
Best regards,
Martijn Grendelman
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-users
curious...
Best regards,
Martijn Grendelman
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr
On 17-11-11 11:51, Martijn Grendelman wrote:
Hi,
Is there a way to 'unique-ify' a collection of resources?
Suppose that nodes export '@@nagios_hostgroup' resources for hostgroups
that they want to be a member of. The Nagios server node collect those:
Nagios_hostgroup ||
But many
:
Oct 18 09:02:13 dolly puppet-master[31443]: Report processor failed: Could
not create RRD file
/var/lib/puppet/rrd/server011.dev.iphion.nl/changes.rrd: you must define
at least one Data Source
Any idea what I could do to fix this?
Best regards,
Martijn Grendelman
--
iphion B.V.
TU/e Innovation
On 14-10-11 20:14, Nigel Kersten wrote:
On Fri, Oct 14, 2011 at 11:11 AM, Jacob Helwig ja...@puppetlabs.com
mailto:ja...@puppetlabs.com wrote:
On Fri, 14 Oct 2011 10:04:19 -0700, Nigel Kersten wrote:
On Fri, Oct 14, 2011 at 7:05 AM, Martijn Grendelman
mart
,
Martijn Grendelman
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit
into the source revealed to me, that this feature is not
present in 2.6.3, but it is in 2.7.5. I have no idea in what version it
was introduced.
It would be nice if the type reference would contain that information.
Best regards,
Martijn Grendelman
--
You received this message because you
it being added repeatedly on every
catalog run, but apart from that? I have never had any problems with it.
If whitespace is permitted from OpenSSH's point of view, shouldn't Puppet
allow it too, and fix problems like this the right way? Or am I missing
something?
Best regards,
Martijn Grendelman
[1
On 29-09-11 14:03, Jonathan Stanton wrote:
On Sep 29, 2011, at 7:35 AM, Martijn Grendelman wrote:
Hi,
I am currently testing my catalog, that runs fine with 2.6.3, with Puppet
2.7.4. Now I am running into a problem, and I wonder why this was 'fixed'
in Puppet the way it was.
Please
Hi,
I have this:
service { bind9:
ensure = running,
hasrestart = true,
pattern = named,
require = Package[bind9],
}
because the process is called 'named'.
Best regards,
Martijn Grendelman
On 31-08-11 22:56, Russell Van Tassell wrote:
Just
sources. I've combined this with a YAML-based ENC to put all variables for
a single node into one YAML file. It's working well for me.
but then, you should better directly go with hiera.
I'm currently checking my mileage with Hiera...
Thanks for all your input!
Best regards,
Martijn
of
parameters you need to pass, or even to avoid class parameterization
altogether. I think this is a great way to go, but Puppetlabs's style
guide disfavors it.
The big question here is: would that be future-proof??
Best regards,
Martijn Grendelman
--
You received this message because you
does what
you tell it to: install a single deb package. APT is made for what you want.
Due to security reasons i cant enable repo urls in my /etc/apt
sources-list file.
You could install the dependencies with 'package' resources, and have the
dpkg-exec depend on those.
Best regards,
Martijn
Hi,
Having installed Puppet 2.7.1 on my testserver yesterday, I am now bugged
by log messages, that tell me not to use dynamic variable lookups:
Jun 29 13:31:09 os1 puppet-master[31910]: Dynamic lookup of
$ssh_permitrootlogin at /etc/puppet/templates/etc/ssh/sshd_config.erb:28
is deprecated.
for = 4G, 2G otherwise
if $mem = 4294967296 {
$shmmax_final = $mem / 2
} else {
$shmmax_final = $mem - 2147483648
}
} else {
$shmmax_final = $mem
}
}
Best regards,
Martijn Grendelman
--
You
mailto:ch...@untrepid.com wrote:
On 8 June 2011 13:30, Martijn Grendelman mart...@iphion.nl
mailto:mart...@iphion.nl wrote:
Hi,
i want to archive the following:
i define an exported
On 09-05-11 14:29, Jeff wrote:
Is it possible to extend 'package' without actually hacking the puppet
code. I'd like to do this:
package { httpd:
name= httpd,
ensure = present,
check = newer,
}
My goal is this. For every package I have in puppet, I'd like to check
to see
On 15-04-11 10:20, Sans wrote:
Thanks Patrick!
Where can I get the list of attributes and their predefined values?
Cheers!!
The type reference:
http://docs.puppetlabs.com/references/latest/type.html
On Apr 15, 9:12 am, Patrick kc7...@gmail.com wrote:
For the package example, I'd try
On 14-03-11 22:31, Brandon Metcalf wrote:
I'm using the module https://github.com/sansnoc/puppet/tree/master/users
but running into a problem where puppet can't find a class. In /etc/
puppet/manifests/nodes.pp I have
node basenode {
include hosts
include groups::namidev
include
Hi,
I have a type named apt::package, that installs packages on Debian base
systems. By default, it sets the schedule to something I defined, to
prevent package updates from happening outside maintenance hours.
Now, in a specific class, I do this:
# This is normally a manual puppet run, so
Hi Nick,
I've tried to achieve my overall goals with several different features
of Puppet, but I've hit a bit of a wall here. I think it's time for me
to explain what I'm trying to accomplish:
I want the enabling of a service in my manifests to configure
the monitoring of that
Hi,
Yesterday I implemented a module for managing Nagios configurations. It
has turned out to be quite a complex beast, but in my test environment, it
seemed to do everything it should.
Now, in production, managing some 30 hosts, I get the following on the
node that is both Puppetmaster and
On 10-03-11 12:49, Martijn Grendelman wrote:
Hi,
Yesterday I implemented a module for managing Nagios configurations. It
has turned out to be quite a complex beast, but in my test environment, it
seemed to do everything it should.
Now, in production, managing some 30 hosts, I get
Hi,
On 10-03-11 13:46, Martijn Grendelman wrote:
Yesterday I implemented a module for managing Nagios configurations. It
has turned out to be quite a complex beast, but in my test environment, it
seemed to do everything it should.
Now, in production, managing some 30 hosts, I get
Hi,
Yesterday I implemented a module for managing Nagios configurations. It
has turned out to be quite a complex beast, but in my test environment, it
seemed to do everything it should.
Now, in production, managing some 30 hosts, I get the following on the
node that is both Puppetmaster and
On 10-03-11 14:39, Martijn Grendelman wrote:
but the error remains.
Pointers still very much appreciated!!
I am very sorry for the noise. The error was the result of a patch that I
recently added to my Puppetmaster, to allow Nagios_* parameters to be
specified as arrays. Stupid.
Best regards
Hi,
I run the Puppetmaster with
storeconfigs = true
thin_storeconfigs = true
dbadapter = mysql
So far, this has been working perfectly, but today I noticed something
odd. Yesterday, I upgraded one of my nodes from Ubuntu Jaunty to Lucid,
but the facts from this node aren't updated in the
After completely deleting the node from the database's 'host' table and
resources that referenced its host_id, a following catalog run refreshed
the database, adding all facts with their current values...
Best regards,
Martijn.
On 04-03-11 12:43, Martijn Grendelman wrote:
Hi,
I run
Hi,
A question for the devs. Will this:
http://projects.puppetlabs.com/issues/4020
make it into a release any time soon?
Best regards,
Martijn.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to
at ...
which sounds logical, but...
Is there any way to do what I want? I can't really think of anything,
since (variable) scoping will always be in my way, as far as I can see...
Best regards,
Martijn.
On Wed, Mar 2, 2011 at 5:15 AM, Martijn Grendelman mart...@iphion.nl
,
Martijn.
On 02-03-11 15:55, Martijn Grendelman wrote:
On 02-03-11 14:49, Brian Gallew wrote:
Sadly, signs point to no.
Too bad. But since I run a patched Puppetmaster anyway, I can do what I
want :-)
Unfortunately, it doesn't solve my problem.
I am trying to do the same thing
On 03-03-11 08:04, Gabriel Filion wrote:
On 11-03-02 02:27 PM, Brian Gallew wrote:
I've found that Puppet/Naginator has the bad habit of occasionally
breaking the Nagios config. Here's how I worked around this: 1) When
you collect your Nagios resource, store them all in a temporary
directory
Hi,
I have one Puppet agent (2.6.3 on Ubuntu) that sometimes does not seem to
survive a reload (SIGHUP). The agent is reloaded by 'logrotate' every
morning, and usually this works OK, but just sometimes, puppetd gives up,
without writing anything extraordinary to syslog (without any debug
in various
conf file settings, so clearly the underlying ruby makes this possible.
I'll think about this code you've pasted. Thanks!
Would you be so kind to post the solution you cho(o)se in the end? I am
interested in this too.. Thank you!
Best regards,
Martijn Grendelman
--
You received
Please step into my office, and I'll remove you :-)
Or look at the mail headers and take appropriate action:
List-Unsubscribe:
http://groups.google.com/group/puppet-users/subscribe?hl=en_US,
mailto:puppet-users+unsubscr...@googlegroups.com
Regards,
Martijn.
On 25-01-11 07:48,
Hi,
All that being said, if its just one or two packages you care about you can
simply add a fact for the package versions, but this fact will only show the
version on the next puppet run not the one during which you install said
package
since the compile stage of the puppet run is
Hi,
On 10-01-11 14:34, Adam Ryczkowski wrote:
I like the idea of parametrized classes very much, and I would like to
use them. Unfortunately Ubuntu Lucid ships with puppet 2.5.4, which
doesn't support it. Does anybody here can tell me, how can I get 2.6.x
version of puppet and puppetmaster on
On 10-01-11 14:47, Martijn Grendelman wrote:
... Ubunutu packages ...
Damn. I STILL can't type 'Ubuntu' properly. Just use Debian, it's easier :-)
Regards,
Martijn.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send
On 27-12-10 17:13, James Turnbull wrote:
Martijn Grendelman wrote:
On 24-12-10 16:47, Martijn Grendelman wrote:
Hi,
Today, I set up 'rrdgraph' reports. What could be the cause of this:
Dec 24 15:52:35 offman01 puppet-master[20593]: Report rrdgraph failed:
Could not create RRD file
/var
On 27-12-10 15:05, Felix Frank wrote:
On 12/27/2010 02:54 PM, Martijn Grendelman wrote:
Hi,
In one of my modules, I have the following:
exec { /bin/sed -i '\~^${line}$~d' '${file}':
The '\~' is there, to make sed use '~' as the command separator instead of
'/', which is too common
Hi,
Today, I set up 'rrdgraph' reports. What could be the cause of this:
Dec 24 15:52:35 offman01 puppet-master[20593]: Report rrdgraph failed:
Could not create RRD file
/var/lib/puppet/rrd/talk.dev.iphion.nl/changes.rrd: you must define at
least one Data Source
I think this is an RRD bug
On 24-12-10 16:47, Martijn Grendelman wrote:
Hi,
Today, I set up 'rrdgraph' reports. What could be the cause of this:
Dec 24 15:52:35 offman01 puppet-master[20593]: Report rrdgraph failed:
Could not create RRD file
/var/lib/puppet/rrd/talk.dev.iphion.nl/changes.rrd: you must define
Hi,
In one of my modules, I have the following:
exec { /bin/sed -i '\~^${line}$~d' '${file}':
The '\~' is there, to make sed use '~' as the command separator instead of
'/', which is too common in the lines I am trying to delete.
However, the puppet master now complains:
Dec 27 14:07:11
Hi,
In one of my modules, I have the following:
exec { /bin/sed -i '\~^${line}$~d' '${file}':
The '\~' is there, to make sed use '~' as the command separator instead of
'/', which is too common in the lines I am trying to delete.
However, the puppet master now complains:
Dec 27
Hi,
Today, I set up 'rrdgraph' reports. What could be the cause of this:
Dec 24 15:52:35 offman01 puppet-master[20593]: Report rrdgraph failed:
Could not create RRD file
/var/lib/puppet/rrd/talk.dev.iphion.nl/changes.rrd: you must define at
least one Data Source
This happens for some nodes, but
Hi,
At http://docs.puppetlabs.com/references/latest/report.html#tagmail I read:
You must have the Ruby RRDtool library installed ... This package may
also be available as ruby-rrd or rrdtool-ruby in your distribution’s
package management system
Maybe it can be noted in the text, that on Debian
Hi,
I was aware of the 'Contribute' page, and it does indeed seem like a lot
of work, even for a reasonably experienced Git user like myself. I will
file a documentation bug. Thanks.
Regards,
Martijn.
On 22-12-10 16:54, Disconnect wrote:
Wait, lets see if I understand the requirements for a
Hi,
I haven't followed the entire discussion, but one small thing caught my
attention:
On 14-12-10 19:15, Rameses Mss wrote:
In your base node (i.e., top level inheritance) set a default:
node base {
$sshd_type=client
include sshd
}
node myclient inherits base {
}
node
Hi,
On Mon, Dec 13, 2010 at 12:56 PM, Yushu Yao y...@lbl.gov
mailto:y...@lbl.gov wrote:
Another though:
Can I do something like
if $(return value of an Exec resource)==0 {
} else {}
I.e. I want to run an shell command first, and do something depend on
the
On 09-12-10 09:44, Hubert Krause wrote:
Hello,
Am Wednesday 08 December 2010 22:22:10 schrieb Patrick:
What distro are you using?
CentOS and Debian. New server will always be Debian. Our Puppet Server is
CentOS at the moment.
Why not just install Augeas when you install puppet?
I made a small mistake. Please see at the bottom.
On 09-12-10 15:30, Martijn Grendelman wrote:
An example: add the following to
puppet_path/modules/modulename/lib/facter/augeas_available.rb
-- cut here --
require 'facter'
Facter.add(augeas_available) do
setcode do
On 08-12-10 21:10, Jason Lavoie wrote:
On 12/08, Martijn Grendelman wrote:
I would like to have the possibility to tell Puppet to queue the trigger,
and when the currently running catalog run is finished, process it and do
another run.
Does this sound like a good idea?
I thought so
On 08-12-10 11:19, Leonko wrote:
Hello,
Anybody know how I can make checking file for verify for size/md5sum
and if it not equal my value rewrite it from server.
There may vriant than simple: file { /my/file: ensure = present,
checksum = true,source = puppet:///files/file}
?
Isn't that
Hi,
I'm sorry, this may not be the response you are waiting for.
Unfortunately, I have only questions to add...
I'm experimenting with converting some of my live puppet content to
Ruby DSL and have found a few gaps I wouldn't mind some advice on. I'm
not sure how many of you have already
Hi,
The lastest Puppet package in Ubuntu Natty /depends/ on libaugeas, rather
than merely recommending it, like it used to, up to and including version
2.6.1.
Is there a strict reason for this from Puppet's point of view? If not,
I'll see if I can harrass the Ubuntu maintainer about this :-)
specific
about the day does not seem possible.
Thanks, that's what I thought.
I have created a custom fact named 'wday', that returns 'Date.today.wday',
so I can test for '$wday 0 and $wday 6'.
Ugly, but it works.
Regards,
Martijn.
On Dec 2, 9:46 am, Martijn Grendelman mart
regards,
Martijn.
On 11/30/10 6:43 AM, Martijn Grendelman wrote:
Hi,
Today, while working on some functions in Puppet, I got back lots of
unexpected results. Lots of times, it seemed like my changes in the code
were not picked up when I re-ran the test-classes.
Even functions that I
Hi Trevor,
More likely just adding
usecacheonfailure = false
to the [puppetd] stanza in /etc/puppet/puppet.conf will help.
I am yet unfamiliar with that option, but just as a remark, there was
really no 'failure' involved here, it was just that enhancements to my
code weren't picked up,
with manifest
changes too? Unfortunately, I've not done enough troubleshooting to
narrow down the cause. I don't know if these issues are related, but
thought I would suggest it.
Thanks,
Martijn.
On Wed, Dec 1, 2010 at 7:33 AM, Martijn Grendelman mart...@iphion.nl
mailto:mart
Hi,
Today, while working on some functions in Puppet, I got back lots of
unexpected results. Lots of times, it seemed like my changes in the code
were not picked up when I re-ran the test-classes.
Even functions that I removed from the code, after using them once or so,
kept working after
Hi puppeteers,
In the function reference [1], I found a 'split' function for splitting a
string into an array, but not a 'join' function for joining an array into
a string. Why not? :)
I have a list of IP addresses, that I use with ssh_authorized_key to
restrict access. The list is now simply a
On 09-09-10 11:50, R.I.Pienaar wrote:
In the function reference [1], I found a 'split' function for
splitting a
string into an array, but not a 'join' function for joining an array
into
a string. Why not? :)
I have a list of IP addresses, that I use with ssh_authorized_key to
restrict
Hi,
But for this to work, the Puppet run needs to run aptitude update to
pick up the new package name. Running the update periodically isn't
enough, but running an update on every catalog run is just overkill.
I understand your concern here, but have you done the timing tests?
How long
Hi,
I have create the following module:
modules/foo
`-- manifests
|-- definitions
| `-- line.pp
`-- init.pp
$ cat modules/foo/manifests/init.pp
import definitions/*.pp
$ cat modules/foo/manifests/definitions/line.pp
define myline($file, $line, $ensure = 'present') {
}
I
On 07-09-10 14:41, R.I.Pienaar wrote:
You define should be:
define foo::myline { }
and it should be in modules/foo/manifests/myline.pp
Is the way I am trying to do things supposed to work?
nope,
What is the reason that this doesn't work? Is it an issue with
loading order?
On 07-09-10 16:34, James Turnbull wrote:
Martijn Grendelman wrote:
It's probably my own lack of brainpower, but I feel the Puppet
documentation could use some more elaborate examples here and there.
Patches welcomed!
http://github.com/reductivelabs/puppet-docs
I had a feeling
Hi,
What does this error mean?
Sep 7 17:15:54 racey puppet-agent[3291]:
(/Stage[main]/Sysctl/Sysctl[kernel.shmmax]) Could not evaluate: No ability
to determine if sysctl exists
I don't know where to start looking. If I should post my configuration,
please let me know.
Best regards,
Martijn.
On 07-09-10 17:29, Martijn Grendelman wrote:
Hi,
What does this error mean?
Sep 7 17:15:54 racey puppet-agent[3291]:
(/Stage[main]/Sysctl/Sysctl[kernel.shmmax]) Could not evaluate: No ability
to determine if sysctl exists
I don't know where to start looking. If I should post my
M C schreef:
We would like to avoid pre-scheduled updates in our production environment
by puppet. The solution I've come across is to instruct the puppet agent
not to update on a schedule and instead use puppet kick from the puppet
master to force updates when we're ready to deploy them. I
On 05-09-10 12:02, Marcin Owsiany wrote:
On Tue, Aug 31, 2010 at 04:03:35PM +0200, Martijn Grendelman wrote:
What I would like, is for Puppet to run `aptitude update` before it
installs or upgrades packages.
FYI you're likely to encounter problems when using aptitude provider for
package
Hi Nigel Kersten,
Thank you for your elaborate answer. I am not sure how to proceed, though...
What I would like, is for Puppet to run `aptitude update` before it
installs or upgrades packages. That doesn't seem out of the ordinary to
me, but I can't make it work in Puppet.
The approach I
Mathias Gug schreef:
I am not sure how I said I want to do an update before /every/ package
install. Once at the start of a Puppet-run, /IF/ one or more packages
need to be installed, would suffice.
You may run into a chicken-egg problem. Packages that are configured as
ensure = latest can
83 matches
Mail list logo
