similar to: How To: Puppet Setup on Redhat 8 using the puppet gem.

Hi, I am running puppet 2.6.12 on a SLES11SP1 server. I get the following error message as part of the puppet catalog run on a SLED11SP1 client. Augeas[sap_host_entries](provider=augeas): Opening augeas with root /, lens path , flags 0 err: /Stage[main]/Sap/Augeas[sap_host_entries]: Could not evaluate: unknown error - Failed to initialize Augeas Can somebody shed some light on the error

Hi, I have a couple of FreeBSD-servers that I try to manage using puppet. I''m just trying it out at the moment and have just deployed 5 new boxes (from PXE and scripted installation so supposedly they are all identical except for the name and ip-addresses). On two of the servers I get the error-messages at the bottom of the post. The first error- message I get every time I run puppet on

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

The following are the steps that I performed to install ruby on my linux machine. This same text is also available on http://linux-certification.blogspot.com/2008/10/setting-up-ruby-on-li... I went to http://www.ruby-lang.org/en/downloads/ There I found out a section with the heading Ruby Source Code I pick the url of the link for the file using the right click and choosing the ''copy link

I''m running puppet 0.24.6 on CentOS 5.2 from a puppetmaster on a virtual server to a variety of client servers both virtual and metal running either CentOS 5.2 or Fedora Core 10. I want to extend this to servers running RHEL 5 (and 6) in the near future. My problem is I have puppet set up with all repositories (mirrored locally using cobbler) included in one file in

Aloha All, I have downloaded many gems in .gem and .tar format from Rubyforge to my dir /usr/local/src/gems/. However, I got the following error below when executing "gem install mongrel-1.1.5.gem" or any other gems from the dir above. "ERROR: could not find gem mongrel-1.1.5.gem locally or in a repository" I''ve notice that within the .gem folder there are two

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Puppet 0.25.1 - code name "zoot" - is now available. The 0.25.1 release is a maintenance release in the 0.25.x branch. The release is available at: http://reductivelabs.com/downloads/puppet/puppet-0.25.1.tar.gz http://reductivelabs.com/downloads/gems/puppet-0.25.1.gem Please report issues and feedback via the Reductive Labs Redmine site:

Hello I have been using puppet for a while now, more or less successfully on SLES 11 and CentOS 5.5 currently I am using puppet 2.6.6 I now am trying it out on redhat 6, and now i run into an problem with even the simplest of modules/classes The error I get is : debug: /Stage[main]/Motd/File[/etc/motd]/content: Executing ''diff -u / etc/motd

RoR-ers, I''ve bumped into an issue with ruby and ssl. I''m trying to run a rake command which aborts because it cannot find openssl.rb. I followed these steps: - mkdir /rho; chown phor /rho - wget ftp://ftp.ruby-lang.org/pub/ruby/1.8/ruby-1.8.7-p72.tar.bz2 - tar jxf ruby-1.8.7-p72.tar.bz2 - cd ruby-1.8.7-p72 - vi ext/Setup and uncomment these lines: bigdecimal curses

Hello, Running latest Puppet 2.7rc4, Ruby 1.9.2 p180, slackware 13.37 64. Default (webrick) setup, no mongrel no apache. Running puppet master on the main puppet server works fine, no problem. Running puppet agent on the same machine works fine, no problem. Running puppet agent on a client server (separate machine) connecting to master gives the following error: "err: Could not request

I''m attempting to deploy puppet via an NFS share. It''s on a local-only network, and it will contain only ruby (gems) and whatever is needed. Seems simple enough, but tonight I am having an issue with this error: # service puppet start Starting puppet: /local/lib/ruby/site_ruby/1.8/rubygems/ custom_require.rb:36:in `gem_original_require'': no such file to load -- openssl

I am using Puppet 3.1.0 on a CentOS 6.3 machines. The puppet master and puppet agents use CentOS 6.3 as their OS. I have a puppet script (init.pp file for the puppet module) that contains the following exec type: exec { "postgres init": cwd => "/applications/module", command => "bash initializePostgres.sh", user => "postgres", group =>

I have a puppet master on Centos 6.3 connected and working properly with other Centos 6.3 agent. I installed puppet agent via gems on a RED HAT 4 node. This is what happens when I try to sign certificate for the new node: AGENT [root@FP2 ~]$ puppet agent -t Info: Creating a new SSL key for fp2 Info: Caching certificate for ca Info: Creating a new SSL certificate request for fp2 Info:

Hello I am hoping to deploy Puppet 0.25.0 within our Unix infrastructure. One of our systems runs on HP-UX B.11.11 (HP-UX 11iv1), I am having trouble getting ruby to run on this platform. The version of ruby that is available on the HP-UX Software Archive (http://hpux.connect.org.uk/) is 1.8.4, however puppet generates an error when it starts up. I have attempted to build 1.8.7 from

I''m working on deploying Puppet to our environment and after reinstalling some nodes, I run Puppet for the first time. It appears to be updating some Puppet specific files (see below), and then times out with the error: "Error: /File[/var/lib/puppet/lib/facter/ip6tables_version.rb]/ensure: change from absent to file failed: execution expired Error: Could not retrieve plugin:

Hi, I''m trying to install puppet as a client on a new machine. I received this weird error when trying to start up as /etc/init.d/ puppet start : /usr/lib/ruby/1.8/openssl/cipher.rb:22: Cipher is not a module (TypeError) from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb: 36:in `gem_original_require'' from

I have the following set up: schedule {nightly: period => daily, range => "18 - 23", repeat => 1 } define deadlypkg { tag("package") $pkgrepo="/staging/PRODUCTION/deadly" package{"$name": source => "$pkgrepo/$name.pkg", ensure => latest, adminfile

I''m working on a system for auto-resigning certificates for our clients and Iv''e basically got it working .. but I notice that Puppet uses an inventory file and a serial # file that seem to be differently formatted than the openssl toolkit uses? The serial number file that puppet generates has a 4 digit number starting with 0000... but openssl tracks its serial numbers in a hex

I am trying to figure out if I am missing something simple here. After upgrading to puppet 3.0 running puppet-rspec tests that use custom resources from modules in the fixtures directory are failing. I have a module that uses the anchor type and with 2.7.19 it works fine. After upgrading to 3.0 all of the tests are failing with Puppet::Error: Puppet::Parser::AST::Resource failed with

Hello everyone, Ruby 1.8.7 is EOS now. So, when will Puppet become Ruby 1.9.2+ compatible? I am considering to deploy Puppet on a large hosts of servers. If Ruby 1.9.2 cannot be supported, I have to turn to Chef. Best regards, Tetsu -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to