[Puppet Users] puppetlabs apache and extra conf.d files

[Arnau]

Hi all,

Puppetlab apache module [1] by default purges everything under
/etc/httpd/conf.d . If you want to add an extra file, you must use
apache::vhost.
I'm writing a module for managin thruk. The trhuk rpm packge provides a
apache conf file (/etc/httpd/conf.d/thruk.conf). At this point I'm
wondering what is the best way for "translating" the conf file provided by
the rpm into a apache:vhost.

Is there any automatic way for writing the apache::vhost from a http conf
file (something like puppet resource ... ? )

How do other people deal with this?

TIA,
Arnau



[1] https://forge.puppetlabs.com/puppetlabs/apache

-- 
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/CAM69jx8aMtQoA80VpmVgvGGX2iLytbfB80%2BzURWq%3DiOCLKt-%2BQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Failed to install PE installer

[Ricson Liberato]

During installation of "puppet-enterprise-installer" on master server,  I'm 
getting some type of error : '[rhel7.dcs01.local] Failed to run PE 
Installer on rhel7.dcs01.local'.

On Puppet Master Server:
iptables STOP
Selinux disabled
Edit /etc/host and IP and hostname 

Please help..

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/3f3f280a-3b64-4589-b78f-4ec0cc902abf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] puppet-common from Puppetlabs APT repository broken on Ubuntu wily

[Markus Birth]

I can't install Puppet from the official Puppetlabs repository 
(apt.puppetlabs.com) because puppet-common requires libaugeas-ruby. And 
libaugeas-ruby isn't available on Ubuntu wily anymore. The package is now 
called ruby-augeas.

Also see: 
https://answers.launchpad.net/ubuntu/+source/libaugeas-ruby/+question/273718

Can somebody fix the package's dependencies, please?

-- 
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/7093eb5d-af0e-45bf-827e-2ee613c3ddcc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Puppet agents get hanged in "Info: Loading facts"

[Eddie Mashayev]

Hi,

Yes I'm running Foreman (Puppet master), I have more than 200 servers which 
works great.
This is the only server which is problematic and seems to be due to Facter.

Thanks,
EddieM

On Thursday, November 5, 2015 at 5:40:21 PM UTC+2, Craig Dunn wrote:
>
> Your code snippet suggests that facter has run,  and the master is 
> timing out running /etc/puppet/node.rb which is the ENC script (which 
> happens after the facts have been sent by the agent).   Are you 
> running Foreman/Satellite? - It sounds like you may have a network 
> connectivity issue here between your Puppet master and ENC 
>
> Craig 
>
> On Thu, Nov 5, 2015 at 4:23 PM, Eddie Mashayev  > wrote: 
> > Hi All, 
> > 
> > I have CentOS 6.5 running puppet agent version 3.8.2 the problem is when 
> I’m 
> > running “puppet agent -t” it gets hanged: 
> > 
> > [root@server ~]# puppet agent -t 
> > Info: Retrieving pluginfacts 
> > Info: Retrieving plugin 
> > Info: Loading facts 
> > Info: Loading facts 
> > 
> > “Could not retrieve catalog from remote server: Error 400 on SERVER: 
> Failed 
> > when searching for node : Failed to find via exec: Execution of 
> > '/etc/puppet/node.rb” 
> > 
> > 
> > 
> > After I checked it I found out the reason, I have more than 1000 VLANs 
> on 
> > the servers and I guess when the Facter collecting the INFO it gets 
> timeout 
> > and fails. 
> > I found this thread to “Allow for disabling certain facts within Facter 
> ” 
> > https://tickets.puppetlabs.com/browse/FACT-718” but it still wasn’t 
> > implemented. 
> > My question is there is any way that puppet won’t get info for VLANS? 
> > Meaning "puppet agent –t" won’t triger the Facter get information about 
> > VLANS? 
> > If no how can I override this issue? 
> > 
> > Thakns, 
> > EddieM 
> > 
> > -- 
> > 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/857038e6-6e35-4bd0-a86e-710093744a71%40googlegroups.com.
>  
>
> > For more options, visit https://groups.google.com/d/optout. 
>
>
>
> -- 
> Enviatics | Automation and configuration management 
> http://www.enviatics.com | @Enviatics 
> http://dojo.training | @DojoTraining 
>

-- 
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/f9f5f40a-d211-45a1-bb6f-80e7713fab68%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Announce: Puppet 3.8.4 available

[Eric Sorenson]

Puppet 3.8.4 is available. This is a bugfix release which fixes a performance 
problem with directory environments, a security vulnerability when Puppet 
generated its CA key, and a small grab-bag of other bugs.

You can see the full release notes here:

https://docs.puppetlabs.com/puppet/3.8/reference/release_notes.html#puppet-384

Here's the complete list of bugs fixed in the release:

https://tickets.puppetlabs.com/issues/?filter=15901

To install or upgrade puppet, follow the installation guide:

https://docs.puppetlabs.com/guides/install_puppet/pre_install.html

Eric Sorenson - eric.soren...@puppetlabs.com - freenode #puppet: eric0
puppet platform // coffee // techno // bicycles

-- 
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/C61C6148-3DCB-43B7-A521-B2BE412EF757%40puppetlabs.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Announce: Puppet Enterprise 2015.2.3 is available

[Rob Braden]

Dear Puppet Enterprise Users,

Puppet Enterprise 2015.2.3 is now available.

Puppet Enterprise 2015.2.3 is a security and bug-fix release of Puppet
Enterprise. This release contains updated versions of PostgreSQL and Java
with fixes for security issues, as well as a security fix for Puppet Server.


In addition, this release adds support for Enterprise Linux 4, Solaris 11
and AIX (5.3, 6.2, 7.1) agents to the 2015.2 series.

For information on these and other fixes in this release, please see
https://docs.puppetlabs.com/pe/2015.2/release_notes.html.

As a current Puppet Enterprise user, you can upgrade to this new version as
part of your annual subscription. If upgrading, it is recommended to
upgrade your master and console servers first.

As always, we want to hear about your experiences with Puppet Enterprise.
If you have any questions about upgrading, be sure to get in touch with
Puppet Labs Support.

-- 
Rob Braden
Puppet Labs Release Team

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

[Puppet Users] Announce: Puppet Enterprise 3.8.3 is available

[Rob Braden]

Dear Puppet Enterprise Users,

Puppet Enterprise 3.8.3 is now available.

Puppet Enterprise 3.8.3 is a security and bug-fix release of Puppet
Enterprise. This release contains updated versions of PostgreSQL and Java
with fixes for security issues, as well as a security fix for Puppet Server.

For information on these and other fixes in this release, please see
https://docs.puppetlabs.com/pe/3.8/release_notes.html.

As a current Puppet Enterprise user, you can upgrade to this new version as
part of your annual subscription. If upgrading, it is recommended to
upgrade your master and console servers first.

As always, we want to hear about your experiences with Puppet Enterprise.
If you have any questions about upgrading, be sure to get in touch with
Puppet Labs Support.

-- 
Rob Braden
Puppet Labs Release Team

-- 
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/CANrW%3D%3D3yLUCxBpoA%3DprupgBLRXqJ3E-F42%2BZVQE6PvW%2B%2BbRWAQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] getting File '/repodata/repomd.xml' not found on medium " https:// .... " while installing the Puppet agent in SLES 11

[Shreyas Guru]

Hello Everybody,

I am still learning puppet and trying out the free PE version in SLES11 
server

I successfully installed PE master in one of the server .. next when I try 
to install Puppet agent in an other server with same platform and 
architecture by curling the cmd (piping using bash) i found in Dashboard, I 
get the following error :


Refreshing service 'spacewalk'.
File '/repodata/repomd.xml' not found on medium 
'https://cdlperfwtweb1.es.ad.adp.com:8140/packages/2015.2.2/sles-11-x86_64?ssl_verify=no'

Abort, retry, ignore? [a/r/i/? shows all options] (a): a
Abort, retry, ignore? [a/r/i/? shows all options] (a): a


I am not sure how to proceed with it.. really helpful if someone can assist 
me

-- 
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/3eb8a636-d056-4a44-a5c7-5d570d960306%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] puppetlabs apache and extra conf.d files

[Hunter Haugen]

The apache module contains many mod manifests [1] that use file
resources with templates [2] that you can pattern your code after. No
need to use apache::vhost at all.

[1] https://github.com/puppetlabs/puppetlabs-apache/tree/master/manifests/mod
[2] https://github.com/puppetlabs/puppetlabs-apache/tree/master/templates/mod

On 11/5/15, Arnau  wrote:
> Hi all,
>
> Puppetlab apache module [1] by default purges everything under
> /etc/httpd/conf.d . If you want to add an extra file, you must use
> apache::vhost.
> I'm writing a module for managin thruk. The trhuk rpm packge provides a
> apache conf file (/etc/httpd/conf.d/thruk.conf). At this point I'm
> wondering what is the best way for "translating" the conf file provided by
> the rpm into a apache:vhost.
>
> Is there any automatic way for writing the apache::vhost from a http conf
> file (something like puppet resource ... ? )
>
> How do other people deal with this?
>
> TIA,
> Arnau
>
>
>
> [1] https://forge.puppetlabs.com/puppetlabs/apache
>
> --
> 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/CAM69jx8aMtQoA80VpmVgvGGX2iLytbfB80%2BzURWq%3DiOCLKt-%2BQ%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.
>


-- 


-Hunter

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

Re: [Puppet Users] puppet-common from Puppetlabs APT repository broken on Ubuntu wily

[Michael Stahnke]

We also don't have wily packages up, so if the first bug was fixed, I don't
think it would work. It's a work in progress.

You can follow https://tickets.puppetlabs.com/browse/CPR-213 for more
information.

On Thu, Nov 5, 2015 at 7:05 AM, Markus Birth  wrote:

> I can't install Puppet from the official Puppetlabs repository (
> apt.puppetlabs.com) because puppet-common requires libaugeas-ruby. And
> libaugeas-ruby isn't available on Ubuntu wily anymore. The package is now
> called ruby-augeas.
>
> Also see:
> https://answers.launchpad.net/ubuntu/+source/libaugeas-ruby/+question/273718
>
> Can somebody fix the package's dependencies, please?
>
> --
> 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/7093eb5d-af0e-45bf-827e-2ee613c3ddcc%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/CAMto7LLcJD8L0JBvpPH7xOv8g9PwTgn1fG7m8kT1-LRvQPwoTA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Puppet Training for Linux System Engineers.

[Unus Humami]

Hello Every one,

If any one interested in learning puppet, please shoot me an email with 
update you about next batch and fees.

Thanks
Humami

-- 
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/1e69660b-5943-4628-b4b6-48befb0109e3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Puppet agents get hanged in "Info: Loading facts"

[Craig Dunn]

Your code snippet suggests that facter has run,  and the master is
timing out running /etc/puppet/node.rb which is the ENC script (which
happens after the facts have been sent by the agent).   Are you
running Foreman/Satellite? - It sounds like you may have a network
connectivity issue here between your Puppet master and ENC

Craig

On Thu, Nov 5, 2015 at 4:23 PM, Eddie Mashayev  wrote:
> Hi All,
>
> I have CentOS 6.5 running puppet agent version 3.8.2 the problem is when I’m
> running “puppet agent -t” it gets hanged:
>
> [root@server ~]# puppet agent -t
> Info: Retrieving pluginfacts
> Info: Retrieving plugin
> Info: Loading facts
> Info: Loading facts
>
> “Could not retrieve catalog from remote server: Error 400 on SERVER: Failed
> when searching for node : Failed to find via exec: Execution of
> '/etc/puppet/node.rb”
>
>
>
> After I checked it I found out the reason, I have more than 1000 VLANs on
> the servers and I guess when the Facter collecting the INFO it gets timeout
> and fails.
> I found this thread to “Allow for disabling certain facts within Facter ”
> https://tickets.puppetlabs.com/browse/FACT-718” but it still wasn’t
> implemented.
> My question is there is any way that puppet won’t get info for VLANS?
> Meaning "puppet agent –t" won’t triger the Facter get information about
> VLANS?
> If no how can I override this issue?
>
> Thakns,
> EddieM
>
> --
> 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/857038e6-6e35-4bd0-a86e-710093744a71%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.



-- 
Enviatics | Automation and configuration management
http://www.enviatics.com | @Enviatics
http://dojo.training | @DojoTraining

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

[Puppet Users] Puppet agents get hanged in "Info: Loading facts"

[Eddie Mashayev]

Hi All, 

I have CentOS 6.5 running puppet agent version 3.8.2 the problem is when 
I’m running “puppet agent -t” it gets hanged: 

[root@server ~]# puppet agent -t 
Info: Retrieving pluginfacts 
Info: Retrieving plugin 
Info: Loading facts 
Info: Loading facts 

“Could not retrieve catalog from remote server: Error 400 on SERVER: Failed 
when searching for node : Failed to find via exec: Execution of 
'/etc/puppet/node.rb” 




After I checked it I found out the reason, I have more than 1000 VLANs on 
the servers and I guess when the Facter collecting the INFO it gets timeout 
and fails. 
I found this thread to “Allow for disabling certain facts within Facter ” 
https://tickets.puppetlabs.com/browse/FACT-718” but it still wasn’t 
implemented. 
My question is there is any way that puppet won’t get info for VLANS? 
Meaning "puppet agent –t" won’t triger the Facter get information about 
VLANS? 
If no how can I override this issue?

Thakns,
EddieM

-- 
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/857038e6-6e35-4bd0-a86e-710093744a71%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.