I nearly forgot to write in that we removed the puppet client (EPEL)
and reinstalled, and the --verbose went away. We never did figure out
where it was coming from, though. Thanks for everyone's help.
On Tue, Mar 9, 2010 at 5:34 PM, Todd Zullinger wrote:
> Kent Rankin wrote:
>> [r...@ ~]#
Kent Rankin wrote:
> [r...@ ~]# rpm -V puppet
> S.5T c /etc/puppet/puppet.conf
> [r...@ ~]# grep verbose /etc/init.d/puppet
> [r...@ ~]# grep verbose /etc/sysconfig/puppet
> [r...@ ~]# cat /etc/sysconfig/puppet
> # The puppetmaster server
> #PUPPET_SERVER=puppet
>
> # If you wi
[r...@ ~]# rpm -V puppet
S.5T c /etc/puppet/puppet.conf
[r...@ ~]# grep verbose /etc/init.d/puppet
[r...@ ~]# grep verbose /etc/sysconfig/puppet
[r...@ ~]# cat /etc/sysconfig/puppet
# The puppetmaster server
#PUPPET_SERVER=puppet
# If you wish to specify the port to connect to
Kent Rankin wrote:
> Installed the EPEL package... it runs it as a daemon without options.
> Here's the output from ps -ef|grep puppet:
>
> root 10249 1 0 Mar08 ?00:02:17 /usr/bin/ruby
> /usr/sbin/puppetd --verbose
That --verbose is what's causing this I think. That's not part of
Installed the EPEL package... it runs it as a daemon without options.
Here's the output from ps -ef|grep puppet:
root 10249 1 0 Mar08 ?00:02:17 /usr/bin/ruby
/usr/sbin/puppetd --verbose
Thanks.
On Tue, Mar 9, 2010 at 4:07 PM, Todd Zullinger wrote:
> I wrote:
>> James Turnbull
I wrote:
> James Turnbull wrote:
>> Do you get a report each time without a value specified in
>> config_version?
>
> Yes. With config_version commented out in puppet.conf, I get a report
> using the timestamp even if nothing has changed. With a command set
> for config_version, I also get a repo
James Turnbull wrote:
> Do you get a report each time without a value specified in
> config_version?
Yes. With config_version commented out in puppet.conf, I get a report
using the timestamp even if nothing has changed. With a command set
for config_version, I also get a report when nothing has
On Tue, Mar 9, 2010 at 12:07 PM, Kent Rankin wrote:
> When is 0.25.5 scheduled to be fixed? If it's not very soon, we're
> going to have to jump on the CFEngine bandwagon.
Just for this feature? If it's that critical to you, wouldn't
providing a patch be a more productive use of your time rather
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/03/10 7:12 AM, Todd Zullinger wrote:
> R.I.Pienaar wrote:
>> http://projects.reductivelabs.com/issues/3043
>>
>> it seems to be related to the ongoing pain with execs
>
> Ahh, I think I may have run into that and that's why I ended up with
> the
R.I.Pienaar wrote:
> http://projects.reductivelabs.com/issues/3043
>
> it seems to be related to the ongoing pain with execs
Ahh, I think I may have run into that and that's why I ended up with
the commands in the config_version directly. It's been a while since
I set that up to test so I'd forgo
When is 0.25.5 scheduled to be fixed? If it's not very soon, we're
going to have to jump on the CFEngine bandwagon.
Thanks.
On Tue, Mar 9, 2010 at 3:04 PM, James Turnbull wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 10/03/10 3:40 AM, R.I.Pienaar wrote:
>>
>> - "Kent Ran
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/03/10 3:40 AM, R.I.Pienaar wrote:
>
> - "Kent Rankin" wrote:
>
>> This started about three days after I upgraded to 0.25 on EPEL. That
>> time delay confused me a great deal.
>>
>> Is this the standard behavior on 0.25? Is there a config
hey,
- "Todd Zullinger" wrote:
> R.I.Pienaar wrote:
> > There's a configuration option, its broken.
> >
> > The feature in 25 lets you tag a manifest with a version and the
> > version is supposed to show up in reports and logs and so forth.
> > you can specify a different way than the defau
R.I.Pienaar wrote:
> There's a configuration option, its broken.
>
> The feature in 25 lets you tag a manifest with a version and the
> version is supposed to show up in reports and logs and so forth.
> you can specify a different way than the default (current timestamp)
> with config_version optio
hello,
- "Kent Rankin" wrote:
>
> Tue Mar 09 13:24:03 -0500 2010 Puppet (info): Applying configuration
> version '1268079838'
>
> The emailed report comes in every 30 minutes, just like that, without
> making any changes on the client. This doesn't seem like how it
> should function.
ri
Here's what I'm seeing in syslog:
Mar 9 12:23:52 puppetd[10249]: Caching catalog for
Mar 9 12:23:52 puppetd[10249]: Applying configuration version '1268079838'
Mar 9 12:23:56 puppetd[10249]: Value of
'preferred_serialization_format' (pson) is invalid for report, using
defaul
hello,
- "Kent Rankin" wrote:
> Just a question, though... I'm getting that report on *EVERY* run,
> and by that, I mean to say that no changes have been made. It's just
> throwing the same version over and over again.
>
with report do you mean a log in syslog? Every run is a new compile
Just a question, though... I'm getting that report on *EVERY* run, and
by that, I mean to say that no changes have been made. It's just
throwing the same version over and over again.
Is that normal?
Thanks.
On Tue, Mar 9, 2010 at 11:40 AM, R.I.Pienaar wrote:
>
> - "Kent Rankin" wrote:
>
- "Kent Rankin" wrote:
> This started about three days after I upgraded to 0.25 on EPEL. That
> time delay confused me a great deal.
>
> Is this the standard behavior on 0.25? Is there a configuration
> option to have it only show when changes are made?
>
There's a configuration option,
This started about three days after I upgraded to 0.25 on EPEL. That
time delay confused me a great deal.
Is this the standard behavior on 0.25? Is there a configuration
option to have it only show when changes are made?
Thanks.
On Tue, Mar 9, 2010 at 10:01 AM, Michael DeHaan
wrote:
> On Tu
On Tue, Mar 9, 2010 at 2:03 AM, Kent Rankin wrote:
> Now, even though no changes have occurred, I'm getting a report like
> this every time it runs:
>
> Tue Mar 09 00:51:25 -0500 2010 Puppet (info): Applying configuration
> version '1268079838'
>
> What am I to do?
>
>
> Thanks.
>
Are you saying
21 matches
Mail list logo
