Re: [Puppet Users] puppet5 upgrade performance issues

[Matthaus Owens]

Hey Chris,
Just wondering if you got any further in figuring this out. I'd be
happy to try to help debug some more if you need as well.

On Wed, Jan 10, 2018 at 10:39 PM, Chris Smith  wrote:
> On 11/01/18 09:42, Poil wrote:
>> Hey,
>>
>> Are you sure that you have environment cache enabled on your Puppet5
>> installation ? (because x10 is what we have here when we disable it)
>
> No, that's not enabled at the moment (it wasn't before either). I'm
> working on setting that up, I did a test run and it helped quite a bit.
>
> Thanks for the suggestion.
>
> Cheers,
> Chris.
>
> --
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/puppet-users/8b8cc991-165b-20df-dbf2-8fe9e48ecd24%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/CACD%3DwAetO8BEYfWnQV%2B6PGe7cx%3DgYttG%2BYCYWvxCpYts8EaOGA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] puppet5 upgrade performance issues

[Matthaus Owens]

Chris,

Good to know that PuppetDB isn't the cause here. One thing worth doing
on your servers is moving forward to Puppet-agent 5.3.2. There was a
performance regression in Puppet 5
https://tickets.puppetlabs.com/browse/PUP-8009 around
internationalization and modules (something like 30% in some cases).
You might also need to set `disable_i18n=true` in the [master] section
of your puppet.conf.
To see what puppetserver is doing and how long it takes you can set
`profile=true` in the [master] section of puppet.conf (I would
recommend only doing this on one of your servers, as it will generate
a lot of log output per puppet run). The profiling results will be
logged at the info level to
/var/log/puppetlabs/puppetserver/puppetserver.log, so you could then
inspect the timing of different parts of the agent lifecycle.

On Tue, Jan 9, 2018 at 7:11 PM, Chris Smith <dmag...@gmail.com> wrote:
> Hi,
>
> Thanks for your help.
>
> On 10/01/18 06:36, Matthaus Owens wrote:
>> Chris,
>> To better help you, it would be great to know a few more things about
>> your installation. First question: are you running puppetserver 5.0.0
>> or something later in the 5.x series (and is it the same on all
>> servers)? Second, what version of the puppet-agent are on those
>> servers? puppetserver 5.1.3 included a fix for
>> https://tickets.puppetlabs.com/browse/SERVER-1922 which should improve
>> performance some.
>
> Hm. Interesting, thanks. I'll check out what a 5.0 -> 5.1 upgrade will do.
>
>>
>> Hiera 3 + hiera-eyaml may also be contributing to the slowness. Here
>> is one ticket (related to SERVER-1922) that indicated moving to hiera
>> 5 improved compile times substantially:
>> https://tickets.puppetlabs.com/browse/SERVER-1919
>
> Also interesting but as noted on the last comment, a lot of the
> structure was changed so that might not all have been hiera3 -> hiera5.
>
>> To dig into what may be causing the compiles to be slower, I would
>> recommend first checking out the client metrics.
>> https://puppet.com/docs/puppetserver/5.1/http_client_metrics.html has
>> some details, and I would be interested in the client metrics that
>> page lists under the /puppet/v3/catalog. They are PuppetDB related
>> requests, and as that was also upgraded alongside puppetserver it
>> would be good to eliminate PuppetDB as a contributor. PuppetDB
>> slowness can show up as slow catalog compiles, which in turn will hold
>> jrubies for longer and might explain some of what you are seeing.
>
> puppetservers are all the same.
>
> We upgraded to:
> # /opt/puppetlabs/server/bin/puppetserver -v
> puppetserver version: 5.0.0
>
> puppetdb is this, it should have been 5.0 as well but I stuffed it up.
> # /opt/puppetlabs/server/bin/puppetdb -v
> puppetdb version: 5.1.3
>
>
> agents are all:
> # /opt/puppetlabs/puppet/bin/puppet --version
> 5.0.0
>
>
> The metrics say
>
> {
>   "route-id": "puppet-v3-file_metadata-/*/",
>   "count": 9373,
>   "mean": 10217,
>   "aggregate": 95763941
> },
> {
>   "route-id": "puppet-v3-catalog-/*/",
>   "count": 828,
>   "mean": 94773,
>   "aggregate": 78472044
> },
> {
>   "route-id": "puppet-v3-node-/*/",
>   "count": 831,
>   "mean": 62709,
>   "aggregate": 5279
> },
> {
>   "route-id": "puppet-v3-file_metadatas-/*/",
>   "count": 4714,
>   "mean": 9288,
>   "aggregate": 43783632
> },
> {
>   "route-id": "puppet-v3-report-/*/",
>   "count": 780,
>   "mean": 3433,
>   "aggregate": 2677740
> },
>
>
>
>   "http-client-metrics": [
> {
>   "count": 821,
>   "mean": 48,
>   "aggregate": 39408,
>   "metric-name":
> "puppetlabs.localhost.http-client.experimental.with-metric-id.puppetdb.command.replace_catalog.full-response",
>   "metric-id": [
> "puppetdb",
> "command",
> "replace_catalog"
>   ]
> },
> {
>   "count": 832,
>   "mean": 25,
>   "aggregate": 20800,
>   "metric-name":
>

Re: [Puppet Users] puppet5 upgrade performance issues

[Matthaus Owens]

Chris,
Hiera 3 + hiera-eyaml may also be contributing to the slowness. Here
is one ticket (related to SERVER-1922) that indicated moving to hiera
5 improved compile times substantially:
https://tickets.puppetlabs.com/browse/SERVER-1919

-Haus

On Tue, Jan 9, 2018 at 11:36 AM, Matthaus Owens <matth...@puppet.com> wrote:
> Chris,
> To better help you, it would be great to know a few more things about
> your installation. First question: are you running puppetserver 5.0.0
> or something later in the 5.x series (and is it the same on all
> servers)? Second, what version of the puppet-agent are on those
> servers? puppetserver 5.1.3 included a fix for
> https://tickets.puppetlabs.com/browse/SERVER-1922 which should improve
> performance some.
> To dig into what may be causing the compiles to be slower, I would
> recommend first checking out the client metrics.
> https://puppet.com/docs/puppetserver/5.1/http_client_metrics.html has
> some details, and I would be interested in the client metrics that
> page lists under the /puppet/v3/catalog. They are PuppetDB related
> requests, and as that was also upgraded alongside puppetserver it
> would be good to eliminate PuppetDB as a contributor. PuppetDB
> slowness can show up as slow catalog compiles, which in turn will hold
> jrubies for longer and might explain some of what you are seeing.
>
> On Mon, Jan 8, 2018 at 7:31 PM, chris smith <dmag...@gmail.com> wrote:
>> Hi there,
>>
>> I recently did an upgrade from puppetserver 2.7.2 to puppetserver 5.0 and
>> performance has bottomed out pretty terribly. Agents and puppetdb also got
>> updated. Compiling the catalog on the server used to take 10-20 seconds, now
>> they are taking 90-150 seconds and agent runs are taking 30+ minutes (used
>> to be a couple of minutes).
>>
>> The architecture is distributed, with:
>>  * a central ca, running puppetserver, puppetdb, postgres 9.6
>>  * separate puppetservers replicated in other datacentres. These are also
>> running puppetdb, pointing writes to the central ca, but reads go to a
>> locally replicated database
>>
>> Other servers (agents) point to the replicated puppetservers to do all of
>> the work.
>>
>> The puppetservers were tuned (upped jvm memory, set max-instances).
>>
>> The architecture hasn't changed since the upgrade.
>>
>> The puppetservers are still running hiera3 configs, they haven't been
>> converted yet (it's on the list, but from what I read it wasn't a
>> showstopper). We have a reasonable amount of encrypted yaml files (using
>> hiera-eyaml-gpg), though this was the same as pre-upgrade and hasn't changed
>> significantly.
>>
>> Since the upgrade, I've tried re-tuning the jvm settings, changing
>> max-instances and not having much luck at all. I found the experimental
>> dashboard on the puppetservers and they show that there are no free jruby's,
>> but there has to be something I'm missing that's causing that to happen.
>>
>> I'm lost on what to look at next, is there an easy way to peak inside jruby
>> to see what's taking so long?
>>
>> Any suggestions would be great.
>>
>> Cheers,
>> Chris.
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Puppet Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to puppet-users+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/puppet-users/4d0dc37f-c07e-4f8c-8323-44a90d68b208%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/CACD%3DwAfJveNpAzekCvjeP8aZ7ma4mD4%2B1KC9JKE4mqELbktB4g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] puppet5 upgrade performance issues

[Matthaus Owens]

Chris,
To better help you, it would be great to know a few more things about
your installation. First question: are you running puppetserver 5.0.0
or something later in the 5.x series (and is it the same on all
servers)? Second, what version of the puppet-agent are on those
servers? puppetserver 5.1.3 included a fix for
https://tickets.puppetlabs.com/browse/SERVER-1922 which should improve
performance some.
To dig into what may be causing the compiles to be slower, I would
recommend first checking out the client metrics.
https://puppet.com/docs/puppetserver/5.1/http_client_metrics.html has
some details, and I would be interested in the client metrics that
page lists under the /puppet/v3/catalog. They are PuppetDB related
requests, and as that was also upgraded alongside puppetserver it
would be good to eliminate PuppetDB as a contributor. PuppetDB
slowness can show up as slow catalog compiles, which in turn will hold
jrubies for longer and might explain some of what you are seeing.

On Mon, Jan 8, 2018 at 7:31 PM, chris smith  wrote:
> Hi there,
>
> I recently did an upgrade from puppetserver 2.7.2 to puppetserver 5.0 and
> performance has bottomed out pretty terribly. Agents and puppetdb also got
> updated. Compiling the catalog on the server used to take 10-20 seconds, now
> they are taking 90-150 seconds and agent runs are taking 30+ minutes (used
> to be a couple of minutes).
>
> The architecture is distributed, with:
>  * a central ca, running puppetserver, puppetdb, postgres 9.6
>  * separate puppetservers replicated in other datacentres. These are also
> running puppetdb, pointing writes to the central ca, but reads go to a
> locally replicated database
>
> Other servers (agents) point to the replicated puppetservers to do all of
> the work.
>
> The puppetservers were tuned (upped jvm memory, set max-instances).
>
> The architecture hasn't changed since the upgrade.
>
> The puppetservers are still running hiera3 configs, they haven't been
> converted yet (it's on the list, but from what I read it wasn't a
> showstopper). We have a reasonable amount of encrypted yaml files (using
> hiera-eyaml-gpg), though this was the same as pre-upgrade and hasn't changed
> significantly.
>
> Since the upgrade, I've tried re-tuning the jvm settings, changing
> max-instances and not having much luck at all. I found the experimental
> dashboard on the puppetservers and they show that there are no free jruby's,
> but there has to be something I'm missing that's causing that to happen.
>
> I'm lost on what to look at next, is there an easy way to peak inside jruby
> to see what's taking so long?
>
> Any suggestions would be great.
>
> Cheers,
> Chris.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/4d0dc37f-c07e-4f8c-8323-44a90d68b208%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/CACD%3DwAf5eC%2B8mixcyYjUGAm-0jeBzYnq%2BOydg3ZNkJ5YWoROmg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] /etc/sysconfig/puppetserver git source?

[Matthaus Owens]

Just to add a little extra info, the template draws from several
sources, one of which is in the project.clj for puppetserver here:
https://github.com/puppetlabs/puppetserver/blob/5.1.x/project.clj#L113-L114

On Wed, Jan 3, 2018 at 12:09 PM, Christopher Wood
 wrote:
> That turned out to be even more interesting, thank you!
>
> On Wed, Jan 03, 2018 at 06:38:02PM +, Morgan Rhodes wrote:
>>Hi Christopher,
>>That file is generated during packaging and is generated from a template
>>in the ezbake
>>project. 
>> [1]https://github.com/puppetlabs/ezbake/blob/master/resources/puppetlabs/lein-ezbake/template/foss/ext/default.erb
>>On Wed, Jan 3, 2018 at 9:56 AM Christopher Wood
>><[2]christopher_w...@pobox.com> wrote:
>>
>>  Is the source for /etc/sysconfig/puppetserver in the puppetserver rpm
>>  stored in any public-facing git repository? If so, where?
>>
>>  More details:
>>
>>  I was reading the tuning guide (it's augment time again) and it occurred
>>  to me to read the commit messages for this file to see how Puppet
>>  figured out the defaults. That information may inform my own
>>  configurations.
>>
>>  [3]https://puppet.com/docs/puppetserver/5.1/tuning_guide.html
>>
>>  I'm not actually a programmer, and couldn't find this file or obvious
>>  source code in the puppetserver git repository if it is there. (Hints
>>  welcome too!)
>>
>>  [4]https://github.com/puppetlabs/puppetserver
>>
>>  Running puppetserver 5.1.4 here.
>>
>>  --
>>  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 [5]puppet-users+unsubscr...@googlegroups.com.
>>  To view this discussion on the web visit
>>  
>> [6]https://groups.google.com/d/msgid/puppet-users/20180103175542.2jt55rzf3hz3tpkp%40iniquitous.heresiarch.ca.
>>  For more options, visit [7]https://groups.google.com/d/optout.
>>
>>--
>>Morgan Rhodes
>>mor...@puppet.com
>>Release Engineer
>>
>>--
>>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 [8]puppet-users+unsubscr...@googlegroups.com.
>>To view this discussion on the web visit
>>
>> [9]https://groups.google.com/d/msgid/puppet-users/CA%2BFnDv3G5WtPSh95p7KW9nraEKBZx9Fo%3DEoRFgj5PNO5OO8-Dg%40mail.gmail.com.
>>For more options, visit [10]https://groups.google.com/d/optout.
>>
>> References
>>
>>Visible links
>>1. 
>> https://github.com/puppetlabs/ezbake/blob/master/resources/puppetlabs/lein-ezbake/template/foss/ext/default.erb
>>2. mailto:christopher_w...@pobox.com
>>3. https://puppet.com/docs/puppetserver/5.1/tuning_guide.html
>>4. https://github.com/puppetlabs/puppetserver
>>5. mailto:puppet-users%2bunsubscr...@googlegroups.com
>>6. 
>> https://groups.google.com/d/msgid/puppet-users/20180103175542.2jt55rzf3hz3tpkp%40iniquitous.heresiarch.ca
>>7. https://groups.google.com/d/optout
>>8. mailto:puppet-users+unsubscr...@googlegroups.com
>>9. 
>> https://groups.google.com/d/msgid/puppet-users/CA%2BFnDv3G5WtPSh95p7KW9nraEKBZx9Fo%3DEoRFgj5PNO5OO8-Dg%40mail.gmail.com?utm_medium=email_source=footer
>>   10. 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/20180103200959.f4lafrj3bqf3bzwf%40iniquitous.heresiarch.ca.
> 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/CACD%3DwAdfVhR4UHvR17uCJa-aHu1diCmv5CstK4O-%2Bz85vyKu7A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] PuppetServer 2.8 resource Leak

[Matthaus Owens]

Depending on what the trocla library does, it could be leaking objects
to the java layer, in which case tuning the max-requests-per-instance
down would not help. In general, the best way to find leaks like you
are talking about is described here:
https://puppet.com/blog/puppet-server-advanced-memory-debugging and
involves taking some heap dumps and investigating what changes between
dumps to see what is leaking.

On Tue, Oct 3, 2017 at 5:11 AM, Poil  wrote:
> Hi,
>
> We have PuppetServer 2.8 on RHEL7.
>
> After some days computation of the catalog become slower and slower; the
> load average of the compute nodes increased and the compute goes in timeout.
>
> All our 4 computes nodes have 48 cores, only 10% of each core is used when
> the timeout occured.
>
> We are on hiera v3, we only tuned  "max-requests-per-instance: 5000" because
> of a databases connection leak with our Trocla library.
>
> Only 150 nodes are connected to our PuppetServer.
>
> We never had this problem with Puppet3 (with more than 3000 nodes)
>
> Anyone have already see this or have a tips to resolv this ?
>
> Best regards,
>
> --
> 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/c6a457e9-5caf-f048-68b7-9dbdc867a5bb%40quake.fr.
> 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/CACD%3DwAc_nSQgO22P7RwytO1vz4X8KtgazJ5P75AqUfmyTuhjwQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Urgent Help Required | Puppet run is dead slow

[Matthaus Owens]

On Mon, Dec 12, 2016 at 8:34 AM, Harish Kothuri 
wrote:

> Hi,
>
> I have a puppet master v3.8.7 and having 300+ nodes running fine till last
> week.
>
> All the agents are running very slow since last week and sometimes it
> started complaining that puppet master is running on heavy load.
>
>
> Following is my master configuration details:
> Puppet : 3.8.7
> CentOS: 6.7 Final
> RAM : 32GB
>
> *processor   : 0*
> *vendor_id   : GenuineIntel*
> *cpu family  : 6*
> *model   : 44*
> *model name  : Intel(R) Xeon(R) CPU   X5690  @ 3.47GHz*
> *stepping: 2*
> *microcode   : 26*
> *cpu MHz : 3457.999*
> *cache size  : 12288 KB*
> *physical id : 0*
> *siblings: 2*
> *core id : 0*
> *cpu cores   : 2*
> *apicid  : 0*
> *initial apicid  : 0*
> *fpu : yes*
> *fpu_exception   : yes*
> *cpuid level : 11*
> *wp  : yes*
> *flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
> mca cmov pat pse36 clflush dts mmx fxsr sse sse2 ss ht syscall nx rdtscp lm
> constant_tsc arch_perfmon pebs bts xtopology tsc_reliable nonstop_tsc
> aperfmperf unfair_spinlock pni pclmulqdq ssse3 cx16 sse4_1 sse4_2 popcnt
> aes hypervisor lahf_lm ida arat epb dtherm*
> *bogomips: 6915.99*
> *clflush size: 64*
> *cache_alignment : 64*
> *address sizes   : 40 bits physical, 48 bits virtual*
> *power management:*
>
> *processor   : 1*
> *vendor_id   : GenuineIntel*
> *cpu family  : 6*
> *model   : 44*
> *model name  : Intel(R) Xeon(R) CPU   X5690  @ 3.47GHz*
> *stepping: 2*
> *microcode   : 26*
> *cpu MHz : 3457.999*
> *cache size  : 12288 KB*
> *physical id : 0*
> *siblings: 2*
> *core id : 1*
> *cpu cores   : 2*
> *apicid  : 1*
> *initial apicid  : 1*
> *fpu : yes*
> *fpu_exception   : yes*
> *cpuid level : 11*
> *wp  : yes*
> *flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
> mca cmov pat pse36 clflush dts mmx fxsr sse sse2 ss ht syscall nx rdtscp lm
> constant_tsc arch_perfmon pebs bts xtopology tsc_reliable nonstop_tsc
> aperfmperf unfair_spinlock pni pclmulqdq ssse3 cx16 sse4_1 sse4_2 popcnt
> aes hypervisor lahf_lm ida arat epb dtherm*
> *bogomips: 6915.99*
>
> *Error Details:*
>
> *Error 1:*
> Failed to generate additional resources using 'eval_generate': Error 503
> on SERVER: This website is under heavy loadWe're sorry, too
> many people are accessing this website at the same time. We're working on
> this problem. Please try again later.
>
> *Error 2:*
> Could not retrieve catalog from remote server: Error 400 on SERVER: Failed
> to submit 'replace facts' command for node.domain.com to PuppetDB at
> puppetmaster.domain.com:8081: Connection refused - connect(2)
>

This error indicates that PuppetDB may be in the process of restarting (or
isn't handling requests for some other reason). It would be good to know
what is happening to PuppetDB. Is there anything in PuppetDB's logs to
indicate what is going on?


>
> Also, attaching the puppet agent log with --debug enabled.
>
> Kindly help.
>
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/puppet-users/bc165bf9-ab20-4a95-8785-1b804dcc2ce3%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/CACD%3DwAdGjjyqv2v4T9mMzVz0KV80oGmGww-E-4UUmKk5YTREjw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: puppetserver unable to start after yum update

[Matthaus Owens]

John,
Thanks for the correction. I definitely mixed up my words while responding
here.

On Wed, Sep 7, 2016 at 5:54 AM, jcbollinger 
wrote:

>
>
> On Tuesday, September 6, 2016 at 12:22:03 PM UTC-5, Matthaus Litteken
> wrote:
>>
>> [...] In answer to your second question, rpmnew files are for when a
>> configuration file has been changed by the user and a package update
>> changes it. Because yum/rpm can't safely replace the configuration file, it
>> drops an rpmnew version of the file with a diff of the updated config file
>> from the package. This allows the user to manually merge in any needed
>> changes (in this case the needed change is the change to the
>> BOOTSTRAP_CONFIG setting).
>>
>>
> It's at best misleading to describe .rpmnew files as containing a diff.
> An x.rpmnew file is the version of x that RPM would have installed if x had
> no local modifications.  If you don't need to preserve the local
> modifications then you can replace x with x.rpmnew.  Otherwise, you can *make
> your own diff* between the two to judge how to merge the changes.
>
>
> 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/8c9d7ace-dceb-4fc1-bdb7-4955543dfc0e%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/CACD%3DwAd9JsZ%2BvVnBr-Uz6Hcq_QN5kiEbYqfy%3DSQ3r2oFv55Dvg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: puppetserver unable to start after yum update

[Matthaus Owens]

Jim,
The puppet server 2.5.0 release had a few changes with respect to
bootstrap.cfg (there are details about it here:
https://docs.puppet.com/puppetserver/2.5/bootstrap_upgrade_notes.html). In
your case it looks like you had modified /etc/sysconfig/puppetserver to
change the heap size, so yum was unable to update your sysconfig file to
point to the new bootstrap config locations (there is some description of
this issue here
https://docs.puppet.com/puppetserver/2.5/release_notes.html#potential-warnings-when-upgrading-with-a-modified-init-configuration).
To get going again, I would recommend updating the BOOTSTRAP_CONFIG setting
in /etc/sysconfig/puppetserver to match what is in
/etc/sysconfig/puppetserver.rpmnew ("/etc/puppetlabs/puppetserver/
services.d/,/opt/puppetlabs/server/apps/puppetserver/config/services.d/").
In answer to your second question, rpmnew files are for when a
configuration file has been changed by the user and a package update
changes it. Because yum/rpm can't safely replace the configuration file, it
drops an rpmnew version of the file with a diff of the updated config file
from the package. This allows the user to manually merge in any needed
changes (in this case the needed change is the change to the
BOOTSTRAP_CONFIG setting).

Hope that helps,
Matthaus

On Sat, Sep 3, 2016 at 6:38 AM, Jim Jim 
wrote:

> Not sure why I am not able to see my email. I don't think it has any
> offensive or rude language ?
>
> On Fri, Sep 2, 2016 at 7:09 PM, Jim Jim 
> wrote:
>
>> Hi Guys,
>>
>> I had a good running puppetserver daemon but after
>>
>> sudo yum update -y
>>
>> It is not running, complaining Specified bootstrap config file does not
>> exist: '/etc/puppetlabs/puppetserver/bootstrap.cfg'.
>> detailed log output from puppetserver-daemon.log is as below:
>>
>> OpenJDK 64-Bit Server VM warning: ignoring option MaxPermSize=256m;
>> support was removed in 8.0
>> Exception in thread "main" java.lang.IllegalArgumentException:
>> Specified bootstrap config file does not exist:
>> '/etc/puppetlabs/puppetserver/bootstrap.cfg'
>> at puppetlabs.trapperkeeper.boots
>> trap$eval14658$wrap_uri_error__14663$fn__14664.invoke(bootstrap.clj:131)
>> at puppetlabs.trapperkeeper.boots
>> trap$eval14658$wrap_uri_error__14663.invoke(bootstrap.clj:127)
>> at puppetlabs.trapperkeeper.bootstrap$eval14681$read_config__
>> 14686$fn__14687.invoke(bootstrap.clj:150)
>> at puppetlabs.trapperkeeper.bootstrap$eval14681$read_config__
>> 14686.invoke(bootstrap.clj:134)
>> at puppetlabs.trapperkeeper.boots
>> trap$eval14704$get_annotated_bootstrap_entries__14709$fn__
>> 14710$iter__14711__14717$fn__14718.invoke(bootstrap.clj:160)
>> at clojure.lang.LazySeq.sval(LazySeq.java:40)
>> at clojure.lang.LazySeq.seq(LazySeq.java:49)
>> at clojure.lang.RT.seq(RT.java:507)
>> at clojure.core$seq__4128.invoke(core.clj:137)
>> at clojure.core.protocols$seq_reduce.invoke(protocols.clj:30)
>> at clojure.core.protocols$fn__6506.invoke(protocols.clj:101)
>> at clojure.core.protocols$fn__645
>> 2$G__6447__6465.invoke(protocols.clj:13)
>> at clojure.core$reduce.invoke(core.clj:6519)
>> at puppetlabs.trapperkeeper.boots
>> trap$eval14944$remove_duplicate_entries__14949$fn__14950.
>> invoke(bootstrap.clj:284)
>> at puppetlabs.trapperkeeper.boots
>> trap$eval14944$remove_duplicate_entries__14949.invoke(bootstrap.clj:263)
>> at puppetlabs.trapperkeeper.boots
>> trap$eval14970$parse_bootstrap_configs_BANG___14977$fn__
>> 14978.invoke(bootstrap.clj:304)
>> at puppetlabs.trapperkeeper.boots
>> trap$eval14970$parse_bootstrap_configs_BANG___14977.invoke(
>> bootstrap.clj:293)
>> at puppetlabs.trapperkeeper.core$
>> eval15252$boot_with_cli_data__15259$fn__15260.invoke(core.clj:129)
>> at puppetlabs.trapperkeeper.core$
>> eval15252$boot_with_cli_data__15259.invoke(core.clj:95)
>> at puppetlabs.trapperkeeper.core$
>> eval15281$run__15286$fn__15287.invoke(core.clj:151)
>> at puppetlabs.trapperkeeper.core$
>> eval15281$run__15286.invoke(core.clj:145)
>> at puppetlabs.trapperkeeper.core$main.doInvoke(core.clj:173)
>> at clojure.lang.RestFn.invoke(RestFn.java:457)
>> at clojure.lang.Var.invoke(Var.java:394)
>> at clojure.lang.AFn.applyToHelper(AFn.java:165)
>> at clojure.lang.Var.applyTo(Var.java:700)
>> at clojure.core$apply.invoke(core.clj:630)
>> at puppetlabs.trapperkeeper.main$_main.doInvoke(main.clj:7)
>> at clojure.lang.RestFn.invoke(RestFn.java:457)
>> at clojure.lang.Var.invoke(Var.java:394)
>> at clojure.lang.AFn.applyToHelper(AFn.java:165)
>> at clojure.lang.Var.applyTo(Var.java:700)
>> 

Re: [Puppet Users] puppetserver error "Service ':CaService' not found" when following puppet install guide

[Matthaus Owens]

AX,

In puppetserver 2.5.0 some changes went in with respect our bootstrap.cfg
config file. This change shouldn't affect fresh installs. It looks as
though you are missing /etc/puppetlabs/puppetserver/services.d/ca.cfg,
which adds the CaService. ca.cfg should look like the following for a
puppet-server install that will also be a CA:
https://github.com/puppetlabs/puppetserver/blob/2.5.0/ezbake/config/services.d/ca.cfg

Also, for more details with respect to the bootstrap.cfg changes in 2.5.0,
here are the docs:
-
https://docs.puppet.com/puppetserver/2.5/release_notes.html#potential-breaking-issues-when-upgrading-with-a-modified-bootstrapcfg
- https://docs.puppet.com/puppetserver/2.5/bootstrap_upgrade_notes.html

Hope that helps,
Matthaus

On Fri, Aug 26, 2016 at 5:45 AM, Alex Xu  wrote:

> Hi all,
>
> I was following puppet install guide for puppet 4.6 puppetserver 2.5.
> After I installed puppetserver and puppet-agent from 
> puppetlabs-release-pc1-trusty.deb
> in a new Ubuntu 14.04 box.
>
> When I try running "puppet resource service puppetserver ensure=running",
> I got following error in /var/log/puppetlabs/puppetserver/puppetserver-
> daemon.log.
>
> Searched on google and there is nothing about CaService. Really appreciate
> any thoughts on this.
>
> Thanks,
> AX
>
>
> 20:20:10.470 [main] DEBUG puppetlabs.trapperkeeper.bootstrap - Loading
> bootstrap configs:
> /opt/puppetlabs/server/apps/puppetserver/config/services.d/bootstrap.cfg
> 20:20:12.653 [main] DEBUG org.eclipse.jetty.util.log - Logging to
> Logger[org.eclipse.jetty.util.log] via org.eclipse.jetty.util.log.Slf4jLog
> 20:20:12.658 [main] INFO  org.eclipse.jetty.util.log - Logging initialized
> @14082ms
> 20:20:12.942 [main] INFO  p.t.services.webserver.jetty9-core - Removing
> buggy security provider SunPKCS11-NSS version 1.7
> 20:20:17.010 [main] DEBUG puppetlabs.trapperkeeper.internal -
> Initializing lifecycle worker loop.
> 20:20:17.096 [main] ERROR puppetlabs.trapperkeeper.internal - Error
> during app buildup!
> java.lang.RuntimeException: Service ':CaService' not found
>  at puppetlabs.trapperkeeper.internal$handle_prismatic_
> exception_BANG_.invoke(internal.clj:98) ~[na:na]
>  at 
> puppetlabs.trapperkeeper.internal$instantiate$fn__13793.invoke(internal.clj:139)
> ~[na:na]
>  at puppetlabs.trapperkeeper.internal$instantiate.invoke(internal.clj:136)
> ~[na:na]
>  at puppetlabs.trapperkeeper.internal$eval14328$build_app_
> STAR___14337$fn__14338.invoke(internal.clj:542) ~[na:na]
>  at puppetlabs.trapperkeeper.internal$eval14328$build_app_
> STAR___14337.invoke(internal.clj:510) ~[na:na]
>  at puppetlabs.trapperkeeper.internal$eval14430$boot_
> services_STAR___14439$fn__14440$fn__14441.invoke(internal.clj:610)
> ~[na:na]
>  at puppetlabs.trapperkeeper.internal$eval14430$boot_
> services_STAR___14439$fn__14440.invoke(internal.clj:609) [na:na]
>  at puppetlabs.trapperkeeper.internal$eval14430$boot_
> services_STAR___14439.invoke(internal.clj:604) [na:na]
>  at puppetlabs.trapperkeeper.core$eval15252$boot_with_cli_data__
> 15259$fn__15260.invoke(core.clj:130) [na:na]
>  at 
> puppetlabs.trapperkeeper.core$eval15252$boot_with_cli_data__15259.invoke(core.clj:95)
> [na:na]
>  at 
> puppetlabs.trapperkeeper.core$eval15281$run__15286$fn__15287.invoke(core.clj:151)
> [na:na]
>  at puppetlabs.trapperkeeper.core$eval15281$run__15286.invoke(core.clj:145)
> [na:na]
>  at puppetlabs.trapperkeeper.core$main.doInvoke(core.clj:173) [na:na]
>  at clojure.lang.RestFn.invoke(RestFn.java:457)
> [puppet-server-release.jar:na]
>  at clojure.lang.Var.invoke(Var.java:394) [puppet-server-release.jar:na]
>  at clojure.lang.AFn.applyToHelper(AFn.java:165)
> [puppet-server-release.jar:na]
>  at clojure.lang.Var.applyTo(Var.java:700) [puppet-server-release.jar:na]
>  at clojure.core$apply.invoke(core.clj:630) [puppet-server-release.jar:na]
>  at puppetlabs.trapperkeeper.main$_main.doInvoke(main.clj:7)
> [puppet-server-release.jar:na]
>  at clojure.lang.RestFn.invoke(RestFn.java:457)
> [puppet-server-release.jar:na]
>  at clojure.lang.Var.invoke(Var.java:394) [puppet-server-release.jar:na]
>  at clojure.lang.AFn.applyToHelper(AFn.java:165)
> [puppet-server-release.jar:na]
>  at clojure.lang.Var.applyTo(Var.java:700) [puppet-server-release.jar:na]
>  at clojure.core$apply.invoke(core.clj:630) [puppet-server-release.jar:na]
>  at clojure.main$main_opt.invoke(main.clj:316)
> [puppet-server-release.jar:na]
>  at clojure.main$main.doInvoke(main.clj:421)
> [puppet-server-release.jar:na]
>  at clojure.lang.RestFn.invoke(RestFn.java:512)
> [puppet-server-release.jar:na]
>  at clojure.lang.Var.invoke(Var.java:409) [puppet-server-release.jar:na]
>  at clojure.lang.AFn.applyToHelper(AFn.java:178)
> [puppet-server-release.jar:na]
>  at clojure.lang.Var.applyTo(Var.java:700) [puppet-server-release.jar:na]
>  at clojure.main.main(main.java:37) [puppet-server-release.jar:na]
> 20:20:17.098 [main] DEBUG puppetlabs.trapperkeeper.core - Finished TK main
> 

Re: [Puppet Users] Puppet web server stops after being started

[Matthaus Owens]

Michael,
If you don't mind posting the contents of your auth.conf as well, that
could help in figuring out what is going on. It looks like there is a
problem with the contents of the file, but without seeing the file, it is
hard to know what specifically is wrong.

Thanks,
Matthaus

On Fri, Aug 5, 2016 at 8:41 AM, 'Michael Wildey' via Puppet Users <
puppet-users@googlegroups.com> wrote:

> Matthaus,
> I found that I renamed the auth.conf by mistake. Now I renamed it again
> and then I started the hole server again.
> After that I tried to start the server again in foreground. The output is
> attached.
>
> Now there is written "Finished TK main lifecycle, shutting down Clojure
> agent threads"
>
> I am getting confused. I've downloaded a bundle from puppet and now it
> wont work. I can't imagine what went wrong during the installation and I
> blive I am not the first one to install puppetserver on a VM. Especially
> after i already installed   it on an other VM.
>
>
> Hope you can help me her
> Michael
>
>
>
>
>
>
> Am Freitag, 5. August 2016 02:24:52 UTC+2 schrieb Matthaus Litteken:
>>
>> Michael,
>> The important bit of that log is the following:
>>
>> 2016-08-03 17:12:31,742 ERROR [async-dispatch-2] [p.t.internal] Error during 
>> service init!!!
>> java.lang.IllegalArgumentException: Missing authorization service 
>> configuration.
>>
>>
>> That indicates that  /etc/puppetlabs/puppetserver/conf.d/auth.conf 
>> (https://docs.puppet.com/puppetserver/2.4/config_file_auth.html) is empty or 
>> doesn't exist. The file that is laid down by default by our packages is 
>> here: 
>> https://github.com/puppetlabs/puppetserver/blob/master/ezbake/config/conf.d/auth.conf.
>>  If you drop that file into  /etc/puppetlabs/puppetserver/conf.d/auth.conf 
>> the service should start successfully. If not, attach the new log and I'd be 
>> happy to help debug further.
>>
>>
>> Hope that helps,
>>
>> -Matthaus
>>
>>
>> On Wed, Aug 3, 2016 at 8:17 AM, 'Michael Wildey' via Puppet Users <
>> puppet...@googlegroups.com> wrote:
>>
>>> Ok, I did it now in foreground, just like you told me.
>>> What I have done before is that I changed the webserver.conf just like
>>> it is described here >>https://docs.puppet.com/pupp
>>> etserver/latest/external_ca_configuration.html#web-server-configuration
>>> <<
>>>
>>> The output is attached.
>>>
>>> Thanks for your hep
>>>
>>>
>>> Michael
>>>
>>>
>>> Am Dienstag, 2. August 2016 18:25:39 UTC+2 schrieb Matthaus Litteken:

 Michael,

 One good way of troubleshooting this sort of thing is to use the
 foreground command. It will attempt to start the process but log everything
 to the console so it's easy to find. `/opt/puppetlabs/bin/puppetserver
 foreground` should do the right thing. If you can paste or gist the log
 output that would help a lot in figuring out what is going on.

 -Matthaus

 On Tue, Aug 2, 2016 at 7:11 AM, 'Michael Wildey' via Puppet Users <
 puppet...@googlegroups.com> wrote:

> I already set the RAM on 2 GB. That was the first thing I though. But
> still it shuts down the web server in less than a second.
> The Log said it is Initialzing, starting and shutting down the web
> server in 0,2 seconds. This is the only information I get from the
> puppetserver.log. Is there a other log I don't know by now where I can get
> more information about it?
>
>
> Am Freitag, 29. Juli 2016 22:03:58 UTC+2 schrieb Rob Nelson:
>>
>> You can check the logs of the puppetserver startup. A common reason
>> is that VMs have less RAM than the process expects to be allocated. You 
>> can
>> either increase the RAM or adjust the puppetserver settings to use less
>> RAM, with impact to the performance of course. See
>> https://docs.puppet.com/puppetserver/latest/install_from_
>> packages.html#system-requirements if that seems a likely cause.
>>
>>
>> Rob Nelson
>> rnel...@gmail.com
>>
>> On Fri, Jul 29, 2016 at 12:18 PM, 'Michael Wildey' via Puppet Users <
>> puppet...@googlegroups.com> wrote:
>>
>>> I installed an puppetserver just like ist is written in the manual
>>> https://docs.puppet.com/puppet/4.5/reference/index.html on Debian
>>> Jessie.
>>>
>>> My Problem is that as soon as I want to get a cert for an agent it
>>> says that the puppetserver doesn't listen on Port 8140.
>>> Now I found out that the web server stops immediately after being
>>> started, but I don't know why.
>>>
>>> Any help is welcome.
>>>
>>> --
>>> 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/93e0e0e8-2b10
>>> 

Re: [Puppet Users] Puppet web server stops after being started

[Matthaus Owens]

Michael,
The important bit of that log is the following:

2016-08-03 17:12:31,742 ERROR [async-dispatch-2] [p.t.internal] Error
during service init!!!
java.lang.IllegalArgumentException: Missing authorization service configuration.


That indicates that  /etc/puppetlabs/puppetserver/conf.d/auth.conf
(https://docs.puppet.com/puppetserver/2.4/config_file_auth.html) is
empty or doesn't exist. The file that is laid down by default by our
packages is here:
https://github.com/puppetlabs/puppetserver/blob/master/ezbake/config/conf.d/auth.conf.
If you drop that file into
/etc/puppetlabs/puppetserver/conf.d/auth.conf the service should start
successfully. If not, attach the new log and I'd be happy to help
debug further.


Hope that helps,

-Matthaus


On Wed, Aug 3, 2016 at 8:17 AM, 'Michael Wildey' via Puppet Users <
puppet-users@googlegroups.com> wrote:

> Ok, I did it now in foreground, just like you told me.
> What I have done before is that I changed the webserver.conf just like it
> is described here >>https://docs.puppet.com/puppetserver/latest/external_
> ca_configuration.html#web-server-configuration<<
>
> The output is attached.
>
> Thanks for your hep
>
>
> Michael
>
>
> Am Dienstag, 2. August 2016 18:25:39 UTC+2 schrieb Matthaus Litteken:
>>
>> Michael,
>>
>> One good way of troubleshooting this sort of thing is to use the
>> foreground command. It will attempt to start the process but log everything
>> to the console so it's easy to find. `/opt/puppetlabs/bin/puppetserver
>> foreground` should do the right thing. If you can paste or gist the log
>> output that would help a lot in figuring out what is going on.
>>
>> -Matthaus
>>
>> On Tue, Aug 2, 2016 at 7:11 AM, 'Michael Wildey' via Puppet Users <
>> puppet...@googlegroups.com> wrote:
>>
>>> I already set the RAM on 2 GB. That was the first thing I though. But
>>> still it shuts down the web server in less than a second.
>>> The Log said it is Initialzing, starting and shutting down the web
>>> server in 0,2 seconds. This is the only information I get from the
>>> puppetserver.log. Is there a other log I don't know by now where I can get
>>> more information about it?
>>>
>>>
>>> Am Freitag, 29. Juli 2016 22:03:58 UTC+2 schrieb Rob Nelson:

 You can check the logs of the puppetserver startup. A common reason is
 that VMs have less RAM than the process expects to be allocated. You can
 either increase the RAM or adjust the puppetserver settings to use less
 RAM, with impact to the performance of course. See
 https://docs.puppet.com/puppetserver/latest/install_
 from_packages.html#system-requirements if that seems a likely cause.


 Rob Nelson
 rnel...@gmail.com

 On Fri, Jul 29, 2016 at 12:18 PM, 'Michael Wildey' via Puppet Users <
 puppet...@googlegroups.com> wrote:

> I installed an puppetserver just like ist is written in the manual
> https://docs.puppet.com/puppet/4.5/reference/index.html on Debian
> Jessie.
>
> My Problem is that as soon as I want to get a cert for an agent it
> says that the puppetserver doesn't listen on Port 8140.
> Now I found out that the web server stops immediately after being
> started, but I don't know why.
>
> Any help is welcome.
>
> --
> 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/93e0e0e8-2b10-48ea-82c3-40fa8ec86d91%
> 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...@googlegroups.com.
>>> To view this discussion on the web visit https://groups.google.com/d/
>>> msgid/puppet-users/e2741ca6-5d04-4949-b214-4b11775c4d37%
>>> 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/695e4bc4-cc4f-4c96-98ef-5fa06705a53a%40googlegroups.com
> 

Re: [Puppet Users] Puppet web server stops after being started

[Matthaus Owens]

Michael,

One good way of troubleshooting this sort of thing is to use the foreground
command. It will attempt to start the process but log everything to the
console so it's easy to find. `/opt/puppetlabs/bin/puppetserver foreground`
should do the right thing. If you can paste or gist the log output that
would help a lot in figuring out what is going on.

-Matthaus

On Tue, Aug 2, 2016 at 7:11 AM, 'Michael Wildey' via Puppet Users <
puppet-users@googlegroups.com> wrote:

> I already set the RAM on 2 GB. That was the first thing I though. But
> still it shuts down the web server in less than a second.
> The Log said it is Initialzing, starting and shutting down the web server
> in 0,2 seconds. This is the only information I get from the
> puppetserver.log. Is there a other log I don't know by now where I can get
> more information about it?
>
>
> Am Freitag, 29. Juli 2016 22:03:58 UTC+2 schrieb Rob Nelson:
>>
>> You can check the logs of the puppetserver startup. A common reason is
>> that VMs have less RAM than the process expects to be allocated. You can
>> either increase the RAM or adjust the puppetserver settings to use less
>> RAM, with impact to the performance of course. See
>> https://docs.puppet.com/puppetserver/latest/install_from_packages.html#system-requirements
>> if that seems a likely cause.
>>
>>
>> Rob Nelson
>> rnel...@gmail.com
>>
>> On Fri, Jul 29, 2016 at 12:18 PM, 'Michael Wildey' via Puppet Users <
>> puppet...@googlegroups.com> wrote:
>>
>>> I installed an puppetserver just like ist is written in the manual
>>> https://docs.puppet.com/puppet/4.5/reference/index.html on Debian
>>> Jessie.
>>>
>>> My Problem is that as soon as I want to get a cert for an agent it says
>>> that the puppetserver doesn't listen on Port 8140.
>>> Now I found out that the web server stops immediately after being
>>> started, but I don't know why.
>>>
>>> Any help is welcome.
>>>
>>> --
>>> 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/93e0e0e8-2b10-48ea-82c3-40fa8ec86d91%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/e2741ca6-5d04-4949-b214-4b11775c4d37%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/CACD%3DwAcYOiZDO4wjyt9UQ1QN5DC2owB9dEWc3Fa2%2B93XRp9-Tg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] running puppetdb on Centos 7

[Matthaus Owens]

mjr,

The tl;dr is that you need to upgrade nss on your system. Running `yum
update nss` should take care of the problem.

The most recent java updates on centos 7 were built against a newer version
of nss, but the Requires on the packages were not updated to account for
this, and so some java calls have started failing. There is a bugzilla
ticket open here https://bugzilla.redhat.com/show_bug.cgi?id=1332456 that
is tracking the issue. It looks like they (Redhat/CentOS) are rebuilding
java to update the Requires to take into account the new nss version, but I
only see rebuilds for Fedora 23/24 in that ticket. We have a ticket
tracking this internally here:
https://tickets.puppetlabs.com/browse/SERVER-1456, it has some more details
as well as a few more upstream distro tickets to watch.

Hope that helps,
Matthaus

On Mon, Aug 1, 2016 at 9:36 AM, Mark  wrote:

> Hello,
>
> I'm trying to transition from Centos 6 to Centos 7 for my puppet master. I
> have some custom modules that set up puppetmaster and puppetdb. Puppetdb
> seems to be having issues and I'm not sure why. I'm running puppetdb using
> postgresql. I've created the user and can confirm that the user hass access
> to the database however nothing is being initialized in postgres. So if I
> connect to the puppetdb database nothing is there.
>
> I've run puppetdb in the forground and got the following error (this is
> puppetdb 2.3.0 using Java 1.7 on Centos 7)
>
> # puppetdb foreground --debug
> Exception in thread "main" java.lang.InternalError,
> compiling:(digest.clj:85:30)
> at clojure.lang.Compiler.load(Compiler.java:7142)
> at clojure.lang.RT.loadResourceScript(RT.java:370)
> at clojure.lang.RT.loadResourceScript(RT.java:361)
> at clojure.lang.RT.load(RT.java:440)
> at clojure.lang.RT.load(RT.java:411)
> at clojure.core$load$fn__5066.invoke(core.clj:5641)
> at clojure.core$load.doInvoke(core.clj:5640)
> at clojure.lang.RestFn.invoke(RestFn.java:408)
> at clojure.core$load_one.invoke(core.clj:5446)
> at clojure.core$load_lib$fn__5015.invoke(core.clj:5486)
> at clojure.core$load_lib.doInvoke(core.clj:5485)
> at clojure.lang.RestFn.applyTo(RestFn.java:142)
> at clojure.core$apply.invoke(core.clj:626)
> at clojure.core$load_libs.doInvoke(core.clj:5524)
> at clojure.lang.RestFn.applyTo(RestFn.java:137)
> at clojure.core$apply.invoke(core.clj:626)
> at clojure.core$require.doInvoke(core.clj:5607)
> at clojure.lang.RestFn.invoke(RestFn.java:551)
> at
> puppetlabs.kitchensink.core$eval9$loading__4958__auto10.invoke(core.clj:7)
> at puppetlabs.kitchensink.core$eval9.invoke(core.clj:7)
> at clojure.lang.Compiler.eval(Compiler.java:6703)
> at clojure.lang.Compiler.eval(Compiler.java:6692)
> at clojure.lang.Compiler.load(Compiler.java:7130)
> at clojure.lang.RT.loadResourceScript(RT.java:370)
> at clojure.lang.RT.loadResourceScript(RT.java:361)
> at clojure.lang.RT.load(RT.java:440)
> at clojure.lang.RT.load(RT.java:411)
> at clojure.core$load$fn__5066.invoke(core.clj:5641)
> at clojure.core$load.doInvoke(core.clj:5640)
> at clojure.lang.RestFn.invoke(RestFn.java:408)
> at clojure.core$load_one.invoke(core.clj:5446)
> at clojure.core$load_lib$fn__5015.invoke(core.clj:5486)
> at clojure.core$load_lib.doInvoke(core.clj:5485)
> at clojure.lang.RestFn.applyTo(RestFn.java:142)
> at clojure.core$apply.invoke(core.clj:626)
> at clojure.core$load_libs.doInvoke(core.clj:5524)
> at clojure.lang.RestFn.applyTo(RestFn.java:137)
> at clojure.core$apply.invoke(core.clj:626)
> at clojure.core$require.doInvoke(core.clj:5607)
> at clojure.lang.RestFn.invoke(RestFn.java:482)
> at
> com.puppetlabs.puppetdb.core$eval3$loading__4958__auto4.invoke(core.clj:14)
> at com.puppetlabs.puppetdb.core$eval3.invoke(core.clj:14)
> at clojure.lang.Compiler.eval(Compiler.java:6703)
> at clojure.lang.Compiler.eval(Compiler.java:6692)
> at clojure.lang.Compiler.load(Compiler.java:7130)
> at clojure.lang.RT.loadResourceScript(RT.java:370)
> at clojure.lang.RT.loadResourceScript(RT.java:361)
> at clojure.lang.RT.load(RT.java:440)
> at clojure.lang.RT.load(RT.java:411)
> at clojure.core$load$fn__5066.invoke(core.clj:5641)
> at clojure.core$load.doInvoke(core.clj:5640)
> at clojure.lang.RestFn.invoke(RestFn.java:408)
> at clojure.core$load_one.invoke(core.clj:5446)
> at clojure.core$load_lib$fn__5015.invoke(core.clj:5486)
> at clojure.core$load_lib.doInvoke(core.clj:5485)
> at clojure.lang.RestFn.applyTo(RestFn.java:142)
> at clojure.core$apply.invoke(core.clj:626)
> at 

Re: [Puppet Users] Re: control-repo how to use the profile setup

[Matthaus Owens]

Alex,

It looks like puppetlabs/java has a defined type to handle getting the
oracle version of java (https://forge.puppet.com/puppetlabs/java#usage).
The link has some examples of using the defined type to install oracle java
6 and oracle java 8.

HTH

On Mon, Jul 11, 2016 at 5:00 PM, Alex Samad  wrote:

> Ta
>
> but !  I don't want to use the rpm / package from the distro (Centos), I
> want to use the one from oracle. I had hoped to use puppet for storing
> that. I have a repo setup and could add it there.
>
> It was a 2 part question, 1 to solve the package problem, the other how to
> use the download from puppet web site. I remember from the training module
> you can store files in classes
>
> A
>
>
>
>
> On Monday, 11 July 2016 23:56:08 UTC+10, aar...@bigmirrorlabs.com wrote:
>>
>>
>> New to puppet here, but I used this to handle my java dependency.
>>
>> https://forge.puppet.com/puppetlabs/java
>>
>>
>>
>> --
> 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/fae84d50-ed98-4c5e-8cd5-c5c43bb88bd2%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/CACD%3DwAcYKRuK3NnBcDWJ74ShKY8ZO6t6U%3D%3DvLr%3D9nHrFbYE2yA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Broken puppetdb

[Matthaus Owens]

It seems like you still have some puppetdb settings in puppet.conf, like
fact_terminus for example. I'd look there before uninstalling the packages.

HTH

On Saturday, June 11, 2016, Zeke Dehnert  wrote:

> Hmm, I grepped for puppetdb in all of the puppet config files and all the
> files in puppeserver/conf.d and removed any reference to puppetdb from all
> of them.  O also made sure that puppetdb and postgres don’t start after a
> reboot, then i rebooted the puppet server systemm, and my clients are still
> getting the following message:
>
> Error: Could not retrieve catalog from remote server: Error 400 on SERVER:
> Failed to execute
> '/pdb/cmd/v1?checksum=f6be4a58649c171db656ecbc791fc023ac1b0208=4=
> it-lnx-01.myhost.com=replace_facts' on at least 1 of the
> following 'server_urls': https://puppetmaster.myhost.com:8081
> Warning: Not using cache on failed catalog
>
> I’m totally at a loss.  Should I uninstall puppetdb, puppet-termini, and
> postgres?  I was thinking about doing that to help get a clean install,
> then later I was going to make a copy of this server, and try installing
> puppetdb and postgres on the copy.  The bummer of this is it was all
> working before I tried to switch to the “Recommended” puppet labs modules.
>
> From: Trevor Vaughan 
> 
> Reply: puppet-users@googlegroups.com
> 
> 
> 
> Date: June 11, 2016 at 3:10:26 PM
> To: puppet-users@googlegroups.com
> 
> 
> 
> Subject:  Re: [Puppet Users] Broken puppetdb
>
> That still looks like your server is trying to send things to PuppetDB.
>
> Check the puppet.conf and grep for puppetdb in your puppet and puppet
> server configuration settings and make sure it's been removed.
>
> Also, fully restart your puppetserver process. An API hit won't do the job.
>
> Trevor
>
> --
> Thanks,
>James “Zeke” Dehnert
>
> *Enphase Energy*  |  Senior Linux Administrator
>
>
>
> (707)763.4787 x7636  // Office
>
> GPG Fingerprint: E899 A10A 960D 4B6C 22D2 8FC2 EA5E4E81
> The information contained in this message may be privileged and
> confidential. It is intended to be read only by the individual or entity to
> whom it is addressed or by their designee. If the reader of this message is
> not the intended recipient, you are on notice that any distribution of this
> message, in any form, is strictly prohibited. If you have received this
> message in error, please immediately notify the sender and delete or
> destroy any copy of this message!
>
> --
> 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/etPan.575c954b.1f0068d6.1b4d%40enphaseenergy.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/CACD%3DwAdvwOxLLr6nK4SW4Vh7XrBEypmXVMuZ0KfT63cbUX8vmQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Packaging scripts for Puppetlabs Vagrant images?

[Matthaus Owens]

Ben,
I think https://github.com/puppetlabs/puppetlabs-packer is what you are
looking for.

HTH

On Wed, Jun 8, 2016 at 9:54 AM, Ben West  wrote:

> I was hoping to test out CentOS v6.8, but the Puppetlabs Vagrant images
> published only go up to v6.6:
> https://atlas.hashicorp.com/puppetlabs
>
> Is there a repo, or other such info somewhere, providing details about how
> these images are rolled?  I.e. so I could create my own CentOS v6.8 image
> to test against?
>
> Thank you.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/e8c2548a-7674-4a4c-85ee-9d09a566fe01%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/CACD%3DwAeaqokUFq5pS%3DYAQMbaP_1UxU93TzUHv4Oh%3DX6o-_vuTA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Outofmemory error for puppetserver process

[Matthaus Owens]

Jim,

What do you consider clean state of process listing? Puppetserver is run
with those options in many production environments.

It certainly is possible to change how puppetserver starts up, but I
wouldn't recommend it. The OnOutOfMemoryError setting is there so that when
such an error occurs, the process comes down right away without attempting
any recovery (you can see https://tickets.puppetlabs.com/browse/SERVER-1368
for more details about this).
If you do want to change how puppetserver starts up, you'll probably want
to setup an override for the ExecStart of puppetserver.
http://askubuntu.com/questions/659267/how-do-i-override-or-configure-systemd-services
has some details on how to do this.

HTH

On Tue, May 31, 2016 at 7:37 AM, Jim  wrote:

> Hi Matthaus,
>
> Assume its a production environment would we have allowed that ? What I'm
> interested in clean state of process listing when I run ps command.
>
> Is that possible?
>
> Regards,
> Jim
>
> On Tuesday, 31 May 2016 01:07:39 UTC+10, Matthaus Litteken wrote:
>>
>> Jim,
>>
>> The 'XX:OnOutOfMemoryError=kill -9 %p' in the process list doesn't
>> indicate that puppet server is out of memory, it is a Java flag that tells
>> Java what to do if puppet server hits an outofmemory error. The output you
>> have pasted looks totally normal to me.
>>
>> HTH
>>
>> On Monday, May 30, 2016, Jim  wrote:
>>
>>> Hi Matthaus,
>>>
>>> My hostname is misleading. I upgraded at the time of posting to Ubuntu
>>> 15.10. Now I have upgraded to 16.04.
>>>
>>> I ran the command you suggested instead of service puppetserver start
>>> and I don't see OutOfMemory errors process.
>>>
>>> root@jim-Ubuntu1504:~# ps -aef|grep -i puppet|grep -v grep
>>> root  1116 1  0 19:34 ?00:00:02
>>> /opt/puppetlabs/puppet/bin/ruby /opt/puppetlabs/puppet/bin/puppet agent
>>> --no-daemonize
>>> root  1719 1  0 19:38 ?00:00:08
>>> /opt/puppetlabs/puppet/bin/ruby /opt/puppetlabs/puppet/bin/mcollectived
>>> --config=/etc/puppetlabs/mcollective/server.cfg
>>> --pidfile=/var/run/puppetlabs/mcollective.pid --daemonize
>>> root  2644  1544  0 22:35 pts/000:00:00 bash
>>> /opt/puppetlabs/server/apps/puppetserver/cli/apps/foreground
>>> root  2650  2644  0 22:35 pts/000:00:00 runuser puppet -s
>>> /bin/bash -c /usr/bin/java -Xms512m -Xmx512m -XX:MaxPermSize=512m
>>> -Dlogappender=STDOUT  -cp
>>> /opt/puppetlabs/server/apps/puppetserver/puppet-server-release.jar
>>>  clojure.main -m puppetlabs.trapperkeeper.main  --config
>>> /etc/puppetlabs/puppetserver/conf.d --bootstrap-config
>>> /etc/puppetlabs/puppetserver/bootstrap.cfg
>>> puppet2651  2650 55 22:35 ?00:00:42 /usr/bin/java -Xms512m
>>> -Xmx512m -XX:MaxPermSize=512m -Dlogappender=STDOUT -cp
>>> /opt/puppetlabs/server/apps/puppetserver/puppet-server-release.jar
>>> clojure.main -m puppetlabs.trapperkeeper.main --config
>>> /etc/puppetlabs/puppetserver/conf.d --bootstrap-config
>>> /etc/puppetlabs/puppetserver/bootstrap.cfg
>>> root@jim-Ubuntu1504:~#
>>>
>>>
>>> Also when I do see that error as like below when I do Ctrl + C and
>>> execute service puppetserver start I get the OutOfMemory error like below.
>>>
>>> root@jim-Ubuntu1504:~# ps -aef|grep -i puppet|grep -v grep
>>> root  1116 1  0 19:34 ?00:00:02
>>> /opt/puppetlabs/puppet/bin/ruby /opt/puppetlabs/puppet/bin/puppet agent
>>> --no-daemonize
>>> root  1719 1  0 19:38 ?00:00:08
>>> /opt/puppetlabs/puppet/bin/ruby /opt/puppetlabs/puppet/bin/mcollectived
>>> --config=/etc/puppetlabs/mcollective/server.cfg
>>> --pidfile=/var/run/puppetlabs/mcollective.pid --daemonize
>>> puppet3386 1 66 22:41 ?00:00:45 /usr/bin/java
>>> -XX:OnOutOfMemoryError=kill -9 %p -Djava.security.egd=/dev/urandom -Xms512m
>>> -Xmx512m -XX:MaxPermSize=512m -cp
>>> /opt/puppetlabs/server/apps/puppetserver/puppet-server-release.jar
>>> clojure.main -m puppetlabs.trapperkeeper.main --config
>>> /etc/puppetlabs/puppetserver/conf.d -b
>>> /etc/puppetlabs/puppetserver/bootstrap.cfg
>>> root@jim-Ubuntu1504:~#
>>>
>>> I wonder if I am doing start-up incorrectly ? Either even in this state
>>> where it sayOutOfMemoryError my puppetserver still serves all of its
>>> agents. The reason I say so is I changed motd file on all agents +
>>> installed vim package on agents.
>>>
>>> I am not sure which is the right method to start the server ? Also
>>> instead of running in foreground can I run it in background using nohup ?
>>>
>>> Regards,
>>> Jim
>>>
>>>
>>> On Friday, 27 May 2016 02:46:14 UTC+10, Matthaus Litteken wrote:

 Jim,
 For debugging failures on ubuntu 15.04, I would recommend trying
 `/opt/puppetlabs/bin/puppetserver foreground`, it may show you the errors
 that are causing the service to shutdown. Ubuntu 15.04 is a bit difficult
 to debug on, because while it has systemd support, the puppetserver
 packages for that platform still 

Re: [Puppet Users] Outofmemory error for puppetserver process

[Matthaus Owens]

Jim,

The 'XX:OnOutOfMemoryError=kill -9 %p' in the process list doesn't indicate
that puppet server is out of memory, it is a Java flag that tells Java what
to do if puppet server hits an outofmemory error. The output you have
pasted looks totally normal to me.

HTH

On Monday, May 30, 2016, Jim  wrote:

> Hi Matthaus,
>
> My hostname is misleading. I upgraded at the time of posting to Ubuntu
> 15.10. Now I have upgraded to 16.04.
>
> I ran the command you suggested instead of service puppetserver start and
> I don't see OutOfMemory errors process.
>
> root@jim-Ubuntu1504:~# ps -aef|grep -i puppet|grep -v grep
> root  1116 1  0 19:34 ?00:00:02
> /opt/puppetlabs/puppet/bin/ruby /opt/puppetlabs/puppet/bin/puppet agent
> --no-daemonize
> root  1719 1  0 19:38 ?00:00:08
> /opt/puppetlabs/puppet/bin/ruby /opt/puppetlabs/puppet/bin/mcollectived
> --config=/etc/puppetlabs/mcollective/server.cfg
> --pidfile=/var/run/puppetlabs/mcollective.pid --daemonize
> root  2644  1544  0 22:35 pts/000:00:00 bash
> /opt/puppetlabs/server/apps/puppetserver/cli/apps/foreground
> root  2650  2644  0 22:35 pts/000:00:00 runuser puppet -s
> /bin/bash -c /usr/bin/java -Xms512m -Xmx512m -XX:MaxPermSize=512m
> -Dlogappender=STDOUT  -cp
> /opt/puppetlabs/server/apps/puppetserver/puppet-server-release.jar
>  clojure.main -m puppetlabs.trapperkeeper.main  --config
> /etc/puppetlabs/puppetserver/conf.d --bootstrap-config
> /etc/puppetlabs/puppetserver/bootstrap.cfg
> puppet2651  2650 55 22:35 ?00:00:42 /usr/bin/java -Xms512m
> -Xmx512m -XX:MaxPermSize=512m -Dlogappender=STDOUT -cp
> /opt/puppetlabs/server/apps/puppetserver/puppet-server-release.jar
> clojure.main -m puppetlabs.trapperkeeper.main --config
> /etc/puppetlabs/puppetserver/conf.d --bootstrap-config
> /etc/puppetlabs/puppetserver/bootstrap.cfg
> root@jim-Ubuntu1504:~#
>
>
> Also when I do see that error as like below when I do Ctrl + C and execute
> service puppetserver start I get the OutOfMemory error like below.
>
> root@jim-Ubuntu1504:~# ps -aef|grep -i puppet|grep -v grep
> root  1116 1  0 19:34 ?00:00:02
> /opt/puppetlabs/puppet/bin/ruby /opt/puppetlabs/puppet/bin/puppet agent
> --no-daemonize
> root  1719 1  0 19:38 ?00:00:08
> /opt/puppetlabs/puppet/bin/ruby /opt/puppetlabs/puppet/bin/mcollectived
> --config=/etc/puppetlabs/mcollective/server.cfg
> --pidfile=/var/run/puppetlabs/mcollective.pid --daemonize
> puppet3386 1 66 22:41 ?00:00:45 /usr/bin/java
> -XX:OnOutOfMemoryError=kill -9 %p -Djava.security.egd=/dev/urandom -Xms512m
> -Xmx512m -XX:MaxPermSize=512m -cp
> /opt/puppetlabs/server/apps/puppetserver/puppet-server-release.jar
> clojure.main -m puppetlabs.trapperkeeper.main --config
> /etc/puppetlabs/puppetserver/conf.d -b
> /etc/puppetlabs/puppetserver/bootstrap.cfg
> root@jim-Ubuntu1504:~#
>
> I wonder if I am doing start-up incorrectly ? Either even in this state
> where it sayOutOfMemoryError my puppetserver still serves all of its
> agents. The reason I say so is I changed motd file on all agents +
> installed vim package on agents.
>
> I am not sure which is the right method to start the server ? Also instead
> of running in foreground can I run it in background using nohup ?
>
> Regards,
> Jim
>
>
> On Friday, 27 May 2016 02:46:14 UTC+10, Matthaus Litteken wrote:
>>
>> Jim,
>> For debugging failures on ubuntu 15.04, I would recommend trying
>> `/opt/puppetlabs/bin/puppetserver foreground`, it may show you the errors
>> that are causing the service to shutdown. Ubuntu 15.04 is a bit difficult
>> to debug on, because while it has systemd support, the puppetserver
>> packages for that platform still ship sysv init scripts. In my experience,
>> the sysv-systemd integration seems to swallow some startup errors and
>> messages that would usually go to journalctl on a systemd platform. We
>> started shipping systemd service files for puppetserver starting in Ubuntu
>> 16.04.
>>
>> HTH
>>
>> On Thu, May 26, 2016 at 6:56 AM, Jim  wrote:
>>
>>> Hi Trevor,
>>>
>>> No luck.
>>>
>>> 2016-05-26 23:46:26,745 INFO  [Thread-1] [p.t.internal] Shutting down
>>> due to JVM shutdown hook.
>>> 2016-05-26 23:46:26,747 INFO  [Thread-1] [p.t.internal] Beginning
>>> shutdown sequence
>>> 2016-05-26 23:46:26,761 INFO  [clojure-agent-send-pool-1]
>>> [p.s.j.jruby-puppet-agents] Flush request received; creating new JRuby pool.
>>> 2016-05-26 23:46:26,765 INFO  [clojure-agent-send-pool-1]
>>> [p.s.j.jruby-puppet-agents] Replacing old JRuby pool with new instance.
>>> 2016-05-26 23:46:26,765 INFO  [clojure-agent-send-pool-1]
>>> [p.s.j.jruby-puppet-agents] Swapped JRuby pools, beginning cleanup of old
>>> pool.
>>> 2016-05-26 23:46:26,770 INFO  [clojure-agent-send-pool-1]
>>> [p.s.j.jruby-puppet-internal] Cleaned up old JRuby instance with id 1.
>>> 2016-05-26 23:46:26,772 INFO  [Thread-1] [p.t.s.w.jetty9-service]
>>> 

Re: [Puppet Users] Outofmemory error for puppetserver process

[Matthaus Owens]

Jim,
For debugging failures on ubuntu 15.04, I would recommend trying
`/opt/puppetlabs/bin/puppetserver foreground`, it may show you the errors
that are causing the service to shutdown. Ubuntu 15.04 is a bit difficult
to debug on, because while it has systemd support, the puppetserver
packages for that platform still ship sysv init scripts. In my experience,
the sysv-systemd integration seems to swallow some startup errors and
messages that would usually go to journalctl on a systemd platform. We
started shipping systemd service files for puppetserver starting in Ubuntu
16.04.

HTH

On Thu, May 26, 2016 at 6:56 AM, Jim  wrote:

> Hi Trevor,
>
> No luck.
>
> 2016-05-26 23:46:26,745 INFO  [Thread-1] [p.t.internal] Shutting down due
> to JVM shutdown hook.
> 2016-05-26 23:46:26,747 INFO  [Thread-1] [p.t.internal] Beginning shutdown
> sequence
> 2016-05-26 23:46:26,761 INFO  [clojure-agent-send-pool-1]
> [p.s.j.jruby-puppet-agents] Flush request received; creating new JRuby pool.
> 2016-05-26 23:46:26,765 INFO  [clojure-agent-send-pool-1]
> [p.s.j.jruby-puppet-agents] Replacing old JRuby pool with new instance.
> 2016-05-26 23:46:26,765 INFO  [clojure-agent-send-pool-1]
> [p.s.j.jruby-puppet-agents] Swapped JRuby pools, beginning cleanup of old
> pool.
> 2016-05-26 23:46:26,770 INFO  [clojure-agent-send-pool-1]
> [p.s.j.jruby-puppet-internal] Cleaned up old JRuby instance with id 1.
> 2016-05-26 23:46:26,772 INFO  [Thread-1] [p.t.s.w.jetty9-service] Shutting
> down web server(s).
> 2016-05-26 23:46:26,781 INFO  [Thread-1] [p.t.s.w.jetty9-core] Shutting
> down web server.
> 2016-05-26 23:46:26,824 INFO  [Thread-1] [o.e.j.s.ServerConnector] Stopped
> ServerConnector@79303966{SSL-HTTP/1.1}{0.0.0.0:8140}
> 2016-05-26 23:46:26,824 INFO  [Thread-1] [o.e.j.s.h.ContextHandler]
> Stopped o.e.j.s.h.ContextHandler@2b87522b{/,null,UNAVAILABLE}
> 2016-05-26 23:46:26,824 INFO  [Thread-1] [o.e.j.s.h.ContextHandler]
> Stopped o.e.j.s.h.ContextHandler@1f2ffb51
> {/puppet-admin-api,null,UNAVAILABLE}
> 2016-05-26 23:46:26,824 INFO  [Thread-1] [o.e.j.s.h.ContextHandler]
> Stopped o.e.j.s.h.ContextHandler@609b2b8a{/puppet,null,UNAVAILABLE}
> 2016-05-26 23:46:26,825 INFO  [Thread-1] [o.e.j.s.h.ContextHandler]
> Stopped o.e.j.s.h.ContextHandler@5b1cbf6d{/puppet-ca,null,UNAVAILABLE}
> 2016-05-26 23:46:26,827 INFO  [Thread-1] [p.t.s.w.jetty9-core] Web server
> shutdown
> 2016-05-26 23:46:26,837 INFO  [Thread-1] [p.t.internal] Finished shutdown
> sequence
> 2016-05-26 23:49:33,878 INFO  [main] [o.e.j.u.log] Logging initialized
> @14524ms
> 2016-05-26 23:49:41,413 INFO  [async-dispatch-2]
> [p.s.v.versioned-code-service] No code-id-command set for
> versioned-code-service. Code-id will be nil.
> 2016-05-26 23:49:41,414 INFO  [async-dispatch-2]
> [p.s.v.versioned-code-service] No code-content-command set for
> versioned-code-service. Attempting to fetch code content will fail.
> 2016-05-26 23:49:41,417 INFO  [async-dispatch-2] [p.t.s.w.jetty9-service]
> Initializing web server(s).
> 2016-05-26 23:49:41,457 INFO  [async-dispatch-2]
> [p.s.j.jruby-puppet-service] Initializing the JRuby service
> 2016-05-26 23:49:41,457 WARN  [async-dispatch-2]
> [p.s.j.jruby-puppet-service] The 'jruby-puppet.use-legacy-auth-conf'
> setting is set to 'true'.  Support for the legacy Puppet auth.conf file is
> deprecated and will be removed in a future release.  Change this setting to
> 'false' and migrate your authorization rule definitions in the
> /etc/puppetlabs/puppet/auth.conf file to the
> /etc/puppetlabs/puppetserver/conf.d/auth.conf file.
> 2016-05-26 23:49:41,500 INFO  [clojure-agent-send-pool-0]
> [p.s.j.jruby-puppet-internal] Creating JRuby instance with id 1.
> 2016-05-26 23:49:58,448 INFO  [clojure-agent-send-pool-0] [puppet-server]
> Puppet Puppet settings initialized; run mode: master
> 2016-05-26 23:49:59,624 INFO  [clojure-agent-send-pool-0]
> [p.s.j.jruby-puppet-agents] Finished creating JRubyPuppet instance 1 of 1
> 2016-05-26 23:49:59,636 INFO  [async-dispatch-2]
> [p.s.c.puppet-server-config-core] Initializing webserver settings from core
> Puppet
> 2016-05-26 23:49:59,672 INFO  [async-dispatch-2]
> [p.p.certificate-authority] CA already initialized for SSL
> 2016-05-26 23:49:59,674 INFO  [async-dispatch-2]
> [p.s.c.certificate-authority-service] CA Service adding a ring handler
> 2016-05-26 23:49:59,749 INFO  [async-dispatch-2]
> [p.p.certificate-authority] Master already initialized for SSL
> 2016-05-26 23:49:59,750 INFO  [async-dispatch-2] [p.s.m.master-service]
> Master Service adding ring handlers
> 2016-05-26 23:49:59,813 INFO  [async-dispatch-2]
> [p.s.p.puppet-admin-service] Starting Puppet Admin web app
> 2016-05-26 23:49:59,844 WARN  [async-dispatch-2]
> [o.e.j.s.h.ContextHandler] Empty contextPath
> 2016-05-26 23:49:59,849 INFO  [async-dispatch-2] [p.t.s.w.jetty9-service]
> Starting web server(s).
> 2016-05-26 23:49:59,868 INFO  [async-dispatch-2] [p.t.s.w.jetty9-core]
> webserver config overridden for 

Re: [Puppet Users] Re: Logrotate module broken, string 'undef' now treated as undef

[Matthaus Owens]

Daniel,
Thanks for filing the ticket. I'll take a stab at reproducing it today. Did
you only see it with puppet runs against a master, or also with local
puppet apply?

On Fri, May 20, 2016 at 8:20 AM, Daniel Urist  wrote:

> I filed a bug: https://tickets.puppetlabs.com/browse/SERVER-1356
>
> On Fri, May 20, 2016 at 6:41 AM, JeremyCampbell <
> jeremycampbel...@gmail.com> wrote:
>
>> I can confirm the same issue on Puppetserver v2.4.0
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Puppet Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to puppet-users+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/puppet-users/62c4f502-e46b-4cef-9fc6-71767eb1d5c3%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/CAEo6%3DKaa43cJg%3Daddt%2B%3DTR1%2B%2BH0C8vm2eAmvYUevcqPuNkHNfg%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/CACD%3DwAfyDLQuTgOjF_UbLYB24g9KAnLYVmYybDGe6vL_iHrzdw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Logrotate module broken, string 'undef' now treated as undef

[Matthaus Owens]

Daniel,
Which version of Puppet are you seeing this on?

On Wed, May 18, 2016 at 2:33 PM, Daniel Urist  wrote:

> I have been using the yo61 logrotate module from puppetforge (
> https://forge.puppet.com/yo61/logrotate), which seems to be the most
> popular, but it recently stopped working, with many errors about undefined
> parameters.
>
> The issue seems to be the use of the string 'undef' as a default value;
> for example:
>
> define logrotate::rule(
>> $create_owner   = 'undef',
>>
>
> Later on in the code, there are comparisons against the actual string
> 'undef'; for example:
>
>
>   if ($create_owner != 'undef') and ($create_mode == 'undef') {
>> fail("Logrotate::Rule[${name}]: create_owner requires create_mode")
>>}
>
>
> Regardless of whether this is best practice, these comparisons are now
> failing, apparently because the string 'undef' is now treated as the value
> undef. I've confirmed this by printing the string with notify (prints
> nothing when it's 'undef'), and changing it to something else, which does
> print.
>
> I'm not sure exactly when this changed or if it's intended behavior or a
> bug, but it does seem odd that now apparently 'undef' === undef
>
> --
> 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/CAEo6%3DKYjAx286r9NNvKtGU3PscrAZ77H5_HXc9CXO1LLa552sg%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/CACD%3DwAcwR0OdVsPguNNzzeqZ_LUHMoLhAyhTJP56bAZDc0J6Jw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Puppetserver package for Ubuntu Xenial not yet available?

[Matthaus Owens]

Martijn,
Yes, there is a plan for releasing Xenial packages. There are puppetserver
and puppetdb releases tentatively planned for tomorrow that will contain
Xenial support.

On Wed, May 18, 2016 at 7:23 AM, Martijn  wrote:

> I'm setting up a new Puppet 4 Server and wanted to start from the newest
> Ubuntu Xenial (16.04) LTS. After installing the
> http://apt.puppetlabs.com/puppetlabs-release-pc1-xenial.deb package I
> noticed the puppetserver package is not yet present in the repo.
>
> I can start with Ubuntu Trusty for now, but is there any planning on the
> availability of a full Xenial setup?
>
> Thanks for the hard work!
>
> Regards, Martijn
>
> --
> 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/2a3f1614-6083-4f22-a805-e60f805575e8%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/CACD%3DwAfhnPT5OXc7EepiJ_ZxkZpWPQu_fyxnr6BmaJB%2B2xwjwg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Puppet Enterprise install URL can not be Accessed

[Matthaus Owens]

Chris,
My first guess would be that your centos 7 machine is firewalled. You may
need to open port 3000 for the install to succeed.
http://stackoverflow.com/questions/24729024/centos-7-open-firewall-port
came up first in a quick search for handling firewall rules in centos 7.

HTH

On Fri, Apr 29, 2016 at 5:50 AM, Christopher Hampton <
c.j.hampton032...@gmail.com> wrote:

> I am building out a Puppet Enterprise Install for a demo lab for work.  I
> am using CentOS 7.  I can download the Tarball and expand it.  Then start
> the installer but when I go to use the URL from another system it is not
> visible.  Does anyone know what is blocking the Web Install UI?
>
> Thanks,
>
> Chris
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/2870a7b0-f1c4-449f-b912-9a265d588401%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/CACD%3DwAdpjFiQoaZ1%2BYDFFZjP0swnhhdC11RXCtW06h0nVPDN8w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] apt-get install puppetserver fails with error: packages have unmet dependencies: Depends: puppet-common (>= 3.7.3-1puppetlabs1) but 3.7.0-1puppetlabs1 is to be installed Depends: pu

[Matthaus Owens]

There are a couple of possibilities for what could be going on. First, I
don't see any calls to `apt-get update`. After adding a new apt source
running `apt-get update` is needed for apt to find any new packages in that
repository.
The second possibility is that you have an apt-pin in place[1]. If you
could paste the output of `apt-cache policy puppet-common`, that would help
to see what is going on.

A side note here: if you are trying to install the latest version of puppet
and puppetserver, you'll want to be using the PC1 repos and not the main
repos. There is documentation for them available here:
https://docs.puppetlabs.com/guides/puppetlabs_package_repositories.html#apt-based-systems

[1] - http://jaqque.sbih.org/kplug/apt-pinning.html

HTH

On Tue, Feb 16, 2016 at 3:44 PM, Mamun Rashid <mamun...@gmail.com> wrote:

> I am trying to install puppet server on an ec2 ubuntu instance>
> --
>
> I get: ubuntu@ip-172-31-43-240:~$ sudo apt-get install puppetserver
>
>
> Reading package lists... Done Building dependency tree Reading state
> information... Done
>
> Some packages could not be installed.
>
> This may mean that you have requested an impossible situation or if you
> are using the unstable distribution that some required packages have not
> yet been created or been moved out of Incoming.
>
>
> The following information may help to resolve the situation:
>
> The following packages have unmet dependencies:
>
> puppetserver : Depends: puppet-common (>= 3.7.3-1puppetlabs1) but
> 3.7.0-1puppetlabs1 is to be installed
>
> Depends: puppet (>= 3.7.3-1puppetlabs1) but 3.7.0-1puppetlabs1 is to be
> installed
>
>
>  E: Unable to correct problems, you have held broken packages.
> ubuntu@ip-172-31-43-240:~$
> --
>
> BUT , I have
>
> ubuntu@ip-172-31-43-240:~$ sudo apt-get install puppet-common
>
>
> Reading package lists... Done Building dependency tree
>
> Reading state information... Done
>
> puppet-common is already the newest version. 0 upgraded, 0 newly
> installed, 0 to remove and 4 not upgraded.
>
> ubuntu@ip-172-31-43-240:~$
> --
>
>
> I got the package this way:
>
>  wget https://apt.puppetlabs.com/puppetlabs-release-trusty.deb
>
> sudo dpkg -i puppetlabs-release-trusty.deb
>
> sudo apt-get install puppetserver
>
> __
>
>
>
> I tried purging puppet-common and reinstalling it. I have also tried sudo
> apt-get upgrade.
>
> Any help will be appreciated. Thanks!!
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/99ec6c49-89ef-48f0-907e-4b4789adec7e%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/99ec6c49-89ef-48f0-907e-4b4789adec7e%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Matthaus Owens
Puppet Labs

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CACD%3DwAfvLfPjd5dK6cxvkpi1M%3DK1U%3DQvUa03_b%3D7F%2B_gZ%3DsVQA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] bizarro error when starting a puppet agent

[Matthaus Owens]

Peter,

To allow us to be more helpful, it would be great if you could include
which version of puppet you are installing and from where. From the problem
you describe, I imagine you are installing from debian or ubuntu.

They include 2 files in their package /etc/puppet/etckeeper-commit-pre
and /etc/puppet/etckeeper-commit-post that are referenced in the
puppet.conf that ships with the package. It looks like etckeeper is
designed to allow someone to version control the etc directory (
https://joeyh.name/code/etckeeper/). The error you're seeing indicates that
the file doesn't exist, so there are 2 options to resolve it.

1. Edit /etc/puppet/puppet.conf to remove or disable the prerun_command and
postrun_command settings.
2. Reinstall the package to try to get the etckeeper-commit-post file back
(this assumes you are using the debian/ubuntu puppet packages)

Another option would be to use the Puppet Labs' apt repositories instead of
debian/ubuntu. We don't ship with those settings on by default in our
packages.

HTH

On Fri, Feb 5, 2016 at 8:18 AM, Peter Berghold <salty.cowd...@gmail.com>
wrote:

> First a disclaimer:   I am trying to provide support for our production
> team setting up a system as a Puppet agent node and most of the work I'm
> doing is being handled with the operations team acting as my voice operated
> keyboards.
>
>
> I handed my operations team instructions on how to install a Puppet client
> on some of our production boxes.  One such box when running the agent for
> the first time issues the following error and the run fails:
>
> "Error: Could not run command from postrun_command: Execution of
> '/etc/puppet/etckeeper-commit-post' retur ned 1: Error: Could not execute
> posix command: No such file or directory -
> /etc/puppet/etckeeper-commit-post"
>
> Never saw this error before and I'm quite baffled by it.  Where is this
> coming from and what is Puppet trying to tell me?
>
>
> Thanks in advance.
>
> --
> 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/CAArvnv2zJrNqO_W3wgeAjWiFmJ%3D%2BJzyohg_is4SQ1_SU153%2BoA%40mail.gmail.com
> <https://groups.google.com/d/msgid/puppet-users/CAArvnv2zJrNqO_W3wgeAjWiFmJ%3D%2BJzyohg_is4SQ1_SU153%2BoA%40mail.gmail.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Matthaus Owens
Puppet Labs

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CACD%3DwAekA%2BxkVk-doG3LAsaR%3D1moR2VMd-vk2oLYvU0kEtcJLg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] 'puppetmaster gem install activemq' issue

[Matthaus Owens]

Kenton,
It looks like you're trying to install the activemq gem, which is a
c++ rubygem. It also depends on other compiled rubygems.
Puppetserver's gem command does not support installing native C and
C++ based rubygems[1]. It might help if you explain a little more
about what you're trying to do, as generally people are interested in
the activemq java package and not the activemq rubygem.

[1] - 
https://docs.puppetlabs.com/puppetserver/latest/gems.html#gems-with-native-c-extensions

On Fri, Dec 11, 2015 at 2:01 PM, Kenton Brede <kbr...@gmail.com> wrote:
> Trying to install activemq on an Oracle Linux 7.2 box.  Using
> puppetlabs-release-pc1-1.0.0-1 which has puppetserver version 2.2.1.
>
> Below is the command I ran and the resulting error message.  I'm not a java
> guy.  Any advice appreciated. -- Thanks.
>
> [puppet ~]# puppetserver gem install activemq
> Building native extensions.  This could take a while...
> ERROR:  Error installing activemq:
> ERROR: Failed to build gem native extension.
>
> java -jar
> /opt/puppetlabs/server/apps/puppetserver/puppet-server-release.jar -r
> ./siteconf20151211-4760-1jn5vxr.rb extconf.rb
>
>
> Error(s) occurred while parsing command-line arguments: Unknown option: "-r"
>
>   -d, --debug   Turns on debug mode
>   -b, --bootstrap-config BOOTSTRAP-CONFIG-FILE  Path to bootstrap config
> file
>   -c, --config CONFIG-PATH  Path to a configuration file
> or directory of configuration files, or a comma-separated list of such
> paths.See the documentation for a list of supported file types.
>   -p, --plugins PLUGINS-DIRECTORY   Path to directory plugin
> .jars
>   -h, --helpShow help
>
> extconf failed, uncaught signal 1
>
> Gem files will remain installed in
> /opt/puppetlabs/server/data/puppetserver/jruby-gems/gems/rice-2.0.0 for
> inspection.
> Results logged to
> /opt/puppetlabs/server/data/puppetserver/jruby-gems/extensions/universal-java-1.8/1.9/rice-2.0.0/gem_make.out
>
> --
> Kent Brede
>
>
>
>
> --
> 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%2BnSE3_swJbORKmgjXMxsMbSUx%2BFFSNCLJjSE1b4S%3D1_CofyYw%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.



-- 
Matthaus Owens
Puppet Labs

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

Re: [Puppet Users] Hiera doesn't work with JSON

[Matthaus Owens]

;
> # interpolated facter variable
> hosts_entry: "sandbox.%{fqdn}"
>
> # hash
> sshd_settings:
> root_allowed: "no"
> password_allowed: "yes"
>
> # alternate hash notation
> sshd_settings: {root_allowed: "no", password_allowed: "yes"}
>
> # to return "true" or "false"
> sshd_settings: {root_allowed: no, password_allowed: yes}
>
>
> $ vim /etc/puppet/hiera.yaml
> $ cat /etc/puppet/hiera.yaml
> ---
> :backends:
> - yaml
> :hierarchy:
> - common
> :merge_behavior: "deeper"
> :yaml:
> :datadir: /etc/puppet/hieradata
>
>
> $ hiera -c /etc/puppet/hiera.yaml hosts_entry
> sandbox.
>
> Awesome! So YAML works.
>
> Back to the JSON version
>
> $ hiera -c /etc/puppet/hiera.yaml hosts_entry
> /usr/lib/ruby/site_ruby/1.8/hiera/filecache.rb:56:in `read_file': Data
> retrieved from /etc/puppet/hieradata/common.json is String not Hash
> (TypeError)
> from /usr/lib/ruby/site_ruby/1.8/hiera/backend/json_backend.rb:24:in
> `lookup'
> from /usr/lib/ruby/site_ruby/1.8/hiera/backend.rb:76:in `datasources'
> from /usr/lib/ruby/site_ruby/1.8/hiera/backend.rb:74:in `map'
> from /usr/lib/ruby/site_ruby/1.8/hiera/backend.rb:74:in `datasources'
> from /usr/lib/ruby/site_ruby/1.8/hiera/backend/json_backend.rb:17:in
> `lookup'
> from /usr/lib/ruby/site_ruby/1.8/hiera/backend.rb:206:in `lookup'
> from /usr/lib/ruby/site_ruby/1.8/hiera/backend.rb:203:in `each'
> from /usr/lib/ruby/site_ruby/1.8/hiera/backend.rb:203:in `lookup'
> from /usr/lib/ruby/site_ruby/1.8/hiera.rb:60:in `lookup'
> from /usr/bin/hiera:225
>
>
> Dah!
>
> No matter how simple I make it or what tweaks I do to the common.json file,
> I always get that exact error. If I run puppet agent, I get a very similar
> error too!
>
> "So just use YAML like the other post said"
> 1) That doesn't fix JSON and it avoids the problem ("Hey doc, my legs are
> broken!" "Have you tried walking on your hands instead? Why not just do
> that?" :-P)
>
> 2) The fancy new tool that my security team is using to manage and monitor
> system wide variables reads/writes JSON but doesn't do YAML. Meaning we
> either have to keep doing the manual checks we are doing, or stick a parser
> in between. Why? Puppet and Heira are supposed to work with JSON, it
> read/writes JSON, this should theoretically just work.
>
> Does anyone know why hiera isn't working with JSON? I really feel like this
> is probably a simple solution that I am just not seeing. I am hoping someone
> else might be able to recognize the answer.
>
> Thanks!
> ~Stack~
>
> --
> 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/2703e86d-f1e8-40a3-9d0c-24fd85bbbfe4%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.



-- 
Matthaus Owens
Puppet Labs

PuppetConf 2015 is coming to Portland, Oregon! Join us October 5-9.
Register now to take advantage of the Early Bird discount —save $249!

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CACD%3DwAde7ZJS5ECkFEZaeMG1M-XukW5HKtJnCSRo8-9Sw3--AA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Unable to get the ruby-ldap gem working with Puppet 4.x

[Matthaus Owens]

Omen,

It looks like you've installed the gem into the agent's gem path
instead of the server's. Puppetserver's docs[1] have details on how to
install a gem for puppetserver.
However, ruby-ldap is a compiled gem that won't work with jruby, so
jruby-ldap is the gem you'd want to use on the server. But, jruby-ldap
has a few issues[2], so even then it might not work. The bug I've
linked is about the LDAP terminus, so if you're writing a custom
function using ldap, it may work. jruby-ldap should have the same
interface as ruby-ldap, so it should just drop in and work.

If jruby-ldap doesn't work for you, there is a pure ruby ldap library
called ruby-net-ldap[3]. It looks like it has a different interface
than ruby-ldap, so it would probably require some rewriting of your
function.

[1] - 
https://docs.puppetlabs.com/puppetserver/2.1/gems.html#installing-and-removing-gems
[2] - https://tickets.puppetlabs.com/browse/SERVER-711
[3] - https://github.com/ruby-ldap/ruby-net-ldap

On Thu, Jul 16, 2015 at 6:15 PM, Omen Wild o...@ucdavis.edu wrote:
 I have a fresh install of Puppet 4.2 on an Ubuntu 14.04 box:
 root@puppet:~# /opt/puppetlabs/bin/puppetserver -v
 puppetserver version: 2.1.1

 We have a locally written Ruby command to do a LDAP lookup to get UIDs
 for our users, but with Puppet 4.2 it errors out:

 - Begin error -
 root@puppet:~# puppet agent -t
 Info: Retrieving pluginfacts
 Info: Retrieving plugin
 Info: Loading facts
 Error: Could not retrieve catalog from remote server: Error 500 on SERVER: 
 Internal Server Error: org.jruby.exceptions.RaiseException: (LoadError) no 
 such file to load -- ldap
 Warning: Not using cache on failed catalog
 Error: Could not retrieve catalog; skipping run
 - End error -

 I installed the gem with:

 - Begin quote -
 root@puppet:/etc/puppetlabs/code# /opt/puppetlabs/puppet/bin/gem install 
 ruby-ldap
 root@puppet:/etc/puppetlabs/code# /opt/puppetlabs/puppet/bin/gem list 
 ruby-ldap

 *** LOCAL GEMS ***

 ruby-ldap (0.9.17)
 - End quote -

 The full back-trace is attached.

 The same Ruby file works with Puppet 3.8.1 on Ubuntu 12.04 with the
 ruby-ldap package installed (not as a gem).

 What am I missing?

 Thanks,
Omen

 --
 Omen Wild
 Systems Administrator
 Metro Cluster

 --
 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/20150717011546.GB10028%40descolada.ucdavis.edu.
 For more options, visit https://groups.google.com/d/optout.



-- 
Matthaus Owens
Puppet Labs

PuppetConf 2015 is coming to Portland, Oregon! Join us October 5-9.
Register now to take advantage of the Early Bird discount —save $249!

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CACD%3DwAe0KcBtucYwQi4%3DXUaNDu4%3DdAAoVdSHQL80%3DT3rfdaHEA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] proper way to mirror apt.puppetlabs.com?

[Matthaus Owens]

Taher,
The readme (http://apt.puppetlabs.com/README.txt) suggests using
`rsync -av --copy-links --del rsync://apt.puppetlabs.com/packages/apt/
/var/apt/` to mirror the apt repos, which should work.

Hope that helps.

On Wed, Apr 1, 2015 at 1:32 AM, Taher Bohari taher.boh...@gslab.com wrote:
 Hello,

 I want to mirror puppet packages locally. I am trying to mirror it using
 cobbler reposync.

 But I am getting the error as  http://apt.puppetlabs.com/ubuntu/dists/lucid/
 is no longer present.

 Instead puppet packages are found at  http://apt.puppetlabs.com/dists/
 location. Using this path also gives me the error.

 Does any one knows how to mirror the puppet packages?

 --
 Thanks.


 On Friday, January 6, 2012 at 7:49:06 AM UTC+5:30, Adam Gibbins wrote:

 The recommendation for mirroring debian repositories is generally to use
 something like apt-mirror or apt-cacher-ng.  Is there a reason you can't do
 this?

 These work by checking the index (e.g.
 http://apt.puppetlabs.com/ubuntu/dists/lucid/main/binary-amd64/Packages) and
 pulling the packages.  You can't walk a HTTP repository, HTTP isn't smart
 like that.

 On 6 January 2012 01:46, Aaron Schaefer aarons...@gmail.com wrote:

 I am wanting to set up a local mirror of apt.puppetlabs.com, and am a
 bit confused by the layout as well as the announcement that was made
 in this thread:


 http://groups.google.com/group/puppet-users/browse_thread/thread/0786824ea9531fe3/f53c9006843ab8dc

 I'm not sure exactly what I should be pulling, as
 rsync://apt.puppetlabs.com/packages/apt
 gets everything, but it seems like a bit of a mess. The top-level
 pool/ directory is older than the top-level dists/ directory, but that
 seems to be what is recommended in the above thread. If you look just
 at the subdirectory ubuntu/ everything is in sync (all updated on Jan
 3rd, 2012), however there are a ton of date-specific directories
 listed under http://apt.puppetlabs.com/ubuntu/dists/ that seem to have
 duplicate information.

 I'm hoping that someone will know the proper way to rsync this mirror,
 so things are compatible going forward. Thanks!

 --
 Aaron Bull Schaefer

 --
 You received this message because you are subscribed to the Google Groups
 Puppet Users group.
 To post to this group, send email to puppet...@googlegroups.com.
 To unsubscribe from this group, send email to
 puppet-users...@googlegroups.com.
 For more options, visit this group at
 http://groups.google.com/group/puppet-users?hl=en.


 --
 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/3fb59986-d04c-45cb-be17-7e8e170770f1%40googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.



-- 
Matthaus Owens
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/CACD%3DwAcj_Lh1QQwL%2B5Xfmfcf%2B-vovHO6hvqE%3DxoOxMWbzskG-g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Geppetto 4.x download is broken

[Matthaus Owens]

Brian,
Geppetto 4.x downloads can be found at
https://downloads.puppetlabs.com/geppetto/4.x. I'll update the wiki
with the correct location. Hope that helps.

On Fri, Feb 27, 2015 at 11:25 AM, Brian Morris
nomadicextre...@gmail.com wrote:
 When attempting to access http://puppetlabs.github.io/geppetto/download.html
 in any of 3 browsers on 2 platforms this error is generated:

 (In Chrome) This webpage has a redirect loop


 (In Firefox) The page isn't redirecting properly



 Additionally, the alternate link given on
 https://github.com/puppetlabs/geppetto/wiki for the download:

 https://downloads.puppetlabs.com/geppetto/downloads

 ... results in a 404:

 Not Found
 The requested URL /geppetto/downloads was not found on this server.

 --
 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/a2190e8e-a02c-4152-be5a-2094494bcd99%40googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.



-- 
Matthaus Owens
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/CACD%3DwAcH_j00rvmz9UizupCyQZxCAv18bq22oxX%3DEWW0r04heQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Enterprise Linux puppet-server-3.7.4-1.el7.noarch doesn't include the init script

[Matthaus Owens]

Bryan,
EL7 has systemd, so we ship systemd service files for puppet and
puppet-server. `service puppet status` should still work, it just
redirects to systemctl under the hood.

rpm -qplv 
http://yum.puppetlabs.com/el/7/products/x86_64/puppet-3.7.4-1.el7.noarch.rpm
| grep service
-rw-r--r--1 rootroot  306 Jan 26 15:46
/usr/lib/systemd/system/puppet.service

rpm -qplv 
http://yum.puppetlabs.com/el/7/products/x86_64/puppet-server-3.7.4-1.el7.noarch.rpm
| grep service
-rw-r--r--1 rootroot  255 Jan 26 15:46
/usr/lib/systemd/system/puppetmaster.service

Hope that helps.

On Tue, Feb 10, 2015 at 8:18 PM, Bryan Arenal b.are...@gmail.com wrote:
 Hi,

 I just installed puppet and puppet-server on my CentOS 7 puppet master
 system but I noticed that there's no init script included (and none
 gets created).  The following doc says there should be one at least
 and one was included on a different ubuntu vm I'd tested on earlier:

 https://docs.puppetlabs.com/guides/install_puppet/install_el.html#step-3-install-puppet-on-the-puppet-master-server

 # rpm -qa |grep puppet
 puppet-3.7.4-1.el7.noarch
 puppetlabs-release-7-11.noarch
 puppet-server-3.7.4-1.el7.noarch

 # for i in `rpm -qa |grep puppet` ; do rpm -ql ${i} |grep ^\/etc ; done
 /etc/NetworkManager
 /etc/NetworkManager/dispatcher.d
 /etc/NetworkManager/dispatcher.d/98-puppet
 /etc/logrotate.d/puppet
 /etc/puppet
 /etc/puppet/auth.conf
 /etc/puppet/modules
 /etc/puppet/puppet.conf
 /etc/tmpfiles.d/puppet.conf
 /etc/pki/rpm-gpg/RPM-GPG-KEY-nightly-puppetlabs
 /etc/pki/rpm-gpg/RPM-GPG-KEY-puppetlabs
 /etc/yum.repos.d/puppetlabs.repo
 /etc/puppet/environments
 /etc/puppet/environments/example_env
 /etc/puppet/environments/example_env/README.environment
 /etc/puppet/environments/example_env/manifests
 /etc/puppet/environments/example_env/modules
 /etc/puppet/fileserver.conf
 /etc/puppet/manifests

 # ls /etc/init.d/
 functions  iprdump*  iprinit*  iprupdate*  netconsole*  network*  README

 # find /etc/rc*.d -iname *puppet*
 (nothing returned)

 On my ubuntu test box, I have:

 # ls /etc/init.d/puppet*
 /etc/init.d/puppet*  /etc/init.d/puppetmaster*  /etc/init.d/puppetqd*

 Should there be one for the EL7 RPM?

 Cheers

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



-- 
Matthaus Owens
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/CACD%3DwAdraBJze0XuoS%2BwH7u7JG6SOO%3DARpZmo6g%3DoAO8VQ7z%2Bg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] puppet cloud provisioner - without enterprise -Error: Unknown Puppet subcommand 'node_aws'

[Matthaus Owens]

Helen,

What does `head -n1 /usr/bin/gem` show? Gem may be running
/usr/bin/ruby1.8 under the hood, which would explain the ruby version
error you're seeing.

On Thu, Jan 22, 2015 at 5:20 AM, Helen Paterson
helen.pater...@gmail.com wrote:
 Hi,





 Has anyone had any luck getting the puppet cloud provisioner without the
 Puppet enterprise ( open source)  ?





 1. installed puppet module install puppetlabs-cloud_provisioner   (from the
 forge)

 2. sudo apt-get install ruby1.9.3 rubygems1.9.1

sudo ln -sf /usr/bin/ruby1.9.3 /usr/bin/ruby

 ( as on on ubuntu 10 and ruby 1.8)

 3.  gem install guid

 4. gem install fog



 with the error

  ERROR: Error installing fog:
  mime-types requires Ruby version = 1.9.2.



(even though the ruby version is no 1.9.3)



 5. touch ~/.fog



 The error I get all along is

  Error: Unknown Puppet subcommand 'node_vmware'

  Error: Unknown Puppet subcommand 'node_aws'


 Regards


 Helen

 --
 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/06dc8a2a-9585-425a-88e3-4a6c8f65e988%40googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.



-- 
Matthaus Owens
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/CACD%3DwAe%3De0NnuhdJ_HQiHpm%3D87n2KCd0DaxL4Cweox58cLqjAA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] newbie having troubles getting started: where is puppetmasterd?

[Matthaus Owens]

puppetmasterd was removed for the Puppet 3 series. The equivalent
command should be `puppet master --genconfig 
/etc/puppet/puppet.conf`. Hope that helps.

On Fri, Dec 12, 2014 at 4:25 PM, Jeff Silverman jeffsilv...@gmail.com wrote:
 I am trying to build a puppet system for the first time, and I am having a
 problem creating my puppet.conf file.  I am working on Ubuntu 12.04 LTS for
 my puppet master, and Centos 7 for my agents.

 Insofar as I can tell, there is no certificate on the puppet master.  The
 reason why I think so is because I am getting

 Exiting; no certificate found and waitforcert is disabled


 errors on the agents, and in the log file on the puppetmaster, I see many
 entries of the form:


 [2014-12-12 15:08:22] 192.168.1.49 - - [12/Dec/2014:15:08:22 PST] GET
 /production/certificate/jeffs-desktop.commercialventvac.com? HTTP/1.1 404
 73
 [2014-12-12 15:08:22] - -
 /production/certificate/jeffs-desktop.commercialventvac.com?



 I searched for jeffs-desktop* in /etc and /var, to no avail.


 I read Pro Puppet by Turnbull and McCune and on page 12, it says that I can
 create a configuration (which I hope includes a certificate) using the
 command


 puppetmasterd --genconfig  puppet.conf


 I find myself in a catch-22 situation.

 root@jeffs-desktop:/etc/puppet# puppetmaster --genconfig 
 /etc/puppet/puppet.conf
 No command 'puppetmaster' found, did you mean:
  Command 'puppetmasterd' from package 'puppetmaster' (main)
 puppetmaster: command not found
 root@jeffs-desktop:/etc/puppet# puppetmasterd --genconfig 
 /etc/puppet/puppet.conf
 The program 'puppetmasterd' is currently not installed.  You can install it
 by typing:
 apt-get install puppetmaster
 root@jeffs-desktop:/etc/puppet#

 oot@jeffs-desktop:/etc/puppet# apt-get install puppetmaster
 Reading package lists... Done
 Building dependency tree
 Reading state information... Done
 puppetmaster is already the newest version.
 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
 root@jeffs-desktop:/etc/puppet#




 I also tried the installation procedure discussed in
 https://docs.puppetlabs.com/guides/install_puppet/install_debian_ubuntu.html
 and that doesn't help, because apt-get thinks I am up-to-date on everything.


 I think I am stuck.


 Any advice?



 Many thanks in advance.


 Jeff



 --
 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/921f136c-a13b-4f62-86ff-54bd0f687c3d%40googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.



-- 
Matthaus Owens
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/CACD%3DwAerG6Kx7JJOraAf13aXLpjgV6r%2BVy%3D_QJ7cwDTkSif01w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] 3.4 client w/ 3.7 master

[Matthaus Owens]

Bernard,
I'm not aware of any issues with 3.x agents talking to a 3.7 master.
It should just work.

On Thu, Oct 30, 2014 at 11:32 AM, Bernard Clark berniecla...@gmail.com wrote:
 Will I have any trouble upgrading a puppetmaster to the latest 3.7 but
 keeping some of the puppet agents at 3.4.3? 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/CACpvNxTOfTydPnGzuHK7hPW3Jk%2Be1StXbdt7iv%3Dk%3D4tXD8UuKg%40mail.gmail.com.
 For more options, visit https://groups.google.com/d/optout.



-- 
Matthaus Owens
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/CACD%3DwAfm7dMgDkGttFXmAoP6XxO3j0JNed1%3DmZmH1kcYpLJVSA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Announce: Puppet Server 0.2.1 Available [Security Release]

[Matthaus Owens]

Puppet Server 0.2.1 is a security release. This release addresses
CVE-2014-7170. All users of Puppet Server are encouraged to upgrade as
soon as possible.

** CVE-2014-7170 **
Local information leakage

Due to a packaging bug[1], there is a window between package
installation/upgrade and service start where privileged data is
accessible to non-privileged local users.

CVSS v2 Score: 2.0 (low severity) [2]
CVSS v2 Vector: (AV:L/AC:L/Au:N/C:P/I:N/A:N/E:F/RL:U/RC:C)

Thanks to Dominic Cleal for responsibly disclosing this issue to us.

Reminder:
As the version number 0.2.1 should imply, Puppet Server is not
production ready (yet), but please do try it out in your favorite
sandbox. Additionally, the API will not be considered fully stable
until Puppet Server reaches 1.0.0.

Install Puppet Server from packages:

https://github.com/puppetlabs/puppet-server/blob/puppet-server-0.2.1/documentation/install_from_packages.markdown

Submit issues to:
https://tickets.puppetlabs.com/browse/SERVER

Source:
https://github.com/puppetlabs/puppet-server

[1] - https://tickets.puppetlabs.com/browse/SERVER-9
[2] - http://nvd.nist.gov/cvss.cfm

-- 
Matthaus Owens
Puppet Labs

Join us at PuppetConf 2014, September 20-24 in San Francisco -
www.puppetconf.com

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CACD%3DwAcVwyh7w%3Dkm%2B-FFssSitXb0HPtm-psck%3DD9aLN27i2ckw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] [security] GPG signing key collision

[Matthaus Owens]

Recently, we were alerted that when receiving the Puppet Labs gpg
signing key from a keyserver, a user was offered two keys.
The key exchange went something like this:

# gpg --fingerprint --search-keys 0x4BD6EC30
gpg: searching for 0x4BD6EC30 from hkp server pgp.mit.edu
(1) Puppet Labs Release Key (Puppet Labs Release Key) i...@puppetlabs.com
4096 bit RSA key 4BD6EC30, created: 2010-07-10
(2) Puppet Labs Release Key (Puppet Labs Release Key) i...@puppetlabs.com
4096 bit RSA key 4BD6EC30, created: 2010-07-10
Keys 1-2 of 2 for 0x4BD6EC30.  Enter number(s), N)ext, or Q)uit 

GPG offers no way of differentiating between the two keys at this
stage, even though one is from us and one is not.

Researching the problem turned up https://evil32.com, where some folks
have brute forced short key collisions on the strong set of the web of
trust. Our keys were used in their example of how
to compromise tarball signatures on this page:
https://evil32.com/examples.html

This is a problem for anyone verifying our packages/tarballs using gpg
short key IDs, which was the method formerly recommend in our our
documentation.

0x1054B7A24BD6EC30 is the long key ID of the real signing key, and it
has been signed by some previous and current employees. Its
fingerprint is 47B3 20EB 4C7C 375A A9DA  E1A0 1054 B7A2 4BD6 EC30.

0x0F65842D4BD6EC30 is the long key ID of the collision key and its
fingerprint is 22A6 C997 D0F3 2A3D 984B  BE13 0F65 842D 4BD6 EC30. It
has since been revoked by the authors of evil32.com.

While the colliding key has been revoked, this is a good opportunity
to recommend some best practices for validating our tarballs using
gpg.

First, always get the gpg key directly from us. This allows the use of
authenticated https instead of http, which gpg keyservers default to.
Here is an easy way to import our gpg key using https:

# wget -O - https://downloads.puppetlabs.com/puppetlabs-gpg-signing-key.pub
| gpg --import

Second, always validate the fingerprint of the key matches what you
expect. The fingerprint of our key should match what was listed above.
The fingerprint can be shown using `gpg --fingerprint
0x1054B7A24BD6EC30`. Some versions of gpg will show the fingerprint
when files are verified. In the following example, the last line shows
the fingerprint of the matching key:

# gpg --verify puppet-3.6.2.tar.gz.asc puppet-3.6.2.tar.gz
gpg: Signature made Tue 10 Jun 2014 12:44:55 PM EDT using RSA key ID 4BD6EC30
gpg: Good signature from Puppet Labs Release Key (Puppet Labs Release
Key) i...@puppetlabs.com
gpg: WARNING: This key is not certified with a trusted signature!
gpg:   There is no indication that the signature belongs to the owner.
Primary key fingerprint: 47B3 20EB 4C7C 375A A9DA  E1A0 1054 B7A2 4BD6 EC30

Finally, when listing keys, if --keyid-format LONG is passed to gpg,
it will list the full long key IDs instead of short IDs, as shown
below. This should make differentiating between keys with matching
short IDs easier.

# gpg --keyid-format LONG -k 0x4BD6EC30
pub   4096R/1054B7A24BD6EC30 2010-07-10 [expires: 2016-07-08]
uid  Puppet Labs Release Key (Puppet Labs
Release Key) i...@puppetlabs.com

pub   4096R/0F65842D4BD6EC30 2010-07-10 [revoked: 2014-09-11]
uid  Puppet Labs Release Key (Puppet Labs
Release Key) i...@puppetlabs.com

Many thanks to duritong on IRC, who alerted us to the collision, and
to evil32 for revoking their colliding key.

-- 
Matthaus Owens
Puppet Labs

Join us at PuppetConf 2014, September 20-24 in San Francisco -
www.puppetconf.com

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CACD%3DwAcLs_44o5U0x%3DE8uD4yM_mtN%3Dt%3DU62G0aKk9bOZyk8Ejg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Access to apt.puppetlabs.com slow for some IP addresses

[Matthaus Owens]

Johannes,

I don't see anything on our end that would be causing the issue you're
seeing. I have enabled some additional logging on the apt repos to get
us extra information about what might be going on. I have also opened
a ticket https://tickets.puppetlabs.com/browse/CPR-60 to track this
issue. Please feel free to add any additional information that might
help us diagnose the problem. Thanks!


On Wed, Aug 6, 2014 at 2:11 AM, Johannes Grassler
j.grass...@syseleven.de wrote:
 Hello,

 we are currently creating and tearing down lots of VMs in our lab
 environment. This includes retrieving and installing Puppet from the
 Puppetlabs repository at apt.puppetlabs.com. Recently we found that from
 some addresses in our lab's /24 access to http://apt.puppetlabs.com is
 painfully slow (things are trickling in at ~800 bytes per second). We
 double-checked our lab network and the automated VM provisioning process and
 found nothing amiss. Now we are wondering whether we ran into some kind of
 rate limiting on the repository's side, since we do repeatedly retrieve the
 same packages in the course of VM provisioning, more often than not from the
 same IP address. One of the 'slow' addresses in question is 37.44.0.243. Is
 there anyone on this list who could look into this?

 If we are indeed causing too much load we'd be happy to set up a public
 mirror of apt.puppetlabs.com.

 Cheers,

 Johannes

 --
 SysEleven GmbH
 Umspannwerk - Aufgang C
 Ohlauer Straße 43
 10999 Berlin

 Tel +49 30 233 2012 0
 Fax +49 30 616 755 50

 http://www.syseleven.de
 http://www.facebook.com/SysEleven

 Firmensitz: Berlin
 Registergericht: AG Berlin Charlottenburg, HRB 108571 B
 Geschäftsführer: Marc Korthaus, Thomas Lohner

 --
 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/a289bd73-cddf-4b76-80d1-c5e5ee6f30d5%40googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.



-- 
Matthaus Owens
Puppet Labs

Join us at PuppetConf 2014, September 20-24 in San Francisco
Register by September 8th to take advantage of the Final Countdown —save $149!

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CACD%3DwAfKvsWK-Mf9GTBU%3D5Qj-YtkH%2BwRKga6rkf0dvLLXBPL%2Bg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Raring has been removed from apt.puppetlabs.com

[Matthaus Owens]

As previously announced[1], Raring has now been removed from our
public apt repositories, as it had reached end of life.

[1] - 
https://groups.google.com/forum/#!msg/puppet-users/YEG0C3OtWfE/Nq6AUGCv5kQJ

-- 
Matthaus Owens
Puppet Labs

Join us at PuppetConf 2014, September 22-24 in San Francisco
Register by May 30th 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/CACD%3DwAd0sYkFYkAw8i%2BR8XVoP3U7DsWZVfpHdF%2BSe-68UwRkCg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] facter for debian: missing '_all.deb' version

[Matthaus Owens]

This issue is being tracked at
https://tickets.puppetlabs.com/browse/CPR-5. The core of the problem
is that facter is not an all arch package. It depends on dmidecode,
which is not available for all architectures. Because of this, facter
is an arch dependent package and there is no all package for it. There
is more detail in the linked ticket.

HTH

On Mon, Apr 28, 2014 at 7:52 AM, JonY ethrbu...@gmail.com wrote:
 To the build-czars at puppet labs: could you please include a *_all.deb
 version of facter in your build cycle? It doesn't appear to have been
 created since v 1.6.18.

 My clients are almost exclusively ARM based and can't upgrade without this
 being available.

 Humbly yours, 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/d01e58d1-70a1-47ae-b802-d49473d2d5b0%40googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.



-- 
Matthaus Owens
Puppet Labs

Join us at PuppetConf 2014, September 22-24 in San Francisco
Register by May 30th 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/CACD%3DwAfekHn0thnJtAx1XMK3xjS6Gt5CdNjqX-%2BJ4atcRtZwZA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Raring leaving apt.puppetlabs.com

[Matthaus Owens]

Ubuntu raring reached end of life on 2014-01-27 [1], so we are no
longer building new packages for it and will remove it from our apt
repository on Monday, May 19.

[1] - 
http://fridge.ubuntu.com/2014/01/28/ubuntu-13-04-raring-ringtail-end-of-life-reached-on-january-27-2014/

-- 
Matthaus Owens
Puppet Labs

Join us at PuppetConf 2014, September 22-24 in San Francisco
Register by May 30th 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/CACD%3DwAe%2B%3Dyzoiz7iXw%3Di58yXNNFw-7A2m0-_fWgthxMYMh-NEQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Quantal leaving apt.puppetlabs.com

[Matthaus Owens]

Ubuntu quantal will reach end of life in April 2014 [1], and we will
no longer be building packages for quantal once Ubuntu announces its
retirement. We will remove it from our apt repository on Monday, June
23.

[1] - https://lists.ubuntu.com/archives/ubuntu-announce/2012-October/000164.html

-- 
Matthaus Owens
Puppet Labs

Join us at PuppetConf 2014, September 22-24 in San Francisco
Register by May 30th 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/CACD%3DwAdzMtFSJLTa036SaTknfrbOtC8SkrKYi05gSF7fnULmjg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Debian jessie, puppetlabs dist-upgrade problem

[Matthaus Owens]

This is probably because the default ruby used to provide
libxmlrpc-ruby and libopenssl-ruby*/ruby-openssl, but the rubies
available in jessie do not. Because puppet depends on both of those
packages, the upgrade does not succeed because apt can't find the
needed dependencies. This has been fixed in master in commit
https://github.com/puppetlabs/puppet/commit/b6514b8dfe92a1e66c086fe1f45e5e7261bd45fb,
but it has not yet been released. It should be released in Puppet
3.6.0.

HTH

On Mon, Apr 21, 2014 at 5:16 AM, Juan Sierra Pons j...@elsotanillo.net wrote:

 El 20/04/2014 18:29, Mike R. mroa...@gmail.com escribió:



 Using wheezy or unstable puppetlabs release, dist-upgrade wants to remove
 puppet and puppet-common to upgrade libruby. Anyone seen this?


 root@enigma:~# apt-get dist-upgrade
 Reading package lists... Done
 Building dependency tree
 Reading state information... Done
 Calculating upgrade... Done
 The following packages were automatically installed and are no longer
 required:
   facter hiera libaugeas-ruby1.8 libjson-ruby libruby libshadow-ruby1.8
 ruby-rgen virt-what
 Use 'apt-get autoremove' to remove them.
 The following packages will be REMOVED:
   puppet puppet-common
 The following packages will be upgraded:
   libruby
 1 upgraded, 0 newly installed, 2 to remove and 0 not upgraded.
 Need to get 7,296 B of archives.
 After this operation, 5,186 kB disk space will be freed.
 Do you want to continue? [Y/n] n
 Abort.
 root@enigma:~#

 --
 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/ce5a9804-9488-4aa0-9a04-f92bb273d962%40googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.

 Hi,

 I had the same problem. I installed older package version using the
 alternatives proposed by aptitude.

 Hope it helps

 Best regards

 --
 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/CABS%3Dy9tHHKySmJVpNye5QBhnVuvrN_eiB3unHuDREru_jjFi%2BQ%40mail.gmail.com.

 For more options, visit https://groups.google.com/d/optout.



-- 
Matthaus Owens
Puppet Labs

Join us at PuppetConf 2014, September 22-24 in San Francisco
Register by May 30th 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/CACD%3DwAf%2B0EkTH%3Dgi5hFna0FKxMbp08Z4VxofSMxLb_%2B1e6wP0g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] puppet repos on ubuntu 14.04

[Matthaus Owens]

Puppet hasn't been released for Ubuntu 14.04 yet. There were some
dependency updates for the puppet package that are needed for Trusty
that haven't been released yet. The commit with the fix
(https://github.com/puppetlabs/puppet/commit/b6514b8dfe92a1e66c086fe1f45e5e7261bd45fb)
should be released in Puppet 3.6.0. Until then I would recommend using
Ubuntu's 3.4.3 packages.

HTH

On Sun, Apr 20, 2014 at 9:29 PM, Matt McMahand mmcmah...@gmail.com wrote:
 Hello,

 I was trying out ubuntu trusty over the weekend and am having some trouble
 installing puppet 3.5.1 from the puppetlabs repo.

 I've tried adding the repo and searching for the package, but no luck:

 cd /tmp  wget -N https://apt.puppetlabs.com/puppetlabs-release-trusty.deb
   sudo dpkg -i puppetlabs-release-trusty.deb
 sudo apt-get update

 sudo apt-cache madison puppet
 puppet |3.4.3-1 | http://us.archive.ubuntu.com/ubuntu/ trusty/main
 amd64 Packages
 puppet |3.4.3-1 | http://us.archive.ubuntu.com/ubuntu/ trusty/main
 Sources


 cat /etc/apt/sources.list.d/puppetlabs.list
 # Puppetlabs products
 deb http://apt.puppetlabs.com trusty main
 deb-src http://apt.puppetlabs.com trusty main

 # Puppetlabs dependencies
 deb http://apt.puppetlabs.com trusty dependencies
 deb-src http://apt.puppetlabs.com trusty dependencies

 # Puppetlabs devel (uncomment to activate)
 # deb http://apt.puppetlabs.com trusty devel
 # deb-src http://apt.puppetlabs.com trusty devel

 I noticed when I added the precise repos (12.04), puppet 3.5.1 was there,
 but couldn't install because of all kinds of repo mismatching. I'm assuming
 this is because I'm using the wrong repo.

 Has anyone else had luck installing?

 --
 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/4dfd2268-d1b1-4931-8d20-8494ffe0e8a8%40googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.



-- 
Matthaus Owens
Puppet Labs

Join us at PuppetConf 2014, September 22-24 in San Francisco
Register by May 30th 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/CACD%3DwAerTA8V2dA01rRSM4qZfs2OnJJYzize6YBpN_N7i7fdbg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Can't get puppet/passenger to stop using /home/puppet/.puppet

[Matthaus Owens]

 Singlewire Software, LLC
 www.singlewire.com
 --
 608.661.1184
 john.pye...@singlewire.com




 --
 John Pyeatt
 Singlewire Software, LLC
 www.singlewire.com
 --
 608.661.1184
 john.pye...@singlewire.com

 --
 You received this message because you are subscribed to the Google Groups
 Puppet Users group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to puppet-users+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/puppet-users/CAEisTLnvt1nWaFWupeNvQTz%2B8YFRu9-OkZsBLVFKMJL2cJ7m%2Bw%40mail.gmail.com.

 For more options, visit https://groups.google.com/d/optout.



-- 
Matthaus Owens
Puppet Labs

Join us at PuppetConf 2014, September 23-24 in San Francisco -
http://bit.ly/pupconf14
Register now and save $350!

-- 
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/CACD%3DwAdG1fP%2BhgkUjG7UDM7rGLB%3DwB5-k6MVnjOtdaogMmgqEQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] RHEL 7 Repository up on yum.puppetlabs.com

[Matthaus Owens]

Kodiak,
Puppet 3.5.0 is currently in RC and should go final soon. Are there
packages you are looking for besides Puppet itself?

On Wed, Apr 2, 2014 at 10:05 AM, Kodiak Firesmith kfiresm...@gmail.com wrote:
 Hi PuppetLabs,
 Any more word on the RHEL 7 effort?  I'm a little surprised that EL7 is so
 far into beta and we still don't have much in
 http://yum.puppetlabs.com/el/7/.
 Thanks,
  - Kodiak



 On Tuesday, February 11, 2014 8:23:03 PM UTC-5, Melissa Stone wrote:

 On Mon, Feb 10, 2014 at 1:16 PM, Johan De Wit jo...@open-future.be
 wrote:

 FYI

 Facter 1.7.5 installs and seems to work.

 Mcollective rpms, we have to wait till the dependencies repo is build.
 rubygem-stomp is needed.


 rubygem-stomp 1.2.10 is now available in the dependency repo for el 7 on
 yum.puppetlabs.com

 --
 Melissa Stone
 Release Engineer, Puppet Labs

 Join us at PuppetConf 2014, September 23-24 in San Francisco

 --
 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/784d2b8d-d3be-4d97-a51b-7feae7b36cc0%40googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.



-- 
Matthaus Owens
Puppet Labs

Join us at PuppetConf 2014, September 23-24 in San Francisco -
http://bit.ly/pupconf14
Register now and save $350!

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

Re: [Puppet Users] RHEL 7 Repository up on yum.puppetlabs.com

[Matthaus Owens]

Kodiak,
A Puppet 3.4.3 master should have no problems supporting a Puppet
3.5.0 client, and if it does it is a bug that you should raise with
us.

On Wed, Apr 2, 2014 at 10:27 AM, Kodiak Firesmith kfiresm...@gmail.com wrote:
 Hi Matthaus, and thanks for the reply!

 We are looking to run RHEL 7 clients during Redhat's beta to prepare for the
 general release.  We'll be upgrading our RHEL 6 Puppet Master to 3.4.3
 shortly but don't plan to upgrade the Puppet Master to RHEL 7 any time soon.

 Will the version skew of a 3.4.3-1 Puppet Master and a 3.5.0 Puppet client
 cause problems?  I've seen in many places that the master should always be
 at an equal or higher rev than all clients.  If this remains the case, and
 you cannot ship 3.4.3 for RHEL 7 this means substantial overhead in standing
 up another Puppet Master for RHEL 7 clients which we would very much like to
 avoid.

 Thanks again!
  - Kodiak


 On Wednesday, April 2, 2014 1:14:07 PM UTC-4, Matthaus Litteken wrote:

 Kodiak,
 Puppet 3.5.0 is currently in RC and should go final soon. Are there
 packages you are looking for besides Puppet itself?

 On Wed, Apr 2, 2014 at 10:05 AM, Kodiak Firesmith kfire...@gmail.com
 wrote:
  Hi PuppetLabs,
  Any more word on the RHEL 7 effort?  I'm a little surprised that EL7 is
  so
  far into beta and we still don't have much in
  http://yum.puppetlabs.com/el/7/.
  Thanks,
   - Kodiak
 
 
 
  On Tuesday, February 11, 2014 8:23:03 PM UTC-5, Melissa Stone wrote:
 
  On Mon, Feb 10, 2014 at 1:16 PM, Johan De Wit jo...@open-future.be
  wrote:
 
  FYI
 
  Facter 1.7.5 installs and seems to work.
 
  Mcollective rpms, we have to wait till the dependencies repo is build.
  rubygem-stomp is needed.
 
 
  rubygem-stomp 1.2.10 is now available in the dependency repo for el 7
  on
  yum.puppetlabs.com
 
  --
  Melissa Stone
  Release Engineer, Puppet Labs
 
  Join us at PuppetConf 2014, September 23-24 in San Francisco
 
  --
  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/784d2b8d-d3be-4d97-a51b-7feae7b36cc0%40googlegroups.com.
  For more options, visit https://groups.google.com/d/optout.



 --
 Matthaus Owens
 Puppet Labs

 Join us at PuppetConf 2014, September 23-24 in San Francisco -
 http://bit.ly/pupconf14
 Register now and save $350!

 --
 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/5240a621-1804-4d80-ae1b-e4436749ba95%40googlegroups.com.

 For more options, visit https://groups.google.com/d/optout.



-- 
Matthaus Owens
Puppet Labs

Join us at PuppetConf 2014, September 23-24 in San Francisco -
http://bit.ly/pupconf14
Register now and save $350!

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

Re: [Puppet Users] Installing Puppet Enterprise Edition

[Matthaus Owens]

Ricky,
Puppet Enterprise supports Ubuntu LTS releases as well as Debian
releases (see 
http://docs.puppetlabs.com/pe/latest/install_system_requirements.html#operating-system
for the complete list). Ubuntu 13.10 is not an LTS (long term support)
release. If you'd like to request support for a platform that is not
currently supported, you can make such a request in
https://tickets.puppetlabs.com/browse/ENTERPRISE-24.

HTH

On Thu, Mar 13, 2014 at 1:29 AM, Rikki rikki.mah...@gmail.com wrote:
 Hi All,

 How are you doing? I am trying to install Puppet enterprise edition. But
 could not figure out which one to download.

 FYI I am running linux mint 16 Petra version which I think is equivalent to
 saucy release for ubuntu 13.10.

 Could you please help me in letting me know which tar ball should I download
 from
 http://puppetlabs.com/misc/pe-files?utm_campaign=pegettingstartedutm_medium=emailutm_source=PE3.1experimentutm_content=t1pedownloadmkt_tok=3RkMMJWWfF9wsRons6nOZKXonjHpfsX86uUtUKe3lMI%2F0ER3fOvrPUfGjI4CSstqI%2BSLDwEYGJlv6SgFSbDCMbFs27gEUhA%3D

 As I can see there is no tarball matching my OS. Looking forward to hear
 from you soon.

 Thanks,
 Ricky

 --
 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/4681fc3e-b2c6-4b1f-b4c9-325be0e02e94%40googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.



-- 
Matthaus Owens
Release Manager, Puppet Labs

Join us at PuppetConf 2014, September 23-24 in San Francisco -
http://bit.ly/pupconf14
Register now and save $350!

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

Re: [Puppet Users] stdlib: result from join_keys_to_values() is unstable

[Matthaus Owens]

Gabriel,
I don't know about the specific implementation of join_keys_to_values,
but ruby's hash behavior changed between the 1.8 series and 1.9 and
later[1]. In ruby 1.8 hashes are enumerated in a seemingly unsorted
manner, while in ruby 1.9 and later hashes are enumerated in insertion
order. If you are on ruby 1.8, it would be worth seeing if you
experience the same issues in ruby 1.9 or later.

[1] - 
http://stackoverflow.com/questions/7065915/why-is-my-hash-autosorting-itself

On Tue, Mar 11, 2014 at 9:27 AM, Gabriel Filion lelu...@gmail.com wrote:
 Hi there,

 Say I have a hash like {a='1',b='2'} and I'd like to get a string that
 looks like a=1,b=2. I tried using a combination of
 join_keys_to_values() and join() and the result looked correct, but was
 unstable. That unstability is because hashes are not always sorted the
 same way.

 An unstable string means that the config file in which I use it gets
 modified for no reason from time to time and this triggers an
 unnecessary service refresh.

 I'm currently using an inline template to achieve what I want, since
 with ruby I can use h.sort.map to always get results in the same order
 from a hash h.

 Thing is, stdlib's sort() function only accepts strings or arrays.


 Is there a way to get a stable string with current means?

 Otherwise, would it be an acceptable idea to add support for hashes in
 sort() ?

 --
 Gabriel Filion




-- 
Matthaus Owens
Release Manager, Puppet Labs

Join us at PuppetConf 2014, September 23-24 in San Francisco -
http://bit.ly/pupconf14
Register now and save $350!

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

Re: [Puppet Users] Bug(?) in puppetlabs-firewall module prevents successful install/upgrade to PE 3.2

[Matthaus Owens]

Peter,
I've opened https://tickets.puppetlabs.com/browse/ENTERPRISE-88 to
track this issue. It seems related to
https://tickets.puppetlabs.com/browse/MODULES-473.

On Tue, Mar 4, 2014 at 10:03 AM, Peter Bukowinski pmb...@gmail.com wrote:
 When upgrading my master from 3.1 to 3.2 (on a Scientific Linux 6.3 server),
 the install fails during the puppetlabs-firewall module installation with
 this error:

 ** /opt/puppet/bin/puppet module install
 /misc/local/pe/puppet-enterprise-3.2.0-el-6-x86_64/modules/puppetlabs-firewall-1.0.0.tar.gz
 --force --ignore-dependencies --modulepath /opt/puppet/share/puppet/modules
 Notice: Preparing to install into /opt/puppet/share/puppet/modules ...
 Notice: Installing -- do not interrupt ...
 Error: No such file or directory -
 /opt/puppet/share/puppet/modules/firewall/spec/acceptance/nodesets/default.yml

 When I look in the nodesets directory, I see a broken symlink that looks
 like it may be missing a -pe in its name:

ls -la /opt/puppet/share/puppet/modules/firewall/spec/acceptance/nodesets/
 total 20
 drwxr-xr-x 2 root root 4096 Mar  4 12:40 .
 drwxr-xr-x 3 root root 4096 Mar  4 12:40 ..
 -r--r--r-- 1 root root  282 Jan 30 12:12 centos-64-x64-pe.yml
 lrwxrwxrwx 1 root root   17 Mar  4 12:40 default.yml - centos-64-x64.yml
 -r--r--r-- 1 root root  254 Jan 30 12:12 sles-11sp1-x64.yml
 -r--r--r-- 1 root root  285 Jan 30 12:12 ubuntu-server-10044-x64.yml

 Has anyone else run into this? In any case, I'd recommend waiting to upgrade
 until you hear otherwise.

 --
 Peter Bukowinski

 --
 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/F9979BCD-D5CE-4906-91DD-6DE388D6665E%40gmail.com.
 For more options, visit https://groups.google.com/groups/opt_out.



-- 
Matthaus Owens
Release Manager, Puppet Labs

Join us at PuppetConf 2014, September 23-24 in San Francisco -
http://bit.ly/pupconf14
Register now and save $350!

-- 
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/CACD%3DwAfJW45zLtcifMggkEy0UQcgGJbcAxwO9Bg6-bdMMLtt%2Bg%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] puppet post install launchd osx

[Matthaus Owens]

   stringcom.puppetlabs.puppet/string
   keyKeepAlive/key
   true/
   keyProgramArguments/key
   array
   string/usr/bin/puppet/string
   stringagent/string
   string--verbose/string
   string--no-daemonize/string
   string--logdest/string
   stringconsole/string
   /array
   keyRunAtLoad/key
   true/
   keyServiceDescription/key
   stringPuppet Daemon/string
   keyServiceIPC/key
   false/
   keyStandardErrorPath/key
   string/var/log/puppet/puppet.err/string
   keyStandardOutPath/key
   string/var/log/puppet/puppet.out/string
   /dict
  
   /plist
  
   --
   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/0b798c59-e87c
 -4dde-886f-885b1a2045ea%40googlegroups.com.
   For more options, visit https://groups.google.com/groups/opt_out.

 
  Hi Ryan,
 
  Unfortunately the plist at that link is a little out of date. The
  ServiceIPC and ServiceDescription keys aren't supported in recent
  versions of OSX. You can just remove them, really. Also, how did
 you
  install puppet, which version of puppet did you install, and on
 what
  version of OSX? Puppet = 3.4.0 installed via dmg lives in
  /Library/Ruby/Site, to make it compatible with ruby 2 on Mavericks,
 so
  you may want to update the plist to reflect this. Puppet  3.4.0
  installed via dmg is installed to the RUBYLIB in your plist.
  Finally, if you're using mavericks and installing from dmg, you'll
  need facter 1.7.5-rc1 or later (I believe we are shipping the final
  version of facter 1.7.5 very soon).
 
  --
  Moses Mendoza
  Puppet Labs
 
  Join us at PuppetConf 2014, September 23-24 in San Francisco -
  http://bit.ly/pupconf14
 
  --
  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/091b78d2-561c
 -409c-984c-175fca39211b%40googlegroups.com.
 
  For more options, visit https://groups.google.com/groups/opt_out.



 --
 Moses Mendoza
 Puppet Labs

 Join us at PuppetConf 2014, September 23-24 in San Francisco -
 http://bit.ly/pupconf14

  --
 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/c3ed55e9-29ba-40e8-8863-adf68ec10ed6%
 40googlegroups.com.

 For more options, visit https://groups.google.com/groups/opt_out.




 --
 Moses Mendoza
 Puppet Labs

 Join us at PuppetConf 2014, September 23-24 in San Francisco -
 http://bit.ly/pupconf14

  --
 You received this message because you are subscribed to a topic in the
 Google Groups Puppet Users group.
 To unsubscribe from this topic, visit
 https://groups.google.com/d/topic/puppet-users/Du5xrfZR9V0/unsubscribe.
 To unsubscribe from this group and all its topics, 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/93eb709f-dd2a-4626-bcb2-f7b96e44cd87%40googlegroups.com
 .

 For more options, visit https://groups.google.com/groups/opt_out.


  --
 You received this message because you are subscribed to the Google Groups
 Puppet Users group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to puppet-users+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/puppet-users/CAPr_nD-BFALbX2PutdPxxj9_SSU3sBguOEKzBUJAn_2FNnXY7g%40mail.gmail.com
 .

 For more options, visit https://groups.google.com/groups/opt_out.




-- 
Matthaus Owens
Release Manager, Puppet Labs

Join us at PuppetConf 2014, September 23-24 in San Francisco

-- 
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/CACD%3DwAfW4CDgAyTK8iD9BL3p8dnSzi_P4oqELHgd1s4EsDGZiQ%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Re: facter-1.7.3 and puppet-3.3.1 on OS X Mavericks 10.9

[Matthaus Owens]

Paul, that ssl error looks like the following post on puppet-users:
https://groups.google.com/forum/#!topic/puppet-users/4-6EimF_-NY/discussion,
which relates to SNI. Adding a server alias to your puppetmaster vhost may
resolve your problem. This is a change in ruby after 1.9.0, so it wouldn't
have been in system ruby on OSX before mavericks.

HTH


On Tue, Feb 11, 2014 at 1:08 AM, Paul Tötterman paul.totter...@iki.fiwrote:

  facter-1.7.4-rc1 is available and it looks like it works!

 Actually, it wasn't until 1.7.5 that the packages available from
 downloads.puppetlabs.com were fixed, but it really seems to work now.

 However, I have a problem with puppet on OS X 10.9. I'm using the
 latest packaged version 3.4.2.

 It may be a problem with the ruby and openssl configuration shipped
 with OS X 10.9, but I'm getting:

 Info: Creating a new SSL key for $fqdn
 Error: Could not request certificate: SSL_connect returned=1 errno=0
 state=SSLv2/v3 read server hello A: (null)

 /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/net/http.rb:918:in
 `connect'

 when running `puppet agent --test --verbose --debug --evaltrace --trace`.

 There are some results on the web about ruby failing because of a
 missing CA cert bundle, but the puppet master generated CA cert
 wouldn't be included anyway, so that isn't a solution in this case.

 Anyone have any other ideas?

 Cheers,
 Paul

 --
 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/CANPS_M5vfAkAuTiytEG_GkB3XckAzk-kGXGXKPzix7CHAQ9uoA%40mail.gmail.com
 .
 For more options, visit https://groups.google.com/groups/opt_out.




-- 
Matthaus Owens
Release Manager, Puppet Labs

Join us at PuppetConf 2014, September 23-24 in San Francisco

-- 
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/CACD%3DwAf%3DCRohcwkaJLBHJFMTwBe9q-%2BkcLhY_pvAK2e%2BxPRLLw%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Puppet 3.4.2 Windows package updated for CVE-2013-6393

[Matthaus Owens]

We have rebuilt our Windows package for Puppet 3.4.2 in response to
CVE-2013-6393[1]. The package includes ruby 1.9.3-p484 compiled against an
updated libyaml. It is available at
http://downloads.puppetlabs.com/windows/puppet-3.4.2-20140211.msi

CVE-2013-6393 is a vulnerability in the libyaml library that could lead to
a denial of service, and the possibility of arbitrary code execution.

[1] - http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-6393

-- 
Matthaus Owens
Release Manager, Puppet Labs

Join us at PuppetConf 2014, September 23-24 in San Francisco

-- 
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/CACD%3DwAdhr83kf0kR_LGsYBNnLCwPd1SE7gZ00fVZm%2BJx6n3uGw%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] RHEL 7 Repository up on yum.puppetlabs.com

[Matthaus Owens]

Johan,
Thanks for the quick feedback. We've been working on the dependencies repo
for rhel 7 and it should be getting updated today and tomorrow.


On Mon, Feb 10, 2014 at 1:16 PM, Johan De Wit jo...@open-future.be wrote:

  FYI

 Facter 1.7.5 installs and seems to work.

 Mcollective rpms, we have to wait till the dependencies repo is build.
 rubygem-stomp is needed.





 On 02/10/2014 08:46 PM, Melissa Stone wrote:

 We are pleased to let you know we are currently working on creating RHEL 7
 packages. We want to do a thorough testing of these packages, so we are
 taking our time with this platform. However, we still want to get the
 packages we do have into your hands. As such, we're going to be slowly
 populating the RHEL 7 repository on yum.puppetlabs.com for your
 consumption. Please, let us know if you run into any issues with the
 available packages by creating an issue at tickets.puppetlabs.com.

 --
 Melissa Stone
 Release Engineer, Puppet Labs

 Join us at PuppetConf 2014, September 23-24 in San Francisco
 --
 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_kpd6DgeTH7P5cCe_L0S2w550gxVvBo8XBtrVsHmA%2BR_OA%40mail.gmail.com
 .

 For more options, visit https://groups.google.com/groups/opt_out.



 --
 Johan De Wit

 Open Source Consultant

 Red Hat Certified Engineer (805008667232363)
 Puppet Certified Professional 2013 (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
 _



 Upcoming Events:

 Puppet Fundamentals Training |
 http://www.open-future.be/puppet-fundamentals-training-4-till-6th-february

 Puppet Introduction Course |
 http://www.open-future.be/puppet-introduction-course-7th-february

 Zabbix Certified Training |
 http://www.open-future.be/zabbix-certified-training-10-till-12th-february

 Zabbix for Large Environments Training |
 http://www.open-future.be/zabbix-large-environments-training-13-till-14th-february

 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/52F94198.4020905%40open-future.be
 .

 For more options, visit https://groups.google.com/groups/opt_out.




-- 
Matthaus Owens
Release Manager, Puppet Labs

Join us at PuppetConf 2014, September 23-24 in San Francisco

-- 
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/CACD%3DwAeSxLpndu5ULdkFUWB6suNJGfELu-xQu51ayAu7qkKBqw%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Puppet Post install

[Matthaus Owens]

This is in response to your dashboard question.
Running dashboard via apache will handle the starting of the rails app
itself, but what you've quoted is the dashboard-workers, which are separate
processes that handle doing work for dashboard, like processing reports
from the puppet master. There are some init scripts in the puppet-dashboard
repo that should work on most platforms to enable the workers to start
automatically on boot.


On Thu, Jan 23, 2014 at 10:30 AM, Jason Hatman jason.hat...@gmail.comwrote:

 I have a complete and working Puppet setup.  Now, I need to automate it.
  Looking at the following page:
 http://docs.puppetlabs.com/guides/installation.html#post-install  I can
 see that it wants me to set up launchd processes for OS X in order to have
 the Puppet service start at boot.  I just want to make sure that this is
 necessary.  I have a master/agent configuration.  In a master/agent setup,
 does it automate this by default or do I still have to setup launchd on
 each machine?

 This is a separate issue from the first one.  I have completed my
 puppet-dashboard setup and it's running fine.  However, I've noticed that
 after I reboot the machine, I no longer have any worker processes running.
  I have to manually run sudo -u puppet-dashboard env
 RAILS_ENV=production script/delayed_job -p dashboard -n 4 -m start before
 any they start working again.  I assumed once I converted dashboard to run
 in apache that this would be automated.  Am I wrong?

 Thanks in advance!!

 --
 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/57ad28a4-8c88-47c3-8b2a-78bda273a456%40googlegroups.com
 .
 For more options, visit https://groups.google.com/groups/opt_out.




-- 
Matthaus Owens
Release Manager, Puppet Labs

Join us at PuppetConf 2014, September 23-24 in San Francisco

-- 
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/CACD%3DwAfK2Dn9dgVL-NfR_C%2BbqK_Y7pXRLzkjAwZeoq5X_3QBBg%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] facter-1.7.3 and puppet-3.3.1 on OS X Mavericks 10.9

[Matthaus Owens]

It didn't make it into Facter 1.7.4, but it will be in Facter 1.7.5, which
should be entering RC soon.


On Tue, Jan 14, 2014 at 11:17 AM, Khoury Brazil khoury.bra...@gmail.comwrote:

 That's good to hear. But I'm still concerned about Facter. Correct me if
 I'm wrong, but this issue indicates that Facter 1.7.5 will be targeted but
 we're currently on 1.7.4:
 https://projects.puppetlabs.com/issues/22107

 Did it make it into 1.7.4?



 On Tue, Jan 14, 2014 at 11:05 AM, Jeff Bachtel 
 jbach...@bericotechnologies.com wrote:

  I don't have a Maverick box to test on, but the PRs in question are
 applied to the 3.4.0 and onward tags, so I would bet that current OS X
 packages would do the right thing and work with the Ruby 2.0 on Maverick.

 Jeff


 On 01/14/2014 01:15 PM, Khoury wrote:

 Does anyone know what the status is on Mavericks support? Has anyone
 tested it? It's been a while since the public release and Apple's policy of
 forcing new Macs to use Mavericks puts is in a tight spot if we can't get
 Puppet support for the OS.

  Thanks,
 Khoury

 On Friday, November 1, 2013 7:52:24 AM UTC-7, Hannes Juutilainen wrote:

  I don't know anything about the release plan or schedule (perhaps
 someone from Puppet Labs could chime in)… Looks bad though:
 https://projects.puppetlabs.com/issues/21868

  —
 Hannes


  On 1.11.2013, at 15.16, Paul Tötterman paul.to...@gmail.com wrote:

   It's the same issue as this: https://projects.
 puppetlabs.com/issues/18205


  Thank you for digging it up for me. Somehow google just failed me.


 It seems to be fixed already but not included in the current release
 version. Building Puppet and Facter from source resolves this issue so I'd
 expect it to be fixed in near future.


  Are you saying that no official released packages from PuppetLabs work
 on OS X 10.9? And the fix is to be released on Puppet 3.4.0? For which no
 release date is set and there seems to be at least 3.3.2 before 3.4.0 will
 come out.

  Cheers,
 Paul

  --
 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/e86bff0a-72e1-4dc8-a1a2-6878f27b4dc3%
 40googlegroups.com.
 For more options, visit https://groups.google.com/groups/opt_out.


   --
 You received this message because you are subscribed to the Google Groups
 Puppet Users group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to puppet-users+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/puppet-users/68a1f653-66ec-4c31-bfe9-7e5ad7d01426%40googlegroups.com
 .
 For more options, visit https://groups.google.com/groups/opt_out.


  --
 You received this message because you are subscribed to the Google Groups
 Puppet Users group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to puppet-users+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/puppet-users/52D58A95.1090308%40bericotechnologies.com
 .

 For more options, visit https://groups.google.com/groups/opt_out.


  --
 You received this message because you are subscribed to the Google Groups
 Puppet Users group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to puppet-users+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/puppet-users/CAAqoMCYta6Dp684oYbEH3_Kd204%2BiWdzHd3S7n5MCA7CixWUdQ%40mail.gmail.com
 .

 For more options, visit https://groups.google.com/groups/opt_out.




-- 
Matthaus Owens
Release Manager, Puppet Labs

Join us at PuppetConf 2014, September 23-24 in San Francisco

-- 
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/CACD%3DwAc1ge7pKwUT329s4F9ghpq22w7aAeJC%3DS9cEVKpxO7VLA%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] puppet 3.3.2 with ruby 2.1.0

[Matthaus Owens]

Stuart,
How have you installed puppet? Have you installed it for each ruby
you're trying out?

On Fri, Dec 27, 2013 at 2:59 PM, Stuart Cracraft smcracr...@gmail.com wrote:
 Tried ruby 2.0.0 but same:

 # /etc/init.d/puppetmaster start

 Starting puppetmaster:
 /usr/local/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:53:in
 `require': cannot load such file -- pupp\

 et/util/command_line (LoadError)

 from
 /usr/local/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:53:in
 `require'

 from /usr/bin/puppet:3:in `main'

 FAILED

 #


 As Robert Burns said:

   “O, wad some Power the giftie gie us
   To see oursels as others see us!
   It wad frae monie a blunder free us,
   An' foolish notion.”

 --
 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/ef45e361-9e64-4a87-b3f2-725162ab7e85%40googlegroups.com.

 For more options, visit https://groups.google.com/groups/opt_out.



-- 
Matthaus Owens
Release Manager, Puppet Labs

Join us at PuppetConf 2014, September 23-24 in San Francisco

-- 
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/CACD%3DwAcot6-y%3D%3DQxfuhWUnOTmn%3DYLQOZPLp%3DurTyqo7zjKYxsg%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] puppet 3.3.2 with ruby 2.1.0

[Matthaus Owens]

Stuart,
The rpms will install puppet into the load path of the system ruby for
your platform. If you've installed a different ruby, then that new
ruby won't be able to load libraries from your system ruby load path.
For custom ruby use, the 3 main options are install from source,
install from a gem, or roll your own native package with the correct
pathing for the updated ruby's load path.

On Fri, Dec 27, 2013 at 3:12 PM, Stuart Cracraft smcracr...@gmail.com wrote:
 Normal - via PL repo yum install.

 I haven't reinstalled Puppet master and Puppet client for each Ruby
 upgrade/downgrade.


 On Friday, December 27, 2013 3:03:04 PM UTC-8, Matthaus Litteken wrote:

 Stuart,
 How have you installed puppet? Have you installed it for each ruby
 you're trying out?

 On Fri, Dec 27, 2013 at 2:59 PM, Stuart Cracraft smcra...@gmail.com
 wrote:
  Tried ruby 2.0.0 but same:
 
  # /etc/init.d/puppetmaster start
 
  Starting puppetmaster:
  /usr/local/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:53:in
  `require': cannot load such file -- pupp\
 
  et/util/command_line (LoadError)
 
  from
  /usr/local/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:53:in
  `require'
 
  from /usr/bin/puppet:3:in `main'
 
  FAILED
 
  #
 
 
  As Robert Burns said:
 
“O, wad some Power the giftie gie us
To see oursels as others see us!
It wad frae monie a blunder free us,
An' foolish notion.”
 
  --
  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/ef45e361-9e64-4a87-b3f2-725162ab7e85%40googlegroups.com.
 
  For more options, visit https://groups.google.com/groups/opt_out.



 --
 Matthaus Owens
 Release Manager, Puppet Labs

 Join us at PuppetConf 2014, September 23-24 in San Francisco

 --
 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/6e983dbb-fc50-441a-9770-dcbc44f74d17%40googlegroups.com.

 For more options, visit https://groups.google.com/groups/opt_out.



-- 
Matthaus Owens
Release Manager, Puppet Labs

Join us at PuppetConf 2014, September 23-24 in San Francisco

-- 
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/CACD%3DwAekqzVZJVk8VmhFq75KsrNs%2Bm2y%3DJ_8HaxV4Fg1Hy1hOQ%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] puppet-dashboard status report and bottleneck

[Matthaus Owens]

Stuart, googling the rake error you were getting resulted in the following hit:

http://stackoverflow.com/questions/15349869/undefined-method-source-index-for-gemmodule-nomethoderror

Which indicated the version of rubygems is not compatible with the
rails application.

On Mon, Dec 16, 2013 at 10:36 PM, Stuart Cracraft smcracr...@me.com wrote:
 Thanks Ramin.

 A good tip.

 Thank-you.

 On Dec 16, 2013, at 1:49 PM, Ramin K ramin-l...@badapple.net wrote:

 No Ruby Mysql bindings aka the mysql gem.

 http://docs.puppetlabs.com/dashboard/manual/1.2/bootstrapping.html#installing-dependencies

 Ramin

 On 12/16/2013 12:37 PM, Stuart Cracraft wrote:

 And the installed gems and ruby version.

 [root@ca-sna-pm01 puppet-dashboard]# gem list

 *** LOCAL GEMS ***

 actionmailer (3.2.13)

 actionpack (3.2.13)

 activemodel (3.2.13)

 activerecord (3.2.13)

 activeresource (3.2.13)

 activesupport (3.2.13)

 archive-tar-minitar (0.5.2)

 arel (3.0.2)

 builder (3.0.4)

 bundler (1.3.5)

 cgi_multipart_eof_fix (2.5.0)

 columnize (0.3.6)

 daemons (1.1.9)

 erubis (2.7.0)

 fastthread (1.0.7)

 gem_plugin (0.2.3)

 hike (1.2.2)

 i18n (0.6.1)

 journey (1.0.4)

 json (1.8.0)

 mail (2.5.4)

 mime-types (1.23)

 mongrel (1.1.5)

 multi_json (1.7.4)

 polyglot (0.3.3)

 rack (1.4.5)

 rack-cache (1.2)

 rack-ssl (1.3.3)

 rack-test (0.6.2)

 rails (3.2.13)

 railties (3.2.13)

 rake (10.0.4)

 rdoc (3.12.2)

 rgen (0.6.2)

 ruby-json (1.1.2)

 ruby-shadow (2.2.0)

 ruby_core_source (0.1.5)

 rubygems-update (2.0.3)

 shadow (1.1)

 sprockets (2.2.2)

 thor (0.18.1)

 tilt (1.4.1)

 treetop (1.4.12)

 tzinfo (0.3.37)

 [root@ca-sna-pm01 puppet-dashboard]# ruby --version

 ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux]

 [root@ca-sna-pm01 puppet-dashboard]#



 On Monday, December 16, 2013 11:46:04 AM UTC-8, Stuart Cracraft wrote:

I followed:

http://docs.puppetlabs.com/dashboard/manual/1.2/bootstrapping.html
http://docs.puppetlabs.com/dashboard/manual/1.2/bootstrapping.html

and have reached the point after

   puppet dashboard install/configuration
   MySQL server and MySQL client installation/configuration/startup

at

   Preparing Schema

and now receive the error:

   rake RAILS_ENV=production db_migrate
   rake aborted!
   undefined method `source_index' for Gem:Module

   See full trace by running task with --trace

the above was run while connected to /usr/share/puppet-dashboard
where there is a project Rakefile which the above uses.

Any thoughts on the above and how to get past it?

Thanks so much!

 --
 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/ee0f339d-79f4-4622-bd51-3a2872d5aa48%40googlegroups.com.
 For more options, visit https://groups.google.com/groups/opt_out.


 --
 You received this message because you are subscribed to a topic in the
 Google Groups Puppet Users group.
 To unsubscribe from this topic, visit
 https://groups.google.com/d/topic/puppet-users/jXit5cwjA9g/unsubscribe.
 To unsubscribe from this group and all its topics, 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/52AF7562.4050209%40badapple.net.
 For more options, visit https://groups.google.com/groups/opt_out.


 --
 You received this message because you are subscribed to the Google Groups
 Puppet Users group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to puppet-users+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/puppet-users/7129942C-D5D2-4CAE-8456-B8AEBB27C76C%40me.com.

 For more options, visit https://groups.google.com/groups/opt_out.



-- 
Matthaus Owens
Release Manager, Puppet Labs

Join us at PuppetConf 2014, September 23-24 in San Francisco

-- 
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/CACD%3DwAdCpvta%3DQu0Y87G5M-9GZcrMYZjcnVQK9FxwUWYqMq4Tw%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Re: Puppet Dashboard: how to connect?

[Matthaus Owens]

Stuart,
rubygem(rake) is provided by the rubygem-rake package, available in
centos 6 or in the optional channel for rhel 6.

On Fri, Dec 13, 2013 at 9:44 AM, Stuart Cracraft smcracr...@gmail.com wrote:
 yum install puppet-dashboard gives a requirement for dependency resolution:

   Error: Package: puppet-dashboard-1.2.23-1.el6.noarch (puppetlabs)
  Requires: rubygem(rake)

 My question is, how to install rubygem so that puppet-dashboard installs?

 Stuart


 On Friday, December 13, 2013 9:25:55 AM UTC-8, Stuart Cracraft wrote:

 Hi - I run puppet 3.3.2 currently of Open Source Puppet.

 I am looking for anyone who has run Puppet Dashboard.

 How do I connect to the dashboard?

 Stuart

 --
 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/b501fed0-1922-4445-b577-1d212c70970d%40googlegroups.com.

 For more options, visit https://groups.google.com/groups/opt_out.



-- 
Matthaus Owens
Release Manager, Puppet Labs

Join us at PuppetConf 2014, September 23-24 in San Francisco

-- 
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/CACD%3DwAd0RBdHtJ14tkBoStL5xrp-Xe1p1X_UQMovePAGnYSv9Q%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] notify

[Matthaus Owens]

Stuart,
It should be
  somevariable = somevalue,
and not
  $somevariable = somevalue,

On Fri, Nov 22, 2013 at 10:32 AM, Stuart Cracraft smcracr...@gmail.com wrote:

 I did the = as you were posting but still got the same error...

 On Friday, November 22, 2013 10:20:04 AM UTC-8, Ken Barber wrote:

 Missing a  on the line with $somevariable ...? For example it should be:

 node 'somenode' {
   class { 'someclass':
  $somevariable = somevalue,
   }
 }

 On Fri, Nov 22, 2013 at 6:18 PM, Stuart Cracraft smcra...@gmail.com
 wrote:
  In nodes.pp I have:
 
  :
  node 'somenode' {
class { 'someclass':= this is line 12
   $somevariable = somevalue,
}
  }
  :
 
  My intent with this is for the somenode node to have someclass
  define its internal variable somevariable with somevalue.
 
  However, on the agent run, this produces the error in messages:
 
Date/Time Host puppet-agent[pid]: Could not parse for environment
  production: Syntax error at 'somevariable'; expected
  '}' at /etc/puppet/manifests/nodes.pp:12 on node somenode
 
  My question is, where's the syntax error it is complaining about?
 
 
  Stuart
 
  --
  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/7d462dd3-8d8c-480a-bef7-e3264e569382%40googlegroups.com.
  For more options, visit https://groups.google.com/groups/opt_out.

 --
 You received this message because you are subscribed to the Google Groups
 Puppet Users group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to puppet-users+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/puppet-users/64bffdb5-36e5-4b3e-96c4-d0e71e3f5526%40googlegroups.com.

 For more options, visit https://groups.google.com/groups/opt_out.



-- 
Matthaus Owens
Release Manager, Puppet Labs

Join us at PuppetConf 2014, September 23-24 in San Francisco

-- 
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/CACD%3DwAdj%3D2u2uJCjXGMwmg66qHFKUUHEYv7NDv_uB8rZ633cuw%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] group type

[Matthaus Owens]

Stuart,
In the type reference, the members property states that it requires
the 'manages members' feature
(http://docs.puppetlabs.com/references/latest/type.html#group-provider-features),
which is available in the aix, directory service, pw and windows_adsi
providers, but not the ldap or groupadd providers. Which provider is
being used for your group resource?

On Mon, Nov 18, 2013 at 11:15 AM, Stuart Cracraft smcracr...@gmail.com wrote:
 Hi.

 Created:

 class mumble {
   :
   random stuff
   :
 }

 class mumble:grouper inherits mumble {
   group { somegroup:
  name = 'somegroup',
  members = 'user1,user2,user3',
  ensure = present,
  gid = 123,
   }
 }

 After a time, mumble:grouper ran, before I added
 user2, and user3 and /etc/group shows:

   somegroup:x:500:

 but it doesn't show what it should show which is:

   somegroup:x:500:user1,user2,user3

 I verified that user1/2/3 all exist in /etc/passwd.

 My question is, why isn't Puppet making the right memberships?

 Do I misunderstand member?

 Stuart




 --
 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/8585e0e1-5063-47c7-bb8b-5b086df1df1e%40googlegroups.com.
 For more options, visit https://groups.google.com/groups/opt_out.



-- 
Matthaus Owens
Release Manager, Puppet Labs

Join us at PuppetConf 2014, September 23-24 in San Francisco

-- 
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/CACD%3DwAf5W8fsY%2BSzGQA7GH0dgsnjGdiP7Pk1H%2BySTBO%2BJWHJqA%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] group type

[Matthaus Owens]

Stuart,
Unfortunately, that doesn't tell us which provider is being used. A
run with --debug should show which providers are being used.

In a test run using the debug flag on a centos 6 box using the group
resource you provided, I got output which included:
'Debug: /Group[somegroup]: Provider groupadd does not support features
manages_members; not managing attribute members'.

If you post the result of running:

puppet apply --debug --exec group { somegroup:
 name = 'somegroup',
 members = 'user1,user2,user3',
 ensure = present,
 gid = 123,
  }

that would help determine which group provider is being used and why
member management isn't being applied.

On Mon, Nov 18, 2013 at 11:37 AM, Stuart Cracraft smcracr...@gmail.com wrote:

 Just local password file and group files mostly. But some ldap.

 On Monday, November 18, 2013 11:34:50 AM UTC-8, Matthaus Litteken wrote:

 Stuart,
 In the type reference, the members property states that it requires
 the 'manages members' feature

 (http://docs.puppetlabs.com/references/latest/type.html#group-provider-features),
 which is available in the aix, directory service, pw and windows_adsi
 providers, but not the ldap or groupadd providers. Which provider is
 being used for your group resource?

 On Mon, Nov 18, 2013 at 11:15 AM, Stuart Cracraft smcra...@gmail.com
 wrote:
  Hi.
 
  Created:
 
  class mumble {
:
random stuff
:
  }
 
  class mumble:grouper inherits mumble {
group { somegroup:
   name = 'somegroup',
   members = 'user1,user2,user3',
   ensure = present,
   gid = 123,
}
  }
 
  After a time, mumble:grouper ran, before I added
  user2, and user3 and /etc/group shows:
 
somegroup:x:500:
 
  but it doesn't show what it should show which is:
 
somegroup:x:500:user1,user2,user3
 
  I verified that user1/2/3 all exist in /etc/passwd.
 
  My question is, why isn't Puppet making the right memberships?
 
  Do I misunderstand member?
 
  Stuart
 
 
 
 
  --
  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/8585e0e1-5063-47c7-bb8b-5b086df1df1e%40googlegroups.com.
  For more options, visit https://groups.google.com/groups/opt_out.



 --
 Matthaus Owens
 Release Manager, Puppet Labs

 Join us at PuppetConf 2014, September 23-24 in San Francisco

 --
 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/c5535875-e7a5-47cf-8113-96b2ee6e1334%40googlegroups.com.

 For more options, visit https://groups.google.com/groups/opt_out.



-- 
Matthaus Owens
Release Manager, Puppet Labs

Join us at PuppetConf 2014, September 23-24 in San Francisco

-- 
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/CACD%3DwAeyoL6Hpfc%3DoJTC9m9%3DEE_DhDaafRCyoQ8HBBP9rDW62w%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] group type

[Matthaus Owens]

-pm01.mercurytechnology.com.pem]:
 Autorequiring File[/var/lib/puppet/ssl/certs][0m

 [0;36mDebug: /File[/var/log/puppet/http.log]: Autorequiring
 File[/var/log/puppet][0m

 [0;36mDebug: /File[/var/lib/puppet/state/graphs]: Autorequiring
 File[/var/lib/puppet/state][0m

 [0;36mDebug: /File[/var/lib/puppet/ssl/private_keys]: Autorequiring
 File[/var/lib/puppet/ssl][0m

 [0;36mDebug: /File[/var/lib/puppet/ssl]: Autorequiring
 File[/var/lib/puppet][0m

 [0;36mDebug: /File[/var/lib/puppet/state/resources.txt]: Autorequiring
 File[/var/lib/puppet/state][0m



 [0;36mDebug: Finishing transaction 7528421020[0m

 [0;36mDebug: Loaded state in 0.00 seconds[0m

 [0;36mDebug: Loaded state in 0.00 seconds[0m

 [0;32mInfo: Applying configuration version '1384804821'[0m

 [0;36mDebug: /Schedule[daily]: Skipping device resources because running on
 a host[0m

 [0;36mDebug: /Schedule[monthly]: Skipping device resources because running
 on a host[0m

 [0;36mDebug: /Schedule[hourly]: Skipping device resources because running on
 a host[0m

 [0;36mDebug: /Schedule[never]: Skipping device resources because running on
 a host[0m

 [0;36mDebug: /Schedule[weekly]: Skipping device resources because running on
 a host[0m

 [0;36mDebug: /Schedule[puppet]: Skipping device resources because running on
 a host[0m

 [0;36mDebug: Finishing transaction 7527187220[0m

 [0;36mDebug: Storing state[0m

 [0;36mDebug: Stored state in 0.03 seconds[0m

 [mNotice: Finished catalog run in 0.16 seconds[0m

 [0;36mDebug: Using settings: adding file resource 'rrddir':
 'File[/var/lib/puppet/rrd]{:links=:follow, :group=puppet,
 :ensure=:directory, :backup=false, :owner=puppet, :mode=750,
 :loglevel=:debug, :path=/var/lib/puppet/rrd}'[0m

 [0;36mDebug: Finishing transaction 7528357160[0m

 [0;36mDebug: Received report to process from
 ca-sna-pm01.mercurytechnology.com[0m

 [0;36mDebug: Processing report from ca-sna-pm01.mercurytechnology.com with
 processor Puppet::Reports::Store[0m

 [root@ca-sna-pm01 manifests]# [root@ca-sna-pm01 manifests]#
 [root@ca-sna-pm01 manifests]# [root@ca-sna-pm01 manifests]#

 [root@ca-sna-pm01 manifests]#

 [root@ca-sna-pm01 manifests]#

 [root@ca-sna-pm01 manifests]# !eg

 egrep bb /etc/group /etc/passwd

 /etc/group:bb:x:500:

 /etc/passwd:bb:x:500:500:bb:/home/bb:/bin/bash

 [root@ca-sna-pm01 manifests]#




 On Monday, November 18, 2013 11:55:59 AM UTC-8, Matthaus Litteken wrote:

 Stuart,
 Unfortunately, that doesn't tell us which provider is being used. A
 run with --debug should show which providers are being used.

 In a test run using the debug flag on a centos 6 box using the group
 resource you provided, I got output which included:
 'Debug: /Group[somegroup]: Provider groupadd does not support features
 manages_members; not managing attribute members'.

 If you post the result of running:

 puppet apply --debug --exec group { somegroup:
  name = 'somegroup',
  members = 'user1,user2,user3',
  ensure = present,
  gid = 123,
   }

 that would help determine which group provider is being used and why
 member management isn't being applied.

 On Mon, Nov 18, 2013 at 11:37 AM, Stuart Cracraft smcra...@gmail.com
 wrote:
 
  Just local password file and group files mostly. But some ldap.
 
  On Monday, November 18, 2013 11:34:50 AM UTC-8, Matthaus Litteken wrote:
 
  Stuart,
  In the type reference, the members property states that it requires
  the 'manages members' feature
 
 
  (http://docs.puppetlabs.com/references/latest/type.html#group-provider-features),
  which is available in the aix, directory service, pw and windows_adsi
  providers, but not the ldap or groupadd providers. Which provider is
  being used for your group resource?
 
  On Mon, Nov 18, 2013 at 11:15 AM, Stuart Cracraft smcra...@gmail.com
  wrote:
   Hi.
  
   Created:
  
   class mumble {
 :
 random stuff
 :
   }
  
   class mumble:grouper inherits mumble {
 group { somegroup:
name = 'somegroup',
members = 'user1,user2,user3',
ensure = present,
gid = 123,
 }
   }
  
   After a time, mumble:grouper ran, before I added
   user2, and user3 and /etc/group shows:
  
 somegroup:x:500:
  
   but it doesn't show what it should show which is:
  
 somegroup:x:500:user1,user2,user3
  
   I verified that user1/2/3 all exist in /etc/passwd.
  
   My question is, why isn't Puppet making the right memberships?
  
   Do I misunderstand member?
  
   Stuart
  
  
  
  
   --
   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/8585e0e1-5063-47c7-bb8b-5b086df1df1e%40googlegroups.com.
   For more options, visit https://groups.google.com/groups/opt_out.
 
 
 
  --
  Matthaus Owens
  Release Manager, Puppet

[Puppet Users] Re: [Puppet-dev] Announce: Puppet 3.3.2 Available

[Matthaus Owens]

That is because apt is still bringing in 3.3.2 of puppet-common. To install
a specific version using apt you must specify versions for both puppet and
puppet-common. Something like 'apt-get install puppet=3.3.1-1puppetlabs1
puppet-common=3.3.1-1puppetlabs1' should work. Or see the example on
pinning at
http://docs.puppetlabs.com/guides/upgrading.html#apt-pinning-example

On Wednesday, November 13, 2013, LaMs wrote:

 This new version in the apt repository of Ubuntu precise (maybe other
 version of OS too) has problem when specifying a specific version for
 puppet package:
 Step to reproduce:
 1: Install a fresh ubuntu precise from iso
 2: Add puppetlabs repo
  - wget https://apt.puppetlabs.com/puppetlabs-release-precise.deb  dpkg
 -i puppetlabs-release-precise.deb
 3: apt-get install puppet=3.3.1-1puppetlabs1


  --
 You received this message because you are subscribed to the Google Groups
 Puppet Users group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to puppet-users+unsubscr...@googlegroups.com javascript:_e({},
 'cvml', 'puppet-users%2bunsubscr...@googlegroups.com');.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/puppet-users/18011b7b-e4f7-4bbd-ac36-8175281c92b8%40googlegroups.com
 .
 For more options, visit https://groups.google.com/groups/opt_out.



-- 
Matthaus Owens
Release Manager, Puppet Labs

Join us at PuppetConf 2014, September 23-24 in San Francisco

-- 
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/CACD%3DwAe5weDu%2BcHQ_33Cq%3DUnouEOu9K8t-662YFnSbszK_Tqng%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Deployed custom facts with module do not show up

[Matthaus Owens]

/etc/puppet/modules is used for deploying needed providers, functions
and facts to agents during a catalog application. The master uses it
to serve those providers, functions, and facts and if modulepath is
passed to a puppet apply, it will also pluginsync those files to the
puppet libdir. `facter -p` only adds the puppet libdir to its load
path, so facts in the modulepath won't be available.

On Wed, Nov 6, 2013 at 5:27 PM, Sergey Sudakovich sudy...@gmail.com wrote:
 Aha, I see so my puppet libdir is /var/lib/puppet/lib, but why when I
 install a module, it goes into /etc/puppet/modules?


 On Wednesday, November 6, 2013 5:07:39 PM UTC-8, Matthaus Litteken wrote:

 Sergey,
 `facter -p` adds puppet's libdir to the load path to load module based
 facts. When running against a master, facts are pluginsynced into this
 directory prior to facter running. You need to make sure that the
 facter directory from your module is in your puppet libdir (you can
 find out what yours is set to by running `puppet agent --configprint
 libdir`). So if your puppet libdir was /var/lib, your libdir should
 look like the following to ensure custom facts are loaded.

 var
 └── lib
 └── facter
 ├── custom_fact.rb
 ├── license
 │   └── thing.rb
 ├── moar_facts.rb
 ├── other_fact.rb
 └── root_home.rb

 On Wed, Nov 6, 2013 at 1:37 PM, Sergey Sudakovich sud...@gmail.com
 wrote:
  Do deploy the module, I just do this:
  puppet module install -f license-0.1.0.tar.gz
  Then to test, i run
  puppet module list
  /etc/puppet/modules
  └──my-license (v0.1.0)
 
  facter -p gives me the same output and facter with no parameters.
 
 
  On Tuesday, November 5, 2013 5:48:46 PM UTC-8, Matthaus Litteken wrote:
 
  How are you deploying the module? Facter won't load module based facts
  by
  default, you need to use 'facter -p' to have Facter load those facts.
 
  On Tuesday, November 5, 2013, Sergey Sudakovich wrote:
 
  When I deploy a module I wrote with couple of custom facts, those
  facts
  do not show up in factor.
  But when I point FACTORLIB to the directory with those factor, they
  work
  just fine.
  I am running a masterless puppet version 2.7.22 and factor 1.7.1
  The module structure looks like so:
 
  -license
  ---lib
  -facter
  ---license.rb
  ---hardware_serial.rb
  -puppet
 
 
  Any idea what is causing this problem or at least where to start the
  debugging?
 
  --
  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/58f49f57-f55c-425f-b408-1b286336ddb7%40googlegroups.com.
  For more options, visit https://groups.google.com/groups/opt_out.
 
 
 
  --
  Matthaus Owens
  Release Manager, Puppet Labs
 
  Join us at PuppetConf 2014, September 23-24 in San Francisco
 
  --
  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/6aa31c1c-e492-43ae-9d79-e1acc84760a0%40googlegroups.com.
 
  For more options, visit https://groups.google.com/groups/opt_out.



 --
 Matthaus Owens
 Release Manager, Puppet Labs

 Join us at PuppetConf 2014, September 23-24 in San Francisco

 --
 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/6535d35d-aef4-4dce-9675-67c5c44d3e99%40googlegroups.com.

 For more options, visit https://groups.google.com/groups/opt_out.



-- 
Matthaus Owens
Release Manager, Puppet Labs

Join us at PuppetConf 2014, September 23-24 in San Francisco

-- 
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/CACD%3DwAfQyaHO%3D_g8h9pb6EiQJe--%3DS8AQkg1WOgjBqmZq-pcMA%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Deployed custom facts with module do not show up

[Matthaus Owens]

Sergey,
`facter -p` adds puppet's libdir to the load path to load module based
facts. When running against a master, facts are pluginsynced into this
directory prior to facter running. You need to make sure that the
facter directory from your module is in your puppet libdir (you can
find out what yours is set to by running `puppet agent --configprint
libdir`). So if your puppet libdir was /var/lib, your libdir should
look like the following to ensure custom facts are loaded.

var
└── lib
└── facter
├── custom_fact.rb
├── license
│   └── thing.rb
├── moar_facts.rb
├── other_fact.rb
└── root_home.rb

On Wed, Nov 6, 2013 at 1:37 PM, Sergey Sudakovich sudy...@gmail.com wrote:
 Do deploy the module, I just do this:
 puppet module install -f license-0.1.0.tar.gz
 Then to test, i run
 puppet module list
 /etc/puppet/modules
 └──my-license (v0.1.0)

 facter -p gives me the same output and facter with no parameters.


 On Tuesday, November 5, 2013 5:48:46 PM UTC-8, Matthaus Litteken wrote:

 How are you deploying the module? Facter won't load module based facts by
 default, you need to use 'facter -p' to have Facter load those facts.

 On Tuesday, November 5, 2013, Sergey Sudakovich wrote:

 When I deploy a module I wrote with couple of custom facts, those facts
 do not show up in factor.
 But when I point FACTORLIB to the directory with those factor, they work
 just fine.
 I am running a masterless puppet version 2.7.22 and factor 1.7.1
 The module structure looks like so:

 -license
 ---lib
 -facter
 ---license.rb
 ---hardware_serial.rb
 -puppet


 Any idea what is causing this problem or at least where to start the
 debugging?

 --
 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/58f49f57-f55c-425f-b408-1b286336ddb7%40googlegroups.com.
 For more options, visit https://groups.google.com/groups/opt_out.



 --
 Matthaus Owens
 Release Manager, Puppet Labs

 Join us at PuppetConf 2014, September 23-24 in San Francisco

 --
 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/6aa31c1c-e492-43ae-9d79-e1acc84760a0%40googlegroups.com.

 For more options, visit https://groups.google.com/groups/opt_out.



-- 
Matthaus Owens
Release Manager, Puppet Labs

Join us at PuppetConf 2014, September 23-24 in San Francisco

-- 
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/CACD%3DwAfyO8ZyVWr%3DC8GUqv8hW%2B8aSnV6tRfXvuUnp41dVhWmSw%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] HELP!!! puppet-enterprise-3.1.0-el-6-i386 master/agent test fails

[Matthaus Owens]

From that error message it looks like time is not in sync between all of
your machines. Have you run ntpdate on them all (or is ntpd running)?


On Fri, Nov 1, 2013 at 3:11 PM, ssharks2...@gmail.com wrote:



 I installed PE Master on one VM and Agents on two VMs pointing to master .
 Agent1 VM 64 bit works fine , but agent2 VM 32 bit fails with below error.
 Only difference is architecture. One more note both the agent nodes were
 accepted from Dashboard,so master has both the certificates.

 Any help will be greatly appreciated.

 puppet-enterprise-3.1.0-el-6-i386]# puppet agent --test

 Info: Caching certificate for Info: Caching certificate_revocation_list
 for ca Warning: Unable to fetch my node definition, but the agent run will
 continue:

 Warning: SSL_connect returned=1 errno=0 state=SSLv3 read server
 certificate B: certificate verify

 failed: [CRL is not yet valid for /CN=hostname

 Info: Retrieving plugin Error: /File[/var/opt/lib/pe-puppet/lib]: Failed
 to generate additional resources using

 'eval_generate': SSL_connect returned=1 errno=0 state=SSLv3 read server
 certificate B: certificate verify failed: [CRL is not yet valid for /CN=]

 Error: /File[/var/opt/lib/pe-puppet/lib]: Could not evaluate: SSL_connect
 returned=1 errno=0 state=SSLv3 read server certificate B: certificate
 verify failed: [CRL is not yet valid for /CN=] Could not retrieve file
 metadata for puppet:///plugins: SSL_connect returned=1 errno=0 state=SSLv3
 read server certificate B: certificate verify failed: [CRL is not yet valid
 for /CN=]

 Error: Could not retrieve catalog from remote server: SSL_connect
 returned=1 errno=0 state=SSLv3 read server certificate B: certificate
 verify failed: [CRL is not yet valid for /CN=]

 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: [CRL is not yet valid
 for /CN=v]

 Thank you
   http://stackoverflow.com/questions/tagged/puppet

 --
 You received this message because you are subscribed to the Google Groups
 Puppet Users group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to puppet-users+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/puppet-users/5bfa43f6-0f51-4135-9dc9-52fa7d4ab10c%40googlegroups.com
 .
 For more options, visit https://groups.google.com/groups/opt_out.




-- 
Matthaus Owens
Release Manager, Puppet Labs

Join us at PuppetConf 2014, September 23-24 in San Francisco

-- 
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/CACD%3DwAez%3DEL%3DLyMKZ_D%2BdTdOnddj%3D4JqM%2BZpHaKk-TdsGNKE%3Dw%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Deployed custom facts with module do not show up

[Matthaus Owens]

How are you deploying the module? Facter won't load module based facts by
default, you need to use 'facter -p' to have Facter load those facts.

On Tuesday, November 5, 2013, Sergey Sudakovich wrote:

 When I deploy a module I wrote with couple of custom facts, those facts do
 not show up in factor.
 But when I point FACTORLIB to the directory with those factor, they work
 just fine.
 I am running a masterless puppet version 2.7.22 and factor 1.7.1
 The module structure looks like so:

 -license
 ---lib
 -facter
 ---license.rb
 ---hardware_serial.rb
 -puppet


 Any idea what is causing this problem or at least where to start the
 debugging?

 --
 You received this message because you are subscribed to the Google Groups
 Puppet Users group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to puppet-users+unsubscr...@googlegroups.com javascript:_e({},
 'cvml', 'puppet-users%2bunsubscr...@googlegroups.com');.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/puppet-users/58f49f57-f55c-425f-b408-1b286336ddb7%40googlegroups.com
 .
 For more options, visit https://groups.google.com/groups/opt_out.



-- 
Matthaus Owens
Release Manager, Puppet Labs

Join us at PuppetConf 2014, September 23-24 in San Francisco

-- 
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/CACD%3DwAfUsG7POPVR-z9Q%3DPgJWit0iSAk1U6K1LqzsWjZ5qQ6FA%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Virt-what on OEL 5

[Matthaus Owens]

Spencer,
Mentioned on IRC but will mention here as well for completeness.
virt-what is in OEL 5 and 6 latest, so you should be able to pull it
in from that repository. Either enabling latest on just that package
or pulling it into a local repository would do the trick.

HTH

On Thu, Oct 10, 2013 at 1:49 PM, Spencer Krum krum.spen...@gmail.com wrote:
 Hello,

 I'm trying to install facter latest on OEL 5.5 but can't because virt-what
 doesn't appear to be in the oracle repositories or EPEL. Can anyone
 confirm/deny this?

 Thanks,
 Spencer Krum

 --
 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 post to this group, send email to puppet-users@googlegroups.com.
 Visit this group at http://groups.google.com/group/puppet-users.
 For more options, visit https://groups.google.com/groups/opt_out.



-- 
Matthaus Owens
Release Manager, Puppet Labs

Join us at PuppetConf 2014, September 23-24 in San Francisco

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Re: [Puppet-dev] Announce: PuppetDB 1.5.0 Available

[Matthaus Owens]

burji is a hostname for a machine that is no longer in use. I would
rsync using the yum.puppetlabs.com hostname. The following works for
me:

rsync 
rsync://yum.puppetlabs.com/packages/yum/el/5/products/x86_64/puppetdb-1.5.0-1.el5.noarch.rpm
-rw-r--r--20569592 2013/09/30 16:47:20 puppetdb-1.5.0-1.el5.noarch.rpm

Hope that helps.

On Wed, Oct 2, 2013 at 9:03 AM, asq asqu...@gmail.com wrote:
 W dniu wtorek, 1 października 2013 19:11:40 UTC+2 użytkownik Matthaus
 Litteken napisał:

 Sorry about that. Something went awry in the ship of 1.5.0. We've
 updated the apt repos and 1.5.0 is now there for all of the debian and
 ubuntu flavors. And as Ken said, thanks for letting us know!


 it seems that rsync is out of the loop too :(

 -bash-3.2$ GET -deS
 http://yum.puppetlabs.com/el/5/products/x86_64/puppetdb-1.5.0-1.el5.noarch.rpm
 GET
 http://yum.puppetlabs.com/el/5/products/x86_64/puppetdb-1.5.0-1.el5.noarch.rpm
 -- 200 OK
 Connection: close
 Date: Wed, 02 Oct 2013 15:56:26 GMT
 Accept-Ranges: bytes
 ETag: 240711-139ddf8-4e7a274f87200
 Server: Apache
 Content-Length: 20569592
 Content-Type: application/x-redhat-package-manager
 Last-Modified: Mon, 30 Sep 2013 23:47:20 GMT
 Client-Date: Wed, 02 Oct 2013 15:57:04 GMT
 Client-Peer: 198.58.114.168:80
 Client-Response-Num: 1
 X-Frame-Options: SAMEORIGIN

 -bash-3.2$ rsync
 rsync://burji.puppetlabs.com/packages/yum/el/5/products/x86_64/puppetdb-1.5.0-1.el5.noarch.rpm
 rsync: link_stat /yum/el/5/products/x86_64/puppetdb-1.5.0-1.el5.noarch.rpm
 (in packages) failed: No such file or directory (2)
 rsync error: some files/attrs were not transferred (see previous errors)
 (code 23) at main.c(1508) [Receiver=3.0.7]

 --
 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 post to this group, send email to puppet-users@googlegroups.com.
 Visit this group at http://groups.google.com/group/puppet-users.

 For more options, visit https://groups.google.com/groups/opt_out.



-- 
Matthaus Owens
Release Manager, Puppet Labs

Join us at PuppetConf 2014, September 23-24 in San Francisco

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: [Puppet-dev] Announce: PuppetDB 1.5.0 Available

[Matthaus Owens]

/opt_out.

 --
 You received this message because you are subscribed to the Google Groups 
 Puppet Announce group.
 To unsubscribe from this group and stop receiving emails from it, send an 
 email to puppet-announce+unsubscr...@googlegroups.com.
 To post to this group, send email to puppet-annou...@googlegroups.com.
 Visit this group at http://groups.google.com/group/puppet-announce.
 For more options, visit https://groups.google.com/groups/opt_out.



-- 
Matthaus Owens
Release Manager, Puppet Labs

Join us at PuppetConf 2014, September 23-24 in San Francisco

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Announce: Facter 1.7.3 Available

[Matthaus Owens]

Facter 1.7.3 is a bugfix release in the 1.7 series.

To see a list of the issues addressed by this release, check out the
1.7.3 version in our issue tracker at:
https://projects.puppetlabs.com/versions/414

Downloads are available at:
 * Source: https://downloads.puppetlabs.com/facter/facter-1.7.3.tar.gz

RPMs are available at https://yum.puppetlabs.com/el or /fedora

Rubygem available at http://rubygems.org/gems/facter

Debs are available at https://apt.puppetlabs.com

Mac package is available at
https://downloads.puppetlabs.com/mac/facter-1.7.3.dmg

Please report feedback via the Puppet Labs Redmine site, using an
affected version of 1.7.3:
 http://projects.puppetlabs.com/projects/facter/

=
## Facter 1.7.3 Release Notes  ##
=

For the full detail of closed issues specific to 1.7.3 see [this list
in Redmine](http://projects.puppetlabs.com/versions/414), containing
no new features, and 10 bugs closed, the majority for Windows.

Windows Executable External Facts (#22077)

Facter on Windows now supports generating external facts from
executables (.exe, .com, .bat, .ps1). Text
based external facts (.txt) have been supported since 1.7.0. See
http://docs.puppetlabs.com/guides/custom_facts.html#executable-facts-windows
for more information.

Windows IP related Facts (#12116, #16665, #16668, #21518)

Facter on Windows used to gather IP related facts using `netsh`, which
did not work reliably on 2003,
due to a dependency on the Routing and Remote Access service, nor did
it work on non EN_US systems.
Version 1.7.3 has been updated to use WMI, which resolves these
issues. It also adds the `ipaddress6`
fact on systems where this is available.

Fedora 19 (#21762)

Facter packages are now available for Fedora 19.


* 12116: Windows domain and fqdn facts error when there is no domain.
* 16665: [windows] wrong ipaddress with locale != en
* 16668: [windows] ipaddress fact reports hostname
* 20989: Facter 1.7.1 on 32 bit windows reports architecture fact as
i1586, should be x86
* 21518: interface fact not available on windows 2003
* 21533: Facter prints errors to stderr on precise and f18
* 21762: Update facter to support F19
* 22064: Potential Local Escalation issue with Facts.d folder for
executable facts on Windows
* 22077: External Facts Support On Windows
* 22163: Remove hardcoded hostname dependencies from facter

==
## Facter 1.7.3 Changelog  ##
==

Adrien Thebo (2):
  d85a4c1 (refactor) Simplify ipaddress fact specs
  56ce53a (maint) Stub extraneous facts when testing ifconfig

Clément Demonchy (1):
  32fd13a ip address fact that return full ifconfig output

Elias Probst (1):
  d49f646 (#21533) Convert network data to string before access

Josh Cooper (12):
  9be738f (#21533) Verify facter doesn't write to stderr
  995232e Maint: Don't load facts twice during specs
  0ddf001 (#16668) Use WMI to collect macaddress fact
  c3199c7 (#16665) Remove references to netsh
  2ac6cc1 Maint: Simplify how interfaces are enumerated
  9f18629 (#16668) Support IPv6 adapter binding order
  abf0d08 Maint: Update yardocs
  fb3bd3b maint: adding lib to spec path in spec helper
  3ade301 (#16668) Backport WMI changes to per-interface facts
  c128221 Maint: Don't output No facts loaded from during tests
  4e12130 Maint: Clear memory facts now that they are loaded earlier
  5a730af (#12116) Don't break on the first interface

Josh Partlow (3):
  6031275 (maint) Fix mocha expectations crashing facter_spec
  ad902bd (maint) Rakefile loads all the libraries it can.
  65577a4 (maint) Update README with a little bit of spec info.

Matthaus Owens (6):
  9f5bec1 (maint) Clean up install.rb dependencies
  9d04cf5 (maint) Remove openssl dependencies from debian/control file
  3979271 (packaging) Update changelog template with currently
supported debian/ubuntu dists.
  53eeb2a (packaging) Remove createpackage.sh from facter
  a1842d0 (packaging) Remove PackageInfo.plist, it is no longer
used by packaging.
  e7a26cf (packaging) Update FACTERVERSION to 1.7.3

Melissa (3):
  18522b4 (Bug #21762) Update facter to support F19
  77de566 (Bug #22163) remove hardcoded hostname dependencies
  9e79d7c (packaging) Update FACTERVERSION to 1.7.3-rc1

Rob Reynolds (14):
  663c3d3 Adding a windows fact for i686 to architecture specs
  0cb1ff1 (#20989) x86 windows hardware model show i686 not i1586
  11ee819 (Maint) Ignore Gemfile.local
  0a8c231 (#16668) Use WMI to collect IPv4 address
  8ab8b98 (#16668) Use WMI to collect netmask fact
  66d8c80 (#16668) Use WMI to collect IPv6 address
  672efc5 (#21518) Use WMI to collect per-interface facts
  8fc6bd5 (#16668) added windows network spec helper
  47bfb4a (#16668) Only consider NICs that have a binding entry
  aaebc4e (#16668) Ipv6 remove warning
  e056b44 (#21738

[Puppet Users] Announce: Facter 1.7.3-rc1 Available

[Matthaus Owens]

Facter 1.7.3-rc1 is a bugfix release candidate in the 1.7 series.

To see a list of the issues addressed by this release, check out the
1.7.3 version in our issue tracker at:
https://projects.puppetlabs.com/versions/414

Downloads are available at:
 * Source: https://downloads.puppetlabs.com/facter/facter-1.7.3-rc1.tar.gz

RPMs are available at https://yum.puppetlabs.com/el or /fedora

Rubygem available at http://rubygems.org/gems/facter

Debs are available at https://apt.puppetlabs.com

Mac package is available at
https://downloads.puppetlabs.com/mac/facter-1.7.3-rc1.dmg

Please report feedback via the Puppet Labs Redmine site, using an
affected version of 1.7.3-rc1:
 http://projects.puppetlabs.com/projects/facter/


## Facter 1.7.3-rc1 Release Notes  ##


For the full detail of closed issues specific to 1.7.3 see [this list
in Redmine](http://projects.puppetlabs.com/versions/414), containing
no new features, and 10 bugs closed, the majority for Windows.

* 12116: Windows domain and fqdn facts error when there is no domain.
* 16665: [windows] wrong ipaddress with locale != en
* 16668: [windows] ipaddress fact reports hostname
* 20989: Facter 1.7.1 on 32 bit windows reports architecture fact as
i1586, should be x86
* 21518: interface fact not available on windows 2003
* 21533: Facter prints errors to stderr on precise and f18
* 21762: Update facter to support F19
* 22064: Potential Local Escalation issue with Facts.d folder for
executable facts on Windows
* 22077: External Facts Support On Windows
* 22163: Remove hardcoded hostname dependencies from facter

=
## Facter 1.7.3-rc1 Changelog  ##
=

Adrien Thebo (2):
  d85a4c1 (refactor) Simplify ipaddress fact specs
  56ce53a (maint) Stub extraneous facts when testing ifconfig

Clément Demonchy (1):
  32fd13a ip address fact that return full ifconfig output

Elias Probst (1):
  d49f646 (#21533) Convert network data to string before access

Josh Cooper (12):
  9be738f (#21533) Verify facter doesn't write to stderr
  995232e Maint: Don't load facts twice during specs
  0ddf001 (#16668) Use WMI to collect macaddress fact
  c3199c7 (#16665) Remove references to netsh
  2ac6cc1 Maint: Simplify how interfaces are enumerated
  9f18629 (#16668) Support IPv6 adapter binding order
  abf0d08 Maint: Update yardocs
  fb3bd3b maint: adding lib to spec path in spec helper
  3ade301 (#16668) Backport WMI changes to per-interface facts
  c128221 Maint: Don't output No facts loaded from during tests
  4e12130 Maint: Clear memory facts now that they are loaded earlier
  5a730af (#12116) Don't break on the first interface

Josh Partlow (3):
  6031275 (maint) Fix mocha expectations crashing facter_spec
  ad902bd (maint) Rakefile loads all the libraries it can.
  65577a4 (maint) Update README with a little bit of spec info.

Matthaus Owens (5):
  9f5bec1 (maint) Clean up install.rb dependencies
  9d04cf5 (maint) Remove openssl dependencies from debian/control file
  3979271 (packaging) Update changelog template with currently
supported debian/ubuntu dists.
  53eeb2a (packaging) Remove createpackage.sh from facter
  a1842d0 (packaging) Remove PackageInfo.plist, it is no longer
used by packaging.

Melissa (3):
  18522b4 (Bug #21762) Update facter to support F19
  77de566 (Bug #22163) remove hardcoded hostname dependencies
  9e79d7c (packaging) Update FACTERVERSION to 1.7.3-rc1

Rob Reynolds (14):
  663c3d3 Adding a windows fact for i686 to architecture specs
  0cb1ff1 (#20989) x86 windows hardware model show i686 not i1586
  11ee819 (Maint) Ignore Gemfile.local
  0a8c231 (#16668) Use WMI to collect IPv4 address
  8ab8b98 (#16668) Use WMI to collect netmask fact
  66d8c80 (#16668) Use WMI to collect IPv6 address
  672efc5 (#21518) Use WMI to collect per-interface facts
  8fc6bd5 (#16668) added windows network spec helper
  47bfb4a (#16668) Only consider NICs that have a binding entry
  aaebc4e (#16668) Ipv6 remove warning
  e056b44 (#21738) Revert (#2157) Remove support for executable
external facts on Windows
  6423c0d (#21738) Add .cmd / Update PowerShell parser
  26a7691 maint: Refactor Key Value Output Parsers
  b9abdd1 (#12116) Windows domain/fqdn error when no domain

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Announce: Puppet Enterprise 3.0.1 Available [ Security Release ]

[Matthaus Owens]

Dear Puppet Enterprise Users,

Puppet Enterprise 3.0.1 is now available.

Puppet Enterprise version 3.0.1 is a security and maintenance release. All
users of Puppet Enterprise are strongly encouraged to upgrade when possible
to
Puppet Enterprise 3.0.1.  Specifically, the 3.0.1 release includes the
following:

## Complete Upgrader Functionality

The puppet installer script can now be used to upgrade all roles in an
existing
PE deployment: master, agent, console, cloud provisioner, and database
support.
Upgrades are supported for all PE roles running 2.8.2 or later, including
migrating data from a 2.8.2 mySQL instance to the new PostgreSQL instance
used
in PE 3. For complete information and instructions, visit
http://docs.puppetlabs.com/pe/latest/install_upgrading.html

Also included are support for SLES (11 SP1 or higher) and changes and
additions
to Console rake tasks. For details, please read the release notes:
http://docs.puppetlabs.com/pe/latest/appendix.html#release-notes

## Security Patches

Puppet Enterprise 3.0.1 includes fixes to address CVE-2013-4073,
CVE-2013-4761, CVE-2013-4762, CVE-2013-4955, CVE-2013-4956, CVE-2013-4958,
CVE-2013-4959, CVE-2013-4961, CVE-2013-4962, CVE-2013-4963, CVE-2013-4964,
CVE-2013-4967, and CVE-2013-4968

For more information on these vulnerabilities, please visit
http://puppetlabs.com/security, or visit
http://puppetlabs.com/security/cve/cve-2013-4073
http://puppetlabs.com/security/cve/cve-2013-4761
http://puppetlabs.com/security/cve/cve-2013-4762
http://puppetlabs.com/security/cve/cve-2013-4955
http://puppetlabs.com/security/cve/cve-2013-4956
http://puppetlabs.com/security/cve/cve-2013-4958
http://puppetlabs.com/security/cve/cve-2013-4959
http://puppetlabs.com/security/cve/cve-2013-4961
http://puppetlabs.com/security/cve/cve-2013-4962
http://puppetlabs.com/security/cve/cve-2013-4963
http://puppetlabs.com/security/cve/cve-2013-4964
http://puppetlabs.com/security/cve/cve-2013-4967 and
http://puppetlabs.com/security/cve/cve-2013-4968

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.

Thanks,
Matthaus Owens
Puppet Labs

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Announce: Puppet 2.7.23 Available [ Security Release ]

[Matthaus Owens]

Puppet 2.7.23 is now available. 2.7.23 addresses two security
vulnerabilties discovered in the 2.7.x series of Puppet. These
vulnerabilities have been assigned Mitre CVE numbers CVE-2013-4956 and
CVE-2013-4761.

All users of Puppet 2.7.22 and earlier who cannot upgrade to the
current version of Puppet, 3.2.4, are strongly encouraged to upgrade
to 2.7.23.

For more information on these vulnerabilities, please visit
http://puppetlabs.com/security/cve/cve-2013-4761 and
http://puppetlabs.com/security/cve/cve-2013-4956 .

Downloads are available at:
 * Source 
https://downloads.puppetlabs.com/puppet/puppet-2.7.23.tar.gzhttps://downloads.puppetlabs.com/puppet/puppet-2.7.22.tar.gz

Windows package is available at
https://downloads.puppetlabs.com/windows/puppet-2.7.23.msihttps://downloads.puppetlabs.com/windows/puppet-2.7.22.msi

RPMs are available at https://yum.puppetlabs.com/el or /fedora

Debs are available at https://apt.puppetlabs.com

Mac package is available at
https://downloads.puppetlabs.com/mac/puppet-2.7.23.dmghttps://downloads.puppetlabs.com/mac/puppet-2.7.22.dmg

Gems are available via rubygems at
https://rubygems.org/downloads/puppet-2.7.23.gemhttps://rubygems.org/downloads/puppet-2.7.22.gem
or
by using `gem
install puppet --version=2.7.23`

Please report feedback via the Puppet Labs Redmine site, using an
affected puppet version of 2.7.23:
http://projects.puppetlabs.com/projects/puppet/

## Changelog ##

Andrew Parker (9):
  e9b54a0 (Maint) Use dirname instead of regexes
  b0924a3 (Maint) Clean up specs
  88da2ab (#21971) Check for possible directory traversal
  24b18de (#21971) Split import and autoloading code paths
  ee80db0 (#21971) Create system for safely dealing with path patterns
  c0d0339 (#21971) Fix how import_all loads files
  4e00895 (Maint) Confine module tool tests off of windows
  78be1de (Maint) Update expectations for older rspec
  c9f8717 (Maint) Update test to reflect chown using the gid too

Josh Partlow (3):
  18379b6 (#21971) Fixes PathPattern's usage of Dir.glob for Windows
  94cedf7 (#21971) Allow paths that contain .. as part of a name
  ddd8b59 (maint) Fix module_utils regex tests for module file perms

Matthaus Owens (3):
  1e5fc90 (packaging) Update CHANGELOG, PUPPETVERSION for 2.7.23
  b2a77e0 (packaging) Remove oneiric from ext/build_defaults.yaml
  2471c0f (maint) Remove rspec requires from the Rakefile

Pieter van de Bruggen (5):
  90d4180 (#14333) Ensure module permissions are sane.
  f02f186 Backporting acceptance tests.
  23bdf22 Fixing broken requires in the acceptance tests.
  b7a0d29 Ensure that PMT uses the correct group membership.
  27abe7e Improving testing around PMT module install permissions.

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Announce: Puppet 3.2.4 Available [ Security Release ]

[Matthaus Owens]

Puppet 3.2.4 is now available. 3.2.4 addresses two security
vulnerabilties discovered in the 3.x series of Puppet. These
vulnerabilities have been assigned Mitre CVE numbers CVE-2013-4956 and
CVE-2013-4761.

All users of Puppet 3.2.3 and earlier are strongly encouraged to upgrade
to 3.2.4.

For more information on these vulnerabilities, please visit
http://puppetlabs.com/security/cve/cve-2013-4761 and
http://puppetlabs.com/security/cve/cve-2013-4956 .

Downloads are available at:
 * Source 
https://downloads.puppetlabs.com/puppet/puppet-3.2.4.tar.gzhttps://downloads.puppetlabs.com/puppet/puppet-2.7.22.tar.gz

Windows package is available at
https://downloads.puppetlabs.com/windows/puppet-3.2.4.msihttps://downloads.puppetlabs.com/windows/puppet-2.7.22.msi

RPMs are available at https://yum.puppetlabs.com/el or /fedora

Debs are available at https://apt.puppetlabs.com

Mac package is available at
https://downloads.puppetlabs.com/mac/puppet-3.2.4.dmghttps://downloads.puppetlabs.com/mac/puppet-2.7.22.dmg

Gems are available via rubygems at
https://rubygems.org/downloads/puppet-3.2.4.gemhttps://rubygems.org/downloads/puppet-2.7.22.gem
or
by using `gem
install puppet --version=3.2.4`

Please report feedback via the Puppet Labs Redmine site, using an
affected puppet version of 3.2.4:
http://projects.puppetlabs.com/projects/puppet/

## Changelog ##

Andrew Parker (6):
  98e3a38 (Maint) Use dirname instead of regexes
  4b8d0a1 (Maint) Clean up specs
  e7e1be1 (#21971) Check for possible directory traversal
  6547651 (#21971) Split import and autoloading code paths
  d689513 (#21971) Create system for safely dealing with path patterns
  214d42e (Maint) Reinstate check for manifest dir

John Duarte (1):
  c9473a6 (#21953) Add test to verify module permissions

Josh Partlow (5):
  3932e78 (#21971) Fix TypeLoader#import_all on Ruby 1.8.7
  a0f8a32 (#21971) Fixes PathPattern's usage of Dir.glob for Windows
  987c4d5 (#21971) Allow paths that contain .. as part of a name
  c0234fe (maint) Fix windows test for embedded '..' in path
  adff11c (maint) Fix module_utils regex tests for module file perms

Matthaus Owens (4):
  05d20ff (maint) Remove rspec requires from the Rakefile
  a754bc8 (packaging) Move systemd BuildRequires into conditional
  019e443 (maint) Correct type in spling of pl-fedora-18-i386 mock
in ext/build_defaults.yaml
  f55814d (packaging) Update PUPPETVERSION for 3.2.4

Melissa Stone (1):
  ecb0f92 (Bug #21768) Update puppet for F19

Pieter van de Bruggen (4):
  fe7b9f0 (#14333) Ensure module permissions are sane.
  01c69eb Fixing a missed test for minitar.
  f8a9eec Ensure that PMT uses the correct group membership.
  afc9859 Improving testing around PMT module install permissions.

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Announce: Puppet Enterprise 2.8.3 Available [ Security Release ]

[Matthaus Owens]

Dear Puppet Enterprise Users,

Puppet Enterprise 2.8.3 is now available.

This is a security release of Puppet Enterprise. All users of Puppet
Enterprise are strongly encouraged to upgrade when possible to Puppet
Enterprise 2.8.3.

Puppet Enterprise 2.8.3 includes fixes to address CVE-2013-4073,
CVE-2013-4761, and CVE-2013-4956

For more information on these vulnerabilities, please visit
http://puppetlabs.com/security, or visit
http://puppetlabs.com/security/cve/cve-2013-4073
http://puppetlabs.com/security/cve/cve-2013-4761 and
http://puppetlabs.com/security/cve/cve-2013-4956

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.

Thanks,
Matthaus Owens
Puppet Labs

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Fedora 17 leaving yum.puppetlabs.com

[Matthaus Owens]

Fedora 17 reached end of life on 2013-07-30 [1], so we are no longer
building new packages for it and will remove it from our yum
repository on Monday, October 28.

[1] - https://lists.fedoraproject.org/pipermail/announce/2013-July/003169.html

-- 
Matthaus Owens
Release Manager, Puppet Labs

Join us at PuppetConf 2013, August 22-23 in San Francisco -
http://bit.ly/pupconf13
Register now and take advantage of the Final Countdown discount - save 15%!

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Announce: Puppet 3.2.3 Available

[Matthaus Owens]

Puppet 3.2.3 packages are now available for f19 on yum.puppetlabs.com.

On Fri, Jul 19, 2013 at 9:24 AM, Darin Perusich da...@darins.net wrote:
 FWIW Puppet Labs could really simplify the creation of packages for
 linux distributions by leveraging the Open Build Service, formerly
 OpenSUSE Build Service. All you need to do to add a distribution is
 check a box and which architectures and the systems will automagically
 build and deploy the packages for you. For a company that deals in
 automation I'd think such a tool would be right up your alley;-)

 You can find the documentation and software http://openbuildservice.org/

 --
 Later,
 Darin


 On Fri, Jul 19, 2013 at 11:21 AM, Moses Mendoza mo...@puppetlabs.com wrote:
 Hi Justin,

 Yes, I'll try to get those up today.

 Moses

 On Wed, Jul 17, 2013 at 3:37 PM, Justin Brown justin.br...@fandingo.org 
 wrote:
 Moses,

 The Fedora 19 packages have not been updated. Could you issue packages for
 http://yum.puppetlabs.com/fedora/f19/?

 Thanks,
 Justin


 On Mon, Jul 15, 2013 at 2:18 PM, Moses Mendoza mo...@puppetlabs.com wrote:

 3.2.3 is a bugfix release of the Puppet 3.2 series. It fixes some
 Windows bugs introduced in 3.2.0, as well as a few performance
 problems and miscellaneous bugs.

 ===
 ## Puppet 3.2.3 Downloads ##
 ===

 Source: https://downloads.puppetlabs.com/puppet/puppet-3.2.3.tar.gz

 RPM and deb packages available in the Puppet Labs repositories at:
 http://yum.puppetlabs.com and http://apt.puppetlabs.com

 Gems are available via rubygems at
 https://rubygems.org/downloads/puppet-3.2.3.gem
   or by using `gem install puppet`

 Mac package is available at
 https://downloads.puppetlabs.com/mac/puppet-3.2.3.dmg

 Windows package is available at
 https://downloads.puppetlabs.com/windows/puppet-3.2.3.msi

 Please report feedback via the Puppet Labs Redmine site, using an
 affected puppet version of 3.2.3:
 https://projects.puppetlabs.com/projects/puppet/

 
 ## Puppet 3.2.3 Contributors ##
 

 Adrien Thebo, Andrew Parker, Dustin J. Mitchell, Josh Cooper, Josh
 Partlow, Justin Stoller, Matthaus Owens, Moses Mendoza, Nick
 Fagerlund, Patrick Carlisle

 =
 ## Puppet 3.2.3 Release Notes ##
 =

 ### Windows Fixes

 This release fixes several Windows bugs that couldn't be targeted for
 earlier 3.2 releases.

 * [#20768: windows user provider can not manage password or home
 directory](https://projects.puppetlabs.com/issues/20768) --- This was
 a regression in 3.2.0/3.2.1.
 * [#21043: setting in puppet.conf ignored on Windows in Puppet
 3.2.1](https://projects.puppetlabs.com/issues/21043) --- This was a
 regression in 3.2.0/3.2.1.
 * [#16080: Service provider broken in Windows Server
 2012](https://projects.puppetlabs.com/issues/16080) --- This affected
 all previous Puppet versions.
 * [#20787: 'puppet resource group' takes incredibly long on
 Windows](https://projects.puppetlabs.com/issues/20787) --- This
 affected all previous Puppet versions.
 * [#20302: Windows File.executable? now returns false on ruby
 1.9](https://projects.puppetlabs.com/issues/20302)
 * [#21280: Don't create c:\dev\null in windows
 specs](https://projects.puppetlabs.com/issues/21280) --- This was only
 relevant to Puppet developers.

 ### Logging and Reporting Fixes

 * [#20383: Bring back helpful error messages like prior to Puppet
 3](https://projects.puppetlabs.com/issues/20383) --- This was a
 regression from 3.0.0, which caused file names and line numbers to
 disappear from duplicate resource declaration errors.
 * [#20900: tagmail triggers in --onetime mode without changes after
 upgrade from 3.1.1 to
 3.2.1](https://projects.puppetlabs.com/issues/20900) --- This was a
 regression in 3.2.0/3.2.1.
 * [#20919: Logging behaviour issues in
 3.2.1](https://projects.puppetlabs.com/issues/20919) --- This was a
 regression in 3.2.0/3.2.1, which caused noisy logging to the console
 even if the `--logdest` option was set.

 ### Performance Fixes

 * [#21376: Stack level too deep after updating from 3.1.1 to
 3.2.2](https://projects.puppetlabs.com/issues/21376) --- This would
 sometimes cause total failures when importing a large number of
 manifest files (such as with the `import nodes/*.pp` idiom).
 * [#21320: Puppet daemon may sleep for 100 years after receiving USR1
 on 64 bit systems](https://projects.puppetlabs.com/issues/21320) ---
 MCollective's Puppet plugin uses puppet agent's USR1 signal to trigger
 a run if the agent is running; on 64-bit systems, this could cause
 puppet agent to keep running, but stop doing scheduled configuration
 runs. This was caused by a bug in Ruby \ 2.0, but we modified Puppet
 to work around it.
 * [#20901: `puppet --version` is unnecessarily
 slow](https://projects.puppetlabs.com/issues/20901) --- This was a
 regression in 3.2.0/3.2.1.

 ### Misc Fixes

 * [#21264: parser = future breaks executing functions

Re: [Puppet Users] facter 1.6.18 tarball has a dangerous mac preflight script

[Matthaus Owens]

Clay,
I've opened a pull to address this issue. We have long since stopped
using the createpackage.sh task internally for building apple packages
and instead use our shared rake tasks. Specifically, `rake
package:bootstrap` followed by `rake package:apple` is how we build
packages internally for release.

On Mon, Jul 15, 2013 at 9:38 AM, Clay Caviness ccavin...@gmail.com wrote:
 The facter 1.6.18 tarball has many issues. First, the
 ext/osx/createpackage.sh script still uses packagemaker, which is
 deprecated. And even if it used that, there are a few references to files in
 the now-deleted conf/osx/ directory.

 So it's pretty difficult to create a Mac pkg from this, but after some
 tweaking of the createpackage.sh script, I managed to do it! I ran the
 package it created, and noticed the preflight script was taking a long
 time to run. I looked at it, and ...

 Well, here is the last two lines of the preflight as shipped in the tarball:
 $ tail -2 ext/osx/preflight
 # remove old doc files
 /bin/rm -Rf ${3}/

 Pop quiz for everyone: what could go wrong here? I'll give a hint, when
 installing a Mac package, $3 is set to the path of the target install
 volume.

 Looking at the source in git, I'm not sure how this preflight got into this
 state; all the packaging stuff is currently a mess (both facter and puppet
 are still using the long-deprecated packagemaker tool, among other issues).

 Anyway, thankfully I caught this before it killed my local home, but I did
 have to re-image.

 (Filed http://projects.puppetlabs.com/issues/21760 with the contents of this
 email, as well.)

 --
 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 post to this group, send email to puppet-users@googlegroups.com.
 Visit this group at http://groups.google.com/group/puppet-users.
 For more options, visit https://groups.google.com/groups/opt_out.





-- 
Matthaus Owens
Release Manager, Puppet Labs

Join us at PuppetConf 2013, August 22-23 in San Francisco -
http://bit.ly/pupconf13
Register now and take advantage of the Early Bird discount - save 25%!

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Announce: Facter 1.7.2 Available

[Matthaus Owens]

Facter 1.7.2 is a bugfix release in the 1.7 series.

To see a list of the issues addressed by this release, check out the
1.7.2 version in our issue tracker at:
https://projects.puppetlabs.com/versions/403

Downloads are available at:
 * Source: https://downloads.puppetlabs.com/facter/facter-1.7.2.tar.gz

RPMs are available at https://yum.puppetlabs.com/el or /fedora

Rubygem available at http://rubygems.org/gems/facter

Debs are available at https://apt.puppetlabs.com

Mac package is available at
https://downloads.puppetlabs.com/mac/facter-1.7.2.dmg

Please report feedback via the Puppet Labs Redmine site, using an
affected version of 1.7.2:
 http://projects.puppetlabs.com/projects/facter/

=
## Facter 1.7.2 Bug Fixes ##
=

(#14522) Invalid byte sequence message for virtual fact on Solaris 10 x86_64

The previous attempt fix this issue did not handle the case where the
data being read from /proc/self/status was already UTF-8 encoded,
resulting in 'Could not retrieve virtual: invalid byte sequence in
US-ASCII' messages to still occur.


(#19764) Linux ipaddress not captured according to documentation

Previously, if the ipconfig command listed the loopback address first,
then facter on linux would report the ipaddress fact as nil. Now,
facter will continue looking and report on the first non 127.0.0.0/8
subnetted IP it finds.


(#20229) Network facts not working on Archlinux with net-tools 1.60

Previously, the ipconfig command with net-tools 1.60 output the
netmask differently causing facter's regular expression matching to
fail. As a result, the global netmask and per-interface netmask_*
facts were nil on Archlinux.


(#20236) Refactor the virtual fact

Previously, if Facter executed lspci and was unable to determine the
virtual platform from the output, dmidecode wass never consulted. Now
dmidecode is always consulted regardless of whether lspci is present
or not.


(#20915) Invalid byte sequence message for virtual fact on Linux

Previously, Facter was reading DMI entries from sysfs and interpreting
it as an encoded string, resulting in 'Could not retrieve virtual:
invalid byte sequence in US-ASCII' messages to occur. Now, Facter
reads the data as binary.


(#20938) Domain facter print spurious warnings to stderr

Previously, if the host and domain information of a system was wrong,
then Facter would output warnings to stderr as a result of executing
hostname and dnsdomainname commands. Now Facter suppresses these
warnings.


(#20321) Facter::Util::Resolution::exec should be more descriptive
when complaining about shell built-ins

Previously, if Facter output a deprecation warning about shell
builtins on Windows, it did not specify which command triggered the
problem. Now Facter includes the command that triggered the warning.

=
## Facter 1.7.2 Changelog ##
=

Adrien Thebo (2):
  d4fb548 (maint) Use RSpec 2.9 expectations
  3f2e478 (maint) Use RSpec 2.9 expectations

Andrew Parker (4):
  f2a1923 (Maint) Remove whitespace errors
  1204033 (#20938) Ignore stderr from domain commands
  9c0cc1e (Maint) Remove duplication in domain tests
  a164fe3 (#20915) Read dmi entries as binary data

Jeff McCune (9):
  819c8db (#14522) Force /proc/self/status encoding to valid UTF-8 (try 2)
  db5281e (#20236) Add example that reproduces dmidecode issue
  ef8db18 (#20236) Refactor the virtual fact and fix dmidecode
  c3a47a5 (#19764) Fix ipaddress issue scanning beyond the first address
  b858297 (maint) Move facter.gemspec to .gemspec
  28408fb (maint) Make facter gemspec report correct version
  d249246 (#20229) Fix per-interface netmask_* facts with net-tools 1.60
  928b7e8 (#20229) Fix netmask fact with Linux net-tools 1.60
  423a3bc (maint) De-duplicate parses RSpec alias

Josh Cooper (2):
  35af4ce (#20301) Handle different error in ruby 1.9
  0da8bd7 (#20301) Handle different error in ruby 1.9

Matthaus Owens (3):
  1ad5ba7 (packaging) Add raring to the default cows list
  e8590a6 (packaging) Remove f16 from mocks to build as it is EOL
  4b3a085 (packaging) Update FACTERVERSION to 1.7.2-rc1
  2027595 (packaging) Update FACTERVERSION to 1.7.2

Moses Mendoza (2):
  2029359 (packaging) Use the packaging loader for tasks
  9ad6dea (packaging) Remove Ubuntu Oneiric from build targets

Stefan Schulte (1):
  e5b8cd5 (#20321) Be more descriptive in deprecation message

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Packages on fedora19

[Matthaus Owens]

Brian,
Yes, there have been some changes to ruby in fedora 19. We will
probably need to tweak the spec we build against before we will get a
clean build on f19. There are some details here:
http://fedoraproject.org/wiki/Features/Ruby_2.0.0#New_Packaging_Guidelines
and http://fedoraproject.org/wiki/Packaging:Ruby

On Wed, Jul 3, 2013 at 4:44 PM, Brian Pitts br...@polibyte.com wrote:
 I tried an installation earlier today and received this error:

 Resolving Dependencies
 -- Running transaction check
 --- Package puppet.noarch 0:3.2.2-1.fc18 will be installed
 -- Processing Dependency: ruby(abi) = 1.8 for package:
 puppet-3.2.2-1.fc18.noarch
 -- Processing Dependency: ruby-rgen for package: puppet-3.2.2-1.fc18.noarch
 -- Running transaction check
 --- Package puppet.noarch 0:3.2.2-1.fc18 will be installed
 -- Processing Dependency: ruby(abi) = 1.8 for package:
 puppet-3.2.2-1.fc18.noarch
 --- Package ruby-rgen.noarch 0:0.6.5-1.fc18 will be installed
 -- Finished Dependency Resolution
 Error: Package: puppet-3.2.2-1.fc18.noarch (puppetlabs-products)
Requires: ruby(abi) = 1.8

 It looks like there's no package providing ruby(api).

 $ repoquery --whatprovides 'ruby(abi)'
 $ repoquery --provides ruby
 ruby = 2.0.0.247-11.fc19
 ruby(runtime_executable) = 2.0.0
 ruby(x86-32) = 2.0.0.247-11.fc19
 ruby = 2.0.0.247-11.fc19
 ruby(runtime_executable) = 2.0.0
 ruby(x86-64) = 2.0.0.247-11.fc19
 $ repoquery --provides ruby-libs
 libruby.so.2.0
 ruby(release) = 2.0.0
 ruby-libs = 2.0.0.247-11.fc19
 ruby-libs(x86-32) = 2.0.0.247-11.fc19
 libruby.so.2.0()(64bit)
 ruby(release) = 2.0.0
 ruby-libs = 2.0.0.247-11.fc19
 ruby-libs(x86-64) = 2.0.0.247-11.fc19



 On 07/03/2013 06:24 PM, Pete Brown wrote:

 I was just wondering the same thing.
 My dev environment runs in Fedora 18 and I almost upgraded yesterday
 but thought some testing was in order first.

 I am likely to do what I did last time and try installing the versions
 from the previous release.
 I will be running up a Fedora 19 vm and install puppet from the Fedora
 18 repo shortly and will let you know how it goes.

 If I can find srpms I may rebuild them and see how that goes. :)

 On 4 July 2013 06:04, Tony G. tony...@gmail.com wrote:

 Howdy!

 Probably this is being worked but just throwing it out there as f19 is
 already out, I guess the package for it will be soon available on
 http://yum.puppetlabs.com/fedora/ ?

 Thanks!

 --
 Tony
 http://tonyskapunk.net

 --
 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 post to this group, send email to puppet-users@googlegroups.com.
 Visit this group at http://groups.google.com/group/puppet-users.
 For more options, visit https://groups.google.com/groups/opt_out.




 --
 All the best,
 Brian Pitts


 --
 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 post to this group, send email to puppet-users@googlegroups.com.
 Visit this group at http://groups.google.com/group/puppet-users.
 For more options, visit https://groups.google.com/groups/opt_out.





-- 
Matthaus Owens
Release Manager, Puppet Labs

Join us at PuppetConf 2013, August 22-23 in San Francisco -
http://bit.ly/pupconf13
Register now and take advantage of the Early Bird discount - save 25%!

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Packages on fedora19

[Matthaus Owens]

We will be working to add fedora 19 support to yum.puppetlabs.com in
the coming month, and will probably have current packages built for
f19 next week. I'll respond back to this thread when they are all
ready.

On Wed, Jul 3, 2013 at 4:24 PM, Pete Brown rendhal...@gmail.com wrote:
 I was just wondering the same thing.
 My dev environment runs in Fedora 18 and I almost upgraded yesterday
 but thought some testing was in order first.

 I am likely to do what I did last time and try installing the versions
 from the previous release.
 I will be running up a Fedora 19 vm and install puppet from the Fedora
 18 repo shortly and will let you know how it goes.

 If I can find srpms I may rebuild them and see how that goes. :)

 On 4 July 2013 06:04, Tony G. tony...@gmail.com wrote:
 Howdy!

 Probably this is being worked but just throwing it out there as f19 is
 already out, I guess the package for it will be soon available on
 http://yum.puppetlabs.com/fedora/ ?

 Thanks!

 --
 Tony
 http://tonyskapunk.net

 --
 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 post to this group, send email to puppet-users@googlegroups.com.
 Visit this group at http://groups.google.com/group/puppet-users.
 For more options, visit https://groups.google.com/groups/opt_out.



 --
 You received this message because you are subscribed to the Google Groups 
 Puppet Users group.
 To unsubscribe from this group and stop receiving emails from it, send an 
 email to puppet-users+unsubscr...@googlegroups.com.
 To post to this group, send email to puppet-users@googlegroups.com.
 Visit this group at http://groups.google.com/group/puppet-users.
 For more options, visit https://groups.google.com/groups/opt_out.





-- 
Matthaus Owens
Release Manager, Puppet Labs

Join us at PuppetConf 2013, August 22-23 in San Francisco -
http://bit.ly/pupconf13
Register now and take advantage of the Early Bird discount - save 25%!

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Announce: Puppet 2.7.22 Available [ Security Release ]

[Matthaus Owens]

Puppet 2.7.22 is now available. 2.7.22 addresses a security
vulnerability discovered in the 2.7.x series of Puppet. This
vulnerability has been assigned Mitre CVE number CVE-2013-3567.

All users of Puppet 2.7.21 and earlier who cannot upgrade to the
current version of Puppet, 3.2.2, are strongly encouraged to upgrade
to 2.7.22.

For more information on this vulnerability, please visit
http://puppetlabs.com/security/cve/cve-2013-3567.

Thanks to Ben Murphy, for discovering and responsibly disclosing the
vulnerability.

Downloads are available at:
 * Source https://downloads.puppetlabs.com/puppet/puppet-2.7.22.tar.gz

Windows package is available at
https://downloads.puppetlabs.com/windows/puppet-2.7.22.msi

RPMs are available at https://yum.puppetlabs.com/el or /fedora

Debs are available at https://apt.puppetlabs.com

Mac package is available at
https://downloads.puppetlabs.com/mac/puppet-2.7.22.dmg

Gems are available via rubygems at
https://rubygems.org/downloads/puppet-2.7.22.gem or by using `gem
install puppet --version=2.7.22`

See the Verifying Puppet Download section at:
https://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet

Please report feedback via the Puppet Labs Redmine site, using an
affected puppet version of 2.7.22:
http://projects.puppetlabs.com/projects/puppet/

## Changelog ##

Justin Stoller (1):
  fea3cb6 Improve CVE 2013 1654 SSLv2 Downgrade Master test

Matthaus Owens (3):
  96be982 (packaging) Update build_defaults to remove EOL
platforms (natty, f15, f16).
  7f40007 (packaging) Update debian build-depends to be ruby1.8 so
that the shebang is correct after install and ruby1.9.1 isn't used on
newer debians.
  e160e99 (packaging) Update CHANGELOG, PUPPETVERSION for 2.7.22

Moses Mendoza (1):
  ba8c021 [packaging] Update mocks for rpmbuilder mock format

Patrick Carlisle (7):
  788fdaf Don't keep Gemfile.lock checked in.
  535da9b Add acceptance test for report processing
  2333fa4 Add vendoring system into puppet
  ee741eb Fix installation of vendored libs
  e8c30cb Vendor safe_yaml 0.9.2
  5926d1a (#20584) Only deserialize expected objects from YAML
  fd758ad Remove acceptance test for yaml parsing that was no longer valid

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Announce: Puppet 3.2.2 Available [ Security Release ]

[Matthaus Owens]

Puppet 3.2.2 is now available. 3.2.2 addresses a security
vulnerability discovered in the 3.x series of Puppet. This
vulnerability has been assigned Mitre CVE number CVE-2013-3567.

All users of Puppet 3.2.1 and earlier are strongly encouraged to
upgrade to 3.2.2.

For more information on this vulnerability, please visit
http://puppetlabs.com/security/cve/cve-2013-3567.

Thanks to Ben Murphy, for discovering and responsibly disclosing the
vulnerability.

Downloads are available at:
 * Source https://downloads.puppetlabs.com/puppet/puppet-3.2.2.tar.gz

Windows package is available at
https://downloads.puppetlabs.com/windows/puppet-3.2.2.msi

RPMs are available at https://yum.puppetlabs.com/el or /fedora

Debs are available at https://apt.puppetlabs.com

Mac package is available at
https://downloads.puppetlabs.com/mac/puppet-3.2.2.dmg

Gems are available via rubygems at
https://rubygems.org/downloads/puppet-3.2.2.gem or by using `gem
install puppet --version=3.2.2`

See the Verifying Puppet Download section at:
https://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet

Please report feedback via the Puppet Labs Redmine site, using an
affected puppet version of 3.2.2:
http://projects.puppetlabs.com/projects/puppet/

## Changelog ##

Matthaus Owens (1):
  a6c08f9 (packaging) Update PUPPETVERSION to 3.2.2

Patrick Carlisle (6):
  81eeace Add acceptance test for report processing
  6a29171 Add vendoring system into puppet
  40f2744 Fix installation of vendored libs
  6f1b979 Vendor safe_yaml 0.9.2
  ce50d4a (#20584) Only deserialize expected objects from YAML
  d06e1df Remove acceptance test for yaml parsing that was no longer valid

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Announce: Puppet Enterprise 2.8.2 Available [ Security Release ]

[Matthaus Owens]

Dear Puppet Enterprise Users,

Puppet Enterprise 2.8.2 is now available.

This is a security release of Puppet Enterprise. All users of Puppet
Enterprise are strongly encouraged to upgrade when possible to Puppet
Enterprise 2.8.2.

Puppet Enterprise 2.8.2 includes fixes to address CVE-2013-3567.

For more information on this vulnerability, please visit
http://puppetlabs.com/security/cve/cve-2013-3567.

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.

Thanks,
Matthaus Owens
Puppet Labs

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] ruby issue

[Matthaus Owens]

 this group and stop receiving emails from it, send an 
 email to puppet-users+unsubscr...@googlegroups.com.
 To post to this group, send email to puppet-users@googlegroups.com.
 Visit this group at http://groups.google.com/group/puppet-users?hl=en.
 For more options, visit https://groups.google.com/groups/opt_out.





-- 
Matthaus Owens
Release Manager, Puppet Labs

Join us at PuppetConf 2013, August 22-23 in San Francisco -
http://bit.ly/pupconf13
Register now and take advantage of the Early Bird discount - save 25%!

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] ruby issue

[Matthaus Owens]

 will be updated

 --- Package libselinux-utils.x86_64 0:2.0.94-5.3.el6_4.1 will be an

 --- update Package puppet.noarch 0:3.2.1-1.el6 will be installed

 -- Processing Dependency: ruby-augeas for package:

 -- puppet-3.2.1-1.el6.noarch Processing Dependency: ruby-rgen for

 -- package: puppet-3.2.1-1.el6.noarch Processing Dependency:

 -- ruby-shadow for package: puppet-3.2.1-1.el6.noarch Finished

 -- Dependency Resolution

 Error: Package: puppet-3.2.1-1.el6.noarch (puppetlabs)

Requires: ruby-augeas

 Error: Package: hiera-1.2.1-1.el6.noarch (puppetlabs)

Requires: rubygem-json

 Error: Package: puppet-3.2.1-1.el6.noarch (puppetlabs)

Requires: ruby-rgen

 Error: Package: puppet-3.2.1-1.el6.noarch (puppetlabs)

Requires: ruby-shadow

  You could try using --skip-broken to work around the problem  You could try
 running: rpm -Va --nofiles --nodigest

 [root@ca-sna-pm01 rubygems-1.8.25]#



 --Stuart

 --
 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 post to this group, send email to puppet-users@googlegroups.com.
 Visit this group at http://groups.google.com/group/puppet-users?hl=en.
 For more options, visit https://groups.google.com/groups/opt_out.





-- 
Matthaus Owens
Release Manager, Puppet Labs

Join us at PuppetConf 2013, August 22-23 in San Francisco -
http://bit.ly/pupconf13
Register now and take advantage of the Early Bird discount - save 25%!

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Re: ruby issue

[Matthaus Owens]

Stuart,
rubygems comes from the redhat optional repo, so you'll need to have
that repo enabled to get the rubygems package.

On Fri, May 31, 2013 at 10:59 AM, Stuart Cracraft smcracr...@gmail.com wrote:
 Okay, things are better but I am getting this error for json and rubygems.


 [root@ca-sna-pm01 augeas-1.0.0]# gem install json

 Building native extensions.  This could take a while...

 Successfully installed json-1.8.0

 1 gem installed

 Installing ri documentation for json-1.8.0...

 Installing RDoc documentation for json-1.8.0...

 [root@ca-sna-pm01 augeas-1.0.0]# yum install puppet-server

 Loaded plugins: product-id, rhnplugin, security, subscription-manager

 This system is not registered to Red Hat Subscription Management. You can
 use subscription-manager to register.

 This system is receiving updates from RHN Classic or RHN Satellite.

 Setting up Install Process

 Resolving Dependencies

 -- Running transaction check

 --- Package puppet-server.noarch 0:3.2.1-1.el6 will be installed

 -- Processing Dependency: puppet = 3.2.1-1.el6 for package:
 puppet-server-3.2.1-1.el6.noarch

 -- Running transaction check

 --- Package puppet.noarch 0:3.2.1-1.el6 will be installed

 -- Processing Dependency: facter = 1.6.11 for package:
 puppet-3.2.1-1.el6.noarch

 -- Processing Dependency: hiera = 1.0.0 for package:
 puppet-3.2.1-1.el6.noarch

 -- Processing Dependency: ruby(selinux) for package:
 puppet-3.2.1-1.el6.noarch

 -- Processing Dependency: ruby-augeas for package:
 puppet-3.2.1-1.el6.noarch

 -- Processing Dependency: ruby-rgen for package: puppet-3.2.1-1.el6.noarch

 -- Processing Dependency: ruby-shadow for package:
 puppet-3.2.1-1.el6.noarch

 -- Running transaction check

 --- Package facter.i386 1:1.7.1-1.el6 will be installed

 --- Package hiera.noarch 0:1.2.1-1.el6 will be installed

 -- Processing Dependency: rubygem-json for package:
 hiera-1.2.1-1.el6.noarch

 --- Package libselinux-ruby.x86_64 0:2.0.94-5.3.el6_4.1 will be installed

 -- Processing Dependency: libselinux = 2.0.94-5.3.el6_4.1 for package:
 libselinux-ruby-2.0.94-5.3.el6_4.1.x86_64

 --- Package ruby-augeas.x86_64 0:0.4.1-1.el6 will be installed

 --- Package ruby-rgen.noarch 0:0.6.2-1.el6 will be installed

 --- Package ruby-shadow.x86_64 0:1.4.1-13.el6 will be installed

 -- Running transaction check

 --- Package libselinux.x86_64 0:2.0.94-5.3.el6 will be updated

 -- Processing Dependency: libselinux = 2.0.94-5.3.el6 for package:
 libselinux-utils-2.0.94-5.3.el6.x86_64

 --- Package libselinux.x86_64 0:2.0.94-5.3.el6_4.1 will be an update

 --- Package rubygem-json.x86_64 0:1.5.5-1.el6 will be installed

 -- Processing Dependency: rubygems for package:
 rubygem-json-1.5.5-1.el6.x86_64

 -- Running transaction check

 --- Package libselinux-utils.x86_64 0:2.0.94-5.3.el6 will be updated

 --- Package libselinux-utils.x86_64 0:2.0.94-5.3.el6_4.1 will be an update

 --- Package rubygem-json.x86_64 0:1.5.5-1.el6 will be installed

 -- Processing Dependency: rubygems for package:
 rubygem-json-1.5.5-1.el6.x86_64

 -- Finished Dependency Resolution

 Error: Package: rubygem-json-1.5.5-1.el6.x86_64 (puppetlabs-deps)

Requires: rubygems

 You could try using --skip-broken to work around the problem

 You could try running: rpm -Va --nofiles --nodigest

 [root@ca-sna-pm01 augeas-1.0.0]#



 --
 You received this message because you are subscribed to the Google Groups
 Puppet Users group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to puppet-users+unsubscr...@googlegroups.com.
 To post to this group, send email to puppet-users@googlegroups.com.
 Visit this group at http://groups.google.com/group/puppet-users?hl=en.
 For more options, visit https://groups.google.com/groups/opt_out.





-- 
Matthaus Owens
Release Manager, Puppet Labs

Join us at PuppetConf 2013, August 22-23 in San Francisco -
http://bit.ly/pupconf13
Register now and take advantage of the Early Bird discount - save 25%!

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Re: ruby issue

[Matthaus Owens]

I don't have a rhel box handy to enable that repo on, but here's the
top google hit.

https://access.redhat.com/site/documentation/en-US/Red_Hat_Subscription_Management/1.0/html/Subscription_Management_Guide/entitlements-and-yum.html

On Fri, May 31, 2013 at 11:57 AM, Stuart Cracraft smcracr...@me.com wrote:
 Can you copy/paste the repo entry which works for you in reply?

 On May 31, 2013, at 11:50 AM, Matthaus Owens matth...@puppetlabs.com wrote:

 Stuart,
 rubygems comes from the redhat optional repo, so you'll need to have
 that repo enabled to get the rubygems package.

 On Fri, May 31, 2013 at 10:59 AM, Stuart Cracraft smcracr...@gmail.com 
 wrote:
 Okay, things are better but I am getting this error for json and rubygems.


 [root@ca-sna-pm01 augeas-1.0.0]# gem install json

 Building native extensions.  This could take a while...

 Successfully installed json-1.8.0

 1 gem installed

 Installing ri documentation for json-1.8.0...

 Installing RDoc documentation for json-1.8.0...

 [root@ca-sna-pm01 augeas-1.0.0]# yum install puppet-server

 Loaded plugins: product-id, rhnplugin, security, subscription-manager

 This system is not registered to Red Hat Subscription Management. You can
 use subscription-manager to register.

 This system is receiving updates from RHN Classic or RHN Satellite.

 Setting up Install Process

 Resolving Dependencies

 -- Running transaction check

 --- Package puppet-server.noarch 0:3.2.1-1.el6 will be installed

 -- Processing Dependency: puppet = 3.2.1-1.el6 for package:
 puppet-server-3.2.1-1.el6.noarch

 -- Running transaction check

 --- Package puppet.noarch 0:3.2.1-1.el6 will be installed

 -- Processing Dependency: facter = 1.6.11 for package:
 puppet-3.2.1-1.el6.noarch

 -- Processing Dependency: hiera = 1.0.0 for package:
 puppet-3.2.1-1.el6.noarch

 -- Processing Dependency: ruby(selinux) for package:
 puppet-3.2.1-1.el6.noarch

 -- Processing Dependency: ruby-augeas for package:
 puppet-3.2.1-1.el6.noarch

 -- Processing Dependency: ruby-rgen for package: puppet-3.2.1-1.el6.noarch

 -- Processing Dependency: ruby-shadow for package:
 puppet-3.2.1-1.el6.noarch

 -- Running transaction check

 --- Package facter.i386 1:1.7.1-1.el6 will be installed

 --- Package hiera.noarch 0:1.2.1-1.el6 will be installed

 -- Processing Dependency: rubygem-json for package:
 hiera-1.2.1-1.el6.noarch

 --- Package libselinux-ruby.x86_64 0:2.0.94-5.3.el6_4.1 will be installed

 -- Processing Dependency: libselinux = 2.0.94-5.3.el6_4.1 for package:
 libselinux-ruby-2.0.94-5.3.el6_4.1.x86_64

 --- Package ruby-augeas.x86_64 0:0.4.1-1.el6 will be installed

 --- Package ruby-rgen.noarch 0:0.6.2-1.el6 will be installed

 --- Package ruby-shadow.x86_64 0:1.4.1-13.el6 will be installed

 -- Running transaction check

 --- Package libselinux.x86_64 0:2.0.94-5.3.el6 will be updated

 -- Processing Dependency: libselinux = 2.0.94-5.3.el6 for package:
 libselinux-utils-2.0.94-5.3.el6.x86_64

 --- Package libselinux.x86_64 0:2.0.94-5.3.el6_4.1 will be an update

 --- Package rubygem-json.x86_64 0:1.5.5-1.el6 will be installed

 -- Processing Dependency: rubygems for package:
 rubygem-json-1.5.5-1.el6.x86_64

 -- Running transaction check

 --- Package libselinux-utils.x86_64 0:2.0.94-5.3.el6 will be updated

 --- Package libselinux-utils.x86_64 0:2.0.94-5.3.el6_4.1 will be an update

 --- Package rubygem-json.x86_64 0:1.5.5-1.el6 will be installed

 -- Processing Dependency: rubygems for package:
 rubygem-json-1.5.5-1.el6.x86_64

 -- Finished Dependency Resolution

 Error: Package: rubygem-json-1.5.5-1.el6.x86_64 (puppetlabs-deps)

   Requires: rubygems

 You could try using --skip-broken to work around the problem

 You could try running: rpm -Va --nofiles --nodigest

 [root@ca-sna-pm01 augeas-1.0.0]#



 --
 You received this message because you are subscribed to the Google Groups
 Puppet Users group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to puppet-users+unsubscr...@googlegroups.com.
 To post to this group, send email to puppet-users@googlegroups.com.
 Visit this group at http://groups.google.com/group/puppet-users?hl=en.
 For more options, visit https://groups.google.com/groups/opt_out.



 --
 Matthaus Owens
 Release Manager, Puppet Labs

 Join us at PuppetConf 2013, August 22-23 in San Francisco -
 http://bit.ly/pupconf13
 Register now and take advantage of the Early Bird discount - save 25%!

 --
 You received this message because you are subscribed to a topic in the 
 Google Groups Puppet Users group.
 To unsubscribe from this topic, visit 
 https://groups.google.com/d/topic/puppet-users/ghDZsdkC3C0/unsubscribe?hl=en.
 To unsubscribe from this group and all its topics, send an email to 
 puppet-users+unsubscr...@googlegroups.com.
 To post to this group, send email to puppet-users@googlegroups.com.
 Visit this group at http://groups.google.com/group/puppet-users?hl=en.
 For more options, visit https://groups.google.com/groups

Re: [Puppet Users] Re: apt repository appears to have dependency issue with latest release (3.2.1)

[Matthaus Owens]

Peter,
hiera-puppet is built in to puppet 3.x, so you don't need to install
it explicitly.

On Fri, May 24, 2013 at 4:56 AM, Peter pe...@ifoley.id.au wrote:
 Eric,

 Damn forgot to cut message down and include the error messages.

 Essentially when I try to install puppet-hiera I get this error message:

 root@play apt/sources.list.d# apt-get install hiera-puppet
 Reading package lists... Done
 Building dependency tree
 Reading state information... Done
 Some packages could not be installed. This may mean that you have
 requested an impossible situation or if you are using the unstable
 distribution that some required packages have not yet been created
 or been moved out of Incoming.
 The following information may help to resolve the situation:

 The following packages have unmet dependencies:
  hiera-puppet : Depends: puppet but it is not going to be installed
 E: Unable to correct problems, you have held broken packages.


 However puppet is already installed:

 root@play apt/sources.list.d# dpkg --status puppet
 Package: puppet
 Status: install ok installed
 Priority: optional
 Section: admin
 Installed-Size: 134
 Maintainer: Puppet Labs 
 Architecture: all
 Version: 3.1.1-1puppetlabs1
 Depends: puppet-common (= 3.1.1-1puppetlabs1), ruby | ruby-interpreter
 Recommends: rdoc
 Suggests: puppet-el, vim-puppet


 Peter

 --
 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 post to this group, send email to puppet-users@googlegroups.com.
 Visit this group at http://groups.google.com/group/puppet-users?hl=en.
 For more options, visit https://groups.google.com/groups/opt_out.





-- 
Matthaus Owens
Release Manager, Puppet Labs

Join us at PuppetConf 2013, August 22-23 in San Francisco -
http://bit.ly/pupconf13
Register now and take advantage of the Early Bird discount - save 25%!

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Re: apt repository appears to have dependency issue with latest release (3.2.1)

[Matthaus Owens]

Maik, there was an update via the puppetlabs-release package to update
the sources.list file to add the dependencies repo.

2013/5/24 Maik Kulbe maik.ku...@gmail.com:
 I can confirm this too and think the way of installing this via a .deb is
 not very nice to admins with more then 10 servers. Why do I need to install
 a package for installing some sources.list.d file when I want it all
 automated. Automation has to do a lot with simplification IMHO, because the
 simpler something is the less likely it will fail. If you want to build a
 robust mechanism of fast deployment a .deb is just really ugly and awkward
 to handle.

 Also I really don't understand why this changed in a way you coudn't upgrade
 anymore. There should have been an update via the repo to at least update
 the sources.list file or create a new one for the dependencies..

 I'm also in with the other guys here - I really don't get why you would need
 a second repository for the dependencies.


 On Thursday, May 23, 2013 5:26:40 PM UTC+2, ma...@marco-scholl.de wrote:

 i can confirm this

 ruby-rgen is not found.

 greets

 ---

 Paketlisten werden gelesen... Fertig
 Abhängigkeitsbaum wird aufgebaut
 Statusinformationen werden eingelesen... Fertig
 Einige Pakete konnten nicht installiert werden. Das kann bedeuten, dass
 Sie eine unmögliche Situation angefordert haben oder, wenn Sie die
 Unstable-Distribution verwenden, dass einige erforderliche Pakete noch
 nicht erstellt wurden oder Incoming noch nicht verlassen haben.
 Die folgenden Informationen helfen Ihnen vielleicht, die Situation zu
 lösen:

 Die folgenden Pakete haben unerfüllte Abhängigkeiten:
  puppet : Hängt ab von: puppet-common (= 3.2.1-1puppetlabs1) soll aber
 nicht installiert werden
 E: Probleme können nicht korrigiert werden, Sie haben zurückgehaltene
 defekte Pakete.
 $ sudo apt-get install puppet-common
 Paketlisten werden gelesen... Fertig
 Abhängigkeitsbaum wird aufgebaut
 Statusinformationen werden eingelesen... Fertig
 Einige Pakete konnten nicht installiert werden. Das kann bedeuten, dass
 Sie eine unmögliche Situation angefordert haben oder, wenn Sie die
 Unstable-Distribution verwenden, dass einige erforderliche Pakete noch
 nicht erstellt wurden oder Incoming noch nicht verlassen haben.
 Die folgenden Informationen helfen Ihnen vielleicht, die Situation zu
 lösen:

 Die folgenden Pakete haben unerfüllte Abhängigkeiten:
  puppet-common : Hängt ab von: ruby-rgen ist aber nicht installierbar
  Empfiehlt: debconf-utils soll aber nicht installiert
 werden
 E: Probleme können nicht korrigiert werden, Sie haben zurückgehaltene
 defekte Pakete.




 --
 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 post to this group, send email to puppet-users@googlegroups.com.
 Visit this group at http://groups.google.com/group/puppet-users?hl=en.
 For more options, visit https://groups.google.com/groups/opt_out.





-- 
Matthaus Owens
Release Manager, Puppet Labs

Join us at PuppetConf 2013, August 22-23 in San Francisco -
http://bit.ly/pupconf13
Register now and take advantage of the Early Bird discount - save 25%!

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Announce: Puppet 3.2.1 Available

[Matthaus Owens]

Puppet 3.2.1 is a bugfix release for the 3.x series of Puppet.

This release addresses two major issues that were uncovered in 3.2.0
and caused us to pull that release (#20726 and #20742). It also
includes a fix for Solaris support (#19760).

Downloads are available at:
 * Source https://downloads.puppetlabs.com/puppet/puppet-3.2.1.tar.gz

Available in native package format at:
http://yum.puppetlabs.com and http://apt.puppetlabs.com

Gems are available via rubygems at
https://rubygems.org/downloads/puppet-3.2.1.gem
  or by using `gem install puppet`

Mac packages are available at
https://downloads.puppetlabs.com/mac/puppet-3.2.1.dmg

Windows packages are available at
https://downloads.puppetlabs.com/windows/puppet-3.2.1.msi

Please report feedback via the Puppet Labs Redmine site, using an
affected puppet version of 3.2.1:
https://projects.puppetlabs.com/projects/puppet/

===
## Puppet 3.2.1 Contributors ##
===

Andrew Parker, Hailee Kenney, Josh Cooper, Josh Partlow, Matthaus Owens

=
## Puppet 3.2.1 Release Notes ##
=

### Issues fixed:

* [Bug #19760]: install sun packages failed with: `Error:
/Stage[main]/Inf_sol10defaultpkg/Package[SMCcurl]: Could not evaluate:
Unable to get information about package SMCcurl because of: No
message`
* [Bug #20726]: usermod command arguments out of order
* [Bug #20742]: unauthenticated clients unable to communicate with
puppet master (running in passenger)

### Known Regressions

On Windows, Puppet 3.2.1 is unable to manage the home directory for a
user account. ([Bug #20768]) This is a regression from Puppet 3.1.1;
it was introduced by switching to Ruby 1.9 in the Windows .msi
package. This bug will be fixed soon in a point release, but wasn't
severe enough to delay shipping.

### All 3.2.1 Changes

To see a list of the issues addressed by this release, check out the
3.2.1 version in our issue tracker at:
https://projects.puppetlabs.com/versions/405

==
## Puppet 3.2.1 Changelog ##
==

Andrew Parker (3):
  76664ae (Maint) Give each test a meaningful name
  ab670d1 (#20742) Handle DNs that cannot be parsed
  de34775 (#20742) Only use certifcate info if there is a CN

Josh Cooper (1):
  4274d66 (#20726) Manage home has issues on Solaris

Josh Partlow (4):
  0588e57 (#20726) Add user managehome acceptance tests
  6f92379 Revert Merge branch 'pull-1512'
  46df39d (#20726) Include password for useradd managehome tests on windows
  866ecbc (maint) Change load order for
puppet/provider/package/windows/package

Matthaus Owens (2):
  2576f8f (packaging) Update PUPPETVERSION to 3.2.1-rc1
  025f00d (packaging) Update PUPPETVERSION to 3.2.1

Nick Fagerlund (1):
  b301ada Maint: Improve documentation of filebucket attributes

Stefan Schulte (3):
  5e091bb (#19760) Use combine when running pkginfo
  887c2037 (#19760) Use pkginfo method instead of execute
  f04d271 (#19760) Remove unnecessary stubbing in sun_spec

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Re: Announce: Puppet 3.2.1 Available

[Matthaus Owens]

Matt,
What platform are you on? Are you using a cache of some sort in front
of apt? We haven't been able to reproduce this problem.

On Wed, May 22, 2013 at 2:50 PM, Matthew Kennedy mattkenn4...@gmail.com wrote:
 It seems that the puppetlabs apt repository is broken with the release of
 these packages.

 When trying to install puppetmaster-passenger I now get this was working
 2 hours ago.

 Some packages could not be installed. This may mean that you have
 requested an impossible situation or if you are using the unstable
 distribution that some required packages have not yet been created
 or been moved out of Incoming.
 The following information may help to resolve the situation:

 The following packages have unmet dependencies:
  puppetmaster-passenger : Depends: puppetmaster-common (=
 3.2.1-1puppetlabs1) but it is not going to be installed
 E: Unable to correct problems, you have held broken packages.

 Matt


 On Wednesday, May 22, 2013 1:54:00 PM UTC-6, Matthaus Litteken wrote:

 Puppet 3.2.1 is a bugfix release for the 3.x series of Puppet.

 This release addresses two major issues that were uncovered in 3.2.0
 and caused us to pull that release (#20726 and #20742). It also
 includes a fix for Solaris support (#19760).

 Downloads are available at:
  * Source https://downloads.puppetlabs.com/puppet/puppet-3.2.1.tar.gz

 Available in native package format at:
 http://yum.puppetlabs.com and http://apt.puppetlabs.com

 Gems are available via rubygems at
 https://rubygems.org/downloads/puppet-3.2.1.gem
   or by using `gem install puppet`

 Mac packages are available at
 https://downloads.puppetlabs.com/mac/puppet-3.2.1.dmg

 Windows packages are available at
 https://downloads.puppetlabs.com/windows/puppet-3.2.1.msi

 Please report feedback via the Puppet Labs Redmine site, using an
 affected puppet version of 3.2.1:
 https://projects.puppetlabs.com/projects/puppet/

 ===
 ## Puppet 3.2.1 Contributors ##
 ===

 Andrew Parker, Hailee Kenney, Josh Cooper, Josh Partlow, Matthaus Owens

 =
 ## Puppet 3.2.1 Release Notes ##
 =

 ### Issues fixed:

 * [Bug #19760]: install sun packages failed with: `Error:
 /Stage[main]/Inf_sol10defaultpkg/Package[SMCcurl]: Could not evaluate:
 Unable to get information about package SMCcurl because of: No
 message`
 * [Bug #20726]: usermod command arguments out of order
 * [Bug #20742]: unauthenticated clients unable to communicate with
 puppet master (running in passenger)

 ### Known Regressions

 On Windows, Puppet 3.2.1 is unable to manage the home directory for a
 user account. ([Bug #20768]) This is a regression from Puppet 3.1.1;
 it was introduced by switching to Ruby 1.9 in the Windows .msi
 package. This bug will be fixed soon in a point release, but wasn't
 severe enough to delay shipping.

 ### All 3.2.1 Changes

 To see a list of the issues addressed by this release, check out the
 3.2.1 version in our issue tracker at:
 https://projects.puppetlabs.com/versions/405

 ==
 ## Puppet 3.2.1 Changelog ##
 ==

 Andrew Parker (3):
   76664ae (Maint) Give each test a meaningful name
   ab670d1 (#20742) Handle DNs that cannot be parsed
   de34775 (#20742) Only use certifcate info if there is a CN

 Josh Cooper (1):
   4274d66 (#20726) Manage home has issues on Solaris

 Josh Partlow (4):
   0588e57 (#20726) Add user managehome acceptance tests
   6f92379 Revert Merge branch 'pull-1512'
   46df39d (#20726) Include password for useradd managehome tests on
 windows
   866ecbc (maint) Change load order for
 puppet/provider/package/windows/package

 Matthaus Owens (2):
   2576f8f (packaging) Update PUPPETVERSION to 3.2.1-rc1
   025f00d (packaging) Update PUPPETVERSION to 3.2.1

 Nick Fagerlund (1):
   b301ada Maint: Improve documentation of filebucket attributes

 Stefan Schulte (3):
   5e091bb (#19760) Use combine when running pkginfo
   887c2037 (#19760) Use pkginfo method instead of execute
   f04d271 (#19760) Remove unnecessary stubbing in sun_spec

 --
 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 post to this group, send email to puppet-users@googlegroups.com.
 Visit this group at http://groups.google.com/group/puppet-users?hl=en.
 For more options, visit https://groups.google.com/groups/opt_out.





--
Matthaus Owens
Release Manager, Puppet Labs

Join us at PuppetConf 2013, August 22-23 in San Francisco -
http://bit.ly/pupconf13
Register now and take advantage of the Early Bird discount - save 25%!

-- 
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

[Puppet Users] Re: Announce: Puppet 3.2.1 Available

[Matthaus Owens]

I neglected to mention in the announcement email, to support the
Future parser, we have added dependencies on ruby-rgen to our puppet
packages that support dependency resolution (gem, deb, rpm). It is
available as a gem
on rubygems.org and packaged as a library in our apt and yum
dependencies repos.

On Wed, May 22, 2013 at 12:54 PM, Matthaus Owens
matth...@puppetlabs.com wrote:
 Puppet 3.2.1 is a bugfix release for the 3.x series of Puppet.

 This release addresses two major issues that were uncovered in 3.2.0
 and caused us to pull that release (#20726 and #20742). It also
 includes a fix for Solaris support (#19760).

 Downloads are available at:
  * Source https://downloads.puppetlabs.com/puppet/puppet-3.2.1.tar.gz

 Available in native package format at:
 http://yum.puppetlabs.com and http://apt.puppetlabs.com

 Gems are available via rubygems at
 https://rubygems.org/downloads/puppet-3.2.1.gem
   or by using `gem install puppet`

 Mac packages are available at
 https://downloads.puppetlabs.com/mac/puppet-3.2.1.dmg

 Windows packages are available at
 https://downloads.puppetlabs.com/windows/puppet-3.2.1.msi

 Please report feedback via the Puppet Labs Redmine site, using an
 affected puppet version of 3.2.1:
 https://projects.puppetlabs.com/projects/puppet/

 ===
 ## Puppet 3.2.1 Contributors ##
 ===

 Andrew Parker, Hailee Kenney, Josh Cooper, Josh Partlow, Matthaus Owens

 =
 ## Puppet 3.2.1 Release Notes ##
 =

 ### Issues fixed:

 * [Bug #19760]: install sun packages failed with: `Error:
 /Stage[main]/Inf_sol10defaultpkg/Package[SMCcurl]: Could not evaluate:
 Unable to get information about package SMCcurl because of: No
 message`
 * [Bug #20726]: usermod command arguments out of order
 * [Bug #20742]: unauthenticated clients unable to communicate with
 puppet master (running in passenger)

 ### Known Regressions

 On Windows, Puppet 3.2.1 is unable to manage the home directory for a
 user account. ([Bug #20768]) This is a regression from Puppet 3.1.1;
 it was introduced by switching to Ruby 1.9 in the Windows .msi
 package. This bug will be fixed soon in a point release, but wasn't
 severe enough to delay shipping.

 ### All 3.2.1 Changes

 To see a list of the issues addressed by this release, check out the
 3.2.1 version in our issue tracker at:
 https://projects.puppetlabs.com/versions/405

 ==
 ## Puppet 3.2.1 Changelog ##
 ==

 Andrew Parker (3):
   76664ae (Maint) Give each test a meaningful name
   ab670d1 (#20742) Handle DNs that cannot be parsed
   de34775 (#20742) Only use certifcate info if there is a CN

 Josh Cooper (1):
   4274d66 (#20726) Manage home has issues on Solaris

 Josh Partlow (4):
   0588e57 (#20726) Add user managehome acceptance tests
   6f92379 Revert Merge branch 'pull-1512'
   46df39d (#20726) Include password for useradd managehome tests on 
 windows
   866ecbc (maint) Change load order for
 puppet/provider/package/windows/package

 Matthaus Owens (2):
   2576f8f (packaging) Update PUPPETVERSION to 3.2.1-rc1
   025f00d (packaging) Update PUPPETVERSION to 3.2.1

 Nick Fagerlund (1):
   b301ada Maint: Improve documentation of filebucket attributes

 Stefan Schulte (3):
   5e091bb (#19760) Use combine when running pkginfo
   887c2037 (#19760) Use pkginfo method instead of execute
   f04d271 (#19760) Remove unnecessary stubbing in sun_spec



-- 
Matthaus Owens
Release Manager, Puppet Labs

Join us at PuppetConf 2013, August 22-23 in San Francisco -
http://bit.ly/pupconf13
Register now and take advantage of the Early Bird discount - save 25%!

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Puppet 3.2.0, the great release that never was. Puppet 3.2.1, the great release that will be

[Matthaus Owens]

Between tagging 3.2.0 final and actually releasing it, a bug was
discovered in the user provider related to managehome on redhat based
systems (https://projects.puppetlabs.com/issues/20726). Rather than
ship 3.2.0 with that bug, we're readying Puppet 3.2.1 for a fresh rc
series to address this issue. We anticipate a release candidate for
3.2.1 later today.
And many thanks to our users who try out our release candidates and
catch these issues.

--
Matthaus Owens
Release Manager, Puppet Labs

Join us at PuppetConf 2013, August 22-23 in San Francisco -
http://bit.ly/pupconf13
Register now and take advantage of the Early Bird discount - save 25%!

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Workaround for Puppet 3 not working in Fedora 18

[Matthaus Owens]

Tom,
Why are installing the EL 6 release package for Fedora 18? Have you
tried 
http://yum.puppetlabs.com/fedora/f18/products/i386/puppetlabs-release-18-7.noarch.rpm
instead?

On Fri, May 17, 2013 at 1:04 PM, Tom Poulton poulton...@gmail.com wrote:
 I setup the Puppet Labs yum repo via sudo rpm -ivh
 http://yum.puppetlabs.com/el/6/products/i386/puppetlabs-release-6-6.noarch.rpm;

 So far between me and a colleague we've tried:
 F18 GNOME:
 Seemed fine I think (but GNOME 3 didn't play nice with VirtualBox, very very
 slow)

 F18 KDE: Initially running Puppet 2.7.X
 The client worked fine but the Puppet Dashboard kept throwing errors that's
 what made me realise we were running 2.7 (I didn't bother to check the yum
 install process as I assumed the Fedora repo would be up to date)

 F18 KDE: Running Puppet 3.1.1
 Ruby errors above. I upgraded my colleagues machine today and ran into
 exactly the same problem

 From that I'm thinking this might be specific to the F18 KDE version, maybe
 ruby is setup in an odd fashion on this spin??

 --
 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 post to this group, send email to puppet-users@googlegroups.com.
 Visit this group at http://groups.google.com/group/puppet-users?hl=en.
 For more options, visit https://groups.google.com/groups/opt_out.





-- 
Matthaus Owens
Release Manager, Puppet Labs

Join us at PuppetConf 2013, August 22-23 in San Francisco -
http://bit.ly/pupconf13
Register now and take advantage of the Early Bird discount - save 25%!

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Announce: Puppet 3.2.1-rc1 Available

[Matthaus Owens]

Puppet 3.2.1-rc1 is a bugfix release candidate for the 3.x series of Puppet.

This release addresses two major issues that were uncovered in 3.2.0
and caused us to pull that release (#20726 and #20742). It also
includes a fix for Solaris support (#19760).

Downloads are available at:
 * Source https://downloads.puppetlabs.com/puppet/puppet-3.2.1-rc1.tar.gz

Available in native package format in the pre-release repositories at:
http://yum.puppetlabs.com and http://apt.puppetlabs.com

For information on how to enable the Puppet Labs pre-release repos, see:
http://docs.puppetlabs.com/guides/puppetlabs_package_repositories.html#enabling-the-prerelease-repos

Gems are available via rubygems at
https://rubygems.org/downloads/puppet-3.2.1.rc1.gem
  or by using `gem install puppet`

Mac packages are available at
https://downloads.puppetlabs.com/mac/puppet-3.2.1-rc1.dmg

Windows packages are available at
https://downloads.puppetlabs.com/windows/puppet-3.2.1-rc1.msi

Please report feedback via the Puppet Labs Redmine site, using an
affected puppet version of 3.2.1-rc1:
https://projects.puppetlabs.com/projects/puppet/

==
## Puppet 3.2.1-rc1 Contributors ##
==

Andrew Parker, Hailee Kenney, Josh Cooper, Josh Partlow, Matthaus Owens


## Puppet 3.2.1-rc1 Release Notes ##


### Issues fixed:

* [Bug #19760]: install sun packages failed with: `Error:
/Stage[main]/Inf_sol10defaultpkg/Package[SMCcurl]: Could not evaluate:
Unable to get information about package SMCcurl because of: No
message`
* [Bug #20726]: usermod command arguments out of order
* [Bug #20742]: unauthenticated clients unable to communicate with
puppet master (running in passenger)

### Known Regressions

On Windows, Puppet 3.2.1 is unable to manage the home directory for a
user account. ([Bug #20768]) This is a regression from Puppet 3.1.1;
it was introduced by switching to Ruby 1.9 in the Windows .msi
package. This bug will be fixed soon in a point release, but wasn't
severe enough to delay shipping.

### All 3.2.1 Changes

To see a list of the issues addressed by this release, check out the
3.2.1 version in our issue tracker at:
https://projects.puppetlabs.com/versions/405

=
## Puppet 3.2.1-rc1 Changelog ##
=

Andrew Parker (3):
  76664ae (Maint) Give each test a meaningful name
  ab670d1 (#20742) Handle DNs that cannot be parsed
  de34775 (#20742) Only use certifcate info if there is a CN

Josh Cooper (1):
  4274d66 (#20726) Manage home has issues on Solaris

Josh Partlow (4):
  0588e57 (#20726) Add user managehome acceptance tests
  6f92379 Revert Merge branch 'pull-1512'
  46df39d (#20726) Include password for useradd managehome tests on windows
  866ecbc (maint) Change load order for
puppet/provider/package/windows/package

Matthaus Owens (1):
  2576f8f (packaging) Update PUPPETVERSION to 3.2.1-rc1

Nick Fagerlund (1):
  b301ada Maint: Improve documentation of filebucket attributes

Stefan Schulte (3):
  5e091bb (#19760) Use combine when running pkginfo
  887c2037 (#19760) Use pkginfo method instead of execute
  f04d271 (#19760) Remove unnecessary stubbing in sun_spec

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Announce: Facter 1.7.1 Available

[Matthaus Owens]

Facter 1.7.1 is a bugfix release in the 1.7 series. It
contains a single fix for an issue seen on Windows 2003 with Ruby
1.9.3 (#20301).

To see a list of the issues addressed by this release, check out the
1.7.1 version in our issue tracker at:
https://projects.puppetlabs.com/versions/400

Downloads are available at:
 * Source: https://downloads.puppetlabs.com/facter/facter-1.7.1.tar.gz

RPMs are available at https://yum.puppetlabs.com/el or /fedora

Rubygem available at http://rubygems.org/gems/facter

Debs are available at https://apt.puppetlabs.com

Mac package is available at
https://downloads.puppetlabs.com/mac/facter-1.7.1.dmg

Please report feedback via the Puppet Labs Redmine site, using an
affected version of 1.7.1:
 http://projects.puppetlabs.com/projects/facter/

=
## Facter 1.7.1 Bug Fixes ##
=

(#20301) Handle different error in ruby 1.9

The NumberOfLogicalProcessor property of the Win32_Processor WMI class
does not exist in the base win2003 install. Previously, we were trying
to access the property, and then catching the resulting error if the
property did not exist.

In ruby 1.8, it would raise a RuntimeError, but in ruby 1.9, it raises a
StandardError, causing the fact to blow up on ruby 1.9.

This commit checks to see if the process object responds to that method,
and only then does it try to call it.

=
## Facter 1.7.1 Changelog ##
=

Josh Cooper (1):
  b5cb1ef (#20301) Handle different error in ruby 1.9

Matthaus Owens (2):
  bf39f9a (packaging) Update FACTERVERSION to 1.7.1-rc1
  785fd8b (packaging) Update FACTERVERSION to 1.7.1

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.