search for: facterversion

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 kernel => Linux kernelmajversion => 2.6 kernelrelease => 2.6.1...

Hello, I am installing Puppet Enterprise agent (puppet-enterprise-1.2.1- solaris-10-sparc) on a Solaris 10 64bit SPARC system. When I view the logs for the agent I see: puppet-agent[14680]: [ID 702911 daemon.error] Could not run Puppet configuration client: Could not retrieve local facts: private method `split'' called for nil:NilClass The client successfully initiates a cert exchange

...//ftp.ie.debian.org/debian <%= lsbdistcodename %> main contrib non-free deb http://security.debian.org/ <%= lsbdistcodename %>/updates main Now the problem is that for squeeze, it does not work as lsbdistcodename gets n/a instead, is there any way to fix this? architecture => amd64 facterversion => 1.5.7 hardwareisa => unknown hardwaremodel => x86_64 id => root is_virtual => true kernel => Linux kernelmajversion => 2.6 kernelrelease => 2.6.26-2-amd64 kernelversion => 2.6.26 lsbdistcodename => n/a lsbdistdescription => Debian GNU/Linux 6.0 (n/a) lsbdistid =&...

...by/site_ruby/1.8/puppet/network/client.rb: 94:in `initialize'' from /opt/csw/lib/ruby/site_ruby/1.8/puppet/network/client/ master.rb:198:in `initialize'' from /opt/csw/bin/puppetd:328:in `new'' from /opt/csw/bin/puppetd:328 # /opt/csw/bin/facter facterversion => 1.5.4 kernel => SunOS kernelrelease => 5.10 kernelversion => Generic_139556-08 operatingsystem => Solaris operatingsystemrelease => 5.10 puppetversion => 0.24.8 rubysitedir => /opt/csw/lib/ruby/site_ruby/1.8 rubyversion => 1.8.7 Machine that works: ================ #...

...76675410 with 1 changes debug: Calling puppetmaster.getconfig err: Could not retrieve configuration: Certificates were not trusted: certificate verify failed warning: Not using cache on failed configuration allo01# openssl version OpenSSL 0.9.7e-p1 25 Oct 2004 allo01# facter domain => xxxxxx facterversion => 1.3.5 fqdn => xxxxxxxxxxxxxxxxxx hardwaremodel => i386 hostname => allo01 ipaddress => xx.Xx.xx.xx kernel => FreeBSD kernelrelease => 6.0-RELEASE operatingsystem => FreeBSD operatingsystemrelease => 6.0-RELEASE ps => ps -auxwww puppetversion => 0.19.3 rubysitedir...

...shorewall-zone { "testname": SHTYPE => ''ipv4'', PARENT => "test" } and still got the error. This is puppet: facterversion => 1.3.7 hardwaremodel => i686 hostname => puppet id => root kernel => Linux kernelrelease => 2.6.20.4-vs2.2.0 lsbdistcodename => sarge lsbdistdescription => Debian GNU/Linux lsbdistid => Debian lsbdistrelease => 3.1 puppetversion => 0.22.3 rubysitedir => /usr/lo...

...it will be a lot of changes to password where there really is not an issue. Since I am trying to get this working across the board for HPUX I wanted to try to hack out the fix myself but have hit a wall. Pertinent Details for the host on which I am finding these issues: architecture => ia64 facterversion => 1.6.12 fqdn => cadcpuppet hardwaremodel => ia64 hostname => cadcpuppet id => root interfaces => lan0,lo0 is_virtual => true kernel => HP-UX kernelmajversion => B.11 kernelrelease => B.11.31 kernelversion => B.11.31 operatingsystem => HP-UX operatingsystemrelea...

...ct to load up location specific file with site specific configuration. It uses the rescue call as describe in "Adding Facts": begin Facter.location rescue Facter.loadfacts() # Line 22 end Most of the time, facter works # facter architecture => i386 . esx_version => 3.5.0u3 facterversion => 1.5.5 . . location => HERE . . However, sometimes, some servers (I can''t see a pattern yet) will have facter go into an infinite loop until there is no more memory. The only way I have been able to reproduce it, is with renaming the files. NB The files originally were named with...

...tall.rb d008d35 (maint) Update debian/rules to use new --ruby flag 43d3e68 Update default cows 4cb1030 Remove asc file a source for RPM builds 903b298 Spec file cleanup 25cb69f Remove INSTALL from Facter cc2015d Remove CHANGELOG from Facter e81b3ab Updating FACTERVERSION for facter 1.6.13-rc1 Matthaus Owens (1): 8083990 Update facter debian packaging for 1.9 support Michael Renz (10): 262ef6a (#1415) Added case for Linux/IB to get correct IB address or fail predictably. 240dfac (#1415) ifconfig should not run twice for Linux. d4d0b80 (#141...

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

...s still nil value for cfkey is still nil value for kernel is still nil value for lsbdistcodename is still nil value for kernel is still nil value for hostname is still nil value for hostname is still nil value for kernel is still nil value for operatingsystem is still nil domain => my.domain.com facterversion => 1.3.7 ps => ps -ef puppetversion => 0.22.4 rubysitedir => /usr/local/puppet/lib/ruby/site_ruby/1.8 rubyversion => 1.8.2 sshdsakey => (....the dsa key...) sshrsakey => (...the rsa key...) I couldn''t find any reference to this issue anywhere...if it''s docum...

...62 (#15464) Make Facter.version settable via Facter.version= Matthaus Litteken (4): defbfb8 (#15291) Add Vendor tag to Facter spec file bf6ee4f Retabbed conf/redhat/facter.spec to lineup tag contents. 42bec60 Updating CHANGELOG and version.rb for 1.6.12-rc2 5a3e537 Updating FACTERVERSION and CHANGELOG for 1.6.12 Moses Mendoza (22): 1bbbc4d Update a facter build-requires for f17 7ca9122 Update a facter build-requires for f17 17243bb Update facter redhat spec for fedora 17 db9d154 Move packaging files to ext, rm conf 6f58b4e Move tasks out of ''...

...39;. Cannot modify/add NIS group entries. usermod: User not added to LDAP group `dduck''. notice: Finished configuration run in 6.44 seconds The default for useradd, usermod, etc is to use files unless the --service flag is set. Facter: architecture => i386 domain => example.com facterversion => 1.3.6 fqdn => puppetserver.example.com hardwareisa => i686 hardwaremodel => i686 hostname => puppetserver id => root ipaddress => 10.10.10.15 kernel => Linux kernelrelease => 2.6.16.27-0.9-bigsmp macaddress => 00:10:18:17:BF:E6 00:10:17:17:BF:E6 00:10:18:18:BF:E6 00...

...fo: Creating a new SSL key at /etc//opt/csw/puppet/ssl/private_keys/ core4.adcom.uci.edu.pem debug: Calling puppetca.getcert warning: peer certificate won''t be verified in this SSL session notice: Did not receive certificate (core4) root:/opt/csw/bin # facter domain => YP.adcom.uci.edu facterversion => 1.5.2 fqdn => core4.YP.adcom.uci.edu hardwareisa => sparc hardwaremodel => sun4v hostname => core4 interfaces => lo0,e1000g0 ipaddress => 128.200.235.71 ipaddress_e1000g0 => 128.200.235.71 kernel => SunOS kernelrelease => 5.10 kernelversion => 5.10 macaddress =&g...

Hello I am entertaining the idea of putting some time and effort into making Facter and Puppet run on MS Windows. Call me crazy ... Does anyone know anything about the issues that I''m likely to face? What are the major stumbling blocks? Initially I''d be happy just getting File to work, this would be of tremendous value. I''m guessing that Facter will require the

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

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

Puppet version: 0.22.4 facterversion => 1.3.7 rubyversion => 1.8.5 Given the following: file { yum_repo_d: path => "/etc/yum.repos.d", ensure => directory, recurse => true, purge => true } yumrepo { pkg_repo: descr => "Packages Repository", enabled => 1, baseur...