On Friday, January 10, 2014 3:19:39 PM UTC+1, jcbollinger wrote:
> A v2.6 agent should work with a v2.7 master, but it is worthwhile checking
> out the effect of the upgrade.
>
The upgrade to 2.7.23 had no effect on the issue.
The master runs 3.3.2 by the way; are there issues with this?
>
On 01/10/2014 03:19 PM, jcbollinger wrote:
> Myself, I'm stumped. I agree with Felix that it looks like there's a
> bug in the provider, but that's not really saying much more than "it
> shouldn't do that". I am curious, however, whether Puppet is actually
> modifying /etc/fstab on either the fai
On Friday, January 10, 2014 5:53:51 AM UTC-6, zerozer...@gmail.com wrote:
>
> On Friday, January 10, 2014 11:32:59 AM UTC+1, Felix.Frank wrote:
>
>
>> I think your original post to the list was pretty much to the point.
>
>
> I just realized the machine was still running puppet 2.6.18.
> I now
On Friday, January 10, 2014 11:32:59 AM UTC+1, Felix.Frank wrote:
> I think your original post to the list was pretty much to the point.
I just realized the machine was still running puppet 2.6.18.
I now upgraded to 2.7.23 and I'll wait some runs before filing the issue.
The bug appears to be
:) OK.
I think your original post to the list was pretty much to the point.
On 01/10/2014 11:31 AM, zerozerouno...@gmail.com wrote:
>
> I'll file a report even though I'm not 100% sure "what" to report… :)
--
You received this message because you are subscribed to the Google Groups
"Puppet Us
On Friday, January 10, 2014 11:05:47 AM UTC+1, Felix.Frank wrote:
looks like a minor bug with the mount provider. You may want to file a
> report, although you should be able to trivially work around it by
> fixing your fstabs, correct?
Yes, it's not a big problem for me. I just wanted to be
Hi,
looks like a minor bug with the mount provider. You may want to file a
report, although you should be able to trivially work around it by
fixing your fstabs, correct?
Thanks,
Felix
On 01/10/2014 10:49 AM, zerozerouno...@gmail.com wrote:
> The problem remained the same, of course, and here is
On Thursday, January 9, 2014 3:58:10 PM UTC+1, jcbollinger wrote:
> puppet agent --no-daemonize --debug --verbose --interval=120 --logdest
>> stdout
>
>
The --interval option is not accepted, so being forced to use the default
of 30 minutes I used:
PUPPET_EXTRA_OPTS="--debug --verbose --lo
On Thursday, January 9, 2014 5:11:06 AM UTC-6, Felix.Frank wrote:
>
> Hi,
>
> I'm not sure whether debug logging ends up in /var/log/messages. There
> may be syslog configuration issues.
>
> Here's an idea:
>
> puppet agent --no-daemonize --debug --verbose --interval=120 --logdest
> stdout
Hi,
I'm not sure whether debug logging ends up in /var/log/messages. There
may be syslog configuration issues.
Here's an idea:
puppet agent --no-daemonize --debug --verbose --interval=120 --logdest
stdout
That should make your debugging agent try to run once and repeat each 2
minutes, dumping t
On Wednesday, January 8, 2014 11:15:24 AM UTC+1, Felix.Frank wrote:
> can you reproduce this using puppet agent --one-time?
>
"puppet agent --onetime" always fails, just like "puppet agent --test".
> If not, you may have to activate debug logging in your background agent.
I added "PUPPET_
Hi,
can you reproduce this using puppet agent --one-time?
If not, you may have to activate debug logging in your background agent.
Otherwise, it will be difficult to determine what's happening when and why.
Thanks,
Felix
On 01/08/2014 10:12 AM, zerozerouno...@gmail.com wrote:
>
> Just for comp
On Tuesday, January 7, 2014 3:10:31 PM UTC+1, zerozer...@gmail.com wrote:
> The problem is with automated puppet runs every 30 minutes, as per
> default: 50% of the runs end with no errors in the report, even though the
> class is not correctly applied.
>
Just for completeness, here is an exc
13 matches
Mail list logo
