Displaying 20 results from an estimated 2000 matches similar to: "Weird Facter behaviour"
2012 May 16
2
Announce: Facter 2.0.0rc1 Available
Facter 2.0.0rc1 is a feature release candidate with bug fixes,
features and other improvements.
Facter 2.0 is designed to accompany the upcoming Puppet 3.0 release
and has breaking changes from Facter 1.6.x. Facter 2.0 is not
backwards compatible with Puppet 2.6 or 2.7.
It includes contributions from the following people: Chris Price,
Daniel Black, Daniel Pittman, Garrett Honeycutt, Gary Larizza,
2007 Jul 17
5
Recommended way to set $FACTERLIB?
Is there a recommended way to set $FACTERLIB so that Puppet will be able
to access custom facts when running as a Red Hat service?
If I export $FACTERLIB=/var/puppet/facts and then run Puppet manually I
have no problems, but I''m not sure how I should be setting $FACTERLIB
when Puppet is running automatically.
Cheers,
James
2011 Apr 07
12
Mutliple custom facts not showing in facter
Hi,
I''ve noticed that defining multiple facts in one file is possible, and
puppet can make use of them correctly, but when trying to call with facter
--puppet they are not shown, do I need something special to make them work
as any other single custom fact?
Master is running 2.6.7
This is a custom fact with two facts in it:
[modules/foobar/lib/facter/foobar.rb ]
require
2009 Jul 27
4
Custom fact errors
I''m a newbie attempting to get a custom fact distributed to clients.
I''ve followed the instructions at http://reductivelabs.com/trac/puppet/wiki/AddingFacts
and based my first fact on a simple recipe.
I''m having at least one problem and possibly more.
1) Puppet/facter fails to load the custom fact, complaining that "non-
sh interpreters are not currently
2012 Jan 30
2
SLES11: facter without arguments produces Error: uninitialized constant Facter::IPAddress
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
2013 Sep 11
4
getting array of hostnames of clients
I need to get an array of hostnames of clients of the puppet server.
There doesn''t seem to be a simple way to do this so I''ve tried a few
methods.
I''ve tried a curl expression in a fact like this:
curl -s -k -H "Accept: yaml"
https://localhost:8140/production/facts_search/search?facts.nodetypet=testnodes
where I''ve got a nodetype fact which works
2010 Oct 21
1
SLES11 facter problems
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
2011 Nov 19
2
Facter Windows: domain is "none"
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
2013 Apr 13
6
facter doesn't load from /ect/facter/facts.d
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
2008 Jan 08
1
odd facter error with split
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
2007 Sep 24
2
ANNOUNCE: Facter 1.3.8
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
2009 Jun 03
4
Facter 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
2007 Apr 26
2
[PATCH] facter: add interfaces, default_gateway facts on Linux
Quick and dirty:
--- lib/facter.rb (revision 203)
+++ lib/facter.rb (working copy)
@@ -989,6 +989,18 @@
%x{/usr/sbin/scutil --get LocalHostName}
end
end
+ Facter.add(:interfaces) do
+ confine :kernel => :linux
+ setcode do
+ %x{/sbin/ifconfig -a -s}.split($/)[1..-1].collect {|line|
2008 Dec 01
2
configuring puppet to run custom facts
Hi,
I''m following
http://reductivelabs.com/trac/puppet/wiki/PluginsInModules in order to
use a custom fact.
My modules looks like:
# ls manifests/modules/network/
manifests plugins
# ls manifests/modules/network/plugins/facter/primaryint.rb
manifests/modules/network/plugins/facter/primaryint.rb
as is said in doc.
Then:
Turn on pluginsync and specify factpath, so that the facts
2010 Jan 22
4
facter question
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:~
2009 May 19
5
facter lsbdistid returns no result
Hi all, I am creating a recipe for rhel boxes which needs to
determine what type of install is present (server or client). I
thought I would use the facter fact lsbdistid for this purpose but
when I run "facter lsbdistid" from the command line nothing is
returned. If I just run facter and grep for lsbdistid, what I am
looking for is returned. Does anyone know why this might be?
2009 Apr 24
4
uninitialized constant Facter::IPAddress (NameError)
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
2012 Jun 14
1
facter --yaml leaves some fields blank
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
2013 Sep 21
3
symlink creation using facter, but facter is nil at first run.
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
2011 Aug 17
5
facter-1.6.0 incorrectly identifies hardware node as virtual
I''ve installed facter-1.6.0 and puppet-2.7.3 on a number of SLES 10
hardware nodes (HP DL580) running the Virtuozzo hosting software.
Well, facter correctly identifies such a machine as a hardware node
("virtual => openvzhn") but somehow concludes that the hardware node
is in fact virtual. ("is_virtual => true")
This breaks some rather important logic. If