similar to: testing puppet with rhn serial key

Hi Everybody, I been looking through google for better part of the day but I haven''t been able to find an answer to my problem. I need an environmental variable to be present in puppet, so that yum works correctly. However after reboot puppet doesn''t read /etc/profile and starts without this profile. If I go into server and do services puppet restart than everything works fine,

May I please ask again for some assistance with the question below? I hope somebody can help me. Thanks, Ed Greenberg -------- Original Message -------- Subject: Re: [Puppet Users] Using custom facts in Puppet Date: Tue, 16 Nov 2010 13:14:06 -0600 From: Ed Greenberg <edg@greenberg.org> Reply-To: puppet-users@googlegroups.com To: puppet-users@googlegroups.com On 11/16/2010 09:33

I''ve got 3 custom facts configured within a couple of modules and am using pluginsync to sync them to the clients. My clients are CentOS 5.7. If I run "puppet agent --test -v", I get the following output and the custom facts get loaded and I can use those facts in my module classes: info: Loading downloaded plugin /var/lib/puppet/lib/facter/oraclehome.rb info: Loading

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

Hi, I''m following http://reductivelabs.com/trac/puppet/wiki/PluginsInModules in order to use a custom fact. My modules looks like: # ls manifests/modules/network/ manifests plugins # ls manifests/modules/network/plugins/facter/primaryint.rb manifests/modules/network/plugins/facter/primaryint.rb as is said in doc. Then: Turn on pluginsync and specify factpath, so that the facts

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

Hi All. I am using: #rpm -qa | egrep ''puppet|facter'' puppetlabs-release-6-7.noarch puppet-3.1.1-1.el6.noarch facter-1.7.1-1.el6.x86_64 on: #cat /etc/redhat-release ; uname -r CentOS release 6.4 (Final) 2.6.32-358.11.1.el6.centos.plus.x86_64 My hostname is server.one.two.com: # hostname server.one.two.com # hostname --fqdn one.two.com #grep HOSTNAME /etc/sysconfig/network

I have followed many tutorials including the ones provided by puppetlabs and I keep seeing the same issues. I began by installing puppet on machine: puppet001, and puppet master on machine: puppetMaster. The hosts files were then configured so that both machines were reachable by the machine name. The puppet.conf files were then updated, and a cert was generated and sent from puppet001 to

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

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 installed puppet from puppet-labs yum repository on OEL familiy of Red Hat Enterprise Linux Server release 5.9 (Tikanga) ---------------------------------------------------------------------------- [root@oel-puppet-master modules]# yum list facter Loaded plugins: rhnplugin, security This system is not registered with ULN. You can use up2date --register to register. ULN support will be

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

If I externalise my Puppet module config to a directory outside of Puppet using the modulepath / manifestdir settings: [main] pluginsync=true modulepath=/home/ec2-user/projects/qmg-puppet/etc/puppet/modules manifestdir=/home/ec2-user/projects/qmg-puppet/etc/puppet/ manifests the agents log the following error: "Could not evaluate: Could not retrieve information from source(s)

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

Hello! I''m just getting started working with Puppet and testing on a Windows 2003 server. When I run facter on this server it returns a wrong value for the ipaddress (should be 10.10.0.203, but facter sets ipaddress=10.0.0.203). As you can see from the following ipconfig output, facter is looking at the TELECOM Ethernet adapter instead of the adapter used for the local domain

Hello, First of all I am new to the Puppet technology. I am trying to get my puppet agent (windows) to reach my puppet master (Linux) server. In this tutorial: http://docs.puppetlabs.com/learning/agent_master_basic.html It claims to test your puppet agent you need to use the ''puppet agent --test'' command. My result when I tried this is: C:\Program Files (x86)\Puppet

About week ago, we moved our production puppet server to an older IBM OpenPower Server with 8 cores and 8GB ram. We use Ubuntu 8.04 LTS for the PowerPC (the most recent version for this hardware). We have puppet 0.24.8, Apache+ssl, Passenger 2.2.2 and Rack 1.0. We manage 780 identically configured compute nodes and gateways with a mix of ppc and x86 cpu''s running either CentOS 5.3, or

Does anyone know why i would get a module error for my ''base'' module that I''m not even including for a node? I''m explicitly NOT include the ''base'', yet puppet-client-t2 still errors when i pull it in. Snips from both are below. Any ideas why this would happen? Thanks, JJ ==== site.pp file [root@puppet-master-t1 puppet]# cat

I made two decisions this afternoon that are now related to each other. 1. Use more of the modules that exist in the Forge 2. Rebuild my monitoring server As I perused the various modules that help with managing monitoring packages my eyes fell upon a module that reported to be able to manage nagiosql, a setup that I had been planning on migrating my nagios monitoring to. So I installed

All, Trying to install puppet-2.6.3 on CentOS 5.4 and I get the following. [root@stsdev-pri ~]# gem install puppet-2.6.3 ERROR: http://rubygems.org/ does not appear to be a repository ERROR: Error installing puppet-2.6.3: puppet requires facter (>= 1.5.1, runtime) Facter is installed: [root@stsdev-pri ~]# facter -v 1.5.8 Ruby is installed: [root@stsdev-pri ~]# ruby --version ruby