this time when I try to connect the first node:
[root@qaagt20 ~]# /etc/init.d/puppet start
Starting puppet: /usr/lib/ruby/1.8/net/http.rb:560:in `initialize'': No
route to host - connect(2) (Errno::EHOSTUNREACH)
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:192: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
[FAILED]
puppet is pingable, so I''m at a loss... sorry for the excess traffic
--e
Eugene Ventimiglia
Director of Systems
GridApp Systems
e: eventi@gridapp.com
o: 646 452 4081
_______________________________________________
Puppet-users mailing list
Puppet-users@madstop.com
https://mail.madstop.com/mailman/listinfo/puppet-users
On Dec 17, 2007, at 12:33 PM, Eugene Ventimiglia wrote:> this time when I try to connect the first node: > > [root@qaagt20 ~]# /etc/init.d/puppet start > Starting puppet: /usr/lib/ruby/1.8/net/http.rb:560:in `initialize'': > No route to host - connect(2) (Errno::EHOSTUNREACH) > 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:192: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 > [FAILED] > > puppet is pingable, so I''m at a loss... sorry for the excess trafficThere''s just no way this can be a Puppet problem -- you must not be connecting to the host you think you''re connecting to or something. That exception is straight out of the Linux networking libraries (I know because it''s erroneous -- the problem is usually that you can''t connect to it, rather than a routing problem). Can you connect to the port that Puppet should be listening on (8140)? -- I object to doing things that computers can do. --Olin Shivers --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com
Very sorry - selinux and iptables were both turned on... since when was dummy mode the default on Linux? --e -----Original Message----- From: puppet-users-bounces@madstop.com [mailto:puppet-users-bounces@madstop.com] On Behalf Of Luke Kanies Sent: Monday, December 17, 2007 1:48 PM To: Puppet User Discussion Subject: Re: [Puppet-users] More 0.24.0 problems On Dec 17, 2007, at 12:33 PM, Eugene Ventimiglia wrote:> this time when I try to connect the first node: > > [root@qaagt20 ~]# /etc/init.d/puppet start Starting puppet: > /usr/lib/ruby/1.8/net/http.rb:560:in `initialize'': > No route to host - connect(2) (Errno::EHOSTUNREACH) > 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:192: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 > [FAILED] > > puppet is pingable, so I''m at a loss... sorry for the excess trafficThere''s just no way this can be a Puppet problem -- you must not be connecting to the host you think you''re connecting to or something. That exception is straight out of the Linux networking libraries (I know because it''s erroneous -- the problem is usually that you can''t connect to it, rather than a routing problem). Can you connect to the port that Puppet should be listening on (8140)? -- I object to doing things that computers can do. --Olin Shivers --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com _______________________________________________ Puppet-users mailing list Puppet-users@madstop.com https://mail.madstop.com/mailman/listinfo/puppet-users