Re: [Puppet Users] error de conection

[Christopher Wood]

I haven't had that experience with puppet, but I have had it with other 
services.

Assuming you've gone through things like checking load, logs (for the 
puppetserver/puppet master), continuous ping, strace, and so on, I recommend 
that you capture packets on either side. Checking timestamps may show you if 
both sides of the tcp conversation are getting through. If they are you know 
the issue is isolated to one or both sides, if the packets aren't getting 
through then you know to check intervening switches and firewalls.

Especially the "connection reset by peer" part. If one end is hanging and the 
other end reports a reset connection, to me that sounds like something in the 
middle.

On Wed, Apr 11, 2018 at 04:43:56AM -0700, Javier Velasco wrote:
>when I run in the agent the command puppet master --debug --no-daemonize
>stays waiting in the line debug: Finishing transaction -612625138 and does
>not deliver the certificate, I run the command
> 
>openssl s_client -connect puppetc4: 8140  and habeces connects and other
>times, when I run again the command puppet master --debug --no-daemonize
> 
>err: Could not retrieve catalog from remote server: Connection reset by
>peer - SSL_connect
> 
>notice: Using cached catalog
> 
>err: Could not retrieve catalog; skipping run
> 
>debug: Executing '/ etc / puppet / etckeeper-commit-post'
> 
>debug: report supports formats: b64_zlib_yaml pson raw yaml; using pson
> 
>err: Could not send report: Connection reset by peer - SSL_connect
> 
>I would appreciate the help possible
> 
>--
>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 [1]puppet-users+unsubscr...@googlegroups.com.
>To view this discussion on the web visit
>
> [2]https://groups.google.com/d/msgid/puppet-users/19c0b7e2-779f-4877-8397-c129be232f3f%40googlegroups.com.
>For more options, visit [3]https://groups.google.com/d/optout.
> 
> References
> 
>Visible links
>1. mailto:puppet-users+unsubscr...@googlegroups.com
>2. 
> https://groups.google.com/d/msgid/puppet-users/19c0b7e2-779f-4877-8397-c129be232f3f%40googlegroups.com?utm_medium=email_source=footer
>3. https://groups.google.com/d/optout

-- 
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/20180413173401.tzghgam3tyvehnpm%40iniquitous.heresiarch.ca.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] master+agent setup on vms with proxy

[Greg Bro]

  Hello,
 i am trying to run a master+agent setup on 2 Centos 7 vms with one 
ethernet adapter for internetconnection and one for the connection between 
the 2 vms.
 But I cant seem to get them together. Since i am behind a company proxy i 
entered the proxy in the yum.conf and the /etc/environment to get the 
packages. 
I have given each vm an ip(ping works) in the same net for the 2. adapters 
and have entered the ips and hostnames in /etc/hosts.
Anything helps. 

-- 
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/e3743d7a-1096-45dd-b162-7ef498c2254e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] error de conection

[Javier Velasco]

when I run in the agent the command puppet master --debug --no-daemonize 
stays waiting in the line debug: Finishing transaction -612625138 and does 
not deliver the certificate, I run the command 


openssl s_client -connect puppetc4: 8140  and habeces connects and other 
times, when I run again the command puppet master --debug --no-daemonize

err: Could not retrieve catalog from remote server: Connection reset by 
peer - SSL_connect

notice: Using cached catalog

err: Could not retrieve catalog; skipping run

debug: Executing '/ etc / puppet / etckeeper-commit-post'

debug: report supports formats: b64_zlib_yaml pson raw yaml; using pson

err: Could not send report: Connection reset by peer - SSL_connect

I would appreciate the help possible

-- 
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/19c0b7e2-779f-4877-8397-c129be232f3f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] [ANN] Resource API v1.1 Release

[David Schmitt]

Hi all,

We're pleased to announce that version 1.1 of the Resource API has been
released yesterday.

The Resource API provides a simple way to create new native resources in
the form of types and providers for Puppet. It is provided as a Ruby gem to
be referenced within modules. Support for it has been included as an
experimental feature in version 1.4 of the Puppet Development Kit (pdk new
provider). Use the resource_api module
 to deploy it in your
infrastructure.

The new release of the Resource API provides the following enhancements:

   - Arrays are now fully supported as data types (v1.1.0)
   - Read only and init only attributes have that status now fully enforced
   (v1.0.3)

The new release also contains the following notable bugfixes:

   - PDK-911 : handling of
   ensure values changed to use strings: Previous to v1.0.3, in some cases
   ensure values of 'absent' and 'present' would be transformed to ruby
   symbols before passing it on to the provider. This behavior was
   inconsistent with both puppet and other Enums in the Resource API, that
   would always use strings. Providers now need to return and accept the
   strings 'absent' and 'present' instead of the :absent and :present
   symbols.
   - PDK-919 : Boolean
   attributes now work in all cases: In some cases
    puppet can ignore true
   boolean values. The Resource API now works around the issue in a
   transparent way that requires no change to providers.

See the CHANGELOG

for a full list of changes.

We encourage all module developers to review the Resource API and use it
when creating types and providers. For reference, there is an example of
its usage in a branch

of the apt module.

Please let us know of your experiences with the Resource API, either here,
on Slack  (#forge-modules), or on the github repo
.


Thanks,

David
-- 
Cheers, David

https://twitter.com/dev_el_ops

-- 
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/CALF7fHbTL5U2iU-wcVnULerPvw08%2B%3D%2BxgoKvytNrDRLhpOcRrQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] How can one communicate the $confdir to the catalog builder?

[Henrik Lindberg]

On 12/04/18 14:58, jcbollinger wrote:



On Wednesday, April 11, 2018 at 11:28:12 AM UTC-5, Henrik Lindberg wrote:

On 11/04/18 18:21, jcbollinger wrote:
 > I'm writing a module for Puppet self-management, or at least I
think I
 > am.  I was surprised to not find very much along those lines on the
 > Forge, and maybe I should take that as a bad sign, but I want to
explore
 > it at least a little bit.  Maybe I just didn't find the right search
 > terms -- searching there for "puppet" is not very useful.
 >
 > Anyway, I've run into a snag with a threshold issue: how to find the
 > config file(s) to manage in the first place.  I know where Puppet
stores
 > its config files by default, for various versions of Puppet and for
 > various operational contexts, but with the existence of the
--confdir
 > option that can be specified on a per-run basis, it is not safe to
 > assume that the config files that informed the current Puppet run
is in
 > the default location (and those are the ones I want to manage). 
In any

 > case, I'm lazy, so I'd rather get Puppet to tell me what it already
 > knows than try to recompute it.
 >
 > But there does not seem to be a standard fact that communicates this
 > information (at least, 'puppet facts' does not print one), and
I'm not
 > seeing any appealing ways to extract the necessary information
from a
 > custom fact's runtime context.  I do see at least one nasty,
tricksome,
 > system-dependent way, but I'm more likely to chuck the whole idea
than
 > go there.  Am I missing some clean way to write a custom fact for
this
 > purpose?  Or does someone have an alternative to suggest?
 >

Have you read the documentation regarding $settings ?

https://puppet.com/docs/puppet/5.5/lang_facts_and_builtin_vars.html#puppet-master-variables




- henrik



Thanks, Henrik, I'm not sure I had read those in detail, since they come 
under the heading of variables set by the master, and the whole problem 
is that the master doesn't have the wanted information.  Still, having 
now read them, I find that the documentation seems to agree with my 
expectations.  In particular:


Note that, other than $environment and $clientnoop, the agent node’s
settings are not available in manifests. If you wish to expose them
to the master in this version of Puppet, you will have to create a
custom fact.


Creating a custom fact to report on the agent's /dynamic/ $confdir 
setting, as recommended by those docs, is precisely what I would like to 
do.  What I'm struggling with is how the fact implementation can 
determine the value for such a fact, inasmuch as the value I want is a 
property of the puppet (agent) process on whose behalf Facter is 
computing facts.




I recall now that we have a ticket with a request to make agent settings 
available on the master side. No progress on that for quite some time 
though. Not sure if ticket is still open or if it was closed in the last 
big triage. I assume it could be implemented as sending all of the 
settings as one fact. Or - indeed as you plan, just the actual setting 
you are interested in.


- henrik

--

Visit my Blog "Puppet on the Edge"
http://puppet-on-the-edge.blogspot.se/

--
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/paprm7%24t64%241%40blaine.gmane.org.
For more options, visit https://groups.google.com/d/optout.