hello list I am attempting to setup a puppet server in the amazon cloud. When I try to hit the host from the test client using puppetd --test I get this response... [root@mclient ~]# puppetd --test err: Could not retrieve catalog from remote server: getaddrinfo: Name or service not known warning: Not using cache on failed catalog err: Could not retrieve catalog; skipping run So I thought what if I try to do a test puppet run on the server itself? Surprisingly I get the same result... [root@mcollective ~]# puppetd --test err: Could not retrieve catalog from remote server: getaddrinfo: Name or service not known warning: Not using cache on failed catalog err: Could not retrieve catalog; skipping run I make sure that puppet is installed: [root@mcollective ~]# rpm -qa | grep puppet puppet-server-0.25.5-1.el5 puppet-0.25.5-1.el5 That the service is running: [root@mcollective ~]# service puppetmaster status puppetmasterd (pid 2025) is running... And listening on the correct port: [root@mcollective ~]# lsof -i :8140 COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME puppetmas 2025 puppet 7u IPv4 15187 TCP *:8140 (LISTEN) So why would this puppet server be unable to contact itself?? thanks in advance!! -- GPG me!! gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B -- 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 more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Tim Dunphy said:> hello list > > I am attempting to setup a puppet server in the amazon cloud. When I > try to hit the host from the test client using puppetd --test I get > this response... > > > > > [root@mclient ~]# puppetd --test > err: Could not retrieve catalog from remote server: getaddrinfo: Name > or service not known > warning: Not using cache on failed catalog > err: Could not retrieve catalog; skipping runHello, In my experience an error like this means that the hostname on your machine may not be set correctly, check outputs of `facter fqdn'' and `hostname -f''. -- Rohan McGovern Quality Engineer Qt Development Frameworks, Nokia -- 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 more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Hello and thanks for your reply!! It looks like the hostname is set correctly [root@mcollective ~]# hostname -f mcollective.acadaca.net [root@mcollective ~]# facter | grep fqdn fqdn => mcollective.acadaca.net And here is a more verbose run of puppetd --test [root@mcollective ~]# puppetd -t -d -v debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/dscl does not exist debug: Puppet::Type::User::ProviderPw: file pw does not exist debug: Failed to load library ''ldap'' for feature ''ldap'' debug: Puppet::Type::User::ProviderLdap: feature ldap is missing debug: Puppet::Type::User::ProviderUser_role_add: file rolemod does not exist debug: /File[/var/lib/puppet/ssl/public_keys]: Autorequiring File[/var/lib/puppet/ssl] debug: /File[/var/lib/puppet/ssl]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/state/graphs]: Autorequiring File[/var/lib/puppet/state] debug: /File[/var/lib/puppet/client_yaml]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/ssl/private_keys/mcollective.acadaca.net.pem]: Autorequiring File[/var/lib/puppet/ssl/private_keys] debug: /File[/var/lib/puppet/ssl/certificate_requests]: Autorequiring File[/var/lib/puppet/ssl] debug: /File[/var/lib/puppet/ssl/private]: Autorequiring File[/var/lib/puppet/ssl] debug: /File[/var/lib/puppet/lib]: Autorequiring File[/var/lib/puppet] debug: /File[/etc/puppet/puppet.conf]: Autorequiring File[/etc/puppet] debug: /File[/var/lib/puppet/facts]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/ssl/public_keys/mcollective.acadaca.net.pem]: Autorequiring File[/var/lib/puppet/ssl/public_keys] debug: /File[/var/lib/puppet/ssl/certs/mcollective.acadaca.net.pem]: Autorequiring File[/var/lib/puppet/ssl/certs] debug: /File[/var/lib/puppet/clientbucket]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/ssl/private_keys]: Autorequiring File[/var/lib/puppet/ssl] debug: /File[/var/lib/puppet/state]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/ssl/crl.pem]: Autorequiring File[/var/lib/puppet/ssl] debug: /File[/var/lib/puppet/ssl/certs/ca.pem]: Autorequiring File[/var/lib/puppet/ssl/certs] debug: /File[/var/lib/puppet/ssl/certs]: Autorequiring File[/var/lib/puppet/ssl] debug: Finishing transaction 23456293293600 with 0 changes debug: /File[/var/lib/puppet/ssl/private_keys/mcollective.acadaca.net.pem]: Autorequiring File[/var/lib/puppet/ssl/private_keys] debug: /File[/var/lib/puppet/ssl/certs/mcollective.acadaca.net.pem]: Autorequiring File[/var/lib/puppet/ssl/certs] debug: /File[/var/lib/puppet/ssl/public_keys]: Autorequiring File[/var/lib/puppet/ssl] debug: /File[/var/lib/puppet/ssl/certs]: Autorequiring File[/var/lib/puppet/ssl] debug: /File[/var/lib/puppet/ssl/private_keys]: Autorequiring File[/var/lib/puppet/ssl] debug: /File[/var/lib/puppet/state]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/ssl/private]: Autorequiring File[/var/lib/puppet/ssl] debug: /File[/var/lib/puppet/ssl/certificate_requests]: Autorequiring File[/var/lib/puppet/ssl] debug: /File[/var/lib/puppet/lib]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/facts]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/ssl/certs/ca.pem]: Autorequiring File[/var/lib/puppet/ssl/certs] debug: /File[/var/lib/puppet/ssl/crl.pem]: Autorequiring File[/var/lib/puppet/ssl] debug: /File[/var/lib/puppet/ssl/public_keys/mcollective.acadaca.net.pem]: Autorequiring File[/var/lib/puppet/ssl/public_keys] debug: /File[/var/lib/puppet/ssl]: Autorequiring File[/var/lib/puppet] debug: Finishing transaction 23456292743820 with 0 changes debug: Using cached certificate for ca debug: Using cached certificate for mcollective.acadaca.net debug: Finishing transaction 23456293690500 with 0 changes debug: Using cached certificate for ca debug: Using cached certificate for mcollective.acadaca.net debug: Using cached certificate_revocation_list for ca debug: catalog supports formats: b64_zlib_yaml marshal pson raw yaml; using pson err: Could not retrieve catalog from remote server: getaddrinfo: Name or service not known warning: Not using cache on failed catalog err: Could not retrieve catalog; skipping run Thanks again for your input! On Wed, Feb 9, 2011 at 6:38 PM, Rohan McGovern <rohan.mcgovern@nokia.com> wrote:> Tim Dunphy said: >> hello list >> >> I am attempting to setup a puppet server in the amazon cloud. When I >> try to hit the host from the test client using puppetd --test I get >> this response... >> >> >> >> >> [root@mclient ~]# puppetd --test >> err: Could not retrieve catalog from remote server: getaddrinfo: Name >> or service not known >> warning: Not using cache on failed catalog >> err: Could not retrieve catalog; skipping run > > Hello, > > In my experience an error like this means that the hostname on your > machine may not be set correctly, check outputs of `facter fqdn'' and > `hostname -f''. > -- > Rohan McGovern > Quality Engineer > Qt Development Frameworks, Nokia >-- GPG me!! gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B -- 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 more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Hi, I think your client can''t resolve puppet server hostname. Try to change ''server'' directive in config file or add ''puppet'' to /etc/hosts or use ''--server'' option in command line. Regards. On 10.02.2011 01:26, Tim Dunphy wrote:> hello list > > I am attempting to setup a puppet server in the amazon cloud. When I > try to hit the host from the test client using puppetd --test I get > this response... > > > > > [root@mclient ~]# puppetd --test > err: Could not retrieve catalog from remote server: getaddrinfo: Name > or service not known > warning: Not using cache on failed catalog > err: Could not retrieve catalog; skipping run > > > So I thought what if I try to do a test puppet run on the server > itself? Surprisingly I get the same result... > > [root@mcollective ~]# puppetd --test > err: Could not retrieve catalog from remote server: getaddrinfo: Name > or service not known > warning: Not using cache on failed catalog > err: Could not retrieve catalog; skipping run > > > I make sure that puppet is installed: > > [root@mcollective ~]# rpm -qa | grep puppet > puppet-server-0.25.5-1.el5 > puppet-0.25.5-1.el5 > > > > That the service is running: > > [root@mcollective ~]# service puppetmaster status > puppetmasterd (pid 2025) is running... > > > > And listening on the correct port: > > [root@mcollective ~]# lsof -i :8140 > COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME > puppetmas 2025 puppet 7u IPv4 15187 TCP *:8140 (LISTEN) > > > > So why would this puppet server be unable to contact itself?? > > thanks in advance!! > > > > > >-- 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 more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Hi Tim, what is your puppet.conf? Have you specified a puppet server to use? If not, by default it will look for a host named puppet which is why its complaining about not being able to resolve. Cheers, Atha On Wednesday, February 9, 2011 at 8:44 PM, Tim Dunphy wrote:> Hello and thanks for your reply!! > > It looks like the hostname is set correctly > > [root@mcollective ~]# hostname -f > mcollective.acadaca.net > > > [root@mcollective ~]# facter | grep fqdn > fqdn => mcollective.acadaca.net > > > And here is a more verbose run of puppetd --test > > > [root@mcollective ~]# puppetd -t -d -v > debug: Puppet::Type::User::ProviderDirectoryservice: file > /usr/bin/dscl does not exist > debug: Puppet::Type::User::ProviderPw: file pw does not exist > debug: Failed to load library ''ldap'' for feature ''ldap'' > debug: Puppet::Type::User::ProviderLdap: feature ldap is missing > debug: Puppet::Type::User::ProviderUser_role_add: file rolemod does not exist > debug: /File[/var/lib/puppet/ssl/public_keys]: Autorequiring > File[/var/lib/puppet/ssl] > debug: /File[/var/lib/puppet/ssl]: Autorequiring File[/var/lib/puppet] > debug: /File[/var/lib/puppet/state/graphs]: Autorequiring > File[/var/lib/puppet/state] > debug: /File[/var/lib/puppet/client_yaml]: Autorequiring File[/var/lib/puppet] > debug: /File[/var/lib/puppet/ssl/private_keys/mcollective.acadaca.net.pem]: > Autorequiring File[/var/lib/puppet/ssl/private_keys] > debug: /File[/var/lib/puppet/ssl/certificate_requests]: Autorequiring > File[/var/lib/puppet/ssl] > debug: /File[/var/lib/puppet/ssl/private]: Autorequiring > File[/var/lib/puppet/ssl] > debug: /File[/var/lib/puppet/lib]: Autorequiring File[/var/lib/puppet] > debug: /File[/etc/puppet/puppet.conf]: Autorequiring File[/etc/puppet] > debug: /File[/var/lib/puppet/facts]: Autorequiring File[/var/lib/puppet] > debug: /File[/var/lib/puppet/ssl/public_keys/mcollective.acadaca.net.pem]: > Autorequiring File[/var/lib/puppet/ssl/public_keys] > debug: /File[/var/lib/puppet/ssl/certs/mcollective.acadaca.net.pem]: > Autorequiring File[/var/lib/puppet/ssl/certs] > debug: /File[/var/lib/puppet/clientbucket]: Autorequiring File[/var/lib/puppet] > debug: /File[/var/lib/puppet/ssl/private_keys]: Autorequiring > File[/var/lib/puppet/ssl] > debug: /File[/var/lib/puppet/state]: Autorequiring File[/var/lib/puppet] > debug: /File[/var/lib/puppet/ssl/crl.pem]: Autorequiring > File[/var/lib/puppet/ssl] > debug: /File[/var/lib/puppet/ssl/certs/ca.pem]: Autorequiring > File[/var/lib/puppet/ssl/certs] > debug: /File[/var/lib/puppet/ssl/certs]: Autorequiring File[/var/lib/puppet/ssl] > debug: Finishing transaction 23456293293600 with 0 changes > debug: /File[/var/lib/puppet/ssl/private_keys/mcollective.acadaca.net.pem]: > Autorequiring File[/var/lib/puppet/ssl/private_keys] > debug: /File[/var/lib/puppet/ssl/certs/mcollective.acadaca.net.pem]: > Autorequiring File[/var/lib/puppet/ssl/certs] > debug: /File[/var/lib/puppet/ssl/public_keys]: Autorequiring > File[/var/lib/puppet/ssl] > debug: /File[/var/lib/puppet/ssl/certs]: Autorequiring File[/var/lib/puppet/ssl] > debug: /File[/var/lib/puppet/ssl/private_keys]: Autorequiring > File[/var/lib/puppet/ssl] > debug: /File[/var/lib/puppet/state]: Autorequiring File[/var/lib/puppet] > debug: /File[/var/lib/puppet/ssl/private]: Autorequiring > File[/var/lib/puppet/ssl] > debug: /File[/var/lib/puppet/ssl/certificate_requests]: Autorequiring > File[/var/lib/puppet/ssl] > debug: /File[/var/lib/puppet/lib]: Autorequiring File[/var/lib/puppet] > debug: /File[/var/lib/puppet/facts]: Autorequiring File[/var/lib/puppet] > debug: /File[/var/lib/puppet/ssl/certs/ca.pem]: Autorequiring > File[/var/lib/puppet/ssl/certs] > debug: /File[/var/lib/puppet/ssl/crl.pem]: Autorequiring > File[/var/lib/puppet/ssl] > debug: /File[/var/lib/puppet/ssl/public_keys/mcollective.acadaca.net.pem]: > Autorequiring File[/var/lib/puppet/ssl/public_keys] > debug: /File[/var/lib/puppet/ssl]: Autorequiring File[/var/lib/puppet] > debug: Finishing transaction 23456292743820 with 0 changes > debug: Using cached certificate for ca > debug: Using cached certificate for mcollective.acadaca.net > debug: Finishing transaction 23456293690500 with 0 changes > debug: Using cached certificate for ca > debug: Using cached certificate for mcollective.acadaca.net > debug: Using cached certificate_revocation_list for ca > debug: catalog supports formats: b64_zlib_yaml marshal pson raw yaml; using pson > err: Could not retrieve catalog from remote server: getaddrinfo: Name > or service not known > warning: Not using cache on failed catalog > err: Could not retrieve catalog; skipping run > > > Thanks again for your input! > > > > On Wed, Feb 9, 2011 at 6:38 PM, Rohan McGovern <rohan.mcgovern@nokia.com> wrote: > > Tim Dunphy said: > > > hello list > > > > > > I am attempting to setup a puppet server in the amazon cloud. When I > > > try to hit the host from the test client using puppetd --test I get > > > this response... > > > > > > > > > > > > > > > [root@mclient ~]# puppetd --test > > > err: Could not retrieve catalog from remote server: getaddrinfo: Name > > > or service not known > > > warning: Not using cache on failed catalog > > > err: Could not retrieve catalog; skipping run > > > > Hello, > > > > In my experience an error like this means that the hostname on your > > machine may not be set correctly, check outputs of `facter fqdn'' and > > `hostname -f''. > > -- > > Rohan McGovern > > Quality Engineer > > Qt Development Frameworks, Nokia > > > > -- > GPG me!! > > gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B > > -- > 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 more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. >-- 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 more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Hi Guys,
Changing the server directive in the puppet conf worked!!! Thanks so
much for your help!!
Also I sent an email yesterday regarding file sharing to the list.
Sorry to be a bother, but I am still struggling with this issue.
Does anyone have any advice regarding this?
Here is the email I sent for easy reference:
-----------------------------
Hi Atha,
This is what the basefiles class that I have created looks like now:
class basefiles {
file { "/etc/ldap.conf":
source => "puppet:///snjh/ldap.conf"
}
file { "/etc/haha.txt":
source => "puppet:///snjh/haha.txt"
}
}
I have allowed everything (for the time being) in filersver.conf :
# Define a section ''files''
# Adapt the allow/deny settings to your needs. Order
# for allow/deny does not matter, allow always takes precedence
# over deny
[snjh]
path /etc/puppet/manifests/files/snjh
allow *
# deny *.evil.example.com
# allow 192.168.0.0/24
And this is the error I am currently getting:
[root@VIRTCENT03:~] #puppetd --test
info: Caching catalog for virtcent03.summitnjhome.com
info: Applying configuration version ''1297290431''
err: //basefiles/File[/etc/haha.txt]: Failed to retrieve current state
of resource: Could not retrieve information from source(s)
puppet://puppet/snjh/haha.txt at
/etc/puppet/manifests/classes/basefiles.pp:10
err: //basefiles/File[/etc/ldap.conf]: Failed to retrieve current
state of resource: Could not retrieve information from source(s)
puppet://puppet/snjh/ldap.conf at
/etc/puppet/manifests/classes/basefiles.pp:6
notice: Finished catalog run in 1.03 seconds
thanks for your help!
-------------------
thanks again!! I really have gotten amazingly valuable help from this
list and I genuinely appreciate your time!
Tim
On Wed, Feb 9, 2011 at 6:46 PM, Sergey Zhuga <sergey.zhuga@gmail.com>
wrote:> Hi,
>
> I think your client can''t resolve puppet server hostname. Try to
change
> ''server'' directive in config file or add
''puppet'' to /etc/hosts or use
> ''--server'' option in command line.
>
> Regards.
>
> On 10.02.2011 01:26, Tim Dunphy wrote:
>>
>> hello list
>>
>> I am attempting to setup a puppet server in the amazon cloud. When I
>> try to hit the host from the test client using puppetd --test I get
>> this response...
>>
>>
>>
>>
>> [root@mclient ~]# puppetd --test
>> err: Could not retrieve catalog from remote server: getaddrinfo: Name
>> or service not known
>> warning: Not using cache on failed catalog
>> err: Could not retrieve catalog; skipping run
>>
>>
>> So I thought what if I try to do a test puppet run on the server
>> itself? Surprisingly I get the same result...
>>
>> [root@mcollective ~]# puppetd --test
>> err: Could not retrieve catalog from remote server: getaddrinfo: Name
>> or service not known
>> warning: Not using cache on failed catalog
>> err: Could not retrieve catalog; skipping run
>>
>>
>> I make sure that puppet is installed:
>>
>> [root@mcollective ~]# rpm -qa | grep puppet
>> puppet-server-0.25.5-1.el5
>> puppet-0.25.5-1.el5
>>
>>
>>
>> That the service is running:
>>
>> [root@mcollective ~]# service puppetmaster status
>> puppetmasterd (pid 2025) is running...
>>
>>
>>
>> And listening on the correct port:
>>
>> [root@mcollective ~]# lsof -i :8140
>> COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME
>> puppetmas 2025 puppet 7u IPv4 15187 TCP *:8140 (LISTEN)
>>
>>
>>
>> So why would this puppet server be unable to contact itself??
>>
>> thanks in advance!!
>>
>>
>>
>>
>>
>>
>
> --
> 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 more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>
>
--
GPG me!!
gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B
--
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 more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
On Feb 10, 2011, at 7:13 AM, Tim Dunphy wrote:> Hi Guys, > > Changing the server directive in the puppet conf worked!!! Thanks so > much for your help!! > > Also I sent an email yesterday regarding file sharing to the list. > Sorry to be a bother, but I am still struggling with this issue. > > Does anyone have any advice regarding this? > > Here is the email I sent for easy reference: > > > ----------------------------- > > Hi Atha, > > This is what the basefiles class that I have created looks like now: > > class basefiles { > > file { "/etc/ldap.conf": > source => "puppet:///snjh/ldap.conf" > > } > > file { "/etc/haha.txt": > source => "puppet:///snjh/haha.txt" > } > } > > > > > I have allowed everything (for the time being) in filersver.conf : > > # Define a section ''files'' > # Adapt the allow/deny settings to your needs. Order > # for allow/deny does not matter, allow always takes precedence > # over deny > [snjh] > path /etc/puppet/manifests/files/snjh > allow * > # deny *.evil.example.com > # allow 192.168.0.0/24This is really not the recommended way. My advice is to put that config back the way it was, and then do it as a module instead. So, put you file at /etc/puppet/modules/somename/files/ldap.conf Then use this as your URL: puppet:///modules/somename/ldap.conf This should just work. -- 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 more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.