Re: [Puppet Users] Puppet 5 Repo Mirror
Sorry it has taken me so long to get back here and thank you! This resolved my problems and I can move on to upgrading Josh On Thursday 13 June 2024 at 12:30:02 UTC+1 Dietrich, Stefan wrote: > Hello Josh, > > while not available anymore on the web, they can be still pulled via rsync > from rsync://rsync.puppet.com/packages/yum/puppet5/ > The README.txt contains additional information for mirroring: > https://yum.puppetlabs.com/README.txt > > Regards, > Stefan > -- 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/32cfbe4e-1310-4906-a154-2b505cd04745n%40googlegroups.com.
[Puppet Users] Puppet 5 Repo Mirror
I know this is a longshot... I have recently changed job and have inherited a mess of a Puppet 5/CentOS 7 environment. I know I need to migrate off both of these and that is my intention In the short term, however, I can't fix anything because the puppetlabs yum repo for puppet 5 disappeared a couple of years back: https://yum.puppetlabs.com/puppet5/ Does anyone know of any current working puppet 5 yum repositories? I just want to make a local mirror that I can use before I embark on the process of uplifting everything Thanks Josh -- 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/de4cbb8b-af0d-4f00-8c8c-6baa97c2e56dn%40googlegroups.com.
[Puppet Users] Re: Could not autoload puppet/provider/apt_key/apt_key
The error occurs because the module is using Ruby 2.6 syntax (such as endless ranges) but Puppet 6 vendors Ruby 2.5. On Friday, February 23, 2024 at 7:39:40 AM UTC-8 Denny Fuchs wrote: > Hi, > > it seems, we have to upgrade to Puppet7. The error is gone, with this > version. > > Denny Fuchs schrieb am Freitag, 23. Februar 2024 um 16:10:02 UTC+1: > >> Hello, >> >> because of Bookworm and apt-key, we have to upgrade apt and stdlib on our >> Puppet6 Server. I've get on all nodes with Debian Buster: >> >> Error: Could not autoload puppet/provider/apt_key/apt_key: >> /etc/puppetlabs/code/environments/newmod/modules/apt/lib/puppet/provider/apt_key/apt_key.rb:100: >> >> syntax error, unexpected ']' >> ... key_long: fingerprint[-16..], # last 16 characters of fin... >> ... ^ >> /etc/puppetlabs/code/environments/newmod/modules/apt/lib/puppet/provider/apt_key/apt_key.rb:101: >> >> syntax error, unexpected ']' >> ... key_short: fingerprint[-8..], # last 8 characters of fing... >> ... ^ >> /etc/puppetlabs/code/environments/newmod/modules/apt/lib/puppet/provider/apt_key/apt_key.rb:103: >> >> syntax error, unexpected tLABEL, expecting '=' >> key_type: nil, >> ^ >> /etc/puppetlabs/code/environments/newmod/modules/apt/lib/puppet/provider/apt_key/apt_key.rb:103: >> >> Can't assign to nil >> key_type: nil, >>^ >> /etc/puppetlabs/code/environments/newmod/modules/apt/lib/puppet/provider/apt_key/apt_key.rb:104: >> >> syntax error, unexpected ',', expecting keyword_end >> ...ed: Time.at(pub_split[5].to_i), >> ... ^ >> /etc/puppetlabs/code/environments/newmod/modules/apt/lib/puppet/provider/apt_key/apt_key.rb:105: >> >> syntax error, unexpected ',', expecting keyword_end >> ...y_expired: pub_split[1] == 'e', >> ... ^ >> /etc/puppetlabs/code/environments/newmod/modules/apt/lib/puppet/provider/apt_key/apt_key.rb:107: >> >> syntax error, unexpected '}', expecting keyword_end >> } >> ^ >> Error: Failed to load custom type 'apt_key' from >> '/etc/puppetlabs/code/environments/newmod/modules/apt/lib/puppet/type/apt_key.rb': >> >> Could not autoload puppet/provider/apt_key/apt_key: >> /etc/puppetlabs/code/environments/newmod/modules/apt/lib/puppet/provider/apt_key/apt_key.rb:100: >> >> syntax error, unexpected ']' >> >> any idea, what happens ? I've tried also >> >> puppet generate types --environment ... >> >> but without success ... >> >> any suggestions ? >> >> cu denny >> >> -- 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/9e8b5054-c8fa-46b0-b9f3-95f50e298f2dn%40googlegroups.com.
[Puppet Users] Re: Binary file in eyaml breaking use of Deferred due to pson
$mykeytab = lookup('mymodule::mykeytab')
file { '/path/to/mykeytab':
ensure => file,
content => $mykeytab,
}
Replace "content => $mykeytab" with "content => Binary($mykeytab)" so that
the data is serialized to the agent correctly.
See
https://www.puppet.com/docs/puppet/7/lang_data_binary.html#reference_template-create-binary-typed-content
for more details.
Also note PSON has been removed in Puppet 8.
Josh
--
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/16e04c4f-507c-4eb6-aa02-413b6449a00fn%40googlegroups.com.
Re: [Puppet Users] RHEL 9 agent support?
On Mon, Jun 13, 2022 at 1:58 PM 'Tim Mooney' via Puppet Users < puppet-users@googlegroups.com> wrote: > > RHEL 9 has been out for a few weeks. > > I see OpenSource puppet agent 7 and puppet bolt packages for RHEL 9, but > no OpenSource puppet agent 6 releases. > > Are there plans to package puppet agent 6 for RHEL 9? > > Tim > -- > Tim Mooney tim.moo...@ndsu.edu > Enterprise Computing & Infrastructure / > Division of Information Technology/701-231-1076 (Voice) > North Dakota State University, Fargo, ND 58105-5164 > > -- > 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/924b35f-bda5-6ae5-efe-d05a8de7aec%40ndsu.edu > . > Hi Tim, Puppet 6 is released quarterly and support for RHEL9 will go out in the next 6.x release. In the meantime, you can try nightly builds from https://nightlies.puppet.com/yum/puppet6-nightly/el/9/x86_64 Josh -- Josh Cooper Software Engineer j...@puppet.com -- 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/CA%2Bu97umrJVa%3DA0p8N1NyFjWhamqtRa3W861ohdNDQfB0nKA85g%40mail.gmail.com.
Re: [Puppet Users] Correction: Puppet Platform 6.27.1 (not 6.27.0) is now available!
On Thu, Apr 21, 2022 at 7:32 AM Steve Huston wrote: > I upgraded this morning, and found that the package is named > puppet-agent-6.27.1-1.el7.x86_64, however the program itself also > thinks it is 6.27.0 which confuses the puppet_agent module: > > Apr 21 10:25:03 coathook puppet-agent[11565]: Starting Puppet client > version 6.27.0 > Apr 21 10:26:54 coathook puppet-agent[11569]: Could not update: > Execution of '/usr/bin/yum -d 0 -e 0 -y downgrade puppet-agent-6.27.0' > returned 1: Error: Nothing to do > Apr 21 10:26:54 coathook puppet-agent[11569]: > (/Stage[main]/Puppet_agent::Install/Package[puppet-agent]/ensure) > change from '6.27.1-1.el7' to '6.27.0' failed: Could not update: > Execution of '/usr/bin/yum -d 0 -e 0 -y downgrade puppet-agent-6.27.0' > returned 1: Error: Nothing to do (corrective) > Apr 21 10:26:54 coathook puppet-agent[11569]: > (/Stage[main]/Puppet_agent::Install/Puppet_agent_end_run[6.27.0]) > Dependency Package[puppet-agent] has failures: true > Apr 21 10:26:54 coathook puppet-agent[11569]: > (/Stage[main]/Puppet_agent::Install/Puppet_agent_end_run[6.27.0]) > Skipping because of failed dependencies > > > This is a bug in the puppet_agent module when using the "auto" parameter, see https://tickets.puppetlabs.com/browse/MODULES-11315 You can workaround the issue by specifying the desired version explicitly. The module assumes the version of the puppet library the compiler is using (derived from Puppet::PUPPETVERSION) is the same as the version of the puppet-agent package. The versions are usually updated together, but it is not always true, as sometimes we update ruby/openssl/curl in the puppet-agent package due to CVEs without making changes to the puppet library. On Tue, Apr 19, 2022 at 7:07 PM Puppet Product Updates > wrote: > > > > Correction: An email sent earlier erroneously said that Puppet Platform > 6.27.0 was released. This should have said Puppet Platform 6.27.1. Thanks > for your understanding! > > > > On Tue, Apr 19, 2022 at 3:49 PM Puppet Product Updates < > puppet-product-upda...@puppet.com> wrote: > >> > >> The release contains new features, minor enhancements, and bug fixes > including: > >> > >> > >> > >> Agent 6.27.1 > >> > >> Adds macOS 12 (x86_64) as a supported Agent platform > >> > >> Allows use of puppet certificate for client HTTPS authentication with > external CAs > >> > >> > >> > >> PuppetDB 6.21.0 > >> > >> Ubuntu 20.04 and SUSE Linux Enterprise 15 are now supported. > >> > >> PuppetDB will no longer run a garbage collection on startup. This may > substantially reduce the time required before PuppetDB begins accepting > commands and queries. > >> > >> PuppetDB should require much less time and memory when parsing some PQL > queries > >> > >> The fact path GC now runs no more than once every 24 hours by default. > This should be much less expensive in most cases, in exchange for a > potentially slower response to the disappearance of individual fact paths. > >> > >> > >> > >> Server 6.19.0 > >> > >> Adds SUSE Linux Enterprise 15 as supported Server platform > >> > >> Server CA now supports using a type 2 key identifier > >> > >> > >> > >> > >> > >> For the full list of changes, check out the release notes: > https://puppet.com/docs/puppet/6/release_notes_osp.html > > > > -- > > 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/CAFH7jMW2%3DMTFtgAAJGzqisvOrBXdX_qUac6%2BRCWba30ODRuRfA%40mail.gmail.com > . > > > > -- > Steve Huston - W2SRH - Unix Sysadmin, PICSciE/CSES & Astrophysical Sci > Princeton University |ICBM Address: 40.346344 -74.652242 > 345 Lewis Library |"On my ship, the Rocinante, wheeling through > Princeton, NJ 08544 | the galaxies; headed for the heart of Cygnus, > (267) 793-0852 | headlong into mystery." -Rush, 'Cygnus X-1' > > -- > 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/CAGdQDTosMkGwf3uVQjPqzUShtc_QsbHjN87_SbCrPjrrwUbjmg%40mail.gmail.com > . > -- Josh Cooper Software Engineer j...@puppet.com -- 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/CA%2Bu97ukJaRSfjdrk3YZU0q1QZS3PFbgw%2Brg%2B%3D%3D03RhBVUR_Hag%40mail.gmail.com.
Re: [Puppet Users] File content misrecognised as checksum
On Wed, Jan 12, 2022 at 8:59 AM Iain Hallam wrote:
> I find myself needing to manage a file that has content that to Puppet
> looks like a checksum. It isn't, but because Puppet sees any file content
> line beginning with "{", 3 to 5 characters, "}", as a checksum, it doesn't
> accept the content but instead tries to find the file in a filebucket...
>
>
> https://github.com/puppetlabs/puppet/blob/2f14ddd269c26cba36771d9b3464c2c29422e46a/lib/puppet/type/file/content.rb#L49
>
> I actually need to store "{CRYPT}$..." which isn't one of Puppet's
> recognised types.
>
> It seems there's no way to work around this in pure Puppet code, so I
> can't manage those files without doing something hackish, like putting a
> modified form of the content in a file alongside then having a script on
> the machine that puts it in the correct place without the modifications,
> but the issue for removing this behaviour was last updated in 2018:
>
I'd use the "checksum" and "checksum_value" parameters along with the
"source" parameter. That way the agent can determine if the file needs
updating without needing the full content in the catalog, and the agent can
download the source as needed, potentially from a regular file server, e.g.
https://
> https://tickets.puppetlabs.com/browse/PUP-1043
>
> It says it will now target Puppet 7, which came and went some time ago.
> Does anyone know if there will be a new target for this?
>
> Thanks,
>
> Iain Hallam.
>
> --
> 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/72752c00-68db-4db2-98ff-b2d42ddeadedn%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/72752c00-68db-4db2-98ff-b2d42ddeadedn%40googlegroups.com?utm_medium=email_source=footer>
> .
>
--
Josh Cooper
Software Engineer
j...@puppet.com
--
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/CA%2Bu97ukKrV6TDs34nh5EbyZ5WnGa-vNLAcLGAf9napOQHBZP%2BQ%40mail.gmail.com.
Re: [Puppet Users] Does Puppet still execute in random order?
On Mon, Jun 21, 2021 at 4:37 PM Sandra Schlichting wrote: > Dear all =) > > It have been +5 years since I used Puppet at my previous job, and back > then I recall Puppet executed the tasks in random order, and I had to glue > all the tasks together to get them to be executed sequential. > > I recall something about Puppet have been completely rewritten since, so I > was wondering if this random order behaviour is still present? > > Hugs, > Sandra =) > > > -- > 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/12a3c096-2592-4ee2-a9bf-4fb4661785d7n%40googlegroups.com > <https://groups.google.com/d/msgid/puppet-users/12a3c096-2592-4ee2-a9bf-4fb4661785d7n%40googlegroups.com?utm_medium=email_source=footer> > . > The magic reordering business was deprecated and removed, and replaced with "manifest ordering". There's more details in https://puppet.com/docs/puppet/7/lang_relationships.html and https://puppet.com/blog/introducing-manifest-ordered-resources/ Josh -- Josh Cooper Software Engineer j...@puppet.com -- 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/CA%2Bu97un%2B%2BXUORj6QAjQrm5TCGDM4Jie-PnKdSkVtvsBYPZ48Lw%40mail.gmail.com.
Re: [Puppet Users] Windows exec resource cannot find command error
On Tue, Dec 8, 2020 at 10:37 AM Michael Watters wrote:
> Here is the exact error message.
>
> Info: /Stage[main]/Dart::Abstract::Windows_node/File[c:/program
> files/telegraf/telegraf.conf]: Scheduling refresh of Exec[c:/program
> files/telegraf/telegraf.exe --service install]
> Error: Could not find command 'c:/program'
> Error: /Stage[main]/Dart::Abstract::Windows_node/Exec[c:/program
> files/telegraf/telegraf.exe --service install]/returns: change from
> 'notrun' to ['0'] failed: Could not find command 'c:/program'
>
> The manifest resource is defined as follows.
>
> exec { 'c:/program files/telegraf/telegraf.exe --service install':
> cwd => 'c:/program files/telegraf',
> refreshonly => true,
> }
>
> On Tuesday, December 8, 2020 at 1:29:55 PM UTC-5 Michael Watters wrote:
>
>> I tried that as well and it simply results in an error stating "Could not
>> find command: c:/program".
>>
>
Probably need to quote the executable due to spaces:
exec { '"c:/program files/telegraf/telegraf.exe" --service install':
...
>> On Monday, December 7, 2020 at 2:06:53 PM UTC-5 Martin Alfke wrote:
>>
>>> Have you tried using the full path to the executable?
>>>
>>> exec { 'c:/program files/telegraf/telegraf.exe --service install' :
>>> ...
>>> }
>>>
>>> > On 7. Dec 2020, at 18:17, Michael Watters wrote:
>>> >
>>> > I have an exec resource in a manifest for our Windows nodes however
>>> the command is failing each time that puppet runs. Here is the definition
>>> of the resource and a screenshot of the error.
>>> >
>>> > ~> exec { 'telegraf.exe --service install':
>>> > cwd => 'c:/program files/telegraf',
>>> > refreshonly => false,
>>> > }
>>> >
>>> >
>>> >
>>> > Is there a way to resolve this? I've tried changing the path
>>> parameters which doesn't make any difference.
>>> >
>>> >
>>> >
>>> > --
>>> > 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...@googlegroups.com.
>>> > To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/puppet-users/ca2819ca-1930-4842-8ed8-0820f19ea343n%40googlegroups.com.
>>>
>>>
>>> --
> 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/88f80e94-2efc-4ca7-bfb1-70abd422f44dn%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/88f80e94-2efc-4ca7-bfb1-70abd422f44dn%40googlegroups.com?utm_medium=email_source=footer>
> .
>
--
Josh Cooper | Software Engineer
j...@puppet.com
--
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/CA%2Bu97u%3D3f_5Dun0qTJdRqkFMk--DUHktsF61-pcBumSyWS-8HA%40mail.gmail.com.
Re: [Puppet-dev] Re: [Puppet Users] Upcoming changes to the rolling 'puppet' repos!
Thanks Pete for putting this together! Some comments below: On Wed, Dec 2, 2020 at 12:33 AM Peter Meier wrote: > Hi All, > > > Tomorrow morning (~9am Pacific) we'll be updating the rolling 'puppet' > > repos to point to the new 'puppet7' release from a couple of weeks ago. > > If you're already using the 'puppet' release packages (such > > as http://yum.puppetlabs.com/puppet-release-el-7.noarch.rpm > > <http://yum.puppetlabs.com/puppet-release-el-7.noarch.rpm>), your repos > > will start pointing to puppet7 tomorrow. > > > Anybody having VMs / Baremetals / ... using VLANs: You will run into a > regression with Facter 4 that will stop puppet 7 from working on these > machines: > > https://tickets.puppetlabs.com/browse/FACT-2870 > > The fix is there, but there is no release yet containing the fix. So > it's worth holding these machines of from being updated on the rolling > repos. > All resolved issues should be available in nightly puppet7 builds, such as http://nightlies.puppet.com/yum/puppet7-nightly-release-el-8.noarch.rpm. It'd be great to get confirmation in the next few days that these issues are in fact fixed. Also all puppet6 builds include facter4 as an opt-in feature, so you can try it out before upgrading to puppet7: # puppet --version 6.19.1 # puppet facts find | grep facter "facterversion": "3.14.14", # puppet config set facterng true --section main # puppet facts find | grep facter "facterversion": "4.0.43", > > Additionally, there are a couple of regressions regarding how networking > facts are being reported by Facter 4: > > https://tickets.puppetlabs.com/browse/FACT-2871 > https://tickets.puppetlabs.com/browse/FACT-2872 > > If you are depending on these facts in your manifests (e.g. in a > condition), it might be the case that puppet will do something > differently. I suggest checking your manifests for the usage of these > facts. > > I didn't check the bug tracker thoroughly for other regressions, but I > have seen a few more. So it might worth looking into it, as regressions > in fact reporting can have unintended side-effects. > We've started adding a 'platform_7.1' label to keep track of these, see https://tickets.puppetlabs.com/issues/?jql=labels%20%3D%20platform_7.1 > And really only cosmetic wise, you get a bunch of warnings in puppet 7 > for the user and exec types: > > https://tickets.puppetlabs.com/browse/MODULES-10876 > https://tickets.puppetlabs.com/browse/PUP-10790 > > They are not really an issue, but might affect you if you are parsing > the output. E.g. filtering cron output -> cron emails are sent out with > these alerts. > > Other than that: Puppet 7 runs smoothly, be sure to re-install your > gems, as it switches to Ruby 2.7 > > best > > ~pete > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to puppet-dev+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-dev/354bd76b-c85c-3026-9906-b7c3d20adf3b%40immerda.ch > . > Josh -- Josh Cooper | Software Engineer j...@puppet.com -- 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/CA%2Bu97um70PU8uvnCBYensFy5NejjoKF7LaBNPGLzmE74xyk%2B-w%40mail.gmail.com.
Re: [Puppet Users] Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: no parameter named 'quick_check'
On Tue, Sep 15, 2020 at 5:25 AM pkraw...@gmail.com wrote: > So I've done some research on the puppet generate types command. I'm > seeing many different results from not having issues to causing issues with > puppet apply and puppet agent executions. We fixed an issue in 6.18.0 (https://tickets.puppetlabs.com/browse/PUP-9602) that caused "puppet apply" to fail in some cases if "puppet generate types" had been run previously. > If I was to run this command and things go wrong, how do you reverse > it? Remove the .resource_types directory? > > On Friday, August 28, 2020 at 2:47:26 PM UTC-4 pkraw...@gmail.com wrote: > >> Justin, yes it's happening in all environments which leads me to believe >> it's related to an old copy >> in /opt/puppetlabs/puppet/cache/lib/puppet/type. Still trying to wrap my >> head around why one domain installation is fine and the other domain >> installation is not. >> >> Here is the contents of that directory which works: >> [root@myserverlab type]# pwd >> /opt/puppetlabs/puppet/cache/lib/puppet/type >> [root@myserverlab type]# ls -al >> total 24 >> drwxr-xr-x 2 root root 77 Jul 16 16:04 . >> drwxr-xr-x 6 root root 61 Feb 3 2020 .. >> -rw-r--r-- 1 root root 1706 Jul 16 16:04 anchor.rb >> -rw-r--r-- 1 root root 6921 Jul 16 16:04 file_line.rb >> -rw-r--r-- 1 root root 1863 May 1 2017 httparch.rb >> -rw-r--r-- 1 root root 6957 Jul 13 17:04 httpfile.rb >> [root@myserverlab type]# >> >> Here is the contents of the directory that doesn't work: >> [root@myserverprod type]# pwd >> /opt/puppetlabs/puppet/cache/lib/puppet/type >> [root@myserverprod type]# ls -al >> total 24 >> drwxr-xr-x 2 root root 77 Sep 30 2018 . >> drwxr-xr-x 6 root root 61 Apr 24 2017 .. >> -rw-r--r-- 1 root root 1752 Sep 30 2018 anchor.rb >> -rw-r--r-- 1 root root 7113 Sep 30 2018 file_line.rb >> -rw-r--r-- 1 root root 1863 May 15 2017 httparch.rb >> -rw-r--r-- 1 root root 6357 Apr 24 2017 httpfile.rb >> [root@myserverprod type]# >> >> You can clearly see the date and size difference of httpfile.rb. I >> quadruple checked the puppet module directory on the prod server and the >> code does have the quick_check parm. For some reason it is just not >> refreshing the server cache. Both domains have a value of 0 for >> environment_timeout for each environment. >> >> On Friday, August 28, 2020 at 2:32:05 PM UTC-4 Justin Stoller wrote: >> >>> On Fri, Aug 28, 2020 at 10:14 AM pkraw...@gmail.com >>> wrote: >>> Great info but I think I might have found the issue. So we don't use r10k to deploy code we use a different tool. But what I found is on the puppet server (master) the httpfile.rb in /opt/puppetlabs/puppet/cache/lib/puppet/type is the older version. >>> >>> I think puppet/cache is read by the agent not the server. I would expect >>> that to cause problems on applying a catalog from the server, not result in >>> a failed compilation. But barring a .resource_tyeps directory existing in >>> an environment it must be an incorrect version of the httpfile.rb in the >>> server's loadpath. >>> >>> I didn't find any ./resource_types directory in our environment directories so not sure if we are using environment isolation or not. >>> >>> Just to clarify it will be ".resource_types" with a leading dot and will >>> be hidden by default. [1] >>> >>> As part of Justin's suggestion to allow the DELETE option to be valid, I had to restart each of our 4 puppet servers so according to some of this conversation, that should have refreshed the cache right? >>> >>> Restarting or reloading will evict the in memory cache so if you have a >>> very long environment_timeout it will work as well as doing an eviction of >>> all your environments. It will not however remove any old files in your >>> .resources_types directory. You will need to run the `puppet generate >>> types` command with `--force` for that. >>> >>> What else is odd is the domain where the quick_check parm is work seems to be getting refreshed somehow in /opt/puppetlabs/puppet/cache/lib/puppet subdirectories (just looking at time stamps). The deploy process works the same in that domain along with the domain where quick_check is not working. >>> >>> Can you validate that the failures happen not along a "domain" but along >>> puppet environments. Like all the nodes that use httpfile in production >>> have this failure but those in staging don't have this issue? If you have >>> some succeeding and some failing I would expect this to be the environment >>> to be the condition causing the different behavior. >>> >>> Since the /opt/puppetlabs/bin/puppet generate types --environment production --force operates by environment, could this possible break the environment as well? These are production boxes I need to run this on and want to make sure I don't break anything. Also using the environment parm will this then setup environment
Re: [Puppet Users] Is "Sensitive" broken?
On Wed, Sep 9, 2020 at 11:16 PM 'Dirk Heinrichs' via Puppet Users <
puppet-users@googlegroups.com> wrote:
> Am Mittwoch, den 09.09.2020, 08:59 -0700 schrieb Josh Cooper:
>
> The issue you're running into is due to the sensitive value being
> interpolated:
>
> content => "${foo}\n"
>
> If you reference the Sensitive variable directly, then it will work as
> expected:
>
> content => $foo
>
>
> OK, thanks a lot. But then I'd loose the trailing "\n".
>
To interpolate sensitive values, you currently have to unwrap the sensitive
value, interpolate the value, and then rewrap as sensitive:
$var = Sensitive('a')
$var2 = Sensitive("${var.unwrap}\n")
file { '/tmp/sensitive.txt':
ensure => file,
content => $var2
}
> And it's also quite counterintuitive, isn't it?
>
Yes, I agree the current behavior is surprising and not easy to work with,
which is why I filed PUP-10092 :)
Think "exec", where it's sometimes needed to provide a password as part of
> the command. One would have to define $password as String instead of
> Sensitive and then wrap the whole command in a Sensitive() call (as Mattias
> suggested).
>
Note the `exec` resource specifically treats the entire
command/unless/onlyif parameters as sensitive, so those values don't
accidentally end up in logs and reports. Also note this capability is
available for any provider by passing `sensitive: true` to
Puppet::Util::Execution.execute
<https://github.com/puppetlabs/puppet/blob/6.18.0/lib/puppet/util/execution.rb#L159>
.
>
> This issue and some possible solutions have been discussed in
> https://tickets.puppetlabs.com/browse/PUP-10092
> <https://urldefense.com/v3/__https://tickets.puppetlabs.com/browse/PUP-10092__;!!Obbck6kTJA!O4r1x_A74uV9gBlwYRiL9nM4gus0ekJBAjar-QkllcvgQnLkdaGjPKxAsiQQM7O9$>.
> For example, Henrik suggested a `rewrap` function
> https://tickets.puppetlabs.com/browse/PUP-10093
> <https://urldefense.com/v3/__https://tickets.puppetlabs.com/browse/PUP-10093__;!!Obbck6kTJA!O4r1x_A74uV9gBlwYRiL9nM4gus0ekJBAjar-QkllcvgQnLkdaGjPKxAsjvV9iIs$>
> .
>
>
> Reg. the solution(s) discussed in there: Wouldn't the addition of a string
> concatenation operator (+) solve the problem right away (to make it content
> => $foo + "\n")?
>
That might work, but is a bit magic and may not work if the order is
reversed (as each type would need to account for concatenation with a
sensitive):
content => "prefix" + $foo
I'm not sure if it's feasible for puppet to cast the "prefix" string to a
sensitive so it can be concatenated with foo. Which I think is why Henrik
was suggesting the "rewrap" function. That way it's explicit and it works
regardless of argument order. Also it would handle hashes/arrays.
Josh
--
Josh Cooper | Software Engineer
j...@puppet.com
--
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/CA%2Bu97umre_yBB_NAxX2%3DeaUJeJE4yXSnZCfrKfH99GGx%2BkTexA%40mail.gmail.com.
Re: [Puppet Users] Is "Sensitive" broken?
On Wed, Sep 9, 2020 at 6:17 AM 'Dirk Heinrichs' via Puppet Users <
puppet-users@googlegroups.com> wrote:
> Hi,
>
> tried to use the "Sensitive" data type for the first time (with Puppet
> 6.18.0), but it doesn't work as expected (found and followed several
> tutorials on the net, see links below), also using the "lookup_options"
> method to ensure the Hiera-provided value is indeed converted to sensitive.
>
> Here's my sample code (Hiera files omitted):
>
> class test (Sensitive $foo) {
> file {'/tmp/foo':
> content => "${foo}\n",
> }
> }
>
> When I run this, I get:
>
> Notice: /Stage[main]/Test/File[/tmp/foo]/content:
> --- /tmp/foo2020-09-09 07:53:40.166807782 +0200
> +++ /tmp/puppet-file20200909-18841-zq93gr 2020-09-09
> 14:55:05.569695841 +0200
> @@ -1 +1 @@
> -bar
> +Sensitive [value redacted]
>
> Notice: /Stage[main]/Test/File[/tmp/foo]/content: content changed
> '{md5}fc552...' to '{md5}48a07...'
>
> and then the file indeed looks like this:
>
> # cat /tmp/foo
> Sensitive [value redacted]
>
> instead of containing the real value provided in Hiera.
>
> Any ideas?
>
> Thanks...
>
> Dirk
>
> https://blog.example42.com/2019/04/04/puppet_sensitive_data/
> https://www.puppetcookbook.com/posts/hide-sensitive-values.html
> https://puppet.com/blog/my-journey-securing-sensitive-data-puppet-code/
> --
> *Dirk Heinrichs*
> Senior Systems Engineer, Delivery Pipeline
> OpenText ™ Discovery | Recommind
> *Phone*: +49 2226 15966 18
> *Email*: dhein...@opentext.com
> *Website*: www.recommind.de
> Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach
> Vertretungsberechtigte Geschäftsführer Gordon Davies, Madhu Ranganathan,
> Christian Waida, Registergericht Amtsgericht Bonn, Registernummer HRB 10646
> This e-mail may contain confidential and/or privileged information. If you
> are not the intended recipient (or have received this e-mail in error)
> please notify the sender immediately and destroy this e-mail. Any
> unauthorized copying, disclosure or distribution of the material in this
> e-mail is strictly forbidden
> Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
> Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail
> irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und
> vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte
> Weitergabe dieser Mail sind nicht gestattet.
>
> --
> 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/b8b44d0a3859790edae6d420ab256d629df227a1.camel%40opentext.com
> <https://groups.google.com/d/msgid/puppet-users/b8b44d0a3859790edae6d420ab256d629df227a1.camel%40opentext.com?utm_medium=email_source=footer>
> .
>
The issue you're running into is due to the sensitive value being
interpolated:
content => "${foo}\n"
If you reference the Sensitive variable directly, then it will work as
expected:
content => $foo
This issue and some possible solutions have been discussed in
https://tickets.puppetlabs.com/browse/PUP-10092. For example, Henrik
suggested a `rewrap` function
https://tickets.puppetlabs.com/browse/PUP-10093.
Josh
--
Josh Cooper | Software Engineer
j...@puppet.com
--
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/CA%2Bu97uk6m7SPOrSxxQ6YJ5nCcWF6FbYU_cvR1-nWntFm9b4MMQ%40mail.gmail.com.
Re: [Puppet Users] Deferred without result
On Mon, Jun 15, 2020 at 4:43 AM Andreas Dvorak
wrote:
> Hello,
>
> I am trying to use the deferred function according to the page
> http://puppet-on-the-edge.blogspot.com/2018/10/the-topic-is-deferred.html
>
> My code does not show the time. Does anybody has a solution?
>
> notify {"time_now":
> message => Deferred('new', [TimeStamp])
> }
>
> $d = Deferred('new', [TimeStamp])
> notify {'time_now_2':
> message => "The time is: ${d}"
> }
>
> $dd = Deferred('new', [TimeStamp])
> notify {"time_now_3":
> message => Deferred("sprintf", ["The time is: %s", $dd])
> }
>
> notify { 'time_now_4':
> message => Deferred('inline_epp', [@(END)])
> The time is: <%= TimeStamp() %>
> |- END
> }
>
>
> My result
>
> Notice: Deferred({'name' => 'new', 'arguments' => [Timestamp]})
> Notice:
> /Stage[main]/Vault::Consul_server::Install/Notify[time_now]/message:
> defined 'message' as 'Deferred({\'name\' => \'new\', \'arguments\' =>
> [Timestamp]})'
> Notice: The time is: Deferred({'name' => 'new', 'arguments' =>
> [Timestamp]})
> Notice:
> /Stage[main]/Vault::Consul_server::Install/Notify[time_now_2]/message:
> defined 'message' as 'The time is: Deferred({\'name\' => \'new\',
> \'arguments\' => [Timestamp]})'
> Notice: Deferred({'name' => 'sprintf', 'arguments' => ['The time is: %s',
> Deferred({'name' => 'new', 'arguments' => [Timestamp]})]})
> Notice:
> /Stage[main]/Vault::Consul_server::Install/Notify[time_now_3]/message:
> defined 'message' as 'Deferred({\'name\' => \'sprintf\', \'arguments\' =>
> [\'The time is: %s\', Deferred({\'name\' => \'new\', \'arguments\' =>
> [Timestamp]})]})'
> Notice: Deferred({'name' => 'inline_epp', 'arguments' => ['The time is:
> <%= TimeStamp() %>']})
> Notice:
> /Stage[main]/Vault::Consul_server::Install/Notify[time_now_4]/message:
> defined 'message' as 'Deferred({\'name\' => \'inline_epp\', \'arguments\'
> => [\'The time is: <%= TimeStamp() %>\']})'
>
>
> Andreas
>
> --
> 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/84e6d862-2c4c-41d6-b45e-f16f94594b99o%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/84e6d862-2c4c-41d6-b45e-f16f94594b99o%40googlegroups.com?utm_medium=email_source=footer>
> .
>
Deferred functions are a new feature in puppet 6. Make sure you're using
the latest version, which currently is 6.16.0.
Josh
--
Josh Cooper | Software Engineer
j...@puppet.com
--
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/CA%2Bu97u%3DJXhA0PcTjEHFi6-R-gCH2pka-TqTpW2i3pbJXyVcLUw%40mail.gmail.com.
[Puppet Users] Re: Auditing directory content not managed by Puppet
On Tuesday, April 28, 2020 at 7:00:28 AM UTC-7, Miroslav Kalina wrote:
>
> Hello guys,
>
> I am trying to audit directory on server and automaticaly regenerate (with
> custom script run by *exec*) it's content whenever user touches it. With
> single files it's easy to do with
>
> file {'/etc/myconfig':
> audit => content,
> }
>
> -> exec {'/usr/local/bin/generate-myconfig.sh':
> refreshonly => true,
> }
>
> Unfortunately when I try to audit directory, content of it's file is not
> audited (which I kinda understand) and even list of files is not audited
> (which I can understand less). When I try to switch to `audit => mtime`, I
> am getting strange errors with `transaction.yaml` format and missing class
> Time.
>
> file {'/etc/mysoft/conf.d':
> ensure => directory,
> audit => mtime,
> }
>
> -> exec {'/usr/local/bin/generate-mysoft-conf.sh':
> refreshonly => true,
> }
>
> On first puppet agent run everything is completely fine, in verbose run I
> got notice
> Notice: /Stage[main]/MySoftModule::Config/File[/etc/mysoft/conf.d]/mtime:
> audit change: previously recorded value '2020-04-28 11:11:00 +0200' has
> been changed to '2020-04-28 11:27:16 +0200'
>
> but another runs gives me always an error
> Error: Transaction store file /opt/puppetlabs/puppet/cache/state/
> transactionstore.yaml is corrupt ((/opt/puppetlabs/puppet/cache/state/
> transactionstore.yaml): Tried to load unspecified class: Time); replacing
> Wrapped exception:
> Tried to load unspecified class: Time
>
> and when I searched `transactionstore.yaml` I can found this section,
> which I belive is related to this error
> File[/etc/mysoft/conf.d]:
> parameters:
> ensure:
> system_value:
> - :directory
> mtime:
> system_value:
> - 2020-04-28 11:27:16.291317766 +02:00
>
> Do you have any idea what am I doing wrong? I believe it's supposed to be
> used like that, but I cannot find much oficial reference and examples to
> audit metaparameter usage. I am using oficial puppetlabs packages,
> currently in version 6.14.0-buster1, but this behaves exactly same at in
> previous versions.
>
> Thank you for any advice.
>
Puppet safely loads YAML by restricting which classes can be loaded
<https://github.com/puppetlabs/puppet/blob/master/lib/puppet/util/yaml.rb#L8-L26>.
The Time class isn't in that list, and the code that loads the
transactionstore doesn't explicitly allow it
<https://github.com/puppetlabs/puppet/blob/9047506d745dc8bd4dc6cca9e67c2c56649f5447/lib/puppet/transaction/persistence.rb#L65>,
so the load fails. Puppet should probably allow the Time class, in addition
to Symbol. Could you file a PUP ticket? Also pull requests are welcome!
Josh
--
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/bacba452-b58a-41a2-9547-64cd9fe94409%40googlegroups.com.
Re: [Puppet Users] Re: Puppetserver performance plummeting a few hours after startup
of >>> JRubies as the number of cpu cores on your master, minus 1, with a maximum >>> of 4 JRubies for the system. >>> If you override the defaults, you can specify any number of JRubies you >>> want with the max-active-instances setting. >>> >>> So by default a 2-cpu puppet master will create 1 JRuby, a 4-cpu puppet >>> master will create 3 JRubies, an 8-cpu puppet master will create 4 JRubies. >>> >>> So now you know how to determine the amount of java heap memory you need >>> to configure, which you can do by configuring the -Xmx and -Xms options in >>> the JAVA_ARGS section of the puppetserver startup command. >>> Then finally make sure the host has enough physical memory available to >>> provide this increased amount of java heap memory. >>> >>> Once enough java heap memory is provided, you'll see the cpu usage stay >>> stable. >>> >>> Kind regards, >>> >>> Kevin Reeuwijk >>> >>> Principal Sales Engineer @ Puppet >>> >>> On Thursday, February 6, 2020 at 11:51:42 AM UTC+1, Martijn Grendelman >>> wrote: >>>> >>>> Hi, >>>> >>>> A question about Puppetserver performance. >>>> >>>> For quite a while now, our primary Puppet server is suffering from >>>> severe slowness and high CPU usage. We have tried to tweak its settings, >>>> giving it more memory (Xmx = 6 GB at the moment) and toying with the >>>> 'max-active-instances' setting to no avail. The server has 8 virtual cores >>>> and 12 GB memory in total, to run Pupperserver, PuppetDB and PostgreSQL. >>>> >>>> Notably, after a restart, the performance is acceptable for a while >>>> (several hours, up to a almost day), but then it plummets again. >>>> >>>> We figured that the server was just unable to cope with the load (we >>>> had over 270 nodes talking to it in 30 min intervals), so we added a second >>>> master that now takes more than half of that load (150 nodes). That did not >>>> make any difference at all for the primary server. The secondary server >>>> however, has no trouble at all dealing with the load we gave it. >>>> >>>> In the graph below, that displays catalog compilation times for both >>>> servers, you can see the new master in green. It has very constant high >>>> performance. The old master is in yellow. After a restart, the compile >>>> times are good (not great) for a while.The first dip represents ca. 4 >>>> hours, the second dip was 18 hours. At some point, the catalog compilation >>>> times sky-rocket, as does the server load. 10 seconds in the graph below >>>> corresponds to a server load of around 2, while 40 seconds corresponds to a >>>> server load of around 5. It's the Puppetserver process using the CPU. >>>> >>>> The second server, the green line, has a consistent server load of >>>> around 1, with 4 GB memory (2 GB for the Puppetserver JVM) and 2 cores >>>> (it's an EC2 t3.medium). >>>> >>>> >>>> >>>> If I have 110 nodes, doing two runs per hour, that each take 30 seconds >>>> to run, I would still have a concurrency of less than 2, so Puppet causing >>>> a consistent load of 5 seems strange. My first thought would be that it's >>>> garbage collection or something like that, but the server plenty of memory >>>> (OS cache has 2GB). >>>> >>>> Any ideas on what makes the Puppetserver starting using so much CPU? >>>> What can we try to keep it down? >>>> >>>> Thanks, >>>> Martijn Grendelman >>>> >>>> -- >>> 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/e8cff298-a0a6-48a9-9bbc-a7f000926467%40googlegroups.com >>> <https://groups.google.com/d/msgid/puppet-users/e8cff298-a0a6-48a9-9bbc-a7f000926467%40googlegroups.com?utm_medium=email_source=footer> >>> . >>> >> -- >> 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/CA%2B%3DBEqXRUJPpkv%3D333Fgk0EgV7h%3DkmK-ZYji5sThpZeQEXHbFQ%40mail.gmail.com >> <https://groups.google.com/d/msgid/puppet-users/CA%2B%3DBEqXRUJPpkv%3D333Fgk0EgV7h%3DkmK-ZYji5sThpZeQEXHbFQ%40mail.gmail.com?utm_medium=email_source=footer> >> . >> > -- > 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/CAMuuXv2PzP7LxniTbSWDnHF59BNFMYwPqe3oH-9wn2%3DwBgrV4Q%40mail.gmail.com > <https://groups.google.com/d/msgid/puppet-users/CAMuuXv2PzP7LxniTbSWDnHF59BNFMYwPqe3oH-9wn2%3DwBgrV4Q%40mail.gmail.com?utm_medium=email_source=footer> > . > -- Josh Cooper | Software Engineer j...@puppet.com -- 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/CA%2Bu97ukhTOsrSnvanNRjWMug%3Do4ogRSTOnEsrFCwJEPO7H4-8A%40mail.gmail.com.
Re: [Puppet Users] Re: Puppetserver performance plummeting a few hours after startup
On Thu, Feb 6, 2020 at 9:04 AM Justin Stoller wrote: > Yvan your issue sounds like https://tickets.puppetlabs.com/browse/PUP-3647, > do you know if that is fixed now, or has regressed since then? > To add to what Justin said, the state file is only supposed to be loaded/updated by the puppet agent process. It's possible the file is accidentally getting loaded in puppetserver, or maybe your puppet agent is an older version and doesn't have the fix? In PUP-3647, the statettl puppet setting controls how long to keep entries in the state file. It defaults to 32 days. You may want to set that to a lower value like "1d", though see the configuration reference page about how that affects scheduled resources. Also note setting it to 0 disables pruning entirely so the file can grow unbounded, which honestly seems wrong. I'd expect 0 to never cache... Josh -- Josh Cooper | Software Engineer j...@puppet.com -- 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/CA%2Bu97u%3DNXnNh1tMoJ%2Bhdv25EEGdt_0S1cBvqV9pAAYP8uCKdAA%40mail.gmail.com.
Re: [Puppet Users] Trying to source a file from https source version 5.5
On Wed, Dec 11, 2019 at 1:35 PM Kevin C wrote: > I am trying to source a file from our Artifactory which using https, but > it fails due to cert issues: > > SSL_connect returned=1 errno=0 state=error: certificate verify failed > > I found some discussions on this issue here > https://tickets.puppetlabs.com/browse/PUP-7814 but adding the cert to the > cert.pem or creating a file in /opt/puppetlabs/puppet/ssl/certs and running > the c_hash command did not work either. > > Any suggestions? > > -- > 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/78a78f59-712d-40d0-9553-fef672231e86%40googlegroups.com > <https://groups.google.com/d/msgid/puppet-users/78a78f59-712d-40d0-9553-fef672231e86%40googlegroups.com?utm_medium=email_source=footer> > . > Is artifactory's cert issued by an intermediate CA? Is artifactory configured to provide the entire cert chain (equivalent to SSLCertificateChainFile in Apache)? Can you connect using the openssl binary in the puppet-agent package? /opt/puppetlabs/puppet/bin/openssl s_client -CApath /opt/puppetlabs/puppet/ssl/certs -connect artifactory.example.com:443 Did you run /opt/puppetlabs/puppet/bin/c_rehash or the one in system openssl? Josh -- Josh Cooper | Software Engineer j...@puppet.com | @coopjn -- 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/CA%2Bu97ukFSuuy7eeCENKmfh0nhzoXKmPMw%3DQSTo3Ywk1CrOsiog%40mail.gmail.com.
Re: [Puppet Users] Re: puppet agent fails to self-restart on config change
On Thu, Nov 21, 2019 at 7:49 AM Yvan Broccard wrote: > I experience the same issue here, sometimes agents are stuck in this >> Shutdown/restart loop, especially if puppet agent changed a config value in >> puppet.conf. >> > > We're using Puppet 6 now here and this issue is new with Puppet 6. In the > past, with puppet serie 4, we never experienced this. > > I've updated the puppet-agent within the 6.10.x serie, hoping that a fix > would be delivered but not so far. > > Our clients nodes are mainly on CentOS 7.6/7.7 > > I'm surprised by the few similar issue I get by browsing the Internet for > this issue. > > Cheers > Yvan > > -- > 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/8fcbe059-90ce-4afa-9806-7a2d837eb3ac%40googlegroups.com > <https://groups.google.com/d/msgid/puppet-users/8fcbe059-90ce-4afa-9806-7a2d837eb3ac%40googlegroups.com?utm_medium=email_source=footer> > . > I was able to reproduce this a few months ago, but didn't find the cause. Could someone file a JIRA ticket if there isn't one already? Josh -- Josh Cooper | Software Engineer j...@puppet.com | @coopjn -- 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/CA%2Bu97unNFFWHZu5dUnZdTExP-96YNtb753yVWDtDWgiXdG0KGA%40mail.gmail.com.
[Puppet Users] HTTP proxy changes in Puppet Agents 5.5.17, 6.4.4, 6.8.0+
Puppet 5.5.16 and prior had a long standing bug that prevented the agent from using a proxy when the HTTP_PROXY environment variable or http_proxy_host puppet setting were defined. This issue, and number of other http proxy issues, were fixed in 5.5.17, 6.4.4 and 6.8.0, so the agent now correctly observes those variables/settings. However, it means puppet may try to use an http proxy when connecting to the puppetserver. In many environments, an http proxy is configured to only allow connections from internal hosts to external hosts, and it will reject any attempt to "reflect" off of the proxy from an internal host to another internal host. In these environments, puppet agents may no longer be able to connect to its puppetserver after upgrading to 5.5.17, 6.4.4 or 6.8.0+. And since the agent can't get a catalog, you can't use puppet to remedy the issue. If you are upgrading to 5.5.17, 6.4.4 or 6.8.x, make sure to add the FQDN of the puppetserver to the NO_PROXY environment variable or no_proxy puppet setting *before* upgrading. Due to https://tickets.puppetlabs.com/browse/PUP-9990 the puppetserver's FQDN must be specified, as opposed to a domain. The ability to specify a domain was fixed in 6.9.0 and will be backported to 5.5.x and 6.4.x in https://tickets.puppetlabs.com/browse/PUP-10112. If upgrading to 6.9.0 or greater, you can specify a dotted domain for the puppetserver, e.g. no_proxy=localhost,.example.com, and/or the puppetserver FQDN. However, don't use wildcards (*.example.com) or "bare" domains ( example.com) as puppet and ruby do not consistently handle them. See https://tickets.puppetlabs.com/browse/PUP-10106, which will be fixed in the next set of releases. Josh -- Josh Cooper | Software Engineer j...@puppet.com | @coopjn -- 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/CA%2Bu97ukSDfAN0fJH1CAz%2BhYS7zYN5hBcqyJW%2BqXfZiV5ogN7tA%40mail.gmail.com.
Re: [Puppet Users] Puppet agent fails collect packages for puppet "Cannot collect packages for Puppet::Type::package::ProviderYum provider; Failed to list packages"
On Wed, Oct 16, 2019 at 9:28 AM Ashwinkumar Kandasamy < kashwinkuma...@gmail.com> wrote: > Hi all, > In my puppet enterprise machine when ever i run the puppet agent -t > command it shows below error, > # puppet agent -t > Info: Using configured environment 'production' > Info: Retrieving pluginfacts > Info: Retrieving plugin > Info: Retrieving locales > Info: Loading facts > Error: Cannot collect packages for Puppet::Type:[image: :package:]:ProviderYum > provider; Failed to list packages > Info: Caching catalog for ,puppetmaster> > Info: Applying configuration version '1571212307' > Error: Could not prefetch package provider 'yum': Failed to list packages > Error: Failed to apply catalog: Failed to list packages > > > PE version -2019.0 > > -- > 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/a41bc387-75f1-499c-9683-ed423d783240%40googlegroups.com > <https://groups.google.com/d/msgid/puppet-users/a41bc387-75f1-499c-9683-ed423d783240%40googlegroups.com?utm_medium=email_source=footer> > . > Try running "puppet resource package --param provider --debug" to see which yum command fails. -- Josh Cooper | Software Engineer j...@puppet.com | @coopjn -- 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/CA%2Bu97u%3D1wPXzPQrSP5aZe3fJG2rp8gV9%2B960%3DrBrQV0koXR6mw%40mail.gmail.com.
Re: [EXTERNAL] - [Puppet Users] Puppet agent is not applying changes
Yes agreed, there are two issues on that:
https://tickets.puppetlabs.com/browse/SERVER-1717 and
https://tickets.puppetlabs.com/browse/PUP-7102. We tried to fix it earlier,
but had to revert due to acceptance test failures. The need for world
readable (or changing the owner or group to puppet) is because puppetserver
runs as the puppet user.
On Tue, Oct 1, 2019 at 8:57 AM Dan Crisp wrote:
> Thanks to all that contributed. I managed to solve the issue. Transpires
> that the permissions on the files and directories (0640 for the most part)
> was not sufficient. I had to ensure that all files in question had 0644
> and directories at 0755 permissions set to get this to work. A simple
> permission denied error somewhere among the logs would of been helpful!!
>
> Thanks again,
> Dan.
>
> On Sunday, September 29, 2019 at 9:19:13 PM UTC+1, Andreas Ntaflos wrote:
>>
>> On 28.09.19 12:15, Martin Alfke wrote:
>> > Hi Dirk,
>> >
>> > you are including class accounts within node default classification.
>> > The accounts module does not do anything unless you add data to it.
>> >
>> > Please look at https://github.com/puppetlabs/puppetlabs-accounts and
>> check if the following example is working:
>>
>> It doesn't look like Dan is using the puppetlabs-accounts module. His
>> accounts module just creates a user and a group (copy/pasting the code
>> from the initial post):
>>
>> # more
>> /etc/puppetlabs/code/environments/production/modules/accounts/manifests/init.pp
>>
>> class accounts {
>>
>> include accounts::groups
>>
>> user { 'djc72uk':
>> ensure => present,
>> home=> '/home/djc72uk',
>> shell => '/bin/bash',
>> managehome => true,
>> gid => 'djc72uk',
>> }
>>
>> }
>>
>> # more
>> /etc/puppetlabs/code/environments/production/modules/accounts/manifests/groups.pp
>>
>> class accounts::groups {
>>
>> group { 'djc72uk':
>> ensure => present,
>> }
>> }
>>
>> Andreas
>>
>> --
> 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/4a709aee-0057-4498-92f8-7b24ec4a31b4%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/4a709aee-0057-4498-92f8-7b24ec4a31b4%40googlegroups.com?utm_medium=email_source=footer>
> .
>
--
Josh Cooper | Software Engineer
j...@puppet.com | @coopjn
Join us for Puppetize PDX <http://www.puppet.com/puppetize> 9-10 October.
--
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/CA%2Bu97umX0td38gQ4WOY7qAgVkPFujDxFrxPkjk1PySweGd-%3Dng%40mail.gmail.com.
Re: [Puppet Users] Puppet agent is not applying changes
Hi Dan,
I think the problem is that default should not be quoted (see
https://puppet.com/docs/puppet/latest/lang_node_definitions.html#syntax):
If you do node "default", then puppet will only apply the class if the
node's fqdn is "default".
Josh
On Thu, Sep 26, 2019 at 9:55 AM Dan Crisp wrote:
> Hello all,
>
> Been at this problem I have for nearly a week now and it's driving
> crazy!!! I hope it's simply a case of someone with some fresh eyes taking
> a look and showing me the error of my ways.
>
> Before I continue with the Puppet deployment, for testing purposes, I just
> want to create a single user namely djc72uk on a single server. The
> servers name is lhcadvdeveye05 and you can see below that it has
> successfully generated a certificate:
>
> # puppetserver ca list --all
> Signed Certificates:
> lhcadvdeveye05.x.com (SHA256)
> F1:07:CD:17:8F:0B:B5:AF:79:8A:13:F3:BA:CA:90:1A:1D:67:2C:74:C2:7F:25:3B:88:E9:34:C5:FB:50:CD:7D
> puppet.fixnetix.com (SHA256)
> 7D:2E:79:6D:DE:97:A7:B0:5D:EB:48:37:3D:B1:0F:B2:C3:E1:7F:ED:70:D9:EC:2D:71:BE:53:4A:7C:9B:B6:81
> alt names: ["DNS:puppet", "DNS:puppet.xx.com"]
>
> I'm seeing the following output from the servers when I run the agent:
>
> # puppet agent --no-daemonize --verbose --onetime
> Info: Using configured environment 'production'
> Info: Retrieving pluginfacts
> Info: Retrieving plugin
> Info: Retrieving locales
> Info: Caching catalog for lhcadvdeveye05.xx.com
> Info: Applying configuration version '1569503223'
> Notice: Applied catalog in 0.24 seconds
>
> Looks all good here other than it's not applying the module I created
> namely accounts (see below within the puppet environment).
>
> *Puppet Server Environment*:
>
> # puppet config print confdir
> /etc/puppetlabs/puppet
>
> # ll /etc/puppetlabs/puppet
> total 48
> drwxr-xr-x. 1 puppet puppet 4096 Sep 25 22:34 ./
> drwxr-xr-x. 1 root root 4096 Sep 24 12:16 ../
> -rw-r--r--. 1 puppet puppet 5487 Sep 23 22:22 auth.conf
> -rw-r--r--. 1 puppet puppet 161 Sep 23 22:22 hiera.yaml
> -rw-r--r--. 1 puppet puppet 697 Sep 25 22:34 puppet.conf
>
> # more /etc/puppetlabs/puppet/puppet.conf
> [master]
> vardir = /opt/puppetlabs/server/data/puppetserver
> logdir = /var/log/puppetlabs/puppetserver
> rundir = /var/run/puppetlabs/puppetserver
> pidfile = /var/run/puppetlabs/puppetserver/puppetserver.pid
> codedir = /etc/puppetlabs/code
> environmentpath = $codedir/environments
> autosign = true
>
> # puppet config print codedir
> /etc/puppetlabs/code
>
> # puppet config print environmentpath
> /etc/puppetlabs/code/environments
>
> # puppet config print modulepath
>
> /etc/puppetlabs/code/environments/production/modules:/etc/puppetlabs/code/modules:/opt/puppetlabs/puppet/modules
>
> # puppet module list --tree
> /etc/puppetlabs/code/environments/production/modules
> └── accounts (???)
> /etc/puppetlabs/code/modules (no modules installed)
> /opt/puppetlabs/puppet/modules (no modules installed)
>
> # puppet config print manifest
> /etc/puppetlabs/code/environments/production/manifests
>
> # ls -lR /etc/puppetlabs/code
> /etc/puppetlabs/code:
> total 8
> drwxr-xr-x. 3 root root 4096 Sep 25 21:02 environments
> drwxr-xr-x. 2 root root 4096 Sep 25 21:02 modules
>
> /etc/puppetlabs/code/environments:
> total 4
> drwxr-xr-x. 5 root root 4096 Sep 25 20:47 production
>
> /etc/puppetlabs/code/environments/production:
> total 20
> -rw-r--r--. 1 root root 808 Sep 25 20:47 environment.conf
> -rw-r--r--. 1 root root 518 Sep 17 22:22 hiera.yaml
> drwxr-xr-x. 2 root root 4096 Sep 24 20:34 manifests
> drwxr-xr-x. 3 root root 4096 Sep 24 19:57 modules
>
>
> /etc/puppetlabs/code/environments/production/manifests:
> total 4
> -rw-r--r--. 1 root root 40 Sep 24 20:34 site.pp
>
> /etc/puppetlabs/code/environments/production/modules:
> total 4
> drwxr-x---. 5 root root 4096 Sep 25 21:18 accounts
>
> /etc/puppetlabs/code/environments/production/modules/accounts:
> total 12
> drwxr-x---. 2 root root 4096 Sep 24 20:38 manifests
>
> /etc/puppetlabs/code/environments/production/modules/accounts/manifests:
> total 8
> -rw-r-. 1 root root 77 Sep 24 20:38 groups.pp
> -rw-r-. 1 root root 224 Sep 24 20:01 init.pp
>
> /etc/puppetlabs/code/modules:
> total 0
>
> # more /etc/puppetlabs/code/environments/production/manifests/site.pp
> node 'default' {
> include accounts
> }
>
> # more
> /etc/puppetlabs/code/environments/production/modules/accounts/manifests/init.pp
> class accounts {
>
> include accounts::groups
>
> user { 'djc72uk':
> ensure => present,
> home
Re: [Puppet Users] http_proxy used for Puppet Master?
On Tue, Sep 3, 2019 at 9:17 AM Josh Cooper wrote: > > > On Mon, Sep 2, 2019 at 9:52 AM Jer Johnson wrote: > >> Hi! >> >> it looks like between Puppet Agent 6.7.2 and 6.8.0 , running "puppet >> agent -t " started picking >> up the http_proxy environment setting . is there a configuration option >> to disable that behavior? >> >> Thanks! >> -jer johnson >> >> -- >> 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/795c98d4-8403-46b5-8440-e42eaa07b038%40googlegroups.com >> <https://groups.google.com/d/msgid/puppet-users/795c98d4-8403-46b5-8440-e42eaa07b038%40googlegroups.com?utm_medium=email_source=footer> >> . >> > > You should be able to add a list of exclusions to NO_PROXY (environment > variable) or no_proxy (puppet setting). See related tickets fixed in 6.8.0: > > https://tickets.puppetlabs.com/browse/PUP-9942 > https://tickets.puppetlabs.com/browse/PUP-9316 > https://tickets.puppetlabs.com/browse/PUP-2172 > > That said I would not expect 6.8.0 to start using the http_proxy > environment setting if it didn't previously in 6.7.2. What are your > HTTP_PROXY and NO_PROXY environment variables and puppet settings on the > agent? > > Also you may be running into https://tickets.puppetlabs.com/browse/PUP-9990, but I haven't been able to reproduce so far. Josh -- 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/CA%2Bu97um%3D5JN5pUCf9XqBq2Vp4jHxrcJeV2FOSP9QN%3DMv5HHRgQ%40mail.gmail.com.
Re: [Puppet Users] Error: Could not run: The CRL issued by 'CN=Puppet CA: server.example.com' is missing
On Tue, Sep 3, 2019 at 8:30 AM Timothy Nelson wrote: > Hi all. I'm in the process of setting up a new puppet server, and I'm > trying to get my old puppet server to set up the server for me. My old > server is puppetserver-5.3.3. My new server is puppet-agent-6.7.2. The > first puppet run was successful; the first puppet run installs a bunch of > puppet modules, and then changes the environment (ie. sets the environment > variable in puppet.conf to a new value). This was all successful, but then > on the second run, it gave me the following error: > > Error: Could not run: The CRL issued by 'CN=Puppet CA: server.example.com' > is missing > > I tried changing back to the original environment. Still the same error. > Tried changing to a non-existent environment. Same error. > > I tried googling for this error, and the two or so relevant hits I found > were in the source code. > > I thought I'd ask here and see if anyone had any relevant ideas about what > might be wrong, and how that should be fixed. > > > -- > 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/CANZ4r3bbf%3DQOMLqOho8oVgAJZehw3Ow9WjFGmU%3Dse-Usz-qPNA%40mail.gmail.com > <https://groups.google.com/d/msgid/puppet-users/CANZ4r3bbf%3DQOMLqOho8oVgAJZehw3Ow9WjFGmU%3Dse-Usz-qPNA%40mail.gmail.com?utm_medium=email_source=footer> > . > My guess is that puppetserver 5.x cannot serve multiple CRLs, which is necessary when using an intermediate CA certificate ( https://tickets.puppetlabs.com/browse/SERVER-2205). What does `puppet ssl verify` display on the 6.x agent? Josh -- Josh Cooper | Software Engineer j...@puppet.com | @coopjn Join us for Puppetize PDX <http://www.puppet.com/puppetize> 9-10 October. -- 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/CA%2Bu97um%2BchtYBNzncK075vuKAj-JtqaPLnSWVZ2aqupODi9%3DoQ%40mail.gmail.com.
Re: [Puppet Users] http_proxy used for Puppet Master?
On Mon, Sep 2, 2019 at 9:52 AM Jer Johnson wrote: > Hi! > > it looks like between Puppet Agent 6.7.2 and 6.8.0 , running "puppet agent > -t " started picking > up the http_proxy environment setting . is there a configuration option > to disable that behavior? > > Thanks! > -jer johnson > > -- > 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/795c98d4-8403-46b5-8440-e42eaa07b038%40googlegroups.com > <https://groups.google.com/d/msgid/puppet-users/795c98d4-8403-46b5-8440-e42eaa07b038%40googlegroups.com?utm_medium=email_source=footer> > . > You should be able to add a list of exclusions to NO_PROXY (environment variable) or no_proxy (puppet setting). See related tickets fixed in 6.8.0: https://tickets.puppetlabs.com/browse/PUP-9942 https://tickets.puppetlabs.com/browse/PUP-9316 https://tickets.puppetlabs.com/browse/PUP-2172 That said I would not expect 6.8.0 to start using the http_proxy environment setting if it didn't previously in 6.7.2. What are your HTTP_PROXY and NO_PROXY environment variables and puppet settings on the agent? Josh -- Josh Cooper | Software Engineer j...@puppet.com | @coopjn Join us for Puppetize PDX <http://www.puppet.com/puppetize> 9-10 October. -- 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/CA%2Bu97u%3DK0sVrPKiud67Xh0QjUo_EpGY_aWdebZm62xZVUhSTng%40mail.gmail.com.
Re: [Puppet Users] Using bash for custom facts - results are strings, not booleans
On Thu, Jul 11, 2019 at 1:30 PM Ben Ford wrote:
> If you just return a string, then that's how it's interpreted even if it
> matches a keyword. To return a datatype, you'd need to return json.
>
> echo '{"gdm_installed": true}'
>
>
> and
>
> echo '{"gdm_installed": false}'
>
>
>
>
> On Thu, Jul 11, 2019 at 12:55 PM 'Prentice Bisbal' via Puppet Users <
> puppet-users@googlegroups.com> wrote:
>
>> I'm trying to use bash to create custom facts that are booleans,
>>
>
One clarification, "custom facts" are written in ruby (
https://puppet.com/docs/facter/latest/custom_facts.html), while facts
written in bash are examples of "external facts" (
https://puppet.com/docs/puppet/latest/external_facts.html).
Unfortunately, when I do, the values are interpreted as strings, and not
>> booleans. For example, here is my bash script, gdm.sh:
>>
>> #!/bin/bash
>>
>> PATH=/usr/bin:/bin:/usr/sbin:/sbin
>>
>> rpm --quiet -q gdm
>> retval=$?
>> if [ $retval -eq 0 ]; then
>> echo gdm_installed=true
>> else
>> echo gdm_installed=false
>> fi
>>
>> When I run the script, I get output in the following format, depending
>> on whether or not the gdm package is installed on the node:
>>
>> gdm_installed=true
>> gdm_installed=false
>>
>> From everything I've read online, that should be sufficient, but when I
>> run 'puppet facts, I see that the values for gdm_installed are strings
>> and not booleans. For example:
>>
>> # puppet facts | grep false
>> "fips_enabled": false,
>> "gdm_installed": "false",
>> "clientnoop": false
>>
>>
>> What am I doing wrong here? Is there something special about bash that
>> prevents it from being used like this?
>>
>
When writing a custom fact like:
Facter.add("myfact") do
setcode { false }
end
The boolean fact value is preserved. This is why the core "fips_enabled"
and "clientnoop" facts are boolean false. When writing an external fact,
fact values will always be strings unless you emit them as structured data
(json or yaml) like Ben suggested.
>> --
>> Prentice
>>
>> --
>> 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/883d5506-d9aa-8aa1-4904-89176566efac%40pppl.gov
>> .
>> For more options, visit 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/CACkW_L63NeWyik17zwXKs7O5GM8GWZSzoGzTQmfGNiTMcwXRyg%40mail.gmail.com
> <https://groups.google.com/d/msgid/puppet-users/CACkW_L63NeWyik17zwXKs7O5GM8GWZSzoGzTQmfGNiTMcwXRyg%40mail.gmail.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
--
Josh Cooper | Software Engineer
j...@puppet.com | @coopjn
--
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/CA%2Bu97unk51rSQfcd2iRsEms%2BDY7e1fm%3DhMA6xXLPAfGok-B7xA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] fips and non fips agent rpms
On Mon, Jun 24, 2019 at 10:04 AM 'slig...@verizon.net' via Puppet Users < puppet-users@googlegroups.com> wrote: > Thanks Josh, > > I am not switching out package. I am making a fips enabled server (with > fips agent installed) into a fips disabled one. Basically updating the grub > and rebooting. Thus now I have a non fips enabled machine with puppet fips > agent installed. So the question is will it work properly or do I have to > install nonfips agent? > > Basically I am using an image with fips agent installed. However, when we > install software, it may not work with fips, so we disable fips but leaving > the agent alone. > > My initial testing with bare bone master and puppet agent -t, showed that > non fips agent will work with fips enabled machine and vice-a -verse But > wanted to figure out what issues I may encounter, if any? > Ah, makes sense. The fips agent should work when fips is disabled. The agent will fallback to allowing md5 for filebucketing and when retrieving file resource metadata, e.g. `source => "puppet:///modules/foo/bar.txt"`. However, if you run into issues you can always specify which digest to use explicitly. See the `digest_algorithm` puppet setting and the `checksum` file parameter. https://puppet.com/docs/puppet/latest/configuration.html#digestalgorithm https://puppet.com/docs/puppet/latest/type.html#file-attribute-checksum Thanks > > M > > On Friday, June 21, 2019 at 1:29:38 PM UTC-4, Josh Cooper wrote: >> >> On Thu, Jun 20, 2019 at 9:05 AM 'sli...@verizon.net' via Puppet Users >> wrote: >> > >> > Hello, >> > >> > We are using some fips and some non-fips agent. Proper agent rpm (fips >> or non fips based on current configuration) has been installed, however, >> after agent installation, if we were to update a agent from fips to >> non-fips or vice-a-verse, will the old agent rpm still function? >> >> The fips and non-fips packages have the same name, but different >> releases. So if you switch from one to the other, the old one will be >> removed. That said, we don't test switching, as we assume the matching >> package is installed from the start. >> >> $ rpm -qi puppet-agent >> Name: puppet-agent >> Version : 6.5.0 >> Release : 1.redhatfips7 >> ... >> >> $ rpm -qi puppet-agent >> Name: puppet-agent >> Version : 6.5.0 >> Release : 1.el7 >> >> > Just running puppet agent -t seems to be working , but in that case not >> sure what is different between fips and non-fips agent? >> >> The fips agent is compiled against system openssl and does not contain >> a vendored openssl: >> >> $ ldd /opt/puppetlabs/puppet/lib/libfacter.so | grep libssl >> libssl.so.10 => /lib64/libssl.so.10 (0x7fefbab83000) >> >> Whereas the non-fips agent is compiled against puppet's vendored openssl: >> >> $ ldd /opt/puppetlabs/puppet/lib/libfacter.so | grep libssl >> libssl.so.1.1 => /opt/puppetlabs/puppet/lib/libssl.so.1.1 >> (0x7f705127f000) >> >> If you install a non-fips puppet-agent on a fips-enabled host, it will >> use the vendored openssl. While it will "work", I wouldn't recommend >> it, because it will subvert the system's openssl. >> >> If you install a fips puppet-agent on a non-fips-enabled host, then it >> should work provided the system openssl is compatible with our ruby. >> >> The puppet ruby code is the same for both fips and non-fips. At >> runtime, puppet detects if fips is enabled, and if so, removes md5 >> from its list of supported checksums. This affects filebucketing and >> retrieving file contents from "puppet:///" sources. Also some >> operations like `puppet module install` cannot be performed due to its >> reliance on md5. That will be changing in the near future though. >> >> Josh >> >> > >> > Thanks >> > >> > M >> > >> > -- >> > 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...@googlegroups.com. >> > To view this discussion on the web visit >> https://groups.google.com/d/msgid/puppet-users/59879625-fca7-4696-997a-ce4d598da63e%40googlegroups.com. >> >> > For more options, visit 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 re
Re: [Puppet Users] Core Modules with Puppet pre6?
On Fri, Jun 21, 2019 at 12:51 AM Martin Alfke wrote: > > Hi, > > has anyone tried what will happen if we place the Puppet 6 core modules in a > Puppetfile when still having a Puppet 5.x agent? > Will the agent still use the built-in types/providers? > > e.g. > Puppetfile: > mod 'puppetlabs/mount_core', :latest > mod 'puppetlabs/augeas_core', :latest > mod 'puppetlabs/zfs_core', :latest > mod 'puppetlabs/yumrepo_core', :latest > mod 'puppetlabs/host_core', :latest > mod 'puppetlabs/selinux_core', :latest > mod 'puppetlabs/zone_core', :latest > mod 'puppetlabs/cron_core', :latest > mod 'puppetlabs/sshkeys_core', :latest > mod 'puppetlabs/nagios_core', :latest > mod 'puppetlabs/mailalias_core', :latest > mod 'puppetlabs/macdslocal_core', :latest > mod 'puppetlabs/maillist_core', :latest > mod 'puppetlabs/k5login_core', :latest > > Many thanks, > Martin > > -- > 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/7213AA1A-AE0F-4E03-8135-78D57B02C3BD%40getmailspring.com. > For more options, visit https://groups.google.com/d/optout. I would expect puppetserver6 to use the core modules during compilation, while all agents should pluginsync the core modules and use their type/providers during catalog application, taking precedent over the versions in the puppet-agent 5.x package. This is one of the reasons we had to make the yumrepo_core module retain compatiblility with 5.x agents: https://github.com/puppetlabs/puppetlabs-yumrepo_core/commit/d751a380d7aea5ba88b3571a342039dfae3621e4 Josh -- 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/CA%2Bu97unrcB%3DFmtQ9fiqenSGdzOBqJUXkqq21e8NFQav5sZDPSg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] stdlib module causes puppet failure
On Thu, Jun 20, 2019 at 10:45 AM Michael Watters wrote: > > I'm having an issue with the puppetlabs-stdlib module causing compilation > failures using the puppet apply command. > > > Error: Class 'stdlib' is already defined (file: > > /mnt/live/puppeteer/conf.d/puppet/modules/stdlib/manifests/init.pp, line: > > 16); cannot redefine (file: > > /mnt/live/puppeteer/conf.d/puppet/modules/stdlib/manifests/init.pp, line: > > 16) on node host.example.com > > The command used to apply our manifest is as follows. > > puppet apply -d --noop --modulepath=puppet/modules --hiera_config=hiera.yaml > ./ > > > > This node is running Fedora 29 with the puppet-headless package. No changes > have been made to the manifest and I'm able to apply the same code on other > nodes with an older version of puppet. Does anybody know how to resolve this > or what would cause puppet to include the same class twice? You may be running into https://tickets.puppetlabs.com/browse/PUP-9602. Try deleting /mnt/live/puppeteer/conf.d/puppet/.resource_types Josh > > -- > 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/e93ac4af-6e04-4aae-96dc-0362b4290f50%40googlegroups.com. > For more options, visit 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/CA%2Bu97umjNLEJ37QfAda%3DW28%2BW44KMqeS%2Bej675WMWDRU%2B3fO_w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] fips and non fips agent rpms
On Thu, Jun 20, 2019 at 9:05 AM 'slig...@verizon.net' via Puppet Users wrote: > > Hello, > > We are using some fips and some non-fips agent. Proper agent rpm (fips or non > fips based on current configuration) has been installed, however, after agent > installation, if we were to update a agent from fips to non-fips or > vice-a-verse, will the old agent rpm still function? The fips and non-fips packages have the same name, but different releases. So if you switch from one to the other, the old one will be removed. That said, we don't test switching, as we assume the matching package is installed from the start. $ rpm -qi puppet-agent Name: puppet-agent Version : 6.5.0 Release : 1.redhatfips7 ... $ rpm -qi puppet-agent Name: puppet-agent Version : 6.5.0 Release : 1.el7 > Just running puppet agent -t seems to be working , but in that case not sure > what is different between fips and non-fips agent? The fips agent is compiled against system openssl and does not contain a vendored openssl: $ ldd /opt/puppetlabs/puppet/lib/libfacter.so | grep libssl libssl.so.10 => /lib64/libssl.so.10 (0x7fefbab83000) Whereas the non-fips agent is compiled against puppet's vendored openssl: $ ldd /opt/puppetlabs/puppet/lib/libfacter.so | grep libssl libssl.so.1.1 => /opt/puppetlabs/puppet/lib/libssl.so.1.1 (0x7f705127f000) If you install a non-fips puppet-agent on a fips-enabled host, it will use the vendored openssl. While it will "work", I wouldn't recommend it, because it will subvert the system's openssl. If you install a fips puppet-agent on a non-fips-enabled host, then it should work provided the system openssl is compatible with our ruby. The puppet ruby code is the same for both fips and non-fips. At runtime, puppet detects if fips is enabled, and if so, removes md5 from its list of supported checksums. This affects filebucketing and retrieving file contents from "puppet:///" sources. Also some operations like `puppet module install` cannot be performed due to its reliance on md5. That will be changing in the near future though. Josh > > Thanks > > M > > -- > 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/59879625-fca7-4696-997a-ce4d598da63e%40googlegroups.com. > For more options, visit 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/CA%2Bu97unZ08CkNbkrwahzXgqAMUdi-%2BvtnX7xrqK7AfCKpiCUOA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] puppet 6 facter -p Thread.exclusive is deprecated, use Thread::Mutex
On Thu, Apr 4, 2019 at 11:45 PM Andreas Dvorak wrote: > Hi, > > I have installed a new server with puppet 6. > > I get these errors with facter. Can somebody please help me? > > facter -v > 3.13.1 (commit 4e1df48f76caa0eaeee90af4239a1df450d45cd7) > > > facter -p osmajorrelease > Thread.exclusive is deprecated, use Thread::Mutex > /opt/puppetlabs/puppet/cache/lib/facter/meminbytes.rb:20:in > `meminfo_number' > /opt/puppetlabs/puppet/cache/lib/facter/meminbytes.rb:13:in `block (3 > levels) in ' > Thread.exclusive is deprecated, use Thread::Mutex > /opt/puppetlabs/puppet/cache/lib/facter/meminbytes.rb:20:in > `meminfo_number' > /opt/puppetlabs/puppet/cache/lib/facter/meminbytes.rb:13:in `block (3 > levels) in ' > Thread.exclusive is deprecated, use Thread::Mutex > /opt/puppetlabs/puppet/cache/lib/facter/meminbytes.rb:20:in > `meminfo_number' > /opt/puppetlabs/puppet/cache/lib/facter/meminbytes.rb:13:in `block (3 > levels) in ' > Thread.exclusive is deprecated, use Thread::Mutex > /opt/puppetlabs/puppet/cache/lib/facter/meminbytes.rb:20:in > `meminfo_number' > /opt/puppetlabs/puppet/cache/lib/facter/meminbytes.rb:13:in `block (3 > levels) in ' > 7 > > puppet-agent-6.4.0-1.el7.x86_64 > puppetserver-6.3.0-1.el7.noarch > puppet6-release-6.0.0-1.el7.noarch > > Regards > Andreas > -- > 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/038d99f1-8562-40c3-b993-548374913995%40googlegroups.com > <https://groups.google.com/d/msgid/puppet-users/038d99f1-8562-40c3-b993-548374913995%40googlegroups.com?utm_medium=email_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > The "meminbytes" fact is coming from a module and downloaded to the agent. The Thread.exclusive call is not needed, and likely occurred when copy/pasting from an old core fact in the Ruby facter implementation. We removed that from core Ruby in https://github.com/puppetlabs/facter/commit/159d3a682f141a5183c933be5ef2cf763f59bb6c#diff-5ac9627bb8707b6cf7eb398ec448edb2 Josh -- Josh Cooper | Software Engineer j...@puppet.com | @coopjn -- 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/CA%2Bu97ukR0ou7cVY31jYMvx-cAB1x-HCTdAWCXfo3avo4Dh0gwA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Error during pluginsync for Puppet 5/6 when using json
On Mon, Feb 11, 2019 at 7:33 AM Andreas Zuber wrote:
> Hello
>
> We are in progress of moving from Puppet 4 to 5/6 and we currently have
> a lab installation of both versions to toy around with.
>
> Our agents are still on version 4 and for them everything works as
> expected without any issues no matter if they connect to the version 4,
> 5 or 6 puppetserver.
>
> However if we use a version 5 or 6 agent to connect to those version 5
> or 6 servers we get a really strange error:
>
> Error: /File[/opt/puppetlabs/puppet/cache/lib]: Failed to generate
> additional resources using 'eval_generate': Could not intern_multiple
> from application/json: Invalid parameter ftype to object class
> Puppet::FileServing::Metadata
>
> We found out that if we force the client to use PSON with
> "--preferred_serialization_format pson" the problem goes away. This is
> also why the problem only occurs on agents > 5 as they are now using
> json as default.
>
> This also only affects the plugin endpoints where it syncs facts.d, lib
> and locals at the very start of the run. The catalog itself can be
> retrieved without issue with json.
>
> So I tried to track this down a bit further. The issue seems to
> originate from a part of code where Puppet tries to add values from a
> received json hash to an object:
>
>
> https://github.com/puppetlabs/puppet/blob/41760e1646ffd91942ebc2290b5108ce31fe529d/lib/puppet/util/methodhelper.rb#L16
>
> The data I get with PSON here is:
>
> [{
> "path":"/etc/puppetlabs/code/environments/test/modules",
> "relative_path":".",
> "links":"follow",
> "owner":0,
> "group":10080,
> "mode":1517,
> "checksum":{
>"type":"ctime",
>"value":"{ctime}2019-02-11 11:02:06 +0100"
> },
> "type":"directory",
> "destination":null
> }]
>
> With JSON the Puppetserver returns:
>
> [{
> "checksum_type":"ctime",
> "links":"follow",
> "destination":null,
> "source":null,
> "group":10080,
> "ftype":"directory",
> "relative_path":".",
> "expiration":"2019-02-11T14:39:20.972+01:00",
> "checksum":"{ctime}2019-02-11 11:02:06 +0100",
> "stat_method":"stat",
> "owner":0,
> "mode":1517,
> "content_uri":null,
> "source_permissions":"use",
> "path":"/etc/puppetlabs/code/environments/test/modules"
> }]
>
> It then tries to call ftype=(value) on an object of
> Puppet::FileServing::Metadata (as the error message says) but that
> attribute only has an attribute reader:
>
>
> https://github.com/puppetlabs/puppet/blob/41760e1646ffd91942ebc2290b5108ce31fe529d/lib/puppet/file_serving/metadata.rb#L16
>
>
> Clearly something very strange is going on here. This can't be the real
> issue as it obviously works for other people. Maybe someone on this list
> has any idea how to track this down further or has encountered a similar
> issue.
>
How are you forcing "ctime" to be used for pluginsync? Normally it's "md5".
Are you overridding "supported_checksum_types" on either the server or
agent? Probably best to see the complete `puppet.conf` for server and agent
when the error occurs.
What puppet-agent and puppetserver versions do you have installed?
Are static catalogs enabled either globally (puppet config get
static_catalogs --section master|agent) on either the server or agent, or
per-environment in "$codedir/environments/test/environment.conf" ?
Did you happen to install the JrJackson gem on the server?
Josh
--
Josh Cooper | Software Engineer
j...@puppet.com | @coopjn
--
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/CA%2Bu97um6ek3FoEyOZwLhe1nQeHO4admP2d5yJquN9Gf8N3eVHQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Permissions denied?
On Tue, Jan 29, 2019 at 10:16 AM Jason McMahan wrote: > Good day, > I received the below error when running the lsp module by kpn from the > forge. > > > Error: /File[C:/ProgramData/PuppetLabs/puppet/var/lib]: Failed to generate > additional resources using 'eval_generate': E > rror 500 on SERVER: Server Error: Permission denied - > /etc/puppetlabs/code/environments/test/modules/local_s > ecurity_policy/lib/puppet_x/lsp/security_policy.rb > > I am a little confused is the permissions issue on the master end or on > the server the agent is running on? > It's an error on the server. The puppetserver process running as the "puppet" user needs read permission to those files. > Any guidance would be appreciated. > > Thank you > Jason > > -- > 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/59bf2f60-d02d-450e-90ef-2d4a7000249b%40googlegroups.com > <https://groups.google.com/d/msgid/puppet-users/59bf2f60-d02d-450e-90ef-2d4a7000249b%40googlegroups.com?utm_medium=email_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- Josh Cooper | Software Engineer j...@puppet.com | @coopjn -- 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/CA%2Bu97u%3DkWvg_7Vdo3Ds5-dVShrsewVunng%2BdCATF1jV1wE5DeQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Re: Puppetserver 6.0 -> Error:num=20 and Error:num=21
On Fri, Jan 4, 2019 at 2:03 PM 'Michael Post' via Puppet Users < puppet-users@googlegroups.com> wrote: > Hello, > >> >> Am Freitag, 4. Januar 2019 22:21:47 UTC+1 schrieb Michael Post: >> >>> Hello, >>> >>> yesterday and today i set up a new Debian Stretch VM and want to install >>> a fresh environment with puppetserver 6. >>> >>>> >>>> sometimes it is good to write and think and read more and more. > I solved my problem. > The exact steps are written in the documentation but you have to find it. > > It is written under > > https://puppet.com/docs/puppet/5.3/config_ssl_external_ca.html#option-2-puppet-server-functioning-as-an-intermediate-ca > > Puppet agent > You need to do two things to prepare Puppet agent for this CA > configuration: > If you copy this file into place before the first Puppet run, you will not > recieve any errors. If you attempt a Puppet run prior to this file being > present you will receive errors since the auto-distributed ca.pem file > doesn’t include the root CA.. > Example error: > Error: Could not request certificate: SSL_connect returned=1 errno=0 > state=error: certificate verify failed: [unable to get local issuer > certificate for /CN=] > > Copy the CA bundle in place prior to a Puppet run. > > Disable certificate revocation validation. > > Copy the CA bundle you created to /etc/puppetlabs/puppet/ssl/certs/ca.pem on > every agent node. > Set certificate_revocation = false in the [main] section of puppet.conf > on every agent node: > > [main] > certificate_revocation = false > > Once you’ve completed both of these steps, the agent can run successfully. > > Have a nice weekend, > > Michael > > -- > 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/ed78a062-6db1-4636-bb78-c2bfbb01cb90%40googlegroups.com > <https://groups.google.com/d/msgid/puppet-users/ed78a062-6db1-4636-bb78-c2bfbb01cb90%40googlegroups.com?utm_medium=email_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > One clarification. Puppetserver6 has a new workflow for importing an external CA certificate, and issuing an intermediate puppet CA from that. Also puppet6 agents will correctly download the CA bundle and process multiple CRLs, so it is not necessary to disable CRL checking. However the steps you outlined are required for puppet5 agents talking to puppetserver6 when it is using intermediate CA certs, as older agents don't process multiple CRLs correctly. See https://puppet.com/docs/puppetserver/6.1/intermediate_ca.html for more details.. Josh -- Josh Cooper | Software Engineer j...@puppet.com | @coopjn -- 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/CA%2Bu97u%3DWLyhfBvb8Hbj%3DUJ%2BNr3SVX7K%2BMAzEXxtSRFamy%3D8OzA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Re: Upgrade to puppet-agent 5.3.5 report failure
On Fri, Nov 30, 2018 at 7:39 AM Darragh Bailey
wrote:
>
>
> On Thursday, November 29, 2018 at 11:27:13 AM UTC, Darragh Bailey wrote:
>>
>>
>>
>> On Wednesday, November 28, 2018 at 6:32:44 PM UTC, Eric Sorenson wrote:
>>>
>>> Hi Darragh, the fact that the error message contains a '400' error
>>> suggests the problem happens on the server when it receives the report.
>>>
>>> My first guess given that error message is also that there's a mix of
>>> versions installed, but it's weird that it only happens on some reports.
>>> Maybe there is something malformed in those reports that triggers a
>>> different code path on the server.
>>>
>>
>> Indeed there is, I missed that there were errors further back in the
>> output log previously and assumed the failure to post the report
>> successfully was the error. Seems they are not compilation errors but
>> rather runtime errors where something unexpected occurred in applying the
>> catalog.
>>
>> For successful runs there is no problem in posting back the report, this
>> at least now gives me something to reproduce consistently, just add an
>> error somewhere that will trigger it.
>>
>
> So confirmed I can reproduce this by simply adding the following block to
> the site.pp for our vagrant environment
>
> exec { 'break the run':
> command => '/bin/false',
> }
>
> However it only triggers the error on the first run, once there is a
> successful run, can't trigger the problem subsequently.
>
This makes me think it's related to the transactionstore functionality (it
keeps track of what the "current" value is the last time puppet applied a
catalog, so that it can tell if a change is due to an intentional manifest
change or the system drifted and needed to be remediated). I say that
because the transaction store records information differently depending if
the event was successful or not. Might want to look in `puppet config print
transactionstorefile --section agent` on the agent to see if there are any
clues.
Also earlier you mentioned:
> Warning: Event['previous_value'] contains a Process::Status value. It
will be converted to the String 'pid 30408 exit 1'
The "previous_value" for an exec should always be "notrun" or the desired
value (due to the onlyif/unless/creates checks causing the exec to skip). I
wonder if somehow the previous system from the transactionstore is ending
up in the next report?
>>
>>> You can save a copy of the reports by adding `store` to the type of
>>> report submission on the master: `reports = https,store` and see what they
>>> look like. They should go into a subdirectory
>>> of /opt/puppetlabs/puppet/cache/reports
>>>
>>
>>> HTH
>>> --eric0
>>>
>>
>> Ah, fantastic, didn't think of that! That will definitely help, many
>> thanks.
>>
>>
> So apparently 'store' is the default based on
> https://puppet.com/docs/puppet/5.4/reporting_about.html#configuring-reporting
> and it should be 'http' just in case anyone else encounters this.
>
> But it doesn't appear to have any effect in capturing the report being
> sent. Might need to make use of nginx and report_port as a way to forward
> on the request while logging it's content it so that I can grab what was
> sent.
>
> Looking on the agent node I see the
> /var/lib/puppet/state/last_run_summary.yaml containing
>
> events:
> failure: 1
> success: 362
> total: 363
>
> But unfortunately there's no /var/lib/puppet/state/last_run_report.yaml
> that corresponds, as it doesn't appear to get updated due to the failure,
> so there's no actual record of the report being sent to the master.
>
You may be running into https://tickets.puppetlabs.com/browse/PUP-6708?
> --
> Darragh Bailey
>
> --
> 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/45e5e998-f3a1-4aa1-8066-5bed2a4dab29%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/45e5e998-f3a1-4aa1-8066-5bed2a4dab29%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
--
Josh Cooper | Software Engineer
j...@puppet.com | @coopjn
--
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/CA%2Bu97ukEMbCtZZzZEP5L1Y1Gjjwy1BwMuUCGrwOcU3Cpu49TcQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Re: Unknown resource type after Upgrade
On Fri, Sep 28, 2018 at 2:33 PM Josh Cooper wrote: > > > > On Fri, Sep 28, 2018 at 1:04 AM Christian Reiß > wrote: >> >> Hey, >> >> thank you-- >> that clears that up. Seems like time will solve the issue; postponing the >> update for now. > > > Filed as https://tickets.puppetlabs.com/browse/MODULES-8015. We should have a > fix by early next week. Thanks to Peter Meier (duritong) this is fixed in nagios_core version 1.0.2, which was released to the forge today[1]. We had a similar issue with the augeas_core modules, and version 1.0.3 was released today as well[2]. Note it wasn't fatal like the nagios case, because augeas is bundled into the puppet-agent package, but nagios is not. We also filed a request to improve pdk validation to detect when a type or provider requires helper in a way that requires the helper code to be in the ruby load path[3]. Josh [1] https://forge.puppet.com/puppetlabs/nagios_core [2] https://forge.puppet.com/puppetlabs/augeas_core [3] https://tickets.puppetlabs.com/browse/PDK-1196 -- Josh Cooper | Software Engineer j...@puppet.com | @coopjn -- 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/CA%2Bu97u%3DaiwY%2BzAsJF0YY5e%2B%2BJoxBHMHg_0tURuCx%2Bm35DjYAmw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Re: Unknown resource type after Upgrade
On Fri, Sep 28, 2018 at 1:04 AM Christian Reiß
wrote:
> Hey,
>
> thank you--
> that clears that up. Seems like time will solve the issue; postponing the
> update for now.
>
Filed as https://tickets.puppetlabs.com/browse/MODULES-8015. We should have
a fix by early next week.
>
> Am Donnerstag, 27. September 2018 11:14:19 UTC+1 schrieb Christian Reiß:
>>
>> Hey folks,
>>
>> I am currently upgrading to 6.x on a test setup using my live puppet
>> code; trying to get it to work with 6.x.
>> One weird issue I am getting is that alle default definitions (upper case
>> classes) are faulting:
>>
>> Error: Could not retrieve catalog from remote server: Error 500 on SERVER
>> : Server Error: Evaluation Error: Resource type not found: Nagios_service
>> (file: /etc/puppetlabs/code/environments/production/modules/pn_icinga/
>> manifests/client/checks.pp, line: 83, column: 3) on node outleapt.test
>> Warning: Not using cache on failed catalog
>> Error: Could not retrieve catalog; skipping run
>>
>>
>>
>> The corresponding manifest looks like this:
>>
>> Nagios_service {
>> check_period => '24x7',
>> ensure=> $::pn_icinga::client::installed,
>> host_name => $::trusted['certname'],
>> initial_state => 'o',
>> max_check_attempts=> '3',
>> notification_interval => '5',
>> notification_options => 'w,u,c,r',
>> notification_period => $notification_period,
>> notifications_enabled => '0',
>> [...]
>> }
>>
>> Did I miss a regression somewhere?
>> Any help is greatly appreciated!
>>
>> -Chris.
>>
> --
> 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/8a5b4fed-cf93-4c8a-8652-5fc3222952c0%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/8a5b4fed-cf93-4c8a-8652-5fc3222952c0%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
--
Josh Cooper | Software Engineer
j...@puppet.com | @coopjn
--
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/CA%2Bu97um4QVRzCEBmpNRqkV__g2W6nCJAK_8%3DY%2Bt%2B_z9W72QdkQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Unknown resource type after Upgrade
On Thu, Sep 27, 2018 at 3:55 AM Christian Reiß
wrote:
> Hey Rafael,
>
> thanks for your reply. Ironically I was readind the deprecated logs and
> seem to have missed that, After doing a puppet module install the error
> changed to
>
> Error: Could not retrieve catalog from remote server: Error 500 on SERVER:
> Server Error: Evaluation Error: Error while evaluating a Type-Name, Could
> not autoload puppet/type/nagios_service: no such file to load -- puppet/
> util/nagios_maker (file: /etc/puppetlabs/code/environments/production/
> modules/pn_icinga/manifests/client/raid.pp, line: 15, column: 3) on node
> outleapt.test
>
>
This is a bug in the nagios_core module. Any time a module type or provider
loads helper code (for example
https://github.com/puppetlabs/puppetlabs-nagios_core/blob/d97ec08c78d966a500cf172f6575329f82df27a6/lib/puppet/type/nagios_service.rb#L1)
it needs to use require_relative or pass a relative path to require. The
reason is because the master needs to serve multiple environments, so we
can't add the environment-specific module path to the global ruby
$LOAD_PATH. Please open a MODULES ticket with component set to nagios_core.
This wasn't an issue prior to puppet6, because the nagios type/provider was
in core puppet, and so was in the $LOAD_PATH.
Mind pushing me once more in the right direction?
>
> -Chris.
>
>
> Am Donnerstag, 27. September 2018 11:25:34 UTC+1 schrieb Rafael Tomelin:
>>
>> Hi dear,
>>
>> This link the puppet6 release notes.
>> https://puppet.com/docs/puppet/6.0/release_notes.html#deprecations
>>
>>
>>- The Nagios types no longer ship with Puppet, and are now available
>>as the puppetlabs/nagios_core module from the Forge.
>>
>>
>> Em qui, 27 de set de 2018 às 07:14, Christian Reiß
>> escreveu:
>>
>>> Hey folks,
>>>
>>> I am currently upgrading to 6.x on a test setup using my live puppet
>>> code; trying to get it to work with 6.x.
>>> One weird issue I am getting is that alle default definitions (upper
>>> case classes) are faulting:
>>>
>>> Error: Could not retrieve catalog from remote server: Error 500 on
>>> SERVER: Server Error: Evaluation Error: Resource type not found:
>>> Nagios_service (file: /etc/puppetlabs/code/environments/production/
>>> modules/pn_icinga/manifests/client/checks.pp, line: 83, column: 3) on
>>> node outleapt.test
>>> Warning: Not using cache on failed catalog
>>> Error: Could not retrieve catalog; skipping run
>>>
>>>
>>>
>>> The corresponding manifest looks like this:
>>>
>>> Nagios_service {
>>> check_period => '24x7',
>>> ensure=> $::pn_icinga::client::installed,
>>> host_name => $::trusted['certname'],
>>> initial_state => 'o',
>>> max_check_attempts=> '3',
>>> notification_interval => '5',
>>> notification_options => 'w,u,c,r',
>>> notification_period => $notification_period,
>>> notifications_enabled => '0',
>>> [...]
>>> }
>>>
>>> Did I miss a regression somewhere?
>>> Any help is greatly appreciated!
>>>
>>> -Chris.
>>>
>>> --
>>> 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...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/puppet-users/bde5ac1d-f1ef-4454-885d-b499f22062c8%40googlegroups.com
>>> <https://groups.google.com/d/msgid/puppet-users/bde5ac1d-f1ef-4454-885d-b499f22062c8%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
>>
>> Atenciosamente,
>>
>> Rafael Tomelin
>>
>> skype: rafael.tomelin
>>
>> E-mail: rafael@gmail.com
>>
>> RHCE - Red Hat Certified Engineer
>> PPT-205 - Puppet Certified Professional 2017
>> Zabbix- ZABBIX Certified Specialist
>> LPI3
>> ITIL v3
>>
> --
> 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/c2b299
Re: [Puppet Users] Re: More oddities with installting FOSS version of Puppet
On Wed, Aug 1, 2018 at 11:22 AM Salty Old Cowdawg wrote: > > > > > > I take it then PC1 is frozen in Puppet 4 Yep, PC1 contains puppet-agent 1.10.x, puppet 4.10.x, puppetserver 2.8.x. We didn't want to release puppet5 into the PC1 repos. > where the other packages ( puppet5-release-wheezy.deb) is strictly for the > Enterprise folks? No, puppet5 is available for FOSS, see https://puppet.com/docs/puppet/latest/puppet_platform.html. For example, http://apt.puppet.com/puppet5-release-wheezy.deb > > I was actually hoping to get Puppet 5 on my home environment since I test > concepts for my paying job (AT) on my home environment. You can also try out puppet6 nightlies from http://nightlies.puppet.com/apt/puppet6-nightly-release-wheezy.deb > > -- > 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/2a62f7d5-a267-490a-a697-ad98e564e5a1%40googlegroups.com. > For more options, visit https://groups.google.com/d/optout.-- Josh Cooper | Software Engineer j...@puppet.com | @coopjn -- 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/CA%2Bu97umPeOnBppuAKFRzhJ-nqQm%2BbzrcVz17Dgz1KQ%2BQVZ6HAg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] More oddities with installting FOSS version of Puppet
On Thu, Jul 26, 2018 at 1:09 PM Peter Berghold wrote: > > Josh, > > I wiped the entire trees meaning /opt/puppetlabs and /etc/puppetlabs > recursive. > Ah, k... FWIW, I'm able to install puppetserver and puppet-agent on 16.04: # wget http://apt.puppet.com/puppetlabs-release-pc1-xenial.deb # dpkg -i puppetlabs-release-pc1-xenial.deb # apt-get update ... # apt-get install puppetserver Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: ca-certificates-java fontconfig-config fonts-dejavu-core java-common libavahi-client3 libavahi-common-data libavahi-common3 libcups2 libfontconfig1 libjpeg-turbo8 libjpeg8 liblcms2-2 libnspr4 libnss3 libnss3-nssdb libpcsclite1 libxi6 libxrender1 libxtst6 openjdk-8-jre-headless puppet-agent x11-common Suggested packages: default-jre cups-common liblcms2-utils pcscd libnss-mdns fonts-dejavu-extra fonts-ipafont-gothic fonts-ipafont-mincho fonts-wqy-microhei fonts-wqy-zenhei fonts-indic The following NEW packages will be installed: ca-certificates-java fontconfig-config fonts-dejavu-core java-common libavahi-client3 libavahi-common-data libavahi-common3 libcups2 libfontconfig1 libjpeg-turbo8 libjpeg8 liblcms2-2 libnspr4 libnss3 libnss3-nssdb libpcsclite1 libxi6 libxrender1 libxtst6 openjdk-8-jre-headless puppet-agent puppetserver x11-common 0 upgraded, 23 newly installed, 0 to remove and 150 not upgraded. Need to get 80.8 MB of archives. After this operation, 247 MB of additional disk space will be used. Do you want to continue? [Y/n] y Fetched 80.8 MB in 4s (16.8 MB/s) Selecting previously unselected package libjpeg-turbo8:amd64. (Reading database ... 63622 files and directories currently installed.) Preparing to unpack .../libjpeg-turbo8_1.4.2-0ubuntu3.1_amd64.deb ... Unpacking libjpeg-turbo8:amd64 (1.4.2-0ubuntu3.1) ... Selecting previously unselected package liblcms2-2:amd64. Preparing to unpack .../liblcms2-2_2.6-3ubuntu2_amd64.deb ... Unpacking liblcms2-2:amd64 (2.6-3ubuntu2) ... Selecting previously unselected package x11-common. Preparing to unpack .../x11-common_1%3a7.7+13ubuntu3_all.deb ... Unpacking x11-common (1:7.7+13ubuntu3) ... Selecting previously unselected package libxtst6:amd64. Preparing to unpack .../libxtst6_2%3a1.2.2-1_amd64.deb ... Unpacking libxtst6:amd64 (2:1.2.2-1) ... Selecting previously unselected package java-common. Preparing to unpack .../java-common_0.56ubuntu2_all.deb ... Unpacking java-common (0.56ubuntu2) ... Selecting previously unselected package libavahi-common-data:amd64. Preparing to unpack .../libavahi-common-data_0.6.32~rc+dfsg-1ubuntu2.2_amd64.deb ... Unpacking libavahi-common-data:amd64 (0.6.32~rc+dfsg-1ubuntu2.2) ... Selecting previously unselected package libavahi-common3:amd64. Preparing to unpack .../libavahi-common3_0.6.32~rc+dfsg-1ubuntu2.2_amd64.deb ... Unpacking libavahi-common3:amd64 (0.6.32~rc+dfsg-1ubuntu2.2) ... Selecting previously unselected package libavahi-client3:amd64. Preparing to unpack .../libavahi-client3_0.6.32~rc+dfsg-1ubuntu2.2_amd64.deb ... Unpacking libavahi-client3:amd64 (0.6.32~rc+dfsg-1ubuntu2.2) ... Selecting previously unselected package libcups2:amd64. Preparing to unpack .../libcups2_2.1.3-4ubuntu0.5_amd64.deb ... Unpacking libcups2:amd64 (2.1.3-4ubuntu0.5) ... Selecting previously unselected package libjpeg8:amd64. Preparing to unpack .../libjpeg8_8c-2ubuntu8_amd64.deb ... Unpacking libjpeg8:amd64 (8c-2ubuntu8) ... Selecting previously unselected package fonts-dejavu-core. Preparing to unpack .../fonts-dejavu-core_2.35-1_all.deb ... Unpacking fonts-dejavu-core (2.35-1) ... Selecting previously unselected package fontconfig-config. Preparing to unpack .../fontconfig-config_2.11.94-0ubuntu1.1_all.deb ... Unpacking fontconfig-config (2.11.94-0ubuntu1.1) ... Selecting previously unselected package libfontconfig1:amd64. Preparing to unpack .../libfontconfig1_2.11.94-0ubuntu1.1_amd64.deb ... Unpacking libfontconfig1:amd64 (2.11.94-0ubuntu1.1) ... Selecting previously unselected package libnspr4:amd64. Preparing to unpack .../libnspr4_2%3a4.13.1-0ubuntu0.16.04.1_amd64.deb ... Unpacking libnspr4:amd64 (2:4.13.1-0ubuntu0.16.04.1) ... Selecting previously unselected package libnss3-nssdb. Preparing to unpack .../libnss3-nssdb_2%3a3.28.4-0ubuntu0.16.04.3_all.deb ... Unpacking libnss3-nssdb (2:3.28.4-0ubuntu0.16.04.3) ... Selecting previously unselected package libnss3:amd64. Preparing to unpack .../libnss3_2%3a3.28.4-0ubuntu0.16.04.3_amd64.deb ... Unpacking libnss3:amd64 (2:3.28.4-0ubuntu0.16.04.3) ... Selecting previously unselected package libpcsclite1:amd64. Preparing to unpack .../libpcsclite1_1.8.14-1ubuntu1.16.04.1_amd64.deb ... Unpacking libpcsclite1:amd64 (1.8.14-1ubuntu1.16.04.1) ... Selecting previously unselected package libxi6:amd64. Preparing to unpack .../libxi6_2%3a1.7.6-1_amd64.deb ... Unpacking libxi6:amd64 (2:1.7.6-1) ... Selecting previously unselected package
Re: [Puppet Users] More oddities with installting FOSS version of Puppet
On Wed, Jul 25, 2018 at 6:16 AM Peter Berghold wrote: > > Once again I undertook trying to get a puppetserver in my personal computing > environment to work and during a fresh install of puppetserver (removing > agent and server first) and clearing the /opt/puppetlabs and /etc/puppetlabs > directories I see the following complaints: Did you delete the /opt/puppetlabs and /etc/puppetlabs directories or delete their contents? If it's the latter, it may be that the puppet-agent package doesn't recreate the intermediate directories, e.g. /opt/puppetlabs/puppet/share, causing later steps to fail. > > Setting up puppet-agent (1.10.14-1xenial) ... > chmod: cannot access > '/opt/puppetlabs/puppet/share/vim/puppet-vimfiles/ftdetect/puppet.vim': No > such file or directory > chmod: cannot access > '/opt/puppetlabs/puppet/share/vim/puppet-vimfiles/ftplugin/puppet.vim': No > such file or directory > chmod: cannot access > '/opt/puppetlabs/puppet/share/vim/puppet-vimfiles/indent/puppet.vim': No such > file or directory > chmod: cannot access > '/opt/puppetlabs/puppet/share/vim/puppet-vimfiles/syntax/puppet.vim': No such > file or directory > chmod: cannot access > '/etc/puppetlabs/code/environments/production/environment.conf': No such file > or directory > Setting up puppetserver (2.8.1-1puppetlabs1) ... > usermod: no changes > > This is on an Ubuntu 16 server and still puppetserver complains about stuff > being missing such as the CAservice now. > > Anybody else run into this? > > > -- > 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/CAArvnv2UyOurHTWArzv7DWUtjtJb85C%2BAPZb%3D2EQAYfF%2B-HScw%40mail.gmail.com. > For more options, visit https://groups.google.com/d/optout. Josh -- Josh Cooper | Software Engineer j...@puppet.com | @coopjn -- 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/CA%2Bu97unXLyfrqDJ4n72%2BvR6SYjja%2B9EvFzhWA%3D5MRbMv_VWPFg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] [Puppet-Users] Puppet Platform 6 Update
etlabs/puppet-specifications <https://github.com/puppetlabs/puppet-specifications> for more details on how to use it.* -- Josh Cooper | Software Engineer j...@puppet.com | @coopjn -- 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/CA%2Bu97u%3D75niK-2BgNanor9p6tHmHOhV1p%2BepLGOvs0rNPaf0Sw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] puppet module repository w/ self signed ssl?
On Tue, Jun 5, 2018 at 8:52 AM, Sean wrote: > Hello, > > I'm wanting to use the module_repository setting in puppet.conf on my > puppet5 master. The local repo mirror we've setup requires SSL, but has a > self-signed cert. Is there a way to make puppet trust that cert? > > Mostly, I want to be able to use puppet module search as a convenience > since the environment is not internet connected. We use control repos and > r10k to deploy from the same repo and it works well. > > 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 view this discussion on the web visit https://groups.google.com/d/ > msgid/puppet-users/0e37e66d-469e-4a61-a6da-46e546ec62d9%40googlegroups.com > <https://groups.google.com/d/msgid/puppet-users/0e37e66d-469e-4a61-a6da-46e546ec62d9%40googlegroups.com?utm_medium=email_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > You should be able to follow the workaround in https://tickets.puppetlabs.com/browse/PUP-8889, but longer term we want to make it easier to support third-party CA certs for things like file sources, etc. Josh -- Josh Cooper | Software Engineer j...@puppet.com | @coopjn -- 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/CA%2Bu97u%3DKsrD2ZZYU_KU1RpcdccDkGfLt439y01x9UCB1_vFmxA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Puppet type provider help?
Not sure what's the issue is... but could you use the powershell module
instead https://github.com/puppetlabs/puppetlabs-powershell?
On Wed, Apr 4, 2018 at 2:09 PM, Jason McMahan <jason.m.mcma...@gmail.com>
wrote:
> Good day,
> I am reviewing a type and provider and would like input or help to better
> understand.
>
> The provider is
> require 'puppet/util'
> Puppet::Type.type(:winad_group).provide(:powershell) do
> confine :operatingsystem => :windows
> defaultfor :operatingsystem => :windows
>
> commands :powershell => Puppet::Util::Powershell.getPowershellCommand
>
> The type is
> Puppet::Type.newtype(:winad_group) do
>
> Then lastly there is a file /puppet/util/powershell.rb
> class Powershell
> def self.getPowershellCommand()
> if File.exists?("#{ENV['SYSTEMROOT']}\\sysnative\\
> WindowsPowershell\\v1.0\\powershell.exe")
> "#{ENV['SYSTEMROOT']}\\sysnative\\WindowsPowershell\\
> v1.0\\powershell.exe"
> elsif File.exists?("#{ENV['SYSTEMROOT']}\\system32\\
> WindowsPowershell\\v1.0\\powershell.exe")
> "#{ENV['SYSTEMROOT']}\\system32\\WindowsPowershell\\
> v1.0\\powershell.exe"
> else
> 'powershell.exe'
> end
> end
> end
>
> If i copy the syntax
> commands :powershell =>
> if File.exist?("#{ENV['SYSTEMROOT']}\\sysnative\\
> WindowsPowershell\\v1.0\\powershell.exe")
> "#{ENV['SYSTEMROOT']}\\sysnative\\WindowsPowershell\\
> v1.0\\powershell.exe"
> elsif File.exist?("#{ENV['SYSTEMROOT']}\\system32\\
> WindowsPowershell\\v1.0\\powershell.exe")
> "#{ENV['SYSTEMROOT']}\\system32\\WindowsPowershell\\
> v1.0\\powershell.exe"
> else
> 'powershell.exe'
> end
>
> Into my provider i am able to run the command correctly, why can i not
> autoload the powershell.rb file and properly use it across multiple
> providers?
>
> Thank you for any help.
>
> --
> 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/dc8c6918-683d-4d1f-ae2c-b94761c79239%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/dc8c6918-683d-4d1f-ae2c-b94761c79239%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
--
Josh Cooper | Software Engineer
j...@puppet.com | @coopjn
--
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/CA%2Bu97unm0mpK3_0D_fs8TcOYdNHuiBubYh0BSUr4_ESDES7P_Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Re: Puppet Agent Hang when PuppetServer Crashes...
On Fri, Jan 5, 2018 at 12:31 PM, John Sellens <jsell...@syonex.com> wrote: > Hi Josh - thanks for the info. > > Can I make an assertion that having the default read timeout be unlimited > is a mistake? In practical terms, anything over 60 seconds means > something is broken. > Timeouts are hard. How does the client know 60 seconds is long enough? Compile times of ~1 min are not unthinkable. Maybe the server is under heavy load? If the timeout is reached, what should the client do? Retry (bad idea since it makes the situation worse)... Fail (bad idea if the server was making progress)... > Could I suggest (without having to go and update the bug because I'm a > bad bad lazy person) that along with the watchdog you change the default > timeout to, say, 5 minutes? That's effectively infinite, but would > likely keep things from getting stuck. > It's definitely possible for the connection to be lost between the time that the server responds and when the agent would normally receive the response. In this half-open scenario, the agent may wait indefinitely, so I agree having a timeout "less than infinite" makes sense. I'm thinking it should be strictly less than runinterval, otherwise you could have agent runs stacking up, and contending for the agent lock. (I wrote some tools back in the early puppet 3 days to run puppet the > way I wanted, and of course I included a timeout on the total run time. > There were some interesting failure modes back in the olden days.) > Yeah, "interesting" is one way to put it :) Puppet 2/3 conflated TCP connect and read timeouts. And it required that the *entire* pluginsync operation take less than Puppet[:configtimeout] minutes (defaulted to 2), otherwise the agent would abort the pluginsync operation, even though it could be making progress downloading individual files (see PUP-2885)! > Thanks - cheers! > > John > > > > On Fri, 2018/01/05 11:53:12AM -0800, Josh Cooper <j...@puppet.com> wrote: > | In Puppet 4 we added settings for configuring http connect and read > | timeouts independently[1]. Previously they were both controlled by the > | configfiletimeout. The default read timeout is unlimited, so the hung > agent > | may be stuck in a socket read. You might want to strace the stuck agent > to > | see what it's up to. > | > | In our upcoming 4.10.x/5.3.x releases, we've added a watchdog to kill a > | stuck run[2]. > | > | Josh > | > | [1] https://tickets.puppetlabs.com/browse/PUP-3666 > | [2] https://tickets.puppetlabs.com/browse/PUP-7517 > | > | -- > | Josh Cooper | Software Engineer > | j...@puppet.com | @coopjn > | > -- Josh Cooper | Software Engineer j...@puppet.com | @coopjn -- 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/CA%2Bu97u%3DCns%2BekXDO1rqQ2TmO1A1kH1JCW0kMtNkViLAHJ8j_Jw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] puppet 5 upgrade seems to have caused multiple 500 error on server with file resources (to Windows clients)
On Fri, Jan 26, 2018 at 8:28 AM, jmp242 <jp10...@gmail.com> wrote:
> Any idea when the puppet server 5.1.5 will be released as referenced in
> that bug report?
>
Puppetserver 5.1.5 was released January 31, and should resolve issues when
serving files whose paths contain URI special characters:
https://puppet.com/docs/puppetserver/5.2/release_notes.html#bug-fixes-1.
>
>
> On Tuesday, January 16, 2018 at 7:16:53 PM UTC-5, Josh Cooper wrote:
>>
>>
>>
>> On Tue, Jan 16, 2018 at 11:08 AM, jmp242 <jp1...@gmail.com> wrote:
>>
>>> We serve multiple file resources depending on configuration via puppet
>>> to Windows 7 and Windows 10 workstations using FLOSS puppet. This was
>>> working with puppet agent 1.10.4 on clients and with puppet server (and
>>> foreman fwiw) 4 on Scientific Linux 7.4. Since we upgraded puppet server to
>>> 5.latest we started having issues with deploying certain, random but
>>> consistent file resources that had worked on the earlier version. In the
>>> logs we see various Error 500 messages - but they all seem to be blank
>>> (i.e. no further info than: Failed to generate additional resources using
>>> 'eval_generate': Error 500 on SERVER: Server Error) or not googleable. The
>>> files are still there and permissions look the same to me on the server.
>>> The manifest code hasn't changed. What's weirder is it seems like some file
>>> resources served like this are working.
>>>
>>> This problem is most prevalent with files served as a defined type so I
>>> wonder if something happened around that?
>>> file { "DesignData-${title}":
>>> path=> "C:/VaultWorkspace/${title}/Vault/Design Data",
>>> source => "puppet:///modules/inventor/Design Data",
>>> recurse => true,
>>> purge => true,
>>> ensure => present,
>>> }
>>>
>>> Example defined type that's now failing with the above... We feed in an
>>> array of users and that's still being parsed correctly - logs show things
>>> like:
>>> //pc5102//Stage[main]/Inventor/Inventor::Designdata[username1]/File[DesignData-username1]
>>> :
>>> Failed to generate additional resources using 'eval_generate': Error 500
>>> on SERVER: Server Error
>>>
>>>
>>>
>> I think you're running into https://tickets.puppetlabs.com
>> /browse/SERVER-1954, which affects puppetserver 5.x and up. There was a
>> change in behavior in the bidi library we use, which breaks serving files
>> with URL special characters like spaces. So high likelihood of breaking
>> Windows agents.
>>
>>
>>> One other place that seems like a related file serving issue to me
>>> anyway is that I have an updated module to test (a forked reboot module)
>>> which I have deployed in my dev environment and code to use the new
>>> parameter, however when I try and apply the manifest I get errors - again
>>> 500 on server, this time that the new parameter doesn't exist. I'm
>>> wondering if this is also an issue with pluginsync or something like that
>>> so the client doesn't see the new module?
>>>
>>
>> That sounds like a lack of environment isolation issue on the compile
>> master. See https://puppet.com/docs/puppet/5.3/environment_isolation.html
>> .
>>
>>
>>>
>>> Any ideas as to what's gone wrong in the update?
>>>
>>> --
>>> 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...@googlegroups.com.
>>> To view this discussion on the web visit https://groups.google.com/d/ms
>>> gid/puppet-users/175349a2-26e3-40e1-b8f7-03e50a302919%40googlegroups.com
>>> <https://groups.google.com/d/msgid/puppet-users/175349a2-26e3-40e1-b8f7-03e50a302919%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> --
>> Josh Cooper | Software Engineer
>> jo...@puppet.com | @coopjn
>>
> --
> 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/e86e0
Re: [Puppet Users] Announce: Puppet Platform 5.3.4 is now available
On Tue, Feb 6, 2018 at 3:04 AM, SCHAER Frederic <frederic.sch...@cea.fr> wrote: > Hi, > > > > On my dev puppetserver, I have : > > # puppet config print environmentpath > > /puppet/code/envs > > > > # grep env /etc/puppetlabs/puppet/puppet.conf > > environmentpath = /puppet/code/envs > > environment = preprod > > > > (yes, the puppetserver for dev hosts is in env preprod ;) ) > > > > On all client nodes referring to that puppetserver, I see since today : > > # puppet agent -t > > Warning: Unable to fetch my node definition, but the agent run will > continue: > > Warning: Could not intern from application/json: Could not find a > directory environment named 'dev' anywhere in the path: > /etc/puppetlabs/code/environments. Does the directory exist? > > Info: Retrieving pluginfacts > > (…) > > And configuration goes on as before. If I change something in puppet, the > change is seen despite the warning. > > > > > > If I downgrade the puppet-server, this changes nothing. > > If I downgrade the puppet-agent, the warning goes away. But configuration > fails because of some unfound ruby gems – that’s new: > > Error: Could not convert change ensure to string: No such file or > directory @ rb_sysopen - /opt/puppetlabs/puppet/lib/ > ruby/gems/2.4.0/gems/fast_gettext-1.1.0/lib/fast_gettext/vendor/empty.mo > > Error: No such file or directory @ rb_sysopen - /opt/puppetlabs/puppet/lib/ > ruby/gems/2.4.0/gems/fast_gettext-1.1.0/lib/fast_gettext/vendor/empty.mo > > > > > > The puppet agent indeed has a default config that I did not specify – and > don’t want to, I’m running with a puppetserver : > > # puppet config print environmentpath > > /etc/puppetlabs/code/environments > > # grep env /etc/puppetlabs/puppet/puppet.conf > > environment = dev > > > > > > > > ð Question : what am I doing wrong ? > > > This was a regression in puppet-agent 5.3.4 involving non-default environments[1]. It will be fixed in puppet-agent 5.3.5. We have many acceptance tests for this functionality, but unfortunately they did not catch this particular failure mode when the initial node request fails. We'll be updating those tests to avoid regressing in the future[2]. Thanks > > > > > > *De :* puppet-users@googlegroups.com [mailto:puppet-users@googlegroups.com] > *De la part de* Molly Waggett > *Envoyé :* lundi 5 février 2018 21:10 > *À :* puppet-users@googlegroups.com > *Objet :* [Puppet Users] Announce: Puppet Platform 5.3.4 is now available > > > > This is a bug-fix release of Puppet Platform. All three components - > puppet-agent, PuppetDB, and Puppet Server - have been updated. > > > > This release of Puppet Agent updates Puppet to 5.3.4 and Facter to 3.9.4. > Puppet 5.3.4 adds two new settings, `sourceaddress` and `runtimeout`. It > also adds module translation distribution to pluginsync, improves Japanese > localization, and fixes several bugs. This release also adds support for > macOS 10.13 (High Sierra), EL 7 on arm64, and Amazon Linux 2. For details, > see the Puppet Agent > <https://puppet.com/docs/puppet/5.3/release_notes_agent.html> release > notes. > > > > PuppetDB 5.1.4 and Puppet Server 5.1.5 add Debian 9 (Stretch) packages, as > well as additional bug fixes. For details, see the Puppet Server > <https://puppet.com/docs/puppetserver/5.1/release_notes.html> and PuppetDB > <https://puppet.com/docs/puppetdb/5.1/release_notes.html> release notes. > > > > Thanks! > > > > -- > > *Molly Waggett* > > Release Engineer @ Puppet, Inc. > > -- > 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/CAFOE68B9vb1VfqAoq6S%2BOmmV6987S61n2NNxkHtCpxpXoEkC > XQ%40mail.gmail.com > <https://groups.google.com/d/msgid/puppet-users/CAFOE68B9vb1VfqAoq6S%2BOmmV6987S61n2NNxkHtCpxpXoEkCXQ%40mail.gmail.com?utm_medium=email_source=footer> > . > For more options, visit 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/CAB586860327CB498EF79903967FEA231A7A720B%40E-EXDAGE-A0. > extra.ce
Re: [Puppet Users] puppet 5 upgrade seems to have caused multiple 500 error on server with file resources (to Windows clients)
On Tue, Jan 16, 2018 at 11:08 AM, jmp242 <jp10...@gmail.com> wrote:
> We serve multiple file resources depending on configuration via puppet to
> Windows 7 and Windows 10 workstations using FLOSS puppet. This was working
> with puppet agent 1.10.4 on clients and with puppet server (and foreman
> fwiw) 4 on Scientific Linux 7.4. Since we upgraded puppet server to
> 5.latest we started having issues with deploying certain, random but
> consistent file resources that had worked on the earlier version. In the
> logs we see various Error 500 messages - but they all seem to be blank
> (i.e. no further info than: Failed to generate additional resources using
> 'eval_generate': Error 500 on SERVER: Server Error) or not googleable. The
> files are still there and permissions look the same to me on the server.
> The manifest code hasn't changed. What's weirder is it seems like some file
> resources served like this are working.
>
> This problem is most prevalent with files served as a defined type so I
> wonder if something happened around that?
> file { "DesignData-${title}":
> path=> "C:/VaultWorkspace/${title}/Vault/Design Data",
> source => "puppet:///modules/inventor/Design Data",
> recurse => true,
> purge => true,
> ensure => present,
> }
>
> Example defined type that's now failing with the above... We feed in an
> array of users and that's still being parsed correctly - logs show things
> like:
> //pc5102//Stage[main]/Inventor/Inventor::Designdata[
> username1]/File[DesignData-username1] :
> Failed to generate additional resources using 'eval_generate': Error 500
> on SERVER: Server Error
>
>
>
I think you're running into
https://tickets.puppetlabs.com/browse/SERVER-1954, which affects
puppetserver 5.x and up. There was a change in behavior in the bidi library
we use, which breaks serving files with URL special characters like spaces.
So high likelihood of breaking Windows agents.
> One other place that seems like a related file serving issue to me anyway
> is that I have an updated module to test (a forked reboot module) which I
> have deployed in my dev environment and code to use the new parameter,
> however when I try and apply the manifest I get errors - again 500 on
> server, this time that the new parameter doesn't exist. I'm wondering if
> this is also an issue with pluginsync or something like that so the client
> doesn't see the new module?
>
That sounds like a lack of environment isolation issue on the compile
master. See https://puppet.com/docs/puppet/5.3/environment_isolation.html.
>
> Any ideas as to what's gone wrong in the update?
>
> --
> 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/175349a2-26e3-40e1-b8f7-03e50a302919%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/175349a2-26e3-40e1-b8f7-03e50a302919%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
--
Josh Cooper | Software Engineer
j...@puppet.com | @coopjn
--
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/CA%2Bu97unGAGcO6a2FPgN%2BRPf9O%3Ds7dFa9RtFzxk%3Dj5-EXY%2BbPMw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] PSON.load fails when string contains e.g. "\n"
"Stage[main]",
> "target"=>"Class[Settings]"}], "classes"=>["settings"]},
> "metadata"=>{"api_version"=>1}}
>
> Can anyone spot the difference between what 'puppet catalog diff' does to
> read PSON, and what the code above does?
>
> --
> 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/2503d182-0c13-4543-ab9f-08f5852abb5c%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/2503d182-0c13-4543-ab9f-08f5852abb5c%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
I can reproduce the issue using a JSON snippet newlines.pson containing:
{
"content": "#!/bin/sh\nPRETEND_NCM_SSH_TRUST_IS_VALID=YES\n"
}
For some reason $MATCH is nil, which is bizarre[1]. Adding `require
'puppet'` to your script fixes the issue for me, or if I change puppet to
use the yielded parameter 'c' instead of '$MATCH'.
$ bx ruby preprocess.rb newlines.pson
Processing file: newlines.pson
/Users/josh/work/puppet/lib/puppet/external/pson/pure/parser.rb:183:in
`block in parse_string': Caught NoMethodError: undefined method `[]' for
nil:NilClass (PSON::GeneratorError)
from /Users/josh/work/puppet/lib/puppet/external/pson/pure/parser.rb:182:in
`gsub'
from /Users/josh/work/puppet/lib/puppet/external/pson/pure/parser.rb:182:in
`parse_string'
from /Users/josh/work/puppet/lib/puppet/external/pson/pure/parser.rb:216:in
`parse_value'
from /Users/josh/work/puppet/lib/puppet/external/pson/pure/parser.rb:280:in
`parse_object'
from /Users/josh/work/puppet/lib/puppet/external/pson/pure/parser.rb:92:in
`parse'
from /Users/josh/work/puppet/lib/puppet/external/pson/common.rb:121:in
`parse'
from /Users/josh/work/puppet/lib/puppet/external/pson/common.rb:255:in
`load'
from preprocess.rb:18:in `'
$ git stash pop
On branch 4.10.x
Your branch is up to date with 'upstream/4.10.x'.
Changes not staged for commit:
(use "git add ..." to update what will be committed)
(use "git checkout -- ..." to discard changes in working directory)
modified: lib/puppet/external/pson/pure/parser.rb
no changes added to commit (use "git add" and/or "git commit -a")
Dropped refs/stash@{0} (6ef5ec0fb8027f9957e9c5f55856389db79258cb)
$ PAGER= git diff
diff --git a/lib/puppet/external/pson/pure/parser.rb
b/lib/puppet/external/pson/pure/parser.rb
index cf607afc0a..58fa165b9d 100644
--- a/lib/puppet/external/pson/pure/parser.rb
+++ b/lib/puppet/external/pson/pure/parser.rb
@@ -180,7 +180,7 @@ module PSON
if scan(STRING)
return '' if self[1].empty?
string =
self[1].gsub(%r{(?:\\[\\bfnrt"/]|(?:\\u(?:[A-Fa-f\d]{4}))+|\\[\x20-\xff])}n)
do |c|
-if u = UNESCAPE_MAP[$MATCH[1]]
+if u = UNESCAPE_MAP[c[1]]
u
else # \u
bytes = ''
$ bx ruby preprocess.rb newlines.pson
Processing file: newlines.pson
{"content"=>"#!/bin/sh\nPRETEND_NCM_SSH_TRUST_IS_VALID=YES\n"}
Note bx is an alias for 'bundle exec'
Josh
[1]
https://github.com/puppetlabs/puppet/blob/4.10.9/lib/puppet/external/pson/pure/parser.rb#L183
--
Josh Cooper | Software Engineer
j...@puppet.com | @coopjn
--
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/CA%2Bu97uk8O_9%3D-2YNLjJj5e85A3%3Dth%3D6Zct8g1QT5bejKoGuuMQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Re: Puppet Agent Hang when PuppetServer Crashes...
On Mon, Jan 1, 2018 at 10:08 PM, Matt Wise <w...@wiredgeek.net> wrote: > We're still tuning, but I ended up dropping our PuppetServer JRubyInstance > count down to 2, and I have the -Xmx setting set to 4GB(!!). I think that > we have a few libraries loaded in that are causing some major bloat, but we > haven't had time to track that down yet. > > The big concern I have is not the crashing of the servers... we can handle > that. The main issue is that it seems that the Puppet Agents get into a > hung state and never recover. Thats not a behavior we ever saw on the older > Puppet 3.x clients. > > On Mon, Jan 1, 2018 at 9:50 PM, John Gelnaw <jgel...@gmail.com> wrote: > >> On Monday, January 1, 2018 at 5:52:10 PM UTC-5, Matt Wise wrote: >>> >>> *Puppet Agent: 5.3.2* >>> *Puppet Server: 5.1.4 - Packaged in Docker, running on Amazon ECS* >>> >> >> I'm running a docker-compose based puppet setup, and had the same >> problem. Short version was to increase the java heap size for the JRuby >> instances for puppetserver. >> >> Using the docker-compose.yml, I added: >> >> environment: >> - PUPPETSERVER_JAVA_ARGS=-Xmx1024m >> >> to the puppet stanza, which gets passed to the puppetserver init script. >> >> We also increased the number of JRuby instances to 7, but that might be >> overkill (roughly 200-250 nodes). That also means 8 gigs of memory on the >> docker host. >> >> The agents would eventually time out, but I seem to recall it was on the >> order of hours for the timeout. >> >> -- >> 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/ms >> gid/puppet-users/20b2d83e-7752-4f87-995f-3ec2fcde5368%40googlegroups.com >> <https://groups.google.com/d/msgid/puppet-users/20b2d83e-7752-4f87-995f-3ec2fcde5368%40googlegroups.com?utm_medium=email_source=footer> >> . >> >> For more options, visit 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/ms > gid/puppet-users/CA%2B9wXBTFODg4VLw5Zmc0eq9DG-i3YZtR5VSWs_ > krJFkaQzRHMQ%40mail.gmail.com > <https://groups.google.com/d/msgid/puppet-users/CA%2B9wXBTFODg4VLw5Zmc0eq9DG-i3YZtR5VSWs_krJFkaQzRHMQ%40mail.gmail.com?utm_medium=email_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > In Puppet 4 we added settings for configuring http connect and read timeouts independently[1]. Previously they were both controlled by the configfiletimeout. The default read timeout is unlimited, so the hung agent may be stuck in a socket read. You might want to strace the stuck agent to see what it's up to. In our upcoming 4.10.x/5.3.x releases, we've added a watchdog to kill a stuck run[2]. Josh [1] https://tickets.puppetlabs.com/browse/PUP-3666 [2] https://tickets.puppetlabs.com/browse/PUP-7517 -- Josh Cooper | Software Engineer j...@puppet.com | @coopjn -- 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/CA%2Bu97umYXi5thW62G31TQ9XRuw1quB2POPQop4L6Pd5zRwfi%3DQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Service set to stopped causes error when the service doesn't exist on Windows
On Thu, Jun 22, 2017 at 9:03 AM, jmp242 <jp10...@gmail.com> wrote:
> I want to make sure Firefox isn't automatically updating itself on our
> Windows computers. In most instances, if I have a service set to stopped,
> not having it installed should equal the same thing. How could I express
> either is OK in Puppet?
>
> service { 'FirefoxUpdateService':
> name => 'mozillamaintenance',
> ensure => stopped,
> }
>
> is throwing an error on my systems that don't seem to have that
> service What's the right solution here?
>
> 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 view this discussion on the web visit https://groups.google.com/d/
> msgid/puppet-users/c6e6ac99-3918-44cb-a8a2-328239db86e8%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/c6e6ac99-3918-44cb-a8a2-328239db86e8%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
Sounds like you're running into
https://tickets.puppetlabs.com/browse/PUP-6822. I recommend voting for the
ticket and adding yourself as a watcher.
Josh
--
Josh Cooper | Software Engineer
j...@puppet.com | @coopjn
--
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/CA%2Bu97un53BPFkdKw9CWRHAEv40s7zacuS7S-r87n6zdbGoCuug%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Re: Scheduled_task?
On Wed, May 17, 2017 at 5:34 AM, Jason McMahan <jason.m.mcma...@gmail.com> wrote: > The full error is > > Error: Failed to call > #::NewWorkItem > with HRESULT: -214702489 > 3.: The system cannot find the path specified. > Error: /Stage[main]/Profile::Windows::Applications::Sysinfo::Base/ > Scheduled_task[Automation/Inventory]/ensure > : change from absent to present failed: Failed to call > #::New > WorkItem with HRESULT: -2147024893 <(214)%20702-4893>.: The system > cannot find the path specified. > > The folder exists but the task is not created nor seen. > > I believe i may just need to create it in the root but would like > verification. > > Thank you > > > > On Tuesday, May 16, 2017 at 6:59:17 PM UTC-5, Jason McMahan wrote: >> >> Good day, >> We were using the scheduled_task resource to create a task. It creates >> the task however we nwed to create the task in a folder under task >> scheduler. >> \automation\inventory >> >> We tried name => '\automation\inventory\ >> But at run says can not find path. >> We looked at working_dir but that didn't sound promising either. Any >> suggestions would be greatly appreciated. Thank you >> > -- > 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/53648950-dc88-4188-b2e4-678a1a14dec0%40googlegroups.com > <https://groups.google.com/d/msgid/puppet-users/53648950-dc88-4188-b2e4-678a1a14dec0%40googlegroups.com?utm_medium=email_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > Puppet only supports v1 of the Windows task scheduler API (which is present in 2003 and up), so I'm inclined to think folders are a v2 API feature, which is filed as https://tickets.puppetlabs.com/browse/PUP-6455. Josh -- Josh Cooper | Software Engineer j...@puppet.com | @coopjn -- 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/CA%2Bu97ukAMKHZDLmD-G8TyPDKNGYdDJf9uaVPW1AVgBdHOs3t9g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Puppet-Agent
On Sat, May 13, 2017 at 9:56 AM, Linux Info <linuxinf...@gmail.com> wrote: > Hello, > > I am trying to connect puppet master node(Centos-7) from fresh puppet > agent node (Centos-7), but getting below errors while executing "puppet > agent -t". > > [root@puppet_client_1 ~]# puppet agent -t > Info: Creating a new SSL key for puppet_client_1 > Error: Could not request certificate: execution expired > Exiting; failed to retrieve certificate and waitforcert is disabled > > Requesting to go through with attached logs to resolve this issue. > > Please let me know if you need any info for the same. > > Best Regards, > Deepankar A > > > -- > 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/CAD33ukGmU_NKBgRcEMGGDQ_LHziHOsUd54yxmJx_ > 4HFF4EEpJw%40mail.gmail.com > <https://groups.google.com/d/msgid/puppet-users/CAD33ukGmU_NKBgRcEMGGDQ_LHziHOsUd54yxmJx_4HFF4EEpJw%40mail.gmail.com?utm_medium=email_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > By default puppet agents will try to connect to "puppet". You likely need to specify the server to connect to (either on the command line or puppet.conf), e.g. puppet agent -t --server . Josh -- Josh Cooper | Software Engineer j...@puppet.com | @coopjn -- 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/CA%2Bu97ukwHLYupbs%3DEnskrwE5AVHmrT%3Dd7a8oecXDP152zT9oyA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Could not find resource, but it's there.
On Mon, Jan 9, 2017 at 2:56 AM, Henrik Lindberg <henrik.lindb...@puppet.com>
wrote:
> On 09/01/17 02:52, chris smith wrote:
>
>> Hi,
>>
>> This seems like a pretty simple thing but I can't figure out why this is
>> throwing a warning.
>>
>> I'm using puppet 4.8.1 installed from the puppetlabs-pc1 on scientific
>> linux 6.
>>
>> # puppet -V
>> 4.8.1
>> # rpm -q puppet-agent
>> puppet-agent-1.8.2-1.el6.x86_64
>>
>>
>> My file is as simple as I can make it:
>>
>> file {'/test':
>> ensure => directory,
>> alias => 'abc',
>> }
>>
>> file {'/test/2':
>> ensure => directory,
>> require => File['abc'],
>> }
>>
>>
>> When I run it, it complains:
>>
>> # puppet apply test.pp
>> Warning: Could not find resource 'File[abc]' in parameter 'require'
>>(at /root/test.pp:8)
>> Notice: Compiled catalog for sl-x86-64.local in environment production
>> in 0.10 seconds
>> Notice: /Stage[main]/Main/File[/test]/ensure: created
>> Notice: /Stage[main]/Main/File[/test/2]/ensure: created
>> Notice: Applied catalog in 0.04 seconds
>>
>> Though it seems to apply the resources in the correct order (I haven't
>> had it fail trying to create /test/2 before /test).
>>
>> Any info or ideas would be great.
>>
>>
> The reason it works is because the default ordering is "manifest order"
> and your manifest has the resources in the correct order.
>
> The reference File['abc'] does not succeed because 'abc' is an alias, and
> not the title - I believe there is a ticket about that already logged.
>
Filed as https://tickets.puppetlabs.com/browse/PUP-6984
>
> - 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/ms
> gid/puppet-users/1d0fd21d-f1a2-5f41-b53d-b0de9c4873f8%40puppet.com.
>
> For more options, visit https://groups.google.com/d/optout.
>
--
Josh Cooper
Developer, Puppet
--
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/CA%2Bu97ukjvHzs1rcu4qb55VYeMy8DnyFX6L0Wihfx0FyVvrcWkQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Unable to install r10k 1.5.1
On Tue, Dec 13, 2016 at 2:45 PM, Matthew Kennedy <mattkenn4...@gmail.com> wrote: > I'm running OSS 3.8 using r10k 1.5.1 and ruby 1.9.3p551 (2014-11-13) > [x86_64-linux] Brightbox > > Error from puppet run. > > Error: Could not update: Execution of '/usr/bin/gem install -v 1.5.1 > --no-rdoc --no-ri r10k --no-ri --no-rdoc' returned 1: ERROR: Error > installing r10k: > fast_gettext requires Ruby version >= 2.1.0. > Various gems are starting to require ruby 2.1 or greater, eg addressable, fast_gettext. In order to continue running with earlier ruby versions, you'll need to pin fast_gettext to an earlier version, e.g. https://github.com/puppetlabs/puppetlabs-apache/commit/03f93e5b0706fa3f47068e33f8ba80c58bab81f8 , https://github.com/puppetlabs/puppet/commit/c3feeca63161127ffd4f66f590df3e75d9f0a62c > It appears that gettext-setup bump a version that changed the dependency > for fast_gettext from fast_gettext ~> 1.1.0 to fast_gettext ~> 1.1 > You might want to submit a PR to r10k to restrict fast_gettext to <= 1.1.0 when running on ruby < 2.1. > This appears to be the commit that changed the dependency > https://github.com/puppetlabs/gettext-setup-gem/commit/ > 7c3b2fe7ee09136515dc84a5c9ac704e1ad2effc > > > -- > 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/3c426e75-bbc1-4b54-bf49-d2b1cb8ddbd6%40googlegroups.com > <https://groups.google.com/d/msgid/puppet-users/3c426e75-bbc1-4b54-bf49-d2b1cb8ddbd6%40googlegroups.com?utm_medium=email_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- Josh Cooper Developer, Puppet -- 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/CA%2Bu97unLUWCmQPANz5pyKcn49M8Rjp6hZf-OXvU5-CYoSbz3Hw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Very frequent "Error: Could not request certificate: The certificate retrieved from the master does not match the agent's private key." on Windows
dowing that > constantly on newly provisioned hosts, right? > > I think that sums things up quite good, as said I've been baning my head > against this, while not ignoring it, could still be something fishy going > on on the puppetmaster that is not managed by me, but me colleauges in the > linux neighborhood don't ecperience this so it is seemingly something to do > with the Windows hosts. > > Cheers, > Fredrik > > -- > 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/56a91341-3509-403a-8eb7-e88d903eb02f%40googlegroups.com > <https://groups.google.com/d/msgid/puppet-users/56a91341-3509-403a-8eb7-e88d903eb02f%40googlegroups.com?utm_medium=email_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- Josh Cooper Developer, Puppet PuppetConf 2016 <https://puppet.com/puppetconf>, 19 - 21 October, San Diego, California *Register to attend or sign up to view the Live Stream <https://puppet.com/puppetconf/registration-pricing>* -- 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/CA%2Bu97unCw79eqr_%2Bm2gd%3Dc6X9XWXOx-0P_UM_eaePrQQ89%2BK%2Bw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Dependacies with Custom Types
Thanks Rob and John. I filed to https://tickets.puppetlabs.com/browse/DOCUMENT-573 to improve the docs in this area. Feel free to comment on the ticket. On Wednesday, July 13, 2016 at 6:54:23 AM UTC-7, Rob Nelson wrote: > > I second this motion, that was a great explanation. I'd love to see that > documented well and maybe in a git repo with a 'bad' and 'good' branch to > better examine the differences, if at all possible! > > > Rob Nelson > rnel...@gmail.com > > On Wed, Jul 13, 2016 at 8:51 AM, jcbollinger <john.bo...@stjude.org > > wrote: > >> >> >> On Wednesday, July 13, 2016 at 12:52:58 AM UTC-5, Josh Cooper wrote: >> [A clear and detailed explanation...] >> >> That was great, Josh. Are the same instructions available somewhere >> among Puppet's online docs and tutorials? If not, they should be. >> >> John >> >> -- >> 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...@googlegroups.com . >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/puppet-users/774fe4a8-0aa4-4227-958a-b97e5e3afe75%40googlegroups.com >> >> <https://groups.google.com/d/msgid/puppet-users/774fe4a8-0aa4-4227-958a-b97e5e3afe75%40googlegroups.com?utm_medium=email_source=footer> >> . >> >> For more options, visit 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/587659fe-3e0b-4636-bf07-8b9c75f172ca%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] puppetserver custom mount Error 400
Hi Chet, As Rob has stated - make sure the user that the Puppet master process is running as has permission to read + execute. Cheers, Josh -- 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/e8f108a8-c62f-40f3-ad51-28bc3c7d1c54%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Dependacies with Custom Types
t;> For more options, visit https://groups.google.com/d/optout. >>> >> >> >> -- >> >> Rob Nelson >> rnel...@gmail.com >> >> -- > 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/ff193af2-9a75-4930-afca-ce2ca87779b4%40googlegroups.com > <https://groups.google.com/d/msgid/puppet-users/ff193af2-9a75-4930-afca-ce2ca87779b4%40googlegroups.com?utm_medium=email_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > Josh -- Josh Cooper Developer, Puppet PuppetConf 2016 <https://puppet.com/puppetconf>, 19 - 21 October, San Diego, California *Early Birds save $350* <https://www.eventbrite.com/e/puppetconf-2016-october-17-21-tickets-18750712887?discount=EarlyBird> - Register by 15 July -- 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/CA%2Bu97u%3DjW7ht3qr__VbkAZ7M7sVoqmo7ezW%3DyNf7m906SxpXpQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Re: SRV records not working correctly
On Fri, Jun 24, 2016 at 8:41 AM, Martin Jackson <martin.h.jack...@gmail.com> wrote: > You might need: > pluginsource = puppet:///plugins > pluginfactsource = puppet:///pluginfacts > > In your puppet.conf. > That's good advice if you're using puppet < 4 and the debug output seems to match that (since the host in the URL is "puppet"): Error: /File[/var/lib/puppet/facts.d]: Could not evaluate: Could not retrieve file metadata for puppet://puppet/pluginfacts: getaddrinfo: Name or service not known Note that issue should be fixed in 4.0 (see https://tickets.puppetlabs.com/browse/PUP-1035). We've had a report of a related issue in 4.x (see https://tickets.puppetlabs.com/browse/PUP-6297). Maybe related? > > On Thursday, June 23, 2016 at 3:35:42 PM UTC-5, Matthew Ceroni wrote: >> >> I am attempting to load balance two master servers via SRV records. >> >> https://gist.github.com/cyrus-mc/fefef0d07dcb6fe211ad8514ce2c710a >> >> As you can see at line 6 it finds 2 records for the specified SRV. At >> line 15 it makes a connection to one of the Puppet servers. >> >> However at line 29 it connects to https://puppet:8140 which is the >> default puppet server if one isn't specified. >> >> Further down the connection details you see it does another SRV lookup >> (line 76), finds 2 records (as it should) and makes a connection to one of >> them for catalog compilation. >> >> So SRV records appear to be working a little. Not sure what is happening >> around line 29 to cause it to just try and connect to puppet. >> >> 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 view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/c358a880-b138-4df1-bdc3-78a792809ce1%40googlegroups.com > <https://groups.google.com/d/msgid/puppet-users/c358a880-b138-4df1-bdc3-78a792809ce1%40googlegroups.com?utm_medium=email_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- Josh Cooper Developer, Puppet PuppetConf 2016 <http://2016.puppetconf.com/>, October 17-21, San Diego, California *Early Birds save $350* <https://www.eventbrite.com/e/puppetconf-2016-october-17-21-tickets-18750712887?discount=EarlyBird> - Register by June 30th -- 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/CA%2Bu97u%3DhqxAZcgEH4t25FcRFJg6ZFcyLZtJSJXHPCT9oJ0%2BKZg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Autorequire defined type from custom type
Hi Matt, On Thu, Jun 9, 2016 at 6:59 AM, Matt Dainty <m...@bodgit-n-scarper.com> wrote: > As per subject, is it possible to autorequire a defined type within a > custom type? > > It's not currently possible, but there's a ticket filed at https://tickets.puppetlabs.com/browse/PUP-5360, and a work in progress PR at https://github.com/puppetlabs/puppet/pull/4337. > I've previously done `autorequire(:a_type) do ... end` for both built in > and other custom types but I was wondering if it's possible and therefore > what do I pass to `autorequire()`? > > Matt > > -- > 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/20160609135937.GD13102%40simulant.bodgit-n-scarper.com > . > For more options, visit https://groups.google.com/d/optout. > -- Josh Cooper Developer, Puppet PuppetConf 2016 <http://2016.puppetconf.com/>, October 17-21, San Diego, California *Early Birds save $350* <https://www.eventbrite.com/e/puppetconf-2016-october-17-21-tickets-18750712887?discount=EarlyBird> - Register by June 30th -- 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/CA%2Bu97umgjj3oL7ZbkJCKAo--hvz6R%3DiWeE%3DHnpu74ByOV4vTEw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Re: Puppet on windows ignoring puppet.conf
On Tue, Apr 19, 2016 at 7:56 AM, Mike Sharpton <sharpt...@gmail.com> wrote: > Note sure if they changed the path with 1.4.1. The path used to be what > is below. May want to try that. > Just to confirm, we haven't changed the location of where puppet.conf goes. > > C:\programdata\PuppetLabs\puppet\etc > Yep that's the one. Note C:\ProgramData is by default hidden. Also you can ask puppet where it thinks its puppet.conf should be (so you can be sure you're editing the same file that the agent will read): C:\>puppet agent --configprint config C:/ProgramData/PuppetLabs/puppet/etc/puppet.conf Note if you are running puppet not elevated, it will attempt to use the per-user location: C:\>puppet agent --configprint config C:/Users//.puppetlabs/etc/puppet/puppet.conf > > On Tuesday, April 19, 2016 at 9:38:20 AM UTC-5, Mattis Haase wrote: >> >> Hello, >> >> we have been using puppet for unix machines for quite a while and it >> works fine. >> >> I have installed the latest puppet-agent (1.4.1) on Windows Server >> 2012R2. The installation went fine and the communication between the >> puppetmaster and the client works. >> >> However, it uses the production environment, ignoring the environment >> setting in: >> >> c:\program files\puppet labs\puppet\etc\puppet.conf >> >> >> It is worth noting that this folder did originally not exist. The folder >> for the conf files was: >> >> c:\program files\puppet labs\puppet\puppet\conf >> >> >> However, all documentation points torwards the first folder. I put the >> same puppet conf into these three folders: >> >> c:\program files\puppet labs\puppet\puppet\conf >> c:\program files\puppet labs\puppet\puppet\etc >> c:\program files\puppet labs\puppet\etc >> >> >> The contents of the file are this: >> >> # This file can be used to override the default puppet settings. >> # See the following links for more details on what settings are available: >> # - >> https://docs.puppetlabs.com/puppet/latest/reference/config_important_settings.html >> # - >> https://docs.puppetlabs.com/puppet/latest/reference/config_about_settings.html >> # - >> https://docs.puppetlabs.com/puppet/latest/reference/config_file_main.html >> # - >> https://docs.puppetlabs.com/puppet/latest/reference/configuration.html >> [main] >> server=puppetmaster.develop.local >> environment=develop >> >> >> However, it still tries to pull from the production environment. >> >> >> puppet.bat agent --configprint environment >> production >> >> >> I restarted the service, to no avail. >> > -- > 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/51f8bdbc-875e-44a5-bbbf-4014e31b3ebc%40googlegroups.com > <https://groups.google.com/d/msgid/puppet-users/51f8bdbc-875e-44a5-bbbf-4014e31b3ebc%40googlegroups.com?utm_medium=email_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- Josh Cooper Developer, Puppet PuppetConf 2016 <http://2016.puppetconf.com/>, October 17-21, San Diego, California *Early Birds save $350* <https://www.eventbrite.com/e/puppetconf-2016-october-17-21-tickets-18750712887?discount=EarlyBird> - Register by June 30th -- 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/CA%2Bu97u%3DxXWoPtYf8-s3_60FkgO%2Bjo09DO%2BPXXNwaL2Z-fhkr3A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Re: Augeas failing when acting on smb.conf
Hi David, Thanks very much for your message, I can confirm this worked! I dropped the new samba.aug into /usr/share/augeas/lenses and it fixed the issue. Appreciate your help. Cheers, Josh On Friday, 26 February 2016 17:20:12 UTC, David Lutterkort wrote: > > On Thursday, February 25, 2016 at 4:41:29 AM UTC-8, Josh Sinfield wrote: >> >> Hi, >> >> I think this is the error you are seeing: >> https://fedorahosted.org/augeas/ticket/354 >> https://github.com/hercules-team/augeas/issues/276 >> >> We also receive this error. >> There seems to be no rpm package available for RHEL6 >1.0.0 nor >1.1.0 >> for RHEL7. >=1.2.0 contains the fix we need. 1.2.0 is available on RHEL5 >> however?!?! >> >> I am going to look at building our own rpm from source, but don't have >> time right now. I tried yesterday but it failed near the end. >> > > You don't necessarily have to rebuild the RPM. Try to drop a newer > samba.aug (e.g., from augeas 1.4.0) into /usr/share/augeas/lenses/ and see > if that resolves the issue. By default, Augeas loads lenses from > /usr/share/augeas/lenses and /usr/share/augeas/lenses/dist, in that order; > the latter is reserved for the lenses that ship with Augeas, but the former > is the right place to drop user-defined lenses, or overrides of lenses that > ship with it. > > David > -- 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/3a9ebc58-64e6-4732-b07d-0e8197ef44d8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Re: Augeas failing when acting on smb.conf
Hi, I think this is the error you are seeing: https://fedorahosted.org/augeas/ticket/354 https://github.com/hercules-team/augeas/issues/276 We also receive this error. There seems to be no rpm package available for RHEL6 >1.0.0 nor >1.1.0 for RHEL7. >=1.2.0 contains the fix we need. 1.2.0 is available on RHEL5 however?!?! I am going to look at building our own rpm from source, but don't have time right now. I tried yesterday but it failed near the end. Cheers, Josh On Tuesday, 4 August 2015 15:56:08 UTC+1, Fabrizio Zelaya wrote: > > Here's the file and I will open a bug report too. Maybe between here and > there we can find the issue. > > Thank you! > > On Tue, Aug 4, 2015 at 10:42 AM, Raphaël Pinson <raphael...@camptocamp.com > > wrote: > >> Is there a way you can post the entire file somewhere maybe? Ideally even >> open a bug report on Augeas, with the file. >> >> >> >> On Tuesday, August 4, 2015 at 4:35:38 PM UTC+2, Fabrizio Zelaya wrote: >>> >>> Martin: We don't use templates because our server have different shares >>> and printers declare on smb.conf and we don't want to touch that. We want >>> puppet to manage only the part that's relevant to DC. >>> >>> Werner and Raphael: Thanks for clarifying a little bit, as I mentioned >>> I'm very new to augeas and I'm trying to make sense of the messages too. >>> >>> There's no line 2545 and on line 67 I got >>> idmap config * : backend = rid >>> >>> There's no column 2545 either following lines are >>>winbind rpc only = true >>>winbind normalize names = true >>> >>> >>> >>> >>> >>> On Tue, Aug 4, 2015 at 10:29 AM, Raphaël Pinson < >>> raphael...@camptocamp.com> wrote: >>> >>>> Sorry, my bad. What's on line 67 of your file? >>>> >>>> >>>> On Tuesday, August 4, 2015 at 3:05:12 PM UTC+2, Werner Flamme wrote: >>>>> >>>>> Raphaël Pinson [04.08.2015 14:03]: >>>>> > Hello, >>>>> > >>>>> > >>>>> > What do you have on line 2545 in your smb.conf? >>>>> >>>>> Isn't this line 67, character 2545? >>>>> >>>>> I guess the characters are counted through the whole file and not for >>>>> each line ;) >>>>> >>>>> > >>>>> > >>>>> > >>>>> > Regards, >>>>> > >>>>> > Raphaël Pinson >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > On Monday, August 3, 2015 at 11:04:01 PM UTC+2, Fabrizio Zelaya >>>>> wrote: >>>>> >> >>>>> >> Hello everyone! >>>>> >> >>>>> >> I am trying to run puppet agent on a SL-6 Machine and one action >>>>> I'm >>>>> >> trying to apply is to add the machine to our domain. However I ran >>>>> into an >>>>> >> issue when running puppet agent -t >>>>> >> >>>>> >> Debug: Augeas[global](provider=augeas): Opening augeas with root /, >>>>> lens >>>>> >> path /var/lib/puppet/lib/augeas/lenses, flags 64 >>>>> >> Debug: Augeas[global](provider=augeas): Augeas version 1.0.0 is >>>>> installed >>>>> >> Warning: Augeas[global](provider=augeas): Loading failed for one or >>>>> more >>>>> >> files, see debug for /augeas//error output >>>>> >> Debug: Augeas[global](provider=augeas): >>>>> >> /augeas/files/etc/samba/smb.conf/error = parse_failed >>>>> >> Debug: Augeas[global](provider=augeas): >>>>> >> /augeas/files/etc/samba/smb.conf/error/pos = 2545 >>>>> >> Debug: Augeas[global](provider=augeas): >>>>> >> /augeas/files/etc/samba/smb.conf/error/line = 67 >>>>> >> Debug: Augeas[global](provider=augeas): >>>>> >> /augeas/files/etc/samba/smb.conf/error/char = 0 >>>>> >> Debug: Augeas[global](provider=augeas): >>>>> >> /augeas/files/etc/samba/smb.conf/error/lens = >>>>> >> /usr/share/augeas/lenses/dist/inifile.aug:391.25-.43: >>>>> >> Debug: Augeas[global](provider=augeas): >>>>> >> /augeas/files/etc
Re: [Puppet Users] Error: Cannot start Windows Service. Access denied
On Thu, Jan 28, 2016 at 6:48 AM, Alex M <alex.marfunen...@googlemail.com>
wrote:
> Hi,
> i have Puppet v3.7.2 and same agent on Windows Server 2012 R2.
> Now i'm training to maintain Windows Services. For that i created new
> manifest:
>
> # cat /etc/puppet/modules/disablesmb/manifests/init.pp
> class disablesmb {
>
> service { 'Audiosrv':
> ensure => running,
> enable => true,
> }
>
> but when i run agent on Windows i get an error:
>
> C:\>puppet agent --test
> Info: Retrieving pluginfacts
> Info: Retrieving plugin
> Info: Caching catalog for test1.domain.company.com
> Info: Applying configuration version '1453991644'
> Error: Cannot start Audiosrv, error was: Execution of
> 'C:/Windows/system32/net.exe start Audiosrv' returned 2: System error 5 has
> occurred.
>
> Access is denied.
> Wrapped exception:
> Execution of 'C:/Windows/system32/net.exe start Audiosrv' returned 2:
> System error 5 has occurred.
>
> Access is denied.
> Error: /Stage[main]/Disablesmb/Service[Audiosrv]/ensure: change from
> stopped to running failed: Cannot start Audiosrv, error was: Execution of
> 'C:/Win
> dows/system32/net.exe start Audiosrv' returned 2: System error 5 has
> occurred.
>
> Access is denied.
> Notice: Finished catalog run in 0.14 seconds
>
> if i run it manually a get same error:
>
> C:\>net.exe start Audiosrv
> System error 5 has occurred.
>
> Access is denied.
>
> what is wrong?
>
> --
> 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/855b3a53-1dd0-4f80-b456-a96299f67c05%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/855b3a53-1dd0-4f80-b456-a96299f67c05%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
Most likely you are not running with elevated privileges, which is required
in order to manage services (and most other things you're going to want to
do with puppet).
Josh
--
Josh Cooper
Developer, Puppet Labs
--
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/CA%2Bu97ukzDz6gp0NPaxvwenEfCF91zPAUdYqFEa8mp78VZ4kqqg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] German Umlauts in Catalog
On Tue, Jan 19, 2016 at 1:09 AM, Bjoern Meier <bjoern.me...@gmail.com> wrote: > Hi, > > how can I use - with a puppet 3.8.3 x64 Windows clients - a File Resource > with öüä character. > > The test on the Master works fine. > On the Client I get: invalid byte sequence in US-ASCII and he cannot > ensure present on the file. > > Thanks for helping me out. > > -- > 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/8b11d187-5dff-40fe-b37d-91a9d2001cef%40googlegroups.com > <https://groups.google.com/d/msgid/puppet-users/8b11d187-5dff-40fe-b37d-91a9d2001cef%40googlegroups.com?utm_medium=email_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > If you are running `puppet agent` on Windows: * what is the output of ruby -e "puts Encoding.default_external" on the master and agent? * what is the agent's code page, e.g. chcp * can you provide a gist of `puppet agent --test --trace` on Windows, showing the stacktrace? * what encoding is the manifest stored in on the master? If you are running `puppet apply`: * what is the output of ruby -e "puts Encoding.default_external" on the agent? * what is the agent's code page, e.g. chcp * can you provide a gist of `puppet apply --trace` on Windows? * what encoding is the manifest stored in on the agent? Josh -- Josh Cooper Developer, Puppet Labs -- 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/CA%2Bu97umrV1x8FZuMS3SP_pEonLyKEYdY8hN2gr8TzCOqCGPipQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] How to cope with accented characters in DisplayName using Puppet 3.8.x on Windows XP?
Arquivos de programas/Puppet >> Labs/Puppet/facter/lib/facter.rb:35:in `' >> from C:/Arquivos de programas/Puppet >> Labs/Puppet/facter/lib/facter.rb:30:in `' >> from C:/Arquivos de programas/Puppet >> Labs/Puppet/sys/ruby/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in >> `require' >> from C:/Arquivos de programas/Puppet >> Labs/Puppet/sys/ruby/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in >> `require' >> from C:/Arquivos de programas/Puppet >> Labs/Puppet/puppet/lib/puppet.rb:6:in `' >> from C:/Arquivos de programas/Puppet >> Labs/Puppet/sys/ruby/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in >> `require' >> from C:/Arquivos de programas/Puppet >> Labs/Puppet/sys/ruby/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in >> `require' >> from C:/Arquivos de programas/Puppet >> Labs/Puppet/puppet/lib/puppet/util/command_line.rb:12:in `' >> from C:/Arquivos de programas/Puppet >> Labs/Puppet/sys/ruby/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in >> `require' >> from C:/Arquivos de programas/Puppet >> Labs/Puppet/sys/ruby/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in >> `require' >> from C:/Arquivos de programas/Puppet >> Labs/Puppet/puppet/bin/puppet:7:in `' >> >> Em segunda-feira, 11 de janeiro de 2016 09:30:46 UTC-2, Tiago Delboni >> escreveu: >>> >>> Hi Josh, thanks for the enlightenment! >>> Any chances I can easily upgrade 3.8.x 's Ruby to fix this issue without >>> breaking current manifests and behaviour? >>> >>> Em sexta-feira, 8 de janeiro de 2016 15:24:27 UTC-2, Josh Cooper >>> escreveu: >>>> >>>> >>>> >>>> On Fri, Jan 8, 2016 at 8:20 AM, Tiago Delboni <del...@gmail.com> wrote: >>>> >>>>> With parser=future it doesn't complain about the escape sequence, but >>>>> keeps creating the package every run. :( >>>>> >>>>> Copying the accented character to the manifest does not work (tried >>>>> many ways). >>>>> >>>>> >>>>> Em sexta-feira, 8 de janeiro de 2016 13:38:25 UTC-2, Henrik Lindberg >>>>> escreveu: >>>>> >>>>>> On 2016-08-01 14:23, Tiago Delboni wrote: >>>>>> > Hi! >>>>>> > >>>>>> > On Windows 7 we have Puppet 4.2.x and, in order to deal with >>>>>> accented >>>>>> > characters commonly found in registry key DisplayName, we use >>>>>> unicode >>>>>> > escape sequences in our manifests such as "\u00FA". >>>>>> > >>>>>> > However, on Windows XP, we couldn't install Puppet 4.2.x so we use >>>>>> > 3.8.x instead. When running the same manifest with escape >>>>>> sequences, >>>>>> > Puppet complains: "Unrecognised escape sequence '\u' in file ...". >>>>>> > >>>>>> Have you tried using 3.8.x with parser=future turned on? That would >>>>>> give >>>>>> you support for \u the same way as in puppet 4.x. >>>>>> >>>>>> > Puppet 3.8.x documentation states that it "treats strings as >>>>>> sequences >>>>>> > of bytes. It does not recognize encodings or translate between >>>>>> them, and >>>>>> > non-printing characters are preserved." >>>>>> > >>>>>> Yes, when you get the waring for \u, it means there will be a literal >>>>>> backslash and a literal u in the resulting string. (That is with the >>>>>> regular parser since it (as it says) does not support the \u escape >>>>>> for >>>>>> unicode chars). >>>>>> >>>>>> > So, how can I deal with software that have accented characters in >>>>>> their >>>>>> > DisplayName? Assuming that registry's encoding is the same on WXP >>>>>> and >>>>>> > W7, I could probably make it work by using Puppet 4.2.x on Windows >>>>>> XP, >>>>>> > but I just don't know how to install it successfully. >>>>>> > >>>>>> >>>>>> Use puppet 3.8.x (latest) as noted above. The other approach (ugly, >>>>>>
Re: [Puppet Users] Rubygem not visible to puppet
On Fri, Jan 8, 2016 at 3:14 AM, Fraser Goffin <goff...@gmail.com> wrote:
> Puppet Version: 4.3.1
> OS: Centos 7
>
> Note: I am running MASTERLESS
>
> I used this to install a gem :-
>
> package { 'rubyzip':
> ensure => present,
> provider => 'gem',
> }
>
> It installed fine, in this location :
> /usr/local/share/gems/gems/rubyzip-1.1.7
>
> gem env shows that the parent folder is on the gem path :-
>
> - GEM PATHS:
> - /home/vagrant/.gem/ruby
> - /usr/share/gems
> - /usr/local/share/gems
>
> However, when a Puppet manifest attempts to make use of that gem, it can't
> find it.
>
> Puppet has its own location for gems, in this particular install its :
> /opt/puppetlabs/puppet/lib/ruby/gems/2.1.0/gems
>
> If I change the package to include that directory as an install option,
> the gem is indeed installed there and Puppet can use it :-
>
> package { 'rubyzip':
> ensure => present,
> provider => 'gem',
> install_options => {
> '--install-dir' => "/opt/puppetlabs/puppet/lib/ruby/gems/2.1.0"
> }
> }
>
> However, this approach seems a bit of a hack and one that will utlimately
> create a maintenance overhead as/when Puppet's version of Ruby is updated,
> not to mention that we also run Puppet on other platforms (including
> Windows) which have different paths. I could handle that but it seems like
> there must be a better way of making this work cross platform without
> resorting to hard-coded paths even if that is parameterised.
>
> Has anyone got a suggestion how to solve this one more elegantly.
>
> Kind Regards
>
> Fraser.
>
> --
> 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/9073677f-6cca-40b4-8949-fba8553edee9%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/9073677f-6cca-40b4-8949-fba8553edee9%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
I'd recommend using the `puppet_gem` package provider, which in 4.x manages
gems in the AIO package, e.g.
package { 'rubyzip':
ensure => present,
provider => 'puppet_gem',
}
Josh
--
Josh Cooper
Developer, Puppet Labs
--
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/CA%2Bu97u%3DgLca%3Dygty%3DQA5fYDQy7WHqF665P6koyxfGORrGhLS9w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] How to cope with accented characters in DisplayName using Puppet 3.8.x on Windows XP?
On Fri, Jan 8, 2016 at 8:20 AM, Tiago Delboni <delb...@gmail.com> wrote: > With parser=future it doesn't complain about the escape sequence, but > keeps creating the package every run. :( > > Copying the accented character to the manifest does not work (tried many > ways). > > > Em sexta-feira, 8 de janeiro de 2016 13:38:25 UTC-2, Henrik Lindberg > escreveu: > >> On 2016-08-01 14:23, Tiago Delboni wrote: >> > Hi! >> > >> > On Windows 7 we have Puppet 4.2.x and, in order to deal with accented >> > characters commonly found in registry key DisplayName, we use unicode >> > escape sequences in our manifests such as "\u00FA". >> > >> > However, on Windows XP, we couldn't install Puppet 4.2.x so we use >> > 3.8.x instead. When running the same manifest with escape sequences, >> > Puppet complains: "Unrecognised escape sequence '\u' in file ...". >> > >> Have you tried using 3.8.x with parser=future turned on? That would give >> you support for \u the same way as in puppet 4.x. >> >> > Puppet 3.8.x documentation states that it "treats strings as sequences >> > of bytes. It does not recognize encodings or translate between them, >> and >> > non-printing characters are preserved." >> > >> Yes, when you get the waring for \u, it means there will be a literal >> backslash and a literal u in the resulting string. (That is with the >> regular parser since it (as it says) does not support the \u escape for >> unicode chars). >> >> > So, how can I deal with software that have accented characters in their >> > DisplayName? Assuming that registry's encoding is the same on WXP and >> > W7, I could probably make it work by using Puppet 4.2.x on Windows XP, >> > but I just don't know how to install it successfully. >> > >> >> Use puppet 3.8.x (latest) as noted above. The other approach (ugly, and >> horrible work around) is to simply copy/paste the actual character into >> the source file, but that is not guaranteed to work for all characters. >> >> Hope that helps >> - henrik >> >> > -- >> > 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...@googlegroups.com >> > <mailto:puppet-users+unsubscr...@googlegroups.com>. >> > To view this discussion on the web visit >> > >> https://groups.google.com/d/msgid/puppet-users/12713369-5970-4a43-804a-ca57a400afd0%40googlegroups.com >> > < >> https://groups.google.com/d/msgid/puppet-users/12713369-5970-4a43-804a-ca57a400afd0%40googlegroups..com?utm_medium=email_source=footer>. >> >> > For more options, visit https://groups.google.com/d/optout. >> >> >> -- >> >> 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/6084ba68-3ac0-458a-ab7c-292d11663e6b%40googlegroups.com > <https://groups.google.com/d/msgid/puppet-users/6084ba68-3ac0-458a-ab7c-292d11663e6b%40googlegroups.com?utm_medium=email_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > Puppet 3.8.x ships with ruby 1.9.3 (32-bit) and 2.0.0 (64-bit), both of which use ANSI versions of Win32 registry APIs (and not the wide/unicode versions). Puppet uses those methods to scan the registry looking for installed applications, and is likely the cause for the problem you're seeing. See https://tickets.puppetlabs.com/browse/PUP-2937?focusedCommentId=87973=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-87973 for more information. Puppet 4.x ships with ruby 2.1.x, which switched to using wide versions of the registry APIs, so I think that's why it's working in that case. Josh -- Josh Cooper Developer, Puppet Labs -- 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/CA%2Bu97ukcQF30gDp5u681Pfx8VWGcDj09gCFjyJ%3DQqv-RNiK6sw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Re: Can Windows environment variables be referenced by 'exec'
On Mon, Oct 12, 2015 at 8:09 AM, Leroy Tennison <leroy.tenni...@gmail.com>
wrote:
> Thanks for the replies, learned more than I imagined.
>
> On Friday, October 9, 2015 at 2:53:47 PM UTC-5, Leroy Tennison wrote:
>>
>> Puppet v3.4.3
>>
>> What I was specifically hoping to do was:
>>
>> exec { 'test' :
>>
>> command => "%comspec% /c (a Windows command-line program with
>> parameters)",
>>
>> }
>>
>>
>> to avoid having to determine where Windows was installed.
>>
>
One useful trick on Windows is to set the `path` parameter of the exec
resource to the value of the `path` fact so that you don't have to know
where Windows was installed:
exec { 'test':
command => "cmd.exe /c echo hello",
path => $path
}
It does assume you trust the `path` fact. For example, a user less
privileged than puppet shouldn't be able to manipulate the system in a way
that causes the `path` fact to contain user specified directories.
Although 'puppet parser vaildate init.pp' doesn't return an error the
>> client agent reports "...not qualified and no path was specified... " (I
>> realize the parser doesn't catch everything)
>>
>> I tried variants %%comspec%% and \%comspec\% (puppet parser complained
>> about this) but nothing works. If this is possible please provide an
>> example of the correct syntax, thanks.
>>
>> Now for the more general question, are environment variables defined on
>> Windows able to be used at all on the puppet server when specifying an
>> agent action?
>>
> --
> 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/d3526938-7e72-475b-890f-6600108136ad%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/d3526938-7e72-475b-890f-6600108136ad%40googlegroups.com?utm_medium=email_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>
Josh
--
Josh Cooper
Developer, Puppet Labs
--
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/CA%2Bu97ukcRywu-M3qNwPxvhVyGcwsPULGVH5eBX3jKd6%2BkWfD8w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Daemonized puppet on Windows and splay
On Wed, Oct 21, 2015 at 8:41 AM, Chris Spence <fiddyspe...@gmail.com> wrote: > We are running puppet (3.7.x) on Windows daemonized. We recently turned > on splay because reasons. After having done so the interval between > daemonised runs, counter to expectation, has become randomised (though we > get an averageish run interval of 30 minutes (30.5 recurring)). The > linuxes here have identical config and their runs are as regular as a > muesli eating vegetarian. Here are some report times and approximate delta > of a representative Windows 2012: > > Oct 21 2015 - 16:03:27 (14) > Oct 21 2015 - 15:49:10 (28) > Oct 21 2015 - 15:21:14 (33) > Oct 21 2015 - 14:48:23 (32) > Oct 21 2015 - 14:16:47 (23) > Oct 21 2015 - 13:53:35 (36) > Oct 21 2015 - 13:17:57 (27) > Oct 21 2015 - 12:54:02 (29) > Oct 21 2015 - 12:25:20 (53) > Oct 21 2015 - 11:31:48 > > Before I raise this as a bug, has anyone else seen this happening? > > -- > 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/fc651143-df27-4bed-948e-6b593f21e465%40googlegroups.com > . > For more options, visit https://groups.google.com/d/optout. > In 2.7-3.1, splay behaved the same on windows and *nix in that splay would vary every agent run. The behavior was changed on *nix in 3.2.0 for https://projects.puppetlabs.com/issues/14766. As part of that change, runinterval is calculated relative to the start of each agent run (instead of the end) and splay is only applied to the first run, but not the 2nd, etc. That way if you're running puppet via cron, the first daemonized run will splay, and each run after should be at a constant runinterval seconds. Previously, users would see "peaks" as runs started to overlap. I'm not sure how well known/understood the "new" *nix behavior is. The splay and splaylimit settings could use updating: https://docs.puppetlabs.com/references/latest/configuration.html#splay, and I know of at least one ticket: https://tickets.puppetlabs.com/browse/PUP-5542. Assuming the current *nix behavior is correct, I would agree Windows is not correct, and should be ticketed. Windows runs as a service that essentially runs `puppet agent --onetime` every run interval seconds ( https://github.com/puppetlabs/puppet/blob/master/ext/windows/service/daemon.rb#L74), and relies on puppet to splay each time. To match *nix behavior, the daemon would need to calculate the initial splay & splaylimit, and tell the agent to ignore those settings, so we don't get double-splay. Josh -- Josh Cooper Developer, Puppet Labs -- 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/CA%2Bu97umuX4DSzei7BdR75LxzNEEbuTyoCg_CzSDTcaDgU7yYnA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Re: How to include quoted string into a command
On Tue, Dec 15, 2015 at 10:20 AM, Vadym Chepkov <vchep...@gmail.com> wrote:
> Shell allows me to escape back-tick:
>
> $ echo "/var/log/syslog -C 8 -a 'kill -HUP \`cat /var/run/syslog.pid\`'"
> /var/log/syslog -C 8 -a 'kill -HUP `cat /var/run/syslog.pid`'
>
> puppet does like them:
>
> $string="/var/log/syslog -C 8 -a 'kill -HUP \`cat /var/run/syslog.pid\`'"
>
Puppet is interpreting \` as an escape sequence since it's in a
double-quoted string, and reporting that it's an invalid escape sequence. I
think you'll need to escape the backslash:
$string="/var/log/syslog -C 8 -a 'kill -HUP \\`cat /var/run/syslog.pid\\`'"
>
> exec{'echo string':
> command => "echo \" ${string} \" ",
> logoutput => true,
> path => '/bin:/usr/bin',
> }
>
> Warning: Unrecognised escape sequence '\`' in file /home/vc7733/quotes.pp
> at line 1
> Warning: Unrecognised escape sequence '\`' in file /home/vc7733/quotes.pp
> at line 1
> Notice: Compiled catalog for pubdevx-dev601.bnaint.com in environment
> production in 0.36 seconds
> Notice: /Stage[main]/Main/Exec[echo string]/returns: /var/log/syslog -C 8
> -a 'kill -HUP `cat /var/run/syslog.pid`'
>
> And as I said earlier, no, I can't use file_line
>
> Thanks,
> Vadym
>
>
> --
> 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/aee7a6c5-307f-4b55-87ac-85f205724ff4%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/aee7a6c5-307f-4b55-87ac-85f205724ff4%40googlegroups.com?utm_medium=email_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>
--
Josh Cooper
Developer, Puppet Labs
--
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/CA%2Bu97ungmrJ3rnzt3296Pfz0SVu-nXbMYOootVLkeCQfd5jXCg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Announce: Puppet-Agent 1.3.0
Puppet Agent 1.3.0 is now available. This is a feature release of the all-in-one agent, which bundles up Ruby, Puppet, Facter, and other components into a single package. Notable changes in this release: * Puppet 4.3.0 - adds an experimental puppet lookup system for module data, support for new language features used by Application Orchestration, new trusted facts, dnf package manager support, filebucket improvements, augeas improvements, and many bug fixes * Facter 3.1.2 - bug fixes to the os version fact on Mac OS X, enables accessing custom structured facts using dot syntax, and preferring dmidecode in puppet-agent * Hiera 3.0.5 - updated from 3.0.4 (testing-related changes only) * PXP Agent 1.0.0 - new component for the forthcoming Application Orchestration feature in Puppet Enterprise * Puppet Agent 1.3.0 - adds Fedora 22 and Mac OS X 10.11 (El Capitan) packages, registers puppet, facter, and hiera as gems, and adds a CA certificate component to enable Forge access Community shout-outs for awesome contributions go to Michael Marod for Augeas improvements, Romain Fihue for working on trusted facts and filebucket, and Jasper Lievisse Adriaanse (as usual) for improving Puppet's NetBSD support. Windows Server 2003 and 2003 R2 are no longer supported platforms as described in our previously announced deprecation: https://docs.puppetlabs.com/puppet/4.3/reference/deprecated_win2003.html You can see links to the full release notes for puppet-agent and individual components here: http://docs.puppetlabs.com/puppet/4.3/reference/about_agent.html To install or upgrade puppet-agent, follow the getting started directions: http://docs.puppetlabs.com/puppet/4.3/reference/index.html -- Josh Cooper Developer, Puppet Labs -- 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/CA%2Bu97uk3sqinR3_NZEbRL-0qsYbp3Vugv63Ja70ez6ZJ_%3DXdwA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Re: External fact script provided by module not parsing on CentOS6
Hi Roan, On Mon, Oct 5, 2015 at 9:36 AM, Roan O'Sullivan <roanosulli...@gmail.com> wrote: > Seems like this may be a regression: > https://tickets.puppetlabs.com/browse/PUP-2705 > > PUP-2705 was closed and marked as fixed in PUP 3.6.2 > <https://tickets.puppetlabs.com/browse/PUP/fixforversion/11726>. However > this same issue is occurring in PE 3.8.1. > > On Monday, October 5, 2015 at 11:47:08 AM UTC-4, Roan O'Sullivan wrote: >> >> I think it's a permissions issue, but not sure how to best resolve. >> >> On CentOS6 the plugin sync sets file mode for external fact script >> (/var/opt/lib/pe-puppet/facts.d/myfacts.sh) to 0644, and then agent (or >> standalone puppet) reports that the file "parsed but returned an empty data >> set": >> >> [root@foo ~]# puppet apply -e 'notice($mypkg_installed)' --environment >> development >> Fact file /var/opt/lib/pe-puppet/facts.d/myfacts.sh was parsed but >> returned an empty data set >> Notice: Scope(Class[main]): >> Notice: Compiled catalog for foo.local in environment development in 0.01 >> seconds >> Notice: Finished catalog run in 0.13 seconds >> [root@foo ~]# >> >> If I "chmod a+x" the script then the fact parses successfully: >> >> [root@foo ~]# chmod a+x /var/opt/lib/pe-puppet/facts.d/myfacts.sh >> [root@foo ~]# puppet apply -e 'notice($mypkg_installed)' --environment >> development >> Notice: Scope(Class[main]): true >> Notice: Compiled catalog for foo.local in environment development in 0.01 >> seconds >> Notice: Finished catalog run in 0.14 seconds >> [root@foo ~]# >> >> But the agent will always reset the file mode back to 0644. >> >> If anyone has suggestions on either preventing Puppet agent from >> reverting the fact script's permissions to 0644, OR getting the parser to >> resolve the facts without making the script executable, would be much >> appreciated. 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 view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/6f35823d-d57f-46e0-86cf-cc2897b39400%40googlegroups.com > <https://groups.google.com/d/msgid/puppet-users/6f35823d-d57f-46e0-86cf-cc2897b39400%40googlegroups.com?utm_medium=email_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > Can you verify that the executable fact on the master is executable? Josh -- Josh Cooper Developer, Puppet Labs *PuppetConf 2015 <http://2015.puppetconf.com/>** is right around the corner! Join us October 5-9 in Portland, OR. **Register now <https://puppetconf2015.eventbrite.com/>**.* -- 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/CA%2Bu97unRxoLrF5xKB7xAX7ij6LEPoBzG9Tgf8ULdTRQkFhxOxw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Dependent Ruby Gems - One run or Two
On Thu, Oct 1, 2015 at 10:35 AM, Fraser Goffin <goff...@gmail.com> wrote: > Hey Josh, > > Thanks for the heads up. You are right, version 0.4.3 does propose a > solution to this but unfortunately in my testing it doesn't quite work. I > have raised a couple of additional issues so with any luck Atlassian will > sort it out sometime soon. So still using the 2 run work-around for now. > Also you mentioned you're deploying on Windows, and it's possible you're running into a second issue PUP-3502, specifically see this comment[1]. It's possible clearing the gem path[2] on windows is not working as expected, so puppet still sees the old gem path from prior to the rest_client gem being installed. > Regards > > Fraser. > > -- > 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/617bff3e-40d6-45d5-9ccf-d408354a6fb3%40googlegroups.com > . > For more options, visit https://groups.google.com/d/optout. > Josh [1] https://tickets.puppetlabs.com/browse/PUP-3502?focusedCommentId=133316=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-133316 [2] https://github.com/puppetlabs/puppet/blob/master/lib/puppet/util/feature.rb#L85 -- Josh Cooper Developer, Puppet Labs *PuppetConf 2015 <http://2015.puppetconf.com/>** is right around the corner! Join us October 5-9 in Portland, OR. **Register now <https://puppetconf2015.eventbrite.com/>**.* -- 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/CA%2Bu97umbh_pH93y3YoUm8e-CghqamVxcbM0Frf%2BoxA%2BFh6yGMQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Dependent Ruby Gems - One run or Two
Hi Fraser,
On Tue, Sep 29, 2015 at 12:04 PM, Fraser Goffin <goff...@gmail.com> wrote:
> Puppet v 4.2.x
> Platform: Windows
>
> I'm using the Atlassian sonatype_nexus Puppet module. It allows you to
> configure Nexus via its RESTful API using a number of abstractions from the
> module. However, ... there is a requirement for a few additional Ruby gems
> to be installed, the key one being a rest_client gem and a number of its
> dependents. At this time the module doesn't provide installation for these
> but its pretty easy to copy them over to the correct location in Puppet
> using a file resource. Something along these lines :-
>
> class sonatype_nexus::windows::install {
> ...
> file { 'copy_gems':
> path=> 'c:/apps/puppet/sys/ruby/lib/',
> source => "puppet:///modules/${source_module_name}",
> recurse => true,
> }
>
> where the calling module contains a files folder with an appropriate
> structure to that under puppet ... e.g :-
>
> .../modules/sonatype_nexus/files/ruby/gems/2.1.0/
>
> OK, so no problem there then ... well actually there is.This file copy is
> (was) happening in an 'install' class and later on in another 'config'
> classI was using the resources that need those gems, say .. something like
> this to define a new Nexus proxied repository :-
>
> class sonatype_nexus::windows::postconfig {
>
> nexus_repository { 'myrepo':
> label => 'MyRepo',
> provider_type => 'maven2',
> type=> 'proxy',
> policy => 'release',
> ...
>}
>
> Unfortunately, when the catalogue is compiled Puppet spots the fact that
> this resource type needs access to the rest_client gem and since it can't
> find it on the system (this being a fresh VM) it throws an exception even
> though it will be there by the time this be of Puppet code runs because of
> the earlier copy and the dependencies established between the install and
> 'postconfig' classes :-
>
> class sonatype_nexus(
> ...
> Class["::sonatype_nexus::${::osfamily}::install"] ->
> Class["::sonatype_nexus::${::osfamily}::preconfig"] ->
> Class["::sonatype_nexus::${::osfamily}::service"] ->
> Class["::sonatype_nexus::${::osfamily}::postconfig"]
>
> So, for now, I have had to separate out the copy of the gems and then the
> install and config of Nexus into two separate Puppet runs. It works fine,
> but is there a way of getting it to work with just a single run ?
>
> Kind Regards
>
> Fraser.
>
>
> --
> 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/f3006946-5ba9-431b-9ad9-9b9e6c96cae1%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/f3006946-5ba9-431b-9ad9-9b9e6c96cae1%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
This issue came up when discussing a puppet PR[1]. It turned out to be a
bug in the nexus_rest module:
https://forge.puppetlabs.com/atlassian/nexus_rest, which looks like they
fixed in 0.4.3[2].
The problem was that previously the providers were not confined and would
try to require the rest_client gem directly. Now, the providers are
confined based on a provider feature, which allows puppet to defer
evaluation of nexus related resources until after the gem is installed, so
that both can occur in the same run.
Josh
[1] https://github.com/puppetlabs/puppet/pull/4220
[2]
https://bitbucket.org/atlassian/puppet-module-nexus_rest/pull-requests/48/issue-4-confine-rest-client-as-a-feature/diff
--
Josh Cooper
Developer, Puppet Labs
*PuppetConf 2015 <http://2015.puppetconf.com/>** is right around the
corner! Join us October 5-9 in Portland, OR. **Register now
<https://puppetconf2015.eventbrite.com/>**.*
--
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/CA%2Bu97unQW15xiBiGegxYdHLfsT%3DhOBBjCHJwyO9YN5qfLbVHzg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Puppetmaster performance degradation after update to 3.8.2
Hi Adam, On Wed, Sep 16, 2015 at 3:47 AM, Adam Winberg <adam.winb...@gmail.com> wrote: > Upgraded from 3.7.3 to 3.8.2 and have after that had very slow compilation > and file serving from the puppet master. We're running our puppetmaster > with apache/passenger, ca. 900 hosts. Complete puppet runs earlier took > 10-15s and after update take 30-300s. Very unstable performance. > > Even running with just a few clients the runtimes are really slow. > Decreasing the 'PassengerMaxPoolSize' makes the runs faster, but then it > cant cope with an increased load. > > I have also tried with the jvm puppetserver with roughly the same > performance (or lack thereof). I noticed the same pattern, if i set > 'max-active-instances' in puppetserver.conf to 2, I get acceptable > performance with a handful of clients, but with increased load it doesnt > cope. If I raise the 'max-active-instances' the performance is even worse. > > This is running on an vmware server, 8 cpu and 12GB RAM. > > Cant find anything in the release notes that explain this performance > drops, does anyone recognize the problem? > > I have now downgraded to 3.7.3 and my puppet runs are as fast as ever > again. > > Any help appreciated. > > Regards > Adam > > > -- > 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/CAFCL3HvvEC4HA4xD655sAPMBMznVdsqcQCYp5FHn%3D_SQ8TG2qg%40mail.gmail.com > <https://groups.google.com/d/msgid/puppet-users/CAFCL3HvvEC4HA4xD655sAPMBMznVdsqcQCYp5FHn%3D_SQ8TG2qg%40mail.gmail.com?utm_medium=email_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > I would take a look at the `--profile` option as described in https://puppetlabs.com/blog/tune-puppet-performance-profiler, making sure to update config.ru as needed. Josh -- Josh Cooper Developer, Puppet Labs *PuppetConf 2015 <http://2015.puppetconf.com/>** is right around the corner! Join us October 5-9 in Portland, OR. **Register now <https://puppetconf2015.eventbrite.com/>**.* -- 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/CA%2Bu97umgvfrNbJFeSRk8Rvnxkys-MAaSHEQKCeKqETy1OrXG1w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Puppetserver 2 API requests returning 403 from curl, but agent/CLI works fine (puppet 4.2.1)
On Fri, Sep 11, 2015 at 7:31 AM, Chris Cowley <chriscowleyso...@gmail.com>
wrote:
> When I run
>
>
> /opt/puppetlabs/bin/puppet node find
>
> I get the expected wall of JSON and agents work fine too.
>
By default, this will generate a node object for the nodename you
specified, but add the local host's fact information, and return that as
JSON. It's probably not what you're wanting to do:
$ puppet node find foo
{
"name": "foo",
"parameters": {
..
"fqdn": "arcturus.delivery.puppetlabs.net",
..
}
To access the puppetmaster's REST API, you'll need to do:
puppet node find --terminus rest
>
> However, I would like to set up monitoring. When I run:
>
> curl --cert /etc/puppetlabs/puppet/ssl/certs/mymachine.pem \
> --key /etc/puppetlabs/puppet/ssl/private_keys/mymachine.pem \
> --cacert /etc/puppetlabs/puppet/ssl/ca/ca_crt.pem \
> -H 'Accept: pson' \
>
> https://:8140/puppet/v3/catalog/?environment=production
>
> the server returns Error 403: Forbidden
>
> Is there something in auth.conf to add to enable acces to API outside of
> CLI?
>
> --
> 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/ebdac597-b4c4-4677-ba7a-ab74da9092dd%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/ebdac597-b4c4-4677-ba7a-ab74da9092dd%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
By default, puppet only allows a node to get its own catalog (see
https://github.com/puppetlabs/puppet/blob/4.2.0/conf/auth.conf#L67-L70).
This means the common name component of the subject's distinguished name in
your client cert, e.g. mymachine, needs to match exactly the for
the catalog you're requesting.
You can also add an ACL to auth.conf to allow a monitoring/controller node
to retrieve all catalogs. Just make sure to only allow the one node to do
that.
path ~ ^/puppet/v3/catalog/
method find
allow
Josh
--
Josh Cooper
Developer, Puppet Labs
*PuppetConf 2015 <http://2015.puppetconf.com/> is coming to Portland,
Oregon! Join us October 5-9.*
*Register now to take advantage of the Final Countdown discount
<https://www.eventbrite.com/e/puppetconf-2015-october-5-9-register-now-its-the-final-countdown-tickets-13115894995?discount=FinalCountdown>
*
*—**save $149!*
--
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/CA%2Bu97unJc%3D2JOrOY23EL6HGb4r0NF_pZ9OQ5d5WDk%2BwAmvHOZA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Re: custom facts sensitive to spaces
On Tuesday, September 8, 2015 at 11:47:44 AM UTC-7, Vince Skahan wrote: > > I think I found a bug in facter in 3.8.2 but wanted to ask here before > opening a PL ticket. > > Basic description is that facter has different behaviors if you run it > without vs. with a fact specified. > > To recreate: > > # echo 'foo = bar' > /etc/facter/facts.d/foo.txt > # facter | grep foo > foo => bar > # facter foo > > # > > Net effect is that if you have spaces around the = sign in your custom > fact definitions, the server doesn't match at all. It seems to look up by > name, which returns nothing (or a blank line, or a space - it's hard to > tell which) > > Workaround is to have no spaces around the = sign, but I think this is a > bug needing fixing. The behavior should be the same when you run "facter | > grep foo" and "facter foo" shouldn't it ? > > I think you're running into https://tickets.puppetlabs.com/browse/FACT-1050 Josh -- 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/377b6326-f854-4a9d-9ea0-f48576098273%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Re: Possibly bug in Puppetlabs/Registry module
://groups.google.com/d/msgid/puppet-users/c0503ad5-5d72-48ed-868f-522491f93e78%40googlegroups.com https://groups.google.com/d/msgid/puppet-users/c0503ad5-5d72-48ed-868f-522491f93e78%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- Rob Reynolds Developer, Puppet Labs *PuppetConf 2015 http://2015.puppetconf.com/ is coming to Portland, Oregon! Join us October 5-9.* *Register now to take advantage of the Early Adopter discount https://www.eventbrite.com/e/puppetconf-2015-october-5-9-tickets-13115894995?discount=EarlyAdopter * *—**save $349!* -- 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/ba3115b4-43e5-49c8-9e2e-261d5f59f3f5%40googlegroups.com https://groups.google.com/d/msgid/puppet-users/ba3115b4-43e5-49c8-9e2e-261d5f59f3f5%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- Rob Reynolds Developer, Puppet Labs *PuppetConf 2015 http://2015.puppetconf.com/ is coming to Portland, Oregon! Join us October 5-9.* *Register now to take advantage of the Early Adopter discount https://www.eventbrite.com/e/puppetconf-2015-october-5-9-tickets-13115894995?discount=EarlyAdopter * *—**save $349!* -- Rob Reynolds Developer, Puppet Labs *PuppetConf 2015 http://2015.puppetconf.com/ is coming to Portland, Oregon! Join us October 5-9.* *Register now to take advantage of the Early Bird discount https://www.eventbrite.com/e/puppetconf-2015-october-5-9-tickets-13115894995?discount=EarlyBird * *—**save $249!* -- 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/CAMJiBK7OQyU77x_hugf6B%2BghkA5_YXQGZs8s3%2BUqK3DVsbPCHA%40mail.gmail.com https://groups.google.com/d/msgid/puppet-users/CAMJiBK7OQyU77x_hugf6B%2BghkA5_YXQGZs8s3%2BUqK3DVsbPCHA%40mail.gmail.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. Josh -- Josh Cooper Developer, Puppet Labs *PuppetConf 2015 http://2015.puppetconf.com/ is coming to Portland, Oregon! Join us October 5-9.* *Register now to take advantage of the Final Countdown discount https://www.eventbrite.com/e/puppetconf-2015-october-5-9-register-now-its-the-final-countdown-tickets-13115894995?discount=FinalCountdown * *—**save $149!* -- 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/CA%2Bu97un7P0nbmqmRcwMWFUtf84Ec5KVvxuXQCL0yQGqEBnPyvQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] keep changing owner
Hi Patrick, On Thu, Aug 13, 2015 at 6:10 AM, Patrick G. pgh2...@gmail.com wrote: Hi, When running puppet agent -t I get Notice: /File[/var/lib/puppet/lib]/owner: owner changed 'puppet' to 'root' Notice: /File[/var/lib/puppet/lib]/group: group changed 'puppet' to 'root' And then Notice: /Stage[main]/My_fw/File[/var/lib/puppet/lib]/owner: owner changed 'root' to 'puppet' Notice: /Stage[main]/My_fw/File[/var/lib/puppet/lib]/group: group changed 'root' to 'puppet' For a lot of files. Why? Puppet will manage file permissions for its internal settings that are file/directories, e.g. Puppet[:libdir] is /var/lib/puppet/lib. It appears you have a module that is trying to manage permissions on that directory as well, and they disagree about what the desired state should be. I would remove the /var/lib/puppet/lib resource from your My_fw module (and any other Puppet settings-related file/directory). Regards, Patrick. -- 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/1af6a1e5-4125-457c-a0ec-5b0a139042df%40googlegroups.com https://groups.google.com/d/msgid/puppet-users/1af6a1e5-4125-457c-a0ec-5b0a139042df%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. Josh -- Josh Cooper Developer, Puppet Labs -- 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/CA%2Bu97uk9uXLLnq%3D-X%3D6-rC-7oK2ERzF9Abvz0ySQZmUPboxuWg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Puppet configuration Based on environmnet
in 0.01 seconds Notice: Finished catalog run in 0.02 seconds Debug: Using cached connection for https://puppetmaster.lab.com:8140 Debug: Caching connection for https://puppetmaster.lab.com:8140 Debug: Closing connection for https://puppetmaster.lab.com:8140 Any pointers on why its is not picking up will be highly appreciated. Thanks, Dev -- 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/77ebd82f-1b6a-4648-8e56-90b2e3d414a8%40googlegroups.com https://groups.google.com/d/msgid/puppet-users/77ebd82f-1b6a-4648-8e56-90b2e3d414a8%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- Josh Cooper Developer, Puppet Labs *PuppetConf 2015 http://2015.puppetconf.com/ is coming to Portland, Oregon! Join us October 5-9.* *Register now to take advantage of the Early Bird discount https://www.eventbrite.com/e/puppetconf-2015-october-5-9-tickets-13115894995?discount=EarlyBird * *—**save $249!* -- 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/CA%2Bu97uk%2BKkrNMmqAEqmh8oThcW5iKWHDHNX2bwZdz82JzzgP4g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Memory leak in Passenger ?
On Fri, Jul 24, 2015 at 12:56 AM, Michael Wörz michael.wo...@gmail.com wrote: Hello, in the past months we are observing raising memory usage on our puppet server and we have to restart it once a week when it starts swapping. Mainly there are 5 Passenger processes that are running for days and using about 15-20% of memory each. System has 4 GB of memory and is serving about 1600 Clients. - rpm -qa | grep passenger ruby193-rubygem-passenger-native-libs-4.0.18-9.8.el6.x86_64 rubygem-passenger-native-libs-4.0.18-9.8.el6.x86_64 mod_passenger-4.0.18-9.8.el6.x86_64 rubygem-passenger-4.0.18-9.8.el6.x86_64 rubygem-passenger-native-4.0.18-9.8.el6.x86_64 ruby193-rubygem-passenger-native-4.0.18-9.8.el6.x86_64 ruby193-rubygem-passenger-4.0.18-9.8.el6.x86_64 - cat /etc/redhat-release CentOS release 6.6 (Final) - rpm -qa | grep puppet puppet-server-3.8.1-1.el6.noarch -- 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/4c9264d3-eead-45fd-801e-2fea531a83a2%40googlegroups.com https://groups.google.com/d/msgid/puppet-users/4c9264d3-eead-45fd-801e-2fea531a83a2%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. You might take a look through the passenger issue tracker and release notes to see if there are any known memory leaks, maybe https://github.com/phusion/passenger/issues/1278? Josh -- Josh Cooper Developer, Puppet Labs *PuppetConf 2015 http://2015.puppetconf.com/ is coming to Portland, Oregon! Join us October 5-9.* *Register now to take advantage of the Early Bird discount https://www.eventbrite.com/e/puppetconf-2015-october-5-9-tickets-13115894995?discount=EarlyBird * *—**save $249!* -- 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/CA%2Bu97unOQyVTkFz-YbLZPFbHFFgs3DmQzgvN1bW%3DMAoYhZvNfw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Puppet 4.2. and latest Puppet Agent 1.2.1-x64 on Windows 2008 r2 keeps crashing with error 400: Invalid byte sequence in UTF-8
:in `find' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/indirection.rb:194:in `find' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/api/indirected_routes.rb:134:in `do_find' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/api/indirected_routes.rb:48:in `call' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/context.rb:64:in `override' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet.rb:223:in `override' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/api/indirected_routes.rb:47:in `call' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/route.rb:82:in `process' org/jruby/RubyArray.java:1613:in `each' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/route.rb:81:in `process' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/route.rb:87:in `process' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/route.rb:87:in `process' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/handler.rb:60:in `process' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/profiler/around_profiler.rb:58:in `profile' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/profiler.rb:51:in `profile' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/handler.rb:58:in `process' file:/opt/puppetlabs/server/apps/puppetserver/puppet-server-release.jar!/puppet-server-lib/puppet/server/master.rb:39:in `handleRequest' Puppet$$Server$$Master_1527977328.gen:13:in `handleRequest' request_handler_core.clj:274:in `invoke' request_handler_service.clj:14:in `handle_request' request_handler.clj:3:in `invoke' request_handler.clj:3:in `invoke' core.clj:626:in `invoke' core.clj:2468:in `doInvoke' master_core.clj:47:in `invoke' ring.clj:22:in `invoke' ring.clj:13:in `invoke' comidi.clj:267:in `invoke' ringutils.clj:106:in `invoke' ringutils.clj:62:in `invoke' ringutils.clj:68:in `invoke' ringutils.clj:118:in `invoke' jetty9_core.clj:408:in `invoke' -- 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/C224994E-EC8F-443C-AC28-C72CC2E214E9%40gt-it.de . For more options, visit https://groups.google.com/d/optout. -- Rob Reynolds Developer, Puppet Labs PuppetConf 2015 is coming to Portland, Oregon! Join us October 5-9. Register now to take advantage of the Early Bird discount —save $249! -- 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/CAMJiBK5gGFbku%3DBZ92kVpBXmvZKdHQhkR__ukm1wv%2BKYtawtkw%40mail.gmail.com . For more options, visit 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/0B8B8EC1-A707-4810-9301-F6D9B09FB98A%40gt-it.de . For more options, visit https://groups.google.com/d/optout. [1] https://projects.puppetlabs.com/issues/12702#note-4 -- Josh Cooper Developer, Puppet Labs *PuppetConf 2015 http://2015.puppetconf.com/ is coming to Portland, Oregon! Join us October 5-9.* *Register now to take advantage of the Early Bird discount https://www.eventbrite.com/e/puppetconf-2015-october-5-9-tickets-13115894995?discount=EarlyBird * *—**save $249!* -- 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/CA%2Bu97um4c4wgKOJgYi1S908U8E0ndcLSM%2B639-vYf9JP-LibVg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Re: API call to certificate_request deletes the request
On Sunday, June 28, 2015 at 10:49:21 AM UTC-7, Mikhail Simin wrote:
I'm using Puppet 3.7.3 and I observe this strange behavior when using the
API to sign a certificate:
== /var/log/apache.log ==
Jun 28 17:18:07.00 prod-puppetca apache: 127.0.0.1 prod-puppetca:8140
- - [28/Jun/2015:17:18:03 +] PUT
/production/certificate_request/prod-clientbox HTTP/1.1 200 1582 -
python-requests/2.7.0 CPython/2.7.6 Linux/3.13.0-46-generic
== /var/log/daemon.log ==
Jun 28 17:18:03.00 prod-puppetca puppet-master[27451]: prod-clientbox
has a waiting certificate request
Jun 28 17:18:07.00 prod-puppetca puppet-master[27451]: Signed
certificate request for prod-clientbox
Jun 28 17:18:07.00 prod-puppetca puppet-master[27451]: Removing file
Puppet::SSL::CertificateRequest prod-clientbox at
'/var/lib/puppet/ssl/ca/requests/prod-clientbox.pem'
For some reason a single PUT call to `certificate_request/` signs the CSR
and then also removes it!
Under normal circumstances (when the CSR does not get removed) I have a
follow up API call for `certificate_status/` with
{desired_state:signed} passed in. However when the CSR is removed, this
no longer works because puppet refuses with the following message:
Cannot sign for host prod-clientbox without a certificate request
Why does the CSR get removed with the same API call that uploads it?
It sounds like you have autosign[1] enabled. Check /etc/puppet/puppet.conf
or in the script that starts your CA.
Josh
[1] https://docs.puppetlabs.com/references/latest/configuration.html#autosign
--
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/5acc5158-2740-4167-9404-4651ed728bc7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Re: facter 3.0 not using /etc/facter/facts.d by default
On Thursday, June 25, 2015 at 7:35:36 AM UTC-7, math...@therussells.me wrote: I think this is a documentation issue only. Looking at this ticket https://tickets.puppetlabs.com/browse/FACT-826 I see mention of a different fact directory. Once i copied my facts to that new directory it picks them up. On Thursday, June 25, 2015 at 10:01:44 AM UTC-4, math...@therussells.me wrote: I just upgraded to puppet4.2 aio on some machines to fix a bug we have been having with puppet. But this introduced a new problem. It seems like out custom facts are not being loaded by puppet or facter. We have 3 external facts manually set in files. [root@x facts.d]# ll /etc/facter/facts.d/ total 12 -rw--- 1 root root 16 Jun 11 09:34 datacenter.txt -rw--- 1 root root 13 Jun 11 09:34 stack.txt -rw--- 1 root root 12 Jun 11 09:34 track.txt but facter does not see them by default [root@x facts.d]# /opt/puppetlabs/bin/facter | grep stack If i use the externa-dir option it works. [root@java-d11ah facts.d]# /opt/puppetlabs/bin/facter --external-dir /etc/facter/facts.d/ | grep stack stack = javaact I dont see anything in the release notes that would of changed this. This is an unintended change. It is being tracked as https://tickets.puppetlabs.com/browse/FACT-1055, and a puppet-agent update should be released soon. -- 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/170a76cd-1018-40aa-bedf-376215ed3bdb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Re: Can we install.. Oracle, weblogic, Notepad++ and tomcat using Puppet
Hi Santosh, yes you can. We do at our company. I recommend https://forge.puppetlabs.com/biemond/orawls for Weblogic. For oracle 11g client we wrote a module which currently cannot be open sourced as it's got some company specific data in it. we also wrote a module for notepad++ but again, it has some company specific data in it. if by oracle you mean java, then I recommend this module: https://forge.puppetlabs.com/biemond/jdk7 For tomcat we use PuppetLabs own tomcat module which you can also find on the puppet forge. HTH, Josh On Wednesday, 24 June 2015 13:49:30 UTC+1, Santosh Gaddam wrote: Can we install.. Oracle, weblogic, Notepad++ and tomcat using Puppet.. if yes what is the process for this... i have one doubt apart from default classes can we install more products using this...? -- 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/13728570-eef5-49d2-adb0-61ac91b70bdd%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] run puppet client behind a Internetproxy with authentification
On Fri, Jun 5, 2015 at 2:05 PM, Rico Steinitz rico.stein...@gmail.com
wrote:
I have some PCs in other Networks. The Puppet Client reach the
Puppet-Master only over a internetproxy (proxy server squid) with
authentification.
The masterport is 443 (HTTPS)
(Puppet client v3.7.5 (OS: Windows 7/2008/2012); Puppet Master 3.7.5
(Debian), Foreman 1.7.5)
i have no problems to communicate over a Proxy without Authentification.
I set the two variables in the puppet.conf on the client:
http_proxy_host=PROXY-IP-ADRESSE
http_proxy_port=8080
But i don't find something about the authentification variables.
I have a workaround. I edit the file:
C:\Program Files\Puppet
Labs\Puppet\puppet\lib\puppet\network\http\factory.rb
I added the authentification variables in the function: def
create_connection(site)
Original without authentification: (line: 29)
args Puppet[:http_proxy_host] Puppet[:http_proxy_port]
NEW with authentification: (line: 29)
args Puppet[:http_proxy_host] Puppet[:http_proxy_port]
Puppet[:http_proxy_user] Puppet[:http_proxy_password]
Is there any other way than to edit the file factory.rb?
--
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/a633c633-33ba-4b14-99a4-0f0273a3b9dd%40googlegroups.com
https://groups.google.com/d/msgid/puppet-users/a633c633-33ba-4b14-99a4-0f0273a3b9dd%40googlegroups.com?utm_medium=emailutm_source=footer
.
For more options, visit https://groups.google.com/d/optout.
This is filed as https://tickets.puppetlabs.com/browse/PUP-4470. It should
be pretty easy to modify the factory to do something along the lines of:
def create_connection(site)
Puppet.debug(Creating new connection for #{site})
http = Puppet::Util::Proxy.proxy(site)
http.use_ssl = site.use_ssl?
http.read_timeout = Puppet[:http_read_timeout]
http.open_timeout = Puppet[:http_connect_timeout]
Josh
--
Josh Cooper
Developer, Puppet Labs
*PuppetConf 2015 http://2015.puppetconf.com/ is coming to Portland,
Oregon! Join us October 5-9.*
*Register now to take advantage of the Early Adopter discount
https://www.eventbrite.com/e/puppetconf-2015-october-5-9-tickets-13115894995?discount=EarlyAdopter
*
*—**save $349!*
--
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/CA%2Bu97u%3DZ95OKDMauO1kkpZvgDd1Ofb4T75b1C8yUx12jUEVi6w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Augeas resource type for Windows?
On Wed, Jun 3, 2015 at 8:38 AM, Charlie Baum charlieb...@gmail.com wrote: I want to use Augeas to manage/change some XML files using my puppet manifest. I'd really prefer not to use templates, and Augeas seems like it does what I want. However when I try it, my Windows event log says there is no suitable provider for Augeas. Is that provider not supported on Windows? Is any Augeas provider available for Windows boxes? I see some in puppetforge but none claim to support Windows. -- 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/e66b2285-700b-40af-9396-ca47b15964e3%40googlegroups.com https://groups.google.com/d/msgid/puppet-users/e66b2285-700b-40af-9396-ca47b15964e3%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. From puppet's perspective, the augeas provider is only suitable if puppet can load the ruby-augeas bindings, which in turn load the augeas native libraries. In the default Puppet MSI install, neither the ruby-augeas bindings nor augeas native libraries are provided, so the provider is not suitable out of the box. However, you may be able to compile augeas for windows and install the ruby-augeas gem... I haven't done that myself, so I'm not sure how well that'll work out. Josh -- Josh Cooper Developer, Puppet Labs *PuppetConf 2015 http://2015.puppetconf.com/ is coming to Portland, Oregon! Join us October 5-9.* *Register now to take advantage of the Early Adopter discount https://www.eventbrite.com/e/puppetconf-2015-october-5-9-tickets-13115894995?discount=EarlyAdopter * *—**save $349!* -- 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/CA%2Bu97umitTf7iEgv5J-fgMTONX9eu86dEun5T1%2B1p3FMgBSN4Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] odd new error with puppet version 3.8.1
On Wed, May 27, 2015 at 1:02 PM, Peter Berghold salty.cowd...@gmail.com wrote: Ever since I upgraded to Puppet version 3.8.1 I now see this error: Error: /File[/var/lib/puppet/facts.d]: Could not evaluate: Could not retrieve information from environment production source(s) puppet:// mcadprod1.mca.sharkrivertech.com/pluginfacts What's that about? Should I worry. Something need configuring? When the agent runs, it will attempt to download external facts from all of the modules on the master to the /var/lib/puppet/facts.d directory on the agent. If no module has a facts.d directory on the master, e.g. in 3.8.x that'd be /etc/puppet/modules/some_module/facts.d, then the agent will display the above message. I think there is a ticket to not display an error message, as it's not really an error. And I think you can work around the issue by creating an empty facts.d directory for one of your modules. Josh -- Josh Cooper Developer, Puppet Labs *PuppetConf 2015 http://2015.puppetconf.com/ is coming to Portland, Oregon! Join us October 5-9.* *Register now to take advantage of the Early Adopter discount https://www.eventbrite.com/e/puppetconf-2015-october-5-9-tickets-13115894995?discount=EarlyAdopter * *—**save $349!* -- 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/CA%2Bu97unVEaSPr4SisA_pC5AtG3usauNVMGJLoqBQ6ABE_ThDeQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Re: puppet agent 4.0 running as root vs puppet server 2.0 running as puppet
On Thu, May 7, 2015 at 6:19 AM, jcbollinger john.bollin...@stjude.org
wrote:
On Thursday, May 7, 2015 at 12:32:59 AM UTC-5, Josh Cooper wrote:
On Wed, May 6, 2015 at 7:29 AM, Johnson Earls darkfo...@gmail.com
wrote:
never mind. puppet agent ignores the user/group config settings, so
those should be kept at puppet, and ${::settings::user} /
${::settings::group} should not be used to configure agent-related options
(such as file ownership).
The `puppet` user and group are really server-side settings, to specify a
less privileged account to run the webrick/passenger/puppetserver process
as.
Right.
To confuse things, `puppet` packages (rpm/deb) have always created the
`puppet` user and group, but was unnecessary on the agent. In Puppet 4, we
have fixed this, so the puppet-agent package does not create a `puppet`
user or group. Only the puppetserver package does that.
So the new package naming confuses even PL itself?
I mean, in our recent discussion of the new package naming and versioning
https://groups.google.com/forum/#!topic/puppet-users/K7-tUQoJ9FA, Eric
and Michael asserted that the puppet-agent package is the basic Puppet
infrastructure package, with which one can run the agent, the traditional
rack-based master, and everything else from Puppet's Ruby stack. They
claim the puppetserver package is *optional*. I completely believe
that's the *intention*, but in that case the puppet-agent package
should be the one responsible for the puppet user and group.
We will be releasing updated passenger packages compatible with
puppet-agent soon[1]. These packages also create the `puppet` user and
group, like puppetserver.
That leaves webrick. I agree, there is currently an inconsistency --
webrick functionality is provided by the puppet-agent package, but the
package does not create the `puppet` user and group. However, you are free
to create the accounts (using `puppet apply` even!), or specify an
alternate account using Puppet's `user` and `group` settings.
That said, webrick is deprecated and will be removed in Puppet 5[2].
Josh
[1] https://tickets.puppetlabs.com/browse/PUP-4452
[2] https://groups.google.com/d/topic/puppet-dev/RHa2tMPRTx4/discussion
--
Josh Cooper
Developer, Puppet Labs
*PuppetConf 2015 http://2015.puppetconf.com/ is coming to Portland,
Oregon! Join us October 5-9.*
*Register now to take advantage of the Early Adopter discount
https://www.eventbrite.com/e/puppetconf-2015-october-5-9-tickets-13115894995?discount=EarlyAdopter
*
*—**save $349!*
--
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/CA%2Bu97um6D8pRJOX_y8Kn0sEqGfPJ47J4H5WHjEM_6bac4%2BaMCg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] puppet agent 4.0 running as root vs puppet server 2.0 running as puppet
On Thu, May 7, 2015 at 11:23 AM, jcf joshua.fiel...@gmail.com wrote:
On May 6, 2015, at 22:32, Josh Cooper j...@puppetlabs.com wrote:
On Wed, May 6, 2015 at 7:29 AM, Johnson Earls darkfoxpr...@gmail.com
wrote:
never mind. puppet agent ignores the user/group config settings, so
those should be kept at puppet, and ${::settings::user} /
${::settings::group} should not be used to configure agent-related options
(such as file ownership).
The `puppet` user and group are really server-side settings, to specify a
less privileged account to run the webrick/passenger/puppetserver process
as.
So, maybe there should be a test to see if the user even exists before
mass-chown’ing directories?
The file and directories I'm talking about are internal to puppet, e.g.
ssldir. When managing them, puppet already takes into account whether the
`puppet` user exists or not.
To confuse things, `puppet` packages (rpm/deb) have always created the
`puppet` user and group, but was unnecessary on the agent. In Puppet 4, we
have fixed this, so the puppet-agent package does not create a `puppet`
user or group. Only the puppetserver package does that.
So there is at least a dependency/ordering problem, at most an unchecked
firehose turned on to change permissions, and this should be considered a
bug. Also, this is playing pretty fast and loose with idempotence if this
can’t be configured around.
The behavior of how puppet manages its internal files has not changed for a
long, long time. The only part that is different is which package creates
the `puppet` user and group.
What's the specific issue you're concerned about?
On Tuesday, May 5, 2015 at 10:40:00 PM UTC-7, Johnson Earls wrote:
I'm running into a frustrating issue, and I'm wondering if I'm just not
doing something right.
My understanding is that the puppet agent has to run with the config
user and group set to root so that it can make changes to the system.
The puppet server, on the other hand, runs as user and group puppet.
However, every time the puppet agent activates, it changes the ownership
of *most* of the subdirectories and files within the
/etc/puppetlabs/puppet/ssl directory to root, which then prevents the
puppet server from either starting up or being able to sign certificates.
In Puppet 4, you can get into this state if you install puppet-agent, and
run it at least once. Since the `puppet` user won't exist, the agent will
set permissions to `root:root:750` for file/directory-related settings like
`privatekeydir`.
Ouch. This violates the “principle of least surprise” at least two
different ways.
If the `puppet` user doesn't exist, we use secure defaults.
If you then install puppetserver, it will create the `puppet` user, start
the server as that user, and fail to start, because the puppet user can't
read `privatekeydir`, etc. However, as soon as you run `puppet agent` (or
`apply`) on the master, it will restore the permissions to `puppet:puppet`
and the puppetserver will start successfully.
So, if I started the components in the wrong order once, it now takes an
extra run to sort everything out, and doesn’t log it well enough to be
deciphered? Double-ouch.
In practice this happens rarely. Usually you install puppetserver, which
brings in puppet-agent as a dependency.
But if you do run into this issue, I recommend filing a ticket and even
submitting a PR to update the puppetserver install logic.
Am I misunderstanding how these two processes work and interact?
Should the puppet agent run with the config user/group set to puppet,
even though puppet won't have permission to make most of the changes on the
system?
Or should the puppet server run as root?
--
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/3955db48-4062-460c-a8a4-0df405277afb%40googlegroups.com
https://groups.google.com/d/msgid/puppet-users/3955db48-4062-460c-a8a4-0df405277afb%40googlegroups.com?utm_medium=emailutm_source=footer
.
For more options, visit https://groups.google.com/d/optout.
--
Josh Cooper
Developer, Puppet Labs
*PuppetConf 2015 http://2015.puppetconf.com/ is coming to Portland,
Oregon! Join us October 5-9.*
*Register now to take advantage of the Early Adopter discount
https://www.eventbrite.com/e/puppetconf-2015-october-5-9-tickets-13115894995?discount=EarlyAdopter
*
*—**save $349!*
--
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/CA%2Bu97unqBLmMMfqE
Re: [Puppet Users] puppet agent 4.0 running as root vs puppet server 2.0 running as puppet
On Thursday, May 7, 2015, Johnson Earls darkfoxpr...@gmail.com wrote: All of my systems get the puppet-agent package installed and enabled as part of kickstart. The puppetserver package only later gets installed for servers that will be puppet servers. Is this ordering really that unexpected? That sounds like a great reason to open a ticket. On Thursday, May 7, 2015 at 12:06:53 PM UTC-7, Josh Cooper wrote: In practice this happens rarely. Usually you install puppetserver, which brings in puppet-agent as a dependency. -- Josh Cooper Developer, Puppet Labs *PuppetConf 2015 http://2015.puppetconf.com/ is coming to Portland, Oregon! Join us October 5-9.* *Register now to take advantage of the Early Adopter discount https://www.eventbrite.com/e/puppetconf-2015-october-5-9-tickets-13115894995?discount=EarlyAdopter * *—**save $349!* - Johnson -- 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 javascript:_e(%7B%7D,'cvml','puppet-users%2bunsubscr...@googlegroups.com'); . To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/c7c9d0c4-6ac2-4b65-8ca8-3bad470c69e2%40googlegroups.com https://groups.google.com/d/msgid/puppet-users/c7c9d0c4-6ac2-4b65-8ca8-3bad470c69e2%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- Josh Cooper Developer, Puppet Labs *PuppetConf 2015 http://2015.puppetconf.com/ is coming to Portland, Oregon! Join us October 5-9.* *Register now to take advantage of the Early Adopter discount https://www.eventbrite.com/e/puppetconf-2015-october-5-9-tickets-13115894995?discount=EarlyAdopter * *—**save $349!* -- 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/CA%2Bu97um344LsbiCvRt36tVLFPaFMb%2BBs0JVZxxPy2qoBFEcyUQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Re: puppet agent 4.0 running as root vs puppet server 2.0 running as puppet
On Wed, May 6, 2015 at 7:29 AM, Johnson Earls darkfoxpr...@gmail.com
wrote:
never mind. puppet agent ignores the user/group config settings, so those
should be kept at puppet, and ${::settings::user} / ${::settings::group}
should not be used to configure agent-related options (such as file
ownership).
The `puppet` user and group are really server-side settings, to specify a
less privileged account to run the webrick/passenger/puppetserver process
as.
To confuse things, `puppet` packages (rpm/deb) have always created the
`puppet` user and group, but was unnecessary on the agent. In Puppet 4, we
have fixed this, so the puppet-agent package does not create a `puppet`
user or group. Only the puppetserver package does that.
On Tuesday, May 5, 2015 at 10:40:00 PM UTC-7, Johnson Earls wrote:
I'm running into a frustrating issue, and I'm wondering if I'm just not
doing something right.
My understanding is that the puppet agent has to run with the config
user and group set to root so that it can make changes to the system.
The puppet server, on the other hand, runs as user and group puppet.
However, every time the puppet agent activates, it changes the ownership
of *most* of the subdirectories and files within the
/etc/puppetlabs/puppet/ssl directory to root, which then prevents the
puppet server from either starting up or being able to sign certificates.
In Puppet 4, you can get into this state if you install puppet-agent, and
run it at least once. Since the `puppet` user won't exist, the agent will
set permissions to `root:root:750` for file/directory-related settings like
`privatekeydir`.
If you then install puppetserver, it will create the `puppet` user, start
the server as that user, and fail to start, because the puppet user can't
read `privatekeydir`, etc. However, as soon as you run `puppet agent` (or
`apply`) on the master, it will restore the permissions to `puppet:puppet`
and the puppetserver will start successfully.
Am I misunderstanding how these two processes work and interact?
Should the puppet agent run with the config user/group set to puppet,
even though puppet won't have permission to make most of the changes on the
system?
Or should the puppet server run as root?
--
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/3955db48-4062-460c-a8a4-0df405277afb%40googlegroups.com
https://groups.google.com/d/msgid/puppet-users/3955db48-4062-460c-a8a4-0df405277afb%40googlegroups.com?utm_medium=emailutm_source=footer
.
For more options, visit https://groups.google.com/d/optout.
--
Josh Cooper
Developer, Puppet Labs
*PuppetConf 2015 http://2015.puppetconf.com/ is coming to Portland,
Oregon! Join us October 5-9.*
*Register now to take advantage of the Early Adopter discount
https://www.eventbrite.com/e/puppetconf-2015-october-5-9-tickets-13115894995?discount=EarlyAdopter
*
*—**save $349!*
--
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/CA%2Bu97unqBLmMMfqE%2BJQ_R8MguFntxD%3DHxynM0uuY-O9py-s%2B4Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Issue with puppet 3.7.5 and augeas
On Fri, Apr 3, 2015 at 9:10 AM, Peter Berghold salty.cowd...@gmail.com wrote: Just this morning the Puppet agent got updated to 3.7.5. Now when classes that use Augeas are applied to hosts I see this: Error: Could not find a suitable provider for augeas Is there a workaround/fix for this? I'm on the Debian wheezy platform. I'd check that puppet can load the ruby augeas bindings. Likely this will return false for you. # irb irb(main):001:0 require 'puppet' = true irb(main):002:0 Puppet.features.augeas? = true -- 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/CAArvnv1At3cLMmLhV%3DSnpBW7aOyaxAjuwik-kJK2TE1-W%2BTYJw%40mail.gmail.com https://groups.google.com/d/msgid/puppet-users/CAArvnv1At3cLMmLhV%3DSnpBW7aOyaxAjuwik-kJK2TE1-W%2BTYJw%40mail.gmail.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. Josh -- Josh Cooper Developer, Puppet Labs *PuppetConf 2015 http://2015.puppetconf.com/ is coming to Portland, Oregon! Join us October 5-9.* *Register now to take advantage of the Early Adopter discount https://www.eventbrite.com/e/puppetconf-2015-october-5-9-tickets-13115894995?discount=EarlyAdopter * *—**save $349!* -- 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/CA%2Bu97u%3D%2B5q4MXduCC7hcQZbBuN2%2BvF1uxUVucmAu37PN7THM6Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Could not retrieve file metadata ... end of file reached
On Tue, Mar 17, 2015 at 4:52 AM, James Green james.mk.gr...@gmail.com wrote: I am not convinced that this is to do with an agent being busy then attempting the next connection. Info: Retrieving pluginfacts Info: Retrieving plugin Info: Loading facts Error: Could not retrieve catalog from remote server: end of file reached Warning: Not using cache on failed catalog Error: Could not retrieve catalog; skipping run The above all happened within a few seconds. I might argue within 4-5 seconds. Unless of course I'd misunderstood your hypothesis? Puppet's persistent http connection feature will attempt to reuse the connection for the duration of the run. There are several opportunities for the connection to remain idle while the puppet agent is busy doing other work, e.g. downloading a package from a repo, executing a long running process, evaluating facts (like your example above), etc. If the connection is idle longer than the master (or load-balancer's) keep alive or idle timeouts, then the server side will close the connection. For example, apache 2.4 defaults HTTP KeepAliveTimeout is 5 seconds[1], and I've seen customer environments where haproxy idle timeouts were set to 60 seconds. One way to check if the server side is closing the connection, is to disable keep alive on the agent as I mentioned earlier. If the problem seems to go away, then I'd try re-enabling keep alive on the agent, and running tcpdump during an agent run. You'll likely see the master/load-balancer sending a TCP RST some exact number of seconds after the agent last wrote to the socket. To resolve the issue, make sure your server side keep alive timeouts are greater than the agent's, either by increasing the server's timeout, or decreasing the agent's. [1] http://httpd.apache.org/docs/2.4/mod/core.html#keepalivetimeout On 13 March 2015 at 05:28, Josh Cooper j...@puppetlabs.com wrote: On Thu, Mar 12, 2015 at 4:21 AM, James Green james.mk.gr...@gmail.com wrote: I was running puppet agent -t --noop repeatedly with this error. Running again, this time omitting --noop, it succeeded. Not entirely clear what this tells me... On 12 March 2015 at 10:58, James Green james.mk.gr...@gmail.com wrote: Error: /Stage[main]/Our_unattended_upgrades/File[/etc/apt/apt.conf.d/20auto-upgrades]: Could not evaluate: Could not retrieve file metadata for puppet:///modules/our_unattended_upgrades/etc/apt/apt.conf.d/20auto-upgrades: end of file reached Wrapped exception: end of file reached Versions on the server: ii facter 2.4.1-1puppetlabs1 all Ruby module for collecting simple facts about a host operating system ii hiera1.3.4-1puppetlabs1 all A simple pluggable Hierarchical Database. ii puppet 3.7.4-1puppetlabs1 all Centralized configuration management - agent startup and compatibility scripts ii puppet-common3.7.4-1puppetlabs1 all Centralized configuration management ii puppetdb 2.2.2-1puppetlabs1 all PuppetDB Centralized Storage. ii puppetdb-terminus2.2.2-1puppetlabs1 all Connect Puppet to PuppetDB by setting up a terminus for PuppetDB. ii puppetlabs-release 1.0-11 all Package to install Puppet Labs gpg key and apt repo ii puppetmaster-common 3.7.4-1puppetlabs1 all Puppet master common scripts ii puppetmaster-passenger 3.7.4-1puppetlabs1 all Centralised configuration management - master setup to run under mod passenger Are we looking at a known bug or are we really going to need to debug this? James On 11 March 2015 at 09:47, James Green james.mk.gr...@gmail.com wrote: Hi, Sorry for the delayed response. In our case we are using Passenger. On 5 March 2015 at 15:24, Henrik Lindberg henrik.lindb...@cloudsmith.com wrote: On 2015-05-03 12:02, James Green wrote: We occasionally have an agent fail because of this. I'm told by others running the agents more frequently that it appears to be at random and not on anything particularly large. If you are using webrick then it is most likely a concurrency problem (more than one agent calling in at the same time). Webrick is not recommended for production use because of this. - 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/md9sfc%24r1e%241%40ger.gmane.org. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Puppet
Re: [Puppet Users] Could not retrieve file metadata ... end of file reached
triggers a metadata request, and the agent receives the EOF exception. Josh -- Josh Cooper Developer, Puppet Labs *PuppetConf 2015 http://2015.puppetconf.com/ is coming to Portland, Oregon! Join us October 5-9.* *Register now to take advantage of the Early Adopter discount https://www.eventbrite.com/e/puppetconf-2015-october-5-9-tickets-13115894995?discount=EarlyAdopter * *—**save $349!* -- 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/CA%2Bu97ukpopZZOcHp1bB5V_Ae34o_%3Dn5vcTakBx3rFccWO5trbg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] External Facts in MODULEPATH/MODULE/facts.d/
On Thu, Mar 5, 2015 at 3:07 PM, Felix Frank felix.fr...@alumni.tu-berlin.de wrote: On 03/05/2015 11:55 PM, Dan White wrote: --external-dir=*/var/lib/puppet/facts.d/* Ah. Good catch! It is not a bug. It is an Undocumented Feature :D Hah! Well I'm not convinced. UX bugs are still issues. Cheers, Felix -- 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/54F8E1C2.7060601%40Alumni.TU-Berlin.de https://groups.google.com/d/msgid/puppet-users/54F8E1C2.7060601%40Alumni.TU-Berlin.de?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. This issue is covered in https://tickets.puppetlabs.com/browse/FACT-696. Note that facter --puppet is deprecated, because it introduces a cyclical dependency between puppet and facter, and the same functionality can be accomplished using `puppet facts find hostname`, or more succinctly `puppet facts find .` In 4.0, it's just `puppet facts find` thanks to Erik's contribution in https://tickets.puppetlabs.com/browse/PUP-3698 Josh -- Josh Cooper Developer, Puppet Labs *PuppetConf 2015 http://2015.puppetconf.com/ is coming to Portland, Oregon! Join us October 5-9.* *Register now to take advantage of the Early Adopter discount https://www.eventbrite.com/e/puppetconf-2015-october-5-9-tickets-13115894995?discount=EarlyAdopter * *—**save $349!* -- 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/CA%2Bu97umCAAmoY5LipE7Zoc%3D%3DO5bjE2Q4X5P0_k035boM9DnKqg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Bug #15326] (Accepted) Scheduled_task does not accept domain user accounts
On Tuesday, February 24, 2015, Helen Paterson helen.pater...@gmail.com
wrote:
Hi,
When i add the user attribute to Scheduled_task, the scheduled task is not
created, but if i comment out the user attribute the scheduled task is
created running as system.
This doesn't seem to work
scheduled_task { 'CopyCF11ReposFromDR':
ensure = present,
enabled= true,
command = 'D:\bin\Schedules\CopyCF11ReposFromDR.bat',
working_dir = 'D:\bin\Schedules',
user = 'MYDOMAIN\puppet-user',
arguments= ' D:\bin\Schedules\CopyCF11ReposFromDR_LOG.txt',
require = File['D:\bin\Schedules\CopyCF11ReposFromDR.bat']
}
You'll need to specify the puppet-user's password if you don't use
the LocalSystem account.
I am using puppet master version 3.7.4 and windows agent version 3.7.4 on
Windows server 2012 R2.
I see this bug has been reported as fixed
https://projects.puppetlabs.com/issues/15326
--
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
javascript:_e(%7B%7D,'cvml','puppet-users%2bunsubscr...@googlegroups.com');
.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/17b6bf14-5a4a-4122-96fa-40703ab7c916%40googlegroups.com
https://groups.google.com/d/msgid/puppet-users/17b6bf14-5a4a-4122-96fa-40703ab7c916%40googlegroups.com?utm_medium=emailutm_source=footer
.
For more options, visit https://groups.google.com/d/optout.
--
Josh Cooper
Developer, Puppet Labs
*Join us at **PuppetConf 2015, October 5-9 in Portland, OR - *
http://2015.puppetconf.com.
*Register early to save 40%!*
--
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/CA%2Bu97um8k%3DjFEfZZ9GD2krteqrsMy%3DcBOV6EuVG3nrbxQWbMtw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
