On 01/28/2011 02:36 PM, Romain Pelisse wrote:
> I'm not making myself very clear also :)    (as you are also in Berlin,
> you can realize my first question was rather late in the night ;) )
> 
> I do apologize. Here is an hopefully enlightening snippet:
> 
> $ grep -e 'server' /etc/puppet/puppet.conf
> server = puppetmaster
> $ ping puppetmaster
> (host down)
> # service puppet start
> ...
> 
> So at this point the puppet client will not be able to connect, throwing
> something like that if run with --no-daemonize and --verbose :
> 
> 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
> 
> Now, I was expecting to find those messages inside the /var/log/puppet/
> folder, as I expected the clients to "check on" the master every 30
> minutes... But, I'm starting to think I'm getting this wrong ? Maybe the
> puppetmaster is "pushing" to puppets every 30 minutes ? 

No, the clients are supposed to pull.

What client version is this? I've seen 0.24.5 clients crash when the
master went down, and seen 0.25.5 clients end up in a (apparent) sort of
deadlock. No further logging in either scenario.

I haven't tried 2.6 yet.

You're right, though. The expected result would be a client log entry
every half hour.

Cheers,
Felix

-- 
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+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Reply via email to