Re: [Puppet Users] Re: 3.2.2 on CentOS 6.3, and "Did not receive certificate"

2013-07-22 Thread Yaniv Kaul
I'd also disable or move to permissive selinux. Y. On Monday, July 22, 2013 10:19:35 PM UTC+3, Forrie wrote: > > Adding --debug to the config.ru didn't provide any real info -- not sure > why, but the client continued to connect and I see this in the log: > > 10.101.0.10 - - [22/Jul/2013:15:11:15

[Puppet Users] Re: 3.2.2 on CentOS 6.3, and "Did not receive certificate"

2013-07-18 Thread Yaniv Kaul
On Thursday, July 18, 2013 12:32:22 AM UTC+3, jcbollinger wrote: > > > On Wednesday, July 17, 2013 12:25:18 PM UTC-5, Yaniv Kaul wrote: >> >> >> How do I verify if multiple copies are installed? >> > > > I would suggest using the 'find' comman

[Puppet Users] Re: 3.2.2 on CentOS 6.3, and "Did not receive certificate"

2013-07-17 Thread Yaniv Kaul
On Wednesday, July 17, 2013 6:00:49 PM UTC+3, jcbollinger wrote: > > > On Tuesday, July 16, 2013 4:32:35 PM UTC-5, Forrie wrote: >> >> We are not configured to auto-sign certificates. >> >> Clearly, the client is making a connection to the master: >> >> >> 10.101.0.10 - - [16/Jul/2013:17:23:46 -04

[Puppet Users] Re: 3.2.2 on CentOS 6.3, and "Did not receive certificate"

2013-07-16 Thread Yaniv Kaul
On Thursday, July 11, 2013 9:41:26 PM UTC+3, Forrie wrote: > I'm having a perplexing problem with Puppet 3.2.2 (agent) on CentOS > 6.3.There are two systems, recently built, that exhibit the same > problem. I'm using the same, very basic and simple config I have on all > of my systems (mo