Here, puppetdb is just an example, I have given the fact is I am able to
open this URL using localhost curl command in Linux terminal.
Okay.
However, same I am expecting to get via browser.
Right but like I said, the API parts don't work in a browser unless
you are using some form of
If I run below command on puppet master. I am able to get output pasted
here.
But the same information, I am trying to capture via browser using
http://puppetdb:8080/v2/facts/operatingsystembut not working
Well, a browser probably won't work trying to traverse that URL
anyway, since a
Someone on IRC had this earlier. See:
http://projects.puppetlabs.com/issues/22530
I've escalated it to the core dev team also.
ken.
On Fri, Sep 13, 2013 at 3:16 PM, Robert Rolfe robertrolfe...@gmail.com wrote:
It's not just you, I am working on the exact same problem. 2.7.20 agents
running
Yes, using postgresql here. It turns out I have another script pushing facts
(without custom facts) into puppetdb, which messed up with puppetdb query
outputs. After fixing that script, things are ok now here.
Aaah, so it wasn't performance at all. Was that a custom script
someone at your
Running puppet only at around 4am once a day here. And I noticed that
puppetdb query not working as expected, if using it to query nodes based on
some custom fact value.
During the days, things are working fine. But if I ran the same query at
around say 3am (searching nodes based on some
Thats strange its working fine for me. What version of Puppet?
[master]
storeconfigs = true
storeconfigs_backend = puppetdb
Those settings are for PuppetDB, the problem specifically is in the
usage of the 'storeconfigs' face - which at the point of migration
should be using the legacy
1) I had to set max-threads higher than my CPU count in
/etc/puppetdb/conf.d/jetty.ini before I could get jetty to behave well. I
haven't yet determined if there is a way through the puppetdb module to
manage this directly--I plan to dig on that, but if someone knows off the
top of their
You might need to move your storeconfigs specific settings into the
[main] block of your puppet.conf ... instead of [master] for this
operation to succeed, since the storeconfigs command doesn't look into
the [master] block I believe.
On Thu, Sep 5, 2013 at 2:01 PM, Darin Perusich
Is it acceptable to do the search based on 'certname'? ie:
curl -G 'http://localhost:8080/v2/facts' --data-urlencode
'query=[and,[~,certname,puppetdb?],[or,[=,name,ipaddress],[=,name,hostname]]]'
ken.
On Mon, Sep 2, 2013 at 7:00 AM, Klavs Klavsen kl...@enableit.dk wrote:
This gives me the
I don't know if the merge is finished, but module installation seems to no
longer function :
No it is not.
[root@servername]# puppet module install puppetlabs/puppetdb
Notice: Preparing to install into /etc/puppet/modules ...
Notice: Downloading from https://forge.puppetlabs.com ...
We have a patch for this but are assessing the impact before merging.
For now I'd just ignore the warning, it shouldn't affect operation.
On Tue, Aug 27, 2013 at 9:28 AM, yannig rousseau
yannig.rouss...@gmail.com wrote:
Is the module puppetdb from the forge still correct ?
Every time I try to
I've been using PuppetDB as an ENC for a while,
So PuppetDB is not an ENC, do you mean Foreman?
but I haven't really
utilized it for stored configs or anything. I was mostly interested in
replacing Dashboard's reporting capabilities, but PuppetDB doesn't yet do
anything (that I can see)
I tired multiple times revoke master cert and created new, no luck
Can you run puppetdb-ssl-setup -f ... restart puppetdb and show us the results?
ken.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop
What does this mean ?
Warning: /etc/puppetdb/ssl/private.pem does not match the file used by
Puppet (/var/lib/puppet/ssl/private_keys/puppettest.eng.com.pem)
Warning: /etc/puppetdb/ssl/public.pem does not match the file used by Puppet
(/var/lib/puppet/ssl/certs/puppettest.eng.com.pem)
Both
postgres=# SELECT datname,pid,query_start from pg_stat_activity;
datname | pid | query_start
--+--+---
postgres | 5866 | 2013-08-23 09:17:36.913697-04
(1 row)
That pretty much confirms PuppetDB is not connecting to PostgreSQL at all.
Try
With the debug i've the next log
2013-08-15 00:37:13,960 DEBUG [main] [bonecp.BoneCPDataSource] JDBC URL =
jdbc:postgresql://127.0.0.1:5432/puppetdb, Username = pupetdb, partitions =
1, max (per partition) = 50, min (per partition) = 1, helper threads = 3,
idle max age = 60 min, idle test
Check your /etc/puppetdb/database.ini, it may be configured for
hsqldb. If in doubt provide the file here and we can take a look.
Instructions for configuring this specifically for PostgreSQL are
here: http://docs.puppetlabs.com/puppetdb/1.4/configure.html#using-postgresql
On Thu, Aug 22, 2013
= master.example.com
port = 8081
[…..]
Thanks.
El 22-08-2013, a las 12:47, Ken Barber k...@puppetlabs.com escribió:
Check your /etc/puppetdb/database.ini, it may be configured for
hsqldb. If in doubt provide the file here and we can take a look.
Instructions for configuring this specifically
We've come across a rather strange problem where the parameters of some
resources in PuppetDB are now empty.
We have a Nagios server collecting resources from PuppetDB and we've started
to get failures like this for one resource type:
Error: Could not retrieve catalog from remote server:
/puppetlabs/puppetdb/blob/master/src/com/puppetlabs/puppetdb/scf/migrate.clj#L326-L331
So its probably not specifically a bug with the schema change.
On Thu, Aug 8, 2013 at 12:48 PM, Ken Barber k...@puppetlabs.com wrote:
We've come across a rather strange problem where the parameters of some
resources
No good idea yet, but there is something suspicious in your curl
responses - the resource hash, did you obfuscate this yourself on
purpose? The two hashes between the first and second requests are
identical. That hash is calculated based on the sum of the resource,
including parameters - so
Wow. Good, don't do anything ... I'll reach out to you directly.
On Thu, Aug 8, 2013 at 3:20 PM, Luke Bigum luke.bi...@lmax.com wrote:
On Thursday, August 8, 2013 2:14:33 PM UTC+1, Ken Barber wrote:
I think that's just me being too sensorship heavy and abusing copy and
paste, I would have
for this yet, and are still looking. FWIW, this
is the first time I've seen this behaviour.
On Thu, Aug 8, 2013 at 3:22 PM, Ken Barber k...@puppetlabs.com wrote:
Wow. Good, don't do anything ... I'll reach out to you directly.
On Thu, Aug 8, 2013 at 3:20 PM, Luke Bigum luke.bi...@lmax.com wrote
board on Trello:
http://links.puppetlabs.com/puppetdb-trello
## PuppetDB 1.4.0 Release Notes ##
Notable features and improvements:
* (#21732) Allow SSL configuration based on Puppet PEM files (Chris
Price Ken Barber
Check your /etc/puppetdb/conf.d/jetty.ini file for the configuration
items ssl-host host. These should both be set to the IP address you
want PuppetDB to listen on, or 0.0.0.0 for all IP addresses. This is
probably set to 127.0.0.1 or something now, which might explain why
PuppetDB is not
Well, it seems puppet config print is useless as it is incorrect with most
values it shows. I know storeconfigs are up and running and I think its
going to puppetdb. I am still having issues with my mod.
How do you know? The previous error you posted Not collecting
exported resources without
Also, you are right about my typo with manifests instead of manifest.
Sometimes I guess you just need a second set of eyes!
Ain't that the truth.
It didn't error out,
but changing that and it looks like my module with storeconfigs is now
working. Thank you!!!
Oh good to hear :-). Do you
You should be able to use 'curl' to access the API, there are some
examples for /v2/nodes in the docs as a start ... and the rest of the
end-points have similar examples:
http://docs.puppetlabs.com/puppetdb/1.3/api/query/v2/nodes.html
Also take a look at the general curl advice page:
Looks like a fault with pgpool specifically. The PuppetDB error is
just an effect of a forced disconnection. Perhaps you need to reach
out to the pgpool/postgresql mailing lists for advice?
I can certainly help with PuppetDB related items, but if pgpool is
segfaulting I'm pretty sure its a bug on
I have a standard Puppet 2.7 configuration installed from Gem on Ubuntu
12.04, running behind Apache.
I'm testing the reprovisioning of the puppet master from scratch in Vagrant
and ran into a little snug - apache configuration points to a puppet
ca_crl.pem file which doesn't exist, so
If it helps I did a bit of a Gist walkthrough of the full cert
recreation etc. using puppet cert generate here:
https://gist.github.com/kbarber/5934100 ...
On Fri, Jul 5, 2013 at 1:00 PM, Ken Barber k...@puppetlabs.com wrote:
I have a standard Puppet 2.7 configuration installed from Gem
Was a ticket ever opened for this? I've just run into the same issue, but
searching the ticket database I'm not able to find anything already open for
it... I'll submit a ticket if there isn't one already.
Not sure whats going on, but this seems to work fine for Puppet 3.2.2:
# cat
* The ports that all nodes share in common I am adding to the
modules/my_firewall/manifests/init.pp file, but the ports that are specific
to a node I am adding to the node definition in manifests/site.pp. What
should I do to prevent the firewall rules from becoming unwieldy in my
site.pp
The output for this task is returns: executed successfully. But the
server hasn't been started and when I look at the directory, it's clear that
the build and compile haven't even been run. Is it obvious to anyone why
this exec step says it's finished but doesn't seem to have done?
The
I am very new to puppet and wants to implement something like this in my
puppet template (erb file)
the logic i am trying to do is :
sssd_count=`rpm -qa | grep 'sssd' | wc -l`
% if sssd_count =2 -%
session optional sss.so
% else %
session optional pam_ldap.so
% end
You mean the Freenode IRC channel #puppet? It looks like it - whats
the problem you are having?
ken.
On Mon, Jun 24, 2013 at 1:30 PM, Dan White y...@comcast.net wrote:
Is the puppet IRC channel up and working or is it just me ?
“Sometimes I think the surest sign that intelligent life exists
I'm in the process of upgrading my puppet from 2x to 3.2.1.
During my testing i found that it appears that puppet node deactivate isn't
removing nodes from storeconfigs.
So it should work and in my experience it often does. Most cases I
hear about this failing is when the Puppet code you are
Although I agree that to be reusable, modules need to provide certain types
of levers, knobs, and switches, as appropriate for their scopes, I think the
case is weak for those controls needing to be called by the same names. At
best, naming conventions for such things might improve ease of
Looks to me like there is only 1 provider for that module, and its
confined to osfamily 'RedHat':
https://github.com/wavesoftware/puppet-glassfish/blob/master/lib/puppet/provider/domain/el.rb#L6-L7
ken.
On Wed, Jun 12, 2013 at 12:29 PM, Kobe Nys k...@allnice.be wrote:
Hello,
My newb question
Implement database, database_user, and database_grant provider
https://github.com/puppetlabs/puppetlabs-postgresql/issues/27
The bug has been closed and that's a little unsatisfying.
database, database_user and database_grant are resources internal
to puppet, but only puppetlabs-mysql
Seems like to me the SSL loaded into PuppetDB (the port 8081 you
mention) is not valid.
A simple activity would be to use our provided tool to reload the
certificates again:
* Move /etc/puppetdb/ssl to ssl.bak to preserve the original
* Backup /etc/puppetdb/conf.d/jetty.ini to say jetty.ini.bak
What kind of database is this? Postgresql or the built-in HSQLDB? And
- how are you calculating the database size?
On Tue, May 28, 2013 at 12:19 PM, shell heriyanto
shell.heriya...@gmail.com wrote:
no efect, this my configuration:
gc-interval = 60
node-ttl = 30m
node-purge-ttl = 30m
Its probably the nagios resource, its well known for not scaling when
the files contain a lot of entries. That would explain why your
PuppetDB is showing low load - as its probably not the bottleneck.
The most performant work-around I've seen for this is that you can use
the nagios_* resources to
solution around
it eventually.
http://projects.puppetlabs.com/projects/puppetdb/issues/new
BTW, what does your puppet.conf look like?
On Tue, May 21, 2013 at 6:36 AM, kl.puppetu...@gmail.com wrote:
Ken, it's working now! Solution below.
On Fri, May 17, 2013 at 4:27 PM, Ken Barber k
and node_purge_ttl were added
but they are not working, this fixes it (fsalum)
* Also fix gc_interval (Ken Barber)
* Support for remote puppetdb (Filip Hrbek)
* Added support for Java VM options (Karel Brezina)
* Add initial rspec-system tests and scaffolding (Ken Barber)
--
You received this message
I am not sure I did the ssl-setup command again. I started all over
again on the puppetdb. Deleted the package, all the logs and
configuration and reinstalled puppetdb. I included a complete output:
http://pastebin.com/raw.php?i=TDejFAvp
Does this make things more clear? I did a clean
have done that.
Do you know if there is an anticipated 1.3.1 release for puppetdb? I haven't
seen any mention of what the next release is going to be.
On May 15, 2013, at 7:06 AM, Ken Barber k...@puppetlabs.com wrote:
Justin,
Take a look at this: http://projects.puppetlabs.com/issues/19884
/ssl and re-ran
puppetdb-ssl-setup didn't you? This action should be enough to restore
the correct key in keystore.jks.
ken.
On Wed, May 15, 2013 at 11:56 AM, kl.puppetu...@gmail.com wrote:
Hi Ken, thanks for your reply,
On Tue, May 14, 2013 at 5:08 PM, Ken Barber k...@puppetlabs.com wrote:
Can
Justin,
Take a look at this: http://projects.puppetlabs.com/issues/19884
My colleague Deepak produced a patch for this problem and it has been
merged in, but its not yet released. In the meantime you can
work-around the problem by downgrading to JDK 1.6, which seems to do
the trick.
ken.
On
:
Any idea on how I can do debugging?
Tried re-installing several times now. I'd like to be able to find out where
the problem lies.
Thanks,
kl
On Friday, May 10, 2013 2:11:09 PM UTC+2, Ken Barber wrote:
How did you setup your SSL certificates? You didn't mention a manual
certificate
How did you setup your SSL certificates? You didn't mention a manual
certificate setup. Perhaps you can get away with just re-initializing
your certificates using 'puppetdb-ssl-setup'? Just backup your
/etc/puppetdb/ssl directory first, and then remove it and re-run the
tool and see if that helps:
Today, you can't replace the database that puppet dashboard uses for
PuppetDB, sorry. You will need to configure Puppet Dashboard as per
normal, using mysql or whatever.
The only feature today that PuppetDB replaces in Dashboard is
Inventory Services, that is - storage of facts for node. This
Let me get this straight ... so you want to be able to query PuppetDB
for what 'node' match propagated that nodes configuration right?
So in the case of 'app3.example.com' you want to be able to find it by
looking for app\d+\.example\.com for example? Or you want to see all
nodes that matches
for 1 node search case due to lack of uniqueness. Sorry about
that :-).
On Fri, May 10, 2013 at 1:54 PM, Ken Barber k...@puppetlabs.com wrote:
Let me get this straight ... so you want to be able to query PuppetDB
for what 'node' match propagated that nodes configuration right?
So in the case
Hi Jeffrey,
It is a 'bug', and a known one at that:
http://projects.puppetlabs.com/issues/17523
Feel free to watch/vote for it.
ken.
On Wed, May 8, 2013 at 7:04 PM, Jeffrey Watts jeffrey.w.wa...@gmail.com wrote:
I'm setting up PuppetDB for the first time (and on OpenSuSE, yay). After
some
Are you running version 7 of the JDK? We believe this was a bug
introduced during a CVE fix into a minor revision of Java 7:
http://projects.puppetlabs.com/issues/19884
If you downgrade to JDK 6 the issue should disappear.
ken.
On Thu, May 2, 2013 at 11:32 AM, Martijn mart...@heemels.com
)
* Allow to set connection for noew role (Kamil Szymanski)
* Fix pg_hba_rule for postgres local access (Kamil Szymanski)
* Fix versions for travis-ci (Ken Barber)
* Add replication support (Jordi Boggiano)
* Cleaned up and added unit tests (Ken Barber)
* Generalization to provide more flexability
Lets take a look at the following files on your puppetmaster:
/etc/puppet/puppet.conf
/etc/puppet/puppetdb.conf
/etc/puppet/routes.yaml
/etc/puppet/auth.conf
On the dashboard:
/usr/share/puppet-dashboard/config/settings.yml (at least thats the
normal path for our package on RHEL 6)
And on your
You can deactivate nodes with the instructions here on your Puppet master:
http://docs.puppetlabs.com/puppetdb/1.2/maintain_and_tune.html#deactivate-decommissioned-nodes
This will deactivate them, which means they should no longer be used
during exported resource collection. You can do this from
A new release of the puppetlabs/puppetdb module is now available on the Forge:
http://forge.puppetlabs.com/puppetlabs/puppetdb/1.2.1
This is a bugfix releases that solves the PuppetDB startup exception:
java.lang.AssertionError: Assert failed: (string? s)
This was due to the default `node-ttl`
A new release of the puppetlabs/puppetdb module is now available on the Forge:
http://forge.puppetlabs.com/puppetlabs/puppetdb/1.2.0
This release is primarily about providing full configuration file
support in the module for PuppetDB 1.2.0. (The alignment of version is
a coincidence I assure you
I have installed all of this so far using the puppetlabs repository and have
had some amount of success, even though the tools seem to be full of
configuration bugs (the ssl config scripts do NOT work correctly, I had to
manually regenerate all of the certificates, keystore truststore
Yeah, sounds like a bug Michael or at least something we can improve
upon - DNS is case insensitive: https://tools.ietf.org/rfc/rfc4343.txt
- but to make things more complex you can override what the node name
is in Puppet (ie. node_name_fact and node_name_value), so I can only
imagine the fun
the agent's certs (signed by the same CA) worked.
On Tue, Apr 2, 2013 at 3:40 PM, Ken Barber k...@puppetlabs.com wrote:
If you specify 'certname' it will use the local certificate with that
name as apposed to using the certificate with the same name as the
boxes fqdn (ie. facter fqdn
I am trying to use this module, but I think I am missing something in the
setup.
From https://github.com/puppetlabs/puppetlabs-firewall it says:
With the latest version, we now have in-built persistence, ...you need some
basic setup to define pre post rules.
resources { firewall:
/alcy/5283712.
On Fri, Mar 29, 2013 at 3:14 AM, Ken Barber k...@puppetlabs.com wrote:
Yeah, it does seem very odd though ... if agent works - and the master
is able to talk to PuppetDB no problem, then its weird that running
puppet master on the command line doesn't seem to work.
What
This is me installing a puppetmaster for Ubuntu with the bog-standard
apt repos the other day - took less than 5 minutes:
https://gist.github.com/kbarber/5209267
As you can see it was pretty straight-forward (apt-get install
puppetmaster-passenger, more or less) - note this was a clean Ubuntu
So I have some questions, as the error could mean a number of things:
What version of PuppetDB are you running? And what exact version of
Java is it using?
Can you take a look at puppetdb.log and tell me if you see any
meaningful error messages?
Without trying to compile a catalog in this
, is there a ~/.puppet directory for that user at all?
ken.
On Thu, Mar 28, 2013 at 1:17 PM, Mohit Chawla
mohit.chawla.bin...@gmail.com wrote:
Hello Ken,
Thanks for the response.
On Thu, Mar 28, 2013 at 6:42 PM, Ken Barber k...@puppetlabs.com wrote:
So I have some questions, as the error could mean
at these masters). And afaik
right now, there wasn't any ~/.puppet dir for root, however I need to
confirm this.
On Thu, Mar 28, 2013 at 7:07 PM, Ken Barber k...@puppetlabs.com wrote:
I'm just trying to run up the same environment so I can try to
replicate it, as yet I can't replicate it on the newer
now been re-enabled with a fix for the regression. Can you try
upgrading to 1.0.1-4ubuntu5.8 (combined with openjdk-7) to see if this
helps?
ken.
On Mon, Mar 25, 2013 at 1:59 PM, Ken Barber k...@puppetlabs.com wrote:
Thanks Hugh, can you confirm if switching to openjdk-6 fixes it?
On Mon, Mar 25
Try:
curl -vv -G -H Accept: application/json
'http://localhost:8080/v2/commands' --data-urlencode
'payload={command:deactivate node,version:
1,payload:\yournodename\}'
The command needs to be submitted with the form parameter 'payload'.
The 'payload' part of the command is itself a JSON
Here is a better working example as a gist, with what you should see
in the puppetdb.log if it was successful:
https://gist.github.com/kbarber/5254512
On Wed, Mar 27, 2013 at 2:19 PM, Ken Barber k...@puppetlabs.com wrote:
Try:
curl -vv -G -H Accept: application/json
'http://localhost:8080/v2
Puppet (err): Could not retrieve catalog from remote server: execution
expired
Puppet (notice): Using cached catalog
/File[/etc/security/http/key.pem] (err): Could not evaluate: SSL_connect
SYSCALL returned=5 errno=0 state=SSLv2/v3 read server hello A Could not
retrieve file metadata for
Thanks Hugh, can you confirm if switching to openjdk-6 fixes it?
On Mon, Mar 25, 2013 at 1:35 PM, Hugh Cole-Baker h...@fanduel.com wrote:
I've filed a bug report http://projects.puppetlabs.com/issues/19884 with
some info on the OpenJDK / Ruby / OpenSSL versions we're using.
--
You received
Russel: Can you confirm the same error message that Hugh is receiving
in your own puppetdb.log?
Hugh: I'd suggest raising a bug with all the details:
http://projects.puppetlabs.com/projects/puppetdb/issues/new ...
Russell, if the problem looks the same I'd confirm it in the same
ticket so we can
. As Ken
mentioned, it would be most helpful if we could get the Ruby/OpenSSL/JDK
versions from your masters and puppetdb servers. Thanks!
On Sat, Mar 23, 2013 at 2:04 AM, Ken Barber k...@puppetlabs.com wrote:
Russel: Can you confirm the same error message that Hugh is receiving
in your own
Hi ak0ska,
How are things going? Anything to report?
ken.
On Fri, Mar 15, 2013 at 5:00 AM, Ken Barber k...@puppetlabs.com wrote:
Hi ak0ska,
FWIW - with the help of some of my colleagues we've managed to
replicate your constraint issue in a lab style environment now:
https
you ask for. However, I feel like I should ask,
whether you think this problem is worth your efforts, if rebuilding the
database might solve the issue?
Cheers,
ak0ska
On Thursday, March 14, 2013 8:05:59 AM UTC+1, Ken Barber wrote:
Hi ak0ska,
So I've been spending the last 2 days trying
Hey all,
I'm hoping I can get some information from other users on the list in
relationship ak0ska's problem listed below. I thought I would start a
new thread so more users would see this message and not loose it in
the original thread which is already pretty long:
way with PuppetDB
directly, so the statement log will still be helpful if you can supply
it.
ken.
On Thu, Mar 14, 2013 at 2:12 PM, Ken Barber k...@puppetlabs.com wrote:
So I have this sinking feeling that all of your problems (including
the constraint side-effect) are related to general
I think most people are implementing either an Apache or NGinx proxy
in front of PuppetDB for this purpose.
For Apache, should be pretty easy to do with proxy based RewriteRule's
in Apache, and within the same virtualhost definition you should be
able to enforce authentication. For example:
ProxyPass / http://localhost:8080/
Location /
AuthType basic
AuthName Restrited Files
AuthBasicProvider file
AuthUserFile /etc/apache2/passw
Require valid-user
/Location
/VirtualHost
On Tuesday, March 12, 2013 10:40:01 AM UTC-7, Ken Barber wrote:
I think most
After dropping the obsolete index, and rebuilding the others, the database
is now ~ 30 GB. We still get the constraint violation errors when garbage
collection starts.
Okay - can you please send me the puppetdb.log entry that shows the
exception? Including surrounding messages?
Also the
A new release of the puppetlabs/puppetdb module is now available on the Forge:
http://forge.puppetlabs.com/puppetlabs/puppetdb/1.1.5
This is a minor bug-release.
Changelog
2013-02-13 - Karel Brezina
* Fix database creation so database_username, database_password and
database_name are
Indexes seem bloated.
Totally agree, you should organise re-indexes starting from the biggest.
relation | size
-+-
public.idx_catalog_resources_tags_gin | 117 GB
public.idx_catalog_resources_tags | 96
It sounds like the dashboard Javascript can't access the HTTP
end-points which is strange. The way it works is that it hits a series
of REST end-points on the web server.
As the dashboard is updated using background Javascript, it can still
keep trying to access backend data even though the web
Vacuum full was running for the whole weekend, so we didn't yet have time to
rebuild indexes, because that would require more downtime, and we're not
sure how long it would take. The size of the database didn't drop that much,
it's now ~370Gb.
Wow. Thats still way too large for the amount of
Any progress today?
On Fri, Mar 1, 2013 at 9:00 AM, ak0ska akos.he...@gmail.com wrote:
Yes, maybe not. The next step will be to recreate it from scratch.
On Friday, March 1, 2013 5:47:06 PM UTC+1, Ken Barber wrote:
Well, I don't think a vacuum will help you - I imagine something is
wrong
is would be handy.
I can organise a secure space on a Puppetlabs support storage area to
upload this data if you are willing. Just contact me privately to
organise it.
ken.
On Fri, Mar 1, 2013 at 2:25 PM, Ken Barber k...@puppetlabs.com wrote:
So I've been pondering this issue of yours, and I keep
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
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
seems
] [replace catalog] puppetdb2.vm
If at all possible - I wouldn't mind a full copy of your puppetdb.log
... to dig a bit deeper. And I know I told you to clear the KahaDB
queue (I always make this mistake) but I don't suppose you kept an old
copy of it?
ken.
On Thu, Feb 28, 2013 at 3:55 PM, Ken Barber k
the
`include` directive in `postgresql.conf` was not compatible. As a
work-around we have added checks in our code to make sure systems
running PostgreSQL 8.1 or older do not have this directive added.
Detailed Changes
2013-01-21 - Ken Barber k...@bob.sh
* Only install `include` directive
I do this kind of thing here:
https://github.com/puppetlabs/puppetlabs-kwalify/blob/master/lib/puppet/parser/functions/validate_resource.rb#L24
ken.
On Fri, Feb 22, 2013 at 6:05 PM, Matt W m...@nextdoor.com wrote:
I'm trying to create a function that I can call in a manifest like this:
So for anyone running RHEL or Centos 5, we've found a bug - but
already have a fix for you all in master:
https://github.com/puppetlabs/puppet-postgresql/issues/130
We'll do a follow up minor release soon to cover this. Thanks!
ken.
On Wed, Feb 20, 2013 at 6:02 PM, Ken Barber k
of the module.
2013-01-31 - jv j...@jeffvier.com
* Fix typo in README.pp for postgresql::db example
2013-02-03 - Ken Barber k...@bob.sh
* Add unit tests and travis-ci support
2013-02-02 - Ken Barber k...@bob.sh
* Add locale parameter support to the 'postgresql' class
2013-01-21 - Michael Arnold git
My biggest concern is that nodes can access other nodes resources stored
in
PuppetDB, which effectively means that parameters like passwords and
other
sensitive information is exposed.
If the data is not exported this shouldn't be the case ordinarily.
It actually is the case. For
My biggest concern is that nodes can access other nodes resources stored in
PuppetDB, which effectively means that parameters like passwords and other
sensitive information is exposed.
If the data is not exported this shouldn't be the case ordinarily.
Obviously though if your content is
Hi all,
I've been looking at a potential problem, as documented here:
http://projects.puppetlabs.com/issues/19241
To do with a leak within the KahaDB persistence layer of ActiveMQ.
Specifically, there are reports of the db.data file growing unbounded:
201 - 300 of 515 matches
Mail list logo
