Providing this isn't a production host, I'd use locate to find the file
posix.rb (that's your built-in file provider), then insert some puts
statements to see if you can find out exactly where in the code it's
failing.
On Friday, March 27, 2015 at 3:49:24 PM UTC+11, Gabriel Filion wrote:
>
> On
On 27/03/15 12:40 AM, Gabriel Filion wrote:
>> Failing that, strace'ing might show you something more useful.
> I'll see what I can find with strace...
unfortunately, nothing really useful..
in the output below, the first file access gives the same error as the
one failing, but seems to work ok:
On 24/03/15 05:03 PM, Christopher Wood wrote:
> On Tue, Mar 24, 2015 at 04:30:27PM -0400, Gabriel Filion wrote:
>> I'm having issues with one server when it tries to apply a super simple
>> file resource that ensures a file is absent:
>>
>> file { '/etc/munin/plugin-conf.d/uptime.conf': ensure => a
On Tue, Mar 24, 2015 at 04:30:27PM -0400, Gabriel Filion wrote:
> Hello,
>
> I'm having issues with one server when it tries to apply a super simple
> file resource that ensures a file is absent:
>
> file { '/etc/munin/plugin-conf.d/uptime.conf': ensure => absent }
>
> I can easily replicate thi
Hello,
I'm having issues with one server when it tries to apply a super simple
file resource that ensures a file is absent:
file { '/etc/munin/plugin-conf.d/uptime.conf': ensure => absent }
I can easily replicate this with a puppet apply -e of the above line.
I get the following error:
err: /S
