similar to: Template aren't generated on few nodes

Hello list. I am trying to read the IP address of the eth0 interface from a CentOS 6.5 VM (XenServer). Running the manifest gives empty values to all of the following vars: $ipaddress, $ipaddress_eth0, and its $::<name> version. $interfaces has "eth0,lo". Running facter from the VM I get: # facter -v 2.0.1 # facter | grep virtual is_virtual => true virtual => xenu #

Hello, when running the command "ip a" on a debian VM, I get this 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast

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

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

Greetings, I''m trying to wrap my head around a solution to a problem I''m facing with an exported resources configuration I have. I''m using the following simple config to build a munin configuration: @@file { "/etc/munin/munin.conf.d/${::fqdn}.node": content => "[All Hosts;${::fqdn}] address ${ipaddress_eth0} use_node_name yes\n\n", tag

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

Hello, I would like to have the following line (among others) in my /etc/xinetd.d/rsync file : server_args = --daemon --address=<ipaddress_eth0> --log-file=/var/log/rsyncd.log To this end, i am using the camptocamp rsyncd module available from git. Everything works except this line. I thought it was, perhaps, a questions of spaces (this has been discussed on the list before),

I am trying to wrap my head around using templates and was wondering what the execution context was, puppetmaster or client? I thought it was client since it would have to also account for facter-based variables, but recent testing on something I thought was pretty neat turned out to cause puppetmaster to segfault in an apparent attempt to evaluate the template on the server side. The

Hi all, I''m trying to build a motd template for all my linux machines. This should contain two type of variables: - client side (from facter), like operatingsystem and architecture - supplied by the master, after parsing a text file (or querying a mysql db), like description and location. So. Where are the template variables evaluated? On the client or on the master? Any hints on how I

I recently upgraded my Puppetmaster to 0.24.4 and it looks like my templates are not working properly. All of my clients use the same certificate, built by my original client "xx". I do this using the certname=blah parameter in the puppet.conf on each client. Up until I upgraded each client would use the "xx" certificate (which I had renamed to "blah") and

I am writing a hp ilo module to automatically assign a static ip that is derived from the IP of the system which is fed in via facter. I basically just need to change the network the ilo is connected to. The ruby code works great inside the irb console. However, puppet doesn''t seem to be able to use the variable I have derived from the ipaddress. This is my first template so I am not

So, looks like the latest facter has fqdn... cool. but for some reason templates can''t access it. I was defining $fqdn in my site.pp, but had to remove it after the last yum update, which brought in a new facter package. But now my templates can use fqdn. Why would this happen? --jason

Hi All, I''ve been trying to use Hiera for node classification, my sit.pp is simple: node default { hiera_include("classes") } which has been working well with simple class definitions like: user@host$ cat testagent.yaml 2012-06-18 14:55:48 jon pts/13 --- classes: - motd Is anyone doing this in production? I''ve seen a little about this on line but it

I have this in nodes.pp $puppetmaster_fqdn = generate("/usr/bin/facter","fqdn") and this in a template http://<%= puppetmaster_fqdn %>:8080 When puppet runs, this is the result: http://puppet.home :8080 Anybody any clue to whats causing this? I''ve tried -%> -- You received this message because you are subscribed to the Google Groups "Puppet

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

Facter 1.6.12-rc1 is a maintenance release candidate in the 1.6.x branch with bug fixes. Downloads are available at: * Source: https://downloads.puppetlabs.com/facter/facter-1.6.12-rc1.tar.gz RPMs are available at https://yum.puppetlabs.com/el or /fedora Rubygem available at http://rubygems.org/gems/facter or by using the --pre option to gem install. Debs are available at

Facter 1.6.12 is a maintenance release in the 1.6.x branch with bug fixes. Downloads are available at: * Source: https://downloads.puppetlabs.com/facter/facter-1.6.12.tar.gz RPMs are available at https://yum.puppetlabs.com/el or /fedora Rubygem available at http://rubygems.org/gems/facter Debs are available at https://apt.puppetlabs.com Mac package is available at

Facter 1.6.13 is a maintenance release in the 1.6.x branch with bug fixes. Downloads are available at: * Source: https://downloads.puppetlabs.com/facter/facter-1.6.13.tar.gz RPMs are available at https://yum.puppetlabs.com/el or /fedora Rubygem available at http://rubygems.org/gems/facter Debs are available at https://apt.puppetlabs.com Mac package is available at

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

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