Hi all,

I am seeing the same error recently and here's the output after the last 
modification:

facter --debug --trace virtual
about to execute /bin/uname -s
Could not retrieve virtual: Invalid argument - 
/sys/firmware/dmi/entries/1-0/raw
about to execute /sbin/virt-what 2>/dev/null
value for lsbdistid is still nil
about to execute /bin/uname -m
about to execute /sbin/lspci 2>/dev/null
physical

facter --debug --timing virtual
about to execute /bin/uname -s
kernel: 2.50ms
Could not retrieve virtual: Invalid argument - 
/sys/firmware/dmi/entries/1-0/raw
about to execute /sbin/virt-what 2>/dev/null
virtual: 32.02ms
lsbdistid: 0.23ms
value for lsbdistid is still nil
operatingsystem: 0.85ms
about to execute /bin/uname -m
hardwaremodel: 2.33ms
architecture: 5.50ms
about to execute /sbin/lspci 2>/dev/null
virtual: 25.62ms
physical

Hopefully this helps 'cause I can't figure it out.

Thank you for your help.


On Wednesday, May 8, 2013 12:14:25 AM UTC+3, Stefan Schulte wrote:
>
> On Tue, 7 May 2013 13:00:53 -0700 (PDT) 
> Charlie Brune <[email protected] <javascript:>> wrote: 
>
> > [root@hogwarts ~]# facter --debug --timing virtual 
> > kernel: 2.97ms 
> > Could not retrieve virtual: Invalid argument - 
> > /sys/firmware/dmi/entries/1-0/raw 
> > virtual: 50.26ms 
> > lsbdistid: 0.53ms 
> > value for lsbdistid is still nil 
> > operatingsystem: 2.00ms 
> > hardwaremodel: 3.36ms 
> > architecture: 10.61ms 
> > virtual: 34.97ms 
> > physical 
> > 
> > 
> > Charlie 
> > 
>
> Still not sure what is going on here. I guess the "Invalid argument" 
> is the output of an external command that is failing. So if you 
> could make the following modification in `util/resolution.rb` (the 
> exact path may be different on your machine, on mine it 
> is 
> `/usr/lib/ruby/gems/1.9.1/gems/facter-1.7.0/lib/facter/util/resolution.rb`) 
>
>
> goto line 171 and change 
>
>       
>     begin 
>       out = %x{#{code}}.chomp 
>       [...] 
>
> to 
>
>     begin 
>       Facter.debug "about to execute #{code}" 
>       out = %x{#{code}}.chomp 
>       [...] 
>
> if you now run `facter --debug virtual` you should see the exact 
> external commands facter is executing. This migh be helpful when 
> finding the root cause of your problem here. 
>
> -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 [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to