Oh ok, thanks Dominic. I'll give that a go.
Regards,
Guy
On Wed, Jun 20, 2012 at 1:37 AM, Dominic Cleal wrote:
> On 19/06/12 22:02, Guy Knights wrote:
> > I can now confirm that Dominic was correct. I'm upgraded to puppet
> > 2.7.16 now and the augeas resources are working. One thing I can also
On 19/06/12 22:02, Guy Knights wrote:
> I can now confirm that Dominic was correct. I'm upgraded to puppet
> 2.7.16 now and the augeas resources are working. One thing I can also
> confirm is that Alan's observation about the context not working and to
> use the full path in the set command was als
I can now confirm that Dominic was correct. I'm upgraded to puppet 2.7.16
now and the augeas resources are working. One thing I can also confirm is
that Alan's observation about the context not working and to use the full
path in the set command was also correct, at least for the sudoers config
Hi again,
I attempted to upgrade puppet from the office Puppet apt repository today,
previously it had been installed from source. I just installed the package
over the top, thinking it would overwrite the existing files. However, when
I run puppet --version it still spits out 2.7.3. I looked a
Sorry, never mind this. I discovered that the source version of puppet was
install in /usr/local/libs/site_ruby while the repository version appears
to have been installed in /usr/lib/ruby1.8.
On Tue, Jun 19, 2012 at 12:41 PM, Guy Knights
wrote:
> Hi again,
>
> I attempted to upgrade puppet from
That looks like the issue then. We're using augeas 0.10 (default with
ubuntu 10.04) and puppet 2.7.3. I'll look at upgrading puppet and see how
that goes.
Thanks all,
Guy
On Saturday, June 16, 2012 12:45:54 AM UTC-7, Dominic Cleal wrote:
>
> On 15/06/12 22:42, Guy Knights wrote:
> > Ok, thanks
On 15/06/12 22:42, Guy Knights wrote:
> Ok, thanks for your help Alan. BTW, I forgot include our puppet version
> - it's 2.7.0.
Which version of Augeas are you using? There's a bug if you're using
Augeas 0.10.0 with any version of Puppet before 2.7.10 where it won't
save the resource. You'll nee
Ok, thanks for your help Alan. BTW, I forgot include our puppet version -
it's 2.7.0.
Cheers,
Guy
On Fri, Jun 15, 2012 at 2:40 PM, Alan Evans wrote:
> From what I understand if you use the 'lens' attribute on the augeas
> resource type the augeas ruby library does essentially the same thing
> a
>From what I understand if you use the 'lens' attribute on the augeas
resource type the augeas ruby library does essentially the same thing
as --noload for augtool. Otherwise (unless its been fixed) every time
you use the augeas resource it opens the augeas-ruby library which
parses all lenses aug
Ok, thanks for the info. Are you implying that the puppet augeas resource
type acts in '--noload' mode, then?
I tried doing the fully qualified set statement but it still does nothing,
unfortunately.
On Fri, Jun 15, 2012 at 2:20 PM, Alan Evans wrote:
> Guy,
>
> The way augeas works is each lens
Guy,
The way augeas works is each lens has filters for which files it
should include and exclude. The --noload switch tells augtool not to
automatically load the lenses in /usr/share/augeas/ so it does not see
these filters. You then have to manually load a lens and tell it
which files to parse.
Yeah, I tried --debug in my puppet command and it didn't give me any
errors. In my original message i did say I tried doing the set from augtool
and it worked, but I just tried it again with augtool --noload and it can't
find anything to do with the sudoers file. It's like it's not reading the
file
Guy,
Check the debug output of the agent. puppetd --debug or puppet agent
--debug (I think)
Or try running the same set with augtool from the command line.
# augtool --noload
augtool> set /files/etc/php5/fpm/php.ini/PHP/error_log /var/log/php/php.log
augtool> print /augeas//error
See what the
I've recently configured a couple of augeas resources, one for a php.ini
file and one for sudoers, however neither set of changes is being saved. I
have no idea why. The sudoers resource is here:
augeas { 'set_sudoers':
context=> '/files/etc/sudoers/spec[user="%sudo"]',
changes
14 matches
Mail list logo
