[Puppet Users] rake edits not showing up in the console

[Jay Benner]

Edits done via node:groups are reporting back "successfully edited", but 
when I look in the console, no change.  What gives?

Ubuntu 12.04
Puppet Enterprise 3.2.0

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

[Puppet Users] Re: Anyone have sample output from Facter on Joyent?

[Matthew Haughton]

Actually all the OS related ones such as osfamily, operatingsystem, kernel 
etc would be fantastic.

On Saturday, 20 September 2014 22:44:04 UTC-4, Matthew Haughton wrote:
>
> Specifically value of "kernelversion".
>
> 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/de1ef940-bc87-45f3-baa6-caefb82628e4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Anyone have sample output from Facter on Joyent?

[Matthew Haughton]

Specifically value of "kernelversion".

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/98709127-52f0-4727-9997-997eca69853c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Manage a single file (directory) from multiple modules

[aarb000]

Thanks Neil,

I am not sure I understand exactly what you mean, so I will post the code I 
have done for testing (I am using different paths, but the concept is the 
same as the original post). 

Here is the class with the define.  It is in a module called copy_directory.

class copy_directory {
}

define managed_preferences ($source = undef) {
  file {"/tmp/":
source  => "puppet:///modules/${source}/tmp",
recurse => true,
owner   => "root",
group   => "root",
mode=> 600,
  }
}

Here is the module that calls it.  

include copy_directory

class test_module {
  managed_preferences { 'title':
  source => "$module_name",
  }
}

I also created a module called test_module2 with the same code.  I know 
that file {"/tmp/": is causing the problem, but the entire point is 
different modules copy files into that directory. To me I'm defining it 
once, and using it twice.  As I defined it in the copy_directory module, 
and I am using it in the test_module and test_module2.   What am I doing 
wrong?

On Saturday, September 20, 2014 12:11:28 PM UTC-5, Neil wrote:
>
> Hi
>
> You should not define it twice. You use it twice.
>
> As in your example the apache uses the firewall define. It does not define 
> the file resource again.
>
> Define managed_preference in a class that you'll use as a library and use 
> that in the modules that need it.
>
> Note the resources using the define 
> each have their own name
>
> Neil
> On 20 Sep 2014 17:46, > wrote:
>
>> I figured out how to create a define type and again it works for the 
>> first module, but when I add a second I get the exact same error which is 
>> what I expected based on the link below.
>>
>> So, does anyone know how to accomplish this?  
>>
>> On Friday, September 19, 2014 6:59:19 PM UTC-5, aar...@gmail.com wrote:
>>>
>>> It appears I'm looking for a defined type to do this.   
>>> https://docs.puppetlabs.com/learning/definedtypes.html#
>>> special-little-flowers
>>>
>>> I'll see if I can get this to work for my purpose though this article 
>>> mentions duplicate definitions and I'm guessing I'll have the same problem. 
>>>  
>>>
>>> On Friday, September 19, 2014 5:34:08 PM UTC-5, aar...@gmail.com wrote:

 Glad the concept is correct, but I've been playing with it and am not 
 sure which part of the firewall class processes the passed on code. In the 
 firewall/apache analogy, you use the following code.

 class apache {
   firewall { '100 allow http and https access':
 port   => [80, 443],
 proto  => tcp,
 action => accept,
 }

 What I am not seeing is what part of the firewall class receives this 
 information and knows what to do with those parameters.  If I understood 
 this, I could probably figure out my example.  

 I tried in my situation

 managed_preferences { 
source  => "puppet:///modules/office_2011/Preferences",
require => Package["$main_package"],
  }

 thinking that it would send these two parameters to the newly create 
 managed_preferences class.  Again, I don't know how to receive the 
 information to process it in the managed_preferences class.   Is the 
 managed_preferences class a different type of class than the office_2011 
 class?  If I knew the official terminology I could look it up and probably 
 figure this out.  

 Thanks again

 On Friday, September 19, 2014 5:06:15 PM UTC-5, Ygor wrote:
>
> Use the same approach the firewall module uses:  A main class, 
> declared at a global level, creates/manages the folder. A defined type is 
> used to create/manage imdividual prefs files and is involed inside the 
> module for the individual app.
>
> A basic pronciple of object-oriented code. Pull out the common bits 
> and manage them in one place - in this case: the common folder. 
>
> "Sometimes I think the surest sign that intelligent life exists 
> elsewhere in the universe is that none of it has tried to contact us."
>
> Bill Waterson (Calvin & Hobbes)
>
> On Sep 19, 2014, at 5:09 PM, aar...@gmail.com wrote:
>
> I have a single class for every application to be installed on our 
> Macintosh clients.  The problem I am having is in the section of the 
> class 
> below.  This copies files to the User Template folder so when users login 
> they get predefined preferences.  
>
> file { "System/Library/User Template/English.lproj/
> Library/Preferences/":
> source  => "puppet:///modules/office_2011/Preferences",
> owner   => "root",
> group   => "wheel",
> mode=> 600,
> recurse => true,
> require => Package["$main_package"],
> }
>
> This would work perfect if I had only one application in which I 
> wanted managed preferences.  I am getting an error that the User Template 
> folder is being 

Re: [Puppet Users] Re: Unable to do "puppet apply nodes.pp"

[Felix Frank]

On 09/20/2014 08:46 PM, Justin tim wrote:
>
> It was a silly mistake that i was doing. I was creating the manifest
> in wrong dir path. My actual environment where puppet would look for
> manifest files is --/etc/puppet/environment/production/manfiest.

Does not compute. Your original post stated that you used

puppet apply user-absent.pp


which looks up the current directory and no other locations.

I suspect that the information you presented was incomplete or
inaccurate. This is acceptable, but please try and be more responsive to
the fellow users who take the time and try to help you out.

> t would be of great help if someone could tell me how to push files on
> multiple clients from the puppet master server ( though i understand
> that puppet is a "pull" system and not a "push" ) using 'puppet apply
> file.pp' . I came accross an article saying that "puppet kick" does a
> push, but again read somewhere that it is depricated in newer versions
> of puppet.

Please open a new thread if you have followup questions that are rather
unrelated to the original topic. Make sure to elaborate on your desired
scenario, so that everyone can give you more educated advice.

-- 
You received this message because you are subscribed 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/541DCD7F.1040907%40Alumni.TU-Berlin.de.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Unable to do "puppet apply nodes.pp"

[Justin tim]

Hi all,

Thanks for all your help and suggestions. The issue got resolved.

It was a silly mistake that i was doing. I was creating the manifest in 
wrong dir path. My actual environment where puppet would look for manifest 
files is --/etc/puppet/environment/production/manfiest.

And i was placing my manifest files under /etc/puppet/manifest. I read all 
of your suggestions and applied each one of them turn by turn, and it seems 
to be working fine for me.

It would be of great help if someone could tell me how to push files on 
multiple clients from the puppet master server ( though i understand that 
puppet is a "pull" system and not a "push" ) using 'puppet apply file.pp' . 
I came accross an article saying that "puppet kick" does a push, but again 
read somewhere that it is depricated in newer versions of puppet.

Would require your expert advise. Kindly suggest.

Thanks in Advance.

On Friday, 19 September 2014 16:51:21 UTC+1, jcbollinger wrote:
>
>
>
> On Thursday, September 18, 2014 6:22:22 PM UTC-5, Jürgen Hermann wrote:
>>
>> The Puppet file you pass to an apply is basically a full site.pp, so try 
>> adding a "node default {…}" around your resources.
>>
>> See https://github.com/jhermann/devpi-puppet/blob/master/site.pp#L31 for 
>> an example.
>>
>>
>
> No, a node block should be unnecessary in this case.  Any declarations 
> appearing at top scope apply to all nodes.  It is in fact possible to 
> support a full-scale site without any node blocks at all (not even a 
> default node).
>
> The most likely explanation is that the named user already exists, which 
> is what Felix was probing.  It is also possible that the problem is related 
> to a missing Ruby module (e.g. ruby-shadow, as shashank suggested), but in 
> that case I would have expected Puppet to emit an error message.
>
>
> 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/14f644d7-da10-4d9b-a084-ea057cd41fc2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: Puppet Explorer 1.3.0

[Erik Dalén]

Yeah, if there was a commonly accepted ENC tool I could probably add
support for that in Puppet Explorer. But it seems that more and more people
just move classification to hiera instead, and most hiera backends don't
have any API to use from a web UI.

On 19 September 2014 14:57, Spencer Krum  wrote:

> Puppet Explorer and PuppetBoard are both superior to the Puppet Dashboard.
> Puppet dashboard is in community support, but this list is full of people
> having trouble installing it. I would highly recommend using one of the
> other tools.
>
> What the Puppet Dashboard does do that the other tools do not do is ENC
> functionality. I think there is a space for an open source lightweight ENC
> to be written for organizations to use and hack on.
>
> Thanks,
> Spencer
>
>
>
>
> On Fri, Sep 19, 2014 at 12:38 PM, PierreR  wrote:
>
>> Out of curiosity, how does it compare with puppet dashboard ?
>>
>> Is Puppet Dashboard really EOL ?
>>
>> What's currently the best reporting open source solution for Puppet ?
>>
>> Cheers
>>
>>
>> On Friday, September 12, 2014 5:19:25 PM UTC+2, Erik Dalén wrote:
>>>
>>> A new release of Puppet Explorer is out! This release adds support for
>>> PuppetDB 2.2, but also drops support for previous PuppetDB releases (once
>>> the v4 API stabilizes it will be easier to keep compatibility).
>>>
>>> The major new feature is support for structured facts, for example you
>>> can search for system_uptime.days>100 if you are using Facter 2.2.
>>>
>>> You can now also subquery the node fields using the #node syntax, for
>>> example #node.catalog-environment=production
>>>
>>> To query for nodes matching timestamps you can use an @ sign in front of
>>> a string to have it parsed by timespec instead of typing a ISO timestamp by
>>> hand. For example: #node.report-timestamp<@"now - 2 hours"
>>>
>>> It also has support for customisable panels in the dashboard, define
>>> your own queries and show how many nodes are matching.
>>>
>>> A pre built tar.gz as well as RPM and DEB packages are available at:
>>> https://github.com/spotify/puppetexplorer/releases
>>>
>>> --
>>> Erik Dalén
>>>
>>  --
>> You received this message because you are subscribed 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/c8780e5b-2afd-43ae-b9db-17bdd87116ee%40googlegroups.com
>> 
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Spencer Krum
> (619)-980-7820
>
> --
> You received this message because you are subscribed 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/CADt6FWOS_grxgrnwkRtHbE8%2BKQAgFLJPD3EFbbNBBdU9XdWrXA%40mail.gmail.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Erik Dalén

-- 
You received this message because you are subscribed 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/CAAAzDLc%2BEUHyL9N_UqK%2BVE4G4zkvGtTFC5A3JkQSgSZ6z3dj8w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] nodes set to environment 'none'

[Tim Dunphy]

Hey all,


 For some reason my client nodes are being set to an environment called
'none'. This causes an error in puppet runs becuase the pupet server
doesn't recognize an environment called 'none'. The environment I want them
to use is called 'Production'.

This is the error that I'm getting on puppet runs

Error: /Stage[main]/Php::Configure/File[/etc/php.ini]: Could not
evaluate: *Could
not retrieve information from environment none source(s) *
puppet:///modules/php/php.ini
Error: /Stage[main]/Lumberjack::Config/File[/etc/logstash/lumberjack.conf]:
*Could
not evaluate: Could not retrieve information from environment none *source(s)
puppet:///modules/lumberjack/lumberjack.conf

 I'm on puppet 3.7 on client and server

[root@ops:~] #puppet --version
3.7.0

My puppet conf:

[main]
logdir = /var/log/puppet
rundir = /var/run/puppet
ssldir = $vardir/ssl
privatekeydir = $ssldir/private_keys { group = service }
hostprivkey = $privatekeydir/$certname.pem { mode = 640 }
autosign   = $confdir/autosign.conf { mode = 664 }

[agent]
classfile = $vardir/classes.txt
localconfig = $vardir/localconfig
default_schedules = false
report= true
pluginsync= false
masterport= 8140
environment   = production
certname  = puppet.mydomain.com
server= puppet.mydomain.com
listen= false
splay = false
runinterval   = 1800
noop  = false
show_diff = false
configtimeout = 120

[master]
autosign   = $confdir/autosign.conf { mode = 664 }
reports= foreman
external_nodes = /etc/puppet/node.rb
node_terminus  = exec
ca = true
ssldir = /var/lib/puppet/ssl
certname   = puppet.mydomain.com
[development]
modulepath =
/etc/puppet/environments/development/modules:/etc/puppet/environments/common:/usr/share/puppet/modules
config_version =
[production]
modulepath = /etc/puppet/environments/production/modules
config_version =

Could some one please let me know how I can get the client nodes to
register under the correct environment?

Thanks
Tim

-- 
You received this message because you are subscribed 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/CAOZy0e%3DtXaB0WLxOZjoU%2B_9LfRYBAwkCdsb13LYNUR-ocw42yA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Manage a single file (directory) from multiple modules

[Neil]

Hi

You should not define it twice. You use it twice.

As in your example the apache uses the firewall define. It does not define
the file resource again.

Define managed_preference in a class that you'll use as a library and use
that in the modules that need it.

Note the resources using the define
each have their own name

Neil
On 20 Sep 2014 17:46,  wrote:

> I figured out how to create a define type and again it works for the first
> module, but when I add a second I get the exact same error which is what I
> expected based on the link below.
>
> So, does anyone know how to accomplish this?
>
> On Friday, September 19, 2014 6:59:19 PM UTC-5, aar...@gmail.com wrote:
>>
>> It appears I'm looking for a defined type to do this.
>> https://docs.puppetlabs.com/learning/definedtypes.html#
>> special-little-flowers
>>
>> I'll see if I can get this to work for my purpose though this article
>> mentions duplicate definitions and I'm guessing I'll have the same problem.
>>
>>
>> On Friday, September 19, 2014 5:34:08 PM UTC-5, aar...@gmail.com wrote:
>>>
>>> Glad the concept is correct, but I've been playing with it and am not
>>> sure which part of the firewall class processes the passed on code. In the
>>> firewall/apache analogy, you use the following code.
>>>
>>> class apache {
>>>   firewall { '100 allow http and https access':
>>> port   => [80, 443],
>>> proto  => tcp,
>>> action => accept,
>>> }
>>>
>>> What I am not seeing is what part of the firewall class receives this
>>> information and knows what to do with those parameters.  If I understood
>>> this, I could probably figure out my example.
>>>
>>> I tried in my situation
>>>
>>> managed_preferences {
>>>source  => "puppet:///modules/office_2011/Preferences",
>>>require => Package["$main_package"],
>>>  }
>>>
>>> thinking that it would send these two parameters to the newly create
>>> managed_preferences class.  Again, I don't know how to receive the
>>> information to process it in the managed_preferences class.   Is the
>>> managed_preferences class a different type of class than the office_2011
>>> class?  If I knew the official terminology I could look it up and probably
>>> figure this out.
>>>
>>> Thanks again
>>>
>>> On Friday, September 19, 2014 5:06:15 PM UTC-5, Ygor wrote:

 Use the same approach the firewall module uses:  A main class, declared
 at a global level, creates/manages the folder. A defined type is used to
 create/manage imdividual prefs files and is involed inside the module for
 the individual app.

 A basic pronciple of object-oriented code. Pull out the common bits and
 manage them in one place - in this case: the common folder.

 "Sometimes I think the surest sign that intelligent life exists
 elsewhere in the universe is that none of it has tried to contact us."

 Bill Waterson (Calvin & Hobbes)

 On Sep 19, 2014, at 5:09 PM, aar...@gmail.com wrote:

 I have a single class for every application to be installed on our
 Macintosh clients.  The problem I am having is in the section of the class
 below.  This copies files to the User Template folder so when users login
 they get predefined preferences.

 file { "System/Library/User Template/English.lproj/
 Library/Preferences/":
 source  => "puppet:///modules/office_2011/Preferences",
 owner   => "root",
 group   => "wheel",
 mode=> 600,
 recurse => true,
 require => Package["$main_package"],
 }

 This would work perfect if I had only one application in which I wanted
 managed preferences.  I am getting an error that the User Template folder
 is being managed by another class.  I understand why.  I also understand
 the purpose.  This code however only copies files into the Template Folder,
 it doesn't overwrite, or purge the folder.  So, in theory, what I want to
 do should be a valid approach to managing preferences.

 I have an idea, but don't know how to execute it.  So I hope someone
 can help.

 In the Puppetlabs/Firewall module, you can access it from another
 module.  So if I have an apache module, I can tell the Firewall module I
 want to open port 80.

 I would like to make a Macintosh Managed Preferences module that will
 manage the User Template folder, and in each application module, I can
 provide that module with files.

 How can I accomplish this?

 Thanks in advance.


  --
 You received this message because you are subscribed to the Google
 Groups "Puppet Users" group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to puppet-users...@googlegroups.com.
 To view this discussion on the web visit https://groups.google.com/d/
 msgid/puppet-users/7fe782a1-fba4-4cef-aeab-4cf85ed170d2%
 40googlegroups.com
 

[Puppet Users] puppetlabs_mysql fails to import two sql scripts given as an array to the db class

[Gideon Maina]

This is so good but I would like to ask if the sql parameter to import sql 
scripts can receive an array as argument that is get two .sql file or more 
and still execute successfully, have tried to give it an array but it joins 
everything to one so that

  mysql::db{...
sql => ["/tmp/1.sql","/tmp/2.sql",]

   }

it assumes the above to be

   /tmp/1.sql/tmp/2.sql

which  is not possible  is there a way for the puppetlabs mysql module 
to have two sql scripts imported at a go

-- 
You received this message because you are subscribed 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/aa478c4a-95ee-4290-8178-cb20d71d4c4e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Manage a single file (directory) from multiple modules

[aarb000]

I figured out how to create a define type and again it works for the first 
module, but when I add a second I get the exact same error which is what I 
expected based on the link below.

So, does anyone know how to accomplish this?  

On Friday, September 19, 2014 6:59:19 PM UTC-5, aar...@gmail.com wrote:
>
> It appears I'm looking for a defined type to do this.   
> https://docs.puppetlabs.com/learning/definedtypes.html#special-little-flowers
>
> I'll see if I can get this to work for my purpose though this article 
> mentions duplicate definitions and I'm guessing I'll have the same problem. 
>  
>
> On Friday, September 19, 2014 5:34:08 PM UTC-5, aar...@gmail.com wrote:
>>
>> Glad the concept is correct, but I've been playing with it and am not 
>> sure which part of the firewall class processes the passed on code. In the 
>> firewall/apache analogy, you use the following code.
>>
>> class apache {
>>   firewall { '100 allow http and https access':
>> port   => [80, 443],
>> proto  => tcp,
>> action => accept,
>> }
>>
>> What I am not seeing is what part of the firewall class receives this 
>> information and knows what to do with those parameters.  If I understood 
>> this, I could probably figure out my example.  
>>
>> I tried in my situation
>>
>> managed_preferences { 
>>source  => "puppet:///modules/office_2011/Preferences",
>>require => Package["$main_package"],
>>  }
>>
>> thinking that it would send these two parameters to the newly create 
>> managed_preferences class.  Again, I don't know how to receive the 
>> information to process it in the managed_preferences class.   Is the 
>> managed_preferences class a different type of class than the office_2011 
>> class?  If I knew the official terminology I could look it up and probably 
>> figure this out.  
>>
>> Thanks again
>>
>> On Friday, September 19, 2014 5:06:15 PM UTC-5, Ygor wrote:
>>>
>>> Use the same approach the firewall module uses:  A main class, declared 
>>> at a global level, creates/manages the folder. A defined type is used to 
>>> create/manage imdividual prefs files and is involed inside the module for 
>>> the individual app.
>>>
>>> A basic pronciple of object-oriented code. Pull out the common bits and 
>>> manage them in one place - in this case: the common folder. 
>>>
>>> "Sometimes I think the surest sign that intelligent life exists 
>>> elsewhere in the universe is that none of it has tried to contact us."
>>>
>>> Bill Waterson (Calvin & Hobbes)
>>>
>>> On Sep 19, 2014, at 5:09 PM, aar...@gmail.com wrote:
>>>
>>> I have a single class for every application to be installed on our 
>>> Macintosh clients.  The problem I am having is in the section of the class 
>>> below.  This copies files to the User Template folder so when users login 
>>> they get predefined preferences.  
>>>
>>> file { "System/Library/User Template/English.lproj/Library/Preferences/":
>>> source  => "puppet:///modules/office_2011/Preferences",
>>> owner   => "root",
>>> group   => "wheel",
>>> mode=> 600,
>>> recurse => true,
>>> require => Package["$main_package"],
>>> }
>>>
>>> This would work perfect if I had only one application in which I wanted 
>>> managed preferences.  I am getting an error that the User Template folder 
>>> is being managed by another class.  I understand why.  I also understand 
>>> the purpose.  This code however only copies files into the Template Folder, 
>>> it doesn't overwrite, or purge the folder.  So, in theory, what I want to 
>>> do should be a valid approach to managing preferences.  
>>>
>>> I have an idea, but don't know how to execute it.  So I hope someone can 
>>> help.
>>>
>>> In the Puppetlabs/Firewall module, you can access it from another 
>>> module.  So if I have an apache module, I can tell the Firewall module I 
>>> want to open port 80.
>>>
>>> I would like to make a Macintosh Managed Preferences module that will 
>>> manage the User Template folder, and in each application module, I can 
>>> provide that module with files.  
>>>
>>> How can I accomplish this?
>>>
>>> Thanks in advance.  
>>>
>>>
>>>  -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "Puppet Users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to puppet-users...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/puppet-users/7fe782a1-fba4-4cef-aeab-4cf85ed170d2%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

[Puppet Users] Re: pluginsync errors on client puppet 3.7

[Tim Dunphy]

Just a brief follow up. I tried disabling pluginsync in the puppet conf.

[root@puppet:/etc/puppet] #grep pluginsync puppet.conf
pluginsync= false

But the error stays the same:

Error: /File[/var/lib/puppet/facts.d]: Failed to generate additional
resources using 'eval_generate': Error 400 on SERVER: Not authorized to
call search on /file_metadata/pluginfacts with {:ignore=>[".svn", "CVS",
".git"], :recurse=>true, :links=>"manage", :checksum_type=>"md5"}
Error: /File[/var/lib/puppet/facts.d]: Could not evaluate: Could not
retrieve file metadata for puppet://puppet.jokefire.com/pluginfacts: Error
400 on SERVER: Not authorized to call find on /file_metadata/pluginfacts
with {:source_permissions=>"use", :links=>"manage"}
Wrapped exception:
Error 400 on SERVER: Not authorized to call find on
/file_metadata/pluginfacts with {:source_permissions=>"use",
:links=>"manage"}

Please help! :)

Thanks
Tim

On Sat, Sep 20, 2014 at 11:08 AM, Tim Dunphy  wrote:

> Hey all,
>
> I'm getting some errors on my client when doing puppet runs that seem
> related to pluginsync:
>
> Error: /File[/var/lib/mydomain/facts.d]: Failed to generate additional
> resources using 'eval_generate': Error 400 on SERVER: Not authorized to
> call search on /file_metadata/pluginfacts with {:ignore=>[".svn", "CVS",
> ".git"], :recurse=>true, :links=>"manage", :checksum_type=>"md5"}
>
> Error: /File[/var/lib/mydomain/facts.d]: Could not evaluate: Could not
> retrieve file metadata for mydomain://mydomain.jokefire.com/pluginfacts:
> Error 400 on SERVER: Not authorized to call find on
> /file_metadata/pluginfacts with {:source_permissions=>"use",
> :links=>"manage"}
>
> Wrapped exception:
>
> Error 400 on SERVER: Not authorized to call find on
> /file_metadata/pluginfacts with {:source_permissions=>"use",
> :links=>"manage"}
>
> Which is odd. Because from what I can tell, puginsync is not being used on
> the server host!
>
> [root@puppet:/etc/puppet] #puppet master --configprint pluginsync
> false
>
> So I'm wondering how I can go about troubleshooting and correcting the
> above error.
>
> Another error that I find confusing is this one on the client:
>
> Warning: Local environment: "production" doesn't match server specified
> environment "none", restarting agent run with environment "none"
>
> Could I get some help with that one too?
>
> Both the client and the server are on puppet 3.7.
>
> Thanks!
> Tim
>
> Warning: Local environment: "production" doesn't match server specified
> environment "none", restarting agent run with environment "none"
>
> --
> GPG me!!
>
> gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B
>
>


-- 
GPG me!!

gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B

-- 
You received this message because you are subscribed 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/CAOZy0ekJkH_FwmOf1OjQ0zvSBumz2WUSSZeDFVQJhetjTO0Ryg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] pluginsync errors on client puppet 3.7

[Tim Dunphy]

Hey all,

I'm getting some errors on my client when doing puppet runs that seem
related to pluginsync:

Error: /File[/var/lib/mydomain/facts.d]: Failed to generate additional
resources using 'eval_generate': Error 400 on SERVER: Not authorized to
call search on /file_metadata/pluginfacts with {:ignore=>[".svn", "CVS",
".git"], :recurse=>true, :links=>"manage", :checksum_type=>"md5"}

Error: /File[/var/lib/mydomain/facts.d]: Could not evaluate: Could not
retrieve file metadata for mydomain://mydomain.jokefire.com/pluginfacts:
Error 400 on SERVER: Not authorized to call find on
/file_metadata/pluginfacts with {:source_permissions=>"use",
:links=>"manage"}

Wrapped exception:

Error 400 on SERVER: Not authorized to call find on
/file_metadata/pluginfacts with {:source_permissions=>"use",
:links=>"manage"}

Which is odd. Because from what I can tell, puginsync is not being used on
the server host!

[root@puppet:/etc/puppet] #puppet master --configprint pluginsync
false

So I'm wondering how I can go about troubleshooting and correcting the
above error.

Another error that I find confusing is this one on the client:

Warning: Local environment: "production" doesn't match server specified
environment "none", restarting agent run with environment "none"

Could I get some help with that one too?

Both the client and the server are on puppet 3.7.

Thanks!
Tim

Warning: Local environment: "production" doesn't match server specified
environment "none", restarting agent run with environment "none"

-- 
GPG me!!

gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B

-- 
You received this message because you are subscribed 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/CAOZy0e%3DHHh-NSjkPwjkE%2BvKRcPRAqKkT_X8EQXbYCPMdY6i5fQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.