rubular.com suggests that the regex should be ^sbx-.*-\d\d$
On 13 March 2013 12:16, Mike Reed mjohn.r...@gmail.com wrote:
Hello all,
I've been trying to configure node-based regex entries and puppet seems to
be giving me a hard time with this one.
Our system naming convention is this:
It looks like a syntax issue (at a minimum):
*package { sudo-ldap:*
*ensure = present,*
*require = Package[sudo],*
*}*
*}*
*
*
There isn't a trailing doublequote for the sudo line.
On 20 January 2013 16:38, Fusebox dnvik...@gmail.com wrote:
Hello Folks!
I am trying to
Legacy perhaps, but we have:
confdir = /etc/puppet
tagmap = $confdir/tagmail.conf
in puppet.conf's [master] section and our tagmails work.
Cheers,
Iain
On 13 June 2012 05:59, Jason Knudsen jason.knud...@gmail.com wrote:
Yeah -- checked that already, sorry forgot to mention that. Setup
If you're running puppet as a daemon with selinux in enforcing mode, I
think you may need to run:
setsebool puppetmaster_use_db on
In the current state and presuming that the audit daemon is running,
/var/log/audit/audit.log should be reporting which aspect of selinux is
preventing the access
Hi Ben,
I would try installing vixie-cron which offers the same capabilities under
EL5 as cronie under EL6:
CentOS5 machine:
$ cat /etc/redhat-release ; rpm -q --whatprovides vixie-cron
CentOS release 5.8 (Final)
vixie-cron-4.1-81.el5
CentOS6 machine:
$ cat /etc/redhat-release ; rpm -q
Is the source file readable by the puppet user?
On 7 March 2012 23:06, Bernd Adamowicz bernd.adamow...@esailors.de wrote:
Niraj,
I'll give you an example that works for me. But it uses modules. If you
don't so far, you really should start.
Given this structure below an environment below
Aside: do you perhaps mean
source = file(/home/$::realuser/puppet/files/smb.conf),
instead of
content = file(/home/$::realuser/puppet/files/smb.conf),
?
Do you have any lines like:
notice(the value of realuser is ${realuser} and ::realuser is
${::realuser} )
in your manifest to confirm what
+1 for tangled strings
On 16 November 2011 04:03, Ken Barber k...@puppetlabs.com wrote:
Depends on why you want this info ... but its available in the catalog
on the box for 'grepping' (more or less).
Something I recommend to some people:
This looks much like the error we had, which was:
ruby: ../../../libraries/libldap/result.c:113: ldap_result: Assertion `ld !=
((void *)0)' failed.
Under CentOS/RHEL, you need to upgrade the version of nss_ldap to
253-37.el5_6.1 (or later)
Bug details:
SSLCertificateFile: file '/var/lib/puppet/ssl/certs/puppet.tst.mydomain.pem'
[root@brllx097 ~]# ls -la
/var/lib/puppet/ssl/certs/puppet.tst.mydomain.com.pem
-rw-r-. 1 puppet root 912 Sep 2 11:40
/var/lib/puppet/ssl/certs/puppet.tst.mydomain.com.pem
Possibly a copy/paste/redact error (or I
To add a newline, put the closing double quote on a new line.
content = zabbix ALL=NOPASSWD: /var/lib/zabbix/bin/start_puppet,
becomes
content = zabbix ALL=NOPASSWD: /var/lib/zabbix/bin/start_puppet
,
On 2 August 2011 09:59, treydock treyd...@gmail.com wrote:
Ok , so this was actually two
Belated update on this one from another 'victim'...
Our CentOS and RHEL hosts don't have ruby-ldap, but we had the same problem,
with ldap-related assertion failures, including a couple of times outside of
a puppet run where ssh sessions would be terminated.
The fix: upgrade the version of
+1 from us too
On 12/05/2011, at 7:40 PM, joel.merr...@gmail.com joel.merr...@gmail.com
wrote:
On Thu, May 12, 2011 at 4:02 AM, Nigel Kersten ni...@puppetlabs.com wrote:
I'd much prefer it if we could concentrate on Puppet providing awesome
data sets for tools to graph rather than supporting
Yep, your experience matches what we see in our setup:
The puppetmaster has neither an auth.conf nor a namespaceauth.conf and operates
with just one error: we can't run puppetd on the puppetmaster because
namespaceauth.conf is missing...
On 23/02/2011, at 2:56 PM, Jed jedbl...@gmail.com wrote:
We use passenger and puppet 0.25.5 too.
Since I've never figured out the right contents for namespaceauth.conf on
the puppetmaster to avoid these 500 errors when performing puppetruns, we
perform the following steps:
1. delete the namespaceauth.conf file on the puppetmaster
2. ensure that the
Here's a script we use for this purpose:
#!/bin/bash
#
# Adapted from http://markmail.org/message/nybqh3be7bcge33h
#
if [ -z $1 ]
then
echo This script is used to retrieve backups of files that were
echo updated by puppet but which you might want to retrieve or
echo reinstate. Remember that
What, no other Aussies?
Aussie, Aussie, Aussie, Oi, Oi OI.
:-D
On 17 December 2010 12:11, Nan Liu n...@puppetlabs.com wrote:
On Thu, Dec 16, 2010 at 5:22 PM, Teyo Tyree t...@puppetlabs.com wrote:
Happy to announce that Daniel Pittman has joined Puppet Labs as a member
of
the development
wrote:
Hi,
The cpu is hardly busy. I'm not clear on the network part though cause
DNS resolutions and n/w connectivity everything's fine. It's just that
out of the blue had this problem.
regards,
On Wed, Dec 8, 2010 at 6:58 AM, Iain Sutton iainsut...@gmail.com wrote:
We experience
Also for the record.
We've experienced the banning - but only for RHEL4 hosts (which use
up2date) and not RHEL5 (which use yum).
Our solution while we still have RHEL4 hosts and haven't implemented RedHat
Satellite or Spacewalk was to push the runinterval out to 14400 for these
hosts. This
Hi,
We are able to successfully invoke puppetrun from the puppetmaster. The two
main differences between our configuration and what is posted below are:
a) the line 'server=puppet.mydomain.com' is in the [puppetd] section on the
client, not in the [main] section
b) we don't have a
20 matches
Mail list logo
