similar to: Make puppet clients look at a domain name rather than an IP?

i thought i would run up a fedora 8 installation and take a look around, my default kickstart installation includes puppet which shouldn''t be a problem however the puppet client fails with Certificates were not trusted: hostname was not match with the server certificate The cause is obvious, the hostname of my puppetmaster is ''puppet1.mydomain.com'' and

Is it possible, using puppet, to configure an EC2 instance so that when it boots it attaches & mounts an EBS volume? If so, what steps would one take to achieve this? -- 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

I''m unable to get a response from the puppetmaster I''m testing with. `netstat -apn` shows puppetmaster/ruby listening on port 8140, but telnet connections are refused both from a different location and from the commandline on the master server. I''ve restarted a number of times but I''m still getting nothing, and AFAICT there aren''t any conflicting

Hi I am reading and configuring puppet in relation to http://reductivelabs.com/trac/puppet/wiki/UsingMongrelOnEnterpriseLinux The question I have is in relation to the ssl certificates generated the first time the puppetmaster service is run and the ability to use a CNAME. If the host that i am running the puppetmaster on is server.example.com and i want to use puppet.example.com as a CNAME that

Hello everyone, I''m a new user regarding puppet but I''m skilled with linux. I have setup a puppetmaster server and also have a puppet client for testing on a different box. /etc/sysconfig/puppet has been edited to reach puppetmaster with option PUPPET_SERVER=puppet.mydomain.cr (I''m in Costa Rica) On the puppetmaster I was able to see the client with puppetca

Hello there, Since the update with ruby all my puppet function is dead (well known issue with the cert) . There has been some discutions on the dev list on how to patch this for future versions. I have read the list and wondered how we can solve the issue while waiting for the .24. I am in beta test of the .23.x version but on my production system i wanted to find a way to solve this now

I am trying to setup Puppet + Mongrel on RHEL5. So far I have followed this document: http://projects.puppetlabs.com/projects/puppet/wiki/Using_Mongrel_On_Enterprise_Linux The puppetmasters all start up and Apache starts up on 8140. However, when my client connects I get the following errors: [root@lv1764p puppet]# puppetd --server puppetdev.encana.com --no- daemonize -o -v info: Retrieving

I''m having difficulty getting my head around some CA issues My client has: [puppetd] ca_server=puppetca.mydomain.com and puppet resolves to a different machine. when puppet connects, it requests a signature from puppetca.mydomain.combut then on the next pass fails with the following: err: Could not retrieve catalog: Certificates were not trusted: SSL_connect returned=1 errno=0

I am finding that the puppetlabs-apache module is somehow adding 30-60 seconds onto a host''s catalog compile time when the puppetmaster has no other hosts contacting or generating catalogs. The Puppetmaster is setup to use Puppet-2.7.18 - Apache & Passenger. RIght now only 2 hosts are even configured to use this new PM, the PM itself and a Foreman host. With neither hosts

Hello! The FAQ contains an entry about autosigning: http://reductivelabs.com/trac/puppet/wiki/FrequentlyAskedQuestions#why-shouldn-t-i-use-autosign-for-all-my-clients It says: > The certificate itself is stored, so two nodes could not connect with the same CN I tried this (using 0.25.4), and actually, that doesn''t seem to be correct. I was able to run puppetd on two different

I''ve tried this over and over, and I just cannot get it to work. I''m trying to do a proof of concept on puppet, so I''m using two CentOS 5.3 systems running in VMs on separate hardware (i.e. the two VMs are not on the same physical box). I''ve built the systems from scratch numerous times, and then pulled down puppet from the rpmforge repo. In the course of

Hi, On my puppet node, there are many facter variables that are empty in my manifests. But, there are not empty when I start "facter" on the node. why ? ex in a module: class resolver { if $::ipaddress6 { ... } $domainename = "$domain" } In this manifest, $domain and $ipaddress6 are empty In the facter command line, there not empty. -- You received this

I''m running a two headed puppetmaster and have disabled crl''s. Let''s call them the primary and the secondary. The primary and secondary both use the primary as their master. The secondary only is used when the primary isn''t responding (I wrap the puppetd call in cron with a short shell script) I''m managing these ca files on the masters, pushing

Hi, I have a number of puppets talking to 1 puppetmaster. Everything was working fine until suddenly this week the puppets are revolting. Whenever I try to run ''puppetd -v'' I see a lot of messages like: Certificates were not trusted: hostname was not match I''m sure I did not make any changes to DNS lately and I didn''t upgrade puppet on any of the machines

I''m trying to setup a puppetmaster, and I''ve got a couple of questions. The first, is a design question. Since I expect to eventually have multiple puppetmaster servers, I''d like to name this one to be named puppet1.example.com. But I''d like my clients to connect via a cname as puppet.example.com. Is this pretty standard? Is there some more common way?

After upgrading my puppet master to 2.6.8 from 2.6.2, I intermittently get things like: puppet-master[29789]: (Scope(Class[Auth::Kerberos_ldap])) Could not look up qualified variable ''common::datacenter::ldap::ldapservers''; class common::datacenter::ldap has not been evaluated puppet-master[29789]: Failed to parse template auth/rhel5/ ldap.conf.erb: undefined method

How can I pre-sign a server which doesn''t yet have a domain pointing to it? I''m trying to get an EC2 "base image" together which is pre-signed with our master, so I can spin-up as many instances as required. These instances which will all share the same characteristics and files (they''re basically dupes), and will all sit behind a load-balancer, so

Morning chaps, From my understanding the puppet master must have a hostname of "puppet". Is this correct? I''d like to be able to call this box whatever I like. I think that I can do that within /etc/puppet/puppet.conf. -- John Maclean MSc (DIC) Enterprise Linux Systems Engineer -- You received this message because you are subscribed to the Google Groups "Puppet

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I am rather new to puppet and set up a puppet server and some clients. during "puppetd --server=puppetmaster.example.com --verbose" I get the following error which says nothing to me: err: Could not retrieve configuration: Uncaught exception compile error (erb):241: syntax error, unexpected tIDENTIFIER, expecting $end

Hi, I''m having a problem with extlookup not respecting the ''certname'' parameter[1].  When executing a puppet run with either the --certname or --fqdn parameters, it ends up using the specified SSL certificate and gets the correct node definition applied from the puppetmaster.  However, it still retrieves extlookup data using the node''s actual FQDN, not the one