similar to: Augeas XML trouble

Anybody knows what this error, bellow, means, the target file, C:/Splunk/etc/system/local/inputs.conf, does exist. sometimes, if I delete the file, it does actually create it, but never update it if it exists and changed... The resource is defined as:     file { "splunk_inputs":        owner   => SYSTEM,        group => SYSTEM,        mode    => 664,        require =>

Good morning , I could help to debug this problem ? "puppet agent - test" Debug: catalog supports formats: b64_zlib_yaml dot pson raw yaml; using pson Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not find class pentaho for s <http://srvdev206.cia.stefanini.com/> erver.test.com /usr/lib/ruby/vendor_ruby/puppet/indirector/rest.rb:185:in

Good morning , I could audar to debug this problem ? "puppet agent - test" Debug: catalog supports formats: b64_zlib_yaml dot pson raw yaml; using pson Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not find class pentaho for srvdev206.cia.stefanini.com on node srvdev206.cia.stefanini.com /usr/lib/ruby/vendor_ruby/puppet/indirector/rest.rb:185:in

Hello, I get these message when i try to run puppet with augeas. Puppet Version are 2.6.1 on server and client. The ouput of the puppet Client with debug: debug: Failed to load library ''selinux'' for feature ''selinux'' debug: Failed to load library ''shadow'' for feature ''libshadow'' debug:

Hello everyone, I am currently struggling with the following issue that only seems to appear in my production environment: When attempting to send a mail from an ActionMailer the template location algorithm does not seem to pick up the corresponding template: ActionView::MissingTemplate (Missing template event_mailer/approval_requested_notification.erb in view path app/views):

Hi everyone, I have a puppet master/client infrastructure setup with apache. When on the same datacenter I don''t have any problem. I am trying to use another datacenter, so I setup the fileserver.conf as followed: # Files in the /path/to/files directory will be served # at puppet:///mount_point/. [modules] allow *.datacenter1 allow *.datacenter2 [plugins]

Hi all, Full path: /usr/lib/ruby/site_ruby/1.8/puppet/provider/ssh_authorized_key/parsed.rb Two problems: 1) Even if filebucketing is disabled, this (still) tries to backup authorized_keys to /var/lib/puppet/clientbucket/[...]; no other modules are doing filebucketing when it''s disabled but they (correctly) do when it is enabled. 2) The filebucketing is (still) being done with euid set

On Mon, Sep 22, 2014 at 02:56:18PM +0200, Pino Toscano wrote: > On Monday 22 September 2014 13:50:18 Richard W.M. Jones wrote: > > On Mon, Sep 22, 2014 at 10:49:42AM +0200, Pino Toscano wrote: > > > The lenses in our custom path need the system lens for base > > > definitions. Disabling the system path was worthless anyway, since > > > our API does not allow

Hi, i''ve upgraded many of my client machines to version 2.7.10 lately and since on some clients (server is running 2.7.10) i get the following error (running puppetd -tvd --noop --trace): /usr/lib/ruby/1.8/puppet/simple_graph.rb:181:in `<=>'' /usr/lib/ruby/1.8/puppet/simple_graph.rb:181:in `sort'' /usr/lib/ruby/1.8/puppet/simple_graph.rb:181:in

We were previously forcing the augeas Modprobe lens to match modules.conf and conf.modules. It turns out that the contents of these files are quite different to modprobe.conf, requiring a new lens. This change keeps the logic which looks for where modules should go, but doesn't update the augeas configuration. If there is no augeas lens for /etc/modules.conf, any attempt to parse or modify it

Augeas now configures the Grub lens for /boot/grub/menu.lst by default. The code which was checking this was broken in the case where there was more than 1 included path. We now check if /boot/grub/menu.lst is included. If it is, we don't reload. If it isn't, we add it, but don't remove any other config first. This fixes RHBZ#586822 --- lib/Sys/VirtV2V/GuestOS/RedHat.pm | 25

Add a function to display more complete augeas errors if they occur. Update all uses of augeas in GuestOS::RedHat to use it for error reporting. --- lib/Sys/VirtV2V/GuestOS/RedHat.pm | 185 ++++++++++++++++++++++++------------- 1 files changed, 121 insertions(+), 64 deletions(-) diff --git a/lib/Sys/VirtV2V/GuestOS/RedHat.pm b/lib/Sys/VirtV2V/GuestOS/RedHat.pm index cf8787d..8b211f0 100644 ---

If Augeas fails to parse a file, more information is available in at least these fields: ><fs> aug-ls /augeas/files/etc/fstab/error /augeas/files/etc/fstab/error/char /augeas/files/etc/fstab/error/lens /augeas/files/etc/fstab/error/line /augeas/files/etc/fstab/error/message /augeas/files/etc/fstab/error/pos Pull out some of these fields and add them to the error message. The new error

(apologies in advance for the line wrap) I have the following tidbit of augeas code, which inserts a rule into /etc/sysconfig/iptables as the first rule of a specifically named chain; # augtool> insert append before "/files/etc/sysconfig/iptables/table/append[. = ''Mayo-Firewall-INPUT''][1]" # augtool> match /files/etc/sysconfig/iptables/table/append[. =

Hi! I using Augeas to handle dump and passno for certain mount points in /etc/fstab. Each mount point is defined as it''s own augeas block: augeas { ''homeLV'': context => ''/files/etc/fstab'', changes => [

what i thought would be a simple edit using augeas is turning out to not be so straight forward, can anyone please help ? the plan is to edit sendmail.cf and change the default DS to DShostname.domain class mail { $key = DS service { ''sendmail'':; } augeas { "sendmail.cf/$key": context =>

Hi, I was running puppet (2.7.5) on a host which needed to have some settings changed in it''s /boot/grub/menu.lst file. This file is however a link to /boot/grub/grub.conf When I used augeas in puppet like shown below augeas { "${dom0::params::module_label}_menu.lst_memory": incl => ''/ boot/grub/menu.lst'', lens => ''Grub.lns'', changes

Don't carry around Augeas lenses. It is fragile, since if the lens is added to upstream Augeas but the version number has not changed, then Augeas won't parse the target file at all. This specifically causes password adjustments to fail in RHEL 7.1. In future, if we need an Augeas lens, it must be added to Augeas, either upstream or as a downstream patch carried around by distros. ---

On Mon, Sep 22, 2014 at 10:49:42AM +0200, Pino Toscano wrote: > The lenses in our custom path need the system lens for base > definitions. Disabling the system path was worthless anyway, since our > API does not allow user-specified custom paths. > > The only possible use for AUG_NO_STDINC to aug-init could have been to > not load the lenses right at init time loading them

On Fri, Apr 28, 2017 at 05:02:29PM +0300, Pavel Butsykin wrote: > > On 20.04.2017 12:19, Pavel Butsykin wrote: > >[This sender failed our fraud detection checks and may not be who they > >appear to be. Learn about spoofing at http://aka.ms/LearnAboutSpoofing] > > > >20.04.2017 10:54, Richard W.M. Jones пишет: > > > >>On Wed, Apr 19, 2017 at 04:58:56PM