similar to: Facter & Puppet disagree on RHEL 6?

Hi I am new in Puppet and i have one error when i test Postgresql module in infrastructure mode. I''m using Puppet 3.1.0 in Debian squeeze or 6.0.7 i tape the next command puppetd -t -v and this is the error info: Retrieving plugin info: Loading facts in pe_version info: Loading facts in postgres_default_version info: Loading facts in iptables info: Loading facts in puppet_vardir

Dear All, I''m very new to Puppet Enterprise.... I have the following setup so far: 1. Puppet Master (Puppet Ent) on Ubuntu with its own Agent 2. Puppet Agent on MAC Mountain Lion Everything looked ok but then I noticed this on the MAC (below), which suggested to me I had the wrong Agent? I''m a little confused on how to get the Puppet Ent Agent for MAC? Info: Retrieving

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

Hi, I am trying to use Hiera in puppet 3 and I have two nodes that both need the same configuration. In this case they are two web servers which have the same apache configuration. Rather than creating two seperate hiera files for node1.yaml and node2.yaml is there a way to group these by role (e.g. webserver.yaml)? I want to avoid duplicating the configuration if possible and keep the data

Hi all, just installed the puppetlabs-mysql module for puppet on my Puppet server which is an Amazon Linux (based on RedHat), but I get this error when I run puppet agent --test : *err: Could not retrieve catalog from remote server: Error 400 on SERVER: Unsupported osfamily: Linux operatingsystem: Amazon, module mysql only support osfamily RedHat and Debian at

Hello, I created puppet class and I want the file operation to be executed on all servers but not on server with hostname "''server1.domain.com". I tried this class, but it does not work. Is there any other way? Thanks class test { if $hostname != ''server1.domain.com'' { file { "/etc/ntp.conf": owner

I''m currently trying to create icinga module and the icinga-web and icinga-idoutils-libdbi-mysql from rpmforge store the initial sql file in version numbered directory(/usr/share/doc/icinga-web-1.7.2/~~~). So, I try to determine the version number from the yum info like as below, but that repository installed after my yum module gets work done. Is there any ways to fetching custom

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

Hello, I''m running Puppet agent stand-alone on Windows. I got data-in-modules working. However, no matter what I put into the module hiera.yaml, I can only override the defaults from common.yaml by osfamily (and not, e.g., by environment). In the setup below the following command outputs: >puppet apply --binder -e "notice lookup (''my_key'')"

As some before me on the group, I have a problem getting the Chocolatey provider to work on Windows. I downloaded it from Github and placed it in /etc/puppetlabs/puppet/modules/chocolatey. (I am running Puppet Enterprise 2.7.19). On a Windows 8 client, I have a very simple manifest: class install_notepadplusplus { if $::osfamily == ''windows { $pkg =

Facter 1.6.2 is a maintenance release containing fixes, updates and refactoring. Primary new features include updated facts for DragonFly BSD, Amazon Linux and Windows. A few other facts have been added and updated. Full release notes below. This release is available for download at: http://puppetlabs.com/downloads/facter/facter-1.6.2.tar.gz See the Verifying Puppet Download section at:

I''m having a problem with variable interpolation that I haven''t found a good solution to. I want to use a variable as part of the name of a fact, but the interpolation doesn''t work as expected. I''ve allowed for passing the mac address into my define() but if it''s not provided I want to look it up via facter. if

I''ve written and deployed a simple Linux SSH module. But I need to modify to include support for FreeBSD and AIX. On top of that, I need to include some conditionals in there that (for example) if (/etc/file1 contains string abc) ; then install sshd-config-x & ssh-config-x elsif (/etc/file1 contains string xyz); then install sshd_config-y & ssh_config-y else install

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

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

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''m trying to get puppet working for the first time, and I''ve run into something that''s got me stumped. This is all on Solaris 10/x64. The initial startup of puppetmasterd wasn''t working, and it appeared to be related to the SSL certs not getting generated properly. I managed to trace that down to the fact that facter isn''t finding the

Hi all, I''ve finally gotten around to releasing Facter 1.5. As the version bump implies, this is a relatively significant release (for a 2.3k line program, anyway). Mostly, the biggest change is refactoring the code internally so that all of the functionality is split into separate classes in separate files. Also, the facts are all loaded on-demand, which provides dramatic

I have 2 RHEL 5.4 systems where all facter lsb* items are missing. Any ideas? Sanitized facter output: architecture => i386 domain => missyou.edu facterversion => 1.5.7 fqdn => broken.missyou.edu hardwareisa => i686 hardwaremodel => i686 hostname => broken id => root interfaces => eth0,sit0 ipaddress => 1.2.1.5 ipaddress_eth0 => 1.2.1.5 is_virtual => true

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