On Feb 23, 4:02 pm, weloki <[email protected]> wrote: > Every time I try to do puppetd --test on a host to get configs from > the puppetmaster server it fails with this error: > > Could not retrieve catalog from remote server: Connection timed > out - connect(2) > > Of course running it on the puppetmaster server itself works fine, so > it's some kind of networking issue. I was thinking maybe it's > something with webrick, which is what I'm using now, but I've only > been testing one host at a time and wasn't doing anything differently > when this started happening. I'm running version 2.7.11 of both puppet > and puppetmaster on Ubuntu server 10.04 LTS. I just upgraded from > 2.7.10 today, but I was developing and testing modules for several > hours afterward and the issue just started happening from out of > nowhere.
There are two main possibilities: 1) Packets from your nodes aren't reaching the master. This could be because physical disconnection, router malfunction, or some similar issue, or 2) The master's network layer is refusing connections to your nodes. I'd start by trying to ping the master from your nodes. If that succeeds then you have narrowed the possibilities to class (2). (But if it fails, then it could still be either (1) or (2)). I'd also check the master's firewall. Easiest (though slightly risky) would be to shut it down while you test Puppet on an agent (don't forget to bring it back up after testing). If Puppet works with the firewall down but fails with the firewall up, then the firewall is your problem. Typically, port 8140 must be open for TCP connections on the master, though it's possible to run Puppet on a different port. John -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
