Hello,
We have upgraded Puppetdb from 1.0.2 to 1.1.1 last week, and recently we
noticed that queue is not processed. We don't know if this problem is
directly linked to the upgrade. There are now 25 000 messages waiting in
the queue. We also see errors in the Postgres log:
ERROR: insert or upd
Yes, actually.
Use multiple git trees with varying levels of security. Keeping anything
and everything in the same tree is indeed bound to cause hedaches in the
future.
On the bright side, if your changes are sufficiently self contained, git
has pretty powerful tools to rebuild your tree to get r
Hi,
the goals seem to be different enough.
Facter tries not only to gather certain pieces of system information, it
also strives to
a) serialize them into a canonical format and
b) do everything platform independently (for supported platforms, i.e.)
Facter has absolutely no capacity to supply a
We flushed the queue and also restarted Postgres. Didn't help.
On Thursday, February 28, 2013 10:14:16 AM UTC+1, ak0ska wrote:
>
> Hello,
>
> We have upgraded Puppetdb from 1.0.2 to 1.1.1 last week, and recently we
> noticed that queue is not processed. We don't know if this problem is
> direct
Hello all,
Does anyone currently manage Cisco ASA's out there via Puppet, if so how ?
Due to the size of our network it would be great if Puppet could manage
Object-groups and ACL's etc to try and standardize across our ASA hosts.
e.g.
On one ASA an Object-group would be called
monitoring_se
I am aware of https://puppetlabs.com/blog/puppet-network-device-management/
but this doesn't manager ACL's or object-groups yet, and my programming
skills aren't that great
Or has anyone used cisco one platform kit (onepk) via puppet
regards
Jim
On Thursday, 28 February 2013 10:36:22 UT
Or maybe it did. The queue size went up to like 900 and after a while it
normalized and started slowly decreasing. Right now it's empty.
There were 2 insert errors in postgres log since its restart.
It was perhaps on our end, but it would be good to hear some theories, or
suggestions where els
The queue jumped back to ~1 600, and according to the puppetdb logs, it
hasn't processed a single entry for like 20 minutes, but the log shows a
lot of slow queries (see example below). Postgres logs show no error.
And now it started processing the queue again.
Slow queries: http://pastebin.co
If you clear the queue and rollback to the original version does the
problem disappear? If you're having processing problems at the latest
version thats what I would do, as I presume we're talking production
here right?
> Can this be somehow related to the the KahaDB leak thread?
No - it doesn't
Hi, thanks for trying to help! :)
If you clear the queue and rollback to the original version does the
> problem disappear? If you're having processing problems at the latest
> version thats what I would do, as I presume we're talking production
> here right?
>
>
Yes, this is production. We wo
On Wednesday, February 27, 2013 8:34:47 AM UTC-6, Justin Lambert wrote:
>
> I've had this blog post [1] bookmarked for a while to pull the remaining
> node specific config I have out of my site.pp, but wasn't sure if there was
> a better method at this point.
>
The custom 'hiera_resources()
> Hi, thanks for trying to help! :)
I'm @ken_barber on irc btw if that is easier.
>> That is a bit of a concern, are you receiving a lot of these? Is this
>> constant?
>
> Before we flushed the queue, quite a lot. Since we flushed it, only 4 times.
>
>
>>
>> > Use of unversioned APIs is deprecate
jim wrote:
> I am aware of https://puppetlabs.com/blog/puppet-network-device-management/
>
> but this doesn't manager ACL's or object-groups yet, and my programming
> skills aren't that great
>
> Or has anyone used cisco one platform kit (onepk) via puppet
>
Cisco is working on integration
Hi All,
Puppet node is automatically updating every 30 minutes,Is there anyway to
update that time span?
Thanks,
Jithin
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an
On Thu, Feb 28, 2013 at 3:18 PM, Jithin Xavier wrote:
> Hi All,
>
> Puppet node is automatically updating every 30 minutes,Is there anyway to
> update that time span?
Yes, this is set in the agent's puppet.conf file:
http://docs.puppetlabs.com/references/3.1.latest/configuration.html#runinterval
> I'm @ken_barber on irc btw if that is easier.
>
Can't use IRC here, sorry. :(
> Okay. Did you clear the ActiveMQ queues after doing this? I usually
> just move the old KahaDB directory out of the way when I do this.
>
I haven't though about myself, but it makes sense, so I just flushe
Thanks Matt,
On which file I should edit to update runinterval?
Thanks
Jithin
On Thu, Feb 28, 2013 at 8:56 PM, Matthew Burgess <
matthew.2.burg...@gmail.com> wrote:
> On Thu, Feb 28, 2013 at 3:18 PM, Jithin Xavier
> wrote:
> > Hi All,
> >
> > Puppet node is automatically updating every 30 mi
On 28.02.2013 16:13, James Turnbull wrote:
jim wrote:
I am aware of https://puppetlabs.com/blog/puppet-network-device-management/
but this doesn't manager ACL's or object-groups yet, and my programming
skills aren't that great
Or has anyone used cisco one platform kit (onepk) via puppet
>> Okay. Did you clear the ActiveMQ queues after doing this? I usually
>> just move the old KahaDB directory out of the way when I do this.
>
>
> I haven't though about myself, but it makes sense, so I just flushed the
> queue again while puppetdb service was stopped. Since this last restart it
> s
In the file /etc/puppet/puppet.conf
In the [main] section.
Thanks & Regards,
Rakesh K.
On Thu, Feb 28, 2013 at 9:19 PM, Jithin Xavier wrote:
> Thanks Matt,
>
> On which file I should edit to update runinterval?
>
> Thanks
> Jithin
>
>
>
> On Thu, Feb 28, 2013 at 8:56 PM, Matthew Burgess <
> ma
Sorry that should have been.. in the [agent] section.
On Thu, Feb 28, 2013 at 9:26 PM, Rakesh Kathpal wrote:
> In the file /etc/puppet/puppet.conf
>
> In the [main] section.
>
> Thanks & Regards,
>
> Rakesh K.
>
>
> On Thu, Feb 28, 2013 at 9:19 PM, Jithin Xavier
> wrote:
>
>> Thanks Matt,
>>
>>
John,
Thanks for your response. I wasn't meaning to complain about the lack of
documentation, was just using it as a data point. I was trying to determine if
there was something I wasn't aware of that was available for me to use now or
something planned in the future. I know hiera is a relat
FYI, I just upgraded only the PuppetDB part to 1.1.1, using the old
1.0.2 terminus I get no errors:
2013-02-28 17:06:27,711 WARN [qtp1478462104-39] [http.server] Use of
unversioned APIs is deprecated; please use /v1/commands
2013-02-28 17:06:28,284 INFO [command-proc-44] [puppetdb.command]
[7a4a
Architecture of PM is Ubuntu 12.04 in a VM with 8GB of RAM (4.7GB used)
with Apache 2.2 as the front end.
No network bottlenecks that I have been able to identify and the nodes this
is happening on seem to be random. Different buildings on campus,
different vlans, etc. I have nodes on the sam
Using 2.6.17, I have something like this:
class yumrepos {
yumrepo { ['a',
'b']:
descr=>"yum repo $name",
baseurl=>"http://someurl/$name";;
}
}
Instead of using the names 'a' and 'b', like I'd expect (so a baseurl
of http://someurl/a), it creates .repo fil
I have a start/stop script which does something like this for the start
command:
program1 &
program2 start
program1 further launches other processes.
I have used 'exec' and 'service' resources to start/stop but either way I
see a /tmp puppet related file descriptor still open in the resultin
Hi all,
I'm installing the latest version of puppet (opensource) for Windows on
Windows 2008 Server (At Amazon EC2).
For some reason, Puppet's scheduled task is configured to run every 20
hours instead of the desired 30 minutes (as shown in
- http://docs.puppetlabs.com/windows/running.html)
I
I've been struggling to get cobbler to bootstrap puppet in Fedora 17.
Currently I'm suffering from puppet bug #9084, and I'm about to see if
applying the changes from https://github.com/puppetlabs/puppet/pull/831 get
me functional (I've already tried the symlink to ca.pem workaround, and it
di
Hello everyone! I hope your Thursdays are going swimmingly!
I'm having an issue with using data looked up via Hiera and using that in a
conditional in my manifest. Here is a simple use-case where I simply cannot
get it to work: http://pastie.org/private/gtplsiajmmrdhjie49bda#
In this example th
---
cagefs_enabled:- 'false'
should be
---cagefs_enabled: 'false'
You were creating an arrray named cagefs_enabled with the first element as
true...
Stefan - Zipkid - Goethals.
On Thu, Feb 28, 2013 at 9:44 PM, wrote:
> Hello everyone! I hope your Thursdays are going swimmingly!
>
> I'm
class yumrepos {
my_yumrepo{ ['a','b']: }
}
define my_yumrepo() {
yumrepo { $name:
descr=>"yum repo $name",
baseurl=>"http://someurl/$name";;
}
}
Should do the trick.
The problem is the $name variable is not usable when calling.. only in the
called type.
Regards,
Stefan
Other folks have pointed out the fact that you made an array, but have you
tried using true and false without the quotes ?
I believe that will produce a proper Boolean value.
“Sometimes I think the surest sign that intelligent life exists elsewhere in
the universe is that none of it has tried
Clearly I have a firm grasp on YAML. That'd be the issue - thanks!
For the record I tried all of the possible values (True, "true", 1) -
obviously it was failing as it was an array as previously mentioned.
On Thu, Feb 28, 2013 at 5:11 PM, Dan White wrote:
> Other folks have pointed out the fact
It may be worth noting that the notice() function printed the variable as a
normal string (or seemingly) making it difficult to recognize the fact it
was actually an array. I'm not sure if this is something that should be
made obvious or not but it's worth noting for anyone who lands on this via
Go
Fedora 18 is officially supported in the puppetlabs yum repos now.
Last I looked it wasn't (only a couple of days ago).
I have been running a couple of node on Fedora 18 for a while and there is
a few issues that occur but I think they still affect 17 as well.
Most of the issues I have seen relate
Actually scratch the comment about puppet having packages for Fedora 18.
The repo exists but it seems to be empty for now.
I guess they are still building it.
On 1 March 2013 10:26, Peter Brown wrote:
> Fedora 18 is officially supported in the puppetlabs yum repos now.
> Last I looked it wasn't
Puppet 3.0.2 is in the updates-testing repository for Fedora 18.
On Thu, Feb 28, 2013 at 7:35 PM, Peter Brown wrote:
> Actually scratch the comment about puppet having packages for Fedora 18.
> The repo exists but it seems to be empty for now.
> I guess they are still building it.
>
>
> On 1 Mar
Hi
I am new in Puppet and i have one error when i test Postgresql module in
infrastructure mode.
I'm using Puppet 3.1.0 in Debian squeeze or 6.0.7
i tape the next command puppetd -t -v and this is the error
info: Retrieving plugin
info: Loading facts in pe_version
info: Loading facts in postg
Are you sure your client is using 3.x? This error typically crops up with older
facter versions which don't define the osfamily variable.
To test, run "facter" on your client and see if osfamily is listed.
Sent from my iPhone
On 01 Mar 2013, at 01:47, "Alejandro Betancourt"
mailto:alejandro.be
No i have a puppetmaster 3.1.0 and when i tape "facter --version" i have
"1.6.17" and if i tape "facter operatingsystem" i have "Debian"
are you french? because i speak french
El viernes, 1 de marzo de 2013 01:44:35 UTC+1, Alejandro Betancourt
escribió:
>
>
>
--
You received this message becau
On Wed, Feb 27, 2013 at 2:53 PM, Yoav Zuri wrote:
> Hi all,
>
> I'm installing the latest version of puppet (opensource) for Windows on
> Windows 2008 Server (At Amazon EC2).
>
> For some reason, Puppet's scheduled task is configured to run every 20
> hours instead of the desired 30 minutes (as s
41 matches
Mail list logo
