Displaying 20 results from an estimated 20000 matches similar to: "facter doesn't load from /ect/facter/facts.d"
2013 Mar 11
3
custom puppet facts
I have written a custom puppet fact using a ruby script. It is very simple
- it just adds a string to a fact. However I have written a module but it
appears to me that the custom fact has been applied to all my machines
without me specifying any node definitions. When I run a puppet agent
--test --noop, I see the custom fact appear in /var/lib/puppet/lib/facter.
Info: Loading facts in
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
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
2013 May 14
3
PuppetDB "Failed to submit 'replace facts' command"
I have a small environment with a single puppetmaster and puppetdb on the same node that I get sporadic "Failed to submit ''replace facts'' command" errors from nodes. It isn''t consistent about which nodes are causing the error and I can''t find anything else going on at the same time on either the master or the agent that these errors happen.
Here
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
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
2013 Sep 18
1
All nodes stopped reporting to puppet enterprise console
My install was working for a couple of months until I rebooted my puppet
server. The clients do not report an error when I run puppet agent -t.
I''ve attempted to remove certificates and renew. The clients get new
certificates, but the console still does not update. Even the puppet
server itself is not updating as a client. After reboot the only thing I
have noticed that changed
2013 Feb 21
8
Facter & Puppet disagree on RHEL 6?
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 ==
2012 Apr 11
8
Facter not initialized in rspec in puppetlabs-stdlib?
I have been working on adding some predicate functions to puppetlabs-stdlib
that test things based on ''interfaces'' and related facts.
The functions themselves seem to work fine in my manifest-based smoketests,
but I am running into trouble that may or may not be due to my ignorance
about rspec or Facter. Something needs to be done to initialize Facter
because
2012 Oct 11
3
puppet facts.d executable PROBLEM
Hi folks,
I''m using this
plugin https://github.com/ripienaar/facter-facts/tree/master/facts-dot-d
and I can''t get a fact out of a simple shell script. YAML TXT JSON works
well
My little shell script testfact.sh looks like
#!/bin/bash
echo "TEST=NOT WORKING"
made it executable
chmod +x testfact.sh
made a puppet agent -t to read the new fact
BUT
$facter --puppet
2013 Jun 12
4
certificate problem
When I try to connect to my new puppet master, I get an error because of
a self-signed certificate:
---snip---
# puppet agent --test --noop
Warning: Unable to fetch my node definition, but the agent run will
continue:
Warning: SSL_connect returned=1 errno=0 state=SSLv3 read server
certificate B: certificate verify failed: [self signed certificate in
certificate chain for /CN=Puppet CA:
2013 Apr 18
4
fact_stomp_server
Does anyone have any insight into this error message?
err: Could not retrieve catalog from remote server: Error 400 on SERVER:
The fact named fact_stomp_server does not appear to be a valid hostname.
The value of '''' does not match ''^[a-zA-Z0-9.-]+$''. A common cause of this
problem is running puppet agent as a normal user instead of root, or the
fact is
2013 Dec 13
2
New to puppet and recieving mcollective error
Im new to puppet and installed it in my home lab to mess with, when i
installed it i used the hostname rather than FQDN so went back and changed
puppet and reran the certificate tool to regenerate the certificates etc,
the agent works fine now but i am getting an mccollective error i think, is
there anything in the config i need to change for mccollective after
altering the name to the FQDN?
2012 Nov 06
19
puppet failing to run
I am getting this error after installing puppet with gem
$ gem install puppet
Fetching: facter-1.6.14.gem (100%)
Fetching: puppet-3.0.1.gem (100%)
Successfully installed facter-1.6.14
Successfully installed puppet-3.0.1
2 gems installed
Installing ri documentation for facter-1.6.14...
Installing ri documentation for puppet-3.0.1...
Installing RDoc documentation for facter-1.6.14...
Installing
2013 Aug 28
3
agent will not run
Hi,
I wonder why the puppet agent on the server itself will not run:
---snip---
# puppet agent --test
Error: Could not run Puppet configuration client: Puppet::Node does not
respond to from_s; can not intern instances from text/plain
Error: Could not run: can''t convert Puppet::Util::Log into Integer
---pins---
whereas the client on a test box tells me:
---snip---
# puppet agent --test
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|
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
2011 Jan 07
4
facter --puppet does not report "environment"
Is it normal that "facter --puppet" does not show the environment
variable? is there a way to have it include it?
Thanks a lot,
Mohamed.
--
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 group, send email to
2012 Jul 17
8
How to override $::operatingsystem fact
Hi,
I want to introduce "Proxmox" as new value in $::operatingsystem.
"Proxmox" is based on Debian, so the normal value is currently "Debian".
To change that, I just write a custom fact based on the facter fact
"operatingsystem"
Facter.add(:operatingsystem) do
> ...
> setcode do
> ...
> elsif
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,