[Puppet Users] Re: catalog-diff and create_resources not correct

[Alex Harvey]

Actually looks like there's an open PR to fix this here
https://github.com/acidprime/puppet-catalog-diff/pull/28

On Wednesday, December 23, 2015 at 3:55:11 PM UTC+11, Alex Harvey wrote:
>
> Hi Johan,
>
> I read your excellent blog post on this
>
> http://johan.koewacht.net/puppet/2015/01/12/catalog-diff-create_resources.html
>
> I have also run into the same issue.  Was this ever resolved?  
>
> You wrote at the end,
>
> But question now, should we patch the catalog-diff preprocessor.rb or 
> puppet’s native create_resources.rb
>
>
> Considering that the purpose of the catalog diff tool is to assist in 
> migrations from earlier to later versions of Puppet, it's no use patching 
> create_resources.rb in a newer version of Puppet.  I think this is really a 
> bug in the catalog diff tool?
>
> Thanks,
> Alex
>
> On Tuesday, December 23, 2014 at 8:36:27 PM UTC+11, Johan De Wit wrote:
>>
>> Hi, 
>>
>> We wanted to use catalog diff to verify the old and new catalogs during 
>> conversionto hiera.  They should be both have the saem resources with the 
>> same paramters.
>> But every resource that is created in the 'new' version with 
>> create_resources(), gives a wrong catalog diff.
>>
>> The resource is indeed in both catalogs, only the old one contains 2 
>> automatic attributes (file: and line:).  I suspect this is the cause.
>>
>> Anyone experienced simular result ?
>>
>> In the meantime, I try to understand the catalog-diff code to see where 
>> this could be corrected.
>>
>> Grts
>>
>> johan
>>
>>
>>Catalog diff output :
>>
>>
>> 
>>test_node 
>>100.0% 
>>
>>
>> 
>>Total resources in old: 0
>>Total resources in new: 1
>>Only in new:
>>notify[my_test_notify]
>>Catalag percentage added:   100.00
>>Catalog percentage removed: 0.00
>>Catalog percentage changed: 0.00
>>Added and removed resources:+1 / 0
>>Node percentage:100.0
>>Node differences:   1
>>
>>
>> 
>>1 out of 1 nodes changed. 
>>100.0% 
>>
>>
>> 
>>Nodes with the most changes by percent changed:
>>1. test_node 
>>100.00%
>>Nodes with the most changes by differeces:
>>1. test_node 
>> 1false
>> 
>>The manifest new and catalog entry
>> 
>>node 'test_node' {
>>   $my_notify =  { 'my_test_notify' => { 'message' => 'this is a test 
>>notify',
>> 'name' => 'test_notify',
>> 'withpath' => 'true', }
>>}
>>   create_resources(notify, $my_notify)
>>}
>> 
>>  {
>>"parameters": {
>>  "withpath": "true",
>>  "message": "this is a test notify",
>>  "name": "test_notify"
>>},
>>"exported": false,
>>"tags": [
>>  "notify",
>>  "my_test_notify",
>>  "node",
>>  "test_node",
>>  "class"
>>],
>>"title": "my_test_notify",
>>"type": "Notify"
>>  }
>> 
>>
>> 
>>The manifest OLD
>> 
>>node 'test_node' {
>>   notify { 'my_test_notify':
>> message  => 'this is a test notify',
>> name => 'test_notify', 
>> withpath => true,
>>   }
>>}
>> 
>>
>>"title": "test_node",
>>"type": "Node"
>>  },
>>  {
>>"parameters": {
>>  "withpath": true,
>>  "message": "this is a test notify",
>>  "name": "test_notify"
>>},
>>"exported": false,
>>"line": 12,
>>"file": 
>>
>> "/etc/puppetlabs/puppet/environments/rese_old/manifests/nodes/test_node.pp",
>>"tags": [
>>  "notify",
>>  "my_test_notify",
>>  "node",
>>  "test_node",
>>  "class"
>>],
>>"title": "my_test_notify",
>>"type": "Notify"
>>  }
>>
>>
>>
>>
>> -- 
>> Johan De Wit
>>
>> Open Source Consultant
>>
>> Red Hat Certified Engineer  (805008667232363)
>> Puppet Certified Professional 2013/2014 (PCP006)
>> _
>>  
>> Open-Future Phone +32 (0)2/255 70 70
>> Zavelstraat 72  Fax   

[Puppet Users] Re: catalog-diff and create_resources not correct

[Alex Harvey]

Hi Johan,

I read your excellent blog post on this
http://johan.koewacht.net/puppet/2015/01/12/catalog-diff-create_resources.html

I have also run into the same issue.  Was this ever resolved?  

You wrote at the end,

But question now, should we patch the catalog-diff preprocessor.rb or 
puppet’s native create_resources.rb


Considering that the purpose of the catalog diff tool is to assist in 
migrations from earlier to later versions of Puppet, it's no use patching 
create_resources.rb in a newer version of Puppet.  I think this is really a 
bug in the catalog diff tool?

Thanks,
Alex

On Tuesday, December 23, 2014 at 8:36:27 PM UTC+11, Johan De Wit wrote:
>
> Hi, 
>
> We wanted to use catalog diff to verify the old and new catalogs during 
> conversionto hiera.  They should be both have the saem resources with the 
> same paramters.
> But every resource that is created in the 'new' version with 
> create_resources(), gives a wrong catalog diff.
>
> The resource is indeed in both catalogs, only the old one contains 2 
> automatic attributes (file: and line:).  I suspect this is the cause.
>
> Anyone experienced simular result ?
>
> In the meantime, I try to understand the catalog-diff code to see where 
> this could be corrected.
>
> Grts
>
> johan
>
>
>Catalog diff output :
>
>
> 
>test_node 
>100.0% 
>
>
> 
>Total resources in old: 0
>Total resources in new: 1
>Only in new:
>notify[my_test_notify]
>Catalag percentage added:   100.00
>Catalog percentage removed: 0.00
>Catalog percentage changed: 0.00
>Added and removed resources:+1 / 0
>Node percentage:100.0
>Node differences:   1
>
>
> 
>1 out of 1 nodes changed. 
>100.0% 
>
>
> 
>Nodes with the most changes by percent changed:
>1. test_node   
>  100.00%
>Nodes with the most changes by differeces:
>1. test_node   
>   1false
> 
>The manifest new and catalog entry
> 
>node 'test_node' {
>   $my_notify =  { 'my_test_notify' => { 'message' => 'this is a test 
>notify',
> 'name' => 'test_notify',
> 'withpath' => 'true', }
>}
>   create_resources(notify, $my_notify)
>}
> 
>  {
>"parameters": {
>  "withpath": "true",
>  "message": "this is a test notify",
>  "name": "test_notify"
>},
>"exported": false,
>"tags": [
>  "notify",
>  "my_test_notify",
>  "node",
>  "test_node",
>  "class"
>],
>"title": "my_test_notify",
>"type": "Notify"
>  }
> 
>
> 
>The manifest OLD
> 
>node 'test_node' {
>   notify { 'my_test_notify':
> message  => 'this is a test notify',
> name => 'test_notify', 
> withpath => true,
>   }
>}
> 
>
>"title": "test_node",
>"type": "Node"
>  },
>  {
>"parameters": {
>  "withpath": true,
>  "message": "this is a test notify",
>  "name": "test_notify"
>},
>"exported": false,
>"line": 12,
>"file": 
>
> "/etc/puppetlabs/puppet/environments/rese_old/manifests/nodes/test_node.pp",
>"tags": [
>  "notify",
>  "my_test_notify",
>  "node",
>  "test_node",
>  "class"
>],
>"title": "my_test_notify",
>"type": "Notify"
>  }
>
>
>
>
> -- 
> Johan De Wit
>
> Open Source Consultant
>
> Red Hat Certified Engineer  (805008667232363)
> Puppet Certified Professional 2013/2014 (PCP006)
> _
>  
> Open-Future Phone +32 (0)2/255 70 70
> Zavelstraat 72  Fax   +32 (0)2/255 70 71
> 3071 KORTENBERG Mobile+32 (0)474/42 40 73
> BELGIUM http://www.open-future.be
> _
>  
>
>
> Upcoming Events:
>
> Zabbix Certified Specialist | 
> http://www.open-future.be/zabbix-certified-professional-training-8th-till-9th-janaury
>
> Zabbix Cert

[Puppet Users] Re: Puppet Server Crashing often

[Chris Price]

On Wednesday, December 16, 2015 at 4:26:26 AM UTC-8, Makrand Sanap wrote:
>
> Hi All,
>
> I am doing POC for puppet enterprise. Master is on CentOS 6.4 VM with 2GB 
> ram. Puppet server is going down on its own. 
>
> [root@mss-pup-mst2 ~]# /etc/init.d/pe-puppetserver status
>> pe-puppetserver dead but pid file exists
>>
>
>
> I can start it without any issues, but it stays for like 30-60 Mins up. 
> then It goes down again.
>
> Logs are not hinting anything, but for one of shutdown, I found following 
> lines. Surprisingly they appeared for only one shutdown incident. Not for 
> others
>
> 2015-12-13 04:38:21,100 INFO  [p.t.internal] Shutting down due to JVM 
>> shutdown hook.
>> 2015-12-13 04:38:21,363 INFO  [p.t.internal] Beginning shutdown sequence
>> 2015-12-13 04:38:21,640 INFO  [p.e.s.j.pe-jruby-metrics-service] PE JRuby 
>> Metrics Service: stopping metrics sampler job
>> 2015-12-13 04:38:21,990 INFO  [p.e.s.j.pe-jruby-metrics-service] PE JRuby 
>> Metrics Service: stopped metrics sampler job
>> 2015-12-13 04:38:22,724 INFO  [p.t.s.w.jetty9-service] Shutting down web 
>> server(s).
>> 2015-12-13 04:38:22,808 INFO  [p.t.s.w.jetty9-core] Shutting down web 
>> server.
>> 2015-12-13 04:38:23,243 INFO  [o.e.j.s.ServerConnector] Stopped 
>> ServerConnector@4369ad74{SSL-HTTP/1.1}{0.0.0.0:8140}
>> 2015-12-13 04:38:23,262 INFO  [o.e.j.s.h.ContextHandler] Stopped 
>> o.e.j.s.h.ContextHandler@3749adc6{/status,null,UNAVAILABLE}
>>
>
This is very unusual, I would not expect for you to see the message "Shutting 
down due to JVM shutdown hook" unless something on your system sent a 
signal to the service to stop or restart.

I presume you have a Puppet agent running on the same node; can you check 
its report and see if it shows anything about it trying to restart Puppet 
Server?  Or maybe try disabling the agent (`service puppet stop`) for a 
period of time and see if the weird behavior of the server only occurs when 
the agent is running?

 

>
>
> After bit of googling, I found following
>
>
> https://github.com/puppetlabs/puppet-server/blob/master/documentation/install_from_packages.markdown#memory-allocation
>
> Thing is, I am not able to find  init file under 
> /etc/sysconfig/puppetserver
> to ask Puppetserver to use less RAM than 2GB. (This proabably seems reason 
> for this)
>
> Do anyone know, where I can set the RAM usage for puppetserver (PE 
> 2015.2.3)?
>
> -- 
> Best,
> Makrand
>
>

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

[Puppet Users] Adding property or parameter to existing core types

[Johan Martinez]

Would it be possible to add a new property or parameter to existing core 
type? I found documentation on adding new types, but not on extending 
existing types with new property/parameters. Any help on how it can be done 
would be appreciated.


thanks,
jM

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

Re: [Puppet Users] Puppet Enterprise Installation errors

[Lindsey Smith]

On Tue, Dec 22, 2015 at 12:07 PM, nathan joiner 
wrote:

> Thanks guys for the suggestions!
>
> My company (NCL) is in charge of purchasing so they haven't upgraded to a
> newer version on their end. That's why I'm stuck with this version.
>
> I also validated the following:
>
> - ensure proper DNS functionality (or specify host/ip in /etc/hosts)
>   - set to localhost
> - ensure proper local time (ntp)
>   - this is correct
> - /tmp needs to be mounted with exec option
>   - /tmp has the exec access (drwxrwxrwt.  3 rootroot 4096 22. Dez
> 19:10 tmp)
>
> - local firewall enabled
>   - This is enabled
> - selinux restrictions enabled
>   - selinux is set to permissive
>
> Any other ideas?
>

Could you post a log of the output from puppet-enterprise-installer?

Also, as a PE customer the Puppet Labs support team could help you.


>
> On Tuesday, December 22, 2015 at 1:22:49 PM UTC-5, Martin Alfke wrote:
>>
>> Hi Nathan,
>>
>> On 22 Dec 2015, at 18:54, Lindsey Smith  wrote:
>>
>> >
>> >
>> > On Tue, Dec 22, 2015 at 9:36 AM, nathan joiner 
>> wrote:
>> > Good Morning,
>> >
>> > I'm trying to setup PE puppet master server and a windows agent node
>> but I'm getting "no authorization" when trying to run the
>> puppet-enterprise-installer.
>> >
>> > Environment:
>> > - I'm using a windows 7 machine
>> > - Using Cmder to add and ssh into a CentOS server that will be used as
>> the Puppetmaster server.
>> >
>> > I've done the following:
>> > - SCPed PE 3.7.2 directory onto the root folder of my CentOS vm
>> >
>> > Any specific reason to use PE 3.7.2? I'd strongly recommend the most
>> recent version of PE 3.8, if not the latest PE 2015.3 with Puppet 4. If
>> you're just starting with Puppet, starting there may be better.
>>
>> Good comment from Lindsey: when you start with Puppet you should go for
>> the newest PE version available.
>> Make use of elder versions in case of specific requirement only.
>>
>> >
>> > - Running as super user (su)
>> > - CDed into puppet enterprise directory
>> > - Ran ./puppet-enterprise-installer -s answers.txt
>> > - Recieved a not authorized error message.
>>
>> Check the following:
>>
>> - ensure proper DNS functionality (or specify host/ip in /etc/hosts)
>> - ensure proper local time (ntp)
>> - /tmp needs to be mounted with exec option
>>
>> More unlikely:
>> - local firewall enabled
>> - selinux restrictions enabled
>>
>> hth,
>> best,
>> Martin
>>
>>
>> >
>> > Thanks!
>> >
>> > --
>> > You received this message because you are subscribed to the Google
>> Groups "Puppet Users" group.
>> > To unsubscribe from this group and stop receiving emails from it, send
>> an email to puppet-users...@googlegroups.com.
>> > To view this discussion on the web visit
>> https://groups.google.com/d/msgid/puppet-users/8d859d0f-d23d-407e-8963-00d3be60da14%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/CAPyei8WAohMawXAx%3D7r07L33Z9XQ9CydBGwth-4jYE9YOyi3hA%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/9e75f90b-6663-42ce-a3f7-8b65f33c5b63%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/CAPyei8U2CjU12Bt4yQf3P-Gav9M7fy2FyHUbnTk0LhFXShw0WA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] [Post Mortem] Outage on apt.puppetlabs.com and yum.puppetlabs.com

[Morgan Rhodes]

*Timeline*


Failures began:  24 Nov 2015 1900 GMT

Notifications of failures began:  24 Nov 2015 1930 GMT

Service restored for apt:  24 Nov 2015 2000 GMT

Service partially restored for yum:  24 Nov 2015 2200 GMT

Service fully restored:  24 Nov 2015 2320 GMT

*Impact*


For some part of the outage (depending on the platform) repositories on
yum.puppetlabs.com and apt.puppetlabs.com were unusable due to missing
content, resulting in 404 errors for both repository metadata and packages.
Several users contacted us via IRC, Twitter, JIRA, and other means.

What happened?

Puppet Labs manages a number of servers that run our public package
repository infrastructure. One of these servers was recently taken down for
emergency maintenance by our provider (which was not disruptive). After
maintenance was completed, we manually initiated a synchronization job to
update the package contents and metadata on this server. Due to human error
this sync was run in reverse, from the out-of-date node to an up-to-date
node. As this process is destructive[1], it resulted in loss of data and
corruption of repository metadata.

What we did to restore service

As part of recent efforts to improve how we ship software to our apt
repositories, a complete backup of those repositories already exists on
disk. Shortly after triaging the issue we were able to restore
apt.puppetlabs.com from that copy.

To restore the yum repositories we had to initiate a synchronization job
from an internal system. The  synchronization job took a considerable
amount of time due to the number of rpm packages and yum metadata that
needed to be restored.

Next steps

To remediate this in the future we’re continuing to update our release
automation and process to better leverage staging infrastructure before
changes are shipped to production infrastructure. This will help ensure
that we always have a complete copy of our repositories that can be
redeployed in case of emergency. We’re also implementing improved
monitoring of this infrastructure and the package repositories it serves.
This outage exposed some deficiencies in how we communicate issues like
this and we are committed to developing a better communication plan for
future incidents.


We apologize for the outage,
Puppet Labs Release Engineering

---
[1] - The synchronization process is destructive (not strictly additive) in
order to remove stale metadata when new packages are published
-- 
Morgan Rhodes
mor...@puppetlabs.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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CA%2BFnDv1yEVy%3D8nEn6Gb289yFQ%2B2F5Rmtc%3DdtWwz%3DGA_B5-vjWg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Puppet Enterprise Installation errors

[nathan joiner]

Thanks guys for the suggestions!

My company (NCL) is in charge of purchasing so they haven't upgraded to a 
newer version on their end. That's why I'm stuck with this version.

I also validated the following:

- ensure proper DNS functionality (or specify host/ip in /etc/hosts) 
  - set to localhost
- ensure proper local time (ntp) 
  - this is correct
- /tmp needs to be mounted with exec option 
  - /tmp has the exec access (drwxrwxrwt.  3 rootroot 4096 22. Dez 
19:10 tmp)

- local firewall enabled 
  - This is enabled
- selinux restrictions enabled 
  - selinux is set to permissive

Any other ideas?

On Tuesday, December 22, 2015 at 1:22:49 PM UTC-5, Martin Alfke wrote:
>
> Hi Nathan, 
>
> On 22 Dec 2015, at 18:54, Lindsey Smith  > wrote: 
>
> > 
> > 
> > On Tue, Dec 22, 2015 at 9:36 AM, nathan joiner  > wrote: 
> > Good Morning, 
> > 
> > I'm trying to setup PE puppet master server and a windows agent node but 
> I'm getting "no authorization" when trying to run the 
> puppet-enterprise-installer. 
> > 
> > Environment: 
> > - I'm using a windows 7 machine 
> > - Using Cmder to add and ssh into a CentOS server that will be used as 
> the Puppetmaster server. 
> > 
> > I've done the following: 
> > - SCPed PE 3.7.2 directory onto the root folder of my CentOS vm 
> > 
> > Any specific reason to use PE 3.7.2? I'd strongly recommend the most 
> recent version of PE 3.8, if not the latest PE 2015.3 with Puppet 4. If 
> you're just starting with Puppet, starting there may be better. 
>
> Good comment from Lindsey: when you start with Puppet you should go for 
> the newest PE version available. 
> Make use of elder versions in case of specific requirement only. 
>
> >   
> > - Running as super user (su) 
> > - CDed into puppet enterprise directory 
> > - Ran ./puppet-enterprise-installer -s answers.txt 
> > - Recieved a not authorized error message. 
>
> Check the following: 
>
> - ensure proper DNS functionality (or specify host/ip in /etc/hosts) 
> - ensure proper local time (ntp) 
> - /tmp needs to be mounted with exec option 
>
> More unlikely: 
> - local firewall enabled 
> - selinux restrictions enabled 
>
> hth, 
> best, 
> Martin 
>
>
> > 
> > Thanks! 
> > 
> > -- 
> > You received this message because you are subscribed to the Google 
> Groups "Puppet Users" group. 
> > To unsubscribe from this group and stop receiving emails from it, send 
> an email to puppet-users...@googlegroups.com . 
> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/puppet-users/8d859d0f-d23d-407e-8963-00d3be60da14%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/CAPyei8WAohMawXAx%3D7r07L33Z9XQ9CydBGwth-4jYE9YOyi3hA%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/9e75f90b-6663-42ce-a3f7-8b65f33c5b63%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Using exec with puppet device management?

[jcbollinger]

On Tuesday, December 22, 2015 at 9:50:37 AM UTC-6, red 888 wrote:
>
> Thanks for taking the time to answer my questions. 
>
> It seems like Puppet isn't the right tool for what I want to accomplish or 
> I will have to wait for native full featured Cisco support.
>
> I think my confusion came from the notion that extending puppet in this 
> way was a simple end usery task.
>


Puppet's end users are generally sysadmins, so what is simple and end-usery 
for them is not necessarily very simple in an absolute sense.  Even so, I'm 
not sure how you got the notion you describe.  I've always found Puppet DSL 
to be fairly easy to *use*, but writing extensions is developing for 
Puppet, not using it, and Puppet's native language is Ruby.  Perhaps you 
fell victim to precisely the misconception that I just denounced: that 
Puppet's language is some oddball form of scripting language.  As I said, 
it isn't.

 

>
> I thought, for example, if I wanted to push out an EIGRP message digest 
> configuration (currently puppet device can't do this out of the box) I 
> could plug in my own code/ios commands *somewhere *and refer to it in my 
> module the same way I do other "resources'" like this (sloppy pseudo code):
>
> keychain {
>   name => chainName
>   keynumber => 5
>   key-string => 
> }
>
> interface {
>   'GigabitEthernet 0/1':
> description => $interface_description_lan
>   eigrp keychain {
> as => 123
> name => chainName
>   }
> }
>
>

No.  Each resource type has a specific set of attributes that it supports, 
each with specific semantics.  In this sense (and in most others) Puppet 
resource types are much closer analogs to Java or C++ classes than Puppet 
classes are.

 

> But, if I understand what you are saying, that would require a great deal 
> of coding.  Being that I am not a ruby dev this would probably be a waste 
> of my time.
>
>

I don't know exactly how much "a great deal" of coding would be to you, but 
the amount involved is certainly a lot more than zero, and in addition to 
Ruby issues, there would be the learning curve specific to Puppet 
development.  I imagine the end result would have at least a few hundred 
lines of Ruby code (but having done that once and gotten it working, you 
could reuse it widely).  If you were looking for something you could do in 
a Monday morning, then no, I don't think this is it.

On the other hand, if configuring EIGRP digest parameters is something you 
imagine others might want to do too, then you should consider filing a 
feature request ticket.

BTW, do you plan to delete your SO question on this topic?  It would be a 
waste for me to write an answer there if you're just going to delete the 
question.


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/8343f248-c157-4705-942f-8e30572c34be%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Puppet Enterprise Installation errors

[Martin Alfke]

Hi Nathan,

On 22 Dec 2015, at 18:54, Lindsey Smith  wrote:

> 
> 
> On Tue, Dec 22, 2015 at 9:36 AM, nathan joiner  
> wrote:
> Good Morning,
> 
> I'm trying to setup PE puppet master server and a windows agent node but I'm 
> getting "no authorization" when trying to run the puppet-enterprise-installer.
> 
> Environment:
> - I'm using a windows 7 machine
> - Using Cmder to add and ssh into a CentOS server that will be used as the 
> Puppetmaster server.
> 
> I've done the following:
> - SCPed PE 3.7.2 directory onto the root folder of my CentOS vm 
> 
> Any specific reason to use PE 3.7.2? I'd strongly recommend the most recent 
> version of PE 3.8, if not the latest PE 2015.3 with Puppet 4. If you're just 
> starting with Puppet, starting there may be better.

Good comment from Lindsey: when you start with Puppet you should go for the 
newest PE version available.
Make use of elder versions in case of specific requirement only.

>  
> - Running as super user (su)
> - CDed into puppet enterprise directory
> - Ran ./puppet-enterprise-installer -s answers.txt
> - Recieved a not authorized error message.

Check the following:

- ensure proper DNS functionality (or specify host/ip in /etc/hosts)
- ensure proper local time (ntp)
- /tmp needs to be mounted with exec option

More unlikely:
- local firewall enabled
- selinux restrictions enabled

hth,
best,
Martin


> 
> 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/8d859d0f-d23d-407e-8963-00d3be60da14%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/CAPyei8WAohMawXAx%3D7r07L33Z9XQ9CydBGwth-4jYE9YOyi3hA%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/53D9328B-7FC0-4977-8D00-6CEF15BFA468%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Puppet Enterprise Installation errors

[Lindsey Smith]

On Tue, Dec 22, 2015 at 9:36 AM, nathan joiner 
wrote:

> Good Morning,
>
> I'm trying to setup PE puppet master server and a windows agent node but
> I'm getting "no authorization" when trying to run the
> puppet-enterprise-installer.
>
> Environment:
> - I'm using a windows 7 machine
> - Using Cmder to add and ssh into a CentOS server that will be used as the
> Puppetmaster server.
>
> I've done the following:
> - SCPed PE 3.7.2 directory onto the root folder of my CentOS vm
>

Any specific reason to use PE 3.7.2? I'd strongly recommend the most recent
version of PE 3.8, if not the latest PE 2015.3 with Puppet 4. If you're
just starting with Puppet, starting there may be better.


> - Running as super user (su)
> - CDed into puppet enterprise directory
> - Ran ./puppet-enterprise-installer -s answers.txt
> - Recieved a not authorized error message.
>
> 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/8d859d0f-d23d-407e-8963-00d3be60da14%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/CAPyei8WAohMawXAx%3D7r07L33Z9XQ9CydBGwth-4jYE9YOyi3hA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Puppet Enterprise Installation errors

[nathan joiner]

Good Morning,

I'm trying to setup PE puppet master server and a windows agent node but 
I'm getting "no authorization" when trying to run the 
puppet-enterprise-installer.

Environment:
- I'm using a windows 7 machine
- Using Cmder to add and ssh into a CentOS server that will be used as the 
Puppetmaster server.

I've done the following:
- SCPed PE 3.7.2 directory onto the root folder of my CentOS vm 
- Running as super user (su)
- CDed into puppet enterprise directory
- Ran ./puppet-enterprise-installer -s answers.txt
- Recieved a not authorized error message.

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/8d859d0f-d23d-407e-8963-00d3be60da14%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Using exec with puppet device management?

[red 888]

Thanks for taking the time to answer my questions. 

It seems like Puppet isn't the right tool for what I want to accomplish or 
I will have to wait for native full featured Cisco support.

I think my confusion came from the notion that extending puppet in this way 
was a simple end usery task.

I thought, for example, if I wanted to push out an EIGRP message digest 
configuration (currently puppet device can't do this out of the box) I 
could plug in my own code/ios commands *somewhere *and refer to it in my 
module the same way I do other "resources'" like this (sloppy pseudo code):

keychain {
  name => chainName
  keynumber => 5
  key-string => 
}

interface {
  'GigabitEthernet 0/1':
description => $interface_description_lan
  eigrp keychain {
as => 123
name => chainName
  }
}

But, if I understand what you are saying, that would require a great deal 
of coding.  Being that I am not a ruby dev this would probably be a waste 
of my time.


On Tuesday, December 22, 2015 at 10:02:59 AM UTC-5, jcbollinger wrote:
>
>
>
> On Monday, December 21, 2015 at 12:30:16 PM UTC-6, red 888 wrote:
>>
>> Thanks for replying!
>>
>> I'm aware of how puppet device works and I know there is no actual agent 
>> software running on the Cisco device (I'm not talking about the newer OnePK 
>> thing).
>>
>> My question was how can I use this to send my own commands in a 
>> integrated way- meaning the same way Puppet Device does it.
>>
>
>
> There is nothing particularly magical about 'puppet device'.  It relies on 
> the same Puppet infrastructure as the agent, and in fact, it seems mostly 
> to be just a specialization of the agent.  The "integrated way" in which 
> 'puppet device' delivers commands to network devices is not directly 
> accessible at the DSL level.  It is an aspect of the Ruby implementations 
> of the providers for the resource types managed by that mechanism.
>
>  
>
>>
>> "You could, however, use an Exec to open a telnet or ssh connection to 
>> the router with which to execute a remote command; *that is akin to how 
>> the built-in device management types work*"
>>
>> Opening my own instance of telent/ssh defeats the purpose- I want to do 
>> it "how the built-in device management" feature does it. Meaning I have 
>> already defined the IPs and authentication info for my routers in 
>> device.conf and I don't want to have to hard code that info into the module.
>>
>
>
> I don't see where hard-coding data into your module comes in.  Pretty much 
> no one wants to do that; instead they externalize and centralize their 
> data.  You could, too.
>
> But if you are serious about using *the same* infrastructure that the 
> providers for the existing resource types use, then you are talking about 
> writing a custom type and provider -- a remote analog of Exec.  That is a 
> significant undertaking, especially considering that the goal is something 
> that must fit even more poorly into the Puppet model than does Exec 
> itself.  If you want to pursue this course anyway, then the Puppet 
> Developers  group 
> would be a more appropriate place to discuss the details.  Most of those 
> folks participate here, too, but they're more likely to notice your 
> question.  Before you go there, however, you should read the Custom Type 
> documentation  and 
> study, say, the current implementation of the Interface resource type and 
> its provider to get oriented to the task.
>
> You should also consider whether you really need Puppet to issue 
> *arbitrary* commands to your routers.  Puppet is fundamentally a 
> state-management service, and it works best when used that way.  If you can 
> characterize the objective of the IOS commands you want to run in terms of 
> managing some aspect of the state of the device, especially an aspect whose 
> value can be not only twiddled but examined, then it would probably be both 
> easier and better to achieve that objective by adding a property to one of 
> the existing resource types used by 'puppet device'.  Of course, I would 
> suggest doing that in the context of a feature request.
>
>  
>
>>
>> Puppet device already has that telnet/ssh connection info so how can I 
>> send the devices my own arbitrary commands from my module?
>>
>>
>
> Well no, it's not 'puppet device' itself that has that (I don't think), 
> it's the providers for the custom types involved.  There are no hooks for 
> it in the DSL, but as I said, you could write your own custom type, with a 
> provider that uses the same Ruby support base.
>
>  
>
>> Is there a way I can refer to the telnet session/connection in my module 
>> and just enter my own commands?
>>
>>
>
> Not without first writing a pile of Ruby code to make it possible, no.
>
> It is perhaps appropos to observe at this point, as I have at times in the 
> past, that Puppet is not a script engine.  Puppet DSL has some scr

[Puppet Users] Re: Using exec with puppet device management?

[jcbollinger]

On Monday, December 21, 2015 at 12:30:16 PM UTC-6, red 888 wrote:
>
> Thanks for replying!
>
> I'm aware of how puppet device works and I know there is no actual agent 
> software running on the Cisco device (I'm not talking about the newer OnePK 
> thing).
>
> My question was how can I use this to send my own commands in a integrated 
> way- meaning the same way Puppet Device does it.
>


There is nothing particularly magical about 'puppet device'.  It relies on 
the same Puppet infrastructure as the agent, and in fact, it seems mostly 
to be just a specialization of the agent.  The "integrated way" in which 
'puppet device' delivers commands to network devices is not directly 
accessible at the DSL level.  It is an aspect of the Ruby implementations 
of the providers for the resource types managed by that mechanism.

 

>
> "You could, however, use an Exec to open a telnet or ssh connection to 
> the router with which to execute a remote command; *that is akin to how 
> the built-in device management types work*"
>
> Opening my own instance of telent/ssh defeats the purpose- I want to do it 
> "how the built-in device management" feature does it. Meaning I have 
> already defined the IPs and authentication info for my routers in 
> device.conf and I don't want to have to hard code that info into the module.
>


I don't see where hard-coding data into your module comes in.  Pretty much 
no one wants to do that; instead they externalize and centralize their 
data.  You could, too.

But if you are serious about using *the same* infrastructure that the 
providers for the existing resource types use, then you are talking about 
writing a custom type and provider -- a remote analog of Exec.  That is a 
significant undertaking, especially considering that the goal is something 
that must fit even more poorly into the Puppet model than does Exec 
itself.  If you want to pursue this course anyway, then the Puppet 
Developers  group would 
be a more appropriate place to discuss the details.  Most of those folks 
participate here, too, but they're more likely to notice your question.  
Before you go there, however, you should read the Custom Type documentation 
 and study, say, the 
current implementation of the Interface resource type and its provider to 
get oriented to the task.

You should also consider whether you really need Puppet to issue *arbitrary* 
commands to your routers.  Puppet is fundamentally a state-management 
service, and it works best when used that way.  If you can characterize the 
objective of the IOS commands you want to run in terms of managing some 
aspect of the state of the device, especially an aspect whose value can be 
not only twiddled but examined, then it would probably be both easier and 
better to achieve that objective by adding a property to one of the 
existing resource types used by 'puppet device'.  Of course, I would 
suggest doing that in the context of a feature request.

 

>
> Puppet device already has that telnet/ssh connection info so how can I 
> send the devices my own arbitrary commands from my module?
>
>

Well no, it's not 'puppet device' itself that has that (I don't think), 
it's the providers for the custom types involved.  There are no hooks for 
it in the DSL, but as I said, you could write your own custom type, with a 
provider that uses the same Ruby support base.

 

> Is there a way I can refer to the telnet session/connection in my module 
> and just enter my own commands?
>
>

Not without first writing a pile of Ruby code to make it possible, no.

It is perhaps appropos to observe at this point, as I have at times in the 
past, that Puppet is not a script engine.  Puppet DSL has some script-like 
characteristics, but its role is solely to describe how to build catalogs; 
the agent never sees DSL.  For their part, Puppet catalogs are not scripts, 
nor script analogues: they are *data*.  The Puppet agent -- or its 
special-purpose analog, 'puppet device' -- uses catalog data and its own 
configuration to determine what actions to perform.  Therefore, if you want 
one of those Puppet services to manage a particular piece of state for you 
then you must convey that request by causing appropriate resources to be 
included in the target node's catalog.  If there is no existing resource 
type by which you can describe what you want, then you need to create one.


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/e6b22aa8-6c72-4186-8aa3-eab25e58b6dd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] hiera doesn't works on puppet 3.8.4

[Marco Parra D.]

Thank you for your response Dirk.

Regards.

On 22-12-2015 11:16, Dirk Heinrichs wrote:

Am 22.12.2015 um 14:39 schrieb mparrad:

DEBUG: 2015-12-22 08:31:53 -0500: Cannot find datafile 
/etc/puppetlabs/code/environments/development/hieradata/common.yaml, 
skipping

nil

The old server is CentOS 6.4, with puppet server 3.4.3-1 hiera 1.1.2-1

the new cerver is CentOS 7, with puppet server 3.8.4-1 hiera 3.0.1-1

Could you tell me what I'm doing wrong? please, or tell me what I'm 
missing here?


Hiera 3.x is for Puppet 4. There seems to be something wrong with your 
installation. This is also reflected in the path above: 
/etc/puppetlabs/code/... is used by Puppet 4. Puppet 3 uses 
/etc/puppet/...


HTH...

Dirk
--

*Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions
*Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach
*Tel*: +49 2226 159 (Ansage) 1149
*Email*: d...@recommind.com 
*Skype*: dirk.heinrichs.recommind
www.recommind.com 
--
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/GbLNjMOlqCI/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/56795B34.6010305%40recommind.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/567965C8.1010300%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] hiera doesn't works on puppet 3.8.4

[Marco Parra D.]

Hi Dirk,
I used the foreman-installer to deploy foreman with puppet, I didn't 
install puppet, was foreman, maybe it was using the wrong hiera version.


Regards.

On 22-12-2015 11:16, Dirk Heinrichs wrote:

Am 22.12.2015 um 14:39 schrieb mparrad:

DEBUG: 2015-12-22 08:31:53 -0500: Cannot find datafile 
/etc/puppetlabs/code/environments/development/hieradata/common.yaml, 
skipping

nil

The old server is CentOS 6.4, with puppet server 3.4.3-1 hiera 1.1.2-1

the new cerver is CentOS 7, with puppet server 3.8.4-1 hiera 3.0.1-1

Could you tell me what I'm doing wrong? please, or tell me what I'm 
missing here?


Hiera 3.x is for Puppet 4. There seems to be something wrong with your 
installation. This is also reflected in the path above: 
/etc/puppetlabs/code/... is used by Puppet 4. Puppet 3 uses 
/etc/puppet/...


HTH...

Dirk
--

*Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions
*Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach
*Tel*: +49 2226 159 (Ansage) 1149
*Email*: d...@recommind.com 
*Skype*: dirk.heinrichs.recommind
www.recommind.com 
--
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/GbLNjMOlqCI/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/56795B34.6010305%40recommind.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/5679659E.2040107%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] hiera doesn't works on puppet 3.8.4

[Dirk Heinrichs]

Am 22.12.2015 um 14:39 schrieb mparrad:

> DEBUG: 2015-12-22 08:31:53 -0500: Cannot find datafile
> /etc/puppetlabs/code/environments/development/hieradata/common.yaml,
> skipping
> nil
>
> The old server is CentOS 6.4, with puppet server 3.4.3-1 hiera 1.1.2-1
>
> the new cerver is CentOS 7, with puppet server 3.8.4-1 hiera 3.0.1-1
>
> Could you tell me what I'm doing wrong? please, or tell me what I'm
> missing here?

Hiera 3.x is for Puppet 4. There seems to be something wrong with your
installation. This is also reflected in the path above:
/etc/puppetlabs/code/... is used by Puppet 4. Puppet 3 uses /etc/puppet/...

HTH...

Dirk
-- 

*Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions
*Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach
*Tel*: +49 2226 159 (Ansage) 1149
*Email*: d...@recommind.com 
*Skype*: dirk.heinrichs.recommind
www.recommind.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/56795B34.6010305%40recommind.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] hiera doesn't works on puppet 3.8.4

[mparrad]

Hi Guys,
I'm trying to migrate my puppet master from Puppet 3.4.3 to 3.8.4
I'm having a lot of issues, and the last one is hiera, on the previous 
version its works fine.

in the old server I have these:

common.yaml:

---
adminusers : - "DOMAIN1\user1"
 - "DOMAIN2\user1"
 - "DOMAIN1\user2"
 - "DOMAIN1\user3"
 - "DOMAIN1\user4"
atlassianadmusers : - "DOMAIN1\user1"
- "DOMAIN2\user1"
localgroup : Administrators
noadminusers: - "none"
perlmodules: - "none"


and when I execute hiera I got these:

[root@oldserver production]# hiera -c /etc/puppet/hiera.yaml -a adminusers 
--debug environment=development
DEBUG: Tue Dec 22 08:29:49 -0500 2015: Hiera YAML backend starting
DEBUG: Tue Dec 22 08:29:49 -0500 2015: Looking up adminusers in YAML backend
DEBUG: Tue Dec 22 08:29:49 -0500 2015: Looking for data source common
DEBUG: Tue Dec 22 08:29:49 -0500 2015: Found adminusers in common
["DOMAIN1\\user1", "DOMAIN2\\user1", "DOMAIN1\\user2", "DOMAIN1\\user3", 
"DOMAIN1\\user4"]


but in the new server I have the same common.yaml file, but I got these:

[root@newserver hieradata]# hiera -c /etc/puppet/hiera.yaml -a perlmodules 
--debug environment=development
DEBUG: 2015-12-22 08:31:53 -0500: Hiera YAML backend starting
DEBUG: 2015-12-22 08:31:53 -0500: Looking up perlmodules in YAML backend
DEBUG: 2015-12-22 08:31:53 -0500: Looking for data source common
DEBUG: 2015-12-22 08:31:53 -0500: Cannot find datafile 
/etc/puppetlabs/code/environments/development/hieradata/common.yaml, 
skipping
nil

The old server is CentOS 6.4, with puppet server 3.4.3-1 hiera 1.1.2-1

the new cerver is CentOS 7, with puppet server 3.8.4-1 hiera 3.0.1-1

Could you tell me what I'm doing wrong? please, or tell me what I'm missing 
here?

Thank you in advance,

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/2aad4b80-58e1-4036-8ec0-2d09957cef43%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: Puppet Server Crashing often

[Makrand]

Hi Jermy,

Just saw your email.

a) Surprisingly puppetserver-daemon.log is blank.size zero

b) Found the init file /etc/sysconfig/pe-puppetserver. Its showing thing as
below.

# Modify this if you'd like to change the memory allocation, enable JMX, etc
> JAVA_ARGS="-Xms1024m -Xmx1024m"
>

Upon restart of puppet server service, the edited values will be reset to
default 1024(tried setting it to 512MB).

c) Upon checking with PS found following.

[root@mss-pup-mst2 puppetserver]# ps -ef | grep java
> 493   1526 1  0 Dec17 ?00:11:59
> /opt/puppetlabs/server/apps/java/lib/jvm/java/jre/bin/java -Xms512m
> -Xmx512m -Dorg.apache.activemq.UseDedicatedTaskRunner=false
> -Djava.util.logging.config.file=logging.properties -Dhawtio.realm=activemq
> -Dhawtio.role=admins
> -Dhawtio.rolePrincipalClasses=org.apache.activemq.jaas.GroupPrincipal
> -Djava.security.auth.login.config=/etc/puppetlabs/activemq/login.config
> -Dcom.sun.management.jmxremote -Djava.awt.headless=true
> -Djava.io.tmpdir=/opt/puppetlabs/server/apps/activemq/tmp
> -Dactivemq.classpath=/etc/puppetlabs/activemq;
> -Dactivemq.home=/opt/puppetlabs/server/apps/activemq
> -Dactivemq.base=/opt/puppetlabs/server/apps/activemq
> -Dactivemq.conf=/etc/puppetlabs/activemq
> -Dactivemq.data=/opt/puppetlabs/server/data/activemq -jar
> /opt/puppetlabs/server/apps/activemq/bin/activemq.jar start
> 497   1618 1  0 Dec17 ?00:21:55
> /opt/puppetlabs/server/bin/java -XX:OnOutOfMemoryError=kill -9 %p
> -Djava.security.egd=/dev/urandom -Xmx256m -Xms256m -cp
> /opt/puppetlabs/server/apps/puppetdb/puppetdb.jar clojure.main -m
> puppetlabs.puppetdb.main --config /etc/puppetlabs/puppetdb/conf.d -b
> /etc/puppetlabs/puppetdb/bootstrap.cfg
> 495   2129 1  0 Dec17 ?00:08:54
> /opt/puppetlabs/server/bin/java -XX:OnOutOfMemoryError=kill -9 %p
> -Djava.security.egd=/dev/urandom -Xmx256m -Xms256m -cp
> /opt/puppetlabs/server/apps/console-services/console-services-release.jar
> clojure.main -m puppetlabs.trapperkeeper.main --config
> /etc/puppetlabs/console-services/conf.d -b
> /etc/puppetlabs/console-services/bootstrap.cfg
>

Thanks for the links. But I saw some people (mostly youtube demos) are
using VM with 1Gigs and working.

With current resources in hand, I can allow 4GB for master node.

Makrand




On Sat, Dec 19, 2015 at 8:44 PM, Jeremy Barlow  wrote:

> Has your Puppet Server written any content into the "
> /var/log/puppetlabs/puppetserver/puppetserver-daemon.log" file?
> Memory-related errors will often be written here instead of to the
> "/var/log/puppetlabs/puppetserver/puppetserver.log" file.  For example, you
> may see something like:
>
> #
>> # java.lang.OutOfMemoryError: GC overhead limit exceeded
>> # -XX:OnOutOfMemoryError="kill -9 %p"
>> #   Executing /bin/sh -c "kill -9 34514"...
>>
>
> I agree that the problem is very likely that 2 GB is too small for the
> needs of the basic Puppet Enterprise configuration.  This link,
> http://docs.puppetlabs.com/pe/2015.2/install_system_requirements.html#evaluation-environment,
> for example, recommends 6 GB of RAM for an monolithic evaluation
> configuration.
>
> You might take a look at this link if you have not already -
> http://docs.puppetlabs.com/pe/2015.2/config_puppetserver.html.  This has
> some general advice on how to tune Puppet Server in PE, including how to
> configure the heap size for the Puppet Server JVM process.  I wouldn't
> recommend dropping the maximum heap size below the default of 2 GB but this
> documentation may be helpful to you for evaluating what the optimal
> configuration for your environment may be.
>
>
> On Wednesday, December 16, 2015 at 4:26:26 AM UTC-8, Makrand Sanap wrote:
>>
>> Hi All,
>>
>> I am doing POC for puppet enterprise. Master is on CentOS 6.4 VM with 2GB
>> ram. Puppet server is going down on its own.
>>
>> [root@mss-pup-mst2 ~]# /etc/init.d/pe-puppetserver status
>>> pe-puppetserver dead but pid file exists
>>>
>>
>>
>> I can start it without any issues, but it stays for like 30-60 Mins up.
>> then It goes down again.
>>
>> Logs are not hinting anything, but for one of shutdown, I found following
>> lines. Surprisingly they appeared for only one shutdown incident. Not for
>> others
>>
>> 2015-12-13 04:38:21,100 INFO  [p.t.internal] Shutting down due to JVM
>>> shutdown hook.
>>> 2015-12-13 04:38:21,363 INFO  [p.t.internal] Beginning shutdown sequence
>>> 2015-12-13 04:38:21,640 INFO  [p.e.s.j.pe-jruby-metrics-service] PE
>>> JRuby Metrics Service: stopping metrics sampler job
>>> 2015-12-13 04:38:21,990 INFO  [p.e.s.j.pe-jruby-metrics-service] PE
>>> JRuby Metrics Service: stopped metrics sampler job
>>> 2015-12-13 04:38:22,724 INFO  [p.t.s.w.jetty9-service] Shutting down web
>>> server(s).
>>> 2015-12-13 04:38:22,808 INFO  [p.t.s.w.jetty9-core] Shutting down web
>>> server.
>>> 2015-12-13 04:38:23,243 INFO  [o.e.j.s.ServerConnector] Stopped
>>> ServerConnector@4369ad74{SSL-HTTP/1.1}{0.0.0.0:8140}
>>> 2015-12-13 04:38:23,262 

[Puppet Users] Re: PuppetDB not working with PostgreSQL

[homerjuhuu78]

Hi Russ,

thanks a lot, that fixed my problem!
I'm sorry that I didn't find that ticket myself, but it was created after 
my extensive google and ticket search and i was concerned with other stuff 
at that time.

So again, thanks and Merry Christmas!
Benjamin

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