On Friday, November 16, 2012 11:44:38 AM UTC-6, Bret Wortman wrote:
>
> On Friday, November 16, 2012 9:47:28 AM UTC-5, jcbollinger wrote:
>>
>>
>>
>> On Thursday, November 15, 2012 3:04:57 PM UTC-6, Bret Wortman wrote:
>>>
>>> Nope. Same outcome. Numerous "No child processes" errors.
>>>
>>
>> I'
On Friday, November 16, 2012 9:47:28 AM UTC-5, jcbollinger wrote:
>
>
>
> On Thursday, November 15, 2012 3:04:57 PM UTC-6, Bret Wortman wrote:
>>
>> Nope. Same outcome. Numerous "No child processes" errors.
>>
>
> I'm not up to performing a code dive at the moment to find out where those
> message
I'm absolutely ready for this to be something I've not done properly during
the kickstart process. I'm just getting started with these tools, so that's
definitely a strong probability. I'll do this again shortly with strace and
see what it reveals.
--
You received this message because you are sub
On Thursday, November 15, 2012 3:04:57 PM UTC-6, Bret Wortman wrote:
>
> Nope. Same outcome. Numerous "No child processes" errors.
>
I'm not up to performing a code dive at the moment to find out where those
messages may be emitted, but that might be useful information to have.
It might also b
Nope. Same outcome. Numerous "No child processes" errors.
On Thursday, November 15, 2012 3:22:09 PM UTC-5, Bret Wortman wrote:
>
> I do now (I was using ksmeta to set puppet_auto_setup but this is so much
> easier & cleaner!); I'll reattempt a build and see what happens.
>
>
>
**
> *
>
> Bret W
I do now (I was using ksmeta to set puppet_auto_setup but this is so much
easier & cleaner!); I'll reattempt a build and see what happens.
*
*
*
Bret Wortman***
http://bretwortman.com/
http://twitter.com/BretWortman
On Thu, Nov 15, 2012 at 3:14 PM, Gmoney wrote:
> On the cobbler side do you
On the cobbler side do you have the folliwng in your /etc/cobbler/
settings file?
# if enabled, this setting ensures that puppet is installed during
# machine provision, a client certificate is generated and a
# certificate signing request is made with the puppet master server
puppet_auto_setup: 1
On Thursday, November 15, 2012 7:56:43 AM UTC-5, Bret Wortman wrote:
>
> F17, Puppet 3.0.1 installed from RPM from a copy of the puppetlabs repos.
> SELinux disabled, iptables disabled.
>
> I just added this line to /etc/security/limits.conf:
>
> puppet hard nproc -1
>
> And it seems to hav
F17, Puppet 3.0.1 installed from RPM from a copy of the puppetlabs repos.
SELinux disabled, iptables disabled.
I just added this line to /etc/security/limits.conf:
puppet hard nproc -1
And it seems to have solved the above issue.
On Thursday, November 15, 2012 7:47:53 AM UTC-5, Edson Ma
Bret,
I'm doing the same thing without any issues. Give us csome basic
info. What OS, puppet version, RPMs or tarballs,
which yum repo, SELNIUX enforcing status and so forth.
On Thu, Nov 15, 2012 at 7:13 AM, Bret Wortman wrote:
> It's continuing even after the ownership "fix", though it's
It's continuing even after the ownership "fix", though it's intermittent.
Some runs will consist of long runs of messages in the client like these:
Error: Could not prefetch package provider 'yum': No child processes
Error: Could not set 'present' on ensure: No child processes at
105:/etc/puppet
On Tuesday, November 13, 2012 1:46:13 PM UTC-6, Bret Wortman wrote:
>
>
>
> On Tuesday, November 13, 2012 2:32:24 PM UTC-5, Bret Wortman wrote:
>>
>> I'm working on setting things up so that I can use Cobbler to kickstart a
>> basic system and then use Puppet to roll out the majority of packages
On Tuesday, November 13, 2012 2:32:24 PM UTC-5, Bret Wortman wrote:
>
> I'm working on setting things up so that I can use Cobbler to kickstart a
> basic system and then use Puppet to roll out the majority of packages based
> on the role a particular system will be playing for us. I've got a
>
13 matches
Mail list logo
