ess the service hadn't been restarted. Restart apache2/httpd.
If this is an error in the e-mail, then going back to the original
error, you have a permissions issue. Ensure the files and parent
directories are all readable by 'foreman'.
--
Dominic Cleal
domi...@cleal.org
--
You r
instance, perhaps
compare against your existing Foreman server, then set these parameters
to the same values.
--
Dominic Cleal
domi...@cleal.org
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop
e in the environment whose metadata.json is
restricting which combinations of concat/stdlib can be installed -
either deliberately or due to a mistake in the dependency spec.
I'd suggest checking any other modules very carefully, and/or try
installing into a minimal environment with the --envir
et.com/puppetlabs/concat/dependencies
>
> https://forge.puppet.com/puppetlabs/stdlib
The latest version of stdlib is 4.15.0, not 4.1.5 (point fifteen, not
one). Version 4.15.0 is higher than the requirement for version 4.2.0.
--
Dominic Cleal
domi...@cleal.org
--
You received this message bec
/puppetserver/latest/release_notes.html for
the latest release notes.
Install puppet-agent 1.9.1 and puppet-server 2.7.2 (at the time of
writing) and you'll have the latest Puppet 4.9.
--
Dominic Cleal
domi...@cleal.org
--
You received this message because you are subscribed to the Google Groups
lity, once installed, are global.
Custom facts from Puppet are read only when the additional agent
directory is included (i.e. with Facter's -p flag). Lenses work in a
very similar way - they are not installed globally.
--
Dominic Cleal
domi...@cleal.org
--
You received this message because
useful.
--
Dominic Cleal
domi...@cleal.org
--
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
ad, I created a small class that returns an unquoted value.
in spec_helper.rb:
class Undef
def inspect
'undef'
end
end
and then to use it:
let(:params) do
{ :example => Undef.new }
end
--
Dominic Cleal
Red Hat Engineering
On 27/04/14 15:38, Remi Ferrand wrote:
> Hi ever
its clients...
>
> Someone had this error?
It's a problem parsing ntp.conf on line 8. Please open a ticket at
https://github.com/hercules-team/augeas/issues and include a copy of
ntp.conf so we can see the issue.
Cheers,
--
Dominic Cleal
Red Hat Engineering
--
You received this mes
er is being removed,
but it's unduly noisy at 'warning' level when in the vast majority of
cases users need to take no action.
--
Dominic Cleal
Red Hat Engineering
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscrib
ules do not show up ?
I'd have expected a few classes from shorewall to show up. Which
version of Puppet's installed? Maybe the module's using a feature that
will only parse in a newer version.
--
Dominic Cleal
Red Hat Engineering
--
You received this message because you are su
/files/etc/group/error/line = 51
Look to see what's there and maybe you can edit the file to workaround
the problem. If the file is still valid, then please file a bug either
with your distribution or upstream
(https://github.com/hercules-team/augeas/issues).
--
Dominic Cleal
Red Hat Engine
On 11/11/13 15:18, Jist Anidiot wrote:
>
>
> On Friday, November 8, 2013 12:23:11 PM UTC-5, Dominic Cleal wrote:
>
> On 06/11/13 21:17, Jist Anidiot wrote:
> > I'm trying to make sure a specific user has a special ssh key used as
> > his identity fil
les/home/user/.ssh/config/IdentityFile
> not_include ~/.ssh/user2nd_rsa",
>
> }
>
> However it adds the line every puppet run. I'm wondering what I might
> be doing wrong.
Try:
onlyif => "match
/files/home/user/.ssh/config/IdentityFile[.='~/.ss
shellvars lens in order to support
parsing it: https://fedorahosted.org/augeas/newticket
In the meantime, perhaps use file_line or similar tools.
--
Dominic Cleal
Red Hat Engineering
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscr
so ideally wouldn't like to use templates.
>
> Any ideas or thoughts?
I don't follow your question. What did you expect or want it to do?
--
Dominic Cleal
Red Hat Engineering
--
You received this message because you are subscribed to the Google Groups
"Puppet Users&quo
#x27;s version,
but that's not published on rubygems.org. Try downloading this and
running gem install against it:
http://download.augeas.net/ruby/ruby-augeas-0.3.0.gem
Else you could try Raphael's Ubuntu packages, maybe the 12.04 ones are a
close match for Debian:
https://launchpad.net
rprise Edition 2010.01
> And my puppet client version is: 2.6.2
>
> Do you guys have any idea on how to solve this problem ?
You said you had an error while compiling, what was the error?
At a guess you'll need to ensure you have at least gcc and augeas-devel
available.
--
Dominic Cleal
nment option to do
the same, which you can set in puppet.conf.
Lastly, you can disable the ENC script if you don't use it for classes
or parameters and instead add "/etc/puppet/node.rb --push-facts" to a
cronjob, which will just upload facts for all hosts to Foreman instead.
--
Dominic
files in the same directory which test the providers,
though since it's fairly specialised they're not great examples. I'd
recommend working from the huge number of examples in the Puppet source
tree itself:
https://github.com/puppetlabs/puppet/tree/master/spec/unit/type
https://github.
On 22/03/13 23:22, Gonzalo Servat wrote:
> On Sat, Mar 23, 2013 at 9:47 AM, Gonzalo Servat <mailto:gser...@gmail.com>> wrote:
>
> On Fri, Mar 22, 2013 at 9:11 PM, Dominic Cleal <mailto:dcl...@redhat.com>> wrote:
>
> Perhaps ideally, lenses c
onsible
for the config file formats themselves so they're more easily kept in
sync. There are a small number of projects that do this (libvirt,
libguestfs, corosync), but it needs a supportive upstream.
Regards,
--
Dominic Cleal
Red Hat Engineering
--
You received this messa
shouldn't have this issue, but
you should have some RequestHeader lines in the puppetmaster vhost that
set client certificate details and SSLCACertificateFile +
SSLVerifyClient to enable verification. It could be that the client
cert isn't getting verified by mod_ssl and so the puppetmaster can't us
ion.securityLevel.createSession=10
> session.securityLevel.listFiles=10
> low.session.timeout=15
> # eof
>
> I want to change createSession from 10 to 11.
>
> my puppet code is:
>
> augeas { "test":
> lens=> "Property.lns",
This line doesn't look
; database
such as PostgreSQL and not sqlite (~foreman/config/database.yaml). If
you're running the database and Foreman on the same system, check it's
powerful enough (not one vCPU and a small amount of RAM), check what
storage it's on etc.
--
Dominic Cleal
Red Hat Engineering
--
or the agent on the master server is
also used for the master process itself (inbound connections).
--
Dominic Cleal
Red Hat Engineering
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving
; [Sun Dec 09 07:57:49 2012] [warn] RSA server certificate CommonName (CN)
> `' does NOT match server name!?
> [/code]
>
> Anybody have some help for me?
Do check syslog, as the puppet master usually logs initialisation
problems there (e.g. permissions).
--
Dominic Cleal
Red Ha
ports for something useful, then look at
PuppetDB 1.1 instead, or improve your storage. If you're using another
report processor (e.g. Foreman), then you need to optimise that.
--
Dominic Cleal
Red Hat Engineering
--
You received this message because you are subscribed to the Google Gro
"defvar ramtmpcomment #comment[.=~regexp('RAMTMP=no')]",
>
> "ins RAMTMP after $ramtmpcomment",
You should use single quotes here, or escape the variable name with
\$ramtmpcomment. Puppet will be interpolating the variable itself
rather than letting Au
e puppet subcommands
You're missing the "node status" subcommand out of this, plus the config
setting is --confdir or --config. Try this instead:
puppet node status --confdir=/etc/puppet/conf --terminus puppetdb
servername.fqdn
See
http://docs.puppetlabs.com/references/stable/co
labs-devel in
/etc/yum.repos.d/puppetlabs.repo or use --enablerepo=puppetlabs-devel
with yum.
--
Dominic Cleal
Red Hat Engineering
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving email
'];
> }
> }
There's no Augeas lens for sendmail.cf files. From Puppet 3, it'll now
warn you if using context and a file wasn't loaded. Otherwise check in
augtool with "print" to see if the file can be loaded.
Maybe use stdlib's file_line type?
--
Dominic
t()+1 is to do this, which has the
bonus of being entirely idempotent - so if the line already exists, it
won't add a second.
set /files/etc/services/service-name[. = 'DB2_db2inst1_2'] "DB2_db2inst1_2"
set /files/etc/services/service-name[. = 'DB2_db2inst1_2']/port 600
/1.8/rubygems/custom_require.rb:31:in
> `gem_original_require'
> from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `require'
> from /usr/lib/ruby/gems/1.8/gems/puppet-module-0.3.4/bin/puppet-module:5
You don't want to use the puppet-module gem, you want to use t
the source
parameter when it should be content => template(...). Puppet is trying
to parse the shell script as a source URL.
--
Dominic Cleal
Red Hat Engineering
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send
tool (a test
utility).
I came up with this example to apply the transformation you mentioned:
augeas { "jbossas-datasource":
lens=> "Xml.lns",
incl=> "/etc/jbossas.xml",
changes => [
"set host/server[#attribute/name='one'] ''&
On 10/12/12 18:59, Bret Wortman wrote:
> On Monday, December 10, 2012 1:51:46 PM UTC-5, Bret Wortman wrote:
>
> On Monday, December 10, 2012 8:34:17 AM UTC-5, Dominic Cleal wrote:
>
> On 07/12/12 11:56, Bret Wortman wrote:
> > Even in interactive mode,
should be much improved
now if you're able to use Puppet 3.
I've added debug if there are parsing errors (which will print output
equivalent to Raphaël's augtool suggestion) and warnings if you're using
context/incl parameters and it finds an error on a file you're tryin
also pluginsync lenses in the
same way as facts etc. This should take precedence over dist lenses
too. Store the lens at:
modulename/lib/augeas/lenses/custom.aug
(http://docs.puppetlabs.com/guides/plugins_in_modules.html)
--
Dominic Cleal
Red Hat Engineering
--
You received this message beca
On 16/10/12 11:42, Dominic Cleal wrote:
> On 15/10/12 16:52, Eugene Vilensky wrote:
>>
>> On Oct 14, 2012, at 12:40 PM, Dominic Cleal > <mailto:dcl...@redhat.com>> wrote:
>>
>>> You're missing quotes around "nrpe", the command should be:
&g
On 15/10/12 16:52, Eugene Vilensky wrote:
>
> On Oct 14, 2012, at 12:40 PM, Dominic Cleal <mailto:dcl...@redhat.com>> wrote:
>
>> You're missing quotes around "nrpe", the command should be:
>>
>> set /files/etc/hosts.allow/*[process='nr
ink that with Augtool I have to explicitly create a
> node, while with Puppet augeas provider, I do not. Hmm.
There's no difference like this. The Puppet provider parses the
commands but feeds them into the same API as augtool itself uses.
Were you having problems just with augtool, or
es/16203 was also raised to make
sure the package depends or recommends on 0.3.0 as a minimum version,
but this hasn't been completed yet.
--
Dominic Cleal
Red Hat Consulting
m: +44 (0)7817 878113
--
You received this message because you are subscribed to the Google Groups
"Puppet Users&
s => "set 1[last()+1] $name",' works like a charm but I
> am unable to get any onlyif to work.
The onlyif line is a bit magical as there's a mini-DSL inside the
provider. My preferred syntax is this:
onlyif => "match size == 0",
So in your case this will work:
hanges => [
"set ApplicationName ${appname}",
"set ApplicationVersion ${appversion}",
],
}
(Where $appname and $appversion are Puppet variables, facts or a proper
data source.)
Cheers,
--
Dominic Cleal
Red Hat Consulting
m: +44 (0)7817 878113
--
You received t
he provider (issue #7285)
that will use the "context" parameter (optional, but usually specified)
to only load lenses that are applicable to that context. Hopefully
you'll see the same drastic reduction in runtime out of the box in the
near future.
--
Dominic Cleal
Red Hat Consul
of a use case for Puppet's purge) then I don't think there's
a good solution. Perhaps you could mark your Puppet-managed resources
with a comment (a #comment subnode usually) and then delete anything
that doesn't match it.
--
Dominic Cleal
Red Hat Consulting
m: +44 (0)7817
mon=100\"'
> augtool> save
> error: Failed to execute command
> error: saving failed (run 'print /augeas//error' for details)
The issue here is a little different, remove the \ before ". The reason
you need this in Puppet is because you're quoting the enti
/ is there,
it believes this is an absolute path rather than being underneath the
context. Remove the leading / and the context will be applied.
--
Dominic Cleal
Red Hat Consulting
m: +44 (0)7817 878113
--
You received this message because you are subscribed to the Google Groups
"Puppet
ot it, could you please pastebin the logging of the whole
resource when debug was enabled?
--
Dominic Cleal
Red Hat Consulting
m: +44 (0)7817 878113
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to
code path on some OSes)
There's another to fix a missing libxml2 dependency in pkg-config if you
need that (which could affect building ruby-augeas).
--
Dominic Cleal
Red Hat Consulting
m: +44 (0)7817 878113
--
You received this message because you are subscribed to the Google Groups
&qu
s
linked below that used to be published via EPEL. You should be able to
download and install with yum localinstall, which will pull in that
dependency from optional.
http://koji.fedoraproject.org/koji/buildinfo?buildID=228762
Cheers,
--
Dominic Cleal
Red Hat Consulting
m: +44 (0)7817 878113
ager), but to clearly delimit the different support
given to those packages compared to the base channel.
There are other packages from optional that you'll find yourself
needing, e.g. libselinux-ruby, so I don't think ignoring it is that easy.
Cheers,
--
Dominic Cleal
Red Hat Co
y nearly. Try this:
augtool> print /files/etc/logrotate.d/syslog/rule/file[. =~
regexp("/var/log/mail.*")]
/files/etc/logrotate.d/syslog/rule/file[3] = "/var/log/maillog"
The regexps are anchored by default, so you need the .* to match
anything after "mail".
an (due to other bugs). It wasn't fixed in 2.6, though
if you're using EPEL then there's a patch in that 2.6 RPM.
--
Dominic Cleal
Red Hat Consulting
m: +44 (0)7817 878113
--
You received this message because you are subscribed to the Google Groups
"Puppet Users&quo
itten by David Lutterkort
>> % augtool print /files/etc/rc.conf
>> /files/etc/rc.conf
>> /files/etc/rc.conf/keymap = "\"us.pc-ctrl\""
>> /files/etc/rc.conf/sshd_enable = "\"YES\""
>> [snip]
This matches what should be back in
geas/lenses/tests/rcconf.aug
> 13563 1 /usr/local/share/augeas/lenses/rcconf.aug
>
> # augtool
> augtool> print /files/etc/rc.conf
> augtool>
Could you try running this in augtool to see if a lens is being used,
and if there are errors?
print /augeas/files/etc/rc.conf/
--
stead of just the one, e.g.
/files/etc/modprobe.conf/install = "foo"
/files/etc/modprobe.conf/install/command = "/bin/true"
I've also changed the install[0] so it doesn't always overwrite the
first install line and instead creates an install line per module.
Cheers,
-
rub.conf. A better idea is to use the "setm" (set multiple)
command to set it on every kernel line, but you'll need Augeas 0.7.2,
ruby-augeas 0.4.0 and Puppet 2.7.0.
There's a good description here of how to use it, which you can wrap
into a define again:
http://planet.ergo-project
ading to the
> latest and test it again...
I'm pretty sure you're right with this. From a quick look at the code,
then it's simply not designed to work with integer values in settings.
You'd need to file an RFE against Puppet for this, as the conditionals
are implemented in
> 0",
}
The idea is that the match condition in onlyif will return the /var
node, only when it has no "acl" opt nodes beneath it.
While the above may work, I'd urge you to consider how you configure
systems with Puppet. Detecting the current configuration (i.e. does or
ease do consider sending your new lens (and
accompanying test) upstream to the augeas-devel list, we'd love to
include it.
Hope that helps.
--
Dominic Cleal
Red Hat Consulting
m: +44 (0)7817 878113
--
You received this message because you are subscribed to the Google Groups
"Pup
as0 package contain any lens files?
I can't find a spec for it to see how the SUSE package is split up, but
the EL/Fedora package would put them in the augeas-libs package:
$ rpm -ql augeas-libs | grep -c \.aug\$
219
The lenses should generally match the Augeas library version so check
the
s' script returning a non-zero exit code? I've seen
bugs before with scripts that report on stdout that the process isn't
running, but failed to return the correct exit code (e.g. 1 or 3 for LSB).
--
Dominic Cleal
Red Hat Consulting
m: +44 (0)7818 512168
--
You received this mess
ckup mechanism (${FILE}.bak) isn't exposed in the
Puppet type.
I don't think it should be, so have put in the request for proper
integration to the filebucket feature like the file type:
http://projects.puppetlabs.com/issues/8105
--
Dominic Cleal
Red Hat Consulting
m: +44 (0)7818 51216
, incl
> etc ?
Rather than setting lens to "Xml", set it to "Xml.lns", as documented here:
http://docs.puppetlabs.com/references/stable/type.html#augeas
The rest looks OK to me (though I'd suggest using XPath type expressions
rather than hard-coding the numbers 16 and
e class was getting, and so I'd have a mixture of both.
That's fair enough. I found the consistency quite useful when working
in a team, so it became a familiar pattern across every module in this
case - even if that meant some classes were empty.
--
Dominic Cleal
Red Hat Consulting
m:
ailed
suggestion I can outline in another post..
[1] http://projects.puppetlabs.com/issues/2247#note-36
--
Dominic Cleal
Red Hat Consulting
m: +44 (0)7818 512168
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group,
way I've proposed doing this
(as implemented in the patch for #7285) is to use noautoload, then strip
out those files that don't match the context - if it's supplied. You
still need the autoinclude as you need to know both the lens and the
file, you can't just specify
7;s under the guise of showing file diffs for Augeas actions,
but happily speeds it up too:
https://projects.puppetlabs.com/issues/2728
Hopefully this focus on Puppet+Augeas performance will help out your
catalog runs in the future!
Cheers,
--
Dominic Cleal
Red Hat Consulting
m: +44 (0)7818 512168
--
You received th
There are also a few recipes for changing individual lines in files on
the Puppet wiki:
http://projects.puppetlabs.com/projects/1/wiki/Simple_Text_Patterns
Both solutions could be wrapped up in a define() to give you an
interface similar to the one you want.
--
Dominic Cleal
Red Hat Cons
On 13/04/11 12:38, Dominic Cleal wrote:
> What you might find useful is a new book that Raphaël Pinson's been
> working on, which starts explaining it from the beginning - it's still
> work in progress though.
>
> https://github.com/raphink/Augeas-book/
> (you&#x
arg($arg, $value) {
exec { "grubby-arg-$arg":
command => "grubby --update-kernel DEFAULT --args '$arg=$value'",
unless => "grubby --info DEFAULT | grep args= | grep
'$arg=$value'",
}
}
boot_kernel_arg { "kernel-co
's been
working on, which starts explaining it from the beginning - it's still
work in progress though.
https://github.com/raphink/Augeas-book/
(you'll need to clone and 'make' it)
Lastly, there are a few of us in #augeas on Freenode who can lend you a
hand with express
On 17/03/11 16:07, Mark Phillips wrote:
> On 17 Mar 2011, at 05:42, James Turnbull wrote:
>
>> Dominic Cleal wrote:
>>> Nobody has been looking at it, it would be great if you and Mark want to
>>> and I'd be happy to help. I haven't even seen any exampl
util
catalogs with multiple versions, so it'd be good to check it copes
properly in its current form too. (Unit tests!)
I think it's best to first collect some evidence about the output format
of pkgutil with multiple versions and what's possible compared to say
yum, then work ou
fetched, plus wget output
(if -q isn't used).
I intend to start up a patch thread soon on puppet-dev with the combined
commits from James, Maciej, Rudy and me to begin the process of getting
the provider included.
Regards,
--
Dominic Cleal
Red Hat Consulting
m: +44 (0)7818 512168
--
Y
77 matches
Mail list logo
