[Puppet Users] puppetdb memory use

[jdt]

Hello,

I recently upgraded to PuppetDB2.2.0 from 1.6.3
When I was running PuppetDB1.6.3 with Puppet 3.4.3 I could do with 256Mb of 
heap space for PuppetDB after the upgrade I've increased first to 512Mb and 
768Mb but I kept getting Out of Memory, so now I've increased it to 1Gb.
When looking at the dashboard it seems like memory is slowly increasing,
I'm running Puppet v3.6.2 with PuppetDB2.2.0 on CentOS6.x with Ruby 1.8.7. 
I have about 850 active puppet agents

Has anyone seen the same behaviour? How can I find out what exactly is 
wrong if anything?

Best Regards,
Jo

-- 
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/67de9de4-d480-4b95-9d8f-e04510611c39%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Puppet agent in background causing dependency failure.

[Josh Cooper]

On Sun, Nov 16, 2014 at 6:27 AM, Felix Frank <
felix.fr...@alumni.tu-berlin.de> wrote:

> On 11/14/2014 10:38 AM, David Schmitt wrote:
> > Puppet evaluates which provider to use only once per agent run.
>
> Hmm, are you sure about that?
>
> As far as I know, providers *will* become suitable during the agent
> transaction. Support for this has been added, seeing as it is not an
> uncommon occurence that a module must install software on the agent
> system that will enable the provider to function in the first place.
>

Yes, this feature was implemented in
https://projects.puppetlabs.com/issues/6907 first released in 2.7.8.

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/5468B451.7040301%40Alumni.TU-Berlin.de
> .
> 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%2Bu97umga_nc6ghT7tsWJ9eQToOH%2BgnXGPx5dpBOTGTdr2WKkQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: Puppet applies new file, then reverts it back

[Alex Elman]

Josh is correct. The first resource has a character with a different case.
Notice the p in the filename. You are managing two different resources from
puppet's perspective.

C:/LiveServices/LiveObjectWebServer/Plugins/LiveBuilder/LiveBuilderplugin.lsp

Versus

C:/LiveServices/LiveObjectWebServer/Plugins/LiveBuilder/LiveBuilderPlugin.lsp
On Jan 6, 2015 12:33 AM, "Josh Cooper"  wrote:

>
>
> On Mon, Jan 5, 2015 at 7:49 AM, jcbollinger 
> wrote:
>
>>
>>
>> On Tuesday, December 30, 2014 7:38:05 AM UTC-6, Nicholas Miller wrote:
>>>
>>> Hi All,
>>>
>>> I'm having a strange issue with one particular file where puppet applies
>>> the new file, then reverts back.  It does this every time puppet runs, see
>>> below:
>>>
>>
>> [...]
>>
>> That is very strange.  Puppet should never manage the same resource twice
>> in the same catalog run, and in any given run, Puppet should never modify
>> the same property of the same resource more than once.  These are such
>> fundamental Puppet principles that I'm inclined to guess that rather than
>> Puppet doing either of the above, it is instead managing two distinct (from
>> its perspective) resources that somehow resolve to the same physical
>> resource.
>>
>>
>>> Has anyone ever had this problem before?  Any ideas on how to fix it?
>>>
>>>
>> I have not had that problem, but if I have guessed right about its nature
>> then you should look carefully at your manifests to find the resource
>> duplication (which will revolve around something about the file name and /
>> or path of two File resources that the catalog compiler doesn't recognize
>> as being equivalent).  You could also look at the cached catalog to verify
>> that there are indeed two file resources corresponding to the given file;
>> if so, then it is conceivable that comparing them will reveal the nature of
>> the collision.
>>
>> In any event, it may be that running the agent with --debug output
>> enabled will provide useful additional information.
>>
>
> I've seen this sort of problem on Windows when mixing upper and lower case
> file paths, so given
>
>   file { 'C:/foo':
> ensure => file,
> content => 'upper',
>   }
>
>   file { 'c:/foo':
> ensure => file,
> content => 'lower',
>   }
>
> Puppet will try to apply both resources, not realizing they are in fact
> the same resource on a Windows case-insensitive filesystem:
>
> C:\work\puppet> bundle exec puppet apply file.pp
> ...
> Notice: /Stage[main]/Main/File[C:/foo]/content: content changed
> '{md5}81e073b428b50247daba38531dcf412a' to
> '{md5}0122b4c2c01ee1c698ecc309d2b8eb5a'
> Notice: /Stage[main]/Main/File[c:/foo]/content: content changed
> '{md5}0122b4c2c01ee1c698ecc309d2b8eb5a' to
> '{md5}81e073b428b50247daba38531dcf412a'
>
> But the output from your agent run seems to use the same case...
>
> Josh
>
> --
> 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%2Bu97u%3DLhj0F-N6V-j3jpxwi%2BNzN85HQ3SOPBrTd6UVAzy9XXA%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/CAGWx_ybtRAWZKNaU9BZPVUGc%3Dx0EsdJ%2B3-o6K_eTZLKYJ4rVfQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: Puppet applies new file, then reverts it back

[Josh Cooper]

On Mon, Jan 5, 2015 at 7:49 AM, jcbollinger 
wrote:

>
>
> On Tuesday, December 30, 2014 7:38:05 AM UTC-6, Nicholas Miller wrote:
>>
>> Hi All,
>>
>> I'm having a strange issue with one particular file where puppet applies
>> the new file, then reverts back.  It does this every time puppet runs, see
>> below:
>>
>
> [...]
>
> That is very strange.  Puppet should never manage the same resource twice
> in the same catalog run, and in any given run, Puppet should never modify
> the same property of the same resource more than once.  These are such
> fundamental Puppet principles that I'm inclined to guess that rather than
> Puppet doing either of the above, it is instead managing two distinct (from
> its perspective) resources that somehow resolve to the same physical
> resource.
>
>
>> Has anyone ever had this problem before?  Any ideas on how to fix it?
>>
>>
> I have not had that problem, but if I have guessed right about its nature
> then you should look carefully at your manifests to find the resource
> duplication (which will revolve around something about the file name and /
> or path of two File resources that the catalog compiler doesn't recognize
> as being equivalent).  You could also look at the cached catalog to verify
> that there are indeed two file resources corresponding to the given file;
> if so, then it is conceivable that comparing them will reveal the nature of
> the collision.
>
> In any event, it may be that running the agent with --debug output enabled
> will provide useful additional information.
>

I've seen this sort of problem on Windows when mixing upper and lower case
file paths, so given

  file { 'C:/foo':
ensure => file,
content => 'upper',
  }

  file { 'c:/foo':
ensure => file,
content => 'lower',
  }

Puppet will try to apply both resources, not realizing they are in fact the
same resource on a Windows case-insensitive filesystem:

C:\work\puppet> bundle exec puppet apply file.pp
...
Notice: /Stage[main]/Main/File[C:/foo]/content: content changed
'{md5}81e073b428b50247daba38531dcf412a' to
'{md5}0122b4c2c01ee1c698ecc309d2b8eb5a'
Notice: /Stage[main]/Main/File[c:/foo]/content: content changed
'{md5}0122b4c2c01ee1c698ecc309d2b8eb5a' to
'{md5}81e073b428b50247daba38531dcf412a'

But the output from your agent run seems to use the same case...

Josh

-- 
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%2Bu97u%3DLhj0F-N6V-j3jpxwi%2BNzN85HQ3SOPBrTd6UVAzy9XXA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Puppet Exec Command on XML update

[Pushparaj BS]

Hi, 

I have an XML file that has configuration for IIS Virtual settings for many 
webservice Applications, and each application is a node in the XML. 

Based on the XML, I have a Powershell script that can read the respective node 
and configure the IIS. 

However, I need to have puppet monitor this node in the XML and trigger the 
script if changed as the XML can be updated for some IIS changes for a 
webservice. 

I can see that exec command gives functionality to watch file changes, but I 
need to watch a node specifically. 

-- 
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/f6572b8d-1086-4b54-9d42-837c1513feae%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Default "Catalog Store" for Puppet 3??

[Drew Decker]

Felix,

Thanks for the information.  This answered my question exactly. 
 storeconfigs is not set and when I run the puppet command that you 
referenced, it showed that storeconfigs was false, only confirming that I 
am not using them.  Good to know.  I wanted to make sure before I 
configured PuppetDB that I wouldn't be overwriting or destroying anything.

Thanks!
Drew

On Sunday, January 4, 2015 10:26:38 AM UTC-6, Felix.Frank wrote:
>
>  Hi,
>
> well, do you currently have storeconfigs=true in the master's puppet.conf? 
> Otherwise, you are not storing things yet (and cannot use exported 
> resources).
>
> See also:
>
> https://docs.puppetlabs.com/references/3.7.0/configuration.html#storeconfigs
> and try
> puppet master --configprint all | grep ^store
>
> You can most likely just install and configure PuppetDB without risk of 
> loosing any data.
>
> HTH,
> Felix
>
> On 01/02/2015 11:04 PM, Drew Decker wrote:
>  
> Guys, 
>
>  Sorry for the (guessing simple) question, but I can't for the life of 
> me, wrap around the Puppet storage concept.  It appears that I *want *to 
> use PuppetDB, for long-term scalable, future reasons.  However, in my 
> existing environment, I have NO idea what I'm currently using from a 
> catalog storage perspective (I'm running Puppet 3.7.3).  It doesn't appear 
> that I'm using storeconfigs since I don't have ActiveRecord installed and 
> the docs for migrating to PuppetDB is to export the storeconfigs and import 
> them into PuppetDB.  I currently just have a standard Puppet installation 
> with Puppet running along Passenger/Apache and all the nodes are talking to 
> the server.  
>
>  I have no idea where to look or really even begin when it comes to 
> knowing my default store.  This probably sounds pretty basic, but this is 
> somewhat new to me.  I understand most of the concepts, but I just want to 
> make sure that I do the migration correctly.  For all I know, when you 
> install PuppetDB and you do not have storeconfigs, it uses some internal 
> Puppet store that gets migrated automatically into PuppetDB - if this were 
> the case, I still don't know how to verify.
>
>  Please set me straight.  Also - if you have any questions, please feel 
> free to let me know and I'll try to explain.
>
>  Thanks!
> Drew
>
>
>  

-- 
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/e11591be-a1d9-41df-a1dd-45244f090d7a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: puppetdb report processor failed

[jdt]

Hello,

at first sight nothing special.
A bunch of  replace facts, replace catalogs, store reports.
Occasionally I see 
 INFO  [o.a.h.i.c.DefaultHttpClient] I/O exception 
(java.net.SocketException) caught when connecting to the target host: 
Network is unreachable
2015-01-05 09:44:49,748 INFO  [o.a.h.i.c.DefaultHttpClient] Retrying connect

Not sure what that means

Best Regards,
Jo

Op maandag 5 januari 2015 15:06:41 UTC+1 schreef kaustubh chaudhari:
>
> what dose puppetdb.log says ?
>
> -Kaustubh
>
> On Sunday, January 4, 2015 5:40:22 PM UTC-5, jdt wrote:
>>
>> Hello,
>>
>> I recently upgraded from puppetdb 1.6 to 2.2 but now it seems like I'm 
>> having issues with the puppetdb report processor.
>> I keep getting the errors below:
>>  puppet-master[23130]: Report processor failed: Environment is nil, 
>> unable to submit report. This may be due a bug with Puppet. Ensure you are 
>> running the latest revision, see PUP-2508 for more details.
>>
>> I'm running puppet-server 3.6.2 on CentOS 6.x behind an Apache with 
>> passenger.
>> The PuppetDB v 2.2.2 is running on a PostgreSQL 9.3
>>
>> Before the upgrade it worked fine, does anyone have an idea on what might 
>> be wrong? Could it be related to the modified SSL config in puppetdb;s 
>> jetty.ini config file? How could I test this?
>> I noticed it since all the hosts now show as unreported in Puppetboard
>>
>> Best Regards,
>> Jo
>>
>

-- 
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/0555ce57-c388-407c-bcf2-4fc14c2f895e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] puppetdb report processor failed

[jdt]

 Hello,

thx for the help, I think it was related to new Package allow_virtual.
I've added a section to the manifest/site.pp to set this for puppet agents 
running 3.6.1 or higher and now I do get reports into PuppetDB.
So that problem seems to be solved now.
I'm only using the production environment and I'm not using any ENC. I'm 
using hiera to assign modules to hosts using hiera_include('classes') in 
the site.pp

I did get several crashes of puppetdb, due to heap space issues. I've 
bumped up the heap space to 512Mbm then to 768Mb;  but I still got 
Out-of-Memory
I've bumped up the heap space to 1Gb now, before it was running fine with 
256Mb. I've also installed Puppetexplorer on the same box.
Would looking into the generated hprof file help in troubleshooting if 1Gb 
still isn't enough? I have about 850 active nodes

Best Regards,
Jo

Op maandag 5 januari 2015 16:18:16 UTC+1 schreef Ken Barber:
>
> > I recently upgraded from puppetdb 1.6 to 2.2 but now it seems like I'm 
> > having issues with the puppetdb report processor. 
> > I keep getting the errors below: 
> >  puppet-master[23130]: Report processor failed: Environment is nil, 
> unable 
> > to submit report. This may be due a bug with Puppet. Ensure you are 
> running 
> > the latest revision, see PUP-2508 for more details. 
> > 
> > I'm running puppet-server 3.6.2 on CentOS 6.x behind an Apache with 
> > passenger. 
> > The PuppetDB v 2.2.2 is running on a PostgreSQL 9.3 
> > 
> > Before the upgrade it worked fine, does anyone have an idea on what 
> might be 
> > wrong? Could it be related to the modified SSL config in puppetdb;s 
> > jetty.ini config file? How could I test this? 
> > I noticed it since all the hosts now show as unreported in Puppetboard 
>
> I doubt it's related. 
>
> This error is meant to pick up on the bug outlined in 
> https://tickets.puppetlabs.com/browse/PUP-2508, which was fixed in 
> 3.6.1, or at least it should have been. Basically internally the 
> environment is not being set in that case, that patch was meant to fix 
> that. In short, its not meant to happen with 3.6.2 at all, so this is 
> surprising. 
>
> I certainly haven't seen this error in later revisions, or seen this 
> particular problem in the wild. I would suspect that you hadn't 
> restarted your Puppet master but I doubt this is true, as the error 
> only occurs when you upgrade (which needs a restart). Its possibly 
> related to some other magic, are you using environments in anger in 
> your setup? ie. do you use environments that are not 'production', and 
> are you doing anything special like using an ENC or something? 
>
> I think at this point we could try to reproduce the problem ourselves 
> for 3.6.2, but that would take me a little time to set up. Before I do 
> this, have you tested this with Puppet 3.7.3 yet? Also, is this only 
> happening in 1 environment, can you reproduce this on another puppet 
> master perhaps? 
>
> ken. 
>

-- 
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/7442bcf9-9681-4747-898f-c5776bcfcb79%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] not able to run Linux command through puppet

[Spriya]

Hi,

I am trying to run linux command through puppet. when i run the same 
command in the command line it is working fine. But when i placed it in the 
puppet it is throwing me an error.

Here is the code:

*Facter.add('unknownjava') do*
*  setcode do*
*%x(`/usr/bin/diff <(/bin/sort 
/home/weblogic/javafoundmodified.txt) <(/bin/sort 
/home/weblogic/authorizedjava.txt) > /home/weblogic/unknownjava.txt | 
/bin/sed -i 's/^.//' /home/weblogic/unknownjava.txt`)*
*  end*
*end*


Here is the  error:
*sh: command substitution: line 0: syntax error near unexpected token `('*
*sh: command substitution: line 0: `/usr/bin/diff <("/bin/sort 
/home/weblogic/javafoundmodified.txt") <("/bin/sort 
/home/weblogic/authorizedjava.txt") > /home/weblogic/unknownjava.txt | 
/bin/sed -i 's/^.//' /home/weblogic/unknownjava.txt'*
*sh: command substitution: line 0: syntax error near unexpected token `('*



-- 
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/8b32a0d5-f06a-4598-9f72-b5a3aca4a610%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Puppet master on Windows

[Chris Price]

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

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

Both projects have docs on how to run from source:

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

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

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

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

Re: [Puppet Users] puppetdb can't delete reports in the future

[Ryan Anderson]

Wow, thanks, this worked great for me. In case it helps others, here are 
the commands in more detail:

# Connect to postgresql
psql -h localhost -d puppetdb -U puppetdb -W
# The psql prompt
puppetdb=> delete from reports where end_time > current_timestamp;
# Disconnect
puppetdb=> \q

On Wednesday, December 31, 2014 1:28:36 AM UTC-6, Wyatt Alt wrote:
>
> Hey Ryan, 
>
> That makes sense, though I'd guess that new reports are being stored and 
> are available through the API, they just aren't reflected as "latest" 
> since that's determined by the end_time stamp.  report-ttl will be 
> ineffective without resetting to the future, and then you'd be deleting 
> reports you may want to keep. 
>
> Best bet would be to clear them manually in psql: 
>
> delete from reports where end_time > current_timestamp; 
>
> Wyatt 
>
>
>
>

-- 
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/4585054d-37f0-4e64-8d11-5412c3595619%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Announcing Tiny Puppet

[jcbollinger]

On Friday, January 2, 2015 3:49:25 AM UTC-6, Alessandro Franceschi wrote:
>
> Hi all,
> with some hardly hidden pride and excitement I'd like to announce the 
> first release of Tiny Puppet  
> ("Yet Another Puppet Abstraction Layer"), a Puppet module that allows easy, 
> quick and coherent management of virtually any application.
>
>

I remember when you first introduced the Tiny Puppet idea to the group.  
I'm amused now that at the time, in the context of the broader discussion, 
you wrote "Sometimes I wonder if a totally data driven approach is 
something that is always the right choice."  It doesn't look like TP is 
*totally* data-driven, but it sure takes a big leap in that direction.

In any event, TP looks great.  It seems, in part, the natural evolution of 
the module standards ideas: if one accepts the proposition that most low- 
(and some not-so-low-)level modules should have standardized form, then not 
only should we not need multiple modules to manage the same component, we 
shouldn't really need multiple standardized modules, either.  Why write all 
that boilerplate?  Automating that sort of thing is what computers are for.

In fact, there are good reasons for modules -- or at least classes -- 
wrapped around TP resources, but it certainly looks like TP will do a great 
job of minimizing all the boilerplate, which I guess was a primary 
objective.

Well done!


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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/06b532b3-c342-4991-9d50-bd5543277d36%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: How to preserve original timestamp when copying a file?

[staceytian4321]

I means the second (the file's last modification timestamp (mtime) as 
recorded in its file metadata in the file system).

OK, thanks anyway for the clarification.

On Monday, January 5, 2015 9:10:55 AM UTC-5, jcbollinger wrote:
>
>
>
> On Friday, January 2, 2015 2:48:00 PM UTC-6, staceyt...@gmail.com wrote:
>>
>> Hi guys,
>>
>> I am wondering if there was an option to preserve the original timestamp 
>> when copying a file? Right now the timestamp is updated every time the file 
>> is recopied. I don't want that. 
>>
>> I am using open source Puppet 3.7.3.
>>
>>
>
> It depends.  Are you talking about a timestamp recorded in the file's 
> content, or are you talking about the file's last modification timestamp 
> (mtime) as recorded in its file metadata in the file system?
>
> If the former, then it's a question of how you generate the content 
> (template and/or concatenated fragments) and of how you evaluate whether it 
> is in sync.  In that case, you haven't provided enough information for us 
> to make any specific suggestions.
>
> If the latter, then no, Puppet does not have any built-in mechanism 
> providing for lying to the OS about the last access or modification time of 
> files it manages.  If this is indeed what you are trying to do then I urge 
> you to choose a different approach, because anything built on deliberate 
> (meta)data falsification is going to be troublesome and brittle.
>
>
> 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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/6eb45b0d-d6c5-4ccc-8fb4-c5355065f687%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Open source Signing Puppet master & Agent cerificates

[jcbollinger]

On Sunday, January 4, 2015 7:44:05 PM UTC-6, roopchand yanamadala wrote:

[...]
 

> Error: /File[/var/lib/puppet/lib]: Could not evaluate: SSL_connect 
> returned=1 errno=0 state=SSLv3 read server certificate B: certificate 
> verify failed: [self signed certificate in certificate chain for /CN=Puppet 
> CA: puppet-master.xxx.local] Could not retrieve file metadata for puppet://
> puppet-master.xxx.com/plugins: SSL_connect returned=1 errno=0 state=SSLv3 
> read server certificate B: certificate verify failed: [self signed 
> certificate in certificate chain for /CN=Puppet CA: puppet-master.xxx.local]
> Error: Could not retrieve catalog from remote server: SSL_connect 
> returned=1 errno=0 state=SSLv3 read server certificate B: certificate 
> verify failed: [self signed certificate in certificate chain for /CN=Puppet 
> CA: puppet-master.xxx.local]
> Warning: Not using cache on failed catalog
> Error: Could not retrieve catalog; skipping run
> Error: Could not send report: SSL_connect returned=1 errno=0 state=SSLv3 
> read server certificate B: certificate verify failed: [self signed 
> certificate in certificate chain for /CN=Puppet CA: puppet-master.xxx.local]
>


By default, the master's CA identifies itself via a self-signed 
certificate, but your client seems to object to that. Since that is not the 
usual result, I have to guess that the client has been configured to refuse 
self-signed certificates by default (this would be in your system's SSL 
configuration, not in Puppet's own configuration).  In that case, your 
options would be:

   1. Configure your SSL library to accept self-signed certificates (at 
   least the Puppet CA's), or
   2. Obtain and install on the master a CA certificate whose certificate 
   chain traces back to an authority the client trusts.

I'm afraid I have no personal experience with the details of either.


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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/b43c9010-ebc2-4691-80fe-0cbe7b7f5204%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Puppet applies new file, then reverts it back

[jcbollinger]

On Tuesday, December 30, 2014 7:38:05 AM UTC-6, Nicholas Miller wrote:
>
> Hi All,
>
> I'm having a strange issue with one particular file where puppet applies 
> the new file, then reverts back.  It does this every time puppet runs, see 
> below:
>

[...]

That is very strange.  Puppet should never manage the same resource twice 
in the same catalog run, and in any given run, Puppet should never modify 
the same property of the same resource more than once.  These are such 
fundamental Puppet principles that I'm inclined to guess that rather than 
Puppet doing either of the above, it is instead managing two distinct (from 
its perspective) resources that somehow resolve to the same physical 
resource.
 

> Has anyone ever had this problem before?  Any ideas on how to fix it?
>
>
I have not had that problem, but if I have guessed right about its nature 
then you should look carefully at your manifests to find the resource 
duplication (which will revolve around something about the file name and / 
or path of two File resources that the catalog compiler doesn't recognize 
as being equivalent).  You could also look at the cached catalog to verify 
that there are indeed two file resources corresponding to the given file; 
if so, then it is conceivable that comparing them will reveal the nature of 
the collision.

In any event, it may be that running the agent with --debug output enabled 
will provide useful additional information.


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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/23b5cf90-7bc4-41a9-add1-eaefc1689e02%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Package (postfix) is not reconfigured if the preseed file is changed

[jcbollinger]

On Monday, December 29, 2014 7:58:28 AM UTC-6, na...@hu.inter.net wrote:
>
> I've implemented a similar solution to generate a preseed file for postfix 
> as describe in 
> http://projects.puppetlabs.com/projects/1/wiki/debian_preseed_patterns.
>
> The basic difference is that I created a puppet template for the pressed 
> file with some parameters. But it  seems that the solution suggested in the 
> wiki page above is working only on the first installation. If the package 
> is already installed and something is changed, than the new preseed file is 
> installed on the puppet agent, but after that nothing happens. I have to 
> run manually "dpkg-reconfigure -f noninteractive postfix".
>
>

That is the nature of a preseed file: it provides *installation-time* 
information for the package.  More specifically, it configures *apt* with 
respect to how to install the named package; it does not configure the 
package itself.

That approach is fine if you are using Puppet strictly for provisioning (at 
least with respect to the preseeded packages), and especially if you are 
migrating from a provisioning approach that relies on preseed files. The 
article you linked asks "Why bother clobbering a config file that is 
automatically generated out of debconf anyway?" as if there were no good 
answer.  If you intend to have ongoing Puppet management of the 
configuration of the installed services, however, then the preseed file 
approach isn't a very good fit, as you discovered.  In that case, you would 
be better off with the standard model described at the top of the article, 
under "Normally you would just do something like the following."

If you insist on continuing with the preseed file, then you need to add 
something like this to your preseed_package type:

exec { "${name}_preseed_update":
  command => "dpkg-reconfigure -f noninteractive ${name}",
  path => "/sbin:/bin:/usr/sbin:/usr/bin",
  refreshonly => true,
  subscribe => File["/var/local/preseed/${name}.preseed"]
}


Note, too, that the above provides a complete solution only if 
dpkg-reconfigure can be relied upon to restart the service when it 
reconfigures it, but in that case you have the service's run status managed 
in two different places.  Otherwise, you need to add appropriate 
relationships to the Service['postfix'] resource, which cannot be done 
cleanly because the resources that need to be related are declared in 
different scopes (the relationships can nevertheless be declared, though). 
This all makes the preseed approach a bit messy for continuing management.  
It's in any case not any easier than the normal approach, and it's probably 
harder unless you start with preseed files already in hand.


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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/daedd60d-ba9c-4911-b2dc-557996196851%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] puppetdb report processor failed

[Ken Barber]

> I recently upgraded from puppetdb 1.6 to 2.2 but now it seems like I'm
> having issues with the puppetdb report processor.
> I keep getting the errors below:
>  puppet-master[23130]: Report processor failed: Environment is nil, unable
> to submit report. This may be due a bug with Puppet. Ensure you are running
> the latest revision, see PUP-2508 for more details.
>
> I'm running puppet-server 3.6.2 on CentOS 6.x behind an Apache with
> passenger.
> The PuppetDB v 2.2.2 is running on a PostgreSQL 9.3
>
> Before the upgrade it worked fine, does anyone have an idea on what might be
> wrong? Could it be related to the modified SSL config in puppetdb;s
> jetty.ini config file? How could I test this?
> I noticed it since all the hosts now show as unreported in Puppetboard

I doubt it's related.

This error is meant to pick up on the bug outlined in
https://tickets.puppetlabs.com/browse/PUP-2508, which was fixed in
3.6.1, or at least it should have been. Basically internally the
environment is not being set in that case, that patch was meant to fix
that. In short, its not meant to happen with 3.6.2 at all, so this is
surprising.

I certainly haven't seen this error in later revisions, or seen this
particular problem in the wild. I would suspect that you hadn't
restarted your Puppet master but I doubt this is true, as the error
only occurs when you upgrade (which needs a restart). Its possibly
related to some other magic, are you using environments in anger in
your setup? ie. do you use environments that are not 'production', and
are you doing anything special like using an ENC or something?

I think at this point we could try to reproduce the problem ourselves
for 3.6.2, but that would take me a little time to set up. Before I do
this, have you tested this with Puppet 3.7.3 yet? Also, is this only
happening in 1 environment, can you reproduce this on another puppet
master perhaps?

ken.

-- 
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/CAE4bNTkZ8hKf5d-V0%3D%2BFCCwDeEH5SEu1RAdMZe2JhfyW-KQA%3DA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Reading configuration from UI.

[jcbollinger]

On Friday, December 26, 2014 3:40:07 AM UTC-6, glos...@gmail.com wrote:


> ---In my setup, there are two applications (applnA and applnB) running on 
> the same host. My requirement is to configure applnB.
>The configuration values are input to UI and the UI is part of applnA 
> only. 
>
>

If the application providing the configuration GUI runs on the same machine 
as the application being configured, then why do you want to put Puppet 
between?  The only thing I'm coming up with is to revert changes to 
application B's configuration that are not made via the GUI.  If that's not 
a significant concern then application A should just configure application 
B directly.  It will be no harder to code that than to make Puppet do the 
job, especially given that you are starting from zero with Puppet.  There 
are many advantages to such direct coupling if you can rely on the 
applications running on the same host.

If you do want to get Puppet involved, then the GUI program needs to record 
the configuration data on disk (somewhere other than the target 
application's config files).  To get that data into Puppet, you could write 
an ENC, you could use hiera (possibly requiring you to write a custom 
back-end), or you could write custom parser functions.  In any case you 
will write Puppet classes and/or defined types modeling the target 
application's configuration in terms of the data involved (Puppet has rich 
facilities for this part).  

I apologize for speaking in generalities, but you haven't provided any 
specifics for us to work with.


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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/aad7e327-4c9c-4ada-ab4d-06b7f029adbc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Puppet - packages long runtime

[kaustubh chaudhari]

Also you might want to run puppet agent with the below parameters for 
details:

# puppet agent --evaltrace -td

-HTH
Kaustubh

On Monday, January 5, 2015 9:20:52 AM UTC-5, kaustubh chaudhari wrote:
>
> Depends on which package you are installing ... also as mentioned in the 
> mail trail you need to check the manual time or installation.
>
> # time yum -y pkg
>
> On Monday, January 5, 2015 1:50:17 AM UTC-5, Royee Tager wrote:
>>
>> Hello all,
>>
>> New CentOS 6.5 clients which run Puppet for the first time have many 
>> packages to install.
>> As you can see below the total runtime is 355.0697 sec.
>> The package part takes 262.6 sec.
>> Is it somehow possible to reduce that time?
>>
>>
>> config_retrieval6.464cron0.0105exec49.8922file33.3775file_line0.0192mount
>> 0.1564package261.6271service3.2403ssh_authorized_key0.0068yumrepo0.2743
>> Total355.0697
>>
>

-- 
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/391ed197-c520-41ad-b86a-c1520c7818c7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Puppet - packages long runtime

[kaustubh chaudhari]

Depends on which package you are installing ... also as mentioned in the 
mail trail you need to check the manual time or installation.

# time yum -y pkg

On Monday, January 5, 2015 1:50:17 AM UTC-5, Royee Tager wrote:
>
> Hello all,
>
> New CentOS 6.5 clients which run Puppet for the first time have many 
> packages to install.
> As you can see below the total runtime is 355.0697 sec.
> The package part takes 262.6 sec.
> Is it somehow possible to reduce that time?
>
>
> config_retrieval6.464cron0.0105exec49.8922file33.3775file_line0.0192mount
> 0.1564package261.6271service3.2403ssh_authorized_key0.0068yumrepo0.2743
> Total355.0697
>

-- 
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/0d94d929-979f-4ffb-a986-d2b604059ea9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: How to preserve original timestamp when copying a file?

[jcbollinger]

On Friday, January 2, 2015 2:48:00 PM UTC-6, staceyt...@gmail.com wrote:
>
> Hi guys,
>
> I am wondering if there was an option to preserve the original timestamp 
> when copying a file? Right now the timestamp is updated every time the file 
> is recopied. I don't want that. 
>
> I am using open source Puppet 3.7.3.
>
>

It depends.  Are you talking about a timestamp recorded in the file's 
content, or are you talking about the file's last modification timestamp 
(mtime) as recorded in its file metadata in the file system?

If the former, then it's a question of how you generate the content 
(template and/or concatenated fragments) and of how you evaluate whether it 
is in sync.  In that case, you haven't provided enough information for us 
to make any specific suggestions.

If the latter, then no, Puppet does not have any built-in mechanism 
providing for lying to the OS about the last access or modification time of 
files it manages.  If this is indeed what you are trying to do then I urge 
you to choose a different approach, because anything built on deliberate 
(meta)data falsification is going to be troublesome and brittle.


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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/9ad3ebab-c4ff-40e1-9adc-8eb20a966e7e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: puppetdb report processor failed

[kaustubh chaudhari]

what dose puppetdb.log says ?

-Kaustubh

On Sunday, January 4, 2015 5:40:22 PM UTC-5, jdt wrote:
>
> Hello,
>
> I recently upgraded from puppetdb 1.6 to 2.2 but now it seems like I'm 
> having issues with the puppetdb report processor.
> I keep getting the errors below:
>  puppet-master[23130]: Report processor failed: Environment is nil, unable 
> to submit report. This may be due a bug with Puppet. Ensure you are running 
> the latest revision, see PUP-2508 for more details.
>
> I'm running puppet-server 3.6.2 on CentOS 6.x behind an Apache with 
> passenger.
> The PuppetDB v 2.2.2 is running on a PostgreSQL 9.3
>
> Before the upgrade it worked fine, does anyone have an idea on what might 
> be wrong? Could it be related to the modified SSL config in puppetdb;s 
> jetty.ini config file? How could I test this?
> I noticed it since all the hosts now show as unreported in Puppetboard
>
> Best Regards,
> Jo
>

-- 
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/3abd7ab1-bf03-4fbf-ba51-68185a7f19b9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] How to solve $concat_basedir not defined error?

[Pete Brown]

I just had a look at the docs and pluginsync needs to be set to true
in the [main] of Both the master and the client.
https://docs.puppetlabs.com/guides/plugins_in_modules.html#enabling-pluginsync

It is on by default in puppet 3+
The default was false in earlier versions.

On 15 December 2014 at 23:24, Martin Alfke  wrote:
> AFAIK pluginsync needs to be set on the agents.
> On the Master you need to install the module
>  - puppet module install puppetlabs/concat
>
> On the agent you need at least one puppet agent run to synchronize the 
> required concat scripts.
> If you run in hoop mode only, concat will always fail due to missing scripts.
>
>> On 15.12.2014, at 09:33, Pete Brown  wrote:
>>
>> Where did you set pluginsync = true?
>> It needs to be in the master section of the puppet.conf on your puppet 
>> master.
>>
>> Which version of puppet, facter, hiera and the concat module are you using?
>>
>> On 13 December 2014 at 08:26, Haani Niyaz  wrote:
>>> Thanks for the info.
>>>
>>> `facter concat_basedir` returns empty.
>>>
>>> `puppet plugin download` returns 'no plugins downloaded.'
>>>
>>>
>>>
>>>
>>>
>>> On Saturday, 13 December 2014 06:27:55 UTC+11, Hunter Haugen wrote:

 The concat_basedir custom fact comes from the concat module
 https://forge.puppetlabs.com/puppetlabs/concat so on the agent, if you can
 run `facter concat_basedir` then puppet should be able to pick it up.

 It looks like you do have the concat module installed at
 /etc/puppet/modules/concat, and if you have pluginsync turned on (which is
 on by default, fwiw) then I'm not really sure what could be the hang-up.

 What does running `puppet plugin download` on the agent do? Does it fix
 the issue?



 -Hunter

 On Fri, Dec 12, 2014 at 2:24 AM, Haani Niyaz  wrote:
>
> Hi there,
>
> I'm fairly new to puppet I am attempting to setup a dashboard for
> puppetdb. I came across puppetexplorer and wanted to trial it out.
>
> I attempted to install puppetexplorer  by doing the following:
>
> puppet module install spotify-puppetexplorer
>
>
> #Added puppetexplorer to my puppet node declaration
>
>
> node 'puppet' {
>  include 'puppetexplorer'
> }
>
>
>
> On running the agent on the master to install puppetexplorer I get the
> following error (running it as root):
>
>
>
>
> Error: Could not retrieve catalog from remote server: Error 400 on
> SERVER: $concat_basedir not defined. Try running again with 
> pluginsync=true
> on the [master] and/or [main] section of your node's
> '/etc/puppet/puppet.conf'. at
> /etc/puppet/modules/concat/manifests/setup.pp:20 on node 
> puppet.example.com
>
>
>
> I already tried setting pluginsync=true and however it does not make a
> difference. Can someone hint at what might be the problem?
>
> 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...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/30b064e2-c85b-42fe-b2e2-e0a2324cd3fd%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/a0c06a9c-5c17-4fb3-b322-d05b6e56496f%40googlegroups.com.
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>
>>
>>
>> --
>> Pete Brown
>> Director and Primary Systems Engineer
>> Abstract IT Pty Ltd.
>>
>> --
>> 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/CAM8R_x8txjAPZyZQYyU4pKKpnGx%2BiaRKMXP09%2Bceq00_Byvv5Q%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/F038EBAF-24EA-4667-9BAF-0E847B3549A0%40gmail.com.
> For more options, visit https://groups.google.com/d/optout.



-- 
Pete Brown
Director and Primary Systems Engine

Re: [Puppet Users] Puppet - packages long runtime

[Christopher Wood]

On Mon, Jan 05, 2015 at 11:07:12AM +0100, Martin Alfke wrote:
> Hi,
> On 05 Jan 2015, at 07:50, Royee Tager  wrote:
> 
> > Hello all,
> > 
> > New CentOS 6.5 clients which run Puppet for the first time have many 
> > packages to install.
> > As you can see below the total runtime is 355.0697 sec.
> > The package part takes 262.6 sec.
> > Is it somehow possible to reduce that time?
> 
> Did you measure the time for manual installation?
> I assume that the timing is similar.
> You can speed package installation by installing a local repo mirror and 
> disable the fastest mirror option.

Explicitly selecting local mirrors will speed up the download.

https://docs.puppetlabs.com/references/latest/type.html#yumrepo

An idea I've toyed with, but haven't yet implemented (since we're so far fine 
with having initial agent runs take 5 minutes), is grepping package names for a 
particular set of profiles out of the classes in question and making a new rpm 
which depends on all those. Then have puppet install the new rpm first using 
some creative chaining. I suspect that yum might be quicker at dependency 
resolution than puppet is.

(I would still have all the other packages listed to provide a complete server 
spec in puppet.)
 
> hth,
> 
> Martin
> 
> 
> 
> > 
> > 
> > config_retrieval6.464
> > cron0.0105
> > exec49.8922
> > file33.3775
> > file_line   0.0192
> > mount   0.1564
> > package 261.6271
> > service 3.2403
> > ssh_authorized_key  0.0068
> > yumrepo 0.2743
> > Total   355.0697
> > 
> > -- 
> > 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/15a5de74-2bc9-4627-ae37-82865dae9d1b%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/D298D66E-3E1D-4D98-B61F-660FB7126D11%40gmail.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/20150105120424.GA26503%40iniquitous.heresiarch.ca.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Pupept User Group @ FOSDEM

[Johan De Wit]

Hi Puppet User Group Organisers,

FOSDEM has approved the stand for this year.  If you want to represent 
your PUG, you are very welcome to join us at the stand.


Like previous year, I would like to ask every PUG, to write a little 
piece in English or your native language to present your PUG to the public.


If you send me your text, the BPUG will be pleased to get it printed and 
hand it out at FOSDEM.


See you all @ FOSDEM.

greats

Johan

--
Johan De Wit

Open Source Consultant

Red Hat Certified Engineer  (805008667232363)
Puppet Certified Professional 2013/2014 (PCP006)
_
 
Open-Future Phone +32 (0)2/255 70 70

Zavelstraat 72  Fax   +32 (0)2/255 70 71
3071 KORTENBERG Mobile+32 (0)474/42 40 73
BELGIUM http://www.open-future.be
_
 


Next Events:
Zabbix Certified Training | 
http://www.open-future.be/zabbix-certified-specialist-training-5th-till-7th-january
Zabbix Certified Professional | 
http://www.open-future.be/zabbix-certified-professional-training-8th-till-9th-janaury
Bacula Administrator 1 | 
http://www.open-future.be/bacula-administrator-i-training-13th-till-15th-january
Puppet Fundamentals | 
http://www.open-future.be/puppet-fundamentals-training-26th-till-28th-january
Puppet Architect | 
http://www.open-future.be/puppet-architect-training-29th-till-30th-january
Subscribe to our newsletter | http://eepurl.com/BUG8H

--
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/54AA7860.1000107%40open-future.be.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Issues with RHEL7

[Saxon Mailey]

Hi Guys,

There appears to be a typo in the subscription-manager example (its missing 
the s from rpms)

The command should be: subscription-manager repos --enable 
rhel-7-server-optional-rpms

This fixed the problem for me.

Thanks :)

On Saturday, 14 June 2014 03:49:44 UTC+10, Arkandel wrote:
>
> Hey folks,
>
> I'm having some issues installing puppet on a brand new RHEL7 server VM 
> and I was wondering if any of you has ran into the same kinds of issues.
>
> This is what I'm getting:
>
> -
> yum install puppet
> Loaded plugins: langpacks, product-id, subscription-manager
> epel/x86_64/metalink   
> 
>| 9.3 kB 
>  00:00:00 
> epel   
> 
>| 3.7 kB 
>  00:00:00 
> rhel-7-server-rpms 
> 
>| 3.7 kB 
>  00:00:00 
> epel/x86_64/primary_db 
> 
>| 1.8 MB 
>  00:00:01 
> Resolving Dependencies
> --> Running transaction check
> ---> Package puppet.noarch 0:3.6.0-1.el7 will be installed
> --> Processing Dependency: hiera >= 1.0.0 for package: 
> puppet-3.6.0-1.el7.noarch
> --> Processing Dependency: facter >= 1.6.6 for package: 
> puppet-3.6.0-1.el7.noarch
> --> Processing Dependency: rubygem(rgen) for package: 
> puppet-3.6.0-1.el7.noarch
> --> Processing Dependency: ruby(selinux) for package: 
> puppet-3.6.0-1.el7.noarch
> --> Running transaction check
> ---> Package facter.x86_64 0:2.0.1-2.el7 will be installed
> ---> Package hiera.noarch 0:1.3.4-1.el7 will be installed
> ---> Package puppet.noarch 0:3.6.0-1.el7 will be installed
> --> Processing Dependency: ruby(selinux) for package: 
> puppet-3.6.0-1.el7.noarch
> ---> Package rubygem-rgen.noarch 0:0.6.6-2.el7 will be installed
> --> Finished Dependency Resolution
> Error: Package: puppet-3.6.0-1.el7.noarch (epel)
>Requires: ruby(selinux)
>  You could try using --skip-broken to work around the problem
>  You could try running: rpm -Va --nofiles --nodigest
> -
>
> And yet 
>
> -
> yum info libselinux
> Loaded plugins: langpacks, product-id, subscription-manager
> Installed Packages
> Name: libselinux
> Arch: x86_64
> Version : 2.2.2
> Release : 6.el7
> Size: 159 k
> Repo: installed
> From repo   : anaconda
> Summary : SELinux library and simple utilities
> URL : http://oss.tresys.com/git/selinux.git
> License : Public Domain
>
> and
>
> Installed Packages
> Name: epel-release
> Arch: noarch
> Version : 7
> Release : 0.1
> Size: 22 k
> Repo: installed
> Summary : Extra Packages for Enterprise Linux repository configuration
> URL : http://download.fedoraproject.org/pub/epel
> License : GPLv2
> --
>
> What gives?
>

-- 
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/4ecb2493-50d5-43a4-871c-826a705b27a8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Puppet - packages long runtime

[Martin Alfke]

Hi,
On 05 Jan 2015, at 07:50, Royee Tager  wrote:

> Hello all,
> 
> New CentOS 6.5 clients which run Puppet for the first time have many packages 
> to install.
> As you can see below the total runtime is 355.0697 sec.
> The package part takes 262.6 sec.
> Is it somehow possible to reduce that time?

Did you measure the time for manual installation?
I assume that the timing is similar.
You can speed package installation by installing a local repo mirror and 
disable the fastest mirror option.

hth,

Martin



> 
> 
> config_retrieval  6.464
> cron  0.0105
> exec  49.8922
> file  33.3775
> file_line 0.0192
> mount 0.1564
> package   261.6271
> service   3.2403
> ssh_authorized_key0.0068
> yumrepo   0.2743
> Total 355.0697
> 
> -- 
> 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/15a5de74-2bc9-4627-ae37-82865dae9d1b%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/D298D66E-3E1D-4D98-B61F-660FB7126D11%40gmail.com.
For more options, visit https://groups.google.com/d/optout.