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

. 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/ Snapshots: http://dd-b.net/dd-b/SnapshotAlbum/data/ Photos: http://dd

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

, 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're caught in this mess). -- David Dyer-Bennet, d...@dd-b.net; http://dd-b.net/ Snapshots: http://dd-b.net/dd-b/SnapshotAlbum/data

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

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/gallery/ Dragaera: http://dragaera.info

[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,

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 certificate. I believe I have that right. On the server

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

, in fact :-). -- 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://dragaera.info -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post

[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

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

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://dragaera.info

[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

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

. 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 least! -- David Dyer-Bennet, d...@dd-b.net; http://dd-b.net

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

: 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 Dyer-Bennet, d...@dd

[Puppet Users] Pushing out puppet.conf?

, mode = 644, source = puppet:/files/lserver/namespaceauth.conf } package { puppet: ensure = latest, } service { puppet: ensure = running, enable = true, } } -- David Dyer-Bennet, d...@dd-b.net; http://dd-b.net/ Snapshots: http://dd-b.net

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

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 enforcing (from memory though CentOS does do that by default...). Cheers chakkerz On Feb 12, 8:20 am, David Dyer-Bennet d...@dd-b.net wrote: Darned

[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 how from this crash. First I

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

] (Sorry if this is a duplicate; it looks to me like I botched the post last try.) -- 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://dragaera.info

[Puppet Users]

/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 [FAILED] -- David Dyer-Bennet, d...@dd