similar to: puppet & RHEL4

Hello, I''m seeing the following when I run puppetd --version /usr/sbin/puppetd:157:in `require'': no such file to load -- puppet (LoadError) from /usr/sbin/puppetd:157 I thought upgrading ruby to 1.8.5 would solve the issue but it has not. In any case, here are the relevant rpm versions... ruby-1.8.5-1.el4.centos ruby-rdoc-1.8.5-1.el4.centos

Is the module puppetdb from the forge still correct ? Every time I try to install puppetdb from the puppet module ("puppet module install puppetlabs/puppetdb"), i got a warning : *Warning: cprice404-inifile is deprecated; please update to puppetlabs-inifile* How may i install the puppetlabs-inifile instead of cprice404 ?? -- You received this message because you are subscribed to

For those of you out there using export/collect (which we really need to come up with a better name for...), can you test the current SVN code? I''m mostly wondering if the performance is any better. To use it, you''ll have to remove your current database, since the database schema is significantly changed. I''m getting what looks like an additional 25% reduction

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

Facter has the feature that it will turn any environment variable named FACTER_* into a fact. I can do this on the commandline no problem, but when I attempt this in puppet it seems to ignore that parts. Is anyone else seeing this? (Is this expected behavior?) I don''t see a ticket or a mail thread on it - though my searching powers have been weak the last couple of weeks... Thanks,

I have created my first ''fact'', first attempt at Ruby too, and configured the fileserver to server it but when a Fedora (5 or 6) client sync''s puppetd appears to hang. CentOS clients sync and use the new fact fine. Find attached the fact file and the output from ''puppetd --debug --factsync'' on a FC5 client is below. This is a 0.20.1 client and

What''s the correct yum repo to use for installing Puppet & Facter on RHEL5 and Centos5? I used to get them from the dlutter-rhel5 repo but this seems to be massively out of date now - latest version of puppet-server in there is 0.24.5-1.el5 and facter 1.5.4-1.el5. In Epel I see puppet-server 0.24.8-1.el5.1 and facter 1.5.4-1.el5 which is better but isn''t 1.5.4 the version

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

I want to use Puppet and Facter on a machine where I don''t have sudo or root access privileges. I won''t be using Puppet for anything that requires that level of access, so I should be OK if I can get it on the box. Any advice on how to proceed? Currently the Facter installer complains that it doesn''t have privileges for /usr/bin/facter. I assume Puppet will have the same

Having issues getting Puppet running under Passenger. From httpd error_log: [ pid=24647 thr=268010020 file=utils.rb:176 time=2011-10-04 11:45:10.892 ]: *** Exception LoadError in PhusionPassenger::Rack::ApplicationSpawner (no such file to load -- puppet/application/master) (process 24647, thread #<Thread: 0x0000001ff30448>): from

Just started a "pilot" puppet server for real after messing around in VMs for the past week or so... I used the 0.24.0 since it was available, and on the test run, got this: err: Could not prefetch package provider ''yum'': Execution of ''/usr/bin/python /usr/lib/ruby/site_ruby/1.8/puppet/provider/package/yumhelper.py'' returned 512: /usr/bin/python:

I thought I read somewhere in Puppet docs/wiki... that it is "recommended" to avoid spaces in file paths, or some similar verbiage, but now I cant find it. Does Puppet have any known issues with spaces in file paths? It would of course scare Windows admins away... So I hope I am wrong in thinking I read that. Thanks a lot, Mohamed. -- You received this message because you are

Hi all, I launched a Puppet service a few month ago and it did function pretty well for some time. Last week, I tried to clean old entries but I think I deleted too much information as I can no more synchronize my clients. I get a certificate error : *[root@REBITPUPPET01 ~]# puppet agent --test Warning: Unable to fetch my node definition, but the agent run will continue: Warning: SSL_connect

I''ve run into an odd one on one of my new RHEL 6 boxes. Puppet and Facter seem to disagree about the value of a fact. Puppet version: 2.7.9 Facter version: 1.6.4 Module: puppetlabs-apache apache::params falls through its if structure: if $::osfamily == ''redhat'' or $::operatingsystem == ''amazon'' { ... } elsif $::osfamily ==

Just curious... CentOS4 lifetime tracks RHEL4 somewhat... Since RedHat has announced LTS (Long Term Support) for RHEL4, are there plans to extend the CentOS 4 support window?

Hello dear list. First of all thanks to all the developers for the great work on puppet. After using it for a while, there is not better tool to manage a network! I have a problem with the $processor fact, which seems to be either not there or ignored at all. I try to implement package deployment for the Macs (Intel vs. PowerPC) as described here:

Hi, I wanted to know whats the ideal way to install puppet client ie the below packages on Red Hat Linux release 9 (Shrike) system -- 2.4.20-8smp I get the dependencies issue with the below(bcso they are for RHEL4 which is 2.6 kernel). What would be an ideal way, where can I get the tar source of the compatible version of puppet/facter/ruby for Redhat 9

I'm looking at this document to convert RHEL4 systems to Yum and setup an updates repository. http://sial.org/howto/yum/ Which version of yum would you recommend for that? What would be the dependencies that need to be installed? Any guidelines for installing Yum on RHEL4 without breaking the RPM dependencies and stuff (and with minimal changes to the system)? The document recommends

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,

Hey guys, Does anyone know how to change the location of puppet.conf? In my situation, I don''t want to store it under /etc/puppet/puppet.conf or ~/.puppet/puppet.conf -- I''d like to store it under /opt/puppet/puppet.conf in this example. Is there a method without having to symlink, perhaps with an environment variable like PUPPET_CONF=.... ? Thanks for your time, Jason --