[Puppet Users] Announce: PuppetDB 2.3.5 is now available!

2015-06-04 Thread Wyatt Alt 
PuppetDB 2.3.5 - June 4, 2015

PuppetDB 2.3.5 Downloads



Available in native package format in the release repositories at:

http://yum.puppetlabs.com and http://apt.puppetlabs.com

For information on how to enable the Puppet Labs repos, see:

http://docs.puppetlabs.com/guides/puppetlabs_package_repositories.html#open-source-repositories

Binary tarball: http://downloads.puppetlabs.com/puppetdb/

Source: http://github.com/puppetlabs/puppetdb

Please report feedback via the Puppet Labs tickets site, using an affected
PuppetDB version of 2.3.5: https://tickets.puppetlabs.com/browse/PDB

Documentation: http://docs.puppetlabs.com/puppetdb/2.3/

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

PuppetDB 2.3.5 Release Notes



PuppetDB 2.3.5 is a backwards-compatible bugfix release that removes a
dependency on rubygem-json that prevented installation alongside the
all-in-one agent on RHEL 5 and 6, fixes a bug that caused us to reject
resource relationship titles containing newlines, and lessens database
contention during command processing. Users that upgrade will see fewer
commands retried due to rollbacks of concurrent transactions in PostgresSQL
(signified in PostgreSQL logs by “ERROR:  could not serialize access due to
concurrent update”)

For more information and upgrade advice, consult the detailed release notes
here:

https://docs.puppetlabs.com/puppetdb/2.3/release_notes.html

Contributors



John Duarte, Ken Barber, Melissa Stone, Rob Browning, Russell Mull, Wyatt
Alt

Changelog

-

John Duarte (2):

 ef409a4 (PDB-1300) Get tests working with Puppet 4 AIO packaging

 1c5859a (PDB-1300) Set conditional beaker options for AIO

Ken Barber (3):

 766608a (PDB-1469) Remove rubygem-json dependency

 93df2aa (PDB-1300) Use manage_firewall => false instead of flushing
iptables later manually

 721a040 (PDB-1300) Wrap aio options parts in conditional

Melissa Stone (1):

 cf2e086 (maint) Do not build stable or testing

Rob Browning (2):

 621d0c0 (PDB-1263) Use beaker EC2 subnet rotation

 d853fd9 (PDB-1454) Handle IOException while starting MQ

Russell Mull (1):

 af26e29 (PDB-1529) Allow newlines in resource names

Wyatt Alt (3):

 3be0e9c Update nodes.markdown

 706df77 (maint) don't activate the node when it's already active
 ddf2e91 (PDB-1571) update release notes for 2.3.5 release

-- 
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/CAJDiH3HVsL_8Be7Gy1LwMAveLZjv_1Kk9Cp4qb%2BzDEoH%2BLCXoQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Announce: Copenhagen Puppet User Group

2015-06-04 Thread Jens Hojgaard 
Hi Puppet Users,

I'm happy to announce the first meetup in Copenhagen Puppet User Group.

It will be held on KU CSS Campus @18:00 - 17. june 2015.

Please come and help us build an active Puppet community in Copenhagen,
and don't forget to signup at our meetup.com page: 
http://www.meetup.com/Copenhagen-Puppet-User-Group


On behalf of the organizers
Jens Højgaard

-- 
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/5cc3558f-0a59-4048-9d73-9c6ba3f5a670%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] MCollective - Restricted Access

2015-06-04 Thread Christopher Wood 
On Thu, Jun 04, 2015 at 01:47:16PM -0400, Tom Tucker wrote:
>Is it possible to limit which node can execute mco related commands? 
>Ideally I would only want an admin node(s) to have this level of access.
>Thanks in advance,

Node, probably not. Every node has to have a socket to the stomp middleware.

However, you can definitely limit commands on a per-person basis. Look into a 
combination of Action Policy Authorization Plugin and some kind of rsa or ssh 
key based auth. I've successfully implemented the ssh key based auth.

https://github.com/puppetlabs/mcollective-actionpolicy-auth
https://github.com/puppetlabs/mcollective-sshkey-security

There's also mcollective-us...@googlegroups.com for more specific mco questions.

># rpm -qa | egrep 'mcol|pupp'
>puppetserver-1.0.8-1.el6.noarch
>mcollective-service-common-3.1.3-1.el6.noarch
>mcollective-2.8.2-1.el6.noarch
>mcollective-puppet-common-1.10.0-1.el6.noarch
>mcollective-nettest-agent-3.0.4-1.el6.noarch
>mcollective-package-agent-4.4.0-1.el6.noarch
>mcollective-client-2.8.2-1.el6.noarch
>mcollective-service-agent-3.1.3-1.el6.noarch
>mcollective-puppet-client-1.10.0-1.el6.noarch
>mcollective-nettest-common-3.0.4-1.el6.noarch
>mcollective-nettest-client-3.0.4-1.el6.noarch
>mcollective-package-common-4.4.0-1.el6.noarch
>mcollective-package-client-4.4.0-1.el6.noarch
>puppetlabs-release-6-11.noarch
>puppet-3.8.1-1.el6.noarch
>mcollective-common-2.8.2-1.el6.noarch
>mcollective-service-client-3.1.3-1.el6.noarch
>mcollective-puppet-agent-1.10.0-1.el6.noarch
>mcollective-facter-facts-1.0.0-1.noarch
>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 [1]puppet-users+unsubscr...@googlegroups.com.
>To view this discussion on the web visit
>
> [2]https://groups.google.com/d/msgid/puppet-users/CAGymF1Ac%3DEKOanL4kjGjJtJksjPRLJfomYtAa6Edv%2BLpVcx-NA%40mail.gmail.com.
>For more options, visit [3]https://groups.google.com/d/optout.
> 
> References
> 
>Visible links
>1. mailto:puppet-users+unsubscr...@googlegroups.com
>2. 
> https://groups.google.com/d/msgid/puppet-users/CAGymF1Ac%3DEKOanL4kjGjJtJksjPRLJfomYtAa6Edv%2BLpVcx-NA%40mail.gmail.com?utm_medium=email&utm_source=footer
>3. https://groups.google.com/d/optout

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/20150604182933.GA481%40iniquitous.heresiarch.ca.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] MCollective - Restricted Access

2015-06-04 Thread Tom Tucker 
Is it possible to limit which node can execute mco related commands?
Ideally I would only want an admin node(s) to have this level of access.

Thanks in advance,

# rpm -qa | egrep 'mcol|pupp'
puppetserver-1.0.8-1.el6.noarch
mcollective-service-common-3.1.3-1.el6.noarch
mcollective-2.8.2-1.el6.noarch
mcollective-puppet-common-1.10.0-1.el6.noarch
mcollective-nettest-agent-3.0.4-1.el6.noarch
mcollective-package-agent-4.4.0-1.el6.noarch
mcollective-client-2.8.2-1.el6.noarch
mcollective-service-agent-3.1.3-1.el6.noarch
mcollective-puppet-client-1.10.0-1.el6.noarch
mcollective-nettest-common-3.0.4-1.el6.noarch
mcollective-nettest-client-3.0.4-1.el6.noarch
mcollective-package-common-4.4.0-1.el6.noarch
mcollective-package-client-4.4.0-1.el6.noarch
puppetlabs-release-6-11.noarch
puppet-3.8.1-1.el6.noarch
mcollective-common-2.8.2-1.el6.noarch
mcollective-service-client-3.1.3-1.el6.noarch
mcollective-puppet-agent-1.10.0-1.el6.noarch
mcollective-facter-facts-1.0.0-1.noarch
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/CAGymF1Ac%3DEKOanL4kjGjJtJksjPRLJfomYtAa6Edv%2BLpVcx-NA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Puppet Learning VM - Resource Ordering Quest - Task 6/6

2015-06-04 Thread Dan White 

OK.
Here are the significant bits:

Debug: importing 
'/etc/puppetlabs/puppet/environments/production/modules/sshd/manifests/init.pp' 
in environment production
Debug: Automatically imported sshd from sshd into production

Debug: /Stage[main]/Sshd/Package[openssh-server]/before: requires 
File[/etc/ssh/sshd_config]
Debug: /Stage[main]/Sshd/Service[sshd]/subscribe: subscribes to 
File[/etc/ssh/sshd_config]

Debug: Executing '/sbin/service sshd status'
Debug: Executing '/sbin/chkconfig sshd'
Debug: Finishing transaction 90055050
Debug: Storing state

I see nothing wrong.
Based on that output, I would say that :
Service sshd is already running
Package openssh-server is already installed
File /etc/ssh/sshd_config is identical to puppet:///modules/sshd/sshd_config
Change any or all of those states and run Puppet again.
“Sometimes I think the surest sign that intelligent life exists elsewhere in the 
universe is that none of it has tried to contact us.”  (Bill Waterson: Calvin & 
Hobbes)

On Jun 04, 2015, at 01:00 PM, Luke Anderson  wrote:

Hi,

Output of "puppet apply 'sshd/tests/init.pp' --debug" is below:

 [0;36mDebug: Runtime environment: puppet_version=3.7.3 (Puppet Enterprise 3.7.1), ruby_version=1.9.3, run_mode=user, default_encoding=UTF-8 [0m [0;36mDebug: Loading external facts from /var/opt/lib/pe-puppet/facts.d [0m [0;32mInfo: Loading facts [0m [0;36mDebug: Loading facts from /etc/puppetlabs/puppet/environments/production/modules/concat/lib/facter/concat_basedir.rb [0m [0;32mInfo: Loading facts [0m [0;36mDebug: Loading facts from /etc/puppetlabs/puppet/environments/production/modules/staging/lib/facter/staging_windir.rb [0m [0;36mDebug: Loading facts from /etc/puppetlabs/puppet/environments/production/modules/staging/lib/facter/staging_http_get.rb [0m [0;32mInfo: Loading facts [0m [0;36mDebug: Loading facts from /etc/puppetlabs/puppet/environments/production/modules/stdlib/lib/facter/pe_version.rb [0m [0;36mDebug: Loading facts from /etc/puppetlabs/puppet/environments/production/modules/stdlib/lib/facter/puppet_vardir.rb [0m [0;36mDebug: Loading facts from /etc/puppetlabs/puppet/environments/production/modules/stdlib/lib/facter/root_home.rb [0m [0;36mDebug: Loading facts from /etc/puppetlabs/puppet/environments/production/modules/stdlib/lib/facter/facter_dot_d.rb [0m [0;32mInfo: Loading facts [0m [0;36mDebug: Loading facts from /etc/puppetlabs/puppet/environments/production/modules/mysql/lib/facter/mysql_version.rb [0m [0;36mDebug: Loading facts from /etc/puppetlabs/puppet/environments/production/modules/mysql/lib/facter/mysql_server_id.rb [0m [0;32mInfo: Loading facts [0m [0;36mDebug: Loading facts from /opt/puppet/share/puppet/modules/pe_staging/lib/facter/staging_http_get.rb [0m [0;32mInfo: Loading facts [0m [0;36mDebug: Loading facts from /opt/puppet/share/puppet/modules/puppet_enterprise/lib/facter/custom_auth_conf.rb [0m [0;36mDebug: Loading facts from /opt/puppet/share/puppet/modules/puppet_enterprise/lib/facter/pe_build.rb [0m [0;36mDebug: Loading facts from /opt/puppet/share/puppet/modules/puppet_enterprise/lib/facter/platform_tag.rb [0m [0;36mDebug: Loading facts from /opt/puppet/share/puppet/modules/puppet_enterprise/lib/facter/pe_version.rb [0m [0;36mDebug: Loading facts from /opt/puppet/share/puppet/modules/puppet_enterprise/lib/facter/windows.rb [0m [0;32mInfo: Loading facts [0m [0;36mDebug: Loading facts from /opt/puppet/share/puppet/modules/pe_concat/lib/facter/pe_concat_basedir.rb [0m [0;32mInfo: Loading facts [0m [0;36mDebug: Loading facts from /var/opt/lib/pe-puppet/lib/facter/custom_auth_conf.rb [0m [0;36mDebug: Loading facts from /var/opt/lib/pe-puppet/lib/facter/pe_build.rb [0m [0;36mDebug: Loading facts from /var/opt/lib/pe-puppet/lib/facter/platform_tag.rb [0m [0;36mDebug: Loading facts from /var/opt/lib/pe-puppet/lib/facter/pe_version.rb [0m [0;36mDebug: Loading facts from /var/opt/lib/pe-puppet/lib/facter/puppet_vardir.rb [0m [0;36mDebug: Loading facts from /var/opt/lib/pe-puppet/lib/facter/root_home.rb [0m [0;36mDebug: Loading facts from /var/opt/lib/pe-puppet/lib/facter/staging_windir.rb [0m [0;36mDebug: Loading facts from /var/opt/lib/pe-puppet/lib/facter/mysql_version.rb [0m [0;36mDebug: Loading facts from /var/opt/lib/pe-puppet/lib/facter/concat_basedir.rb [0m [0;36mDebug: Loading facts from /var/opt/lib/pe-puppet/lib/facter/windows.rb [0m [0;36mDebug: Loading facts from /var/opt/lib/pe-puppet/lib/facter/mysql_server_id.rb [0m [0;36mDebug: Loading facts from /var/opt/lib/pe-puppet/lib/facter/facter_dot_d.rb [0m [0;36mDebug: Loading facts from /var/opt/lib/pe-puppet/lib/facter/staging_http_get.rb [0m [0;36mDebug: Loading facts from /var/opt/lib/pe-puppet/lib/facter/pe_concat_basedir.rb [0m [0;36mDebug: importing '/etc/puppetlabs/puppet/environments/production/modules/sshd/manifests/init.pp' in environment production [0m [0;36mDebug: Automatically imported sshd from sshd into production [0m [0;36mDebug: Executing '/bin/rpm --version' [0m [0;36mDebug: Executing '/bin/rpm -

Re: [Puppet Users] Creating Windows MSI for puppet agent

2015-06-04 Thread Melissa Stone 
On Thu, Jun 4, 2015 at 1:05 AM, Puppeteer  wrote:

> Hi,
>
> I want to create a custom MSI for the puppet agent. Can someone guide me
> on this.
> I tried using puppetlabs/puppet_for_the_win but was not successful.
>

Hey!

Unfortunately, we have yet to streamline this process for external use. You
can still roll your own native facter build though. You'll want to use the
script at
https://github.com/puppetlabs/facter/blob/master/contrib/facter.ps1. You
need to run the script on probably a windows 2012 box (64 bit), and I would
strongly suggest reviewing the script to ensure that we don't do anything
that's going to mess you up. It's meant to be run on a disposable box.

After that builds, we collect all the built bits and library dependencies
into the zip archive that the automation in puppet_for_the_win looks for.
We don't have that automation in a public space, but here's a summary of
what goes into that archive. This assumes you're building 64 bit, so if
you're building for a 32 bit machine, you'll have to modify it.

# Move all necessary dll's into facter bindir
"cp /cygdrive/c/tools/mingw64/bin/libgcc_s_seh-1.dll
/cygdrive/c/tools/mingw64/bin/libstdc++-6.dll
/cygdrive/c/tools/mingw64/bin/libwinpthread-1.dll
/home/Administrator/facter/release/bin/"

# Format everything to prepare to archive it
"mkdir -p /home/Administrator/archive/lib ; cp -r
/home/Administrator/facter/release/bin /home/Administrator/facter/lib/inc
/home/Administrator/archive/ ; cp
/home/Administrator/facter/release/lib/facter.rb
/home/Administrator/archive/lib/"

# Zip up the built archives
"7za.exe a -r -tzip facter.zip
'C:\\cygwin64\\home\\Administrator\\archive\\*'\"

Once you have that archive, you can modify the config file you're using to
point to where that archive can be found. That *should* let the automation
in puppet_for_the_win work.

Let me know how that goes!


>
> I used the command:
> rake windows:build AGENT_VERSION_STRING=1.0.0 CONFIG=foss-4.1-x86.yaml
>
> I get the following error:
>
> curl -O
> http://builds.puppetlabs.lan/facter/9586d5cd1ee6c18e88506a8f4a8b12f2ee51
> d154/artifacts/windows//facter-2.4.3-1074-g9586d5c-x86.zip
>
> curl: (6) Couldn't resolve host 'builds.puppetlabs.lan'
> rake aborted!
> Command failed with status (6): [curl -O
> http://builds.puppetlabs.lan/facte...]
>
> Tasks: TOP => windows:msi => windows:wixobj => windows:wxs =>
> windows:stage => w
> indows:checkout => windows:clone
> (See full trace by running task with --trace)
>
> 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/d759891a-e50b-4553-a36f-3416f39a88c7%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Melissa Stone
Release Engineer, Puppet Labs
--

*PuppetConf 2015  is coming to Portland,
Oregon! Join us October 5-9.*
*Register now to take advantage of the Early Adopter discount

*
*—**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/CAHEe_ko3nJcrCApycWK5a0Jh%3Dv8GUeETkDi8VZqXiMzRV3PDgw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Puppet Learning VM - Resource Ordering Quest - Task 6/6

2015-06-04 Thread Luke Anderson 
Hi,

Output of "puppet apply 'sshd/tests/init.pp' --debug" is below:

 [0;36mDebug: Runtime environment: puppet_version=3.7.3 (Puppet Enterprise 
3.7.1), ruby_version=1.9.3, run_mode=user, default_encoding=UTF-8 [0m
 [0;36mDebug: Loading external facts from /var/opt/lib/pe-puppet/facts.d [0m
 [0;32mInfo: Loading facts [0m
 [0;36mDebug: Loading facts from 
/etc/puppetlabs/puppet/environments/production/modules/concat/lib/facter/concat_basedir.rb
 [0m
 [0;32mInfo: Loading facts [0m
 [0;36mDebug: Loading facts from 
/etc/puppetlabs/puppet/environments/production/modules/staging/lib/facter/staging_windir.rb
 [0m
 [0;36mDebug: Loading facts from 
/etc/puppetlabs/puppet/environments/production/modules/staging/lib/facter/staging_http_get.rb
 [0m
 [0;32mInfo: Loading facts [0m
 [0;36mDebug: Loading facts from 
/etc/puppetlabs/puppet/environments/production/modules/stdlib/lib/facter/pe_version.rb
 [0m
 [0;36mDebug: Loading facts from 
/etc/puppetlabs/puppet/environments/production/modules/stdlib/lib/facter/puppet_vardir.rb
 [0m
 [0;36mDebug: Loading facts from 
/etc/puppetlabs/puppet/environments/production/modules/stdlib/lib/facter/root_home.rb
 [0m
 [0;36mDebug: Loading facts from 
/etc/puppetlabs/puppet/environments/production/modules/stdlib/lib/facter/facter_dot_d.rb
 [0m
 [0;32mInfo: Loading facts [0m
 [0;36mDebug: Loading facts from 
/etc/puppetlabs/puppet/environments/production/modules/mysql/lib/facter/mysql_version.rb
 [0m
 [0;36mDebug: Loading facts from 
/etc/puppetlabs/puppet/environments/production/modules/mysql/lib/facter/mysql_server_id.rb
 [0m
 [0;32mInfo: Loading facts [0m
 [0;36mDebug: Loading facts from 
/opt/puppet/share/puppet/modules/pe_staging/lib/facter/staging_http_get.rb [0m
 [0;32mInfo: Loading facts [0m
 [0;36mDebug: Loading facts from 
/opt/puppet/share/puppet/modules/puppet_enterprise/lib/facter/custom_auth_conf.rb
 [0m
 [0;36mDebug: Loading facts from 
/opt/puppet/share/puppet/modules/puppet_enterprise/lib/facter/pe_build.rb [0m
 [0;36mDebug: Loading facts from 
/opt/puppet/share/puppet/modules/puppet_enterprise/lib/facter/platform_tag.rb 
[0m
 [0;36mDebug: Loading facts from 
/opt/puppet/share/puppet/modules/puppet_enterprise/lib/facter/pe_version.rb [0m
 [0;36mDebug: Loading facts from 
/opt/puppet/share/puppet/modules/puppet_enterprise/lib/facter/windows.rb [0m
 [0;32mInfo: Loading facts [0m
 [0;36mDebug: Loading facts from 
/opt/puppet/share/puppet/modules/pe_concat/lib/facter/pe_concat_basedir.rb [0m
 [0;32mInfo: Loading facts [0m
 [0;36mDebug: Loading facts from 
/var/opt/lib/pe-puppet/lib/facter/custom_auth_conf.rb [0m
 [0;36mDebug: Loading facts from /var/opt/lib/pe-puppet/lib/facter/pe_build.rb 
[0m
 [0;36mDebug: Loading facts from 
/var/opt/lib/pe-puppet/lib/facter/platform_tag.rb [0m
 [0;36mDebug: Loading facts from 
/var/opt/lib/pe-puppet/lib/facter/pe_version.rb [0m
 [0;36mDebug: Loading facts from 
/var/opt/lib/pe-puppet/lib/facter/puppet_vardir.rb [0m
 [0;36mDebug: Loading facts from /var/opt/lib/pe-puppet/lib/facter/root_home.rb 
[0m
 [0;36mDebug: Loading facts from 
/var/opt/lib/pe-puppet/lib/facter/staging_windir.rb [0m
 [0;36mDebug: Loading facts from 
/var/opt/lib/pe-puppet/lib/facter/mysql_version.rb [0m
 [0;36mDebug: Loading facts from 
/var/opt/lib/pe-puppet/lib/facter/concat_basedir.rb [0m
 [0;36mDebug: Loading facts from /var/opt/lib/pe-puppet/lib/facter/windows.rb 
[0m
 [0;36mDebug: Loading facts from 
/var/opt/lib/pe-puppet/lib/facter/mysql_server_id.rb [0m
 [0;36mDebug: Loading facts from 
/var/opt/lib/pe-puppet/lib/facter/facter_dot_d.rb [0m
 [0;36mDebug: Loading facts from 
/var/opt/lib/pe-puppet/lib/facter/staging_http_get.rb [0m
 [0;36mDebug: Loading facts from 
/var/opt/lib/pe-puppet/lib/facter/pe_concat_basedir.rb [0m
 [0;36mDebug: importing 
'/etc/puppetlabs/puppet/environments/production/modules/sshd/manifests/init.pp' 
in environment production [0m
 [0;36mDebug: Automatically imported sshd from sshd into production [0m
 [0;36mDebug: Executing '/bin/rpm --version' [0m
 [0;36mDebug: Executing '/bin/rpm -ql rpm' [0m
 [0;36mDebug: Executing '/bin/rpm --version' [0m
 [mNotice: Compiled catalog for learning.puppetlabs.vm in environment 
production in 0.96 seconds [0m
 [0;36mDebug: Puppet::Type::Package::ProviderSun: file /usr/bin/pkginfo does 
not exist [0m
 [0;36mDebug: Puppet::Type::Package::ProviderPortage: file /usr/bin/emerge does 
not exist [0m
 [0;36mDebug: Puppet::Type::Package::ProviderPkgin: file pkgin does not exist 
[0m
 [0;36mDebug: Puppet::Type::Package::ProviderUp2date: file 
/usr/sbin/up2date-nox does not exist [0m
 [0;36mDebug: Puppet::Type::Package::ProviderDpkg: file /usr/bin/dpkg does not 
exist [0m
 [0;36mDebug: Puppet::Type::Package::ProviderFink: file /sw/bin/fink does not 
exist [0m
 [0;36mDebug: Puppet::Type::Package::ProviderPkg: file /usr/bin/pkg does not 
exist [0m
 [0;36mDebug: Puppet::Type::Package::ProviderUrpmi: file urpmi does not exist 
[0m
 [0;36mDebug: Puppet::Type::Package::ProviderAix: file /usr/bin/lslpp does not 
e

[Puppet Users] Could not evaluate: Could not find command '/var/lib/puppet/concat/bin/concatfragments.rb'

2015-06-04 Thread Joe Koenig 
I've got a puppet agent (3.8) on CentOS 7 that I'm trying to configure 
using the puppetlabs-apache module. I'm getting the following on the first 
run:

*Error: 
/Stage[main]/Main/Node[web-agent-..xxx.com]/Apache::Vhost[example.com]/Concat[25-example.com.conf]/Exec[concat_25-example.com.conf]:
 
Could not evaluate: Could not find command 
'/var/lib/puppet/concat/bin/concatfragments.rb'*

Here's what my site.pp looks like:

node /^web-agent-(.*)\.bds-puppet\.com$/ {

class { 'yum':

extrarepo => ['epel', 'puppetlabs', 'remi_php55', 'remi']

}

file { ["/data", "/data/web", "/data/web/vhosts", 
"/data/web/vhosts/example.com"]: ensure => "directory" }

file { ["/data/logs", "/data/logs/apache"]: ensure => "directory" }

class { 'apache':

package_ensure => '2.4.6-31.el7.centos',

server_signature => 'Off',

default_vhost => false,

default_mods => false,

mpm_module => false

}

class { 'apache::mod::prefork':

startservers => '8',

minspareservers => '3',

maxspareservers => '5',

serverlimit => '1024',

maxclients => '1024',

maxrequestsperchild => '4000'

}

apache::vhost { 'www.example.com':

port => '80',

serveraliases => ['example.com','*.example.com'],

docroot => '/data/web/vhosts/example.com',

access_log_file => 'example.com_access_log',

error_log_file => 'example.com_error_log',

logroot => '/data/logs/apache',

override => 'All',

directoryindex => 'index.php index.html',

add_default_charset => 'UTF-8',

options => ['-Indexes']

}

class { 'apache::mod::cache': }

class { 'apache::mod::deflate': }

class { 'apache::mod::dir': }

class { 'apache::mod::mime': }

class { 'apache::mod::mime_magic': }

class { 'apache::mod::proxy': }

class { 'apache::mod::rewrite': }

class { 'apache::mod::ssl': }

class { 'apache::mod::status': }

class { 'apache::mod::vhost_alias': }

class { '::apache::mod::php':

package_name => "php-5.5.25-1.el7.remi",

} 

package { 
["php-mcrypt","php-mysqlnd","php-gd","php-ldap","php-soap","php-mbstring","php-opcache","libcurl-devel"]:

ensure => "installed",

require => Class['apache']

}

package { "openldap-devel": ensure => "installed" }

package { ["openssl","openssl-devel"]: ensure => "latest" }

package { "wkhtmltopdf": ensure => "0.12.1-1.el7" }

}

Any pointers on what may be causing this would be greatly appreciated. 
Thanks!

Joe

-- 
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/4717bf8b-1fcb-4e7a-bb3f-163abf149557%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Augeas resource type for Windows?

2015-06-04 Thread Josh Cooper 
On Wed, Jun 3, 2015 at 8:38 AM, Charlie Baum  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
> 
> .
> 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  is coming to Portland,
Oregon! Join us October 5-9.*
*Register now to take advantage of the Early Adopter discount

*
*—**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.

[Puppet Users] Creating Windows MSI for puppet agent

2015-06-04 Thread Puppeteer 
Hi,

I want to create a custom MSI for the puppet agent. Can someone guide me on 
this. 
I tried using puppetlabs/puppet_for_the_win but was not successful.

I used the command:
rake windows:build AGENT_VERSION_STRING=1.0.0 CONFIG=foss-4.1-x86.yaml

I get the following error: 

curl -O 
http://builds.puppetlabs.lan/facter/9586d5cd1ee6c18e88506a8f4a8b12f2ee51
d154/artifacts/windows//facter-2.4.3-1074-g9586d5c-x86.zip

curl: (6) Couldn't resolve host 'builds.puppetlabs.lan'
rake aborted!
Command failed with status (6): [curl -O 
http://builds.puppetlabs.lan/facte...]

Tasks: TOP => windows:msi => windows:wixobj => windows:wxs => windows:stage 
=> w
indows:checkout => windows:clone
(See full trace by running task with --trace)

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/d759891a-e50b-4553-a36f-3416f39a88c7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.