similar to: Issue: packages with same name, different providers.

Hi all, Doing some work with a puppet 2.7.14 installation to see what''s new and needs to be changed, however i''m seeing unexpected behavior with my manifests, so my external node directory isn''t being imported. This is on a rhel 5 server with the puppet rpms from yum.puppetlabs.com, but the cilent machines is based on fc17 beta with 2.7.13 rpm (which is with that

New install of 2.5.1 on Ubuntu 10.10 server. Multiple (6) new installs on Ubuntu 12.04 clients running agent 2.7.14-1puppetlabs1 from the puppetlabs repo generating the following error. err: Could not retrieve catalog from remote server: Error 400 on SERVER: No matching value for selector param ‘undef’ at /opt/puppet/share/puppet/modules/pe_mcollective/manifests/init.pp:89 on node

All- I''m using puppet 2.7.14. I''ve reviewed http://docs.puppetlabs.com/puppet/2.7/reference/modules_fundamentals.html but it doesn''t seem to cover what I''m attempting. Consider a module layout like this: $ tree mymodule mymodule |-- Modulefile |-- README |-- manifests | |-- init.pp | |-- special_type | | `-- prereqs.pp | `-- special_type.pp

Hi all, I''m in the procedure of migrating my old puppet server (puppet-2.6.14-1.el5) with mongrel to a new one (puppet-2.7.14-1.el6.noarch) with passenger. I''m facing a really strange behaviour with the catalog compilation time. I''ve 3 servers: 1.-) Centos 5.8 puppet-2.6.14-1.el5 + rubygem-mongrel-1.0.1-6.el5 Client: Compiled catalog for td055.pic.es in environment

Puppet version: 2.7.14 Puppet master behind apache with mod_proxy load balancer. I am able to authenticate with the cert as per these headers: Accept: s X-SSL-Subject: /CN=puppetagent1.example.com X-Client-DN: /CN=puppetagent1.example.com X-Client-Verify: SUCCESS Any idea what this error means ? I share my ssl dir on the load balancer and the puppet master. -- You received this message

Hello, I''m trying to use External Node classification and I have not idea what is my mistake. I getting the following error : err: Could not retrieve catalog from remote server: Error 400 on SERVER: undefined method `downcase'' for ["hola", {"mens"=>"HOLA"}]:Array on node casa I have a very simple parameter class : class hola( $mens =

Hi, Ubuntu Lucid has a very outdated puppet, 0.25.4 according to: http://docs.puppetlabs.com/guides/puppetlabs_package_repositories.html#for-debian-and-ubuntu I did this to "enable the repository": wget http://apt.puppetlabs.com/puppetlabs-release_1.0-3_all.deb sudo dpkg -i puppetlabs-release_1.0-3_all.deb but this still does not result in installing an up to date puppet apt-get

I am using puppet 2.7.14 on Ubuntu 10.04 LTS. I have the following gems: *** LOCAL GEMS *** diff-lcs (1.1.3) hiera (0.3.0) hiera-puppet (0.3.0) metaclass (0.0.1) mocha (0.12.1) puppet-lint (0.1.13) puppetlabs_spec_helper (0.2.0) rake (0.9.2.2) rspec (2.11.0) rspec-core (2.11.1) rspec-expectations (2.11.2) rspec-mocks (2.11.1) rspec-puppet (0.1.3) When I run "rake help" I get the

Hello, I''ve tried searching for this but I don''t seem to be able to find a way to search past archives in this list. Is there a way to get a per-process qos functionality in linux? At this very moment, I''m using with success a kind of ''workaround'' in my server, which involves creating multiple virtual ethernet interfaces with different IPs and binding

Hello everybody, I was thinking about a special script to be done with rsync, when I realized my needs might have been common enough to have already been fulfilled by somebody else through a script or by some backup software. I have a folder I share between two computers of mine, A and B. What i want is to be able to keep it in full sync. If a file is added in A, it should be added to B when

Dear all, I have this setup on Ubuntu 12.04 and using puppetmaster/puppet 2.7.14 and puppetdb/puppetdb-terminus 0.9.0 from puppetlabs. My puppetmaster also run puppetdb. I also use hiera in this setup. hadoop4 is puppetmaster and hadoop02 is puppet client. puppet node status hadoop4.west.net hadoop4.west.net Currently active Last catalog: 2012-06-05T23:23:33.159Z Last facts:

Hi folks, I noticed an interesting problem with the nagios_* providers especially in Debian. Besides writing to the wrong file (I fixed that issue) I''ve noticed there is a umask issue where the config files end up being owned by root with perms 0640. This causes nagios to spit milk out of its nose because it cannot read the configuration files. I came up with a kludgey solution to the

Hey Folks, Has anybody seen this when using puppet-module, installed via gem, in puppet 3.0.2 on CentOS 6.3? [puppet]# puppet-module install puppetlabs-firewall /usr/lib/ruby/site_ruby/1.8/puppet/settings.rb:254:in `convert'': Error converting value for param ''config'': Could not find value for $confdir (Puppet::Settings::InterpolationError) from

I have a single LB running Apache with mod_proxy in front of a Puppet master. These are the LB and Puppet master configs: <Proxy balancer://puppetmaster> BalancerMember http://192.168.1.10:8140 </Proxy> Listen 8140 <VirtualHost *:8140> SSLEngine on SSLCipherSuite SSLv2:-LOW:-EXPORT:RC4+RSA SSLProtocol -ALL +SSLv3 +TLSv1 SSLCipherSuite

I''ve installed the puppet labs lvm module. After fixing the missing "}" at line 20 in init.pp (really?!?!), I''m getting this:'' err: Could not retrieve catalog from remote server: Error 400 on SERVER: Puppet::Parser::AST::Resource failed with error ArgumentError: Invalid resource type physical_volume at /truth/sauce/env/prod/modules/role/manifests/common.pp:43

I am running puppet 2.7.14 - CentOS 6 server, CentOS and windows 2008 R2 clients. I''m having problems with the "puppet kick" command - it works on linux clients, and on my windows box when "puppet agent --no-daemonize --verbose" is run from a command prompt. However, when I run it as a windows service, I get "Host blah failed: Connection refused -

I noticed that a number of my Windows hosts had stopped dialing in, and upon closer inspection I found that Puppet was crashing in Ruby and wevtapi.dll. I can''t find any reference to this in the issue tracker, although I''ve got over a dozen occurrences in my environment, all with the same descriptions as below. I checked to see if the times were similar, in case the server

Hi, While i''ve read the wiki page on development of custom providers ( http://www.reductivelabs.com/trac/puppet/wiki/ProviderDevelopment), i cannot find information on where the custom provider''s source file should be located. My little provider works fine if i copy it to /usr/lib/ruby/site_ruby/1.8/puppet/provider/package but i''d prefer to keep that in tact from the

Hello, What would you think of moving database, database_grant and database_user types and providers from puppetlabs-mysql to its own module (puppetlabs-dbproviders for example) so that we can develop providers for others RDBMS ? I''d like to develop providers for postgresql, so I think it makes sense to put this types/providers in its own module. best regards, Mickaël Canévet --

I have a bunch of CentOS machines. In the process of puppetizing one of them I''m getting this warning (more complete debug info at the end): warning: Found multiple default providers for service: init, base; using init info: /Service[gmond]: Provider init does not support features enableable; not managing attribute enable Given that all of my instances are running the same OS and should