similar to: Trying to run puppet from a tarball

I am banging my head against the wall for recently built hosts that are unable to verify the server''s certs. The usual is not working. on the puppet agent machine: find /var/lib/puppet/ssl -type f -delete on puppet master: puppetca --clean <new_host_cert> on agent: puppetd --server puppet --waitforcert 2 --no-daemonize -d -o on puppet master: puppetca --sign

I keep getting the following error when I do a catalog run: err: Could not request certificate: SSL_connect SYSCALL returned=5 errno=0 state=SSLv2/v3 read server hello A No idea why its giving me this error. Any help would be appreciated. Thanks! -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to

Hi all I started researching on puppet and decided I''ll try it out on Vmware Workstation using Ubuntu 10.04. So I''m trying to do the simplest puppet install pattern as outlined in http://projects.puppetlabs.com/projects/puppet/wiki/Simplest_Puppet_Install_Pattern. For now, I''m trying to test puppetd and puppetmasterd on the same machine. I start puppetmaster and

Hi Luke and other people working on 0.24. I hope this is constructive. So, I have our configuration working against a checkout from git as of last night. Subject to (sorry, here''s the big but :) * external_nodes script is not being called (#951) * Custom types aren''t working unless I drop them into $rubysitedir/puppet/{type,provider}. Previously they worked in

Good day, After having lurked for a while I''ve decided to actually start using puppet starting on my small home network. I''ve been following : http://reductivelabs.com/trac/puppet/wiki/InstallationGuide and :- http://www.howtoforge.com/installing_puppet_on_ubuntu to test puppet on 2 hosts, librarian running the puppetmasterd and mortvm. Unfortunately, I

Hi. Is there any way to make puppet run a particular module first before another module is run. For example, I''m using the augeas resource type in one of the modules. But libaugeas-ruby1.8 is not installed in the client machine. So when the catalog is run, I get the following error: Could not find a default provider for augeas. So I built another module that will install the

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

Hi guys, Apologies if this is covered elsewhere. I''ve had a hunt through Google, Redline, and the FAQs but dont see it. Puppet 0.24.8 (and 24.7 on teh same box) starts up fine, but then just sits there, regardless of what I set runinterval to be. Puppet Server debug output stops at: debug: Creating default schedules debug:

Got the following: err: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not autoload package: Could not autoload /usr/local/lib/site_ruby/1.8/puppet/provider/package/windows.rb: no such file to load -- windows/error at /etc/puppet/modules/php/manifests/init.pp:28 on node This after I reverted back to puppet v2.7.11 on my master. Not running windows anywhere... why am I

One more error/warning from the latest Puppet from git: In the provider I have KEYS = Facter.value(:roothome) + "/.ssh/authorized_keys" Puppet::Type.type(:authorizedkey).provide(:parsed, ... I get an error on the Puppetmaster: Could not autoload "/usr/lib/ruby/site_ruby/1.8/puppet/provider/authorizedkey/parsed.rb": undefined method `+'' for nil:NilClass Could not

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

Hiera was properly working in my environment. But puppet was looking at old version even when I have the latest hiera gem installed. So I could''nt use json backend. But puppet is not looking at my latest hiera gem. Not sure when went wrong here. Scenario: I have installed hiera couple of months back. So the gem was installed under /opt/puppet/lib/gems/1.8/gems/hiera-0.3.0

I am working on building a facter tag based node classifier similar to https://github.com/jordansissel/puppet-examples/tree/master/nodeless-puppet/. However, I have run into an issue where I cannot use puppet''s require file ability to push the yaml file containing the facts file to the client because it would require two runs of puppet to pickup changes. Consequently, I have written into

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,

Hello all, I don''t know if I have hit a strange bug or it''s just an incorrect interpretation about how parameter autoloading works... Today I have been searching, analysing and about to hit my head against a wall trying to figure out why a call to hiera_hash was not merging data from top level among different hierarchies. The problem was that I was trying to do something

Why doesn''t puppet autoload modules with capitals in the class names? Jul 5 09:55:54 s_sys@test01.sjc.xxx.com puppetd[6527]: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not find class repo::centOSBase in namespaces repo::common at /etc/puppet/modules/repo/manifests/common.pp:8 on node test01.sjc.xxx.com Change ''centOSBase'' to

Hi All, I get a error message stating that Could not send report: Error 400 on server: Could not autoload foreman: Function foreman already defined. I am integrating puppet report to be displayed with foreman. What can be the problem ??? Regards Niraj K. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this

Hello, Running into a problem when wanting to daemon-ize the agent. It doesnt seems to do anything: - cannot find any daemon process with (ps aux | grep puppet) - the config is not updated after editing some params on the master - /var/log/puppet stay empty... while, when logged as root, it is working without issue with $puppet agent --test. ##Conf Ubuntu 12.04 Puppet 2.7.11 ## Daemon is

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

Hi, Has anyone had success getting the Inventory Service running in RHEL 6? My Puppet Nodes are getting the following error: > [root@puppetnode-01 ~]# puppetd --debug --verbose --no-daemonize > ... > err: Could not retrieve catalog from remote server: Error 400 on SERVER: > Could not autoload inventory_active_record: uninitialized constant > ActiveRecord > ...