On Tue, 7 May 2013 10:01:03 -0700 (PDT) Charlie Brune <goo...@bruneworld.com> wrote:
> I did discover that Puppet appears to be running just fine. I think > the problem may be isolated to facter and puppet appears to forgive > the problem. 8-) > > Here's the output you requested. (I don't see a trace.) > > [root@hogwarts log]# facter -v > > 1.7.0 > > [root@hogwarts log]# facter --debug --trace virtual > > Could not retrieve virtual: Invalid argument - > > /sys/firmware/dmi/entries/1-0/raw > > value for lsbdistid is still nil > > physical > > [root@hogwarts log]# > > > > > Ok can you then please run `facter --debug --timing virtual`. This should give you something like % facter --debug --timing virtual kernel: 2.94ms virtual: 0.06ms virtual: 0.44ms lsbdistid: 20.66ms operatingsystem: 22.72ms hardwaremodel: 2.37ms architecture: 30.14ms virtual: 57.26ms physical So the `--timing` option has the neat benefit that we see what other facts facter has to resolve to get to the `virtual` fact. If you could provide the values for these facts as well I should be able to follow the actual code path and see where facter may have problems. -Stefan -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.