I'm in the process of scalling my puppet master to two server with a
separate CA. My plan was to establish a new CA and reissue
certificates. Part way through the process I noticed a behavior that
seems a bit alarming.
With one of my clients pointing to the new CA and new Puppetmaster but with
Hi,
On Tue, Jan 3, 2012 at 5:47 AM, Nigel Kersten wrote:
> This is actually in Facter.
>
> Can you bug report here please?
>
> http://projects.puppetlabs.com/projects/facter/issues
>
>
I just found that there already is a related bug report:
http://projects.puppetlabs.com/issues/1415
Gerald
If
ss is something updated that is now causing
puppet to hang when set to listen.
I'll post back if I find more. I'll submit a bug if I can isolate it.
-Chip
On Fri, Nov 11, 2011 at 11:19 AM, Chip Schweiss wrote:
> Yes the lock file is created immediately and never runs. The logs repor
and another where puppet daemon will
> work for awhile, then fail, leaving puppetdlock file. Do you have a
> puppetdlock file left after your daemon has been running long enough to try
> to run? It may be immediately, but we use splay, so have to wait awhile.
>
>
> On Fri, No
1 at 3:23 PM, Chip Schweiss wrote:
>
>> This is on Centos 5.7 with puppet 2.6.9. This installation has been
>> running for about a year and now nearly all my hosts are hanging.
>>
>> Running 'puppetd --test' or 'puppetd --test --debug' executes
>>
This is on Centos 5.7 with puppet 2.6.9. This installation has been
running for about a year and now nearly all my hosts are hanging.
Running 'puppetd --test' or 'puppetd --test --debug' executes successfully
every time. However when the puppet service is started it will create the
lock file (/v
ould understand that in puppet everything is 'set' before anything is
> 'done'.
> Stages just help to order the 'get it done' part.
>
> So the answer to your question about "a method to access a variable" is:
> just access it!
>
>
I'm looking for a method to access a variable set in my main state from a
class in my post stage?
Is this possible? Any know way of passing the information?
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to p
my network class I want to use deploy_* variables defined in the node.
I not sure how to get puppet to always load the node definition before all
other classes. Almost seems like a bug.
-Chip
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" gro
I have pre, main, and post stages configured in my manifests.
When I assign variables in the node declaration they are present in
the main stage, but not my pre-stage.
How do I assign variables at the node level that can be referenced in
my pre stage?
-Chip Schweiss
--
You received this
On Tue, Apr 19, 2011 at 6:30 AM, Ben Hughes wrote:
> On Mon, Apr 18, 2011 at 09:16:13AM -0700, Kal McFate wrote:
>
> > How do I tell puppet to log somewhere other than /var/log/messages. None
> of
> > the logging configuration options seem to do anything any more.
> Specifically
> > puppetdlog.
>
I have a hash with network information structured as such:
$networkinfo = {
'machine1.domain.local' => { eth0 => { ip => '192.168.1.50',
mask => '255.255.255.0', gw => '192.168.1.254' },
eth1 => { ip => '192.168.2.68', mask =>
'255.255.255.0' } },
'machine2.domain.local' =
Hi,
On Tue, Nov 30, 2010 at 10:52 PM, Dan Bode wrote:
> Hi,
>
> Anyone have interest in a puppet meet-up in Vienna? I will be in the area
> for the holidays and would love to meet up with local puppet users to chat
> about Puppet/Linux and such. I am thinking about the 20th of December.
>
> rega
13 matches
Mail list logo
