Re: [Puppet Users] Ordering agent runs

[Thomas Müller]

Am Mittwoch, 7. Oktober 2015 23:21:59 UTC+2 schrieb Xav Paice:
>
> On 07/10/15 08:20, Rick Lindal wrote:
>
> Thanks for the link Martin. We are using open source.
>
>
sounds like it will be made available later on:

"Language changes used to model applications will be available as part of 
Open Source Puppet, with additional open source tooling coming in 
subsequent updates."

 

-- 
You received this message because you are subscribed 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/92710555-a26c-4bc4-9d13-7771fadcdb7e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Why the copied file on client site will not be recovered from server?

[Wei Chen]

Hi,

I change the copied file on client site on purpose to see if this will be 
recovered by server. According to the document, the changed file on client 
will be recovered by server every half an hour. But this doesn't happen.

Why?

-- 
You received this message because you are subscribed 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/577b6116-f213-4367-9e69-ae0f57c7d5e6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Waiting for Node Classifier to start

[Nandaraj Ks]

Hi ,

I am trying to install puppet enterprise in ubuntu 12.04 with 4 core 
processor and 16 GB ram at the final stage installation i stuck with the 
"Waiting for Node Classifier to start" and show following log message

"

** HTTP_PROXY= http_proxy= HTTPS_PROXY= https_proxy= 
/opt/puppetlabs/puppet/bin/curl --tlsv1 -s --cacert 
/etc/puppetlabs/puppet/ssl/certs/ca.pem --key 
/opt/puppetlabs/server/data/console-services/certs/puppet.marlabs.com.private_key.pem
 --cert 
/opt/puppetlabs/server/data/console-services/certs/puppet.marlabs.com.cert.pem 
https://puppet.marlabs.com:4433/classifier-api/v1/last-class-update | grep -q 
last_update.*[[:digit:]]"
I have check the 4433 port and pe-console-services  is not able to start and 
tried to start manually but not able to start.


Thank you
Nandaraj.ks

-- 
You received this message because you are subscribed 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/8a00529d-0802-4a90-a113-a5e55649862a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Managing Chocolatey sources with File resource and Template on Windows 7 x64 SP1

[Fredrik Nilsson]

Let's see if I can shed some light on this. Updated to Chocolatey 
0.9.10-beta1 to see if this behaviour disappears, sadly it didn't. To 
puppet runs back to back will result in the file getting replaced both 
runs. There are no "manual" chocolatey interference during those runs as 
they are back to back, allthough I notice quite som action in my 
chocolatey.log durring those runs. I'm a little uncertain if that is the 
normal behaviour or not as I haven't monitored this file before this issue 
occured. I asked my puppet master right now and he had the feeling this 
surfaced when we moved from agent version 3.8.1 to 3.8.3, I'm not 100% with 
him on that as I know there where some server updates in the same time 
frame. Anyhow, logs are fun so I'm gonna give you the 225 rows it logs 
during the normal puppet run that might cast a light on whether chocolatey 
or puppet is the bad guy

chocolatey.log:
2015-10-08 08:47:56,795 [DEBUG] - Configured 
chocolatey.infrastructure.logging.log4net.config.xml from assembly choco, 
Version=0.9.10.0, Culture=neutral, PublicKeyToken=79d02ea9cad655eb
2015-10-08 08:47:56,795 [DEBUG] - Configured 
chocolatey.infrastructure.logging.log4net.config.xml from assembly choco, 
Version=0.9.10.0, Culture=neutral, PublicKeyToken=79d02ea9cad655eb
2015-10-08 08:47:56,826 [DEBUG] - XmlConfiguration is now operational
2015-10-08 08:47:57,154 [DEBUG] - Attempting to delete file 
"C:\ProgramData\chocolatey\config\chocolatey.config.update".
2015-10-08 08:47:57,217 [INFO ] - 0.9.10-beta1
2015-10-08 08:48:08,873 [DEBUG] - Configured 
chocolatey.infrastructure.logging.log4net.config.xml from assembly choco, 
Version=0.9.10.0, Culture=neutral, PublicKeyToken=79d02ea9cad655eb
2015-10-08 08:48:08,873 [DEBUG] - Configured 
chocolatey.infrastructure.logging.log4net.config.xml from assembly choco, 
Version=0.9.10.0, Culture=neutral, PublicKeyToken=79d02ea9cad655eb
2015-10-08 08:48:08,920 [DEBUG] - XmlConfiguration is now operational
2015-10-08 08:48:09,232 [DEBUG] - Attempting to copy 
"C:\ProgramData\chocolatey\config\chocolatey.config.update"
 to "C:\ProgramData\chocolatey\config\chocolatey.config".
2015-10-08 08:48:09,248 [DEBUG] - Attempting to delete file 
"C:\ProgramData\chocolatey\config\chocolatey.config.update".
2015-10-08 08:48:09,310 [INFO ] - 0.9.10-beta1
2015-10-08 08:48:10,185 [DEBUG] - Configured 
chocolatey.infrastructure.logging.log4net.config.xml from assembly choco, 
Version=0.9.10.0, Culture=neutral, PublicKeyToken=79d02ea9cad655eb
2015-10-08 08:48:10,185 [DEBUG] - Configured 
chocolatey.infrastructure.logging.log4net.config.xml from assembly choco, 
Version=0.9.10.0, Culture=neutral, PublicKeyToken=79d02ea9cad655eb
2015-10-08 08:48:10,217 [DEBUG] - XmlConfiguration is now operational
2015-10-08 08:48:10,560 [DEBUG] - Attempting to delete file 
"C:\ProgramData\chocolatey\config\chocolatey.config.update".
2015-10-08 08:48:10,639 [DEBUG] - Chocolatey is running on Windows v 
6.3.9600.0
2015-10-08 08:48:10,639 [DEBUG] - Attempting to delete file 
"C:/ProgramData/chocolatey/choco.exe.old".
2015-10-08 08:48:10,639 [DEBUG] - Attempting to delete file 
"C:\ProgramData\chocolatey\choco.exe.old".
2015-10-08 08:48:10,654 [DEBUG] - Command line: 
"C:\ProgramData\chocolatey\choco.exe" list -lo -r
2015-10-08 08:48:10,654 [DEBUG] - Received arguments: list -lo -r
2015-10-08 08:48:10,732 [DEBUG] - The source 
'https://__OUR__LOCAL__REPO__/chocolatey;https://chocolatey.org/api/v2/' 
evaluated to a 'normal' source type
2015-10-08 08:48:10,732 [DEBUG] - 
NOTE: Hiding sensitive configuration data! Please double and triple 
 check to be sure no sensitive data is shown, especially if copying 
 output to a gist for review.
2015-10-08 08:48:10,748 [DEBUG] - Configuration: CommandName='list'|
CacheLocation='C:\Users\ADM_FR~1\AppData\Local\Temp'|
ContainsLegacyPackageInstalls='True'|
CommandExecutionTimeoutSeconds='2700'|
Sources='https://__OUR__LOCAL__REPO__/chocolatey;https://chocolatey.org/api/v2/'|
SourceType='normal'|Debug='False'|Verbose='False'|Force='False'|
Noop='False'|HelpRequested='False'|RegularOutput='False'|
QuietOutput='False'|PromptForConfirmation='True'|AcceptLicense='False'|
AllowUnofficialBuild='False'|AllVersions='False'|
SkipPackageInstallProvider='False'|Prerelease='False'|ForceX86='False'|
OverrideArguments='False'|NotSilent='False'|IgnoreDependencies='False'|
AllowMultipleVersions='False'|AllowDowngrade='False'|
ForceDependencies='False'|Information.PlatformType='Windows'|
Information.PlatformVersion='6.3.9600.0'|
Information.PlatformName='Windows Server 2012 R2'|
Information.ChocolateyVersion='0.9.10.0'|
Information.ChocolateyProductVersion='0.9.10-beta1'|
Information.FullName='choco, Version=0.9.10.0, Culture=neutral, 
PublicKeyToken=79d02ea9cad655eb'|
Information.Is64Bit='True'|Information.IsInteractive='True'|
Information.IsUserAdministrator='True'|
Information.IsProcessElevated='True'|Features.AutoUninstaller='True'|

Re: [Puppet Users] Write arrays to an erb

[Sergiu Cornea]

Hi Martin, 

Thank you for your response.

This is the code I have developed: 

http://pastebin.com/76SzwhZV

Thank you,

Kind regards,
Sergiu

On Wednesday, 7 October 2015 20:39:56 UTC+1, Martin Alfke wrote:
>
> Hi Sergiu, 
> On 07 Oct 2015, at 09:12, Sergiu Cornea  > wrote: 
>
> > Hello guys, 
> > 
> > I am passing 4 arrays in the Hiera file a: {a,b,c} b: {d,e,f} c: {g,h,i} 
> d: {j,k,l} which I am using them in an .erb template. However, when I am 
> trying to run Puppet it is complaining saying that cannot associate the 
> file with that name as it is already declared in a manifest. 
> > 
> > I am using the create_resource function with Puppet 3.7 on Ubuntu 14.04. 
> > 
> > Could someone please help me understand what I am doing wrong? 
>
> It would be useful to have the code pasted in gist. 
> Otherwise it will be difficult to help. 
>
> Best, 
> Martin 
>
> > 
> > Thank you, 
> > 
> > Regards, 
> > Sergiu 
> > 
> > This message and its attachments are private and confidential. If you 
> have received this message in error, please notify the sender and remove it 
> and its attachments from your system. 
> > 
> > The University of Westminster is a charity and a company limited by 
> guarantee. Registration number: 977818 England. Registered Office: 309 
> Regent Street, London W1B 2UW. 
> > 
> > 
> > -- 
> > You received this message because you are subscribed 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/f2795f58-5d39-4ff3-9a44-79d2caeeae49%40googlegroups.com.
>  
>
> > For more options, visit https://groups.google.com/d/optout. 
>
>
-- 


This message and its attachments are private and confidential. If you have 
received this message in error, please notify the sender and remove it and 
its attachments from your system.

The University of Westminster is a charity and a company 
limited by guarantee. Registration number: 977818 England. 
Registered Office: 309 Regent Street, London W1B 2UW.

-- 
You received this message because you are subscribed 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/01548fae-44ff-4849-ac6a-14aaba0e7d66%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Ordering agent runs

[Rick Lindal]

Thanks again. I certainly hope it will be made available to open source. I
like puppet but we are considering switching to SALT due to the lack of
orchestration capability.

On Thu, Oct 8, 2015 at 12:27 AM, Thomas Müller 
wrote:

>
>
> Am Mittwoch, 7. Oktober 2015 23:21:59 UTC+2 schrieb Xav Paice:
>>
>> On 07/10/15 08:20, Rick Lindal wrote:
>>
>> Thanks for the link Martin. We are using open source.
>>
>>
> sounds like it will be made available later on:
>
> "Language changes used to model applications will be available as part of
> Open Source Puppet, with additional open source tooling coming in
> subsequent updates."
>
>
>
> --
> 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/ONKtSBuE_6M/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/92710555-a26c-4bc4-9d13-7771fadcdb7e%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/CAKHF65gW1QxYj4u5cTNHJnVMOBqoMZeJVD1PBQTUSHyMU3XCWw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Why the copied file on client site will not be recovered from server?

[jcbollinger]

On Thursday, October 8, 2015 at 1:34:39 AM UTC-5, Wei Chen wrote:
>
> Hi,
>
> I change the copied file on client site on purpose to see if this will be 
> recovered by server. According to the document, the changed file on client 
> will be recovered by server every half an hour. But this doesn't happen.
>
>
A file whose content is *managed* by Puppet will see that content restored 
to whatever is specified for it whenever Puppet performs a catalog run.  If 
the agent is running in daemon mode, then by default it will attempt to 
perform a catalog run every 30 minutes.

If you modify a file and the change is not reverted within 30 minutes, then 
there is a wide variety of possible explanations, among them:

   - no catalog run has been performed.  This could be because
  - the agent does not yet have a certificate the master will accept 
  (most likely because its certificate has not yet been signed), or
  - the agent is not running in daemon mode, and has not been run 
  manually, or
  - the agent is configured not to perform catalog runs at all, or to 
  perform them only at intervals larger than 30 minutes, or
  - catalog runs have been manually disabled, or
  - the agent was unable to obtain its catalog from the master, and 
  either does not have a cached one or is configured to not use cached 
  catalogs. OR
  - the affected file's content is not under Puppet management.  This 
   could be because
  - the file itself is not under management, or
  - the file resource corresponding to the affected file specifies 
  neither a source nor content, or
  - the file resource's 'ensure' attribute is set to something other 
  than 'file', or
  - the file resource is configured with replace => false. OR
   - the agent does not have sufficient privilege to modify the file.

There may be other possibilities.

Many of those alternatives could be identified either generally or 
specifically by examination of the appropriate system log file on the 
client, and for a few of them the master's logs might also be 
illuminating.  We could perhaps rule some of them out by examination of the 
resource declaration for the file in question.  It might also be useful to 
try running the agent manually ('puppet agent -t').

Overall, however, you have not yet given us *nearly* enough information to 
diagnose the problem.


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/06e1ea9f-6708-4636-afb0-1cdda7f0ef75%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Write arrays to an erb

[Sergiu Cornea]

Hi John,

Thank you for your response.

Well what I am trying to do is to create A file with data from Hiera.

I am using this module: https://github.com/GRIF-IRFU/puppet-omd plus the 
one I have just developed to add new sites, hosts and commands. However, I 
have been asked to create Business Intelligence rules which takes some IP 
addresses and the same number of services and group them together. 

Let's say, I've got 10 nodes with 10 services each. In the bi.mk file I 
have to declare a rule which looks as follows:

aggregation_rules["customer"] = {
 'aggregation': 'worst!1!2',
 'comment': u'All the services associated with the customer',
 'nodes': [(u'10.0.0.1', u'service1_ssl'),
   (u'10.0.0.2',
u'service1_101'),
   (u'10.0.0.3',
u'service1_103')],
 'params': [],
 'title': u'Customer Services'
}

So therefore, what I am trying to do, is that I've got a template which 
does this for me, and I have specified A CLASS instead of define as you've 
said I was getting an error saying that the couldn't associate alias 
because file it is already declared (because of its path). So, the class 
i've created makes a file from an erb template. However, when I am running 
Puppet I just get printed in the file the name of the class instead of the 
data.

I was thinking about using concat but I am a Puppet beginner and I am not 
really sure how to go about incorporating the erb logic in the concat 
function.

Thank you,

Kind regards,
Sergiu

On Thursday, 8 October 2015 15:37:25 UTC+1, jcbollinger wrote:
>
>
>
> On Thursday, October 8, 2015 at 3:38:55 AM UTC-5, Sergiu Cornea wrote:
>>
>> Hi Martin, 
>>
>> Thank you for your response.
>>
>> This is the code I have developed: 
>>
>> http://pastebin.com/76SzwhZV
>>
>>
> Are we to assume that the commented-out File declaration in that code is 
> the one that causes the difficulty?  So that the error occurs with the 
> definition below?
>
> define omd::omd_create::omd_rules ( 
>   $omd_site= '', 
>   $omd_service = [], 
>   $omd_ip  = [], 
>   $h   = {}, ) { 
>   
>   file { $title: 
> path=> '/omd/sites/test/etc/check_mk/multisite.d/wato/bi.mk', 
> ensure  => file, 
> content => template('omd/bi.mk.erb'), 
>   } 
> }
>
> That would be completely believable.  Although the definition is not 
> inherently erroneous, it only accommodates a single instance, because it 
> declares a file resource with a fixed path, and any second instance will 
> therefore attempt to declare a duplicate resource.
>
> It's unclear what you're trying to do here.  If you are trying to manage 
> separate files then of course you need to specify each one's name.  If you 
> are trying to manage a single file with information gleaned from multiple 
> resources, then then consider looking into the Concat module.  On the other 
> hand, if you are indeed trying to manage a single file, then consider 
> whether you can instead do it via a single resource -- it appears that your 
> code could be modified to accommodate that, but it depends to some extent 
> on how it is used, and what you want to do with it in the future.
>
>
> John
>
>
-- 


This message and its attachments are private and confidential. If you have 
received this message in error, please notify the sender and remove it and 
its attachments from your system.

The University of Westminster is a charity and a company 
limited by guarantee. Registration number: 977818 England. 
Registered Office: 309 Regent Street, London W1B 2UW.

-- 
You received this message because you are subscribed 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/4e072c33-a7cf-40c6-9ac3-c21436db4dfe%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Write arrays to an erb

[jcbollinger]

On Thursday, October 8, 2015 at 3:38:55 AM UTC-5, Sergiu Cornea wrote:
>
> Hi Martin, 
>
> Thank you for your response.
>
> This is the code I have developed: 
>
> http://pastebin.com/76SzwhZV
>
>
Are we to assume that the commented-out File declaration in that code is 
the one that causes the difficulty?  So that the error occurs with the 
definition below?

define omd::omd_create::omd_rules ( 
  $omd_site= '', 
  $omd_service = [], 
  $omd_ip  = [], 
  $h   = {}, ) { 
  
  file { $title: 
path=> '/omd/sites/test/etc/check_mk/multisite.d/wato/bi.mk', 
ensure  => file, 
content => template('omd/bi.mk.erb'), 
  } 
}

That would be completely believable.  Although the definition is not 
inherently erroneous, it only accommodates a single instance, because it 
declares a file resource with a fixed path, and any second instance will 
therefore attempt to declare a duplicate resource.

It's unclear what you're trying to do here.  If you are trying to manage 
separate files then of course you need to specify each one's name.  If you 
are trying to manage a single file with information gleaned from multiple 
resources, then then consider looking into the Concat module.  On the other 
hand, if you are indeed trying to manage a single file, then consider 
whether you can instead do it via a single resource -- it appears that your 
code could be modified to accommodate that, but it depends to some extent 
on how it is used, and what you want to do with it in the future.


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/6cc0acf5-7db7-4cb9-af3c-921c63c6d57a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: The right way to create Hiera resources?

[jcbollinger]

On Wednesday, October 7, 2015 at 4:07:29 PM UTC-5, Marc Teale wrote:
>
> Is there a right/approved/standard way to create hiera resources for forge 
> modules that don't do it on their own?  (This is a question about the right 
> way to structure my Puppet code.  I'm not asking how to use 
> hiera_create_resources.)
>


Ok, but it's still not clear what you *are* asking.  The term "hiera 
resource" is not meaningful, so I can only guess at what you mean when you 
ask about creating one.  My first guesses at what it means to "create hiera 
resource would involve you editing your Hiera data files, however, which is 
not ordinarily something to which Puppet code structure has any relevance.  
So what in the world are you talking about?

 

>
> To create resources from hiera definitions in the past, I've used wrapper 
> classes, the quickshiftn-hiera class (an abandoned fork of hunner-hiera 
> that creates hiera resources without defining them in manifests), and small 
> class I wrote to do the job.  None of them work all that well. 
>
>

Are you asking about how to write Puppet code that declares resources with 
identities and properties drawn from your Hiera data?

 

> Let me give you an example of the structuring problem I'm running into:
>
> Say I want to install Elasticsearch.  I go to the forge, I install the 
> module, I include the class in Hiera, and define an instance, like so:
>
> ---
> classes:
>   - 'elasticsearch'
>
>  
>
> elasticsearch::ensure: 'present'
> elasticsearch::manage_repo: true
> elasticsearch::repo_version: '1.7'
> elasticsearch::instance:
>   'elasticsearch': {}
>
>
>  Elasticsearch installs, but no instance is created because the 
> elasticsearch-elasticsearch module doesn't create any hiera resources.  So, 
> what's the right way to create the instance?
>


It's still not clear what, specifically, you are asking.  Hiera is just a 
data service.  Site and machine data are very important for using Puppet 
effectively, and Hiera therefore plays a central role, but in the end it's 
still just a data service.  You cannot declare resources with Hiera, nor 
can you declare classes.  The example data you present has no inherent 
*effect* at all -- it's just data.

Much of the data is, however, structured in a way that will be meaningful 
to the catalog builder under certain circumstances.  It also contains data 
that match up with a common convention by which manifests can use Hiera 
data to determine which classes to declare.  But these are properties of 
how the data are used, not of the data themselves.

I guess in the end the question you are posing seems likely to fall into 
one of two general categories:

   1. How to write Puppet manifest code that can make effective use of 
   Hiera data to declare resources, or
   2. How to write Puppet code that declares resources based on specific 
   data you have already in hand.

Neither of those seems complete, however, inasmuch as one normally needs to 
design manifests and data together.  Moreover, there is no one approach 
that is ideal for every circumstance and person.  We can talk about this in 
the context of a specific example -- maybe elasticsearch -- but that needs 
to start with your requirements for the resulting configuration of target 
nodes, and any implementation requirements / preferences you may have.  If 
you have existing manifest code (even if it's just hiera_include('classes'))  
and data to start with then that might be helpful both as a starting point 
and to further clarify what you're after.


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/94730d0a-7a85-4650-9f92-d58e50f51c8c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Using ENC and node defintion for configuration

[jcbollinger]

On Wednesday, October 7, 2015 at 9:07:53 AM UTC-5, Richard Rechenberg wrote:
>
> Hello Puppet Users,
>
> for handling my different environments I'am using directory environments. 
> Every environment has its own node definiton stored in the nodes.pp. For 
> only one of the environments I want to use an ENC. Caused by this I added 
> the following inside the masters puppet.conf:
>
> node_terminus = exec
>> external_nodes = /opt/getClasses.sh
>>
>
> Using this configuration only the environment which nodes are known by the 
> ENC get ther configuration all other nodes which are still stored inside 
> node.pp files only get a 404 error.
>
> Has someone done this mix before?
>
>

If you configure an ENC on the master, it will be consulted for every 
catalog request, and it must return a valid result and exit with a success 
code (0).  That output can be devoid of data, but it must be provided for 
every node.  If there is also a node block for any node, then every node 
must have a corresponding node block, (even if it is a default node 
block).  Classification information from an ENC, if any, is merged with 
classification data from the appropriate node block, if any, as described 
in the ENC general documentation 
.

The bottom line is that if your master is going to use an ENC for some 
clients and node blocks for some clients, then it will expect to use both 
classification approaches together for all clients.  It is trivial to back 
up an ENC with an empty default node block to pick up clients that don't 
otherwise have a matching node block.  How you get your ENC to provide 
empty responses for nodes it doesn't otherwise want to classify depends on 
your ENC, but if there's no better alternative then you should be able to 
wrap the real ENC in a script that handles it.


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/ba51ed13-2f60-4d71-9cb4-d483f275875b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Confused after system upgrade - F22, Puppet 4.1.0-5

[Bret Wortman]

Actually, I think my hiera problem may be rleated to this line in my 
hiera.yaml file:

:yaml:
  :datadir: '/etc/puppet/environments/%{environment}/data'

Since I saw that environments changed in Puppet 4.

On Thursday, October 8, 2015 at 12:08:35 PM UTC-4, Bret Wortman wrote:
>
> So I upgraded our Puppet server to Fedora 22, which brought with it an 
> upgrade from Puppet 3.8-ish to 4.1.0-5. And as this wasn't expected (I 
> should have read and studied more -- it's definitely my fault), a few 
> things have confused me as I've started reading the Puppetlabs site for 4.1 
> documentation:
>
> 1. It says that config files are now under /etc/puppetlabs/puppet, but the 
> RPM says it installed everything to /etc/puppet as always. Which is right?
>
> 2. My hiera config, or at least the default .yaml file I set up, isn't 
> being seen -- I suspect this is related to #1, but could something else be 
> to blame? The specific error when running a Puppet 4.1 client against my 
> system (actually, the agent running on the server since this was the first 
> F22 upgrade we did) is:
>
> Error: Could not retrieve catalog from remote server: Error 400 on SERVER: 
> Evalutaiton Error: Error while evaluating a Function Call, Could not find 
> data item proxy in any Hiera data file and no default supplied at 
> /path/to/manifests/site.pp:25:10 on node puppetserver.foo.net
>
> 3. Has Puppetlabs stopped providing RPMs at their yum server? I haven't 
> seen a full set since F20.
>
> Thanks,
>
>
> Bret Wortman
>
>

-- 
You received this message because you are subscribed 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/5b2ec91c-ca65-4e6d-9b26-e354d165a169%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Ordering agent runs

[Rick Lindal]

The steep learning curve is the problem. From my research, Salt has
orchestration built in. Puppet does not. It has been a long process getting
a component stack put together and subsequent maintenance is a challenge.
Honestly, I don't have the cycles to integrate another component in the
stack. :-)

rjl

On Thu, Oct 8, 2015 at 10:42 AM, Christopher Wood <
christopher_w...@pobox.com> wrote:

> On Thu, Oct 08, 2015 at 09:45:54AM -0600, Rick Lindal wrote:
> >Thanks again. I certainly hope it will be made available to open
> source. I
> >like puppet but we are considering switching to SALT due to the lack
> of
> >orchestration capability.
>
> I'm nosy, what does salt get you that mcollective doesn't? It's easy
> enough to find articles comparing puppet to anything but comparisons of
> orchestration capabilities feel quite rare. (Using mcollective here and
> while there was a steep learning curve at the start now I have a stack of
> custom plugins.)
>
> >On Thu, Oct 8, 2015 at 12:27 AM, Thomas Müller <[1]
> tho...@chaschperli.ch>
> >wrote:
> >
> >  Am Mittwoch, 7. Oktober 2015 23:21:59 UTC+2 schrieb Xav Paice:
> >
> >On 07/10/15 08:20, Rick Lindal wrote:
> >
> >  Thanks for the link Martin. We are using open source.
> >
> >  sounds like it will be made available later on:
> >  "Language changes used to model applications will be available as
> part
> >  of Open Source Puppet, with additional open source tooling coming in
> >  subsequent updates."
> >
> >
> >  --
> >  You received this message because you are subscribed to a topic in
> the
> >  Google Groups "Puppet Users" group.
> >  To unsubscribe from this topic, visit
> >  [2]
> https://groups.google.com/d/topic/puppet-users/ONKtSBuE_6M/unsubscribe.
> >  To unsubscribe from this group and all its topics, send an email to
> >  [3]puppet-users+unsubscr...@googlegroups.com.
> >  To view this discussion on the web visit
> >  [4]
> https://groups.google.com/d/msgid/puppet-users/92710555-a26c-4bc4-9d13-7771fadcdb7e%40googlegroups.com
> .
> >  For more options, visit [5]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 [6]puppet-users+unsubscr...@googlegroups.com.
> >To view this discussion on the web visit
> >[7]
> https://groups.google.com/d/msgid/puppet-users/CAKHF65gW1QxYj4u5cTNHJnVMOBqoMZeJVD1PBQTUSHyMU3XCWw%40mail.gmail.com
> .
> >For more options, visit [8]https://groups.google.com/d/optout.
> >
> > References
> >
> >Visible links
> >1. mailto:tho...@chaschperli.ch
> >2.
> https://groups.google.com/d/topic/puppet-users/ONKtSBuE_6M/unsubscribe
> >3. mailto:puppet-users+unsubscr...@googlegroups.com
> >4.
> https://groups.google.com/d/msgid/puppet-users/92710555-a26c-4bc4-9d13-7771fadcdb7e%40googlegroups.com?utm_medium=email_source=footer
> >5. https://groups.google.com/d/optout
> >6. mailto:puppet-users+unsubscr...@googlegroups.com
> >7.
> https://groups.google.com/d/msgid/puppet-users/CAKHF65gW1QxYj4u5cTNHJnVMOBqoMZeJVD1PBQTUSHyMU3XCWw%40mail.gmail.com?utm_medium=email_source=footer
> >8. https://groups.google.com/d/optout
>
> --
> 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/ONKtSBuE_6M/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/20151008164209.GA10019%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/CAKHF65jmZHVURUwdC5mw%2BoCB3msfZJRszWNdN45YD9MX8ab9YA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Ordering agent runs

[Christopher Wood]

On Thu, Oct 08, 2015 at 09:45:54AM -0600, Rick Lindal wrote:
>Thanks again. I certainly hope it will be made available to open source. I
>like puppet but we are considering switching to SALT due to the lack of
>orchestration capability.

I'm nosy, what does salt get you that mcollective doesn't? It's easy enough to 
find articles comparing puppet to anything but comparisons of orchestration 
capabilities feel quite rare. (Using mcollective here and while there was a 
steep learning curve at the start now I have a stack of custom plugins.)

>On Thu, Oct 8, 2015 at 12:27 AM, Thomas Müller <[1]tho...@chaschperli.ch>
>wrote:
> 
>  Am Mittwoch, 7. Oktober 2015 23:21:59 UTC+2 schrieb Xav Paice:
> 
>On 07/10/15 08:20, Rick Lindal wrote:
> 
>  Thanks for the link Martin. We are using open source.
> 
>  sounds like it will be made available later on:
>  "Language changes used to model applications will be available as part
>  of Open Source Puppet, with additional open source tooling coming in
>  subsequent updates."
>   
> 
>  --
>  You received this message because you are subscribed to a topic in the
>  Google Groups "Puppet Users" group.
>  To unsubscribe from this topic, visit
>  
> [2]https://groups.google.com/d/topic/puppet-users/ONKtSBuE_6M/unsubscribe.
>  To unsubscribe from this group and all its topics, send an email to
>  [3]puppet-users+unsubscr...@googlegroups.com.
>  To view this discussion on the web visit
>  
> [4]https://groups.google.com/d/msgid/puppet-users/92710555-a26c-4bc4-9d13-7771fadcdb7e%40googlegroups.com.
>  For more options, visit [5]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 [6]puppet-users+unsubscr...@googlegroups.com.
>To view this discussion on the web visit
>
> [7]https://groups.google.com/d/msgid/puppet-users/CAKHF65gW1QxYj4u5cTNHJnVMOBqoMZeJVD1PBQTUSHyMU3XCWw%40mail.gmail.com.
>For more options, visit [8]https://groups.google.com/d/optout.
> 
> References
> 
>Visible links
>1. mailto:tho...@chaschperli.ch
>2. https://groups.google.com/d/topic/puppet-users/ONKtSBuE_6M/unsubscribe
>3. mailto:puppet-users+unsubscr...@googlegroups.com
>4. 
> https://groups.google.com/d/msgid/puppet-users/92710555-a26c-4bc4-9d13-7771fadcdb7e%40googlegroups.com?utm_medium=email_source=footer
>5. https://groups.google.com/d/optout
>6. mailto:puppet-users+unsubscr...@googlegroups.com
>7. 
> https://groups.google.com/d/msgid/puppet-users/CAKHF65gW1QxYj4u5cTNHJnVMOBqoMZeJVD1PBQTUSHyMU3XCWw%40mail.gmail.com?utm_medium=email_source=footer
>8. 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/20151008164209.GA10019%40iniquitous.heresiarch.ca.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Error:Could not autoload puppet/type/ec2_instance: /etc/puppet/modules/aws/lib/puppet/type/ec2_instance.rb:31:

[jcbollinger]

On Wednesday, October 7, 2015 at 11:06:50 AM UTC-5, Ramkumar Nagaraj wrote:
>
> Does anyone have experience with getting the puppetlabs-aws module to 
> work? 
>
> I am running:
>
> Puppet 3.8.3 
>
> Centos 6.7
>
> Ruby 1.8.7
>
>
> Following the readme on the forge:
>
> http://ift.tt/1Q4LHkQ
>
>
> I should be able to run commands like
>
> puppet apply tests/create.pp --test puppet apply tests/test.pp --test
>
>
> But i keep getting the error:
>
> *Error: Could not autoload puppet/type/ec2_instance: 
> /etc/puppet/modules/aws/lib/puppet/type/ec2_instance.rb:31: syntax error, 
> unexpected ':', expecting ')' newparam(:name, namevar: true) do ^ 
> /etc/puppet/modules/aws/lib/puppet/type/ec2_instance.rb:227: syntax error, 
> unexpected kEND, expecting $end Error: Could not autoload 
> puppet/type/ec2_instance: 
> /etc/puppet/modules/aws/lib/puppet/type/ec2_instance.rb:31: syntax error, 
> unexpected ':', expecting ')' newparam(:name, namevar: true) do ^ 
> /etc/puppet/modules/aws/lib/puppet/type/ec2_instance.rb:227: syntax error, 
> unexpected kEND, expecting $end on node  Error: Could 
> not autoload puppet/type/ec2_instance: 
> /etc/puppet/modules/aws/lib/puppet/type/ec2_instance.rb:31: syntax error, 
> unexpected ':', expecting ')' newparam(:name, namevar: true) do ^ 
> /etc/puppet/modules/aws/lib/puppet/type/ec2_instance.rb:227: syntax error, 
> unexpected kEND, expecting $end on node ***
>
>
> In addition from the readme, I should be able to run commands like
>
> puppet node_aws list. But i keep getting that the subcommand node_aws is 
> unknown.
>
> What am I missing?
>
>
>

The Ruby syntax error being reported strongly suggests a problem with the 
version of Ruby you are using.  Although Puppet 3 itself is compatible with 
Ruby 1.8.7, the puppetlabs-aws  
module documents Ruby 1.9 as a minimum requirement.  I'm not much impressed 
by the mismatch in requirements, but in truth, continuing support for Ruby 
1.8[.7] has been an irksome and sometimes difficult problem in the main 
code base, and Puppet 4 drops support for Ruby 1.8 altogether.

You could address the issue by installing a Ruby 1.9 subsystem and 
configuring Puppet to use it.  If you adopt that approach then you will 
probably need to arrange for it to be done not just on the master but also 
on the clients.  Alternatively, you could look for a different module that 
does what you want, or write your own.  If you have a budget for this then 
you could consider engaging PL's (or someone else's) consulting services to 
update the module for compatibility with your Ruby.  I'm inclined to doubt 
that PL would otherwise accept this as a flaw that it is obligated to fix, 
since the module's requirements are well documented, and PL has long been 
moving away from Ruby 1.8.


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/a026c6de-46ba-49f0-ba06-28b486f25fe3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Confused after system upgrade - F22, Puppet 4.1.0-5

[Bret Wortman]

So I upgraded our Puppet server to Fedora 22, which brought with it an 
upgrade from Puppet 3.8-ish to 4.1.0-5. And as this wasn't expected (I 
should have read and studied more -- it's definitely my fault), a few 
things have confused me as I've started reading the Puppetlabs site for 4.1 
documentation:

1. It says that config files are now under /etc/puppetlabs/puppet, but the 
RPM says it installed everything to /etc/puppet as always. Which is right?

2. My hiera config, or at least the default .yaml file I set up, isn't 
being seen -- I suspect this is related to #1, but could something else be 
to blame? The specific error when running a Puppet 4.1 client against my 
system (actually, the agent running on the server since this was the first 
F22 upgrade we did) is:

Error: Could not retrieve catalog from remote server: Error 400 on SERVER: 
Evalutaiton Error: Error while evaluating a Function Call, Could not find 
data item proxy in any Hiera data file and no default supplied at 
/path/to/manifests/site.pp:25:10 on node puppetserver.foo.net

3. Has Puppetlabs stopped providing RPMs at their yum server? I haven't 
seen a full set since F20.

Thanks,


Bret Wortman

-- 
You received this message because you are subscribed 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/0e9e133a-1d48-45c3-9a1f-ead296205868%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Augeas type: Removing an entry from /etc/hosts

[Seth Rice]

I know this is way late, by 5 years or so, but I wanted to share what I 
just discovered, related to your post. Since your post did help me discover 
it after all.  I only got into augeas 4 days ago, and puppet about a month 
ago. 

Though augeas is a harsh mistress, I found that you can do some good 
sudoers stuff with it. Also how to specify if you want it to wipe a 
matching entry and replace it, or just replace pieces of it. 

I have a module that has it's own user that will be created, and 
permissions granted in sudoers and locked down. Here is what I found works 
on the current opensource puppet today. 

This augeas (awe-geez) excerpt below is from the user manifest in that 
module. Above I have all the regular puppet jazz to create a user, it's 
home path, create keys, etc. It all references back to a params.pp file for 
the variables. I found that with puppet, things work more consistently if 
you use this type of setup for a variable. 

"${User}"

Double quotes, and braces between the $ and the actual variable. However 
Augeas doesn't like that setup. so once you start getting to the 'changes 
=> [ ' part, you need to change your variable statements to be what you'd 
have in bash. 

$User

Also note, as seen below, I use the double quotes for my commands when 
using a variable. Otherwise use single quotes. 

  augeas { "sudoers user ${User}":
   context  => '/files/etc/sudoers',
   changes  => [
"set spec[user = '$User']/user $User",
"set spec[user = '$User']/host_group/host ALL",
"set spec[user = '$User']/host_group/command ALL",
"set spec[user = '$User']/host_group/command/runas_user ALL",
"set spec[user = '$User']/host_group/command/tag NOPASSWD",
   ],
   require  => [ User[$User] ],
  }

  augeas { "sudoers user ${User} TTY":
   context  => '/files/etc/sudoers',
   changes  => [
"set Defaults[type = ':$User']/type :$User",
"set Defaults[type = ':$User']/requiretty/negate ''",
   ],
   require => [ augeas["sudoers user $User"] ],
  }

  augeas { "sudoers Cmnd_Alias ${CMNDALIAS}":
   context => '/files/etc/sudoers',
   changes => [
"rm  Cmnd_Alias[alias/name = '$CMNDALIAS']/alias/command[.]",
"set Cmnd_Alias[alias/name = '$CMNDALIAS']/alias/name $CMNDALIAS",
"set Cmnd_Alias[alias/name = '$CMNDALIAS']/alias/command[1] 
/bin/cp",
"set Cmnd_Alias[alias/name = '$CMNDALIAS']/alias/command[2] 
/bin/grep",
"set Cmnd_Alias[alias/name = '$CMNDALIAS']/alias/command[3] 
/bin/date",
"set Cmnd_Alias[alias/name = '$CMNDALIAS']/alias/command[4] 
/bin/ls",
"set Cmnd_Alias[alias/name = '$CMNDALIAS']/alias/command[5] 
/bin/rm",
"set Cmnd_Alias[alias/name = '$CMNDALIAS']/alias/command[6] 
/bin/mv",
   ],
   require => File['/etc/sudoers'],
  }


Now the key thing I wanted to point out that I just discovered in all this, 
is this line in the Cmnd_Alias section. 

"rm  Cmnd_Alias[alias/name = '$CMNDALIAS']/alias/command[.]",

There is a subtle difference between using a [.] or a [*]. Because I'm 
declaring which command goes in what order, the dot will match any command, 
and the * will match only the ones stated in this manifest, and ignore the 
rest. So I went to [6] in my command listing above. This means with a dot 
[.], it will blow away 1-6, as well as any others, like 7-999, or however 
high it can go. If I use the star [*], then it only replace 1-6, and leave 
7-999 or however high, well alone. 

Here is a command I've been running on the system I want to apply the 
changes on, to show me what augeas sees while I work. 

watch -n3 "augtool print /files/etc/sudoers | grep -Ei '(use 
r|host_group|alias|defaults\[11\])' | grep -Ev '(spec\[(1|2)\]|comment)'"

that output for me looks like this:

Every 3.0s: augtool print /files/etc/sudoers | grep ...  Thu Oct  8 
11:23:52 2015

/files/etc/sudoers/Defaults[6]/env_keep/var[5] = "USERNAME"
/files/etc/sudoers/spec[3]/user = "dude"
/files/etc/sudoers/spec[3]/host_group
/files/etc/sudoers/spec[3]/host_group/host = "ALL"
/files/etc/sudoers/spec[3]/host_group/command = "ALL"
/files/etc/sudoers/spec[3]/host_group/command/runas_user = "ALL"
/files/etc/sudoers/spec[3]/host_group/command/tag = "NOPASSWD"
/files/etc/sudoers/Defaults[11]
/files/etc/sudoers/Defaults[11]/type = ":dude"
/files/etc/sudoers/Defaults[11]/requiretty
/files/etc/sudoers/Defaults[11]/requiretty/negate
/files/etc/sudoers/Cmnd_Alias
/files/etc/sudoers/Cmnd_Alias/alias
/files/etc/sudoers/Cmnd_Alias/alias/name = "DUDEADMIN"
/files/etc/sudoers/Cmnd_Alias/alias/command[1] = "/bin/cp"
/files/etc/sudoers/Cmnd_Alias/alias/command[2] = "/bin/grep"
/files/etc/sudoers/Cmnd_Alias/alias/command[3] = "/bin/date"
/files/etc/sudoers/Cmnd_Alias/alias/command[4] = "/bin/ls"
/files/etc/sudoers/Cmnd_Alias/alias/command[5] = "/bin/rm"
/files/etc/sudoers/Cmnd_Alias/alias/command[6] = "/bin/mv"

So why does all this matter? As far as I can tell 

[Puppet Users] How to specify wildcat in target path?

[staceytian4321]

Hi all,

I am using open source puppet 3.7.3. Wondering if anyone knows how to 
specify wildcat in target path?

For example, I want to specify a target path as:

/home/user/*/test1/*/local

I don't know what the pattern will be under folder /home/user, so I need to 
use /home/user/*

But it doesn't work

Any clue how to achieve this function?

Thanks,
Stacey

-- 
You received this message because you are subscribed 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/67af788e-7365-484a-9ac5-e9c4a4286f0e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] PuppetDB Service Won't Install/Start

[Wyatt Alt]

Hey Dan,

I see the bottom of a java stacktrace in your log snippet there -- could 
you get the full stacktrace from journalctl and stick it in a gist?


Wyatt

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

Re: [Puppet Users] Confused after system upgrade - F22, Puppet 4.1.0-5

[Martin Alfke]

Hi Bret,

On 08 Oct 2015, at 09:08, Bret Wortman  wrote:

> So I upgraded our Puppet server to Fedora 22, which brought with it an 
> upgrade from Puppet 3.8-ish to 4.1.0-5. And as this wasn't expected (I should 
> have read and studied more -- it's definitely my fault), a few things have 
> confused me as I've started reading the Puppetlabs site for 4.1 documentation:
> 
> 1. It says that config files are now under /etc/puppetlabs/puppet, but the 
> RPM says it installed everything to /etc/puppet as always. Which is right?

The PuppetLabs website refers to PL packages.
Maybe Fedora Packages still have everything in /etc/puppet.

> 
> 2. My hiera config, or at least the default .yaml file I set up, isn't being 
> seen -- I suspect this is related to #1, but could something else be to 
> blame? The specific error when running a Puppet 4.1 client against my system 
> (actually, the agent running on the server since this was the first F22 
> upgrade we did) is:
> 
> Error: Could not retrieve catalog from remote server: Error 400 on SERVER: 
> Evalutaiton Error: Error while evaluating a Function Call, Could not find 
> data item proxy in any Hiera data file and no default supplied at 
> /path/to/manifests/site.pp:25:10 on node puppetserver.foo.net
> 
> 3. Has Puppetlabs stopped providing RPMs at their yum server? I haven't seen 
> a full set since F20.

The last set of Packages has been made for Fedora 21:
https://docs.puppetlabs.com/puppet/latest/reference/system_requirements.html#fedora

> 
> Thanks,
> 
> 
> Bret Wortman
> 
> 
> -- 
> You received this message because you are subscribed 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/0e9e133a-1d48-45c3-9a1f-ead296205868%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/3FCC3CBF-B118-4709-B515-2C8F07B4CEC2%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] PuppetDB Service Won't Install/Start

[Dan]

Hi,

I've just started to build a Centos 7 puppet master and I've applied the 
puppetdb classes as follows:

  class { 'puppetdb':  }


  class { 'puppetdb::master::config':
require => Class['puppetdb']
  }

The whole catalog runs fine also installing puppetserver but when it gets 
to starting the puppetdb service it blows up and if I check the service 
status I get:

[root@basecentos ~]# systemctl status puppetdb.service
puppetdb.service - puppetdb Service
   Loaded: loaded (/usr/lib/systemd/system/puppetdb.service; disabled)
   Active: failed (Result: exit-code) since Fri 2015-10-09 04:05:02 JST; 
25min ago
  Process: 21591 ExecStartPost=/bin/bash ${INSTALL_DIR}/ezbake-functions.sh 
wait_for_app (code=exited, status=1/FAILURE)
  Process: 21590 ExecStart=/usr/bin/java $JAVA_ARGS 
-XX:OnOutOfMemoryError=kill -9 %%p -Djava.security.egd=/dev/urandom -cp 
${INSTALL_DIR}/puppetdb.jar clojure.main -m puppetlabs.puppetdb.main 
--config ${CONFIG} -b ${BOOTSTRAP_CONFIG} $@ (code=exited, status=1/
FAILURE)
 Main PID: 21590 (code=exited, status=1/FAILURE)

Oct 09 04:05:02 basecentos java[21590]: clojure.main$main.doInvoke 
(main.clj:421)
Oct 09 04:05:02 basecentos java[21590]: clojure.lang.RestFn.invoke 
(RestFn.java:512)
Oct 09 04:05:02 basecentos java[21590]: clojure.lang.Var.invoke 
(Var.java:409)
Oct 09 04:05:02 basecentos java[21590]: clojure.lang.AFn.applyToHelper 
(AFn.java:178)
Oct 09 04:05:02 basecentos java[21590]: clojure.lang.Var.applyTo 
(Var.java:700)
Oct 09 04:05:02 basecentos java[21590]: clojure.main.main (main.java:37)
Oct 09 04:05:02 basecentos systemd[1]: puppetdb.service: main process 
exited, code=exited, status=1/FAILURE
Oct 09 04:05:02 basecentos systemd[1]: puppetdb.service: control process 
exited, code=exited status=1
Oct 09 04:05:02 basecentos systemd[1]: Failed to start puppetdb Service.
Oct 09 04:05:02 basecentos systemd[1]: Unit puppetdb.service entered failed 
state.


I've been looking around and have no idea how how to get past this next 
bitany suggestions?

Thanks

Dan

-- 
You received this message because you are subscribed 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/5de4632c-fdc6-42a7-a443-d05ee3d3fdbe%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.