Hi. When running "puppetd --server <puppetmaster> --waitforcert 50 --test" on a puppet client we get the following error: /usr/lib/ruby/1.8/net/http.rb:560:in `initialize'': getaddrinfo: Name or service not known (SocketError) from /usr/lib/ruby/1.8/net/http.rb:560:in `open'' from /usr/lib/ruby/1.8/net/http.rb:560:in `connect'' from /usr/lib/ruby/1.8/timeout.rb:56:in `timeout'' from /usr/lib/ruby/1.8/timeout.rb:76:in `timeout'' from /usr/lib/ruby/1.8/net/http.rb:560:in `connect'' from /usr/lib/ruby/1.8/net/http.rb:553:in `do_start'' from /usr/lib/ruby/1.8/net/http.rb:548:in `start'' from /usr/lib/ruby/site_ruby/1.8/puppet/network/xmlrpc/client.rb:128:in `start'' from /usr/lib/ruby/site_ruby/1.8/puppet/network/client.rb:99:in `initialize'' from /usr/lib/ruby/site_ruby/1.8/puppet/network/client/master.rb:203:in `initialize'' from /usr/sbin/puppetd:312:in `new'' from /usr/sbin/puppetd:312 Our system specs are these: uname -a: Linux a01apfl004.adeo.no 2.6.18-53.el5 #1 SMP Wed Oct 10 16:34:19 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux cat /etc/redhat-release: Red Hat Enterprise Linux Server release 5.1 (Tikanga) puppetd --version: 0.24.1 Does anyone know what may be causing this? We have checked /etc/hosts and it seems to be correct. Regards, Kenneth Holter _______________________________________________ Puppet-users mailing list Puppet-users@madstop.com https://mail.madstop.com/mailman/listinfo/puppet-users
I had a similar problem when I was starting out with Puppet. Check to make sure iptables isn''t getting in the way. /etc/init.d/iptables stop And see if you still get the same error. -Andrew Otto On Feb 12, 2008, at 3:09 PM, Holter, Kenneth wrote:> Hi. > > > When running "puppetd --server <puppetmaster> --waitforcert 50 -- > test" on a puppet client we get the following error: > > /usr/lib/ruby/1.8/net/http.rb:560:in `initialize'': getaddrinfo: Name > or service not known (SocketError) > from /usr/lib/ruby/1.8/net/http.rb:560:in `open'' > from /usr/lib/ruby/1.8/net/http.rb:560:in `connect'' > from /usr/lib/ruby/1.8/timeout.rb:56:in `timeout'' > from /usr/lib/ruby/1.8/timeout.rb:76:in `timeout'' > from /usr/lib/ruby/1.8/net/http.rb:560:in `connect'' > from /usr/lib/ruby/1.8/net/http.rb:553:in `do_start'' > from /usr/lib/ruby/1.8/net/http.rb:548:in `start'' > from /usr/lib/ruby/site_ruby/1.8/puppet/network/xmlrpc/ > client.rb:128:in `start'' > from /usr/lib/ruby/site_ruby/1.8/puppet/network/client.rb: > 99:in `initialize'' > from /usr/lib/ruby/site_ruby/1.8/puppet/network/client/ > master.rb:203:in `initialize'' > from /usr/sbin/puppetd:312:in `new'' > from /usr/sbin/puppetd:312 > > > Our system specs are these: > > uname -a: > > Linux a01apfl004.adeo.no 2.6.18-53.el5 #1 SMP Wed Oct 10 16:34:19 > EDT 2007 x86_64 x86_64 x86_64 GNU/Linux > > cat /etc/redhat-release: > > Red Hat Enterprise Linux Server release 5.1 (Tikanga) > > puppetd --version: > > 0.24.1 > > > Does anyone know what may be causing this? We have checked /etc/ > hosts and it seems to be correct. > > > Regards, > > Kenneth Holter > > _______________________________________________ > Puppet-users mailing list > Puppet-users@madstop.com > https://mail.madstop.com/mailman/listinfo/puppet-users_______________________________________________ Puppet-users mailing list Puppet-users@madstop.com https://mail.madstop.com/mailman/listinfo/puppet-users
Tried shutting down iptables, but the problem persists. "telnet <puppetmaster> 8140" also worked, indicating that the firewall is not the problem. ________________________________ Fra: puppet-users-bounces@madstop.com [mailto:puppet-users-bounces@madstop.com] På vegne av Andrew Otto Sendt: 12. februar 2008 09:34 Til: Puppet User Discussion Emne: Re: [Puppet-users] getaddrinfo: Name or service not known I had a similar problem when I was starting out with Puppet. Check to make sure iptables isn''t getting in the way. /etc/init.d/iptables stop And see if you still get the same error. -Andrew Otto On Feb 12, 2008, at 3:09 PM, Holter, Kenneth wrote: Hi. When running "puppetd --server <puppetmaster> --waitforcert 50 --test" on a puppet client we get the following error: /usr/lib/ruby/1.8/net/http.rb:560:in `initialize'': getaddrinfo: Name or service not known (SocketError) from /usr/lib/ruby/1.8/net/http.rb:560:in `open'' from /usr/lib/ruby/1.8/net/http.rb:560:in `connect'' from /usr/lib/ruby/1.8/timeout.rb:56:in `timeout'' from /usr/lib/ruby/1.8/timeout.rb:76:in `timeout'' from /usr/lib/ruby/1.8/net/http.rb:560:in `connect'' from /usr/lib/ruby/1.8/net/http.rb:553:in `do_start'' from /usr/lib/ruby/1.8/net/http.rb:548:in `start'' from /usr/lib/ruby/site_ruby/1.8/puppet/network/xmlrpc/client.rb:128:in `start'' from /usr/lib/ruby/site_ruby/1.8/puppet/network/client.rb:99:in `initialize'' from /usr/lib/ruby/site_ruby/1.8/puppet/network/client/master.rb:203:in `initialize'' from /usr/sbin/puppetd:312:in `new'' from /usr/sbin/puppetd:312 Our system specs are these: uname -a: Linux a01apfl004.adeo.no 2.6.18-53.el5 #1 SMP Wed Oct 10 16:34:19 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux cat /etc/redhat-release: Red Hat Enterprise Linux Server release 5.1 (Tikanga) puppetd --version: 0.24.1 Does anyone know what may be causing this? We have checked /etc/hosts and it seems to be correct. Regards, Kenneth Holter _______________________________________________ Puppet-users mailing list Puppet-users@madstop.com https://mail.madstop.com/mailman/listinfo/puppet-users _______________________________________________ Puppet-users mailing list Puppet-users@madstop.com https://mail.madstop.com/mailman/listinfo/puppet-users
"Holter, Kenneth" <Kenneth.Holter@nav.no> writes:> /usr/lib/ruby/1.8/net/http.rb:560:in `initialize'': \ > getaddrinfo: Name or service not known (SocketError)This error indicates that your local resolver is not able to look up either the provided puppetmaster host or port name. What''s in your /etc/puppet/puppet.conf ? -- Stig Sandbeck Mathisen, Linpro
Hi.
This is our /etc/puppet/puppet.conf file:
-- File start
# Main config parameters
[main]
vardir = /var/lib/puppet
logdir = /var/log/puppet
rundir = /var/run/puppet
ssldir = $vardir/ssl
pluginsync = true
# pluginsource = puppet://$server/plugins
storeconfigs = true
# Puppet client configuration
[puppetd]
report = true
classfile = $vardir/classes.txt
localconfig = $vardir/localconfig
# Puppetmaster configuration
[puppetmasterd]
certname = a07mmfl001.internsone.local
storeconfigs = true
dbadapter = mysql
dbuser = puppet
dbpassword = puppet
dbserver = localhost
dbsocket = /var/lib/mysql/mysql.sock
reports = tagmail,daily,security
-- File end
I''m able to reach puppetmaster on port 8140 when issuing the command
"telnet a07mmfl001.internsone.local 8140".
-----Opprinnelig melding-----
Fra: puppet-users-bounces@madstop.com [mailto:puppet-users-bounces@madstop.com]
På vegne av Stig Sandbeck Mathisen
Sendt: 12. februar 2008 10:19
Til: puppet-users@madstop.com
Emne: Re: [Puppet-users] getaddrinfo: Name or service not known
"Holter, Kenneth" <Kenneth.Holter@nav.no> writes:
> /usr/lib/ruby/1.8/net/http.rb:560:in `initialize'': \
> getaddrinfo: Name or service not known (SocketError)
This error indicates that your local resolver is not able to look up either the
provided puppetmaster host or port name.
What''s in your /etc/puppet/puppet.conf ?
--
Stig Sandbeck Mathisen, Linpro
_______________________________________________
Puppet-users mailing list
Puppet-users@madstop.com
https://mail.madstop.com/mailman/listinfo/puppet-users
Possibly Parallel Threads
- Howto model different stages
- getaddrinfo: nodename nor servname provided, or not known
- Facter 1.6.9 complains about "No LSB modules are available."
- SocketError: getaddrinfo: Name or service not known --> error while running test case
- Do we need a new name for "--test"?