date:20131217

[Puppet Users] A different way of managing POSIX ACLs : fooacl

2013-12-17 Thread Matthias Saou

Hi,

I have just published the module I use to manage POSIX ACLs : fooacl

I don't consider it the cleanest possible approach to the problem, but
it's very efficient and flexible. I would actually call it a hack :-)

There's room for improvement, such as splitting out Execs per managed
path to avoid useless re-applying on unchanged paths, or using file
snippets without concat to avoid depending on that module. Pull
requests are more than welcome :-)

I'll publish it to the forge shortly, too.

https://github.com/thias/puppet-fooacl

Short extract of the README :

--
Most (all?) other ACL modules implement a type which can be declared
only once per file, which isn't flexible. This module takes the unusual
approach of creating a single large concatenated script to manage all
ACLs recursively in a single run. Ugly, yet very efficient and flexible
since ACLs aren't tied to the file type in any way.

Features :

* Set ACLs for the same path from different parts of your puppet
manifests (flexible).
* Set global ACL permissions to be applied for all paths managed by
the module (flexible).
* Automatic purging of ACLs on paths as long as at least one ACL is
still being applied by the module (remove users easily and
reliably).
* Automatic setting of both normal and default ACLs to the same values
(shortens declarations, increases code readability).
--

Feedback welcome!

Matthias

--
Matthias Saou ██ ██
██ ██
Web: http://matthias.saou.eu/ ██
Mail/XMPP: matth...@saou.eu ██
██
GPG: 4096R/E755CC63██ ██ ██
8D91 7E2E F048 9C9C 46AF ██ ██ ██ ██
21A9 7A51 7B82 E755 CC63

[Puppet Users] puppet environments not working

2013-12-17 Thread Chantal Rosmuller

Hi, 

On our puppet server the puppet environments do not seem to work. This is 
our puppet.conf:

[main]
logdir=/var/log/puppet
vardir=/var/lib/puppet
ssldir=/var/lib/puppet/ssl
rundir=/var/run/puppet
factpath=$vardir/lib/facter
confdir=/etc/puppet
templatedir=$confdir/templates
modulepath=$confdir/modules
manifest=$confdir/manifests/site.pp
manifestsdir=$confdir/manifests
hiera_config=/etc/puppet/hiera.yaml
pluginsync = true

[master]
certname= puppet3.domain.com 
hostprivkey = /var/lib/puppet/ssl/private_keys/puppet3.domain.com.pem {mode 
= 640}
ssl_client_header = HTTP_X_CLIENT_DN
ssl_client_verify_header = HTTP_X_CLIENT_VERIFY
# ssl_client_header = SSL_CLIENT_S_DN
# ssl_client_verify_header = SSL_CLIENT_VERIFY
reports = store,tagmail
#reports = store,tagmail,puppetdb
storeconfigs = true
storeconfigs_backend = puppetdb

[dev]
modulepath=$confdir/environments/dev/modules
manifest=$confdir/environments/dev/manifests/site.pp

When i try 

puppet agent --environment dev --no-daemonize --verbose --onetime 

The changes in dev are not applied. Can it have anything to do with 
puppetdb?

The servers seems to recognize the puppet environment:

puppet module list --environment 'dev'

returns:

/etc/puppet/environments/dev/modules
├── aliases (???)
├── apt (???)
 etc


versions on the server:

ii  puppet 3.3.1-1puppetlabs1all   
   Centralized configuration management - agent startup and 
compatibility scripts
ii  puppet-common  3.3.1-1puppetlabs1all   
   Centralized configuration management
ii  puppetdb   1.5.0-1puppetlabs1all   
   PuppetDB Centralized Storage.
ii  puppetdb-terminus  1.5.0-1puppetlabs1all   
   Connect Puppet to PuppetDB by setting up a terminus for PuppetDB.
ii  puppetmaster   3.3.1-1puppetlabs1all   
   Centralized configuration management - master startup and 
compatibility scripts
ii  puppetmaster-common3.3.1-1puppetlabs1all   
   Puppet master common scripts




-- 
You received this message because you are subscribed 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/2b3130a5-1641-4f60-9bc7-88b4bfb4fff5%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] puppet environments not working

2013-12-17 Thread John Pyeatt

Not certain if this is the issue or not, but there seems to be a bug in the
master regarding when the configuration file is read to override the
default settings. Try doing this:
1) start up your puppet master
2) after it is up and running try running this from the command line   *touch
/etc/puppet/puppet.conf*   this will force the puppet master to reparse the
configuration settings.

I had a similar problem reading modulepath=.  There is apparently a fix for
this in 3.4


On Tue, Dec 17, 2013 at 7:02 AM, Chantal Rosmuller crosmul...@gmail.comwrote:

 Hi,

 On our puppet server the puppet environments do not seem to work. This is
 our puppet.conf:

 [main]
 logdir=/var/log/puppet
 vardir=/var/lib/puppet
 ssldir=/var/lib/puppet/ssl
 rundir=/var/run/puppet
 factpath=$vardir/lib/facter
 confdir=/etc/puppet
 templatedir=$confdir/templates
 modulepath=$confdir/modules
 manifest=$confdir/manifests/site.pp
 manifestsdir=$confdir/manifests
 hiera_config=/etc/puppet/hiera.yaml
 pluginsync = true

 [master]
 certname= puppet3.domain.com
 hostprivkey = /var/lib/puppet/ssl/private_keys/puppet3.domain.com.pem
 {mode = 640}
 ssl_client_header = HTTP_X_CLIENT_DN
 ssl_client_verify_header = HTTP_X_CLIENT_VERIFY
 # ssl_client_header = SSL_CLIENT_S_DN
 # ssl_client_verify_header = SSL_CLIENT_VERIFY
 reports = store,tagmail
 #reports = store,tagmail,puppetdb
 storeconfigs = true
 storeconfigs_backend = puppetdb

 [dev]
 modulepath=$confdir/environments/dev/modules
 manifest=$confdir/environments/dev/manifests/site.pp

 When i try

 puppet agent --environment dev --no-daemonize --verbose --onetime

 The changes in dev are not applied. Can it have anything to do with
 puppetdb?

 The servers seems to recognize the puppet environment:

 puppet module list --environment 'dev'

 returns:

 /etc/puppet/environments/dev/modules
 ├── aliases (???)
 ├── apt (???)
  etc


 versions on the server:

 ii  puppet 3.3.1-1puppetlabs1all
Centralized configuration management - agent startup and
 compatibility scripts
 ii  puppet-common  3.3.1-1puppetlabs1all
Centralized configuration management
 ii  puppetdb   1.5.0-1puppetlabs1all
PuppetDB Centralized Storage.
 ii  puppetdb-terminus  1.5.0-1puppetlabs1all
Connect Puppet to PuppetDB by setting up a terminus for PuppetDB.
 ii  puppetmaster   3.3.1-1puppetlabs1all
Centralized configuration management - master startup and
 compatibility scripts
 ii  puppetmaster-common3.3.1-1puppetlabs1all
Puppet master common scripts




  --
 You received this message because you are subscribed 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/2b3130a5-1641-4f60-9bc7-88b4bfb4fff5%40googlegroups.com
 .
 For more options, visit https://groups.google.com/groups/opt_out.




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

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

Re: [Puppet Users] puppet environments not working

2013-12-17 Thread Chantal Rosmuller

Thnaks, i tried but it didn't work. We do not start puppetmaster as a 
standalone service so I stopped and started apache. (can that have anything 
to do with the problem ?)

On Tuesday, December 17, 2013 3:08:41 PM UTC+1, John Pyeatt wrote:

 Not certain if this is the issue or not, but there seems to be a bug in 
 the master regarding when the configuration file is read to override the 
 default settings. Try doing this:
 1) start up your puppet master
 2) after it is up and running try running this from the command line   *touch 
 /etc/puppet/puppet.conf*   this will force the puppet master to reparse 
 the configuration settings.

 I had a similar problem reading modulepath=.  There is apparently a fix 
 for this in 3.4


 On Tue, Dec 17, 2013 at 7:02 AM, Chantal Rosmuller 
 crosm...@gmail.comjavascript:
  wrote:

 Hi, 

 On our puppet server the puppet environments do not seem to work. This is 
 our puppet.conf:

 [main]
 logdir=/var/log/puppet
 vardir=/var/lib/puppet
 ssldir=/var/lib/puppet/ssl
  rundir=/var/run/puppet
 factpath=$vardir/lib/facter
 confdir=/etc/puppet
  templatedir=$confdir/templates
 modulepath=$confdir/modules
 manifest=$confdir/manifests/site.pp
  manifestsdir=$confdir/manifests
 hiera_config=/etc/puppet/hiera.yaml
 pluginsync = true

 [master]
 certname= puppet3.domain.com 
 hostprivkey = /var/lib/puppet/ssl/private_keys/puppet3.domain.com.pem 
 {mode = 640}
  ssl_client_header = HTTP_X_CLIENT_DN
 ssl_client_verify_header = HTTP_X_CLIENT_VERIFY
 # ssl_client_header = SSL_CLIENT_S_DN
 # ssl_client_verify_header = SSL_CLIENT_VERIFY
 reports = store,tagmail
 #reports = store,tagmail,puppetdb
  storeconfigs = true
 storeconfigs_backend = puppetdb

 [dev]
 modulepath=$confdir/environments/dev/modules
 manifest=$confdir/environments/dev/manifests/site.pp

 When i try 

 puppet agent --environment dev --no-daemonize --verbose --onetime 

 The changes in dev are not applied. Can it have anything to do with 
 puppetdb?

 The servers seems to recognize the puppet environment:

 puppet module list --environment 'dev'

 returns:

 /etc/puppet/environments/dev/modules
 ├── aliases (???)
 ├── apt (???)
  etc


 versions on the server:

 ii  puppet 3.3.1-1puppetlabs1all 
  Centralized configuration management - agent startup and 
 compatibility scripts
 ii  puppet-common  3.3.1-1puppetlabs1all 
  Centralized configuration management
 ii  puppetdb   1.5.0-1puppetlabs1all 
  PuppetDB Centralized Storage.
 ii  puppetdb-terminus  1.5.0-1puppetlabs1all 
  Connect Puppet to PuppetDB by setting up a terminus for PuppetDB.
 ii  puppetmaster   3.3.1-1puppetlabs1all 
  Centralized configuration management - master startup and 
 compatibility scripts
 ii  puppetmaster-common3.3.1-1puppetlabs1all 
  Puppet master common scripts




  -- 
 You received this message because you are subscribed 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 javascript:.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/puppet-users/2b3130a5-1641-4f60-9bc7-88b4bfb4fff5%40googlegroups.com
 .
 For more options, visit https://groups.google.com/groups/opt_out.




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


-- 
You received this message because you are subscribed 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/cf56d648-a42a-49c2-abab-59678409e802%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: A different way of managing POSIX ACLs : fooacl

2013-12-17 Thread jcbollinger



On Tuesday, December 17, 2013 5:10:20 AM UTC-6, Matthias Saou wrote:

 Hi, 

 I have just published the module I use to manage POSIX ACLs : fooacl 

 I don't consider it the cleanest possible approach to the problem, but 
 it's very efficient and flexible. I would actually call it a hack :-) 



But cool, nonetheless.  It has many of the features I would hope to see in 
such a module.

 

 There's room for improvement, such as splitting out Execs per managed 
 path to avoid useless re-applying on unchanged paths, or using file 
 snippets without concat to avoid depending on that module.



Or a way to detect and reject inconsistent ACL entry declarations.  Or a 
way to leave unmanaged ACL entries alone while managing other entries in 
the same files' ACLs.  Even with a few holes, though, it's still better 
than anything else I'm aware of in that space.  Nice work!


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/6866899a-da3c-4a10-842d-77c2f9541a77%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Geppetto complains about uninitialized variables in reduce function

2013-12-17 Thread Igor Berger

Hello,

I'm using the following expression to format a list:

$valid_environments = ['env1', 'env2', 'env3']
$env_message = $valid_environments.reduce |$message, $env| { 
${message}, ${env} }

It works at run-time (Puppet 3.2.4 standalone with --parser=future).

However in Eclipse (v4.3.1), Geppetto (v4.0) shows these errors:

Reference to not yet initialized variable: env'
Reference to not yet initialized variable: message'

The workspace Puppet target version is set to future.

Is there another syntax I could use to make Geppetto happy or is this a bug?

Thanks,
Igor.

-- 
You received this message because you are subscribed 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/eb6d78c8-0223-496a-8aec-640c546e5559%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] puppet master stopped loading facts since puppetdb installation

2013-12-17 Thread cko

hey,

so i just installed puppetdb on a dedicated server (with pgsql). 

I noticed that the puppet master server doesn't load any facts.

root@puppetmaster:~$ puppet agent -t
 Info: Retrieving plugin
 Info: Caching catalog for puppetmaster.local.domain
 Info: 'replace catalog' command for puppetmaster.local.domain submitted to 
 PuppetDB with UUID 87de0ebc-1543-4b8a-8434-ca9220238fda
 Info: Applying configuration version '1387297065'
 Notice: Finished catalog run in 20.88 seconds


Is this intended? Or did i miss something while installing and connecting 
puppetDB?

-- 
You received this message because you are subscribed 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/18ad2d51-9259-4abb-97a4-5b28bd77eee0%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] MySQL server install with datadir != /var/lib/mysql

2013-12-17 Thread Chris McDermott

I'm a bit late to this thread, but I ran into the same problem with the
puppetlabs-mysql module - it's a bug in how the module was written. There
is a fork by the folks at MediaTemple which addressed that issue:

https://github.com/mediatemple/puppetlabs-mysql

I've been using that successfully for several months now to do exactly what
you propose - specify an alternate location for the datadir and have the
module install/configure/start mysqld with no intervention required.

Chris

On Wed, Dec 4, 2013 at 6:27 PM, Justin tcpan...@gmail.com wrote:

Have you tried creating a symlink (eg. /var/lib/mysql - /mysql/data)
before installing with yum?
On Dec 3, 2013 8:40 PM, Thomas thomas.e.ke...@gmail.com wrote:

Has anybody sucessfully used puppetlabs-mysql (or some other method) to
install MySQL-server on Linux with a my.cnf where datadir != /var/lib/mysql
?

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

[Puppet Users] Re: recursive descent

2013-12-17 Thread Stuart Cracraft

That is very, very disturbing.

On Wednesday, December 11, 2013 2:25:04 PM UTC-8, Stuart Cracraft wrote:


 I want to recursively descend infinitely through a directory tree in 
 regards to ensuring:

   (a) owner, group, permission
   (b) existence of the full path, all the leaves, out to the final leaf, 
 e.g.
/somedir/somesubdir/{file1,file2,file3,somesubdirtoo} and so forth

 This could be done trivially with an exec but is not 
 pure-Puppet-ecosystem, obviously.

 So my questions are, from a Puppet-puritan-perspective:

   is there a way to do (a)
   is there a way to do (b)
   is there a way to do (a)+(b)

 and last:

   is there a way to do (a)+(b) in a reasonable period of time for a 
 shallow tree of few leaves

 Yours in squirrelhood,

 Stuart




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

Re: [Puppet Users] puppet environments not working

2013-12-17 Thread Jeff Bachtel

There is a problem with variable hooks in puppet.conf that is fixed in 
the latest 3.4 release candidates (or so sayeth the bugreps).


Can you try explicitly specifying your directories instead of using 
$confdir in that puppet.conf, at least to test?


Jeff

On 12/17/2013 09:18 AM, Chantal Rosmuller wrote:
Thnaks, i tried but it didn't work. We do not start puppetmaster as a 
standalone service so I stopped and started apache. (can that have 
anything to do with the problem ?)


On Tuesday, December 17, 2013 3:08:41 PM UTC+1, John Pyeatt wrote:

Not certain if this is the issue or not, but there seems to be a
bug in the master regarding when the configuration file is read to
override the default settings. Try doing this:
1) start up your puppet master
2) after it is up and running try running this from the command
line *touch /etc/puppet/puppet.conf* this will force the puppet
master to reparse the configuration settings.

I had a similar problem reading modulepath=.  There is apparently
a fix for this in 3.4


On Tue, Dec 17, 2013 at 7:02 AM, Chantal Rosmuller
crosm...@gmail.com javascript: wrote:

Hi,

On our puppet server the puppet environments do not seem to
work. This is our puppet.conf:

[main]
logdir=/var/log/puppet
vardir=/var/lib/puppet
ssldir=/var/lib/puppet/ssl
rundir=/var/run/puppet
factpath=$vardir/lib/facter
confdir=/etc/puppet
templatedir=$confdir/templates
modulepath=$confdir/modules
manifest=$confdir/manifests/site.pp
manifestsdir=$confdir/manifests
hiera_config=/etc/puppet/hiera.yaml
pluginsync = true

[master]
certname= puppet3.domain.com http://puppet3.domain.com
hostprivkey =
/var/lib/puppet/ssl/private_keys/puppet3.domain.com.pem {mode
= 640}
ssl_client_header = HTTP_X_CLIENT_DN
ssl_client_verify_header = HTTP_X_CLIENT_VERIFY
#ssl_client_header = SSL_CLIENT_S_DN
#ssl_client_verify_header = SSL_CLIENT_VERIFY
reports = store,tagmail
#reports = store,tagmail,puppetdb
storeconfigs = true
storeconfigs_backend = puppetdb

[dev]
modulepath=$confdir/environments/dev/modules
manifest=$confdir/environments/dev/manifests/site.pp

When i try

puppet agent --environment dev --no-daemonize --verbose --onetime

The changes in dev are not applied. Can it have anything to do
with puppetdb?

The servers seems to recognize the puppet environment:

puppet module list --environment 'dev'

returns:

/etc/puppet/environments/dev/modules
├── aliases (???)
├── apt (???)
 etc


versions on the server:

ii  puppet 3.3.1-1puppetlabs1all  Centralized
configuration management - agent startup and compatibility scripts
ii  puppet-common  3.3.1-1puppetlabs1all
 Centralized configuration management
ii  puppetdb 1.5.0-1puppetlabs1all  PuppetDB
Centralized Storage.
ii  puppetdb-terminus  1.5.0-1puppetlabs1all
 Connect Puppet to PuppetDB by setting up a terminus for PuppetDB.
ii  puppetmaster 3.3.1-1puppetlabs1all
 Centralized configuration management - master startup and
compatibility scripts
ii  puppetmaster-common  3.3.1-1puppetlabs1all
 Puppet master common scripts





-- 
You received this message because you are subscribed 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
javascript:.
To view this discussion on the web visit

https://groups.google.com/d/msgid/puppet-users/2b3130a5-1641-4f60-9bc7-88b4bfb4fff5%40googlegroups.com

https://groups.google.com/d/msgid/puppet-users/2b3130a5-1641-4f60-9bc7-88b4bfb4fff5%40googlegroups.com.
For more options, visit
https://groups.google.com/groups/opt_out
https://groups.google.com/groups/opt_out.




-- 
John Pyeatt

Singlewire Software, LLC
www.singlewire.com http://www.singlewire.com/
--
608.661.1184
john@singlewire.com javascript:

--
You received this message because you are subscribed 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/cf56d648-a42a-49c2-abab-59678409e802%40googlegroups.com.

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


--
You received this message because you are subscribed to the Google Groups Puppet 
Users

Re: [Puppet Users] Re: recursive descent

2013-12-17 Thread ygor

Have you tried experimenting ?br /Much of my Puppet savvy is from tinkering. 
br /br /Try some code. See what works and what does not work. br /br 
/Sometimes I think the surest sign that intelligent life exists elsewhere in 
the universe is that none of it has tried to contact us.br /Bill Waterson 
(Calvin  Hobbes)

-- 
You received this message because you are subscribed 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/594141407.88154.1387317298820.JavaMail.root%40sz0126a.westchester.pa.mail.comcast.net.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Re: recursive descent

2013-12-17 Thread Stuart Cracraft

I don't have time to play hunt-the-wumpus.

On Dec 17, 2013, at 1:54 PM, y...@comcast.net wrote:

Have you tried experimenting ?
Much of my Puppet savvy is from tinkering.

Try some code. See what works and what does not work.

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)

- Original Message -
From: smcracr...@gmail.com
To: puppet-users@googlegroups.com
Sent:Tue Dec 17 09:17:55 UTC 2013
Subject: [Puppet Users] Re: recursive descent

That is very, very disturbing.

On Wednesday, December 11, 2013 2:25:04 PM UTC-8, Stuart Cracraft wrote:

I want to recursively descend infinitely through a directory tree in regards
to ensuring:

(a) owner, group, permission
(b) existence of the full path, all the leaves, out to the final leaf, e.g.
/somedir/somesubdir/{file1,file2,file3,somesubdirtoo} and so forth

This could be done trivially with an exec but is not pure-Puppet-ecosystem,
obviously.

So my questions are, from a Puppet-puritan-perspective:

is there a way to do (a)
is there a way to do (b)
is there a way to do (a)+(b)

and last:

is there a way to do (a)+(b) in a reasonable period of time for a shallow
tree of few leaves

Yours in squirrelhood,

Stuart

--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an
email to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/d24784e1-769c-4666-b077-a8856c898ff1%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to a topic in the Google
Groups Puppet Users group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/puppet-users/Hf6ReeSy2mE/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/594141407.88154.1387317298820.JavaMail.root%40sz0126a.westchester.pa.mail.comcast.net.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Re: yamlyzer

2013-12-17 Thread Jeff Bachtel

Have you tried a yaml to csv converter like
https://github.com/tokland/yaml2csv ? Note that it seems to require the
csv module syntax from ruby 1.9.3.

Jeff

On 12/16/2013 03:29 PM, Stuart Cracraft wrote:
Is the back-end piece of Puppet Dashboard which implements the
CSV-capability

of the YAML interpretation available as a standalone?

On Thursday, December 12, 2013 3:20:41 PM UTC-8, Stuart Cracraft wrote:

Hi everybody,

Is there a command-line program which parses:

puppetmasters*:/var/lib/puppet/reports/*/*.yaml

into simple a simple (though lengthy) report perhaps with
column/field/etc. selection based on a straightforward method.

Holler if you know of any. I know this was queried by me
on this list recently and all sorts of stuff was posted. If
I don't get it here, I'll need to go over to puppet-developers
and ask there.

Surely, someone has written something they're proud of and
will share it forward.

Stuart

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

Re: [Puppet Users] recursive descent

2013-12-17 Thread Andy Spiegl

  http://christian.hofstaedtler.name/blog/2008/11/puppet-managing-directories-recursively.html

I thought I had understood recursive directory management.  It worked
fine until I switched to puppet v3 (Debian 3.3.2-1puppetla to be exact)
Since then, files in subdirs aren't copied anymore.

An example:
  File {
owner = nagios,
group = nagios,
mode  = '0644',
  }
  file { '/var/lib/nagios':
ensure= directory,
source= 'puppet:///modules/nagios/var_lib_nagios',
recurse   = true,
  }
  file { '/var/lib/nagios/plugins':
ensure= directory,
recurse   = true,
mode  = '0775',
  }
  file { '/var/lib/nagios/bin':
ensure= directory,
recurse   = true,
mode  = '0775',
  }

 lama:~/.../puppet/modules/nagios ls -la files/var_lib_nagios
 total 8
 drwxrwxr-x 2 andy users 4096 2013-11-15 15:56:23 bin/
 drwxrwxr-x 2 andy users 4096 2013-11-25 12:01:14 plugins/

Why aren't these directories copied to /var/lib/nagios?
I tried setting recurselimit to '2' but that didn't help either.

Thanks for any hint!
 Andy.


-- 
 A mathematician is a machine for converting coffee into theorems.  (Alfred 
Renyi)

-- 
You received this message because you are subscribed 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/20131217191221.GA31279%40spiegl.de.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Re: yamlyzer

2013-12-17 Thread Stuart Cracraft

This is very interesting Jeff.

I will play with it.

Thanks!

On Dec 17, 2013, at 2:04 PM, Jeff Bachtel jbach...@bericotechnologies.com
wrote:

Have you tried a yaml to csv converter like
https://github.com/tokland/yaml2csv ? Note that it seems to require the csv
module syntax from ruby 1.9.3.

Jeff

On 12/16/2013 03:29 PM, Stuart Cracraft wrote:
Is the back-end piece of Puppet Dashboard which implements the CSV-capability
of the YAML interpretation available as a standalone?

On Thursday, December 12, 2013 3:20:41 PM UTC-8, Stuart Cracraft wrote:

Hi everybody,

Is there a command-line program which parses:

puppetmasters*:/var/lib/puppet/reports/*/*.yaml

into simple a simple (though lengthy) report perhaps with
column/field/etc. selection based on a straightforward method.

Holler if you know of any. I know this was queried by me
on this list recently and all sorts of stuff was posted. If
I don't get it here, I'll need to go over to puppet-developers
and ask there.

Surely, someone has written something they're proud of and
will share it forward.

Stuart
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an
email to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/d333f68c-ad66-40bb-b969-9248114cd766%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to a topic in the Google
Groups Puppet Users group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/puppet-users/GxeE-URziu8/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/52B0CA5A.2010505%40bericotechnologies.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] new puppet book revision

2013-12-17 Thread Stuart Cracraft

It looks like Amazon/publishers/authors/etc. have revised the new puppet 
book date:

http://www.amazon.com/Pro-Puppet-Spencer-Krum/dp/1430260408/ref=sr_1_3?ie=UTF8qid=1387318030sr=8-3keywords=puppet+3

Fun!

-- 
You received this message because you are subscribed 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/875905a6-03ea-4da3-83fe-eda66f34384a%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

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

2013-12-17 Thread Matthaus Owens

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

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

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

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

 A good tip.

 Thank-you.

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

 No Ruby Mysql bindings aka the mysql gem.

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

 Ramin

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

 And the installed gems and ruby version.

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

 *** LOCAL GEMS ***

 actionmailer (3.2.13)

 actionpack (3.2.13)

 activemodel (3.2.13)

 activerecord (3.2.13)

 activeresource (3.2.13)

 activesupport (3.2.13)

 archive-tar-minitar (0.5.2)

 arel (3.0.2)

 builder (3.0.4)

 bundler (1.3.5)

 cgi_multipart_eof_fix (2.5.0)

 columnize (0.3.6)

 daemons (1.1.9)

 erubis (2.7.0)

 fastthread (1.0.7)

 gem_plugin (0.2.3)

 hike (1.2.2)

 i18n (0.6.1)

 journey (1.0.4)

 json (1.8.0)

 mail (2.5.4)

 mime-types (1.23)

 mongrel (1.1.5)

 multi_json (1.7.4)

 polyglot (0.3.3)

 rack (1.4.5)

 rack-cache (1.2)

 rack-ssl (1.3.3)

 rack-test (0.6.2)

 rails (3.2.13)

 railties (3.2.13)

 rake (10.0.4)

 rdoc (3.12.2)

 rgen (0.6.2)

 ruby-json (1.1.2)

 ruby-shadow (2.2.0)

 ruby_core_source (0.1.5)

 rubygems-update (2.0.3)

 shadow (1.1)

 sprockets (2.2.2)

 thor (0.18.1)

 tilt (1.4.1)

 treetop (1.4.12)

 tzinfo (0.3.37)

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

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

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



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

I followed:

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

and have reached the point after

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

at

   Preparing Schema

and now receive the error:

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

   See full trace by running task with --trace

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

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

Thanks so much!

 --
 You received this message because you are subscribed to the Google
 Groups Puppet Users group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to puppet-users+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/puppet-users/ee0f339d-79f4-4622-bd51-3a2872d5aa48%40googlegroups.com.
 For more options, visit https://groups.google.com/groups/opt_out.


 --
 You received this message because you are subscribed to a topic in the
 Google Groups Puppet Users group.
 To unsubscribe from this topic, visit
 https://groups.google.com/d/topic/puppet-users/jXit5cwjA9g/unsubscribe.
 To unsubscribe from this group and all its topics, send an email to
 puppet-users+unsubscr...@googlegroups.com.

 To view this discussion on the web visit
 https://groups.google.com/d/msgid/puppet-users/52AF7562.4050209%40badapple.net.
 For more options, visit https://groups.google.com/groups/opt_out.


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

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



-- 
Matthaus Owens
Release Manager, Puppet Labs

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

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

Re: [Puppet Users] puppet master stopped loading facts since puppetdb installation

2013-12-17 Thread Deepak Giridharagopal

On Dec 17, 2013, at 9:56 AM, cko dert...@gmail.com wrote:

hey,

so i just installed puppetdb on a dedicated server (with pgsql).

I noticed that the puppet master server doesn't load any facts.

What do you mean doesn't load any facts? What is the problem you're seeing?

root@puppetmaster:~$ puppet agent -t
Info: Retrieving plugin
Info: Caching catalog for puppetmaster.local.domain
Info: 'replace catalog' command for puppetmaster.local.domain submitted to
PuppetDB with UUID 87de0ebc-1543-4b8a-8434-ca9220238fda
Info: Applying configuration version '1387297065'
Notice: Finished catalog run in 20.88 seconds

Is this intended? Or did i miss something while installing and connecting
puppetDB?

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

2013-12-17 Thread Stuart Cracraft

 

All to nought. No change alas.

 

Confirmation of version:

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

  rubygems-update (1.8.25)

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

 

Retry of Schematization:

 

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

  rake RAILS_ENV=production db:migrate

  rake aborted!

  undefined method `source_index' for Gem:Module

 

  (See full trace by running task with --trace)

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

 

The following would not be expected to work without the Schematization 
prerequisite above:

 

[root@ca-sna-pm01 puppet-dashboard]# sudo -u puppet-dashboard 
./script/server -e production

./script/../config/../vendor/rails/railties/lib/rails/gem_dependency.rb:21:in 
`add_frozen_gem_path': undefined method `source_index\

' for Gem:Module (NoMethodError)

from ./script/../config/boot.rb:50:in `load_initializer'

from ./script/../config/boot.rb:41:in `run'

from ./script/../config/boot.rb:14:in `boot!'

from ./script/../config/boot.rb:113

from ./script/server:2:in `require'

from ./script/server:2

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

Stuart

On Tuesday, December 17, 2013 2:36:04 PM UTC-8, Matthaus Litteken wrote:

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


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

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

 On Mon, Dec 16, 2013 at 10:36 PM, Stuart Cracraft 
 smcra...@me.comjavascript: 
 wrote: 
  Thanks Ramin. 
  
  A good tip. 
  
  Thank-you. 
  
  On Dec 16, 2013, at 1:49 PM, Ramin K ramin...@badapple.netjavascript: 
 wrote: 
  
  No Ruby Mysql bindings aka the mysql gem. 
  
  
 http://docs.puppetlabs.com/dashboard/manual/1.2/bootstrapping.html#installing-dependencies
  
  
  Ramin 
  
  On 12/16/2013 12:37 PM, Stuart Cracraft wrote: 
  
  And the installed gems and ruby version. 
  
  [root@ca-sna-pm01 puppet-dashboard]# gem list 
  
  *** LOCAL GEMS *** 
  
  actionmailer (3.2.13) 
  
  actionpack (3.2.13) 
  
  activemodel (3.2.13) 
  
  activerecord (3.2.13) 
  
  activeresource (3.2.13) 
  
  activesupport (3.2.13) 
  
  archive-tar-minitar (0.5.2) 
  
  arel (3.0.2) 
  
  builder (3.0.4) 
  
  bundler (1.3.5) 
  
  cgi_multipart_eof_fix (2.5.0) 
  
  columnize (0.3.6) 
  
  daemons (1.1.9) 
  
  erubis (2.7.0) 
  
  fastthread (1.0.7) 
  
  gem_plugin (0.2.3) 
  
  hike (1.2.2) 
  
  i18n (0.6.1) 
  
  journey (1.0.4) 
  
  json (1.8.0) 
  
  mail (2.5.4) 
  
  mime-types (1.23) 
  
  mongrel (1.1.5) 
  
  multi_json (1.7.4) 
  
  polyglot (0.3.3) 
  
  rack (1.4.5) 
  
  rack-cache (1.2) 
  
  rack-ssl (1.3.3) 
  
  rack-test (0.6.2) 
  
  rails (3.2.13) 
  
  railties (3.2.13) 
  
  rake (10.0.4) 
  
  rdoc (3.12.2) 
  
  rgen (0.6.2) 
  
  ruby-json (1.1.2) 
  
  ruby-shadow (2.2.0) 
  
  ruby_core_source (0.1.5) 
  
  rubygems-update (2.0.3) 
  
  shadow (1.1) 
  
  sprockets (2.2.2) 
  
  thor (0.18.1) 
  
  tilt (1.4.1) 
  
  treetop (1.4.12) 
  
  tzinfo (0.3.37) 
  
  [root@ca-sna-pm01 puppet-dashboard]# ruby --version 
  
  ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux] 
  
  [root@ca-sna-pm01 puppet-dashboard]# 
  
  
  
  On Monday, December 16, 2013 11:46:04 AM UTC-8, Stuart Cracraft wrote: 
  
 I followed: 
  
 http://docs.puppetlabs.com/dashboard/manual/1.2/bootstrapping.html 
 http://docs.puppetlabs.com/dashboard/manual/1.2/bootstrapping.html 
  
 and have reached the point after 
  
puppet dashboard install/configuration 
MySQL server and MySQL client installation/configuration/startup 
  
 at 
  
Preparing Schema 
  
 and now receive the error: 
  
rake RAILS_ENV=production db_migrate 
rake aborted! 
undefined method `source_index' for Gem:Module 
  
See full trace by running task with --trace 
  
 the above was run while connected to /usr/share/puppet-dashboard 
 where there is a project Rakefile which the above uses. 
  
 Any thoughts on the above and how to get past it? 
  
 Thanks so much! 
  
  -- 
  You received this message because you are subscribed to the Google 
  Groups Puppet Users group. 
  To unsubscribe from this group and stop receiving emails from it, send 
  an email to puppet-users...@googlegroups.com javascript:. 
  To view this discussion on the web visit 
  
 https://groups.google.com/d/msgid/puppet-users/ee0f339d-79f4-4622-bd51-3a2872d5aa48%40googlegroups.com.
  

  For more options, visit https://groups.google.com/groups/opt_out. 
  
  
  -- 
  You received this message because you are subscribed to a topic in the 
  Google Groups Puppet Users group. 
  To unsubscribe from this topic, visit 
  https://groups.google.com/d/topic/puppet-users/jXit5cwjA9g/unsubscribe. 
  To unsubscribe from this group and all its topics, send an email to

Re: [Puppet Users] Re: yamlyzer

2013-12-17 Thread Stuart Cracraft

Alas, it was all for naught.

Anyone know about the uninitialized constant Yaml2csv error?

[root@ca-sna-pm01 bin]# /usr/local/bin/yaml2csv.rb foobar.yml

./yaml2csv.rb:43: uninitialized constant Yaml2csv (NameError)

from
/usr/lib/ruby/site_ruby/1.8/rubygems/core_ext/kernel_require.rb:45:in
`gem_original_require'

from
/usr/lib/ruby/site_ruby/1.8/rubygems/core_ext/kernel_require.rb:45:in
`require'

from /usr/local/bin/yaml2csv.rb:7

[root@ca-sna-pm01 bin]#

Stuart

On Tuesday, December 17, 2013 2:20:47 PM UTC-8, Stuart Cracraft wrote:

This is very interesting Jeff.

I will play with it.

Thanks!

On Dec 17, 2013, at 2:04 PM, Jeff Bachtel jbach...@bericotechnologies.com
wrote:

Have you tried a yaml to csv converter like
https://github.com/tokland/yaml2csv ? Note that it seems to require the
csv module syntax from ruby 1.9.3.

Jeff

On 12/16/2013 03:29 PM, Stuart Cracraft wrote:

Is the back-end piece of Puppet Dashboard which implements the
CSV-capability
of the YAML interpretation available as a standalone?

On Thursday, December 12, 2013 3:20:41 PM UTC-8, Stuart Cracraft wrote:

Hi everybody,

Is there a command-line program which parses:

puppetmasters*:/var/lib/puppet/reports/*/*.yaml

into simple a simple (though lengthy) report perhaps with
column/field/etc. selection based on a straightforward method.

Holler if you know of any. I know this was queried by me
on this list recently and all sorts of stuff was posted. If
I don't get it here, I'll need to go over to puppet-developers
and ask there.

Surely, someone has written something they're proud of and
will share it forward.

Stuart

--
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/GxeE-URziu8/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/52B0CA5A.2010505%40bericotechnologies.com
.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Process hung on FreeBSD

2013-12-17 Thread Patrick Gibson

This is my first attempt with Puppet, and I'm working on FreeBSD 9.2 with
Puppet 3.3.1 and Ruby 2.0. I'm starting with just a very simple example to
get my feet wet:

node 'myhost' {
package { 'devel/jsmin':
ensure = 'installed',
provider = 'ports'
}
}

When I apply this with:

puppet apply -v --debug manifests/site.pp

I get a bunch of output about selinux and other Linuxisms (making think
that I should be specifying that 'myhost' is FreeBSD?), and finally it
starts to install the port I want:

Debug: Prefetching ports resources for package
Debug: Executing '/usr/sbin/pkg_info -aoQ'
Debug: Executing '/usr/sbin/pkg_info -aoQ'
Debug: Executing '/usr/local/sbin/portupgrade -N -M BATCH=yes devel/jsmin'

It seems like it's working, but it actually just stalls here. Running that
last command by hand finishes in a few seconds, and the BATCH=yes option in
there ensures that user input is never needed. I'm kind of stuck at this
point, as beyond adding -v and --debug, I don't know how to further
diagnose things. I can see that the process is running in my `ps` output,
but I can't think of why it would be stalled.

Any thoughts would be appreciated. Am I crazy for using Puppet on FreeBSD?
It seems like very few other people must be based on my Google searches and
available documentation.

Thanks,

Patrick

[Puppet Users] very odd Duplicate declaration problem.

2013-12-17 Thread Nathan Earixson

puppet 3.3.2 on RHEL6

If I run puppet on a node:
# sudo puppet agent --test --noop

I get the following error:

*Error: Could not retrieve catalog from remote server: Error 400 on SERVER:
Duplicate declaration: Package[bind] is already declared in file
/etc/puppet/modules/site/manifests/dns_test.pp:4; cannot redeclare at
/etc/puppet/modules/site/manifests/dns.pp:4 on node
bushlnxadm01.chicagobooth.eduWarning: Not using cache on failed
catalogError: Could not retrieve catalog; skipping run*

That's weird. That node isn't a DNS server and shouldn't even be thinking
about running bind.

If I open /etc/puppet/manifests/site.pp and save the file, the error goes
away on next puppet agent run.

After about 15 minutes the node starts trying to apply the classes from
*/etc/puppet/modules/site/manifests/dns_test.pp
*and after another 5 or so minutes I start getting the duplicate
declaration error again.

If I save the manifest the puppet agent command works as expected for
another 15 minutes or so.

I can't even begin to think of where to start looking on this. Any thoughts
would be appreciated.
This seems to be happening on every node.

-n

[Puppet Users] Process hang on FreeBSD

2013-12-17 Thread Patrick Gibson

I'm a first-time Puppet user, working with FreeBSD 9.2, Puppet 3.3.1, and
Ruby 2.0. I'm starting out with a very simple setup to test the waters:

node 'myhost' {
package { 'devel/jsmin':
ensure = 'installed',
provider = 'ports'
}
}

When I run:

puppet apply -v --debug manifests/site.pp

I get a bunch of output with various Linuxisms like selinux, rpm, apt-get,
dpkg, etc (making me think I need to specify that this is a FreeBSD host?),
and then:

It all looks good, except that the process seems to stall out here. Running
'/usr/local/sbin/portupgrade -N -M BATCH=yes devel/jsmin' manually works
fine and completes in a few seconds. I can see from the `ps` listing that
command is active, but it just sits there, not completing.

I'm not sure how to debug this any further. Is it considered a bad idea to
run Puppet on a FreeBSD host? Based on my Google searches and amount of
discussion around it, it seems like there are very few people who are doing
this.

Any insight would be greatly appreciated.

Thanks,

Patrick

Re: [Puppet Users] recursive descent

2013-12-17 Thread Ben Ford

If you override something in a recursive directory, you're overriding
everything. The subdirectories are being managed explicitly by the resource
managing them, not by a combination of it and the parent. Look inline below:

On Tuesday, December 17, 2013 11:12:21 AM UTC-8, Andy Spiegl wrote:

http://christian.hofstaedtler.name/blog/2008/11/puppet-managing-directories-recursively.html

I thought I had understood recursive directory management. It worked
fine until I switched to puppet v3 (Debian 3.3.2-1puppetla to be exact)
Since then, files in subdirs aren't copied anymore.

An example:
File {
owner = nagios,
group = nagios,
mode = '0644',
}
file { '/var/lib/nagios':
ensure= directory,
source= 'puppet:///modules/nagios/var_lib_nagios',
recurse = true,
}

Manages /var/lib/nagios with recurse true.

file { '/var/lib/nagios/plugins':
ensure= directory,
recurse = true,
mode = '0775',
}

Completely takes precedence over File['/var/lib/nagios'] and manages
'/var/lib/nagios/plugins' telling Puppet that all you care about is that
it's a directory with mode 775. Notice that you no longer have a source for
this subdirectory, so it's explicitly not managed.

If you add source = 'puppet:///modules/nagios/var_lib_nagios/plugins' then
I suspect you'll get what you want.

file { '/var/lib/nagios/bin':
ensure= directory,
recurse = true,
mode = '0775',
}

lama:~/.../puppet/modules/nagios ls -la files/var_lib_nagios
total 8
drwxrwxr-x 2 andy users 4096 2013-11-15 15:56:23 bin/
drwxrwxr-x 2 andy users 4096 2013-11-25 12:01:14 plugins/

Why aren't these directories copied to /var/lib/nagios?
I tried setting recurselimit to '2' but that didn't help either.

Thanks for any hint!
Andy.

--
A mathematician is a machine for converting coffee into theorems.
(Alfred Renyi)

Re: [Puppet Users] recursive descent

2013-12-17 Thread Ben Ford




   file { '/var/lib/nagios/plugins': 
 ensure= directory, 
 recurse   = true, 
 mode  = '0775', 
   } 


I should also point out that this is unnecessary, as Puppet will 
automatically promote read permissions to read  execute permissions for 
directories. If you simply remove the second file declarations from your 
code, you'll have the behavior that I think you're expecting.

http://docs.puppetlabs.com/references/latest/type.html#file-attribute-mode

-- 
You received this message because you are subscribed 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/f4d039a2-d13e-4a98-b9d2-80e9ebea0785%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Process hang on FreeBSD

2013-12-17 Thread Jeff Bachtel

First, to clarify - do you have pkgng installed on your FreeBSD box?
That is, should you be using /usr/sbin/pkg instead of
/usr/local/bin/pkg_info if you are doing local package management?

If so, the current freebsd provider is not likely to work well for you,
as it's pretty tied into the old framework. There's a new pkgng provider
for freebsd+puppet available at https://github.com/xaque208/puppet-pkgng
that might be worth trying.

Second, to debug you can try changing
/usr/lib/ruby/site_ruby/1.8/puppet/provider/package/ports.rb (or
equivalent, on FreeBSD that could all be under
/usr/local/lib/ruby/site_ruby/2.0/puppet/provider/package/ports.rb or
elsewhere) line 19 from

cmd = %w{-N -M BATCH=yes} @resource[:name]
to
cmd = %w{-v -N -M BATCH=yes} @resource[:name]

to turn on portupgrade's verbosity.

Third, no running Puppet on FreeBSD is not a bad idea. Lots of people
work pretty hard to make it work, but it unfortunately doesn't get the
exposure and attention that Linux does, and thus stuff might not be as
well tested.

Jeff

On 12/17/2013 07:31 PM, Patrick Gibson wrote:
I'm a first-time Puppet user, working with FreeBSD 9.2, Puppet 3.3.1,
and Ruby 2.0. I'm starting out with a very simple setup to test the
waters:

node 'myhost' {
package { 'devel/jsmin':
ensure = 'installed',
provider = 'ports'
}
}

When I run:

puppet apply -v --debug manifests/site.pp

I get a bunch of output with various Linuxisms like selinux, rpm,
apt-get, dpkg, etc (making me think I need to specify that this is a
FreeBSD host?), and then:

It all looks good, except that the process seems to stall out here.
Running '/usr/local/sbin/portupgrade -N -M BATCH=yes devel/jsmin'
manually works fine and completes in a few seconds. I can see from the
`ps` listing that command is active, but it just sits there, not
completing.

I'm not sure how to debug this any further. Is it considered a bad
idea to run Puppet on a FreeBSD host? Based on my Google searches and
amount of discussion around it, it seems like there are very few
people who are doing this.

Any insight would be greatly appreciated.

Thanks,

Patrick
--
You received this message because you are subscribed 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/5f2d0086-69b5-4a5e-8d36-419e294f1695%40googlegroups.com.

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

Re: [Puppet Users] Process hang on FreeBSD

2013-12-17 Thread Russell A. Jackson

On 12/17/2013 04:31 PM, Patrick Gibson wrote:
 Debug: Executing '/usr/local/sbin/portupgrade -N -M BATCH=yes devel/jsmin'

In short, out-of-the-box, puppet is broken on FreeBSD in regards to package
handling.

Portupgrade doesn't like being run with stdin not being a terminal. You'll
probably find you have a `script` process taking 100% cpu when you see it hang.
This problem has been around for a long time and still hasn't been fixed as far
as I know.

The default (freebsd) pkg_add binary package provider is also broken mainly
because the of heuristics that pkg_add -r use. You'll find this to a problem
when the symlink name under /Latest doesn't match the name that the package
records in the pkgdb. This leads to puppet trying to install the package on
every run.

If you install puppet from ports, it applies a patch to address this problem but
requires using the ports origin (like with the ports provider) as the package
name. Instead of using pkg_add -r, it downloads the ports index and looks up the
package name for a given ports origin and then supplies the specific url of the
full package name as a argument to pkg_add.

I have an updated version of this provider that fixes a number of issues as well
as supporting ensure = latest.

https://bitbucket.org/csub/puppet-module-freebsd

Be aware, having this module in your module path will mask the default freebsd
provider distributed with puppet.

There are also third party puppet modules that implement a provider for pkgng
that work well. If you can migrate to pkgng, I would strongly suggest doing so.

-- 
Russell A. Jackson r...@csub.edu
Network/Datacenter Operations
California State University, Bakersfield



signature.asc
Description: OpenPGP digital signature

Re: [Puppet Users] very odd Duplicate declaration problem.

2013-12-17 Thread Jeff Bachtel

Do you have use_cached_catalog set on puppet agents or puppetmaster? Are
you using storeconfigs / puppetdb?

Offhand, I'd guess that when you modify mtime of site.pp by saving, that
forces puppet to invalidate the cached catalog and temporarily resolve
the problem.

If necessary, are you able to update to the latest 3.4rc (agent might
suffice) for testing?

Jeff

On 12/17/2013 03:35 PM, Nathan Earixson wrote:

puppet 3.3.2 on RHEL6

If I run puppet on a node:
# sudo puppet agent --test --noop

I get the following error:

/Error: Could not retrieve catalog from remote server: Error 400 on
SERVER: Duplicate declaration: Package[bind] is already declared in
file /etc/puppet/modules/site/manifests/dns_test.pp:4; cannot
redeclare at /etc/puppet/modules/site/manifests/dns.pp:4 on node
bushlnxadm01.chicagobooth.edu

Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run/

That's weird. That node isn't a DNS server and shouldn't even be
thinking about running bind.

If I open /etc/puppet/manifests/site.pp and save the file, the error
goes away on next puppet agent run.

After about 15 minutes the node starts trying to apply the classes
from //etc/puppet/modules/site/manifests/dns_test.pp /and after
another 5 or so minutes I start getting the duplicate declaration
error again.

If I save the manifest the puppet agent command works as expected for
another 15 minutes or so.

I can't even begin to think of where to start looking on this. Any
thoughts would be appreciated.

This seems to be happening on every node.

-n

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

[Puppet Users] Announce: Facter 1.7.4 Available

2013-12-17 Thread Melissa Stone

Facter 1.7.4
---

   - Final: Released December 17, 2013
   - RC1: December 9, 2013


Facter 1.7.4 Downloads
--
Source: https://downloads.puppetlabs.com/facter/facter-1.7.4.tar.gz

Available in native package format in the pre-release repositories at:
http://yum.puppetlabs.com and http://apt.puppetlabs.com

For information on how to enable the Puppet Labs repos, see:
http://docs.puppetlabs.com/guides/puppetlabs_package_repositories.html#open-source-repositories

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

Mac packages are available at
https://downloads.puppetlabs.com/mac/facter-1.7.4.dmg

Please report feedback via the Puppet Labs tickets site, using an
affected facter version of 1.7.4:
https://tickets.puppetlabs.com/browse/FACT



Facter 1.7.4 release notes
---
*External Fact Fixes*

This release fixes several issues related to external facts:

Bug #22944: External facts are evaluated many
timeshttps://projects.puppetlabs.com/issues/22944

Facter was evaluating each external fact several times per run, which could
cause significant slowdowns. This is now fixed, and Facter will load each
external fact once.

Bug #22349: Facter fails to run as a non-root user when /etc/facter/facts.d
is not readable https://projects.puppetlabs.com/issues/22349

When running as a non-root user, Facter will now load external facts from a
.facter/facts.d/ directory in the current user’s home directory. This works
on both Windows and *nix. (Prior to this fix, Facter would try to load
external facts from the system-wide external facts directory, and would
bail with an error if that directory wasn’t readable.)

Bug #22622: Facter (and Puppet) broken when executable external facts
return no output https://projects.puppetlabs.com/issues/22622

Facter was making a bad assumption that the output of an executable
external fact would always consist of at least one line of text. What this
fix presupposes is… maybe it doesn’t??

Maint: Do not execute com, cmd, exe, or bat files if not on windows

In preparation for pluginsync support for external facts, Facter needed a
bit of defense for situations where Windows external facts may be present
on non-Windows systems.

*Windows Fixes*

Bug #22619: Error when NetConnectionId is missing on
NetworkAdapterhttps://projects.puppetlabs.com/issues/22619

This was a regression in Facter 1.7.3 — Facter would fail and quit on
systems where a network adapter was configured in a specific way.

Bug #23368: Executable external facts fail on Windows
2003https://projects.puppetlabs.com/issues/23368

This was a problem with file paths containing a space, which included the
default directory for external facts under Windows 2003.

*Miscellaneous Fixes*

Bug #15586: ‘facter –help’ does not work with Ruby
1.9.3https://projects.puppetlabs.com/issues/15586

Facter was using an Rdoc feature that went away, so we replaced it with
something else. You can now get help on the command line when running
Facter under Ruby 1.9.3.

Bug #22322: facter should suppress stderr from “swap” commands on
Solarishttps://projects.puppetlabs.com/issues/22322

This was causing noisy logging on Solaris.

Bug #22334: Facter outputs information to stderr regardless of whether
–debug is enabled https://projects.puppetlabs.com/issues/22334

This was causing noisy logging everywhere.

*Fact Resolution Fixes (Various OSes)*

This release fixes several bugs where facts reported incorrect values on
certain operating systems.

Bug #21604: Xen virtual fact doesn’t work on
Windowshttps://projects.puppetlabs.com/issues/21604

Bug #16081: Facter reports bogus arch on
AIXhttps://projects.puppetlabs.com/issues/16081

Bug #12504: operatingsystemrelease doesn’t work for Ubuntu LTS
12.04https://projects.puppetlabs.com/issues/12504

Bug #18215: processorcount counting CPU cores on
Solarishttps://projects.puppetlabs.com/issues/18215

Bug #20739: processorX facts fail on HP superdome
servershttps://projects.puppetlabs.com/issues/20739

Bug #20994: memoryfree and memorysize facts are set to 0 on
AIXhttps://projects.puppetlabs.com/issues/20994

Bug #22844: The ‘virtual’ and ‘is_virtual’ facts are incorrect for Windows
guests hosted on kvm https://projects.puppetlabs.com/issues/22844

Bug #22789: is_virtual incorrectly shows true for
vserver_hosthttps://projects.puppetlabs.com/issues/22789

*Testing Fixes and Administrivia*

Refactor #22651: add fixture access methods for example /proc/cpuinfo
fileshttps://projects.puppetlabs.com/issues/22651

Bug #22238: Remove Fedora 17 from
build_defaults.yamlhttps://projects.puppetlabs.com/issues/22238

Bug #23135: Update Facter Master Windows/Solaris jobs to use
vcloud.https://projects.puppetlabs.com/issues/23135


Facter 1.7.4 Contributors
--
Adrien Thebo, Alex Harvey, Andrew Parker, Aran

Re: [Puppet Users] Puppet Labs issue tracker migration 16 Dec 2013

2013-12-17 Thread Josh Cooper

On Mon, Dec 16, 2013 at 8:19 AM, Erik Dalén erik.gustav.da...@gmail.comwrote:

What is the desired workflow for submitting a pull request for a ticket?

Charlie wrapped up the documentation for this here:
http://docs.puppetlabs.com/community/puppet_projects_workflow.html If you
find issues or have questions, please let us know.

The old field for branch seems gone and the issue status In topic branch
awaiting review is gone as well.

Please add a issue link to the PR and set the status to ready for merge.

The workflow menu shows 25 different issue statuses and I have no clue
which one to choose.

On 10 December 2013 19:51, Eric Sorenson eric.soren...@puppetlabs.comwrote:

Hi, as I mailed about a little while ago[1], we're migrating issue
tracking for Puppet Labs projects from Redmine to JIRA.

After working through the tooling and integration concerns, we're going
to make the switch on 16th of December.

More info on how this will work:

* Everybody needs to create a new account on JIRA, since we can’t migrate
passwords from redmine to jira.
* If you were watching redmine bugs to track their progress, you will be
notified via email with the new location of the bug in JIRA. You'll need to
set yourself up to watch the bug in JIRA with your newly-created account.
* Some older issues that we think are obsolete will not be migrated, but
if we made a mistake and forgot to include your favorite bug, there will be
a link on each Redmine issue where you can migrate it with a single click.
* The Redmine instance will remain up and read-only, because there's a
ton of back history, outgoing links, google indexing, etc that is quite
valuable to keep.
* Projects that use github issues will also migrate, but pull request
workflow remains as-is.

Please let me know if you have any additional questions.

[1] https://groups.google.com/d/topic/puppet-users/4lV1cT6Li-M/discussion

--
Eric Sorenson - eric.soren...@puppetlabs.com - freenode #puppet: eric0
puppet platform // coffee // techno // bicycles

--
Erik Dalén

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

--
Josh Cooper
Developer, Puppet Labs

Re: [Puppet Users] puppet master stopped loading facts since puppetdb installation

2013-12-17 Thread cko

Every node (except for the master) does something like this when i run
puppet agent -t:

root@node1:~$ puppet agent -t
Info: Retrieving plugin
Info: Loading facts in /var/lib/puppet/lib/facter/concat_basedir.rb
Info: Loading facts in /var/lib/puppet/lib/facter/environment.rb
Info: Loading facts in /var/lib/puppet/lib/facter/pe_version.rb
Info: Loading facts in /var/lib/puppet/lib/facter/puppet_vardir.rb
Info: Loading facts in /var/lib/puppet/lib/facter/iptables_version.rb
Info: Loading facts in /var/lib/puppet/lib/facter/ssh_hostkey_localhost.rb
Info: Loading facts in /var/lib/puppet/lib/facter/fsecure_version.rb
Info: Loading facts in /var/lib/puppet/lib/facter/facter_dot_d.rb
Info: Loading facts in /var/lib/puppet/lib/facter/root_home.rb
Info: Loading facts in
/var/lib/puppet/lib/facter/iptables_persistent_version.rb
Info: Loading facts in /var/lib/puppet/lib/facter/ip6tables_version.rb
Info: Caching catalog for node1.local.domain
Info: Applying configuration version '1386350341'
Notice: Finished catalog run in 25.51 seconds

The puppet master however doesn't.

An example on how this affects the functionality:

I use a template that manages the /etc/motd file.
It contains the fact kernelrelease. Meaning after i update the kernel on
the master, this information is supposed to be updated. (I'm still talking
about the master server, every other nodes works as expected!)
But since the master doesn't load facts on a run, the motd file doesn't get
updated.

On Wednesday, December 18, 2013 12:13:09 AM UTC+1, Deepak Giridharagopal
wrote:

On Dec 17, 2013, at 9:56 AM, cko der...@gmail.com javascript: wrote:

hey,

so i just installed puppetdb on a dedicated server (with pgsql).

I noticed that the puppet master server doesn't load any facts.

What do you mean doesn't load any facts? What is the problem you're
seeing?

root@puppetmaster:~$ puppet agent -t
Info: Retrieving plugin
Info: Caching catalog for puppetmaster.local.domain
Info: 'replace catalog' command for puppetmaster.local.domain submitted
to PuppetDB with UUID 87de0ebc-1543-4b8a-8434-ca9220238fda
Info: Applying configuration version '1387297065'
Notice: Finished catalog run in 20.88 seconds

Is this intended? Or did i miss something while installing and connecting
puppetDB?

[Puppet Users] A different way of managing POSIX ACLs : fooacl

[Puppet Users] puppet environments not working

Re: [Puppet Users] puppet environments not working

Re: [Puppet Users] puppet environments not working

[Puppet Users] Re: A different way of managing POSIX ACLs : fooacl

[Puppet Users] Geppetto complains about uninitialized variables in reduce function

[Puppet Users] puppet master stopped loading facts since puppetdb installation

Re: [Puppet Users] MySQL server install with datadir != /var/lib/mysql

[Puppet Users] Re: recursive descent

Re: [Puppet Users] puppet environments not working

Re: [Puppet Users] Re: recursive descent

Re: [Puppet Users] Re: recursive descent

Re: [Puppet Users] Re: yamlyzer

Re: [Puppet Users] recursive descent

Re: [Puppet Users] Re: yamlyzer

[Puppet Users] new puppet book revision

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

Re: [Puppet Users] puppet master stopped loading facts since puppetdb installation

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

Re: [Puppet Users] Re: yamlyzer

[Puppet Users] Process hung on FreeBSD

[Puppet Users] very odd Duplicate declaration problem.

[Puppet Users] Process hang on FreeBSD

Re: [Puppet Users] recursive descent

Re: [Puppet Users] recursive descent

Re: [Puppet Users] Process hang on FreeBSD

Re: [Puppet Users] Process hang on FreeBSD

Re: [Puppet Users] very odd Duplicate declaration problem.

[Puppet Users] Announce: Facter 1.7.4 Available

Re: [Puppet Users] Puppet Labs issue tracker migration 16 Dec 2013

Re: [Puppet Users] puppet master stopped loading facts since puppetdb installation

31 matches

Site Navigation

Mail list logo

Footer information