On Thursday, June 19, 2014 2:48:19 AM UTC-5, [email protected] wrote: > > > > *It's work. * > It was spelling problem, I change it now to: > > *node_terminus = exec. * > >
Good. > And it work when 'external_nodes =' with or without the ' /usr/bin/env > PUPPET_DASHBOARD_URL=http://user:pass@localhost:3000' > Surprising. You should anyway omit that bit. > I also delete *'node: <certname>*' from my script. > > Fine. I'm not sure what that's supposed to be for, either. I don't think it's required. > Now when I start httpd, after changing the puppet.conf, I get in the > system message file: > > *Config file /etc/puppet/puppet.conf changed; triggering re-parse of all > config files. * > > > Ok. > But I start getting in the puppet server, system message file: > > > *puppet-agent[23124]: Failed to apply catalog: getaddrinfo: Name or > service not known puppet-agent[23124]: Could not send report: getaddrinfo: > Name or service not known * > > > It looks like the agent is trying to contact the master via a machine name that it cannot resolve. Since this is happening on the machine that hosts the master, and you've been mucking with the Puppet configuration on that machine, it seems likely that you changed something there to create this problem (or maybe Puppet itself did, at your behest). In particular, unless your machine can resolve the hostname "puppet" (to the address of the master), the [agent] section of your puppet.conf should contain a 'server' setting that identifies the puppetmaster machine by a resolvable name that appears on the master's certificate. Normally, the master's FQDN is a good choice. > Sorry & I'm very appreciate your help, Thanks to everyone! > > Q: If I upgrade puppet, should I backup something. Can it make my puppet > server/Passenger stop working? > > It's always wise to make backups before updating critical components. Any update you perform carries some risk of breakage. With that said, Puppet bugfix updates (x.y.n to x.y.m) are pretty safe. You should not expect any breakage around such updates unless you happen to be relying on buggy behavior (which is never safe). Puppet feature updates (x.n.y to x.m.z) are generally safe. They are not supposed to cause breakage of any documented behavior, but regressions occasionally happen. You should already have your manifests (including third-party modules) and data under revision control, in which case you don't need any additional backup of those. For the most protection, you should also back up your master's data directory, especially all the SSL certificates. Losing those may require you to generate new certificates for all your clients, which can really ruin your day. John -- 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/c7d0bea8-0c26-442e-b69b-f110fa0b730f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
