Yeah I think that error occurs when the agent node can't resolve the master's hostname. If you don't define a master I believe the default is just the hostname "puppet". It's probably trying to resolve that and failing.
Rich On Friday, July 4, 2014, John Kennedy <[email protected]> wrote: > First thing off the top of my head is that puppet.conf on the client does > not define which server is the master. > What happens if you try: > > puppet agent --test --server puppetmaster.puppet > > John > > > John Kennedy (_8(|) > I have a yellow dog: > http://www.theyellowdogproject.com/The_Yellow_Dog_Project/About.html > > Why would anyone foster a dog/cat? > I would rather cry watching them leave our home to live a life of > happiness and joy in a loving home than cry because no one stepped up to > help them and they died alone, frightened, and sad in a shelter. > > > On Fri, Jul 4, 2014 at 5:32 AM, Mark Matrosow <[email protected] > <javascript:_e(%7B%7D,'cvml','[email protected]');>> wrote: > >> Hey guys, >> Sorry for my bad english. I'm on a traineeship at the moment. My boss >> gave me the task to install Puppet on 2 virtual machines and install a >> package on the puppetclient over the puppetmaster (Im running Debian >> "wheezy" on both machines). >> I configurated both machines and also could sign the puppetclient on the >> puppetmaster. If I type: puppet agent --test in my clients terminal I get >> the following error: >> >> err: Could not retrieve catalog from remote server: getaddrinfo: No >> address associated with hostname >> warning: Not using cache on failed catalog >> err: Could not retrieve catalog; skipping run >> err: Could not send report: getaddrinfo: No address associated with >> hostname >> >> I documented the way of my configurations: >> (I did it on German thats why Konfiguration with "K" ;) ) >> Puppetmaster >> >> Hostname Konfiguration >> Puppetmaster → vi /etc/hostname → „puppetmaster“ >> >> Domain/Host Konfiguration >> → vi /etc/hosts >> >> 127.0.0.1 localhost >> #127.0.1.1 puppetmaster.puppet puppetmaster >> 192.168.56.101 puppetmaster.puppet puppetmaster >> 192.168.56.102 puppetclient1.puppet puppetclient1 >> >> Network Interface >> >> # The loopback network interface >> auto lo >> iface lo inet loopback >> >> # The primary network interface >> auto eth1 >> iface eth1 inet static >> address 192.168.56.101 >> netmask 255.255.255.0 >> network 192.168.56.0 >> broadcast 192.168.56.255 >> dns-nameservers 192.168.56.101 >> >> auto eth0 >> iface eth0 inet dhcp >> >> # I got 1 auto and 1 static, because i need to network adapters: NAT and >> Hots-only for my machines, otherwise the connection wouldnt work as it >> should. >> >> nodes.pp >> Puppetmaster → cd /etc/puppet/manifests → vi nodes.pp → >> >> node ’puppetmaster’ { >> include apache2 >> } >> >> site.pp >> /etc/puppet/manifests → vi site.pp >> >> package { >> 'apache2': >> ensure => installed >> } >> >> service { >> 'apache2': >> ensure => true, >> enable => true, >> require => Package['apache2'] >> } >> >> >> Puppet.conf >> cd /etc/puppet → vi puppet.conf → >> >> [master] >> # These are needed when the puppetmaster is run by passenger >> # and can safely be removed if webrick is used. >> ssl_client_header = SSL_CLIENT_S_DN >> ssl_client_verify_header = SSL_CLIENT_VERIFY >> puppetclient1 = 192.168.56.102 >> >> >> Puppetclient1 >> >> Hostname Konfiguration >> Puppetclient1 → vi /etc/hostname → „puppetclient1“ >> >> Domain/Host Konfiguration >> vi /etc/hosts >> >> 127.0.0.1 localhost >> #127.0.1.1 puppetclient1.puppet puppetclient1 >> 192.168.56.101 puppetmaster.puppet puppetmaster >> 192.168.56.102 puppetclient1.puppet puppetclient1 >> >> Network Interface >> >> # The loopback network interface >> auto lo >> iface lo inet loopback >> >> auto eth0 >> iface eth0 inet dhcp >> >> # The primary network interface >> auto eth1 >> iface eth1 inet static >> address 192.168.56.102 >> netmask 255.255.255.0 >> network 192.168.56.0 >> broadcast 192.168.56.255 >> dns-nameservers 192.168.56.101 >> >> >> Puppet.conf >> cd /etc/puppet → vi puppet.conf >> >> [master] >> # These are needed when the puppetmaster is run by passenger >> # and can safely be removed if webrick is used. >> ssl_client_header = SSL_CLIENT_S_DN >> ssl_client_verify_header = SSL_CLIENT_VERIFY >> certname=puppetmaster >> >> Would be very kind of you if you guys could help me (: >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Puppet Users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] >> <javascript:_e(%7B%7D,'cvml','puppet-users%[email protected]');> >> . >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/puppet-users/3db33b4a-1d59-4cd0-80a3-7a9b8572c833%40googlegroups.com >> <https://groups.google.com/d/msgid/puppet-users/3db33b4a-1d59-4cd0-80a3-7a9b8572c833%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] > <javascript:_e(%7B%7D,'cvml','puppet-users%[email protected]');> > . > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/CAD6OLfye489OjpWX4PeuQq33kvZgQ%3DPOaKOGSRJ%2BCQbj_Bz0UQ%40mail.gmail.com > <https://groups.google.com/d/msgid/puppet-users/CAD6OLfye489OjpWX4PeuQq33kvZgQ%3DPOaKOGSRJ%2BCQbj_Bz0UQ%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAPGcbtDHds2PW9-tV3H392GY0A%3D8q%3DJsHyrBDVW1eLi%2BrXAhUQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
