On 10/07/2010 09:01 PM, Mohamed Lrhazi wrote:
> Am thinking about configrung my clients this way:
>
> 1: Daemonized puppet runs from init.d script as normal with this:
>
> [r...@chapeau ~]# cat /etc/sysconfig/puppet
> ...
> PUPPET_EXTRA_OPTS=--no-client
> ...
>
> [r...@chapeau ~]# cat /etc/puppe
Am thinking about configrung my clients this way:
1: Daemonized puppet runs from init.d script as normal with this:
[r...@chapeau ~]# cat /etc/sysconfig/puppet
...
PUPPET_EXTRA_OPTS=--no-client
...
[r...@chapeau ~]# cat /etc/puppet/puppet.conf
[puppetd]
report = true
listen = true
2: A
> > From the 2.6.1 man page:
> >
> > test: Enable the most common options used for testing.
> > These are +onetime+, +verbose+, +ignorecache,
> > +no-daemonize+, and +no-usecacheonfailure+.
> >
> >
> >>
> >> Because --test is what we are using constantly he
>>> I'm guessing that it will work if you run it with the -no-deamonize
>>> option.
>>>
>>> You really don't want to use --test. That will have other effects.
>>
>> Patrick,
>>
>> could you elaborate on that?
>
> From the 2.6.1 man page:
>
> test: Enable the most common options used
- Original Message -
> From: "Felix Frank"
> To: puppet-users@googlegroups.com
> Sent: Thursday, October 7, 2010 3:40:01 AM
> Subject: Re: [Puppet Users] puppet push mode
> On 10/07/2010 04:48 AM, Patrick wrote:
> > I'm guessing that it will work
On Oct 7, 2010, at 12:40 AM, Felix Frank wrote:
> On 10/07/2010 04:48 AM, Patrick wrote:
>>
>> On Oct 6, 2010, at 5:20 PM, Mohamed Lrhazi wrote:
>>
>>> On Wed, Oct 6, 2010 at 7:33 PM, James Louis wrote:
if an instance of puppetd is already running then you'll get that error
message w
On 10/07/2010 04:48 AM, Patrick wrote:
>
> On Oct 6, 2010, at 5:20 PM, Mohamed Lrhazi wrote:
>
>> On Wed, Oct 6, 2010 at 7:33 PM, James Louis wrote:
>>> if an instance of puppetd is already running then you'll get that error
>>> message when you try to start up another instance. also there may b
On Oct 6, 2010, at 5:20 PM, Mohamed Lrhazi wrote:
> On Wed, Oct 6, 2010 at 7:33 PM, James Louis wrote:
>> if an instance of puppetd is already running then you'll get that error
>> message when you try to start up another instance. also there may be a
>> puppetd.pid left from the last time it wa
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 already running then you'll
On Wed, Oct 6, 2010 at 7:33 PM, James Louis wrote:
> if an instance of puppetd is already running then you'll get that error
> message when you try to start up another instance. also there may be a
> puppetd.pid left from the last time it was ran. you would then have to
> remove that pid file.
>
if an instance of puppetd is already running then you'll get that error
message when you try to start up another instance. also there may be a
puppetd.pid left from the last time it was ran. you would then have to
remove that pid file.
On Wed, Oct 6, 2010 at 6:16 PM, Mohamed Lrhazi wrote:
> On W
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 reports about what needs to run (from the noop p
sounds like you have puppetd already running
On Wed, Oct 6, 2010 at 5:42 PM, Mohamed Lrhazi wrote:
> The error when run without --test is:
>
> # puppetd --noop --onetime
> Could not prepare for execution: Could not create PID file:
> /var/lib/puppet/run/puppetd.pid
>
>
>
> On Wed, Oct 6, 2010
The error when run without --test is:
# puppetd --noop --onetime
Could not prepare for execution: Could not create PID file:
/var/lib/puppet/run/puppetd.pid
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 w
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 I assume from cron) with --onetime and --noop, while the
listner is running, I get this:
# puppetd --noop --test
notice: Ign
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
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 this be proper configuration or would it be an unsupported hack ?
Thanks a lot.
Mohamed.
--
You received thi
On Wed, Oct 6, 2010 at 4:33 PM, James Louis wrote:
> 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.
>
Thanks a lot. That seems to work
Now I know how to run pupp
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 wrote:
> > I couldn'
On Wed, Oct 6, 2010 at 9:01 AM, James Louis wrote:
> I couldn't find anything that said the setting of runinterval would affect
> the stopping of pull. Ohad, I did find the no-client option and have it in
> effect. It does appear to stop the pull.
>
That does not work for me... what version are y
> 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.
The wiki is good starting point to add content. And James recently
pointed out how to get things to the curated documentation [1]. But I
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 find anything tha
On 10/06/2010 03:01 PM, James Louis wrote:
> I couldn't find anything that said the setting of runinterval would affect
> the stopping of pull. Ohad, I did find the no-client option and have it in
> effect. It does appear to stop the pull.
can you look a ticket to improve documentation? Or even co
I couldn't find anything that said the setting of runinterval would affect
the stopping of pull. Ohad, I did find the no-client option and have it in
effect. It does appear to stop the pull.
On Wed, Oct 6, 2010 at 7:53 AM, Ohad Levy wrote:
> --no-client
>
> Ohad
>
> On Tue, Oct 5, 2010 at 3:33 P
--no-client
Ohad
On Tue, 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 30 minutes. What else needs to be s
man puppet.conf
---
runinterval
How often puppetd applies the client configuration; in seconds.
* Default: 1800
---
i would assume that an interval of 0 would prevent puppet from running
periodically, perhaps someone else can correct me if i'm wrong.
byron
From: puppet-users@go
26 matches
Mail list logo
