[Puppet Users] Re: Could not evaluate: 'test' is not executable

2010-12-20 Thread Rudy Gevaert
On Friday, December 10, 2010 11:34:15 AM UTC+1, luke.bigum wrote: > > > file called 'grep'... Removing this stray file and puppet now runs > fine :) > > Hi Luke. Yes you are right! I had a file called test in /root ! thanks! -- You received this message because you are subscribed to the

Re: [Puppet Users] Re: Could not evaluate: 'test' is not executable

2010-12-10 Thread Patrick
On Dec 10, 2010, at 3:40 AM, luke.bigum wrote: >>> This doesn't appear to affect the actual execution of commands, so >>> don't be worried about the wrong commands being executed based on the >>> CWD of Puppet. >> >> Except it might be. Puppet might have been trying to execute the file and >>

[Puppet Users] Re: Could not evaluate: 'test' is not executable

2010-12-10 Thread luke.bigum
> > This doesn't appear to affect the actual execution of commands, so > > don't be worried about the wrong commands being executed based on the > > CWD of Puppet. > > Except it might be.  Puppet might have been trying to execute the file and > then failing because the permissions were 644 instead

Re: [Puppet Users] Re: Could not evaluate: 'test' is not executable

2010-12-10 Thread Patrick
On Dec 10, 2010, at 2:34 AM, luke.bigum wrote: > Thanks for the suggestion Patrick, it led me to the cause of the > problem :) > > I wrote a very simple local test manifest to emulate the Exec problem > with 'puppet apply' and it still occurred. Out of pure habit, I often > execute 'ls -l' when

[Puppet Users] Re: Could not evaluate: 'test' is not executable

2010-12-10 Thread luke.bigum
Thanks for the suggestion Patrick, it led me to the cause of the problem :) I wrote a very simple local test manifest to emulate the Exec problem with 'puppet apply' and it still occurred. Out of pure habit, I often execute 'ls -l' when I switch between terminals (so I know where I am) and noticed

Re: [Puppet Users] Re: Could not evaluate: 'test' is not executable

2010-12-09 Thread Patrick
On Dec 9, 2010, at 9:14 AM, luke.bigum wrote: > Interesting, I've noticed that puppet runs triggered from a daemonised > puppetd aren't affected by the problem (as Dashboard and /var/log/ > messages says their is no errors), but when run from the command line > as puppetd --test it fails as usual

[Puppet Users] Re: Could not evaluate: 'test' is not executable

2010-12-09 Thread luke.bigum
Interesting, I've noticed that puppet runs triggered from a daemonised puppetd aren't affected by the problem (as Dashboard and /var/log/ messages says their is no errors), but when run from the command line as puppetd --test it fails as usual for me: err: /Stage[main]/Fh_freetds/Exec[change /etc/

[Puppet Users] Re: Could not evaluate: 'test' is not executable

2010-12-09 Thread luke.bigum
Hi Rudy, I'm not sure if you fixed this yet, but I ran into the same problem using grep in an unless parameter of an exec resource. I went looking through the Ruby code, in /usr/lib/ruby/site_ruby/1.8/ puppet/type/exec.rb on line 571. I changed these four lines: unless FileTest.executable?