Hello All,
I am trying to put puppet into push mode only. The instructions I've seen
have said to put listen=true in puppet.conf but that doesn't seem to have
stopped the pull every 30 minutes. What else needs to be set?
Thanks,
Jim
--
“Twenty years from now you will be more disappointed by th
Oct 5, 2010 at 3:33 PM, James Louis wrote:
>
>> Hello All,
>>
>> I am trying to put puppet into push mode only. The instructions I've seen
>> have said to put listen=true in puppet.conf but that doesn't seem to have
>> stopped the pull every
Pete,
Is there a central location for Puppet documentation? I would be glad to
add/update the docs. Seems there should be a chapter/paragraph on using push
only.
Jim
On Wed, Oct 6, 2010 at 8:16 AM, Peter Meier wrote:
> On 10/06/2010 03:01 PM, James Louis wrote:
> > I couldn't
you have to use --no-client on the command line when running puppetd. I've
set it up in my /etc/sysconfig/puppet file on CentOS so it's pulled in as
part of PUPPET_EXTRAOPTS.
On Wed, Oct 6, 2010 at 3:09 PM, Mohamed Lrhazi wrote:
> On Wed, Oct 6, 2010 at 9:01 AM, James Louis
that sounds like how I would set it up
On Wed, Oct 6, 2010 at 4:42 PM, Mohamed Lrhazi wrote:
> I think I got it...
>
> - Run puppetd with --no-client and listen mode. Activate changes by
> calling puppetrun
> - From cron, run puppetd --noop on regular basis to report on the config.
>
> Would thi
t;
> On Wed, Oct 6, 2010 at 6:40 PM, Mohamed Lrhazi wrote:
> > On Wed, Oct 6, 2010 at 6:33 PM, James Louis wrote:
> >> that sounds like how I would set it up
> >>
> >
> > One little problem though It I try to run puppetd from command
> > line (and
> On Wed, Oct 6, 2010 at 7:07 PM, James Louis wrote:
> > sounds like you have puppetd already running
>
> That's right. I am trying to see if I can run puppetd in listen mode,
> permanently. AND, from shell/cron, run puppetd --noop.
>
> Goal:
> - Receive constant
all I know is you should probably only run one instance at a time. I'm kinda
of a noob at this too so I hope I've been helpful.
On Wed, Oct 6, 2010 at 7:20 PM, Mohamed Lrhazi wrote:
> On Wed, Oct 6, 2010 at 7:33 PM, James Louis wrote:
> > if an instance of puppetd is a
Thanks Daniel,
in puppet.conf on the server: (we are just trying to get a file installed to
the int environment client)
[main]
vardir = /var/lib/puppet
logdir = /var/log/puppet
rundir = /var/run/puppet
ssldir = $vardir/ssl
pidfile=$rundir/puppetmaster.pid
[int]
#modulepat
Don't know what to tell you. Commenting out the line in that file fixed the
problem. And it's been working great since.
On Thu, Nov 18, 2010 at 5:51 PM, Felix Frank <
felix.fr...@alumni.tu-berlin.de> wrote:
> On 12.11.2010 19:22, techn0gichida wrote:
>
>> I found the problem in /etc/sysconfig/pup
t;
> On Nov 18, 6:32 pm, James Louis wrote:
> > Don't know what to tell you. Commenting out the line in that file fixed
> the
> > problem. And it's been working great since.
>
> I'm glad your problem is fixed.
>
> Folks around here have previously info
I'm kind of new at all this too but has something been changed recently on
the server(s) or the network? It looks like there might be a problem with
accessing network information.
On Tue, Dec 7, 2010 at 5:35 AM, Himanshu Raina wrote:
> Hi,
>
> Is there anyone who can help in this regard ??
>
> On
d, but we're okay with this for the short term).
> >
> > Do you have something chewing CPU on your systems?
> >
> > On 8 December 2010 00:07, James Louis wrote:
> >>
> >> I'm kind of new at all this too but has something been changed recently
and what is the current functionality for the --test option?
On Sun, Jan 23, 2011 at 5:48 PM, Nigel Kersten wrote:
> On Sun, Jan 23, 2011 at 3:38 PM, Dan Bode wrote:
> > On Sun, Jan 23, 2011 at 3:35 PM, Daniel Pittman
> > wrote:
> >>
> >> My inclination is to say that "ontime" or "verbose" hav
M, Patrick wrote:
>
> On Jan 23, 2011, at 4:02 PM, James Louis wrote:
>
> > and what is the current functionality for the --test option?
>
> To quote Nigel:
>
> --onetime
> --no-daemonize
> --ignorecache
> --verbose
> --no-usecacheonfailure
>
> and I t
exactly. to what purpose?
On Sun, Jan 23, 2011 at 6:50 PM, Patrick wrote:
>
> On Jan 23, 2011, at 4:47 PM, James Louis wrote:
>
> > that tells what options are applied when --test is used but doesn't
> explain the functionality of --test (i.e. --test is an option to enabl
at 4:53 PM, James Louis wrote:
> > exactly. to what purpose?
>
> To trigger an immediate run on a client with the common options used
> when testing a real run, not a noop run.
>
> If there was a clear word that described this functionality, we
> probably wouldn&
th levels of output --
> either v1, v2, v3 or vv, vvv, , etc.
>
> -Eric
>
>
> On Jan 23, 8:51 pm, Nigel Kersten wrote:
> > On Sun, Jan 23, 2011 at 5:34 PM, James Louis
> wrote:
> > > so the actual changes take place, if any, during a test vs a
My experience is having "listen = true" in the puppet conf and starting the
client with --no-client does prevent the puppet pull. This works for me so
that I can issue a puppet kick on the server to only serve changes when I
want to.
On Tue, Feb 15, 2011 at 2:54 PM, Nan Liu wrote:
> On Tue, Feb
logs from the same VCS that the internal one uses.
>
> (Personally, I would suggest that opening the port is less security
> auditing overhead than an entire puppet master out in the DMZ, but
> YM(and auditors)MV.)
>
> Daniel
>
> On Tue, Feb 15, 2011 at 13:04, James Louis wrote
set enabled=0 in /etc/yum.repos.d/epel.repo and use --enablerepo=epel when
using yum to install puppet
On Wed, Feb 16, 2011 at 7:27 AM, Romain Pelisse wrote:
> Personnally, I just used the EPEL repository to install both puppet and
> puppetmaster. I still need to figure out a way to tell to yum
t; catalog to be pushed to the client. Not just the server telling the client
> to pull the config, because the client can't connect to the server since the
> client is locked in the DMZ.
>
> On Feb 15, 2011, at 5:37 PM, James Louis wrote:
>
> in spite of this not actually bei
22 matches
Mail list logo
