Never run an agent with a higher version than the master. This will not work.
At least not running a 3.x agent against a 2.x master.
Bernd
From: puppet-users@googlegroups.com [mailto:puppet-users@googlegroups.com] On
Behalf Of Axel Bock
Sent: Montag, 15. Juli 2013 14:36
To:
First, put the whole line in single quotes in order to prevent Puppet from
trying to resolve all the dollar signs as variables. Then simply escape all
quotes within your string. I didn't test it, but this should work:
line = 'PROMPT_COMMAND=\'history -a (tee -a ~/.bash_history | logger -t
And as an alternative you also may delete the host and its resources directly
inside the database. It's described here:
http://www.bernd-adamowicz.de/209/removing-hosts-from-stored-configurations/.
Bernd
From: puppet-users@googlegroups.com [mailto:puppet-users@googlegroups.com] On
Behalf Of
No. Never have a higher version of Puppet on your agents than on your master.
Bernd
From: puppet-users@googlegroups.com [mailto:puppet-users@googlegroups.com] On
Behalf Of Balasubramaniam Natarajan
Sent: Donnerstag, 29. November 2012 16:28
To: puppet-users@googlegroups.com
Subject: [Puppet
The versions might be the reason. Never run agents with a higher version than
the master. Try upgrading your master or downgrading your agent. Most
presumably this will solve the problem. If not, just get back to the list.
Bernd
-Original Message-
From: puppet-users@googlegroups.com
The Puppet cookbook is always a good starting point: http://puppetcookbook.com/.
And for your particular problem this is the real world example:
http://puppetcookbook.com/posts/restart-a-service-when-a-file-changes.html
Bernd
From: puppet-users@googlegroups.com
This could be a scope issue. You may want to try $::variable or some other
prefix depending on where this variable actually is defined.
See: http://docs.puppetlabs.com/guides/scope_and_puppet.html
Bernd
From: puppet-users@googlegroups.com [mailto:puppet-users@googlegroups.com] On
Behalf Of
I provided some posts about the health of Puppet agents some time ago. They
might help too. The first one is found here:
http://www.bernd-adamowicz.de/80/monitoring-puppet-part-1/. The others are
linked.
Bernd
-Original Message-
From: puppet-users@googlegroups.com
See:
* http://docs.puppetlabs.com/guides/exported_resources.html or
* http://www.bernd-adamowicz.de/12/puppet-stored-configurations-and-icinga/
Cheers,
Bernd
-Original Message-
From: puppet-users@googlegroups.com [mailto:puppet-users@googlegroups.com] On
Behalf Of Brent Clark
Sent:
On master use:
puppetca --clean your.host.name
On the agent I use this to delete all keys and certificates.
find /var/lib/puppet -name * -type f -exec rm -f {} \;
There might be a more elegant solution.
Regards,
Bernd
Von: puppet-users@googlegroups.com [mailto:puppet-users@googlegroups.com] Im
On 09/14/2012 03:09 PM, jcbollinger wrote:
On Friday, September 14, 2012 6:14:37 AM UTC-5, badamowicz wrote:
The other questions from all of you and finally Den's question, which
was: Are you trying to set any permissions inside that directory
elsewhere in the manifest? made
manage the checkouts of git or svn with
puppet as well.
I wrote a few tricky resources for this a while ago and they are
infinitely handy.
On Wed, Sep 12, 2012 at 04:08:13PM +0200, Bernd Adamowicz wrote:
No ideas at all?
-Ursprüngliche Nachricht-
Von: Bernd Adamowicz
Gesendet
: puppet-users@googlegroups.com [mailto:puppet-users@googlegroups.com] Im
Auftrag von Bernd Adamowicz
Gesendet: Donnerstag, 13. September 2012 10:46
An: puppet-users@googlegroups.com
Betreff: Re: [Puppet Users] AW: Issue with large directory content
Thanks for your answers so far.
But beware
: puppet-users@googlegroups.com [mailto:puppet-users@googlegroups.com] Im
Auftrag von Bernd Adamowicz
Gesendet: Donnerstag, 13. September 2012 14:45
An: 'puppet-users@googlegroups.com'
Betreff: AW: [Puppet Users] AW: Issue with large directory content
This keeps being weird. Simply thought to wait
No ideas at all?
-Ursprüngliche Nachricht-
Von: Bernd Adamowicz
Gesendet: Dienstag, 11. September 2012 16:16
An: puppet-users@googlegroups.com
Betreff: Issue with large directory content
Hi all,
I got this directory configuration:
file {
${codebase_ng
Hi all,
I got this directory configuration:
file { ${codebase_ng::repository_mount}/${sonatype_work_dir}:
ensure = directory,
owner = $nexus_user,
group = $nexus_group,
mode= 0755,
recurse = false,
Did you ever try Gepetto (https://github.com/cloudsmith/geppetto)? At least in
the coming version (3.0) will support Puppet 3. I really do recommend Gepetto
since I've been working with it for more than a year now and it helped me a lot
creating error free code. You should give it a try. There
Hi Sandra,
Yes, you may either use it as an Eclipse plugin or as a standalone program.
There's no link to vi or Emacs at all. I think I know what you mean. My
absolutely favorite editor is vim. Normally I don't need anything else but the
command line and vim. However, when it's about creating
, Bernd Adamowicz
bernd.adamow...@esailors.de wrote:
Tried to attach one of my agents to another environment with a
command like this:
puppet agent --verbose --debug --server my.puppet.master
--environment my_new_env --no-daemonize
But it still receives the old catalog of the old
I'm not an expert in regular expression. But if I run into problems like this
one, I always turn to this page:
http://www.regexplanet.com/advanced/java/index.html Has always helped me.
Bernd
-Ursprüngliche Nachricht-
Von: puppet-users@googlegroups.com [mailto:puppet-
Tried to attach one of my agents to another environment with a command like
this:
puppet agent --verbose --debug --server my.puppet.master --environment
my_new_env --no-daemonize
But it still receives the old catalog of the old environment. No errors or
warnings in log files both on master
: Freitag, 13. Juli 2012 11:08
An: puppet-users@googlegroups.com
Betreff: Re: [Puppet Users] What is the intention of thin_storeconfigs?
On 12/07/12 10:29, Bernd Adamowicz wrote:
I started doing some experiments with the configuration option
'thin_storeconfigs=true' by adding this option
thin_storeconfigs
On Fri, 2012-07-06 at 09:43 +0200, Bernd Adamowicz wrote:
Which is the right way to use thin_storeconfigs? Currently I'm about
to try this:
storeconfigs = true
thin_storeconfigs = true
Or should it be only a single line containing the 'thin_storeconfigs'
directive
Thanks to all who gave feedback on this topic. I will have a deeper look at
this issue throughout the next days and weeks and will share my experience then.
Bernd
-Ursprüngliche Nachricht-
Von: Bernd Adamowicz
Gesendet: Donnerstag, 12. Juli 2012 10:29
An: 'puppet-users
I started doing some experiments with the configuration option
'thin_storeconfigs=true' by adding this option to one of my Puppet masters.
However, I could not determine any change in behavior. I expected to have the
resources collected faster, but Puppet still takes some 15min to do the job.
Searching LinkedIn should be a good starting point. Where are you located (US,
Europe, ..)?
Bernd
Von: puppet-users@googlegroups.com [mailto:puppet-users@googlegroups.com] Im
Auftrag von JeremyCampbell
Gesendet: Samstag, 7. Juli 2012 19:06
An: puppet-users@googlegroups.com
Betreff: [Puppet
Which is the right way to use thin_storeconfigs? Currently I'm about to try
this:
storeconfigs = true
thin_storeconfigs = true
Or should it be only a single line containing the 'thin_storeconfigs' directive
without 'storeconfigs=true'?
Thanks Bernd
--
You received this message because you
We got a totally integrated solution made up with Puppet, Icinga and stored
resources. When integrating a new host into Puppet, one just has to wait until
it gets monitored in Icinga - no more work to do. Some details are found here:
http://www.bernd-adamowicz.de/tag/monitoring/
Bernd
it's based on Nagios. Overall you are pleased with the solution?
Sent from my iPhone
On Jun 25, 2012, at 7:45 AM, Bernd Adamowicz
bernd.adamow...@esailors.de wrote:
We got a totally integrated solution made up with Puppet, Icinga and
stored resources. When integrating a new host
@googlegroups.com [mailto:puppet-
us...@googlegroups.com] Im Auftrag von Alexander Bien
Gesendet: Montag, 25. Juni 2012 15:10
An: puppet-users@googlegroups.com
Betreff: Re: AW: [Puppet Users] OT: Monitoring solutions
On 25.06.2012 14:45, Bernd Adamowicz wrote:
We got a totally integrated solution made up
k...@mocker.orgmailto:k...@mocker.org wrote:
Curious if Icinga has integrated graphing or if it's an add-on since it's based
on Nagios. Overall you are pleased with the solution?
Sent from my iPhone
On Jun 25, 2012, at 7:45 AM, Bernd Adamowicz
bernd.adamow...@esailors.demailto:bernd.adamow
This might give another starting point:
* http://www.bernd-adamowicz.de/180/monitoring-puppet-part-3/
*
http://www.bernd-adamowicz.de/85/synchronizing-puppet-generated-icinga-configuration/
Essentially the first link might be helpful.
Bernd
Von:
Obviously the user which is executing the Puppet start command is not allowed
to access the directory '/var/lib/puppet/run/' or the file
'/var/lib/puppet/run/pidlock.rb'. Are you starting the master as root? If not,
you should. If the problem persists, check the access rights and permissions of
I cannot help with this problem. But I'm facing the same issue from the very
first time I'm using Puppet. It happens only on my Puppet master boxes. I'm
running Puppet 2.6.12 on RHEL 5.5. If I can provide more information to help
solving this issue, just let me know.
Bernd
Von:
Yes, actually each of my masters has its own SVN-URL checked out with the
appropriate configuration. A cron job is doing updates in 5 minute intervals.
Quite easy and works very reliable.
Bernd
-Ursprüngliche Nachricht-
Von: puppet-users@googlegroups.com [mailto:puppet-
You should try
debug = true
verbose = true
in your agent and/or master configurations. Some more hints on monitoring and
on Nagios/Icinga checks are found here:
http://www.bernd-adamowicz.de/180/monitoring-puppet-part-3/
Bernd
Von:
I'm not aware of any undo functions in Puppet. I think the only thing you can
do is do create a proper user configuration for your Suse and Solaris boxes and
let Puppet fix it.
Bernd
Von: puppet-users@googlegroups.com [mailto:puppet-users@googlegroups.com] Im
Auftrag von root
Gesendet:
No ideas?
-Ursprüngliche Nachricht-
Von: Bernd Adamowicz
Gesendet: Montag, 16. April 2012 13:32
An: 'puppet-users@googlegroups.com'
Betreff: Could not send report: Error 400 on SERVER: execution expired
Hi all!
One of my Puppet masters has to compile some 3800 stored
Hi all!
One of my Puppet masters has to compile some 3800 stored configurations which
takes a very long time to proceed. Example log:
Apr 16 13:17:13 mymaster puppet-agent[15249]: Finished catalog run in 954.58
seconds
Apr 16 13:18:35 mymaster puppet-master[11422]: execution expired
Apr 16
Try to change
* exec { 'chk_vomsdir':
to something like
* exec { chk_vomsdir_${dir}:
and
* require = Exec[ 'chk_vomsdir' ];
to
* require = Exec[chk_vomsdir_${dir}];
This should make everything unique.
Bernd
-Ursprüngliche Nachricht-
Von: puppet-users@googlegroups.com
' ];
}
}
---
I don't get any error at all.
Cheers,
San
On Apr 12, 2:55 pm, Bernd Adamowicz bernd.adamow...@esailors.de
wrote:
Try to change
* exec { 'chk_vomsdir':
to something like
* exec { chk_vomsdir_${dir}:
and
* require = Exec
Concerning backup: I have everything below '/var/lib/puppet' backed up
regularly on my Puppet masters. This will also contain all client certificates.
Concerning client certificates: Are the clients still requesting? What does
'puppetca --list' say? It might be possible to simply re-accepting
You need virtual resources:
1. Define package A in a virtual way:
@package {
A :
ensure = 'present',
}
2. Then realize it wherever needed:
class module2::app2 {
realize(Package[A])
# your stuff here...
}
Cheers,
Bernd
Von: puppet-users@googlegroups.com [mailto:puppet-users@googlegroups.com] Im
Auftrag von Mike
Gesendet: Dienstag, 13. März 2012 15:04
An: puppet-users@googlegroups.com
Betreff: [Puppet Users] Can't send certificate request
I can't get a new client working with my puppet master. When I try to
Try
puppet agent --verbose --debug --server your.server --environment your_env
--waitforcert 60 --no-daemonize
Bernd
Von: puppet-users@googlegroups.com [mailto:puppet-users@googlegroups.com] Im
Auftrag von Bernd Adamowicz
Gesendet: Dienstag, 13. März 2012 15:54
An: 'puppet-users
That's basically OK, but try
source = puppet:///files/etc/sudoers
instead. This will link automatically to your local host's Puppet master. If
you are already working with modules, you should work with
source = puppet:///modules/yourmodulename/etc/sudoers
Your file 'sudoers' must then be
/site.pp:33
notice: Finished catalog run in 0.47 seconds.
Can you suggest me some steps where i can copy some files to puppet
client from start.??
Thanx
Niraj
On Mar 7, 5:39 am, Bernd Adamowicz bernd.adamow...@esailors.de
wrote:
That's basically OK, but try
source = puppet
Hi Henrik,
looks great! Discovered lots of warnings and even an error (which Puppet did
not complain about) after upgrading. Fixed all my Puppet code now and I think
this is another good step in improving my overall code quality.
Thanks for the work. Looking forward for new releases.
Bernd
I'm not sure, but you could try changing the SELinux stuff with Puppet
configuration instead of 'chcon'. I got a little description here:
http://berndadamowicz.wordpress.com/2011/12/16/nrpe-and-selinux/.
Be aware that the SELinux attributes might be changed back after Puppet has
applied the
I'm pretty sure that, besides the other answers already provided, your main
problem is the wrong user for your Puppet configuration. It should be user
'puppet' and not 'root'. That's how '/etc/puppet' should look like:
drwxr-xr-x 5 puppet puppet 4.0K Dec 12 17:48 .
drwxr-xr-x 79 root root
Are you sure Puppet does change your bash-files? I got the same configuration a
lot of times (Puppet 2.6.6 and 2.6.12) and did not encounter such behavior. Can
you give more details?
Bernd
-Ursprüngliche Nachricht-
Von: puppet-users@googlegroups.com [mailto:puppet-
I'm not quite sure, but my experience is that as soon as you remove the
@@-resources from your node configuration, they will also be dropped from the
database by the Puppet master. You may want to check with some
select-statements if this is really true.
I once deleted some resources manually
Augeas?
-Ursprüngliche Nachricht-
Von: puppet-users@googlegroups.com [mailto:puppet-
us...@googlegroups.com] Im Auftrag von Sans
Gesendet: Donnerstag, 1. Dezember 2011 15:54
An: Puppet Users
Betreff: [Puppet Users] Re: How to make partial change to a line??
Does anyone have any
] storeconfgs not initializing database
Hi Bernd,
I've tried with and without dbsocket being set but it has no affect.
--
Later,
Darin
On Wed, Nov 30, 2011 at 3:53 AM, Bernd Adamowicz
bernd.adamow...@esailors.demailto:bernd.adamow...@esailors.de wrote:
Did you try uncommenting the 'dbsocket' line
I recently set up our CI system using two Puppet masters and some 50 Puppet
agents. If you follow some installation instruction it will not take longer
than a day for having set up your first Puppet master and some agents. Once
this is done the actual work starts:
* create/configure the Puppet
We have a single Puppet master for every data center. Every master has its own
Subversion branch containing the appropriate Puppet configuration along with
the environments needed. It's quite an easy concept which works very well for
us and which also allows managing configurations between the
I made a really bad mistake today by deleting all files below /var/lib/puppet
on one of my Puppet masters. (I simply issued a command in the wrong terminal
window.) A first analysis showed that all SSL certificates from the clients
have gone (puppetca --list --all). However the clients are
and restored the ssl dir from backup. No
problem while restarting
kind regards,
Martin
2011/11/28 Bernd Adamowicz bernd.adamow...@esailors.de:
I made a really bad mistake today by deleting all files below
/var/lib/puppet on one of my Puppet masters. (I simply issued a command
Is there anything special about the cron resource? I have a configuration like
this:
cron { sync-stored-config:
command = /some/command.sh,
user = icinga,
hour = *,
minute = 15,45,
}
But the 'minute' field produces this error:
8955 Nov 22 14:30:11 bob puppet-agent[7950]:
behaviour?
On Tue, Nov 22, 2011 at 03:48:31PM +0100, Bernd Adamowicz wrote:
Is there anything special about the cron resource? I have a
configuration like this:
cron { sync-stored-config:
command = /some/command.sh,
user = icinga,
hour = *,
minute = 15,45
I've never used the file resource along with stored configurations. But the
first thing I would do is to dig into the database the configurations are
stored. Something like this:
[root@myhost ~]# mysql -u puppet -p
Enter password:
mysql use puppet
mysql select title,host_id from resources
Just an idea: Seems, Puppet is using the URL http://localhost/reports/upload
though you have specified 'reporturl = http://localhost:3000/reports/upload'.
Is it possible that there is some command line argument overriding your
puppet.conf?
However I don't use the 'reporturl' argument at all.
the Puppet agent. If
anyone is interested in details, see: http://wp.me/p1RukY-1n.
Thanks for helping, Gabriel!
Bernd
-Ursprüngliche Nachricht-
Von: Bernd Adamowicz [mailto:i...@bernd-adamowicz.de]
Gesendet: Donnerstag, 17. November 2011 22:36
An: Bernd Adamowicz
Betreff: Fwd: Re: [Puppet
the permissions.
however, there's no require link between both.
what happens if you try and remove the require link from Nagios_XYZ -
${baseconfigdir}/${conf_file_srvs} ?
On 11-11-16 05:57 PM, Bernd Adamowicz wrote:
Hi all,
I'm a little bit confused that I did not get a single reply from the
list
. So I hope it's OK. Tell me, if not.
Bernd
On Mon, 31 Oct 2011 13:28:37 +0100, Bernd Adamowicz
bernd.adamow...@esailors.de wrote:
-Ursprüngliche Nachricht-
Von: puppet-users@googlegroups.com [mailto:puppet-
us...@googlegroups.com] Im Auftrag von Bernd Adamowicz
Gesendet: Donnerstag
:02 +0100, Gabriel Filion lelu...@gmail.com
wrote:
On 11-11-17 04:04 AM, Bernd Adamowicz wrote:
Removing the 'require' link leads back to the very first problem I've
encountered: The files are not regenerated even thought the stored
configurations inside the MySQL database changed (I did check
-Ursprüngliche Nachricht-
Von: puppet-users@googlegroups.com [mailto:puppet-
us...@googlegroups.com] Im Auftrag von Bernd Adamowicz
Gesendet: Mittwoch, 9. November 2011 13:44
An: 'puppet-users@googlegroups.com'
Betreff: [Puppet Users] AW: nagios_service does not replace target file
Now I tried
Can you be a little bit more precise please? What are you doing exactly, which
commands? What is not working? Any error messages in syslog?
Bernd
-Ursprüngliche Nachricht-
Von: puppet-users@googlegroups.com [mailto:puppet-
us...@googlegroups.com] Im Auftrag von Javid Mehraban
the only one ever
running into this problem. So I'd like to ask this list and mainly the Puppet
guys if you think this is worth filing a bug?
Thanks
Bernd
-Ursprüngliche Nachricht-
Von: puppet-users@googlegroups.com [mailto:puppet-
us...@googlegroups.com] Im Auftrag von Bernd Adamowicz
Hi all,
I'm using Puppet 2.6.6 on both clients and master along with stored
configurations. My clients provide Nagios configurations like this example:
@@nagios_service { check_ping_${hostname}:
check_command = check_ping!100.0,20%!500.0,60%,
use = generic-service,
If you really dropped the database you have to recreate it before the first
Puppet run:
05mysql create database puppet;
06 Query OK, 1 row affected (0.00 sec)
07
08 mysql grant all privileges on puppet.* to puppet@localhost identified
by 'xxx';
09 Query OK, 0 rows
We use the basic checks for any Unix machine along with special checks for
running Puppet master and client process where appropriate. A service which
uses NRPE and a check_procs call on the Puppet boxes like these two examples
works fine for us:
We were using Naginator resources like nagios_host, etc. along with stored
configurations and exported resources. Worked pretty well. However we have to
separate the Puppet master and the Icinga (Nagios) server. They will be on
different machines from now on. Are there any best practices for
.
On Sep 29, 2011, at 8:47 AM, Bernd Adamowicz wrote:
We were using Naginator resources like nagios_host, etc. along with
stored configurations and exported resources. Worked pretty well.
However we have to separate the Puppet master and the Icinga (Nagios)
server. They will be on different
I'm not quite sure, but maybe exported resources could help. Some introductions
are found here:
* http://docs.puppetlabs.com/guides/exported_resources.html
*
http://blog.gurski.org/index.php/2010/01/28/automatic-monitoring-with-puppet-and-nagios/
They also cover the Nagios issue.
Cheers Bernd
Yes, I was simply missing the worker process.
Thanks, Craig and Michael!
-Ursprüngliche Nachricht-
Von: puppet-users@googlegroups.com [mailto:puppet-
us...@googlegroups.com] Im Auftrag von Craig White
Gesendet: Montag, 12. September 2011 22:00
An: puppet-users@googlegroups.com
Try this:
node client {
file { /home/admin/puppet/jck.txt:
owner = admin,
group = admin,
mode = 0744,
source = puppet:///test/jck.txt,
}
Beware the colon and the commas. (Didn't you get any error messages in your log
Von: puppet-users@googlegroups.com [mailto:puppet-users@googlegroups.com] Im
Auftrag von John Kennedy
Gesendet: Dienstag, 13. September 2011 13:43
An: puppet-users@googlegroups.com
Betreff: Re: [Puppet Users] Re: Puppet not pushing file
On Tue, Sep 13, 2011 at 12:27, Bernd Adamowicz
Hi all!
After installing and configuring puppet-dashboard-1.2.1-0.1rc1.el6.noarch.rpm
following the installation instruction given in the Pro Puppet book,
everything seems fine. (No errors during installation and configuration.)
However Dashboard only shows me that there are 'x pending tasks'
Hi all,
is there a way to avoid changing the state (present/absent) of a user? In my
case I just want to do a kind of 'check' if the user is present. If so, I will
do some file-resource stuff on him. If not, nothing should be done at all.
Example:
# create the user resource
user { 'someuser':
Sorry, the file resource should of course be:
# copy file if user exists
# do nothing if not
file { /home/someuser/.bashrc:
require = User[someuser],
...
}
-Ursprüngliche Nachricht-
Von: puppet-users@googlegroups.com [mailto:puppet-
us...@googlegroups.com] Im Auftrag von Bernd
, Bernd Adamowicz bernd.adamow...@esailors.de
wrote:
Hi all,
is there a way to avoid changing the state (present/absent) of a
user? In my case I just want to do a kind of 'check' if the user is
present. If so, I will do some file-resource stuff on him. If not,
nothing should be done at all
Ok, found the answer myself. Just installed 25.5-rc2 on client and server and
tried it. But same error message when parsing the template.
Is there an elegant way to use complex facts in puppet's erb
templates?
Puppet will support hashes in the next major version (Rwolf),
although I am
Hi all,
I'm working with Puppet version 0.25.4 and as far as I have read in this list
it's not possible to access complex data structures from within an ERB
template, instead serializing is needed. Due to my lack of Ruby knowledge I
didn't find the right solution for this problem:
Given this
Dan, I think what you suggested seems to be the right way. I had a deeper look
at external node classifiers as well as on working with different environments
inside Puppet. I have not been aware of these concepts but will start now to
create a proof of concept for our systems.
Thanks all for
Sounds pretty much like the problem I posted yesterday. You may have a look at
it here:
http://groups.google.com/group/puppet-users/browse_thread/thread/336a6c1d941acca8/b50faf7711b7bf41?hl=enlnk=gstq=adamowicz#b50faf7711b7bf41.
It seems that external node definitions and different environments
Hi all,
given these two classes inside the file
'/etc/puppet/modules/templates_eval/manifests/init.pp':
53 class templates_eval::providevars {
54
55
$hibernate_connection_dialect=org.hibernate.dialect.Oracle10gDialect
56 }
57
58 class
87 matches
Mail list logo
