Re: [Puppet Users] Failing to connect new client to master

om remote server: certificate verify failed warning: Not using cache on failed catalog err: Could not retrieve catalog; skipping run (Ping from the client shows the name is resolving to the IP I expect it to; that it's actually talking to the server I checked certificate names on.) -- David

Re: [Puppet Users] Failing to connect new client to master

On Thu, July 22, 2010 18:20, Patrick Mohr wrote: > > On Jul 22, 2010, at 12:20 PM, David Dyer-Bennet wrote: > >> >> On Thu, July 22, 2010 12:27, Patrick Mohr wrote: >>> The hostname the client connects to, must match the name on the >>> server's >&g

Re: [Puppet Users] Failing to connect new client to master

sed on time. Yes; in one case the client and the server are the same, and in the other the client is a xen guest on the server. So the clocks are *precisely* synced, in fact :-). -- David Dyer-Bennet, d...@dd-b.net; http://dd-b.net/ Snapshots: http://dd-b.net/dd-b/SnapshotAlbum/data/ Photos: htt

Re: [Puppet Users] Try at simple puppet setup -- fails

forth. Is it also introducing other complications? Are there special steps I need to take when client and server are the same? -- David Dyer-Bennet, d...@dd-b.net; http://dd-b.net/ Snapshots: http://dd-b.net/dd-b/SnapshotAlbum/data/ Photos: http://dd-b.net/photography/gallery/ Dragaera: http:/

Re: [Puppet Users] Try at simple puppet setup -- fails

ere), and that fails in exactly the same way. I've also gotten a DNS name assigned to my server, and gotten rid of all the special /etc/hosts files, and am using only the real FQDN to refer to the server; that hasn't helped either. I've been keeping busy trying things, at

Re: [Puppet Users] certificate verified failed -- After upgrade/rollback from 2.6

week for my descriptions, but it sounds like probably the same thing somewhow. I've also manually deleted the ssl directory, and even the entire /etc/puppet and /var/lib/puppet directories, and removed and reinstalled the software packages. Sort-of glad it's not just me (though sorry you&#x

Re: [Puppet Users] Re: certificate verified failed -- After upgrade/rollback from 2.6

Well, drat. I've been doing that regularly, and getting the same error you've been seeing. So apparently I've got some other issue. Sigh. -- David Dyer-Bennet, d...@dd-b.net; http://dd-b.net/ Snapshots: http://dd-b.net/dd-b/SnapshotAlbum/data/ Photos: http://dd-b.net/photography/ga

Re: [Puppet Users] Re: Can't get simplest client / server connection to work still

t. Search > for it. Ah, that's useful, thanks. A pointer to something that should eventually get me more information! This is the first thing I've really done with certificates, so I don't know the tools there very well. -- David Dyer-Bennet, d...@dd-b.net; http://dd-b.net/ Sn

[Puppet Users] Simplest setups not working

NAT on a private LAN (it's part of a cluster behind LVS in NAT mode). The client system can connect out to other services on the same host as the puppet server, but if it's depending on picking up server broadcasts or anything, that's not going to fly. -- David Dyer-Bennet, [

[Puppet Users] Some cert problem

tificate signing request showed up, and the client acknowledged getting the signed certificate, so I don't have a really basic network or config problem here. -- David Dyer-Bennet, [EMAIL PROTECTED]; http://dd-b.net/ Snapshots: http://dd-b.net/dd-b/SnapshotAlbum/data/ Photos: http://dd-b.

[Puppet Users]

uppet from /usr/lib/ruby/site_ruby/1.8/puppet/node/catalog.rb:136:in `apply' from /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:731:in `use' from /usr/lib/ruby/1.8/sync.rb:229:in `synchronize' from /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb

[Puppet Users] selinux problem? which appeared for "no apparent reason" and which I can't kilil

_ruby/1.8/puppet/util/settings.rb:711:in `use' from /usr/lib/ruby/site_ruby/1.8/puppet/network/client/master.rb:197:in `initialize' from /usr/sbin/puppetd:328:in `new' from /usr/sbin/puppetd:328

[Puppet Users] Re: selinux problem? which appeared for "no apparent reason" and which I can't kilil

setroubleshoot are running and check the /var/ > log/audit/* and /var/log/messages files for the errors. I believe the > audit logs should give you a command to run that tells you how to fix > the problem... this is of course assuming you are running with selinux > enabled and enforci

[Puppet Users] Re: selinux problem? which appeared for "no apparent reason" and which I can't kilil

On Thu, February 12, 2009 10:34, Frank Sweetser wrote: > > David Dyer-Bennet wrote: >> Darned thing is suddenly failing. We had a reboot last night, and I >> changed a couple of files today too, so either one could somehow be >> responsible. But I can't figure out

[Puppet Users] Pushing out puppet.conf?

ot;/etc/puppet/namespaceauth.conf": owner => root, group => root, mode => 644, source => "puppet:/files/lserver/namespaceauth.conf" } package { "puppet": ensure => latest, } service { "puppet":

[Puppet Users] Failing to connect new client to master

I've had a small working puppet setup, reduced by circumstances to 1.5 clients, for a while. It was up to 6 at one point, but things scaled down. So I thought I knew how to make the most basic things work. But I've been beating my head against the wall trying to get a new master and new clients

[Puppet Users] Try at simple puppet setup -- fails

This is my latest simple-as-can-be setup, with more useful information based on questions people asked me. I could sure use some help here; I've even gotten a previous puppet installation working (and it's still working; older puppet version). I'm running Centos 5.5. Puppet is installed from the

[Puppet Users] Simple setup, separate client and server -- same error

Ran through about the same scenario as before, modified for client and server being on separate systems. Got the same error. Here are the details and some things I thought might be relevant info at the end. On server Uninstall puppet. Remove /etc/puppet and /var/lib/puppet. Clean up old puppet

[Puppet Users] Can't get simplest client / server connection to work still

I've triple-checked that I'm restarting the server after changing the config. I'm sure I have been all along; in any case the latest test fails just like the others, with err: Could not retrieve catalog from remote server: hostname not match with the server certificate Just out of curiosity, whi