Hmm, what does the ENV say the user is? Does that user have appropriate permissions on the files in the PATH?
The errors mean for some reason the Ruby runtime environment can't access those executables. Not sure why... On Thu, Nov 13, 2008 at 1:35 PM, martin <[EMAIL PROTECTED]> wrote: > > > > On Nov 13, 9:07 pm, Luke Kanies <[EMAIL PROTECTED]> wrote: > > > As Andrew says, the providers must be considered unsuitable because > > they're missing executables. > > > But the executables are in the PATH, even in the incorrect one. > > > You *can* set the path in puppet.conf; try that. > > > I fixed the virtual fact, and got the correct PATH. > > But it still fails when run through cron (even though the PATH contain > all commands the providers are looking for). > > Another thing which could be wrong are the facts. What is the best way > to dump them from within puppet? > > cheers, > /Martin > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
