similar to: facter vs specs

I''m trying to load custom facts via /etc/facter/facts.d/* according to instructions on http://docs.puppetlabs.com/guides/custom_facts.html#structured-data-facts I must have missed a setting somewhere because I get nothing. The first clue may be that /etc/facter didn''t exist. I had to create it manually. Is there a setting or search path I need to create? Details: puppet

I'm trying to compile hello.c with clang.exe, but I'm getting an error about missing cstdlib headers. Source: https://github.com/mcandre/mcandre/tree/master/c/hello/ Trace: C:\Users\andrew\Desktop\src\mcandre\c\hello>gmake clang -O2 -Wall -Wextra -Wmost -Weverything -o hello hello.c hello.c:1:10: fatal error: 'stdio.h' file not found #include <stdio.h> ^ 1

Hi all, I''m trying to find a better way to implement this, but I can''t think of. I have a jdk module that requires to create a symlink to whatever version is the one installed. Say I install jdk-6u35, it will create something like /usr/java/jdk_1.6.35. I would like to create a symlink /usr/java/jdk whose target would be /usr/java/jdk_1.6.35. The point here isn''t to ask

Hi All. I am using: #rpm -qa | egrep ''puppet|facter'' puppetlabs-release-6-7.noarch puppet-3.1.1-1.el6.noarch facter-1.7.1-1.el6.x86_64 on: #cat /etc/redhat-release ; uname -r CentOS release 6.4 (Final) 2.6.32-358.11.1.el6.centos.plus.x86_64 My hostname is server.one.two.com: # hostname server.one.two.com # hostname --fqdn one.two.com #grep HOSTNAME /etc/sysconfig/network

We found out, the hard way, that version 1.7 of Facter adds facts for mounted linux file systems. This is nice for normal servers. For a server hosting Oracle not so good. We went from about 100 facts per server to well over 3,000 (our Oracle boxes have quite a few volumes mounted). Of course, this choked our ENC (Foreman) having this many facts pumped into it and required us to downgrade

I''ve run into an odd one on one of my new RHEL 6 boxes. Puppet and Facter seem to disagree about the value of a fact. Puppet version: 2.7.9 Facter version: 1.6.4 Module: puppetlabs-apache apache::params falls through its if structure: if $::osfamily == ''redhat'' or $::operatingsystem == ''amazon'' { ... } elsif $::osfamily ==

Ran into a problem with Facter on a Windows 2008 R2 system running on a proxmox server. Facter reports the machine as being physical. This is due to the WMI query used in the virtual.rb file is being return "Bochs" as the Manufacturer and Model. Adding an additional "When" statement to the Ruby file (virtual.rb) corrected the check coming back as physical. -- You

Hi all, first post here... reposting this from Stack Overflow as it didn''t get much traction there... I am using puppet to read a fact from facter, and based on that I apply a different configuration to my modules. Problem: the puppet agent isn''t seeing this fact. Running puppet agent --test interactively works as expected. Even running it non-interactively from a script

The facter 1.6.18 tarball has many issues. First, the ext/osx/createpackage.sh script still uses packagemaker, which is deprecated. And even if it used that, there are a few references to files in the now-deleted conf/osx/ directory. So it''s pretty difficult to create a Mac pkg from this, but after some tweaking of the createpackage.sh script, I managed to do it! I ran the package it

Hi, I run into problems with the ipaddress fact using the latest Facter gem (1.6.4, 1.6.5) on SLES11. The versions and gems I use work perfectly fine on SLES10 SP3. The problem: running "facter" without arguments results in an error, even though the erroring fact "ipaddress" is ok. test:~ # cat /etc/SuSE-release SUSE Linux Enterprise Server 11 (x86_64) VERSION = 11 PATCHLEVEL

I installed the 2.6.2 puppet and facter 1.5.8 gems and tried to run puppet, but it failed with the following message: err: Could not run Puppet configuration client: Could not retrieve local facts: uninitialized constant Facter::IPAddress Then I tried running facter alone: # facter /usr/lib64/ruby/vendor_ruby/1.8/facter/ipmess.rb:19: uninitialized constant Facter::IPAddress (NameError) After

I''m new to puppet in general - I just have a minimal node.pp defined for 2 clients so far. Before I reinvent the wheel ... is there a good web UI to facter that everyone uses? I''ve looked over foreman and I figure since it''s new, it''s probably not in widespread use currently. Any suggestions? --~--~---------~--~----~------------~-------~--~----~ You received

Not sure if this is another issue cropping up with 0.24.1 but I''m getting the following: info: Loading fact raid /etc/puppet/facts/location.rb:5: private method `split'' called for nil:NilClass (NoMethodError) from /usr/lib/ruby/site_ruby/1.8/facter.rb:510:in `call'' from /usr/lib/ruby/site_ruby/1.8/facter.rb:510:in `value'' from

Hi All Background: I am running Puppet to configure ESX 3.5 servers by NFS mounting the Puppet binaries and configuration from a shared server. This is to ensure VMware don''t come back refusing support for installing non standard software on the server. # ruby -v ruby 1.8.7 (2009-04-08 patchlevel 160) [i686-linux] # facter -v 1.5.5

Hello, Since i use facter 1.5.5 i got error running it by hand. It still work in puppet but i loosed the hability to run it from the command line: (aqadmin)> /var/lib/gems/1.8/gems/facter-1.5.5/bin/facter /var/lib/gems/1.8/gems/facter-1.5.5/bin/facter:50:in `require'': no such file to load -- facter (LoadError) from /var/lib/gems/1.8/gems/facter-1.5.5/bin/facter:50

I just started getting this error on some machines after a yum update from centos 5.2 to centos 5.3. Does anyone know what it means? Since I''m not a ruby person, I''m not sure how to debug this, but it looks to me like facter is having trouble parsing information about my interfaces. # facter /usr/lib/ruby/site_ruby/1.8/facter/ipmess.rb:19: uninitialized constant

I could swear this worked fine earlier.. Now facter, and hence puppet, do not see the domain name anymore: What could cause this? C:\Temp>facter --version 1.6.2 C:\Temp>facter | findstr kernel kernel => windows kernelmajversion => 6.1 kernelrelease => 6.1.7601 kernelversion => 6.1.7601 C:\Temp>facter fqdn NCS-VDI-05.none C:\Temp>facter hostname NCS-VDI-05

I''ve just committed Facter 1.3.8. All of the work for this release was done by James Turnbull, so everyone should thank him for getting it done. Here''s the changelog: Fixed Rdoc::usage bug on CentOS 5 - closed Puppet #753 and Facter #40 Added support to return multiple interfaces and their IP addresses and MAC addressess as facts. Returns

int he example below I run facter looking for the fact "sp_serial_number". as you can see, the command facter sp_serial_number returns nothing, but the fact is there and is returned when just running facter and grepping for the fact. Some fact seem to work and others do not. any ideas? marcuspro:~ allan$ facter --version 1.5.7 marcuspro:~ allan$ facter sp_serial_number marcuspro:~

Sometimes "facter --yaml" doesn''t list all the values specified on the command line. I can''t find rhyme nor reason why. Here''s a demo to show what I mean: # facter --version 1.5.7 # facter --yaml fqdn macaddress lsbdistcodename --- fqdn: my.host.name.example.com lsbdistcodename: squeeze macaddress: "00:00:00:00:00:00" We had been using the above