Yeah, I've looking into this but it would require a bit of re-tooling for
us. We currently just summarize everything in our completed column, if we
broke it out by week we'd have to add some logic to the summarize method to
figure out which week the card actually fell in.
I'm not saying this isn't
Facter 1.7.2 is a bugfix release in the 1.7 series.
To see a list of the issues addressed by this release, check out the
1.7.2 version in our issue tracker at:
https://projects.puppetlabs.com/versions/403
Downloads are available at:
* Source: https://downloads.puppetlabs.com/facter/facter-1.7.2.
The KDE project does their weekly commit digest for every week even though
it sometimes gets done late. So you can sometimes get the last two digests
at once. I think that is better if they can't come out every week.
http://www.commit-digest.org/
On 10 July 2013 21:26, Jeff McCune wrote:
> Tha
That's what I'm thinking. :)
On Wednesday, July 10, 2013, James Turnbull wrote:
> Jeff McCune wrote:
> > I don't think it's the cadence that's the problem but rather my
> > discipline sending it out each Monday. Perhaps switching it to Friday
> > when the previous week is still at the top of my
Jeff McCune wrote:
> I don't think it's the cadence that's the problem but rather my
> discipline sending it out each Monday. Perhaps switching it to Friday
> when the previous week is still at the top of my mind will be better.
> On Monday's I'm usually looking forward at the week ahead rather t
I don't think it's the cadence that's the problem but rather my discipline
sending it out each Monday. Perhaps switching it to Friday when the
previous week is still at the top of my mind will be better. On Monday's
I'm usually looking forward at the week ahead rather than the week behind
and I t
It's also possible that PuppetDB is not running due to the postgres error.
On the PuppetDB machine, you can run these to find out:
service pe-puppetdb status
telnet localhost 8081
PuppetDB logs can be found in /var/log/pe-puppetdb/puppetdb.log (I
believe). If there is an error at the en
Hi Chris,
Thanks for the reply.
Please bare with me a little while... I will move to the suggested group.
I have been grappling with the 8081 port issue...
telnet produces this:
connect to address 192.168.60.130: Connection refused
I used something like this: iptables -A INPUT -p tcp --dport
On Wednesday, 10 July 2013 12:43:00 UTC+3, Joseph Mwesigwa Bbaale wrote:
>
> Hello developers.
>
> First, I am really new to puppet so, please pardon me if my question has
> rather an obvious answer.
>
> I have tried to install puppet on both a Debian 6 VM and CentOS 6.3 VM but
> always get thi
Hi Joseph,
Based on this line:
SERVER: Failed to submit 'replace facts' command for
pptconsole.ca.local to PuppetDB at pptconsole.ca.local:8081: No route to
host - connect(2)
It sounds as though you may have a DNS issue. If you log in to your puppet
master VM, are you able to ping 'pptconso
Hello developers.
First, I am really new to puppet so, please pardon me if my question has
rather an obvious answer.
I have tried to install puppet on both a Debian 6 VM and CentOS 6.3 VM but
always get this error along the way:
## Setting up the database...
Configuring postgresql server...
11 matches
Mail list logo
