similar to: Puppet Starting error

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

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

There''s a problem installing puppet on Solaris 10 -- in this situation, we aren''t really doing anything with puppet there. The version we''re using is: ruby 1.8.7 (2011-02-18 patchlevel 334) [i386-solaris2.9] Here''s the first error: # gem update puppet > > Updating installed gems > > Updating puppet > > Building native extensions. This

Greetings, I''m trying to set up a minimal CentOS 4 kickstart that installs puppet during the %post and then use puppet to build up the rest of the configuration. I''ve gotten things so that puppet 0.20.1-2 will install using yum during the %post in the kickstart, but now I''m seeing this error when it tries to run during %post and after I reboot the newly installed

Just wondering if anyone has built (or found) Puppet rpm packages for RHEL4 x86_64 version. James ********************************************************************************* Important Note This email (including any attachments) contains information which is confidential and may be subject to legal privilege. If you are not the intended recipient you must not use, distribute or copy this

How are people upgrading puppet itself on their hosts that run puppetd? Can puppet be used to upgrade to a new puppet package via gem, rpm or some other package provider? How do you handle restarting? Just hoping theres a better way than "ssh and a for loop" or having to have another configuration management system installed.

Hey all, I have recorded my steps towards getting puppet functional through one of the four different methods that I can think of, which are: 1.Source(copying and insatlling to the recommended unix FSH directory, /usr/local/src) 2.pkg hosted at explanatorygap 3.MacPorts 4.RubyGems I haven''t cleanly tested the last two, but here''s where I am with the first two: 1. I

Hello all, I have puppet rpm on internal repository for updating it to servers that don''t have it on their normal repos (Centos, Fedora Core 4 or older...) Then I have this to ensure that puppet is at latest version: package { "puppet": ensure => latest, provider => yum, } I added puppet 0.22.3 to my internal repository and all servers updated to that version,

I am trying to setup puppet for use with ldap. Following the page (http://www.reductivelabs.com/trac/puppet/wiki/LdapNodes ) I run ruby -rldap -e ''puts :installed'' with success, however ruby - rpuppet -e ''p Puppet.features.ldap?'' fails with ruby: no such file to load -- puppet (LoadError) I imagine that it is related to how I have things installed. I am

I just upgraded from 0.23.2-1 on RHEL 4&5 to 0.24.1-1. I used Dlutter''s repository. What a mess I''m in now. Anyway to make a long story short I moved all of the old configs out of the way (/etc/puppet, /var/lib/puppet) and started over with a fresh install. I can''t get puppetd on the server to request a cert. If I do a "puppetd -v --waitforcert 90" the

Hi, I have Redhat 9 & RHEL 4.2 with puppet clients installed. When is use puppetd -test the updates get effected, but when when running them as daemon mode nothing happens. ## Nothing Happens - no change is detected /etc/init.d/puppet status puppetd (pid 15538) is running... ## When running manually puppetd -test the changes from server gets updated. Is there any

What is puppet doing here? Nov 17 00:02:01 gumby yum: Installed: tf-starterkit-tfel0-1.0-1.tf.noarch Nov 17 00:02:01 gumby puppetd[720]: (//Node[gumby.fr.xxx.com]/Starterkit::Setup[tfel0]/Package[tf-starterkit-tfel0]/ensure) created Nov 17 00:02:07 gumby yum: Installed: tf-jboss-server-4.2.3.GA-1.tf.noarch Nov 17 00:02:07 gumby puppetd[720]:

I''m just starting a roll out of Puppet and I''m seeing a problem on maybe 25% of client nodes. The symptoms are that the clients stop updating. In the Puppetmaster log, I''m seeing things like: Feb 9 20:10:23 vs4 puppetmasterd[17942]: Compiled catalog for xxxx in 0.05 seconds Feb 9 20:40:41 vs4 puppetmasterd[17942]: Compiled catalog for xxxx in 0.05 seconds Feb 9

Hi, I can''t find an option of the puppetd client that can just print what the puppetd client will do on my system (updateing files, installing softwares, etc), but without doing all the things (like a "diff" between the current state of my system and the state defined on the puppet server). Is such option exists ? Regards

Hi, I exposed few days ago this situation on the IRC, but unfortunately I haven''t found a way to solve it yet. I run the Puppet Master with multiple environments, and everything is working good but a couple of nodes that are causing me some troubles. These nodes are pointing to my production environment and I need to point them back to development to grab some changes I made. I

> I''ve built a puppet solaris - package which is distributed via jumpstart > at installation time of a solaris 10 machine. > It''s postinstallation registers the puppetd into smf and starts puppetd > afterwards. Puppetd connects to puppetmasterd, gets ist certificate signed > (autosig on) and the configuration stuff. > Now the interesting part: a new solaris zone

Hi I am looking for quite a while now to run Puppet inside a vserver. The installation worked perfectly, but when I run a test I get this message: smb-configmaster / # puppetd --server 192.168.0.144 --waitforcert 60 --test /usr/lib/ruby/site_ruby/1.8/puppet/network/client/ca.rb:31:in `request_cert'': Certificate retrieval failed: Could not connect to 192.168.0.144 on port 8140

Hi all, I am using Puppet to execute an Expect script (http://expect.sourceforge.net) on a client. The Puppet recipe, test.pp, is: exec { ''/root/test.exp'': command => ''/root/test.exp'', logoutput => true } The recipe runs correctly when run using ''puppet --debug --verbose test.pp'': debug: /Stage[main]//Exec[/root/test.exp]:

Can anyone help me with this error I am having. I am using puppet on Debian Etch, version 0.20.1-1 from apt works OK, but due to one or two problems we want to use the version from testing, 0.23.2-10, but the puppetd just fails upon startup spitting this out: Starting puppet configuration management tool/usr/lib/ruby/1.8/timeout.rb:54:in `open'': execution expired (Timeout::Error)

Greetings, I''ve two questions for y''all. 1) I''ve setup an alternate installation path for puppet in a site local directory outside of ''the usual places''. Puppetd seems to insist that /etc/puppet/namespaceauth.conf exists despite setting :authconfig in both puppet and puppetd. As a result part of my installation now includes a symlink to point