similar to: odd facter error with split

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

I am trying to streamline the current distribution specific setup and creation of VE''s within OpenVZ with puppet. My first attempt has gone horribly wrong as you will see below. Here''s the script I wrote to replace the redhat specific setup that OpenVZ used: [jleggett@lxp6d15m3 scripts]$ cat redhat-add_ip.sh #!/bin/bash # # Debug - take out later set -x

I suspect this has more to do with Ruby than Puppet, but I know little about Ruby and Google has failed me, so I''m asking here. I''m finally getting some of our older systems brought into Puppet. I installed it on several this morning without incident, but there are two (more or less identical RHEL 5.3 systems) that throw horrible errors. These systems did not have Puppet or Ruby

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

Hi everyone, I have a puppet master/client infrastructure setup with apache. When on the same datacenter I don''t have any problem. I am trying to use another datacenter, so I setup the fileserver.conf as followed: # Files in the /path/to/files directory will be served # at puppet:///mount_point/. [modules] allow *.datacenter1 allow *.datacenter2 [plugins]

Hi, I have a puppet infrastructure running 2.6.14 under Passenger with about 30 nodes. I''m just spinning up a new Cent 6.3, puppet 2.7.19 master. Right now I have the master built and configured using the same configuration as my 2.6.14 setup, with a few tweaks for the new version. Puppet on the master built itself fine. I have puppetd stopped on the master. I tried pointing one

Anyone know what this is? It doesn''t seem related to puppet but I''m stumped. info: Loading facts in dmidecode info: Loading facts in cpuinfo debug: catalog supports formats: b64_zlib_yaml marshal pson raw yaml; using pson /usr/lib64/ruby/site_ruby/1.8/puppet/indirector/rest.rb:55:in `deserialize'' /usr/lib64/ruby/site_ruby/1.8/puppet/indirector/rest.rb:69:in

How do I debug errors with external nodes? When my client connects, the following appears on the puppetmaster when running in debug mode. It''s not feasible to always be running the pupeptmaster in debug mode. debug: importing ''/etc/puppet/modules/yum/manifests/client.pp'' in environment production info: Automatically imported yum::client from yum/client into production

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

Hello Everybody, I am trying to install the puppetdb on the same machine as am running my puppetmaster. I am getting the following error when am trying to connect the agent: Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Failed to submit ''replace facts'' command for ftldwshost180.wsdev.citrix.com to PuppetDB at

I read somewhere recently about problems with Puppet and Ruby 1.9. I''m wondering if this is still an issue? Thanks. -- 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 puppet-users+unsubscribe@googlegroups.com. For

Hi, I''ve created this fact: require ''facter'' if FileTest.exists?("/etc/ha.d") if `service heartbeat status` =~ /running/ cib = `cibadmin -Q`.grep(/epoch/).to_s epoch = cib.scan(/[0-9]+/).first Facter.add("cib_epoch") do setcode do epoch.to_i + 1 end end end end end I''ve tested it as

Hi, My puppet master don''t want to start anymore. Any idea ? [root@puppetmaster requests]# puppet master --no-daemonize --debug debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/dscl does not exist debug: Puppet::Type::User::ProviderPw: file pw does not exist debug: Puppet::Type::User::ProviderUser_role_add: file rolemod does not exist debug:

For the benefit of those running OEL (Oracle Enterprise Linux) or OVS, be aware that under 2.6.0rc4 facter doesn''t properly recognize OEL in /usr/lib/ruby/site_ruby/1.8/facter/operatingsystemrelease.rb. A diff for a fix is below; probably not the best fix but if you need it work now, this''ll do it for you. I''ve already filed a bug:

Trying to get an EC2 AMI running puppet 0.25 and i''m hitting a problem. After installing the rpms and starting puppet it was just quitting with only: puppetd[3313]: Reopening log files In the log file. When running it with the following I get some more output. -bash-3.1# puppetd -D -d -t --trace debug: Puppet::Type::User::ProviderUser_role_add: file roleadd does not exist debug:

I am working on building a facter tag based node classifier similar to https://github.com/jordansissel/puppet-examples/tree/master/nodeless-puppet/. However, I have run into an issue where I cannot use puppet''s require file ability to push the yaml file containing the facts file to the client because it would require two runs of puppet to pickup changes. Consequently, I have written into

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

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|

Hi, Is it possible to have an array as the output of a custom fact? And then to pass it into a template in Puppet? I currently have a fact that looks like this: Facter.add("exports") do setcode do case Facter.hostname when (/thishost/i): [ "/local", "/local2" ] end end end & a template like this: <%

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