[Puppet Users] Re: Changes to module not picked up by agent

[Chris Price]

Can you check the value of 'environment_timeout' in your puppet.conf and/or 
environment.conf files?  If that is set to anything other than zero, this 
might be expected behavior.  There is an HTTP API that you can use to clear 
the environment cache if you need to:

https://docs.puppet.com/puppetserver/latest/admin-api/v1/environment-cache.html


On Thursday, August 18, 2016 at 10:51:05 AM UTC-7, mike r wrote:
>
> restarted pe-puppetserver seems to clear cache on master, and the node got 
> the updated version. But if I make any other changes to my modules, node 
> isnt getting the updated catalog, its using cached version again.
>
>
> Master running on Ubuntu 14.04  puppet 4.5.2
> node running on centos7 puppet 4.5.2
>
>
>
>
> On Thursday, August 18, 2016 at 12:32:12 PM UTC-4, mike r wrote:
>>
>> Im trying to run an Nginx module, my install.pp has the following line
>>
>>
>>
>> $agent_version = $::puppetversion
>>   
>> #  if $agent_version < 3.8 {
>> #fail(" Node ${::fqdn} has a Puppet agent version: 
>> ${agent_version} which is not compatible with this module. Need to have 
>> minimum Puppet agent 3.8 -")
>>  # }
>>  
>> the IF statement is commented out, yet when I run agent on target, it 
>> looks like its cached the old version of the manifest, it still tries to do 
>> the IF statement
>>
>> [root@centos7node state]# puppet agent -t
>> Info: Using configured environment 'production'
>> Info: Retrieving pluginfacts
>> Info: Retrieving plugin
>> Info: Loading facts
>> Error: Could not retrieve catalog from remote server: Error 400 on 
>> SERVER: Evaluation Error: Error while evaluating a Resource Statement, 
>> Evaluation Error: *Error while evaluating a Function Call,  Node 
>> centos7node has a Puppet agent version: 4.5.2 which is not compatible with 
>> this module. Need to have minimum Puppet agent 3.8 - at 
>> /etc/puppetlabs/code/environments/production/modules/nginx/manifests/install.pp:18:3
>>  
>> on node centos7node*
>> Warning: Not using cache on failed catalog
>> Error: Could not retrieve catalog; skipping run
>>
>>
>>
>> Not sure where the caching is occuring, on Master or Agent, Im guessing 
>> on master. Any way to clear the cache on both ends? Didnt see anything in 
>> docs. 
>>
>>
>>

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/e71f414c-117f-4df0-b512-f47ae5349bc5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] [ANN] Puppet Server 2.5.0 is available

[Chris Price]

Hi!  We’re happy to announce the new 2.5.0 release of Puppet Server.  This
is a backward compatible feature release that also contains a few bug
fixes.  Highlights include:


   -

   New workflows for certificate signing and authentication, based on
   improved support for X.509 authorization extensions
   -

   A more flexible layout for managing the bootstrapping of the services
   required to run the server, to provide a better upgrade UX in future
   releases (*please see the NOTE below*, especially if you are managing
   your bootstrap.cfg file and/or have disabled the CA service on any of your
   servers)
   -

   Bug fixes related to errant warning messages when running `puppetserver
   gem`, and empty PID files upon installation on EL6


Release notes with more info on all of the above can be found here:

https://docs.puppet.com/puppetserver/latest/release_notes.html#puppet-server-25

NOTE: If you plan to upgrade from a previous version of Puppet Server, and
if you are managing your `bootstrap.cfg` file via Puppet module or other
means (e.g. to disable the CA service on compile masters), please read
the release
notes

and the detailed notes on bootstrap upgrades
prior
to upgrading.

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAMx1Qf%2BhAaMHU0HpS%3DeBmufiuNa4ktZNPtyBMcyROXhTZu9igQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Additional Puppet Server Failure

[Chris Price]

On Monday, February 22, 2016 at 5:01:20 PM UTC-8, Matthew Ceroni wrote:
>
> I have the following setup.
>
> 1) Existing PuppetServer version 1.1.3 
>
> 2) New PuppetServer version 1.1.3 installation (new DC)
>
> I followed the following documentation on setting up multiple Puppet 
> Masters 
>
>
> https://docs.puppetlabs.com/guides/scaling_multiple_masters.html#option-1-direct-agent-nodes-to-the-ca-master
>
> Essentially I pre-generated the SSL certificate for the new puppet server 
> from the existing puppet server, instead of letting the puppet server 
> generate it on startup. 
>
> A new node checks in and contacts server 1 (pre-existing Puppet server) 
> for CA functions (configured via ca_server in puppet.conf). Certificate 
> generates and node caches it. However, the puppet run (which runs against 
> the new puppet server) generates the following error:
>
> Warning: Unable to fetch my node definition, but the agent run will 
> continue:
>
>  
>
> Warning: SSL_connect SYSCALL returned=5 errno=0 state=SSLv3 read finished 
> A 
>
> Info: Retrieving pluginfacts 
>
> Error: /File[/var/lib/puppet/facts.d]: Failed to generate additional 
> resources using 'eval_generate': SSL_connect SYSCALL returned=5 errno=0 
> state=SSLv3 read finished A 
>
> Error: /File[/var/lib/puppet/facts.d]: Could not evaluate: Could not 
> retrieve file metadata for puppet://aws-puppet-01.xx.com/pluginfacts: 
> SSL_connect SYSCALL returned=5 errno=0 state=SSLv3 read finished A 
>
> Info: Retrieving plugin 
>
> Error: /File[/var/lib/puppet/lib]: Failed to generate additional 
> resources using 'eval_generate': SSL_connect SYSCALL returned=5 errno=0 
> state=SSLv3 read finished A 
>
> Error: /File[/var/lib/puppet/lib]: Could not evaluate: Could not retrieve 
> file metadata for puppet://aws-puppet-01.xx.com/plugins: SSL_connect 
> SYSCALL returned=5 errno=0 state=SSLv3 read finished A 
>
> Info: Loading facts 
>
> Error: Could not retrieve catalog from remote server: SSL_connect SYSCALL 
> returned=5 errno=0 state=SSLv3 read finished A 
>
> Notice: Using cached catalog 
>
> Error: Could not retrieve catalog; skipping run 
>
> Error: Could not send report: SSL_connect SYSCALL returned=5 errno=0 state
> =SSLv3 read finished A
>
>
> If I point the node at the other puppet server it runs fine. 
>
>
> I have verified that the certificate being used on the new puppet server 
> is in fact signed by the same CA that generates the node certificate and 
> the certificate used on the pre-existing puppet server. I can also connect 
> to the new Puppet server via OpenSSL and issue a simple HTTP GET command 
> (don't know a valid get request so end up with a 404 response, but it shows 
> the certificate is setup correctly).
>

Are you using the agent's certs/key when you make this connection via 
openssl?  Can you include the syntax of the command you're running for 
this?  Have you tried with curl?  e.g.

curl --cacert $ssldir/certs/ca.pem --cert $ssldir/certs/agent-node.pem 
--key $ssldir/private_keys/agent-node.pem 
https://new-puppet-master:8140/production/nodes/agent-node

Also, are there any log messages in the puppetserver.log file?  If not, 
perhaps try editing the 'logback.xml' config file and changing the log 
level from info/warn to 'debug', and then see if any log messages appear?

My best guess at the moment is that either:
* the new puppet server's cert is not signed by the same CA, or,
* the certname of the puppet server cert does not match the hostname that 
the agent is using to try to connect to it
 

>
> Also, I have disabled CA services on the second puppetserver as it is not 
> providing CA capabilities. 
>

How did you go about doing this?
 

>
> As a test I removed the SSL certificates and started up Puppetserver fresh 
> on the new server, that way it generated the CA certificates, etc.
>

If the new puppet server instance is generating its own CA cert, then its 
CA is not disabled, and its CA cert will not be compatible with the CA cert 
from the original puppet server.  The steps I'd recommend:

1. shut down puppet server on the new puppet server host
2. make sure that its CA is disabled ( 
https://docs.puppetlabs.com/puppetserver/latest/external_ca_configuration.html#disabling-the-internal-puppet-ca-service
 
)
3. set up the puppet agent on the new puppet server host; configure it to 
connect to the old puppet server as its master
4. do an agent run on the new puppet server host; this will cause it to 
request a cert from the old puppet server CA
5. once you've signed that cert and are able to complete your agent runs 
successfully on the new puppet server host, it should have valid certs in 
place
6. start puppet server back up on the new puppet server host; it should 
find the certs that were generated by the agent and use them
7. now try running an agent on a different host, pointed at your new puppet 
server.

 

> A node then successfully checks in, gets a certificate and can apply a 
> manifest. This 

[Puppet Users] Re: Puppet Server Crashing often

[Chris Price]

On Wednesday, December 16, 2015 at 4:26:26 AM UTC-8, Makrand Sanap wrote:
>
> Hi All,
>
> I am doing POC for puppet enterprise. Master is on CentOS 6.4 VM with 2GB 
> ram. Puppet server is going down on its own. 
>
> [root@mss-pup-mst2 ~]# /etc/init.d/pe-puppetserver status
>> pe-puppetserver dead but pid file exists
>>
>
>
> I can start it without any issues, but it stays for like 30-60 Mins up. 
> then It goes down again.
>
> Logs are not hinting anything, but for one of shutdown, I found following 
> lines. Surprisingly they appeared for only one shutdown incident. Not for 
> others
>
> 2015-12-13 04:38:21,100 INFO  [p.t.internal] Shutting down due to JVM 
>> shutdown hook.
>> 2015-12-13 04:38:21,363 INFO  [p.t.internal] Beginning shutdown sequence
>> 2015-12-13 04:38:21,640 INFO  [p.e.s.j.pe-jruby-metrics-service] PE JRuby 
>> Metrics Service: stopping metrics sampler job
>> 2015-12-13 04:38:21,990 INFO  [p.e.s.j.pe-jruby-metrics-service] PE JRuby 
>> Metrics Service: stopped metrics sampler job
>> 2015-12-13 04:38:22,724 INFO  [p.t.s.w.jetty9-service] Shutting down web 
>> server(s).
>> 2015-12-13 04:38:22,808 INFO  [p.t.s.w.jetty9-core] Shutting down web 
>> server.
>> 2015-12-13 04:38:23,243 INFO  [o.e.j.s.ServerConnector] Stopped 
>> ServerConnector@4369ad74{SSL-HTTP/1.1}{0.0.0.0:8140}
>> 2015-12-13 04:38:23,262 INFO  [o.e.j.s.h.ContextHandler] Stopped 
>> o.e.j.s.h.ContextHandler@3749adc6{/status,null,UNAVAILABLE}
>>
>
This is very unusual, I would not expect for you to see the message "Shutting 
down due to JVM shutdown hook" unless something on your system sent a 
signal to the service to stop or restart.

I presume you have a Puppet agent running on the same node; can you check 
its report and see if it shows anything about it trying to restart Puppet 
Server?  Or maybe try disabling the agent (`service puppet stop`) for a 
period of time and see if the weird behavior of the server only occurs when 
the agent is running?

 

>
>
> After bit of googling, I found following
>
>
> https://github.com/puppetlabs/puppet-server/blob/master/documentation/install_from_packages.markdown#memory-allocation
>
> Thing is, I am not able to find  init file under 
> /etc/sysconfig/puppetserver
> to ask Puppetserver to use less RAM than 2GB. (This proabably seems reason 
> for this)
>
> Do anyone know, where I can set the RAM usage for puppetserver (PE 
> 2015.2.3)?
>
> -- 
> Best,
> Makrand
>
>

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/59958791-b989-484e-add0-09d7298eb328%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Puppet Server dying with high number of JRuby instances

[Chris Price]

Stefan,

That is a very weird error.  The way it reads it sounds like something that 
should happen on every JRuby instance or on none of them 
(NoClassDefFoundError usually means it's trying to load some code that 
doesn't exist), so I wouldn't expect you to see a difference in behavior 
between 16 instances and 32 instances.

It might be best if you open a bug about this on our issue tracker: 
https://tickets.puppetlabs.com/browse/SERVER , so that we can get some 
other folks to weigh in on it... would you mind doing that?

On Tuesday, August 25, 2015 at 12:05:54 PM UTC+1, Dietrich, Stefan wrote:

 Hello, 

 we tried to today to migrate our Puppet Masters from Apache/Passenger to 
 Puppet Server 1.1.1. 
 However, Puppet Server just dies with error messages as soon as we 
 increase the number of JRuby instances to 24 and a JVM heapsize of  16GB. 

 During startup of Puppet Server, it starts to spawn the JRuby instances 
 one after another and around ~8 instances an exception is logged: 
 2015-08-25 10:25:05,676 INFO  [puppet-server] Puppet Puppet settings 
 initialized; run mode: master 
 2015-08-25 10:25:06,254 INFO  [p.s.j.jruby-puppet-agents] Finished 
 creating JRubyPuppet instance 7 of 32 
 2015-08-25 10:25:08,567 ERROR [p.t.internal] shutdown-on-error triggered 
 because of exception! 
 java.lang.IllegalStateException: There was a problem adding a JRubyPuppet 
 instance to the pool. 
 Caused by: org.jruby.embed.EvalFailedException: (LoadError) load error: 
 jopenssl/load -- java.lang.NoClassDefFoundError: 
 org/jruby/ext/openssl/NetscapeSPKI 
 at 
 org.jruby.embed.internal.EmbedEvalUnitImpl.run(EmbedEvalUnitImpl.java:132) 
 ~[puppet-server-release.jar:na] 
 at 
 org.jruby.embed.ScriptingContainer.runUnit(ScriptingContainer.java:1341) 
 ~[puppet-server-release.jar:na] 

 The full log file is available in this Gist [1]. 
 The log file is from the initial setup with max-active-instances set to 32 
 and a JVM heap size of 48gb. 
 We had a working setup with 16GB Heap and 16 instances. Sometimes 24 
 worked as well, but not always. 
 However, 16 instances will be too small to handle all the Puppet agents. 
 Increasing the timeout in /etc/sysconfig/puppetserver did not help either. 

 We use rather beefy HW for our 3x Puppet Masters (2x Dell R715, 1x R815), 
 for Apache/Passenger this scaled nicely. 

 The OS on the Puppet Masters is Scientific Linux 6.6 (RHEL 6.6 clone) and 
 OpenJDK 8 is used. 
 We tried the Oracle JRE as well, but this did not change anything. 
 HTTPS is terminated at our F5 Loadbalancer, which forwards the traffic 
 unencrypted to Puppet Server. 

 Any help would be appreciated! 

 [1] https://gist.github.com/stdietrich/5a5b8f9b1dc2445c3ec7 

 Regards, 
 Stefan 

 -- 
  
 Stefan DietrichDeutsches Elektronen-Synchrotron (IT-Systems) 
 Ein Forschungszentrum der Helmholtz-Gemeinschaft 
 Notkestr. 85 
 phone:  +49-40-8998-4696   22607 Hamburg 
 e-mail: stefan@desy.de javascript: 
  Germany 
  


-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/f38505c9-8793-45d4-bee0-1aa0f45bdf94%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Puppet master on Windows

[Chris Price]

On Monday, December 29, 2014 1:52:41 PM UTC-8, Alejandro del Castillo wrote:

 Hello,

 We are looking at the different options out there to build a System 
 Management solution for embedded systems. I am encouraged by the fact that 
 puppet support opkg and it's already in use by OpenWRT (we build our own 
 distribution, but it's opkg-based). Digging/experimenting around with 
 puppet, it looks like it can do most of what we want. We would need to 
 write several modules, custom UI, etc, but it looks doable. The only 
 problem is that we absolutely must have Windows support for the host. That 
 is a deal breaker requirement, as many of our customers (unfortunately) 
 will expect Windows on the server side. As I am looking at options, I would 
 like to understand what would be the effort for the Windows port of the 
 server side components (at least puppet master, hiera, possibly puppetDB). 
 I do get that this is not a priority for the community and do understand 
 that if we take this approach, we would be maintaining the Windows server 
 side, which is something that is on the table for us. 


 Alejandro,

Puppet Server and PuppetDB both run on the JVM, so, theoretically they 
might Just Work on Windows.  We don't provide packaging, so you'd 
probably need to just try running them from source. 

Both projects have docs on how to run from source:

https://docs.puppetlabs.com/puppetserver/1.0/dev_running_from_source.html
https://docs.puppetlabs.com/puppetdb/latest/install_from_source.html

Hiera, to some degree, is a kind of plugin that runs inside the server, so 
it should work fine with Puppet Server.

I'm not aware of any efforts to run these apps on Windows, so, your mileage 
may vary... and I'm not aware of it being on our product roadmap to provide 
official support for Windows on the server-side.  That said, I'm not aware 
of any reason why it *shouldn't* work, so would be interested to hear about 
your results if you decide to try it.

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/90266123-78db-4122-aff9-ca2a4faf769f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: PuppetServer Inconsistent Errors

[Chris Price]

On Friday, November 14, 2014 8:52:55 AM UTC-8, Brian Wong wrote:

 I am currently using version 0.4.0 of PuppetServer using the official RPM 
 package on CentOS 7. I am running into an issue where a node's agent runs 
 error out inconsistently. The node's agent run would sometimes successfully 
 complete or give different errors upon other runs. Below are examples of 
 the errors that the agent would report. The errors never show up together 
 but instead are confined to different invocations of the agent run. It may 
 be slightly confusing, but the node where agent runs are performed also 
 happens to be the server which is running PuppetServer as well. I am using 
 Puppet to manage the PuppetServer.

 - one error that would sometimes appear
 Notice: Finished catalog run in 8.08 seconds
 Error: Could not send report: Error 400 on SERVER: Could not create 
 resources for managing Puppet's files and directories in sections 
 [:reporting]: Invalid parameter ensure
 Invalid parameter ensurelogdir = /var/log/puppet 


These errors are very strange.  How frequently would you say that it 
happens?  If you are able to jump on to #puppet-dev in freenode we could 
maybe try to suggest some debugging patches you could apply to the ruby 
code to help us narrow it down. 

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/e311eac6-075b-4a57-bdd3-e50f3f967ab7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Announce: PuppetDB 1.5.2 Available

[Chris Price]

PuppetDB 1.5.2 is now available for download!  This is a maintenance and
bugfix release.

=
## Downloads ##
=

Available in native package format at:
http://yum.puppetlabs.com and http://apt.puppetlabs.com

Puppet module:
http://forge.puppetlabs.com/puppetlabs/puppetdb

Source (same license as Puppet): http://github.com/puppetlabs/puppetdb/

# Documentation (including how to install):
http://docs.puppetlabs.com/puppetdb/1.5

# Issues can be filed at:
http://projects.puppetlabs.com/projects/puppetdb/issues



##  PuppetDB 1.5.2 Release Notes  ##


Notable changes and fixes:

* Improve handling of logfile names in our packaging, so that it's easier to
  integrate with tools like logrotate.

* Better error logging when invoking subcommands.

* Fix bugs in `order-by` support for `facts`, `fact-names`, and `resources`
query endpoints.

* Documentation improvements.

* Add packaging support for Ubuntu `saucy`.

* Add support for PEM private keys that are not generated by Puppet, and
are not
  represented as key pairs.

* Fix inconsistencies in names of `sourcefile` / `sourceline` parameters
when
  using `nodes/node/resources` version of `nodes` endpoint; these were
always
  being returned in the `v2` response format, even when using `/v3/nodes`.

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: [Puppet-dev] Announce: PuppetDB 1.5.0 Available

[Chris Price]

Someone kindly pointed out that the link to the docs in the original
release e-mail was pointing to an older version of the docs.  The correct
link is:

http://docs.puppetlabs.com/puppetdb/1.5



On Tue, Oct 1, 2013 at 10:11 AM, Matthaus Owens matth...@puppetlabs.comwrote:

 Sorry about that. Something went awry in the ship of 1.5.0. We've
 updated the apt repos and 1.5.0 is now there for all of the debian and
 ubuntu flavors. And as Ken said, thanks for letting us know!

 On Tue, Oct 1, 2013 at 3:47 AM, Ken Barber k...@puppetlabs.com wrote:
  Hmm ... thanks for letting us know.
 
  My humblest apologies, we'll get the updates out for those distro
  releases ASAP. As Daniele mentioned, on apt.puppetlabs.com it seems
  only lucid is available now, the others releases are missing.
 
  ken.
 
  On Tue, Oct 1, 2013 at 9:56 AM, Daniele Sluijters
  daniele.sluijt...@gmail.com wrote:
  It's not just the Precise packages that are missing. The complete Debian
  suite is missing too, squeeze, wheezy, jessy and sid.
 
 
  On Tuesday, 1 October 2013 04:59:16 UTC+2, blkperl wrote:
 
  No packages for precise/raring? Its missing debs for 1.5.0. Lucid seems
  fine
 
  Thanks,
  William
 
 
  On Mon, Sep 30, 2013 at 4:56 PM, Chris Price ch...@puppetlabs.com
 wrote:
 
  PuppetDB 1.5.0 is now available for download!  This is a new feature
  release that contains a few bug-fixes as well.
 
  =
  ## Downloads ##
  =
 
  Available in native package format at:
  http://yum.puppetlabs.com and http://apt.puppetlabs.com
 
  Puppet module:
  http://forge.puppetlabs.com/puppetlabs/puppetdb
 
  Source (same license as Puppet):
 http://github.com/puppetlabs/puppetdb/
 
  # Documentation (including how to install):
  http://docs.puppetlabs.com/puppetdb/1.5
 
  # Issues can be filed at:
  http://projects.puppetlabs.com/projects/puppetdb/issues
 
 
  
  ##  PuppetDB 1.5.0 Release Notes  ##
  
 
  Notable features and improvements:
 
  * (#21520) Configuration for soft failure when PuppetDB is unavailable
 
This feature adds a new option 'soft_write_failure' to the puppetdb
configuration.  If enabled the terminus behavior is changed so that
 if
  a
command or write fails, instead of throwing an exception and causing
  the agent
to stop it will simply log an error to the puppet master log.
 
  * New v3 query API
 
New `/v3` URLs are available for all query endpoints.  The `reports`
  and
`events` endpoints, which were previously considered `experimental`,
  have
been moved into `/v3`.  Most of the other endpoints are 100%
  backwards-compatible
with `/v2`, but now offer additional functionality.  There are few
  minor
backwards-incompatible changes, detailed in the comments about
  individual
endpoints below.
 
  * Query paging
 
This feature adds a set of new HTTP query parameters that can be
 used
  with most
of the query endpoints (`fact_names`, `facts`, `resources`, `nodes`,
  `events`,
`reports`, `event-counts`) to allow paging through large result sets
  over
multiple queries.  The available HTTP query parameters are:
 
   * `limit`: an integer specifying the maximum number of results to
  return.
   * `order-by`: a list of fields to sort by, in ascending or
  descending order.
  The legal set of fields varies by endpoint; see the
 documentation
  for
  individual endpoints for more info.
   * `offset`: an integer specifying the first result in the result
 set
  that
  should be returned.  This can be used in combination with
 `limit`
  and `order-by` to page through a result set over multiple
  queries.
   * `include-total`: a boolean flag which, if set, will cause the
 HTTP
  response
 to contain an `X-Records` header indicating the total number of
  results that are
 available that match the query.  (Mainly useful in combination
  with `limit`.)
 
  * New features available on `events` endpoint
 
  * The `events` data now contains `file` and `line` fields.  These
  indicate
the location in the manifests where the resource was declared.
  They can
be used as input to an `events` query.
  * Add new `configuration-version` field, which contains the value
  that Puppet
supplied during the agent run.
  * New `containing-class` field: if the resource is declared
 inside of
  a
Puppet class, this field will contain the name of that class.
  * New `containment-path` field: this field is an array showing the
  full
path to the resource from the root of the catalog (contains an
  ordered
list of names of the classes/types that the resource is
 contained
  within).
  * New queryable timestamp fields:
  * `run-start-time`: the time (on the agent node) that the run
  began
  * `run-end-time`: the time (on the agent node) that the run
  completed

[Puppet Users] Announce: PuppetDB 1.5.0 Available

[Chris Price]

PuppetDB 1.5.0 is now available for download!  This is a new feature
release that contains a few bug-fixes as well.

=
## Downloads ##
=

Available in native package format at:
http://yum.puppetlabs.com and http://apt.puppetlabs.com

Puppet module:
http://forge.puppetlabs.com/puppetlabs/puppetdb

Source (same license as Puppet): http://github.com/puppetlabs/puppetdb/

# Documentation (including how to install):
http://docs.puppetlabs.com/puppetdb/1.http://docs.puppetlabs.com/puppetdb/1.2
5

# Issues can be filed at:
http://projects.puppetlabs.com/projects/puppetdb/issues



##  PuppetDB 1.5.0 Release Notes  ##


Notable features and improvements:

* (#21520) Configuration for soft failure when PuppetDB is unavailable

  This feature adds a new option 'soft_write_failure' to the puppetdb
  configuration.  If enabled the terminus behavior is changed so that if a
  command or write fails, instead of throwing an exception and causing the
agent
  to stop it will simply log an error to the puppet master log.

* New v3 query API

  New `/v3` URLs are available for all query endpoints.  The `reports` and
  `events` endpoints, which were previously considered `experimental`, have
  been moved into `/v3`.  Most of the other endpoints are 100%
backwards-compatible
  with `/v2`, but now offer additional functionality.  There are few minor
  backwards-incompatible changes, detailed in the comments about individual
  endpoints below.

* Query paging

  This feature adds a set of new HTTP query parameters that can be used
with most
  of the query endpoints (`fact_names`, `facts`, `resources`, `nodes`,
`events`,
  `reports`, `event-counts`) to allow paging through large result sets over
  multiple queries.  The available HTTP query parameters are:

 * `limit`: an integer specifying the maximum number of results to
return.
 * `order-by`: a list of fields to sort by, in ascending or descending
order.
The legal set of fields varies by endpoint; see the documentation
for
individual endpoints for more info.
 * `offset`: an integer specifying the first result in the result set
that
should be returned.  This can be used in combination with `limit`
and `order-by` to page through a result set over multiple queries.
 * `include-total`: a boolean flag which, if set, will cause the HTTP
response
   to contain an `X-Records` header indicating the total number of
results that are
   available that match the query.  (Mainly useful in combination with
`limit`.)

* New features available on `events` endpoint

* The `events` data now contains `file` and `line` fields.  These
indicate
  the location in the manifests where the resource was declared.  They
can
  be used as input to an `events` query.
* Add new `configuration-version` field, which contains the value that
Puppet
  supplied during the agent run.
* New `containing-class` field: if the resource is declared inside of a
  Puppet class, this field will contain the name of that class.
* New `containment-path` field: this field is an array showing the full
  path to the resource from the root of the catalog (contains an ordered
  list of names of the classes/types that the resource is contained
within).
* New queryable timestamp fields:
* `run-start-time`: the time (on the agent node) that the run began
* `run-end-time`: the time (on the agent node) that the run
completed
* `report-receive-time`: the time (on the puppetdb node) that the
report was received by PuppetDB
* Restrict results to only include events that occurred in the latest
report
  for a given node: `[=, latest-report?, true]`

* New `event-counts` endpoint

`v3` of the query API contains a new `event-counts` endpoint, which can
be
used to retrieve count data for an event query.  The basic input to the
endpoint is an event query, just as you'd provide to the `events`
endpoint,
but rather than returning the actual events, this endpoint returns
counts
of `successes`, `failures`, `skips`, and `noops` for the events that
match
the query.  The counts may be aggregated on a per-resource, per-class,
or per-node basis.

* New `aggregate-event-counts` endpoint

  This endpoint is similar to the `event-counts` endpoint, but rather than
  aggregating the counts on a per-node, per-resource, or per-class basis,
  it returns aggregate counts across your entire population.

* New `server-time` endpoint

  This endpoint simply returns a timestamp indicating the current time on
  the PuppetDB server.  This can be used as input to time-based queries
  against timestamp fields that are populated by PuppetDB.

* Minor changes to `resources` endpoint for `v3`

  The `sourcefile` and `sourceline` fields have been renamed to `file` and
`line`,
  for consistency with other parts of the API.

* Minor 

[Puppet Users] Announce: PuppetDB 1.3.2 Available

[Chris Price]

PuppetDB 1.3.2 is now available for download!  This is a very minor
compatibility release for the 1.3 series of PuppetDB.

===
## Downloads ##
===

Available in native package format at:
http://yum.puppetlabs.com and http://apt.puppetlabs.com

Puppet module:
http://forge.puppetlabs.com/puppetlabs/puppetdb

Source (same license as Puppet): http://github.com/puppetlabs/puppetdb/

# Documentation (including how to install):
http://docs.puppetlabs.com/puppetdb/1.http://docs.puppetlabs.com/puppetdb/1.2
3

# Issues can be filed at:
http://projects.puppetlabs.com/projects/puppetdb/issues

# See our development board on Trello:
http://links.puppetlabs.com/puppetdb-trello


##  PuppetDB 1.3.2 Release Notes  ##


Bug fixes:

* Size of column `puppet_version` in the database schema is insufficient

  There is a field in the database that is used to store a string
  representation of the puppet version along with each report.  Previously,
  this column could contain a maximum of 40 characters, but for
  certain builds of Puppet Enterprise, the version string could be
  longer than that.  This change simply increases the maximum length of
  the column.

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Announce: PuppetDB 1.3.1 Available

[Chris Price]

PuppetDB 1.3.1 is now available for download!  This is a bug-fix release
for the 1.3 series of PuppetDB.

=
## Downloads ##
=

Available in native package format at:
http://yum.puppetlabs.com and http://apt.puppetlabs.com

Puppet module:
http://forge.puppetlabs.com/puppetlabs/puppetdb

Source (same license as Puppet): http://github.com/puppetlabs/puppetdb/

# Documentation (including how to install):
http://docs.puppetlabs.com/puppetdb/1.http://docs.puppetlabs.com/puppetdb/1.2
3

# Issues can be filed at:
http://projects.puppetlabs.com/projects/puppetdb/issues

# See our development board on Trello:
http://links.puppetlabs.com/puppetdb-trello


##  PuppetDB 1.3.1 Release Notes  ##


Many thanks to the following
people who contributed patches to this release:

* Chris Price
* Deepak Giridharagopal
* Ken Barber
* Matthaus Owens
* Nick Fagerlund

Bug fixes:

* (#19884) Intermittent SSL errors in Puppet master / PuppetDB communication

  There is a bug in OpenJDK 7 (starting in 1.7 update 6) whereby SSL
  communication using Diffie-Hellman ciphers will error out a small
  percentage of the time.  In 1.3.1, we've made the list of SSL ciphers
  that will be considered during SSL handshake configurable.  In addition,
  if you're using an affected version of the JDK and you don't specify
  a legal list of ciphers, we'll automatically default to a list that
  does not include the Diffie-Hellman variants.  When this issue is
  fixed in the JDK, we'll update the code to re-enable them on known
  good versions.

* (#20563) Out of Memory error on PuppetDB export

  Because the `puppetdb-export` tool used multiple threads to retrieve
  data from PuppetDB and a single thread to write the data to the
  export file, it was possible in certain hardware configurations to
  exhaust all of the memory available to the JVM.  We've moved this
  back to a single-threaded implementation for now, which may result
  in a minor performance decrease for exports, but will prevent
  the possibility of hitting an OOM error.

* Don't check for newer versions in the PE-PuppetDB dashboard

  When running PuppetDB as part of a Puppet Enterprise installation, the
  PuppetDB package should not be upgraded independently of Puppet
Enterprise.
  Therefore, the notification message that would appear in the PuppetDB
  dashboard indicating that a newer version is available has been removed
  for PE environments.

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Announce: PuppetDB 1.3.0 Available

[Chris Price]

On Wednesday, May 8, 2013 5:31:16 AM UTC-7, Erik Dalén wrote:


 For example finding all nodes that failed their last puppet run seems like 
 it would need one node query and then a event query for each one. 


I'm guessing last run is something we'll bake into the query API at some 
point too. 

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Announce: PuppetDB 1.3.0 Available

[Chris Price]

PuppetDB 1.3.0 is now available for download! This is a backward
compatible feature release of PuppetDB.

=
## Downloads ##
=

Available in native package format at:
http://yum.puppetlabs.com and http://apt.puppetlabs.com

Puppet module:
http://forge.puppetlabs.com/puppetlabs/puppetdb

Source (same license as Puppet): http://github.com/puppetlabs/puppetdb/

# Documentation (including how to install):
http://docs.puppetlabs.com/puppetdb/1.http://docs.puppetlabs.com/puppetdb/1.2
3

# Issues can be filed at:
http://projects.puppetlabs.com/projects/puppetdb/issues

# See our development board on Trello:
http://links.puppetlabs.com/puppetdb-trello


##  PuppetDB 1.3.0 Release Notes  ##


Many thanks to following people who contributed patches to this
release:

* Branan Purvine-Riley
* Chris Price
* Deepak Giridharagopal
* Ken Barber
* Matthaus Owens
* Moses Mendoza
* Nick Fagerlund
* Nick Lewis

Notable features:

* Report queries

  The query endpoint `experimental/event` has been augmented to support a
  much more interesting set of queries against report data.  You can now
query
  for events by status (e.g. `success`, `failed`, `noop`), timestamp ranges,
  resource types/titles/property name, etc.  This should make the report
  storage feature of PuppetDB *much* more valuable!

* Import/export of PuppetDB reports

  PuppetDB 1.2 added the command-line tools `puppetdb-export` and
`puppetdb-import`,
  which are useful for migrating catalog data between PuppetDB databases or
  instances.  In PuppetDB 1.3, these tools now support importing
  and exporting report data in addition to catalog data.

Bug fixes:

* `puppetdb-ssl-setup` is now smarter about not overwriting keystore
  settings in `jetty.ini` during upgrades

* Add database index to `status` field for events to improve query
performance

* Fix `telnet` protocol support for embedded nrepl

* Upgrade to newer version of nrepl

* Improvements to developer experience (remove dependency on `rake` for
  building/running clojure code)

-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: Need a solution for puppet node clean (puppet v3.0.2)

[Chris Price]

David,

Are you using PuppetDB?  There was a thread on this list recently about the 
same topic, and there was some example SQL that could be used in the 
short-term.  We have a few open tickets around coming up with better 
solutions for this and we expect to be addressing them Very Soon Now.  If 
you are using PuppetDB and you are interested in links (to either the 
tickets or the previous thread) let me know and I'll dig them up.

Thanks!
Chris

On Thursday, January 31, 2013 10:26:18 AM UTC-8, David Kerr wrote:

 My environment heavily depends on exported resources to detect our mongo 
 instances and to populate our haproxies. 

 When we bring up and down nodes in AWS puppet node clean isn't cleaning 
 up the exported resources so we get ghost
 machines loaded into those config files.

 Up until today I've attempted to limp along by doing:
 puppet node clean
 sudo puppet cert clean
 delete from catalog_resources where title like '%hostname%'
 delete from resource_params where value like '%hostname%'

 That's been pretty good, but today I ran into a problem where even that 
 didn't work.

 I'm comfortable working in the DB, but what's tough is trying to match the 
 hashed ID's across tables (the data model doesn't make it exactly clear 
 what's going on)

 If someone's already tackled this beast and has a script that does it 
 right, that would be fantastic.
 I also understand that this is solved in 3.1, but I'm not too keen on 
 upgrading to an RC just to
 get exported resources working correctly.

 If someone has insight into the data model and can help me fill the gaps 
 that would be wonderful

 Thanks.


-- 
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 email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Difficulty debugging crashing PuppetDB

[Chris Price]

Cody,

Can you provide some details on your OS and JVM flavors / versions?  Also, 
you mentioned there was nothing in the logs--does this include the 
syslog?  And are there any other *files* in the /var/log/puppetdb directory?


On Wednesday, January 9, 2013 5:30:03 PM UTC-8, Cody Robertson wrote:

 I have no core dumps however I need to make sure I have it set to allow 
 them. It literally just goes kaput - very strange. I've yet to have time to 
 strace it yet today however I did it briefly and it was merely doing a 
 bunch of waits.

 On Wednesday, January 9, 2013 6:43:05 PM UTC-5, Ken Barber wrote:

 Do you get a core dump? Does it seriously just silently 'stop' with no 
 SEGV or anything - even in the forground? 

 On Wed, Jan 9, 2013 at 11:07 PM, Cody Robertson codyha...@gmail.com 
 wrote: 
  There is nothing in the logs as previously noted. It simply crashed 
 quietly. 
  
  This is the same for when I'm running it in the foreground with --debug 
 or 
  when it's a daemon. It simply quietly crashes. 
  
  -- 
  013-01-09 18:00:15,841 DEBUG [command-proc-89] 
  [bonecp.PreparedStatementHandle] SELECT timestamp FROM 
 certname_catalogs 
  WHERE certname='typhoon.xxx.com' ORDER BY timestamp DESC LIMIT 1 
  2013-01-09 18:00:16,185 DEBUG [command-proc-89] 
  [bonecp.PreparedStatementHandle] SELECT 1 FROM catalogs WHERE 
  hash='b9915aef874b1a291e32f1b7cbe0efa9848fb923' LIMIT 1 
  2013-01-09 18:00:16,185 DEBUG [command-proc-89] 
 [bonecp.StatementHandle] 
  UPDATE catalogs SET api_version=1, catalog_version='1357754062' WHERE 
  hash='b9915aef874b1a291e32f1b7cbe0efa9848fb923' 
  2013-01-09 18:00:16,185 DEBUG [command-proc-89] 
 [bonecp.StatementHandle] 
  DELETE FROM certname_catalogs WHERE certname='typhoon.xxx.com' 
  2013-01-09 18:00:16,186 DEBUG [command-proc-89] 
  [bonecp.PreparedStatementHandle] INSERT INTO certname_catalogs 
  (certname,catalog,timestamp) VALUES 
  ('typhoon.xxx.com','b9915aef874b1a291e32f1b7cbe0efa9848fb923',2013-01-09 

  18:00:15.815) 
  2013-01-09 18:00:16,186 INFO  [command-proc-89] [puppetdb.command] 
  [7779017b-5be2-415d-afd6-264d6d4d789e] [replace catalog] 
 typhoon.xxx.com 
  sh-4.1# 
  -- 
  
  I'll attempt to attach a strace to it however it's so remarkably 
 verbose 
  it's always a treat to sift through it. Is there an easy way to 
 increase the 
  verbosity of puppetDB perhaps? 
  
  -Cody 
  
  On Wednesday, January 9, 2013 6:11:19 AM UTC-5, Matthew Burgess wrote: 
  
  On Wed, Jan 9, 2013 at 1:37 AM, Cody Robertson codyha...@gmail.com 
  wrote: 
   Hello! How is everyone this splendid evening? 
   
   I've recently migrated to the latest Puppet and PuppetDB (using the 
   build in 
   database) however I'm noticing PuppetDB keeps crashing without any 
   errors 
   that I can find in the logs. I've ran it in the foreground using the 
   puppetdb-foreground command however it simply exits after awhile. 
 The 
   only 
   thing I can consistently do is see it crash - I can't get any useful 
   debug 
   information beyond that. 
   
   Can anyone shed some light on how I should go about this? Thank you! 
  
  What does /var/log/messages say.  Just a stab in the dark, but if your 
  server is short of memory, then the kernel's oom killer may be 
  targetting the puppetdb process; that would certainly be evident in 
  your /var/log/messages output. 
  
  If that's not the culprit, then attaching 'strace' to the puppetdb 
  process might be informative (strace -p pid). 
  
  Regards, 
  
  Matt. 
  
  -- 
  You received this message because you are subscribed to the Google 
 Groups 
  Puppet Users group. 
  To view this discussion on the web visit 
  https://groups.google.com/d/msg/puppet-users/-/vADEbpPDw7IJ. 
  
  To post to this group, send email to puppet...@googlegroups.com. 
  To unsubscribe from this group, send email to 
  puppet-users...@googlegroups.com. 
  For more options, visit this group at 
  http://groups.google.com/group/puppet-users?hl=en. 



-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/4eL0sJzc1IoJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Difficulty debugging crashing PuppetDB

[Chris Price]

You could also try `puppetdb-foreground --debug` for some more verbose 
logging.  And, is there anything at all in /var/log/puppetdb?

On Wednesday, January 9, 2013 3:11:19 AM UTC-8, Matthew Burgess wrote:

 On Wed, Jan 9, 2013 at 1:37 AM, Cody Robertson 
 codyha...@gmail.comjavascript: 
 wrote: 
  Hello! How is everyone this splendid evening? 
  
  I've recently migrated to the latest Puppet and PuppetDB (using the 
 build in 
  database) however I'm noticing PuppetDB keeps crashing without any 
 errors 
  that I can find in the logs. I've ran it in the foreground using the 
  puppetdb-foreground command however it simply exits after awhile. The 
 only 
  thing I can consistently do is see it crash - I can't get any useful 
 debug 
  information beyond that. 
  
  Can anyone shed some light on how I should go about this? Thank you! 

 What does /var/log/messages say.  Just a stab in the dark, but if your 
 server is short of memory, then the kernel's oom killer may be 
 targetting the puppetdb process; that would certainly be evident in 
 your /var/log/messages output. 

 If that's not the culprit, then attaching 'strace' to the puppetdb 
 process might be informative (strace -p pid). 

 Regards, 

 Matt. 


-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/r4X9JqrxEDwJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] problems with puppetdb

[Chris Price]

Hi Ryan,

The puppetdb process shouldn't be trying to manipulate the postgres process 
in any way--it should only be communicating with it via a socket, and the 
authentication should be based on the postgres database user account rather 
than the system user account.  Are you seeing any errors in your puppetdb 
logs when you run it as the 'puppet' user?

Thanks!
Chris

On Wednesday, December 19, 2012 7:54:44 AM UTC-8, Ryan Bond wrote:

 It seems that once I cut over to postgres the puppet user was no longer 
 able to launch puppetdb.

 The easy fix was changing the user to root in 
 /etc/default/puppetdb...but I doubt this is something I'll want to leave in 
 place.


 On Tue, Dec 18, 2012 at 5:17 PM, Peter Brown rendh...@gmail.comjavascript:
  wrote:

 On 18 December 2012 15:50, Ryan Bond drb...@gmail.com javascript:wrote:

 Was this issue ever resolved? I've been experiencing the same symptoms, 
 ever since I switched over to postgresql.

 Interestingly enough, when I run *java -jar 
 /usr/share/puppetdb/puppetdb.jar services -c /etc/puppetdb/conf.ini * 
 instead 
 of the init script, puppetdb fires up with no problems.

 Any feedback would be appreciated.


 I had the issue on you home testing setup and haven't looked at it for a 
 while.

 I use puppetdb with a postgresql backed on CentOS at work and it works 
 pretty well.
  

  
 Thanks,
 Ryan


 On Friday, July 20, 2012 11:24:33 AM UTC-5, Chris Price wrote:

 OK, yes, the most important bit from that log output is this:

 SelectChannelConnector@**localhost:8080

 If you hit port 8080 with a browser and/or via telnet, it should be 
 open.  Ideally there should also be some output about opening port 8081 
 for 
 SSL connections, but it's entirely possible that the packaging issues that 
 you brought to our attention are the reason that that did not get 
 configured properly.  We can dig into your jetty.ini file to investigate 
 that if needed.

 As for the netstat output: what arguments are you calling it with?  On 
 my system, I get (filtered down to the relevant bits):

 cprice@localhost ~/work/puppetdb $ netstat -ntpl
 (Not all processes could be identified, non-owned process info
  will not be shown, you would have to be root to see it all.)
 Active Internet connections (only servers)
 Proto Recv-Q Send-Q Local Address   Foreign Address 
 State   PID/Program name 
 tcp6   0  0 127.0.0.1:8080  :::*   
  LISTEN  24802/java  
 tcp6   0  0 192.168.101.134:8081:::*   
  LISTEN  24802/java  

 So, I can see port 8080 and 8081 open.  It's possible that there may be 
 a few additional IPv4/tcp ports open that are owned by java 
 processes--these could perhaps be attributed to ActiveMQ or our embedded 
 database.  Would love to see how this output matches up with yours.

 Thanks
 Chris

  
 On Thursday, July 19, 2012 8:15:37 PM UTC-7, Pete wrote:

 On 20 July 2012 11:20, Chris Price ch...@puppetlabs.com wrote: 
  Hello Pete, 
  
  Do you have a reliable way to reproduce the port issue that you 
 mentioned? 
  We'd like to troubleshoot it further but haven't found any way to 
 reproduce 
  it on our end yet. 
  
  If you're not getting log output in /var/log/puppetdb, can you 
 please try 
  the following?: 
  
  1. Edit the file /etc/puppetdb/conf.d/config.**ini, and comment out 
 the 
  logging-config line. 
  2. Run this command: 
  
  java -jar /usr/share/puppetdb/puppetdb.**jar services -c 
 /etc/puppetdb/conf.d 

 I tried that but only got INFO level logging 
 I edited the log4j.properties file and turned on debug level console 
 logging and got this output 


 root@korolev:~# java -jar /usr/share/puppetdb/puppetdb.**jar 
 services -c /etc/puppetdb/conf.ini 
 2012-07-20 13:03:40,982 INFO  [puppetlabs.jetty] Removing buggy 
 security provider SunPKCS11-NSS version 1.7 
 2012-07-20 13:03:46,916 INFO  [cli.services] PuppetDB version 0.9.2 
 2012-07-20 13:03:48,490 INFO  [cli.services] Starting broker 
 2012-07-20 13:03:51,892 INFO  [cli.services] Starting 2 command 
 processor threads 
 2012-07-20 13:03:51,896 INFO  [cli.services] Starting query server 
 2012-07-20 13:03:51,897 INFO  [cli.services] Starting database 
 compactor (60 minute interval) 
 2012-07-20 13:03:52,015 INFO  [cli.services] Beginning database 
 compaction 
 org.eclipse.jetty.ssl.password : 2012-07-20 13:03:52,420 INFO 
 [cli.services] Finished database compaction 
 ^C2012-07-20 13:08:27,976 INFO  [cli.services] Shutdown request 
 received; puppetdb exiting. 
 root@korolev:~# java -jar /usr/share/puppetdb/puppetdb.**jar services 
 -c 
 /etc/puppetdb/conf.ini 
 2012-07-20 13:08:44,944 INFO  [puppetlabs.jetty] Removing buggy 
 security provider SunPKCS11-NSS version 1.7 
 2012-07-20 13:08:50,008 INFO  [main] [cli.services] PuppetDB version 
 0.9.2 
 2012-07-20 13:08:50,008 DEBUG [main] [bonecp.BoneCPDataSource] JDBC 
 URL = 
 jdbc:postgresql://127.0.0.1:**5432/puppetdbhttp://127.0.0.1

[Puppet Users] Re: Help with PuppetDB

[Chris Price]

Also, there are a few notes on common SSL issues here:

http://docs.puppetlabs.com/puppetdb/puppetdb-faq.html#puppetdb-is-complaining-about-a-truststore-or-keystore-file-what-do-i-do


On Friday, December 7, 2012 8:27:14 AM UTC-8, Nishant Jain wrote:

 Hello Everybody,
I am trying to install the puppetdb on the same 
 machine as am running my puppetmaster.
 I am getting the following error when am trying to connect the agent:

 Error: Could not retrieve catalog from remote server: Error 400 on SERVER: 
 Failed to submit 'replace facts' command for 
 ftldwshost180.wsdev.citrix.com to PuppetDB at 10.12.14.85:8081: 
 Connection refused - connect(2)
 Warning: Not using cache on failed catalog
 Error: Could not retrieve catalog; skipping run


 Can anybody tell me how to resolve this error???

 System Information:
 Red Hat Enterprise Linux Server release 5.8 (Tikanga)
 puppet 3.0.1
 puppetdb 1.0.4



 I have installed and made the changes for the pupeptdb according to the 
 following link:
 https://github.com/puppetlabs/puppetdb


 I think the error is related to the ssl certificates??

 The output with running trace is as follows:
 gnoring --listen on onetime run
 Warning: Unable to fetch my node definition, but the agent run will 
 continue:
 Warning: Error 400 on SERVER: Could not retrieve facts for 
 ftldwshost180.wsdev.citrix.com: Failed to find facts from PuppetDB at 
 10.12.14.85:8081: SSL_connect SYSCALL returned=5 errno=0 state=SSLv3 read 
 finished A
 Info: Retrieving plugin
 Error: Could not retrieve catalog from remote server: Error 400 on SERVER: 
 Failed to submit 'replace facts' command for 
 ftldwshost180.wsdev.citrix.com to PuppetDB at 10.12.14.85:8081: 
 SSL_connect SYSCALL returned=5 errno=0 state=SSLv3 read finished A
 /usr/lib/ruby/site_ruby/1.8/puppet/indirector/rest.rb:65:in `deserialize'
 /usr/lib/ruby/site_ruby/1.8/puppet/indirector/rest.rb:121:in `find'
 /usr/lib/ruby/site_ruby/1.8/puppet/indirector/indirection.rb:191:in `find'
 /usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:243:in 
 `retrieve_new_catalog'
 /usr/lib/ruby/site_ruby/1.8/puppet/util.rb:348:in `thinmark'
 /usr/lib/ruby/1.8/benchmark.rb:308:in `realtime'
 /usr/lib/ruby/site_ruby/1.8/puppet/util.rb:347:in `thinmark'
 /usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:242:in 
 `retrieve_new_catalog'
 /usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:67:in `retrieve_catalog'
 /usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:107:in 
 `prepare_and_retrieve_catalog'
 /usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:159:in `run'
 /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:45:in `run'
 /usr/lib/ruby/site_ruby/1.8/puppet/agent/locker.rb:20:in `lock'
 /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:45:in `run'
 /usr/lib/ruby/1.8/sync.rb:230:in `synchronize'
 /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:45:in `run'
 /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:119:in `with_client'
 /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:42:in `run'
 /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:84:in `run_in_fork'
 /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:41:in `run'
 /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:175:in `call'
 /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:175:in `controlled_run'
 /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:39:in `run'
 /usr/lib/ruby/site_ruby/1.8/puppet/application/agent.rb:338:in `onetime'
 /usr/lib/ruby/site_ruby/1.8/puppet/application/agent.rb:311:in 
 `run_command'
 /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:346:in `run'
 /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:438:in `plugin_hook'
 /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:346:in `run'
 /usr/lib/ruby/site_ruby/1.8/puppet/util.rb:500:in `exit_on_fail'
 /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:346:in `run'
 /usr/lib/ruby/site_ruby/1.8/puppet/util/command_line.rb:76:in `execute'
 /usr/bin/puppet:10
 Warning: Not using cache on failed catalog
 Error: Could not retrieve catalog; skipping run



 Thanks,
 Nishant

















-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/igakMIA6i3AJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Re: Question about PuppetDB queries

[Chris Price]

Hi,

Thanks for letting us know about the log messages you are seeing!

A few thoughts:

1) Re: the first query that you sent (DELETE FROM catalogs...): this is the 
PuppetDB garbage collector, which cleans up unused data from the tables 
every so often.  It's not entirely shocking that this query might take over 
10 seconds on occasion, so this one is probably nothing to be too worried 
about--though we will be keeping an eye out on our end of things, and if 
this is something that users are seeing in their logs frequently, we'll 
probably at least make some changes to improve the way we're logging it.

2) The logging on that second query is horrible, that's definitely a bug on 
our end.  I've created a ticket for it here:
http://projects.puppetlabs.com/issues/17732

3) Now, perhaps more importantly, we'd like to figure out why the queries 
are running slow for you in the first place.  As I mentioned, it's not 
entirely shocking/concerning that that first query would end up taking 
longer than 10 seconds to run, but the second one is fairly surprising. 
 Could you possible provide us with some specs about your environment? 
 What kind of hardware are you running PuppetDB on?  Which database backend 
are you using?  How many nodes do you have in your population, and 
approximately how many resources per node?  (A screenshot of your PuppetDB 
dashboard web page might be useful if you don't mind sharing one.)

If you need a faster response, please feel free to jump on IRC (Freenode, 
#puppet), and just mention the word 'puppetdb'.

Thanks again for letting us know!

On Monday, November 19, 2012 2:53:51 AM UTC-8, ak0ska wrote:

 Hello,

 We get a good amount of warnings regarding queries that couldn't be 
 executed within the threshold. There are 2 types of queries that usually 
 get logged with this warning, I just wanted to ask if these queries look 
 normal, because we cannot really judge, as we're fairly new to PuppetDB. 
 Especially the second one looks weird, and it also makes our logfile grow 
 fast.

 Example for type 1 : http://pastebin.com/exNG2bCj

 Example for type 2 (this is actually one single entry in the log) : 
 http://pastebin.com/ym9AHPSk

 Thanks in advance!

 Cheers,

 ak0ska


-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/HKiNpIzrvdAJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Re: PuppetDB Install error: ::postgresql::validate_db_connection at /etc/puppet/modules/puppetdb/manifests/server/validate_db.pp:62

[Chris Price]

Great, glad you were able to work it out.  Out of curiosity, how did you 
install the puppetdb module?  I presume you did not use the `puppet module` 
tool, which installs those dependencies for you.  Would it be valuable for 
us to put some more explicit information about the dependencies somewhere 
so that others don't encounter the same issue?  Any suggestions on where we 
should put that info?

Thanks for the feedback!  Please let us know if you have any additional 
trouble!


On Wednesday, October 31, 2012 9:44:31 AM UTC-7, Worker Bee wrote:

 thanks, I was just getting ready to reply.
 I did actually find this information and get it working!

 Thank and feel free to ping me if you have any problems!




 On Tue, Oct 30, 2012 at 5:42 PM, Nr18 j...@woodwing.com javascript:wrote:

 Found it!!

 You need to include the dependencies of the module in you module path:

 cprice404/inifile - http://forge.puppetlabs.com/cprice404/inifile
 puppetlabs/postgresql - 
 http://forge.puppetlabs.com/puppetlabs/postgresql

 Regards,

 Nr18


 On Tuesday, 30 October 2012 22:18:01 UTC+1, Nr18 wrote:

 I have the same issue did you find a solution or explanation for this 
 issue?

 On Friday, 12 October 2012 16:04:01 UTC+2, Worker Bee wrote:

 Hi Everyone;

 I am getting the following error when I try to install PuppetDB.

 Maybe I have stale instructions??  

 Thanks!
 Bee

 Error: Could not retrieve catalog from remote server: Error 400 on 
 SERVER: Invalid tag ::postgresql::validate_db_**connection at 
 /etc/puppet/modules/puppetdb/**manifests/server/validate_db.**pp:62 

  -- 
 You received this message because you are subscribed to the Google Groups 
 Puppet Users group.
 To view this discussion on the web visit 
 https://groups.google.com/d/msg/puppet-users/-/Wf8DXzYUoh8J.

 To post to this group, send email to puppet...@googlegroups.comjavascript:
 .
 To unsubscribe from this group, send email to 
 puppet-users...@googlegroups.com javascript:.
 For more options, visit this group at 
 http://groups.google.com/group/puppet-users?hl=en.




-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/vjlJF8Azs-sJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Re: PuppetDB Install error: ::postgresql::validate_db_connection at /etc/puppet/modules/puppetdb/manifests/server/validate_db.pp:62

[Chris Price]

Ah, I see... so you downloaded the module tarball and built your own RPM? 
 Anything we could have done to help highlight the fact that the module had 
some dependencies?

On Wednesday, October 31, 2012 11:54:44 AM UTC-7, Worker Bee wrote:

 In my case, I need to be able to install as an rpm because we use yum (for 
 now) to ensure consistent distribution across all of our environments.  

 Just for testing, I also did an install via 'puppet module' and that 
 worked pretty well...


 On Wed, Oct 31, 2012 at 2:51 PM, Chris Price 
 ch...@puppetlabs.comjavascript:
  wrote:

 Great, glad you were able to work it out.  Out of curiosity, how did you 
 install the puppetdb module?  I presume you did not use the `puppet module` 
 tool, which installs those dependencies for you.  Would it be valuable for 
 us to put some more explicit information about the dependencies somewhere 
 so that others don't encounter the same issue?  Any suggestions on where we 
 should put that info?

 Thanks for the feedback!  Please let us know if you have any additional 
 trouble!


 On Wednesday, October 31, 2012 9:44:31 AM UTC-7, Worker Bee wrote:

 thanks, I was just getting ready to reply.
 I did actually find this information and get it working!

 Thank and feel free to ping me if you have any problems!




 On Tue, Oct 30, 2012 at 5:42 PM, Nr18 j...@woodwing.com wrote:

 Found it!!

 You need to include the dependencies of the module in you module path:

 cprice404/inifile - 
 http://forge.puppetlabs.**com/cprice404/inifilehttp://forge.puppetlabs.com/cprice404/inifile
 puppetlabs/postgresql - http://forge.puppetlabs.**
 com/puppetlabs/postgresqlhttp://forge.puppetlabs.com/puppetlabs/postgresql

 Regards,

 Nr18


 On Tuesday, 30 October 2012 22:18:01 UTC+1, Nr18 wrote:

 I have the same issue did you find a solution or explanation for this 
 issue?

 On Friday, 12 October 2012 16:04:01 UTC+2, Worker Bee wrote:

 Hi Everyone;

 I am getting the following error when I try to install PuppetDB.

 Maybe I have stale instructions??  

 Thanks!
 Bee

 Error: Could not retrieve catalog from remote server: Error 400 on 
 SERVER: Invalid tag ::postgresql::validate_db_**con**nection at 
 /etc/puppet/modules/puppetdb/**m**anifests/server/validate_db.**pp**:62 


  -- 
 You received this message because you are subscribed to the Google 
 Groups Puppet Users group.
 To view this discussion on the web visit https://groups.google.com/d/**
 msg/puppet-users/-/**Wf8DXzYUoh8Jhttps://groups.google.com/d/msg/puppet-users/-/Wf8DXzYUoh8J
 .

 To post to this group, send email to puppet...@googlegroups.com.
 To unsubscribe from this group, send email to puppet-users...@**
 googlegroups.com.

 For more options, visit this group at http://groups.google.com/**
 group/puppet-users?hl=enhttp://groups.google.com/group/puppet-users?hl=en
 .


  -- 
 You received this message because you are subscribed to the Google Groups 
 Puppet Users group.
 To view this discussion on the web visit 
 https://groups.google.com/d/msg/puppet-users/-/vjlJF8Azs-sJ.

 To post to this group, send email to puppet...@googlegroups.comjavascript:
 .
 To unsubscribe from this group, send email to 
 puppet-users...@googlegroups.com javascript:.
 For more options, visit this group at 
 http://groups.google.com/group/puppet-users?hl=en.




-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/7z61tiLXXYoJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Benchmark puppetDB

[Chris Price]

Hello Heriyanto,

Were you able to come up with something to solve your problem?  We don't 
currently have any sort of sample catalog that could be used to easily 
benchmark the performance difference in your environment, though your 
e-mail has prompted some internal discussion about how we could conceivably 
provide something like that in the future.

I suspect that if you simply time any agent run in your environment (for an 
agent with a non-trivial number of resources) against legacy storedconfigs, 
and then time it again with PuppetDB, you should notice some difference 
(because legacy storeconfigs must synchronously insert all of the catalog 
data into the database before the run completes).  You could also run your 
master with the --debug flag, which might provide you with some timing 
info for the various phases of the process.

However, the biggest benefits come when you have a master that is under 
some load from concurrent agent requests.  That might be a bit more tricky 
to simulate in your own environment if the blog posts and other data we've 
posted isn't sufficient, but we would be happy to try to help if you have 
questions!

Thanks
Chris

On Wednesday, October 17, 2012 5:45:07 AM UTC-7, Heriyanto wrote:

 Hi Nan,

 Thank for your reply, yes that what im talking about, i can't prove just 
 with link to puppet blog,
 yes you right catalog compile should give our output, do you have some 
 example of one
 with large number of resources for my testing?

 Thank for your help
 Regards,

 On Tue, Oct 16, 2012 at 1:12 AM, Nan Liu n...@puppetlabs.comjavascript:
  wrote:

 On Mon, Oct 15, 2012 at 1:41 AM, shell heriyanto
 shell.h...@gmail.com javascript: wrote:
  I know puppetDB its more faster than storeconfigs, but to replace
  storeconfigs with puppetDB into production server
  Its need more explanation than some link from puppetlabs, need prove to 
 my
  bos and team.
  For testing i just have 1 puppetmaster and 1 and 2 puppet agent, how i 
 can
  look different performance?
  Its that any idea / or complex puppet stanza to benchmark / compare this
  with storeconfigs?

 A catalog compile should show the difference in speed (especially one
 with large number of resources). This is discussed in the Puppet DB
 blog post. Also Deepak has great talk at Puppet Conf discussing why
 PuppetDB is async (which isn't something quite as easy to benchmark
 with just 2 agents):

 http://youtu.be/xw83cRofkpM

 HTH,

 Nan

 --
 You received this message because you are subscribed to the Google Groups 
 Puppet Users group.
 To post to this group, send email to puppet...@googlegroups.comjavascript:
 .
 To unsubscribe from this group, send email to 
 puppet-users...@googlegroups.com javascript:.
 For more options, visit this group at 
 http://groups.google.com/group/puppet-users?hl=en.




-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/vTscH5wWHWEJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Re: PuppetDB Connection Failures

[Chris Price]

Hello Bee,

This message is often the result of one of the following:

1) Firewall blocking the puppetdb port
2) DNS issue with the hostname specified in your puppetdb.conf
3) DNS issue with the ssl-host specified in your jetty.ini on the puppetdb 
server

Are you able to connect (e.g. via telnet) from the master machine to port 
8081 on the puppetdb machine?

Please feel free to jump on the #puppet channel in Freenode if you need 
rapid assistance!  We'll be happy to help.

Thanks
Chris

On Wednesday, October 17, 2012 1:42:06 PM UTC-7, Worker Bee wrote:

 Hi Everyone;

 I am now getting a puppetdb connection error when I attempt to run
 #puppet agent --test

 Error: Could not retrieve catalog from remote server: Error 400 on SERVER: 
 Failed to submit 'replace facts' command for puppetdev to PuppetDB at 
 puppetdev:8081: Connection refused - connect(2)


 puppet.conf
 [master]
 storeconfigs = true
 storeconfigs_backend = puppetdb


 puppetdb.conf
 [main]
 server = puppetdev04
 port = 8081
 JAVA_ARGS=-Xmx192m

 I am running 3.0 open source with passenger
 Using postgres

 I have the puppetdb daemin running

 Any advice, as always, would be greatly appreciated!


 Bee 

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/DwtFZvuAGtcJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Re: PuppetDB SSL error (while trying to reach the dashboard)

[Chris Price]

Hi SirHopcount,

How did you install PuppetDB?  Is there any chance that any of your certs 
(agent / master) have changed since the time when you installed?

I've found that sometimes the easiest way to get things fixed up when you 
have this problem is to do the following:

0) Stop puppetdb
1) remove PuppetDB's SSL directory entirely (usually /etc/puppetdb/ssl)
2) make sure that the agent on the puppetdb machine can run successfully 
against the master (puppet agent --test, sounds like you've already done 
this.
3) Run the puppetdb-ssl-setup script (which should be in your sbin 
directory)
4) Restart puppetdb

If that doesn't fix it, the next things I would doublecheck are the values 
in jetty.ini and that the IP addresses / DNS names for your hosts match up 
with what their certnames are.  Please let us know if this doesn't get you 
moving and we will be happy to assist further.


On Wednesday, September 19, 2012 2:00:49 AM UTC-7, SirHopcount wrote:

 Hi All,

 I am having some problems getting PuppetDB and SSL to work. I build an 
 test environment in Vagrant without any problems but when it try and deploy 
 it to my production environment I can't seem to get it to work with SSL.  I 
 followed the instructions on the puppetlabs website and I made sure I could 
 do an successful puppet run before installing PuppetDB:

 (changed the hostname/company name)

 # puppet agent --test
 info: Caching catalog for hostname.company.local
 info: Applying configuration version '1347960542'
 notice: Finished catalog run in 2.04 seconds

 But when I try to reach the dashboard it get an error:

 The connection was interrupted
 The connection to xxx.xxx.xxx.xxx:8081 was interrupted while the page 
 was loading.

 When I check the puppetdb log file I see the following error:

 2012-09-19 10:39:24,016 WARN  [qtp1281335597-66] [io.nio] 
 javax.net.ssl.SSLException: Received fatal alert: unknown_ca
 2012-09-19 10:39:49,182 WARN  [qtp1281335597-67] [io.nio] 
 javax.net.ssl.SSLHandshakeException: null cert chain
 2012-09-19 10:39:49,218 WARN  [qtp1281335597-66] [io.nio] 
 javax.net.ssl.SSLHandshakeException: null cert chain
 2012-09-19 10:39:49,251 WARN  [qtp1281335597-67] [io.nio] 
 javax.net.ssl.SSLProtocolException: handshake alert: no_certificate

 I checked the jetty.ini file and made sure both the keystore and 
 truststore exist. It also has an key-password and trust-password set. I 
 changed the jetty.ini file to allow http connections and then I can reach 
 the dashboard via http without any problems. Does anybody have an idea what 
 could be wrong ?


-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/XftI1lGbfloJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Help me name a class in the new puppetdb module!

[Chris Price]

That's a fair statement; it's been brought up around the office.  The goal 
for now is to have a single puppetdb module that is capable of managing 
everything related to puppetdb, and then potentially later wrap some subset 
of the puppetdb classes in the puppet/master module.  For the short term, 
I'm just trying to name the class inside of the puppetdb module.

Thanks for the suggestion!

On Saturday, September 15, 2012 7:03:20 AM UTC-7, Ashley Penney wrote:

 I kind of feel like the reason you're having a problem naming this is 
 that it doesn't really belong in the puppetdb class but in the puppet 
 module that sets up the server. :) 

 That's how I did this, I have a puppetdb module that purely sets up 
 puppetdb and then puppet::server::puppetdb to handle that other stuff. 
  Failing that I guess I nominate the name puppetdb::puppetmaster 
 despite the ugliness! 

 On Fri, Sep 14, 2012 at 7:03 PM, Chris Price 
 ch...@puppetlabs.comjavascript: 
 wrote: 
  Anyone interested in helping me name a class in the forthcoming puppetdb 
  module? 
  
  There are 2 major parts to the module... the part that sets up puppetdb 
  itself, and the part that sets up the puppet master to talk to puppetdb. 
  I'm brainstorming names for the latter... a class that you would apply 
 on 
  your puppet master machine to tell it how to find and use puppetdb. 
  
  Any suggestions? 
  
  -- 
  You received this message because you are subscribed to the Google 
 Groups 
  Puppet Users group. 
  To post to this group, send email to 
  puppet...@googlegroups.comjavascript:. 

  To unsubscribe from this group, send email to 
  puppet-users...@googlegroups.com javascript:. 
  For more options, visit this group at 
  http://groups.google.com/group/puppet-users?hl=en. 


-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/Q0Hmd1t26l4J.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Help me name a class in the new puppetdb module!

[Chris Price]

Not a bad idea, thanks for the suggestion!

On Monday, September 17, 2012 2:39:15 AM UTC-7, Stefan Goethals wrote:

 Why not simply puppetdb::server for the ... well, puppetdb server and 
 puppetdb::client for... the client, as that is exactly what the 
 puppetmaster is to puppetdb?

 Regards,

 Stefan.

 On Sat, Sep 15, 2012 at 4:03 PM, Ashley Penney ape...@gmail.comjavascript:
  wrote:

 I kind of feel like the reason you're having a problem naming this is
 that it doesn't really belong in the puppetdb class but in the puppet
 module that sets up the server. :)

 That's how I did this, I have a puppetdb module that purely sets up
 puppetdb and then puppet::server::puppetdb to handle that other stuff.
  Failing that I guess I nominate the name puppetdb::puppetmaster
 despite the ugliness!

 On Fri, Sep 14, 2012 at 7:03 PM, Chris Price 
 ch...@puppetlabs.comjavascript: 
 wrote:
  Anyone interested in helping me name a class in the forthcoming puppetdb
  module?
 
  There are 2 major parts to the module... the part that sets up puppetdb
  itself, and the part that sets up the puppet master to talk to puppetdb.
  I'm brainstorming names for the latter... a class that you would apply 
 on
  your puppet master machine to tell it how to find and use puppetdb.
 
  Any suggestions?
 
  --
  You received this message because you are subscribed to the Google 
 Groups
  Puppet Users group.
  To post to this group, send email to 
  puppet...@googlegroups.comjavascript:
 .
  To unsubscribe from this group, send email to
  puppet-users...@googlegroups.com javascript:.
  For more options, visit this group at
  http://groups.google.com/group/puppet-users?hl=en.

 --
 You received this message because you are subscribed to the Google Groups 
 Puppet Users group.
 To post to this group, send email to puppet...@googlegroups.comjavascript:
 .
 To unsubscribe from this group, send email to 
 puppet-users...@googlegroups.com javascript:.
 For more options, visit this group at 
 http://groups.google.com/group/puppet-users?hl=en.




-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/uV1NNslhb2EJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Help me name a class in the new puppetdb module!

[Chris Price]

Anyone interested in helping me name a class in the forthcoming puppetdb
module?

There are 2 major parts to the module... the part that sets up puppetdb
itself, and the part that sets up the puppet master to talk to puppetdb.
 I'm brainstorming names for the latter... a class that you would apply on
your puppet master machine to tell it how to find and use puppetdb.

Any suggestions?

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Re: minor change in inkling/postgresql – PostgreSQL

[Chris Price]

Thanks or the feedback, Jeremy.  Knowing that there are folks out there who 
would find it useful helps me to prioritize :)  I still have this on my 
to-do list, and hope to get a chance to work on it sometime in the next 
week or so.  I'll send another response to this thread as soon as I do.

On Wednesday, September 5, 2012 9:31:42 PM UTC-7, Jeremy Kitchen wrote:

 On Wed, Aug 29, 2012 at 09:43:49AM -0700, Chris Price wrote: 
  I'd love to put together a test manifest that illustrates how to do 
 what 
  you're doing w/o modifying params.pp directly, 

 I'd love to see this, myself, for educational purposes. I'm still pretty 
 new to puppet and the variable scoping scares me a bit, so I'd like to 
 see some good examples of how people are doing overridable defaults like 
 this! 

 -Jeremy 


-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/6OCT9012ReoJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Re: Trying to setup puppetdbquery on puppet-3.0.0-rc5

[Chris Price]

Chuck,

The cause of this issues is that we introduced our own HTTP connection 
wrapper in 3.0 (rather than using Net::HTTP directly).  This allows us to 
do a better job of centralizing the logic related to managing SSL setup and 
error handling.

Our Connection class provides a subset of the methods available on Ruby's 
HTTP class, and it looks like puppetdbquery is using one of the methods 
that don't currently exist in our new API.

The possible solutions would be to add the missing #start method to our new 
class, or to tweak puppetdbquery so that it doesn't rely on the #start 
method.  I'll ping the folks on our platform team and see what their 
thoughts are.

Thanks for the heads up!
Chris

On Thursday, August 30, 2012 6:04:27 AM UTC-7, Chuck wrote:

 I have puppetdbquery working on my puppet-2.7.16 puppet master but I am 
 getting an error when using it with puppet-3.0.0-rc5

 https://github.com/dalen/puppet-puppetdbquery

 This is the error I am getting:

   err: Could not retrieve catalog from remote server: Error 400 on SERVER: 
 undefined method `start' for 
 #Puppet::Network::HTTP::Connection:0x7fa6e25db7c8 

 How would I go about finding the actual cause of this issue?


 Thanks,


-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/cnmWN3qKeJYJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Re: minor change in inkling/postgresql – PostgreSQL

[Chris Price]

Hello OSX007,

You are on the right track, for sure.  The goal of the params.pp is to set 
default values for those things and allow you to override them in your own 
manifests.  It's definitely OK for you to edit params.pp directly if you 
know for sure that the settings you've specified will always be the ones 
that you want, but otherwise you should be able to override them in your 
own manifests and pass them in without modifying the module's params.pp 
directly.  This would allow you to potentially use the module to manage 
both 8.x and 9.x instances.

I'd love to put together a test manifest that illustrates how to do what 
you're doing w/o modifying params.pp directly, and submit a pull request to 
the module so that it will be easier for other folks to figure out how to 
do it in the future.  I'd also love to provide a single parameter like 
postgres_version that you could just set to 9.1 and then add code to 
the module that would switch all of those path variables to the correct 
values for you.  I hope to continue submitting pull requests with features 
like that over time, but if you have any such submissions you'd like to 
make yourself, I'm sure they'd be welcomed!

On Wednesday, August 29, 2012 12:15:13 AM UTC-7, OXS007 wrote:

 I think i figured it out in the Postgresql module edit the params.pp so 
 that it looks like this;

 case $::osfamily {

 'RedHat': {

   $service_name = 'postgresql-9.1'

   $client_package_name  = 'postgresql91'

   $server_package_name  = 'postgresql91-server'

   $needs_initdb = true

   $initdb_path  = '/usr/pgsql-9.1/bin/initdb'

   $createdb_path= '/usr/pgsql-9.1/bin/createdb'

   $psql_path= '/usr/pgsql-9.1/bin/psql'

   $datadir  = '/var/lib/pgsql/9.1/data/'

   $pg_hba_conf_path = '/var/lib/pgsql/9.1/data/pg_hba.conf'

   $postgresql_conf_path = '/var/lib/pgsql/9.1/data/postgresql.conf'

   $firewall_supported   = true

   $persist_firewall_command = '/sbin/iptables-save  
 /etc/sysconfig/iptables'
 }




 Op woensdag 29 augustus 2012 02:14:54 UTC-4 schreef OXS007 het volgende:

 Hi,

 When running the Postgresql module the database installed by default is 
 8.4 what we need is 9.1 where do i define the version to be installed by 
 puppet.

 If i edit the params,pp like;

 $client_package_name   = 'postgresql91'
 $server_package_name   = 'postgresql91'

 The 9.1 is being installed but i get some errors like these;

 Execution of '/sbin/service postgresql start' returned 1

 Thanks in forward for you help.



-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/ewViWOoG3kIJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Re: multi-master with puppetdb

[Chris Price]

Hello Alexander,

There are a few things to consider before deciding how you'd like to set 
this up.

The first question, I think, is: why do you want to run two puppetdb 
services rather than just pointing both puppet masters to a single puppetdb 
service?  If you're goal is to share the postgres database, then in most 
cases, that will be your bottleneck (as opposed to the puppetdb service 
itself).  Thus, you might not be buying yourself much by adding a second 
puppetdb service.

Second: do you have a shared CA for the two puppet masters?  Since the 
puppetdb service's SSL auth will be based on a single puppet master's CA, 
you won't be able to connect to a single puppetdb service with two 
different masters using two different CA's.

Third: If you do decide to run two puppetdb services pointing to a single 
postgres instance--this *should* work, but it's not necessarily a 
recommended configuration.  You'd need to be very careful to make sure that 
the two puppetdb services were always running the *exact* same version as 
one another; if you were ever to upgrade one of them without upgrading the 
other, you might trigger a schema migration in the postgres database that 
would render it incompatible with the older version of puppetdb.

Please let us know if you have any additional questions!
Thanks
Chris



On Thursday, August 23, 2012 4:52:17 AM UTC-7, Alexander Swen wrote:

 hi,

 we consider to run a second instance of our puppet master and would like 
 to know how we should do this.
 We have one puppet master with a puppetdb instance on the same server. 
 Puppetdb uses a postgres db on a postgr cluster.

 My main concern is: can we run puppetdb on the second box two? with the 
 same db as the first one?

 thanks for your advise, best regards,
 Alex



-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/JLPEy5Nh1XwJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Re: postgres plugin puppetdb

[Chris Price]

Thanks JM.  Your config files look good and the existence of all of those 
tables in your puppetdb database certainly makes it look as though puppetdb 
is communicating with postgres properly.  Since increasing the heap size 
seems to have gotten you past the issues for now, my next guess is that it 
is some combination of catalog size and number of concurrent agent 
requests, and perhaps number of cores on your machine.  We would love to 
investigate further, so if you are willing to share a postgres dump with us 
that would be fantastic!

I'll e-mail you off-list to follow up on that.  I'd also be interested in 
seeing the output of 'cat /proc/cpuinfo'.

Thanks!
Chris

On Wednesday, August 8, 2012 1:08:09 AM UTC-7, A_SAAS wrote:

 Hi,

 The configuration files are attached.

 Here is the postgres login:
 [root@puppetmaster]:/data/local/postgresql/dumps #  psql -h localhost 
 puppetdb puppetdb
 psql (8.4.12)
 SSL connection (cipher: DHE-RSA-AES256-SHA, bits: 256)
 Type help for help.

 puppetdb= \l
   List of databases
Name|  Owner   | Encoding  | Collation | Ctype |   Access privileges

 ---+--+---+---+---+---
  postgres  | postgres | SQL_ASCII | C | C |
  puppetdb  | puppetdb | SQL_ASCII | C | C |
  template0 | postgres | SQL_ASCII | C | C | =c/postgres
   : 
 postgres=CTc/postgres
  template1 | postgres | SQL_ASCII | C | C | =c/postgres
   : 
 postgres=CTc/postgres
 (4 rows)
 puppetdb= \d
   List of relations
  Schema |  Name   | Type  |  Owner
 +-+---+--
  public | catalog_resources   | table | puppetdb
  public | catalogs| table | puppetdb
  public | certname_catalogs   | table | puppetdb
  public | certname_facts  | table | puppetdb
  public | certname_facts_metadata | table | puppetdb
  public | certnames   | table | puppetdb
  public | classes | table | puppetdb
  public | edges   | table | puppetdb
  public | resource_params | table | puppetdb
  public | schema_migrations   | table | puppetdb
  public | tags| table | puppetdb


 And by the way I changed the JVM max heap at 256M and since then no issue. 
 Regarding the postgres dump file, I'll be willing to give it to you so 
 contact me in private to get the URL or let me know where I can put it as 
 long as nobody could access it publicly.


 Regards,
 JM




 On Tue, Aug 7, 2012 at 6:59 PM, Chris Price ch...@puppetlabs.comjavascript:
  wrote:

 JM,

 Hmm... so, those versions of Java seem fine--those are probably the ones 
 we've done the most testing with.

 So, the error message that you sent indicates that the JVM is running out 
 of RAM.  This could possibly indicate that you are still using the embedded 
 database instead of postgres--the embedded database uses a lot of RAM.  Can 
 we see what your database.ini file looks like?  In fact, perhaps we can 
 take a look at all of the files in your /etc/puppetdb/conf.d directory?

 You could also connect directly to your postgres database using psql or 
 pgadmin, and check to see if the puppetdb tables exist and contain data.

 The only other possibility that I can think of would be if one or more of 
 your nodes has an extremely large catalog, and that the puppetdb JVM 
 instance doesn't have enough memory to process the catalog.  If that's the 
 case, we can try increasing your JVM max heap space in 
 /etc/default/puppetdb... but we would be really interested in collecting 
 some data from you about what that catalog looks like (for our own testing 
 and debugging purposes) if it turns out that that is the culprit. 

 Thanks!
 Chris


On Wednesday, August 8, 2012 1:08:09 AM UTC-7, A_SAAS wrote:

 Hi,

 The configuration files are attached.

 Here is the postgres login:
 [root@puppetmaster]:/data/local/postgresql/dumps #  psql -h localhost 
 puppetdb puppetdb
 psql (8.4.12)
 SSL connection (cipher: DHE-RSA-AES256-SHA, bits: 256)
 Type help for help.

 puppetdb= \l
   List of databases
Name|  Owner   | Encoding  | Collation | Ctype |   Access privileges

 ---+--+---+---+---+---
  postgres  | postgres | SQL_ASCII | C | C |
  puppetdb  | puppetdb | SQL_ASCII | C | C |
  template0 | postgres | SQL_ASCII | C | C | =c/postgres
   : 
 postgres=CTc/postgres
  template1 | postgres | SQL_ASCII | C | C | =c/postgres
   : 
 postgres=CTc/postgres
 (4 rows)
 puppetdb= \d
   List of relations
  Schema |  Name

Re: [Puppet Users] Re: postgres plugin puppetdb

[Chris Price]

?

 Regards,
 JM


 On Mon, Aug 6, 2012 at 6:40 PM, Chris Price ch...@puppetlabs.comwrote:

 Hello A_SAAS,

- Do you see any messages in the file 
/var/log/puppetdb/puppetdb.log?
- If not, can you try editing the file 
/etc/puppetdb/log4j.properties and replace INFO with DEBUG, and 
 then 
see if you get any messages in the aforementioned log file?
- What version of java are you using?  We've encountered some 
SSL-related problems between very early versions of the Oracle JDK 7 
 and 
puppetdb. 

 Thanks!
 Chris


 On Monday, August 6, 2012 1:51:07 AM UTC-7, A_SAAS wrote:

 Hi everyone,


 We are using collectd collecting system information, I am trying to 
 setup the postgres plugin for puppetdb (http://collectd.org/wiki/**
 index.php/Plugin:PostgreSQLhttp://collectd.org/wiki/index.php/Plugin:PostgreSQL),
  
 what could be the relevant value to get? I am trying to see what is going 
 on because lately sometime I get some Sun Aug 05 10:39:12 +0200 2012 
 Puppet (err): Could not retrieve catalog from remote server: Error 400 on 
 SERVER: Failed to submit 'replace catalog' command for XX to 
 PuppetDB at puppetmaster.fqdn:8081: [500 Server Error] 


 I am using puppet:
 ii  puppet2.7.18-1puppetlabs1 
  Centralized configuration management - agent startup and compatibility 
 scripts
  ii  puppet-common   2.7.18-1puppetlabs1 
  Centralized configuration management
 ii  puppet-dashboard1.2.10-1puppetlabs2  Dashboard 
 for Puppet
 ii  puppetdb 0.9.2-1puppetlabs2   
 PuppetDB Centralized Storage.
 ii  puppetdb-terminus   0.9.2-1puppetlabs2   Connect 
 Puppet to PuppetDB by setting up a terminus for PuppetDB.
 ii  puppetmaster  2.7.18-1puppetlabs1 
  Centralized configuration management - master startup and compatibility 
 scripts
 ii  puppetmaster-common 2.7.18-1puppetlabs1  Puppet master 
 common scripts


 On debian squeeze for handling 120 server and the puppetmaster is a 
 1950 with 4go of memory and it doesn't seems to be under heavy load.

 Regards,
 JM

  -- 
 You received this message because you are subscribed to the Google 
 Groups Puppet Users group.
 To view this discussion on the web visit 
 https://groups.google.com/d/msg/puppet-users/-/JHdLQ5zvobAJ.
 To post to this group, send email to puppet-users@googlegroups.com.
 To unsubscribe from this group, send email to 
 puppet-users+unsubscr...@googlegroups.com.
 For more options, visit this group at 
 http://groups.google.com/group/puppet-users?hl=en.






-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/eoIR0s_RTDQJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Re: postgres plugin puppetdb

[Chris Price]

Hello A_SAAS,

   - Do you see any messages in the file /var/log/puppetdb/puppetdb.log?
   - If not, can you try editing the file /etc/puppetdb/log4j.properties 
   and replace INFO with DEBUG, and then see if you get any messages in 
   the aforementioned log file?
   - What version of java are you using?  We've encountered some 
   SSL-related problems between very early versions of the Oracle JDK 7 and 
   puppetdb.

Thanks!
Chris


On Monday, August 6, 2012 1:51:07 AM UTC-7, A_SAAS wrote:

 Hi everyone,


 We are using collectd collecting system information, I am trying to setup 
 the postgres plugin for puppetdb (
 http://collectd.org/wiki/index.php/Plugin:PostgreSQL), what could be the 
 relevant value to get? I am trying to see what is going on because lately 
 sometime I get some Sun Aug 05 10:39:12 +0200 2012 Puppet (err): Could not 
 retrieve catalog from remote server: Error 400 on SERVER: Failed to submit 
 'replace catalog' command for XX to PuppetDB at 
 puppetmaster.fqdn:8081: [500 Server Error] 


 I am using puppet:
 ii  puppet2.7.18-1puppetlabs1 
  Centralized configuration management - agent startup and compatibility 
 scripts
 ii  puppet-common   2.7.18-1puppetlabs1  Centralized 
 configuration management
 ii  puppet-dashboard1.2.10-1puppetlabs2  Dashboard for 
 Puppet
 ii  puppetdb 0.9.2-1puppetlabs2   PuppetDB 
 Centralized Storage.
 ii  puppetdb-terminus   0.9.2-1puppetlabs2   Connect 
 Puppet to PuppetDB by setting up a terminus for PuppetDB.
 ii  puppetmaster  2.7.18-1puppetlabs1  Centralized 
 configuration management - master startup and compatibility scripts
 ii  puppetmaster-common 2.7.18-1puppetlabs1  Puppet master 
 common scripts


 On debian squeeze for handling 120 server and the puppetmaster is a 1950 
 with 4go of memory and it doesn't seems to be under heavy load.

 Regards,
 JM


-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/JHdLQ5zvobAJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] problems with puppetdb

[Chris Price]

OK, yes, the most important bit from that log output is this:

SelectChannelConnector@localhost:8080

If you hit port 8080 with a browser and/or via telnet, it should be open. 
 Ideally there should also be some output about opening port 8081 for SSL 
connections, but it's entirely possible that the packaging issues that you 
brought to our attention are the reason that that did not get configured 
properly.  We can dig into your jetty.ini file to investigate that if 
needed.

As for the netstat output: what arguments are you calling it with?  On my 
system, I get (filtered down to the relevant bits):

cprice@localhost ~/work/puppetdb $ netstat -ntpl
(Not all processes could be identified, non-owned process info
 will not be shown, you would have to be root to see it all.)
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address   Foreign Address State   
PID/Program name 
tcp6   0  0 127.0.0.1:8080  :::*LISTEN 
 24802/java  
tcp6   0  0 192.168.101.134:8081:::*LISTEN 
 24802/java  

So, I can see port 8080 and 8081 open.  It's possible that there may be a 
few additional IPv4/tcp ports open that are owned by java processes--these 
could perhaps be attributed to ActiveMQ or our embedded database.  Would 
love to see how this output matches up with yours.

Thanks
Chris


On Thursday, July 19, 2012 8:15:37 PM UTC-7, Pete wrote:

 On 20 July 2012 11:20, Chris Price ch...@puppetlabs.com wrote: 
  Hello Pete, 
  
  Do you have a reliable way to reproduce the port issue that you 
 mentioned? 
  We'd like to troubleshoot it further but haven't found any way to 
 reproduce 
  it on our end yet. 
  
  If you're not getting log output in /var/log/puppetdb, can you please 
 try 
  the following?: 
  
  1. Edit the file /etc/puppetdb/conf.d/config.ini, and comment out the 
  logging-config line. 
  2. Run this command: 
  
  java -jar /usr/share/puppetdb/puppetdb.jar services -c 
 /etc/puppetdb/conf.d 

 I tried that but only got INFO level logging 
 I edited the log4j.properties file and turned on debug level console 
 logging and got this output 


 root@korolev:~# java -jar /usr/share/puppetdb/puppetdb.jar services -c 
 /etc/puppetdb/conf.ini 
 2012-07-20 13:03:40,982 INFO  [puppetlabs.jetty] Removing buggy 
 security provider SunPKCS11-NSS version 1.7 
 2012-07-20 13:03:46,916 INFO  [cli.services] PuppetDB version 0.9.2 
 2012-07-20 13:03:48,490 INFO  [cli.services] Starting broker 
 2012-07-20 13:03:51,892 INFO  [cli.services] Starting 2 command 
 processor threads 
 2012-07-20 13:03:51,896 INFO  [cli.services] Starting query server 
 2012-07-20 13:03:51,897 INFO  [cli.services] Starting database 
 compactor (60 minute interval) 
 2012-07-20 13:03:52,015 INFO  [cli.services] Beginning database compaction 
 org.eclipse.jetty.ssl.password : 2012-07-20 13:03:52,420 INFO 
 [cli.services] Finished database compaction 
 ^C2012-07-20 13:08:27,976 INFO  [cli.services] Shutdown request 
 received; puppetdb exiting. 
 root@korolev:~# java -jar /usr/share/puppetdb/puppetdb.jar services -c 
 /etc/puppetdb/conf.ini 
 2012-07-20 13:08:44,944 INFO  [puppetlabs.jetty] Removing buggy 
 security provider SunPKCS11-NSS version 1.7 
 2012-07-20 13:08:50,008 INFO  [main] [cli.services] PuppetDB version 0.9.2 
 2012-07-20 13:08:50,008 DEBUG [main] [bonecp.BoneCPDataSource] JDBC 
 URL = jdbc:postgresql://127.0.0.1:5432/puppetdb, Username = puppet, 
 partitions = 5, max (per partition) = 10, min (per partition) = 1, 
 helper threads = 3, idle max age = 60 min, idle test period = 240 min 
 2012-07-20 13:08:50,348 INFO  [main] [cli.services] Starting broker 
 2012-07-20 13:08:54,677 DEBUG [main] [index.BTreeIndex] loading 
 2012-07-20 13:08:54,744 DEBUG [main] [index.BTreeIndex] loading 
 2012-07-20 13:08:54,748 DEBUG [main] [index.BTreeIndex] loading 
 2012-07-20 13:08:54,748 DEBUG [main] [index.BTreeIndex] loading 
 2012-07-20 13:08:54,748 DEBUG [main] [index.BTreeIndex] loading 
 2012-07-20 13:08:54,757 DEBUG [main] [index.BTreeIndex] loading 
 2012-07-20 13:08:55,652 INFO  [main] [journal.Journal] ignoring zero 
 length, partially initialised journal data file: db-1.log number = 1 , 
 length = 0 
 2012-07-20 13:08:56,247 DEBUG [main] [index.BTreeIndex] loading 
 2012-07-20 13:08:56,247 DEBUG [main] [index.BTreeIndex] loading 
 2012-07-20 13:08:56,250 DEBUG [main] [index.BTreeIndex] loading 
 2012-07-20 13:08:56,310 INFO  [main] [cli.services] Starting 2 command 
 processor threads 
 2012-07-20 13:08:56,315 INFO  [main] [cli.services] Starting query server 
 2012-07-20 13:08:56,316 INFO  [main] [cli.services] Starting database 
 compactor (60 minute interval) 
 2012-07-20 13:08:56,351 INFO  [clojure-agent-send-off-pool-3] 
 [cli.services] Beginning database compaction 
 2012-07-20 13:08:56,372 DEBUG [clojure-agent-send-off-pool-2] 
 [component.Container] Container 
 org.eclipse.jetty.server.Server@3c716932

Re: [Puppet Users] problems with puppetdb

[Chris Price]

Hello Pete,

Do you have a reliable way to reproduce the port issue that you mentioned? 
 We'd like to troubleshoot it further but haven't found any way to 
reproduce it on our end yet.

If you're not getting log output in /var/log/puppetdb, can you please try 
the following?:

1. Edit the file /etc/puppetdb/conf.d/config.ini, and comment out the 
logging-config line.
2. Run this command:

java -jar /usr/share/puppetdb/puppetdb.jar services -c /etc/puppetdb/conf.d

This should allow you to see the output on the console as puppetdb is 
trying to start up.  If you can copy and paste that output for us, it may 
be helpful.

Thanks!
Chris


On Monday, July 16, 2012 5:37:16 PM UTC-7, Pete wrote:

 On 17 July 2012 10:19, Deepak Giridharagopal dee...@puppetlabs.com 
 wrote: 
  On Mon, Jul 16, 2012 at 5:13 PM, Peter Brown rendhal...@gmail.com 
 wrote: 
  
  On 17 July 2012 03:15, Chris Price ch...@puppetlabs.com wrote: 
   Also, would you mind sharing a bit more info about your setup?  I 
   presume: 
   
   * You are installing from the puppetlabs apt repos? 
  
  yes 
  
   * Your upgrade was from puppetdb 0.9.1 to 0.9.2? 
  
  and yes. 
  
  thanks again Deepak. 
  I shall add myself to the ticket. 
  It seems it's a problem with jetty because all the other settings seem 
  to be working fine. 
  I am guessing Jetty is part of the puppetdb install? 
  I tried installing jetty as well but still get the same results. 
  
  
  Indeed, that's part of the install. It's embedded in PuppetDB as a 
 library. 
  The ports thing is super-weird...we definitely didn't change them as 
 part of 
  the upgrade. In fact, your configs should have remained unchanged. How 
 are 
  you determining what ports it's listening on? What does 
  /var/log/puppetdb/puppetdb.log say during startup? 

 i am using netstat -nap and grepping for the PID to find out what 
 ports it's using. 

 I am not not getting any logging into /var/log/puppetdb/puppetdb.log 
 It was working yesterday but nothing there today. 
 I just tried running it under the official oracle jre 1.6.0.33 and same 
 results. 
 I have also tried reinstalling from scratch and get the same results. 

 I am at a loss as to what to try next. 

  
  Thanks! 
  deepak 
  
  -- 
  Deepak Giridharagopal / Puppet Labs / grim_radical 
  
  -- 
  You received this message because you are subscribed to the Google 
 Groups 
  Puppet Users group. 
  To post to this group, send email to puppet-users@googlegroups.com. 
  To unsubscribe from this group, send email to 
  puppet-users+unsubscr...@googlegroups.com. 
  For more options, visit this group at 
  http://groups.google.com/group/puppet-users?hl=en. 


-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/BoEHNeXgvsUJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] problems with puppetdb

[Chris Price]

Also, would you mind sharing a bit more info about your setup?  I presume:

* You are installing from the puppetlabs apt repos?
* Your upgrade was from puppetdb 0.9.1 to 0.9.2?

On Monday, July 16, 2012 9:36:40 AM UTC-7, Deepak Giridharagopal wrote:

 On Sun, Jul 15, 2012 at 7:42 PM, Peter Brown rendhal...@gmail.com wrote:

 Hi everyone,

 I got the new version installed and am now having a strange issue.
 my puppetdb server seems to start but then dies after a few seconds
 with no logging that i can find.
 I tried setting the log level to DEBUG but still nothing.

 I tried running by hand and discovered it couldn't read it's config
 files so i fixed that.
 It also wants write access to /usr/share/puppetdb
 This seems like strange place it would need write access to.
 Is the really necessary?
 It is also ringing security bells in my head so I am a bit hesitant to
 give it write access without knowing why.

 My puppetdb is running on latest ubuntu with latest openjdk 6


 I've created ticket http://projects.puppetlabs.com/issues/15536 to track 
 this; we'll take a look at that this iteration. Would you mind adding 
 yourself as a watcher on that ticket?

 Thanks for the report!

 deepak

 --
 Deepak Giridharagopal / Puppet Labs / grim_radical


-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/UF5A0GCai9UJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Fwd: possible changes to puppet config file

[Chris Price]

On Thursday, June 28, 2012 1:40:39 AM UTC-7, David Schmitt wrote:

 If you're at it: It is ugly that an environment master will 
 automatically pull in the puppetmaster settings too. Especially if the 
 manifests are in git and every branch is an environment. 


David,

Thanks for the feedback.  Could you explain your situation a bit further? 
 I'm trying to envision this, and it seems like it could only affect an 
agent running on the same node as the master--is that correct?  Because on 
the other agent nodes they won't have the same puppet.conf, and thus they 
won't read in those settings?  I would like to get a bug filed on this but 
just want to make sure that I understand the scenario first.

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/dFAOXsRsjb0J.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Fwd: possible changes to puppet config file

[Chris Price]

Hi everyone,

We've been doing some work lately to harden the pluginsync functionality
for Puppet 3.x.  An issue was brought to my attention by Jeff McCune:

In current versions of puppet, it's possible to configure things like your
vardir and libdir in any section of the config file; potentially, this
means that you can specify a different libdir for all three of [main,
master, agent].

This causes problems with respect to pluginsync; when you run an agent, it
will sync down plugins / modules / faces from the master into the *agent's*
libdir.  Then, when you try to run a face (even the help face), your
libdir will be set to the main libdir, and thus it won't have the content
that it needs from the previous agent run.

The basic problem here is that all of our various client-side programs
*must* share the same libdir.  Thus, it seems that we need to restrict the
ability to set these for individual client programs.

We have a short-term and a long-term solution in mind to resolve this.  In
the short term, we will simply disallow libdir and related settings from
appearing in any sections of puppet.conf other than main and master.
 (This will still allow the master to have a separate libdir from
client-side programs.)  The ticket and pull req for this are here:

http://projects.puppetlabs.com/issues/15211
https://github.com/puppetlabs/puppet/pull/875

Slightly longer term, we are thinking of simply removing support for
run-mode-specific configuration sections in the puppet.conf file.  We
would only allow three sections: main (possibly renamed to global or
similar), master, and ca.  (Obviously you could still specify
environments in there as well, though we probably should move those to a
separate config file in the future.)

This is filed as a ticket here:

http://projects.puppetlabs.com/issues/15212

Would love to hear any feedback that anyone has on this topic!

Thanks
Chris

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Re: HTTP 400 errors when using storeconfigs

[Chris Price]

Hi Matt,

I think it would be worth opening a ticket for this ( 
http://projects.puppetlabs.com/projects/puppet/issues/new ).  The fact that 
you are seeing it with both storeconfigs/mysql and puppetdb/postgres leads 
me to believe that the issue is more likely in puppet core than in either 
of the catalog storage backends.

It would also be useful if you could run the puppet master with the 
--trace command-line option (and possibly with --debug as well) and 
capture that log file.

It sounds like you are running the master via apache/passenger, correct?

A manifest file that could reproduce your setup would be ideal to attach to 
the ticket, but the VM will be very useful if it's not easy to put together 
such a manifest.  How large is the VM image?  It might be too big to attach 
directly to the ticket, but if you mention it in the ticket we can figure 
out the best way to get the file from you.

Thanks!
Chris

On Thursday, June 14, 2012 4:29:17 AM UTC-7, Matthew Burgess wrote:

 So, continuing this saga, I decided yesterday to try and make use of 
 puppetdb as it's supposed to have performance improvements over and 
 above storeconfigs. 

 My first change was to move from a MySQL to PostgreSQL database behind 
 storeconfigs.  That still showed the issues I'm seeing.  With 
 PostgreSQL in place, I then configured puppetdb, but I'm still seeing 
 these issues with concurrent users. 

 At this point, is it worth raising an issue at puppetlabs.com?  I have 
 the failing environment on a VM now, so if someone wants a copy/or 
 login details to it, I'm happy to provide them if it helps figure out 
 what's going on. 

 Thanks, 

 Matt. 


-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/NdraCH3guVAJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Re: puppetdb: UTF-8 byte sequence

[Chris Price]

No action necessary; we should be able to create repro scenarios that will 
help us provide more info in the warning message (and resolve the ticket 
that I mentioned).  If you happen to know (or are able to identify) which 
resource in your system is triggering the warning (because of a String that 
contains a non-UTF-8 byte sequence), it would be interesting to see what 
your resource looked like.  Otherwise, since the odds are high that the 
warning should be harmless, just let us know if you notice any other 
unusual behavior or problems that you suspect might be related to this.

Thanks again for the feedback!

On Thursday, June 14, 2012 3:20:07 AM UTC-7, A_SAAS wrote:

 Hi,

 I have no idea how I can help, tell me what to do and I would be glad to 
 help.


 Regards,
 Jeremy MAURO


 On Thu, Jun 14, 2012 at 12:11 AM, Chris Price ch...@puppetlabs.comwrote:

 Because the serialization format (JSON) and the database both require 
 UTF-8 character encoding for their data, puppetdb needs to encode strings 
 before it sends them from the puppet master to the puppetdb server.  Due to 
 limitations in Puppet's representation of strings (character encoding is 
 not explicitly specified), it's not possible for us to do anything too 
 fancy when we encounter a byte sequence that is not directly representable 
 in UTF-8.  Thus, when this scenario occurs, you will see the warning that 
 you mentioned.  This does mean that we will be discarding the invalid bytes.

  Whether or not this is cause for concern in your particular case depends 
 on which resource triggered the warning, and what your use case for that 
 resource is.  If the offending resource is an exported resource that other 
 nodes are relying on, then this could cause problems.  If the offending 
 resource is one that you query or report on, then your data could be skewed 
 slightly.  Otherwise, this is effectively harmless for you.

  One thing that we should do on our end, though, is try to provide a bit 
 more context to the warning message to help you try to identify which 
 resource is causing the warning.  To that end I've filed the following 
 ticket:

 http://projects.puppetlabs.com/issues/15016

 (Also worth noting: in the existing/old storeconfigs, the behavior for 
 handling this scenario is undefined... so for us, this warning is a first 
 step towards providing comprehensive, robust support for handling string 
 encoding.)

 We are definitely interested in hearing more details about your setup if 
 this does cause you any problems.

 Thanks for the feedback!
 Chris

 On Wednesday, June 13, 2012 6:06:38 AM UTC-7, jcbollinger wrote:



 On Wednesday, June 13, 2012 5:51:22 AM UTC-5, A_SAAS wrote:

 Me again regarding puppetdb, I have the following warning message:
 Jun 13 12:49:15 puppetmaster puppet-master[28444]: Ignoring invalid 
 UTF-8 byte sequences in data to be sent to PuppetDB

 Do I have to worry?


 I don't know any relevant specifics about PuppetDB, but on general 
 principles I would say that to the extent you rely on the data curated by 
 PuppetDB to be correct, yes, you should worry.  The message suggests data 
 stream corruption between PuppetDB and whatever other part of the master is 
 talking to it at that point.  Probably they disagree about what character 
 encoding to use, but whatever the cause of the problem, the message 
 suggests that PuppetDB interpreted the data in question differently than 
 its source intended.  There is a bug of some kind in there, so I would file 
 a ticket.


 John

 -- 
 You received this message because you are subscribed to the Google Groups 
 Puppet Users group.
 To view this discussion on the web visit 
 https://groups.google.com/d/msg/puppet-users/-/PZtYDMbV1XQJ.

 To post to this group, send email to puppet-users@googlegroups.com.
 To unsubscribe from this group, send email to 
 puppet-users+unsubscr...@googlegroups.com.
 For more options, visit this group at 
 http://groups.google.com/group/puppet-users?hl=en.




-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/5ljDNLRfadEJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Re: puppetdb: UTF-8 byte sequence

[Chris Price]

Because the serialization format (JSON) and the database both require UTF-8 
character encoding for their data, puppetdb needs to encode strings before 
it sends them from the puppet master to the puppetdb server.  Due to 
limitations in Puppet's representation of strings (character encoding is 
not explicitly specified), it's not possible for us to do anything too 
fancy when we encounter a byte sequence that is not directly representable 
in UTF-8.  Thus, when this scenario occurs, you will see the warning that 
you mentioned.  This does mean that we will be discarding the invalid bytes.

 Whether or not this is cause for concern in your particular case depends 
on which resource triggered the warning, and what your use case for that 
resource is.  If the offending resource is an exported resource that other 
nodes are relying on, then this could cause problems.  If the offending 
resource is one that you query or report on, then your data could be skewed 
slightly.  Otherwise, this is effectively harmless for you.

 One thing that we should do on our end, though, is try to provide a bit 
more context to the warning message to help you try to identify which 
resource is causing the warning.  To that end I've filed the following 
ticket:

http://projects.puppetlabs.com/issues/15016

(Also worth noting: in the existing/old storeconfigs, the behavior for 
handling this scenario is undefined... so for us, this warning is a first 
step towards providing comprehensive, robust support for handling string 
encoding.)

We are definitely interested in hearing more details about your setup if 
this does cause you any problems.

Thanks for the feedback!
Chris

On Wednesday, June 13, 2012 6:06:38 AM UTC-7, jcbollinger wrote:



 On Wednesday, June 13, 2012 5:51:22 AM UTC-5, A_SAAS wrote:

 Me again regarding puppetdb, I have the following warning message:
 Jun 13 12:49:15 puppetmaster puppet-master[28444]: Ignoring invalid 
 UTF-8 byte sequences in data to be sent to PuppetDB

 Do I have to worry?


 I don't know any relevant specifics about PuppetDB, but on general 
 principles I would say that to the extent you rely on the data curated by 
 PuppetDB to be correct, yes, you should worry.  The message suggests data 
 stream corruption between PuppetDB and whatever other part of the master is 
 talking to it at that point.  Probably they disagree about what character 
 encoding to use, but whatever the cause of the problem, the message 
 suggests that PuppetDB interpreted the data in question differently than 
 its source intended.  There is a bug of some kind in there, so I would file 
 a ticket.


 John



-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/PZtYDMbV1XQJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] selinux symlink patch

[Chris Price]

Hey folks,

I am reviewing the following pull request, which has to do with how puppet
deals with symlinks in selinux:

https://github.com/puppetlabs/puppet/pull/563

Just wondering if there is anyone out there who considers themselves strong
with selinux who has an opinion on this one way or the other.

Thanks in advance!
Chris

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Re: selinux symlink patch

[Chris Price]

Update: a little more digging reveals that the original selinux symlink
code came as a result of this ticket:

http://projects.puppetlabs.com/issues/2791

Still interested in feedback if anyone has any.


On Fri, Apr 6, 2012 at 12:58 PM, Chris Price ch...@puppetlabs.com wrote:

 Hey folks,

 I am reviewing the following pull request, which has to do with how puppet
 deals with symlinks in selinux:

 https://github.com/puppetlabs/puppet/pull/563

 Just wondering if there is anyone out there who considers themselves
 strong with selinux who has an opinion on this one way or the other.

 Thanks in advance!
 Chris


-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.