Displaying 20 results from an estimated 4000 matches similar to: "Puppet agent daemon not seeing a Facter fact"
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|
2007 Jun 13
3
Facter ''operatingsystemrelease'' fact.
From looking at the Facter code, it looks like the
''operatingsystemrelease'' fact is currently a mirror of the
''kernelrelease'' fact.
I''d like to implement this fact so that it returns the major version of
the operating system, eg:
Debian Sarge: operatingsystemrelease => 3.1
Debian Etch: operatingsystemrelease => 4.0
RHEL3 update 8:
2013 May 13
2
Creating defined resources based on array of parameters.
Hi all,
With the goal of making my code a little more DRY, I am trying to define
resource parameters in an array of hashes, and then create defined
resources from these array items. I am having trouble figuring out the
syntax for accessing the hash values for the hash currently being worked on
("self?").
Here''s the code to make it clear:
##### Configuration arguments
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
2013 Jun 24
4
Disable certain facter facts?
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
2009 Jul 01
1
Facter infinite looping on custom facts
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
2012 Aug 16
2
Custom Facts accessible via Facter
I don''t get it. I just wrote a simple test custom fact in ruby (ugh, I
hate ruby) and was able to access it as a variable on the client side.
However, it doesn''t appear in the facter output. Is is supposed to?
Doug
--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To post to this group, send email to
2012 Jun 26
2
access "indexed" facter facts
Hi everyone,
I have a fact which looks like that: drbdconnectionstate0. You see the "0"
at the end... Now I''d like to access this fact in a "dynamic" way, the "0"
should be variable. I''m thinking of something like that: if
${drbdconnectionstate0}${drbddevice} == ''Unconfigured''.
But as you may guess, this does not work... Has
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
2006 Jul 28
1
List of Facter "facts"
[This email is either empty or too large to be displayed at this time]
2012 Feb 07
1
Removing custom facts from Facter
Hi,
I need to remove a custom fact from facter. How to do this? For now, I
set the environment variable FACTER_customfact = something but would
like to get rid of it permanently.
Thanks,
Werner
--
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
2007 Jun 22
1
Where are Facter facts?
I can''t seem to find anyplace that list the facts that I can us in my
puppet scripts; can somebody please point me in the right direction?
--
--
Perfection is just a word I use occasionally with mustard.
--Atom Powers--
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
2011 Jan 26
3
You cannot save facts to the code store; it is only used for getting facts from Facter
I have successfully updated puppet clients from my master using the
built-in WEBrick server. When I updated my setup to using
Apache2+passenger, my clients get this error message:
err: Could not retrieve catalog from remote server: Error 400 on
SERVER: You cannot save facts to the code store; it is only used for
getting facts from Facter
warning: Not using cache on failed catalog
err: Could not
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
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
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:~