On Jun 20, 4:54 pm, "[email protected]" <[email protected]>
wrote:
> I tried using "try the logouput => ON_FAILURE in the exec."
> But my client is a puppet CentOS. (The puppet version is outdated).
> Not recognizing this parameter.
>
> As you asked, I used the - debug.
> The output was this:http://pastie.org/2098147
The command that is failing now is 'cp -rp /usr/share/wordpress/ /var/
www/zertico'. Based on the manifests you attached, it looks like you
use this executable path: ["/usr/local/bin", "/opt/local/bin", "/usr/
bin", "/usr/sbin"] (but I can't be sure, because your manifests don't
exactly match your log). On my CentOS 5 boxes, the cp command is in /
bin (only; this is the LSB-mandated location), so it will not be found
when Puppet attempts to apply your Exec. Given that you're running a
simple command rather than a script, I'd recommend that you just
specify the full path to the cp command (i.e. /bin/cp) instead of
using a separate 'path' parameter.
> I discovered that any command that has not executed any parameter. Only simple
> commands.
> exec {"Free": path => ["/ usr / bin"]}
>
> The problem really is in the function "exec".
The problem is in the specific Exec resource(s) in your manifest.
Exec in general works fine for many, many people, with a wide variety
of commands.
John
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
