from:"jon"

I need to convert my resource based system to ENC. It's mostly 
straightforward but I'm not sure how to handle operations like these: 

Class['apt'] - Package| |

-- 
You received this message because you are subscribed 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/b6324c21-3725-480d-b2ab-33ee48577ba6%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] ENC - how to set order of operations?

Right. So how would I declare this dependency setup if I stop using node 
files?

On Monday, February 3, 2014 9:33:40 AM UTC-8, Jose Luis Ledesma wrote:

 Hi

 Perhaps  I'm confused but an ENC stores node definition and not collector 
 nor dependencies...doesn't it?

 Regards,
 El 03/02/2014 16:13, Jon Yeargers ethr...@gmail.com javascript: 
 escribió:

 I need to convert my resource based system to ENC. It's mostly 
 straightforward but I'm not sure how to handle operations like these: 

 Class['apt'] - Package| |

  -- 
 You received this message because you are subscribed 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/b6324c21-3725-480d-b2ab-33ee48577ba6%40googlegroups.com
 .
 For more options, visit https://groups.google.com/groups/opt_out.



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

Re: [Puppet Users] ENC - how to set order of operations?

So if a given node is named in both an ENC and the site manifest... it will
use both? IE If I have some definitions that I want to send everywhere and
others that are node specific.. I can use both types of node entries?

On Monday, February 3, 2014 10:14:52 AM UTC-8, Dan Bode wrote:

On Mon, Feb 3, 2014 at 9:45 AM, Jon Yeargers ethr...@gmail.comjavascript:
wrote:

Right. So how would I declare this dependency setup if I stop using node
files?

Even if you use an ENC, Puppet will still consult your site manifest, so
using an ENC does not preclude you from setting resource dependencies via
collection in your site manifest.

On Monday, February 3, 2014 9:33:40 AM UTC-8, Jose Luis Ledesma wrote:

Perhaps I'm confused but an ENC stores node definition and not
collector nor dependencies...doesn't it?

Regards,
El 03/02/2014 16:13, Jon Yeargers ethr...@gmail.com escribió:

I need to convert my resource based system to ENC. It's mostly
straightforward but I'm not sure how to handle operations like these:

Class['apt'] - Package| |

To view this discussion on the web visit https://groups.google.com/d/
msgid/puppet-users/b6324c21-3725-480d-b2ab-33ee48577ba6%
40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an
email to puppet-users...@googlegroups.com javascript:.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/89c4d5d6-1f79-454c-8d22-1e1fb9ce15d6%40googlegroups.com
.

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

--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/d0568d5a-450f-45e3-9d4e-7d85e2e07d60%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Port for ENC requests?

I'm trying to debug a new ENC setup. I created a short perl script to 
output a few lines of YAML. It runs fine on the puppet server but when I 
try it on a client I get this error:

Warning: Error 400 on SERVER: Failed to find client.domain.org via exec: 
Execution of the '/etc/puppet/ENC/plug0.pl client.domain.org' returned 13:

What I've tried:

- turning off SELinux / adding exceptions
 * no change
- running the script locally
* runs fine
- looking for errors in apache logs
* nothing in there
- looking for errors in $LOGDIR/messages
* nothing there either

What I'm wondering about is whether these requests need a certain port to 
be open in the firewall. The clients in question are connected via a VPN so 
the traffic is somewhat non-standard.

Somewhere else I should be looking for errors? What does error 13 imply?

-- 
You received this message because you are subscribed 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/7fb3cc93-b3ef-41f8-a169-40bffc13e2d3%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Error Message: Could not set present on ensure: Function not implemented

2014-01-29 Thread Jon Jaroker

Hello, 

Would anyone know what the error message Could not set present on ensure: 
Function not implemented means.  It is appearing in Puppet 2.7.13 on a 
File resource type.  The --debug flag does not give any hints.  

The complete manifest triggering this error is located here:

http://jaroker.org/technical_notes/issues/software/puppet/start

The full error message is:

err: /Stage[main]//Node[bose]/Openvz::Bindmount[apps07]/File[Bind Mount 
Config for apps07 on bose]/ensure: change from absent to present failed: 
Could not set 'present on ensure: Function not implemented - 
/etc/vz/conf/1107.mount20140128-9690-11oic7u-0 at 
/etc/puppet/modules/common/openvz/manifests/bindmount.pp:47

The resource being managed (where the problem is occurring) is:

file { Bind Mount Config for ${container} on ${host}:
ensure  = present,
path= $bind_conf,
content = 
template('openvz/mount.conf.erb','common/header.sh.erb'),
mode= 740, #(Proxmox file system unable to chmod)
}


Any suggestions on how to troubleshoot this?

Thank you,
Jon

-- 
You received this message because you are subscribed 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/4459553d-128f-4345-a4b7-6d1873d3dc7b%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Puppet 2.7.23 error Could not set present on ensure: Function not implemented

2014-01-28 Thread Jon Jaroker

Hello, I was wondering if anyone can give me a pointer on how to solve an
ambiguous Puppet error Function not implemented when attempting to create
a file using the 'file' resource type. The '--debug' flag does not produce
useful information.

My puppet manifests work fine on several other physical and virtual hosts.
This error appears on a new host that was recently installed. The
software and hardware configuration of this new host are almost identical
to all other systems on which the same puppet manifests runs normally.

I notice the error message is appending (what appears to be) the temporary
file name used in generating a diff to the managed resource.

I put the error message and relevant manifest on a web page as well as
excerpt them below.

Can someone offer suggestions on how I can debug this?

Thank you,
Jon

Full manifest is located here:

http://jaroker.org/technical_notes/issues/software/puppet/start

The error message is:

err: /Stage[main]//Node[bose]/Openvz::Bindmount[apps07]/File[Bind Mount Config
for apps07 on bose]/ensure: change from absent to present failed: Could not set
'present on ensure: Function not implemented -
/etc/vz/conf/1107.mount20140128-9690-11oic7u-0 at
/etc/puppet/modules/common/openvz/manifests/bindmount.pp:47

This error is being triggered by the following resource:

file { Bind Mount Config for ${container} on ${host}:
ensure = present,
path= $bind_conf,
content = template('openvz/mount.conf.erb','common/header.sh.erb'),
mode= 740, #(Proxmox file system unable to chmod)
}

--
You received this message because you are subscribed 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/d74d6954-c868-4cf4-8e2d-67dd740d9acf%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: What is the convention used if I want to pull content from source-control for populating a manifest resource?

2014-01-28 Thread Jon Jaroker

The URI scheme for 'source' is either 'puppet' or 'file'.  Here is the man 
page:

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

To pull from a repository, you should use a subversion manifest that 
implements checkout.  

Jon

On Monday, January 27, 2014 1:45:30 PM UTC-5, Mark Jaffe wrote:

 Manifest for an app:

 class my_app {
 .
 .
 .

file { '/etc/sysconfig/my_app/configs':
 ensure =  directory,
 mode  =   0755,
 source =  '
 https://subversion.mycompany.com/repository/project/trunk/model-config',
 }

 How would I provide user auth?


-- 
You received this message because you are subscribed 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/33875a92-1c20-4ecc-b998-b4624a5241be%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Getting agent v3.4 to manage my services

2013-12-31 Thread Jon Yeargers

I corrected the problem by including this in my /etc/init.d/script:

if [ -e $PIDFILE ]
then
exit 0
else
exit 1
fi

Put this in a 'status' command for your service control script. It works in
puppet v3.4.

On Monday, December 30, 2013 3:11:30 PM UTC-8, Edson Manners wrote:

I had this same problem and couldn't figure out why it did it. I was
moving from 2.7.23 to 3.x and it was driving me nuts, I never found what
was the exact cause as there weren't any errors showing up and ' puppet
agent -t' ran clean.

I ended up blowing away my whole puppet/passenger/puppetdb install and
starting from 3.4 in order to get past it. I wish you better luck.

On 12/30/2013 06:04 PM, Jon Yeargers wrote:

I have a group of services that are supposed to be maintained by puppet
agent. Up until I moved from 2.6 to 3.4 they were kept up to date and
running (as expected).

Since the upgrade of the puppet agent these services are no longer being
monitored. I'm sure that the server is still seeing the files as errors in
them are flagged.

Running 'puppet agent --debug' shows the requests for 'service name
status' go by and yet even though the service is not running there is no
move to start it. Running the 'service name start' command starts the
service normally.

So: what have I broken by upgrading my clients? As I mentioned - this
used to work.
--
You received this message because you are subscribed 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/dba2294d-826c-46d1-817c-6fd383818220%40googlegroups.com
.
For more options, visit https://groups.google.com/groups/opt_out.

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

[Puppet Users] Getting agent v3.4 to manage my services

2013-12-30 Thread Jon Yeargers

I have a group of services that are supposed to be maintained by puppet 
agent. Up until I moved from 2.6 to 3.4 they were kept up to date and 
running (as expected).

Since the upgrade of the puppet agent these services are no longer being 
monitored. I'm sure that the server is still seeing the files as errors in 
them are flagged. 

Running 'puppet agent --debug' shows the requests for 'service name 
status' go by and yet even though the service is not running there is no 
move to start it. Running the 'service name start' command starts the 
service normally.

So: what have I broken by upgrading my clients?  As I mentioned - this used 
to work.

-- 
You received this message because you are subscribed 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/dba2294d-826c-46d1-817c-6fd383818220%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] triggering 'apt-get update'?

2013-12-20 Thread Jon Yeargers

I'm using the puppetforge 'apt' module to deal with some repositories. It 
has 'always-apt-update' as a property and I've had it set to 'true' but I'm 
wondering what happens if I don't. 

Is the puppet package manager 'smart' enough to get the latest versions of 
packages that it's monitoring ('ensure = latest') without being told to 
keep the repository up to date?

The main reason I'm asking is that the 'apt-get update' seems to always run 
last in the 'agent' pass. IE it takes two runs to get the latest packages - 
1 to update the cache and the 2nd to get the latest versions. 

-- 
You received this message because you are subscribed 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/f1848bdf-c513-4d27-a156-8f6847e60650%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Execution expired? Error message during agent run

2013-12-20 Thread Jon Yeargers

Running 'puppet agent --test' - after 5-10 minutes of execution this error 
appeared:

err: Could not run Puppet configuration client: execution expired

When I ran the same command the execution resumed and continued to 
completion.


-- 
You received this message because you are subscribed 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/dd24edc8-dff5-44de-83d1-2b16e45e0d14%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Re: puppet node find doesn't return classes and scope vars ?

2013-12-19 Thread Jon McKenzie

https://tickets.puppetlabs.com/browse/PUP-1185

On Thursday, December 19, 2013 7:49:08 AM UTC-5, Felix.Frank wrote:

 Is there an issue for this in Jira? If not, it would be much appreciated 
 for either of you to create one. 

 Thanks, 
 Felix 

 On 12/13/2013 11:08 PM, Paul Archer wrote: 
  I see that puppet 3.3.2 has the problem as well. Worse, the 
  documentation for 'puppet node' doesn't match the actual command. 
  
  
  On Friday, December 13, 2013 11:13:26 AM UTC-6, Jon McKenzie wrote: 
  
  Re-upping this topic rather than creating a new one. 
  
  I'm using Puppet 3.3.1 and am still having this problem. 


-- 
You received this message because you are subscribed 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/d8ab6651-45c5-45ea-846b-c1e2d874885d%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Re: Getting latest agent on debian for ARM?

2013-12-13 Thread Jon Yeargers

So am I SOL on this? Is ARM considered an 'unsupported architecture' until 
I can create a 'dmidecode' for this platform?

On Wednesday, December 11, 2013 10:55:11 AM UTC-8, Jon Yeargers wrote:

 I can wget and install facter but the issues continue:

 root@plugpc-005:/tmp# apt-get install puppet
 Reading package lists... Done
 Building dependency tree
 Reading state information... Done
 You might want to run 'apt-get -f install' to correct these:
 The following packages have unmet dependencies:
  facter : Depends: dmidecode but it is not installable
  puppet : Depends: puppet-common (= 3.3.2-1puppetlabs1) but it is not 
 going to be installed
 E: Unmet dependencies. Try 'apt-get -f install' with no packages (or 
 specify a solution).


 root@plugpc-005:/tmp# apt-get install puppet-common
 Reading package lists... Done
 Building dependency tree
 Reading state information... Done
 You might want to run 'apt-get -f install' to correct these:
 The following packages have unmet dependencies:
  facter : Depends: dmidecode but it is not installable
  puppet-common : Depends: ruby-shadow but it is not installable or
   libshadow-ruby1.8 but it is not going to be 
 installed
  Depends: libaugeas-ruby but it is not going to be 
 installed or
   libaugeas-ruby1.9.1 but it is not going to be 
 installed or
   libaugeas-ruby1.8 but it is not going to be 
 installed
  Depends: hiera (= 1.0.0) but it is not going to be 
 installed
  Depends: ruby-rgen (= 0.6.5) but it is not going to be 
 installed
  Recommends: lsb-release but it is not going to be 
 installed
  Recommends: debconf-utils but it is not going to be 
 installed
 E: Unmet dependencies. Try 'apt-get -f install' with no packages (or 
 specify a solution).


 Attempts to install any of these packages gives me similar errors.

 On Wednesday, December 11, 2013 9:50:07 AM UTC-8, Jeff Bachtel wrote:

  You can fetch it directly (wget, curl, whatever) from


 http://apt.puppetlabs.com/pool/squeeze/main/f/facter/facter_1.6.18-1puppetlabs1_all.deb

 Jeff

 On 12/11/2013 12:39 PM, Jon Yeargers wrote:
  
  root@plugpc-005:~# apt-get install ruby libopenssl-ruby pciutils
 Reading package lists... Done
 Building dependency tree
 Reading state information... Done
 Note, selecting 'libruby' instead of 'libopenssl-ruby'
 pciutils is already the newest version.
 libruby is already the newest version.
 ruby is already the newest version.
 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

  There isn't a 'download' option for apt-get on this system so I tried 
 '--download-only':

  root@plugpc-005:~# apt-get --download-only install  facter
 Reading package lists... Done
 Building dependency tree
 Reading state information... Done
 Some packages could not be installed. This may mean that you have
 requested an impossible situation or if you are using the unstable
 distribution that some required packages have not yet been created
 or been moved out of Incoming.
 The following information may help to resolve the situation:

  The following packages have unmet dependencies:
  facter : Depends: dmidecode but it is not installable
 E: Broken packages
  
  I added '--ignore-missing' but the result was the same. 

 On Wednesday, December 11, 2013 7:47:02 AM UTC-8, Jeff Bachtel wrote: 

  demidecode (which is a hard dependency for facter) is not available for 
 armel in Debian's repository. I have confirmed that facter will not fail 
 outright when dmidecode is missing.

 The following facter variables will not be created, however:
 bios_release_date
 bios_vendor
 bios_version
 boardmanufacturer
 boardproductname
 boardserialnumber
 manufacturer
 productname
 serialnumber
 type
 uuid

 If that's acceptable for you, you can try

 apt-get install ruby libopenssl-ruby pciutils
 apt-get download facter
 dpkg -i --force-depends facter*.deb
 apt-get install puppet

 This will manually install the other facter dependencies (which should 
 exist for armel), download the facter .deb file, then do an install of it 
 without checking depends. The puppet install should succeed after that.

 I think facter's dmidecode dependency should be a Suggests vice a 
 Depends, and it might be worth filing a bugrep to get it changed.

 Jeff


 On 12/11/2013 10:31 AM, Jon Yeargers wrote:
  
 I also tried 'apt-get dist-upgrade'. This brought down 'hiera' (along 
 with a few other things). 

  Then tried 'apt-get install puppet-common' - this failed as 'facter' 
 needed a higher version.

  .. so tried 'facter' but this failed with:

  facter : Depends : dmidecode but it is not installable

  
  
  If I do 'apt-cache search dmidecode' it isn't available.

 On Wednesday, December 11, 2013 7:26:02 AM UTC-8, Jon Yeargers wrote: 

 'apt-get update' ran fine this time. 

  'apt-get install puppet':

  Some packages could not be installed. This may

[Puppet Users] Re: puppet node find doesn't return classes and scope vars ?

2013-12-13 Thread Jon McKenzie

Re-upping this topic rather than creating a new one.

I'm using Puppet 3.3.1 and am still having this problem.

For example, if I run:

puppet node find $(puppet config print certname) --render-as yaml 

The resulting YAML is missing ENC-set parameters (among other things).

On the other hand, if I call the Puppet server's REST API (e.g. a GET to 
https://puppet:8140/production/node/certname), I *do* get the ENC-set 
parameters.

I'd like to use the provided command-line tool to do this, but it doesn't 
seem to be working correctly. Am I missing something?

Thanks!

On Friday, April 5, 2013 4:14:36 AM UTC-4, Mohit Chawla wrote:

 Hi, 

 I am trying to use the node subcommand like so: 

 puppet node find --terminus rest --render-as yaml --mode master foo.com

 This only shows facts, name, environment, expiration and time but not the 
 classes or node level variables. 

 Puppet version is 2.7.20. Any suggestions ? 


-- 
You received this message because you are subscribed 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/8441d5dd-8207-4f3a-9fce-6f8ab872b199%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Re: Getting latest agent on debian for ARM?

2013-12-13 Thread Jon Yeargers

Just out of curiosity I created my own 'dmidecode' package with a trivial 
(does nothing) dmidecode executable. Once this was installed the rest of 
puppet v 3.3.2 installed fine.

NOW: it's having trouble accepting that certain services are already 
running and it's trying to restart them every time. Strangely enough it 
doesn't happen with 'system' services (EG apache2, snmpd) but only with my 
code. I can't imagine this is related to my fake dmidecode but I'll keep 
looking into it.

On Friday, December 13, 2013 4:08:10 AM UTC-8, Felix.Frank wrote:

 Ideally, there will be a newly released facter package that replaces 
 this dependency by a suggestion or recommendation. It will Just Work for 
 you then. 

 In the meantime, these are your options: 
 a) fetch the facter source package and build a forked package without 
 this dependency 
 b) fetch all deb packages you require and install them in one go using 
 dpkg -i --force-depends or similar. 

 Option (a) is simple if you're versed in the creation of Debian 
 packages, and pretty difficult if you're not. 

 HTH, 
 Felix 

 On 12/13/2013 12:39 PM, Jon Yeargers wrote: 
  So am I SOL on this? Is ARM considered an 'unsupported architecture' 
  until I can create a 'dmidecode' for this platform? 


-- 
You received this message because you are subscribed 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/40a9fd9d-127e-48b9-8c67-c284ca6bd694%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Re: Getting latest agent on debian for ARM?

2013-12-13 Thread Jon Yeargers

Answer here: 
http://stackoverflow.com/questions/14607385/puppet-does-not-start-a-service-varnish-when-puppet-apply-is-run



On Friday, December 13, 2013 11:07:01 AM UTC-8, Jon Yeargers wrote:

 Just out of curiosity I created my own 'dmidecode' package with a trivial 
 (does nothing) dmidecode executable. Once this was installed the rest of 
 puppet v 3.3.2 installed fine.

 NOW: it's having trouble accepting that certain services are already 
 running and it's trying to restart them every time. Strangely enough it 
 doesn't happen with 'system' services (EG apache2, snmpd) but only with my 
 code. I can't imagine this is related to my fake dmidecode but I'll keep 
 looking into it.

 On Friday, December 13, 2013 4:08:10 AM UTC-8, Felix.Frank wrote:

 Ideally, there will be a newly released facter package that replaces 
 this dependency by a suggestion or recommendation. It will Just Work for 
 you then. 

 In the meantime, these are your options: 
 a) fetch the facter source package and build a forked package without 
 this dependency 
 b) fetch all deb packages you require and install them in one go using 
 dpkg -i --force-depends or similar. 

 Option (a) is simple if you're versed in the creation of Debian 
 packages, and pretty difficult if you're not. 

 HTH, 
 Felix 

 On 12/13/2013 12:39 PM, Jon Yeargers wrote: 
  So am I SOL on this? Is ARM considered an 'unsupported architecture' 
  until I can create a 'dmidecode' for this platform? 



-- 
You received this message because you are subscribed 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/0b3e34b1-e3e1-4e8d-8a3a-23ab6be1bf8d%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Re: Getting latest agent on debian for ARM?

'apt-get update' ran fine this time.

'apt-get install puppet':

Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
puppet : Depends: puppet-common (= 3.3.2-1puppetlabs1) but
2.6.2-5+squeeze8 is to be installed
E: Broken packages

I also tried uninstalling puppet and then doing the install. Same result.

On Tuesday, December 10, 2013 3:11:27 PM UTC-8, Moses Mendoza wrote:

Hi all, apt.puppetlabs.com has been updated with additional
architectures so the 'all' packages should install. Can you check if
you still have the same issues?

On Tue, Dec 10, 2013 at 12:01 PM, Moses Mendoza
mo...@puppetlabs.comjavascript:
wrote:
On Tue, Dec 10, 2013 at 10:52 AM, Jon Yeargers
ethr...@gmail.comjavascript:
wrote:
I updated the repository file using the official puppet-recommended
version.
The corrected line is:

deb http://apt.puppetlabs.com squeeze main (i mistakenly entered
'wheezy'
above).

When I do 'apt-get update' I'm told:

W: Filed to fetch http://apt.puppetlabs.com/dists/squeeze/ReleaseUnable to
find expected entry main/binary-armel/Packages in Meta-index file
(malformed
Release file?)

On Tuesday, December 10, 2013 9:11:44 AM UTC-8, Felix.Frank wrote:

That's not the issue at all I think.

Is that source.list entry from a howto?

Have you tried the instructions here:

http://docs.puppetlabs.com/guides/puppetlabs_package_repositories.html#for-debian-and-ubuntu

Because what apt is making of your configuration is plain wrong.

On 12/10/2013 05:50 PM, Jon Yeargers wrote:
If I create a '/etc/apt/sources.list.d/puppet.list' with:

deb http://apt.puppetlabs.com/pool wheezy stable

I get:

Failed to fetch

http://apt.puppetlabs.com/pool/dists/wheezy/stable/binary-armel/Packages.gz
404 Not Found

I'm thinking that I might need to set this up on an x86 machine and
then
rebuild the package file myself in a private repository.

My apologies - this is a problem with our apt repository configuration
- we did not set it up to include architectures other than i386 and
amd64. We will be remedying this soon, so that while we may not yet
have arm-specific packages, at least our all-arch packages will work.

https://groups.google.com/d/msgid/puppet-users/0e4f7484-682f-44c9-b370-5a977d4085ee%40googlegroups.com.

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

--
Moses Mendoza
Puppet Labs

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

--
Moses Mendoza
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/a2bd1ecb-dd6a-42cb-9ffc-333e9cfdc0db%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Re: Getting latest agent on debian for ARM?

I also tried 'apt-get dist-upgrade'. This brought down 'hiera' (along with
a few other things).

Then tried 'apt-get install puppet-common' - this failed as 'facter' needed
a higher version.

.. so tried 'facter' but this failed with:

facter : Depends : dmidecode but it is not installable

If I do 'apt-cache search dmidecode' it isn't available.

On Wednesday, December 11, 2013 7:26:02 AM UTC-8, Jon Yeargers wrote:

'apt-get update' ran fine this time.

'apt-get install puppet':

The following packages have unmet dependencies:
puppet : Depends: puppet-common (= 3.3.2-1puppetlabs1) but
2.6.2-5+squeeze8 is to be installed
E: Broken packages

I also tried uninstalling puppet and then doing the install. Same result.

On Tuesday, December 10, 2013 3:11:27 PM UTC-8, Moses Mendoza wrote:

Hi all, apt.puppetlabs.com has been updated with additional
architectures so the 'all' packages should install. Can you check if
you still have the same issues?

On Tue, Dec 10, 2013 at 12:01 PM, Moses Mendoza mo...@puppetlabs.com
wrote:
On Tue, Dec 10, 2013 at 10:52 AM, Jon Yeargers ethr...@gmail.com
wrote:
I updated the repository file using the official puppet-recommended
version.
The corrected line is:

deb http://apt.puppetlabs.com squeeze main (i mistakenly entered
'wheezy'
above).

When I do 'apt-get update' I'm told:

W: Filed to fetch http://apt.puppetlabs.com/dists/squeeze/ReleaseUnable
to
find expected entry main/binary-armel/Packages in Meta-index file
(malformed
Release file?)

On Tuesday, December 10, 2013 9:11:44 AM UTC-8, Felix.Frank wrote:

That's not the issue at all I think.

Is that source.list entry from a howto?

Have you tried the instructions here:

http://docs.puppetlabs.com/guides/puppetlabs_package_repositories.html#for-debian-and-ubuntu

Because what apt is making of your configuration is plain wrong.

On 12/10/2013 05:50 PM, Jon Yeargers wrote:
If I create a '/etc/apt/sources.list.d/puppet.list' with:

deb http://apt.puppetlabs.com/pool wheezy stable

I get:

Failed to fetch

http://apt.puppetlabs.com/pool/dists/wheezy/stable/binary-armel/Packages.gz
404 Not Found

I'm thinking that I might need to set this up on an x86 machine and
then
rebuild the package file myself in a private repository.

https://groups.google.com/d/msgid/puppet-users/0e4f7484-682f-44c9-b370-5a977d4085ee%40googlegroups.com.

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

--
Moses Mendoza
Puppet Labs

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

--
Moses Mendoza
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/96382244-64e6-458e-a33a-81f24a4befbf%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Re: Getting latest agent on debian for ARM?

root@plugpc-005:~# apt-get install ruby libopenssl-ruby pciutils
Reading package lists... Done
Building dependency tree
Reading state information... Done
Note, selecting 'libruby' instead of 'libopenssl-ruby'
pciutils is already the newest version.
libruby is already the newest version.
ruby is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

There isn't a 'download' option for apt-get on this system so I tried
'--download-only':

root@plugpc-005:~# apt-get --download-only install facter
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
facter : Depends: dmidecode but it is not installable
E: Broken packages

I added '--ignore-missing' but the result was the same.

On Wednesday, December 11, 2013 7:47:02 AM UTC-8, Jeff Bachtel wrote:

demidecode (which is a hard dependency for facter) is not available for
armel in Debian's repository. I have confirmed that facter will not fail
outright when dmidecode is missing.

The following facter variables will not be created, however:
bios_release_date
bios_vendor
bios_version
boardmanufacturer
boardproductname
boardserialnumber
manufacturer
productname
serialnumber
type
uuid

If that's acceptable for you, you can try

apt-get install ruby libopenssl-ruby pciutils
apt-get download facter
dpkg -i --force-depends facter*.deb
apt-get install puppet

This will manually install the other facter dependencies (which should
exist for armel), download the facter .deb file, then do an install of it
without checking depends. The puppet install should succeed after that.

I think facter's dmidecode dependency should be a Suggests vice a Depends,
and it might be worth filing a bugrep to get it changed.

Jeff

On 12/11/2013 10:31 AM, Jon Yeargers wrote:

I also tried 'apt-get dist-upgrade'. This brought down 'hiera' (along with
a few other things).

Then tried 'apt-get install puppet-common' - this failed as 'facter'
needed a higher version.

.. so tried 'facter' but this failed with:

facter : Depends : dmidecode but it is not installable

If I do 'apt-cache search dmidecode' it isn't available.

On Wednesday, December 11, 2013 7:26:02 AM UTC-8, Jon Yeargers wrote:

'apt-get update' ran fine this time.

'apt-get install puppet':

The following packages have unmet dependencies:
puppet : Depends: puppet-common (= 3.3.2-1puppetlabs1) but
2.6.2-5+squeeze8 is to be installed
E: Broken packages

I also tried uninstalling puppet and then doing the install. Same
result.

On Tuesday, December 10, 2013 3:11:27 PM UTC-8, Moses Mendoza wrote:

Hi all, apt.puppetlabs.com has been updated with additional
architectures so the 'all' packages should install. Can you check if
you still have the same issues?

deb http://apt.puppetlabs.com squeeze main (i mistakenly entered
'wheezy'
above).

When I do 'apt-get update' I'm told:

W: Filed to fetch http://apt.puppetlabs.com/dists/squeeze/ReleaseUnable
to
find expected entry main/binary-armel/Packages in Meta-index file
(malformed
Release file?)

On Tuesday, December 10, 2013 9:11:44 AM UTC-8, Felix.Frank wrote:

That's not the issue at all I think.

Is that source.list entry from a howto?

Have you tried the instructions here:

http://docs.puppetlabs.com/guides/puppetlabs_package_repositories.html#for-debian-and-ubuntu

Because what apt is making of your configuration is plain wrong.

On 12/10/2013 05:50 PM, Jon Yeargers wrote:
If I create a '/etc/apt/sources.list.d/puppet.list' with:

deb http://apt.puppetlabs.com/pool wheezy stable

I get:

Failed to fetch

http://apt.puppetlabs.com/pool/dists/wheezy/stable/binary-armel/Packages.gz
404 Not Found

I'm thinking that I might need to set this up on an x86 machine
and then
rebuild the package file myself in a private repository.

My apologies - this is a problem with our apt repository configuration
- we did

Re: [Puppet Users] Re: Getting latest agent on debian for ARM?

I can wget and install facter but the issues continue:

root@plugpc-005:/tmp# apt-get install puppet
Reading package lists... Done
Building dependency tree
Reading state information... Done
You might want to run 'apt-get -f install' to correct these:
The following packages have unmet dependencies:
 facter : Depends: dmidecode but it is not installable
 puppet : Depends: puppet-common (= 3.3.2-1puppetlabs1) but it is not going 
to be installed
E: Unmet dependencies. Try 'apt-get -f install' with no packages (or 
specify a solution).


root@plugpc-005:/tmp# apt-get install puppet-common
Reading package lists... Done
Building dependency tree
Reading state information... Done
You might want to run 'apt-get -f install' to correct these:
The following packages have unmet dependencies:
 facter : Depends: dmidecode but it is not installable
 puppet-common : Depends: ruby-shadow but it is not installable or
  libshadow-ruby1.8 but it is not going to be 
installed
 Depends: libaugeas-ruby but it is not going to be 
installed or
  libaugeas-ruby1.9.1 but it is not going to be 
installed or
  libaugeas-ruby1.8 but it is not going to be 
installed
 Depends: hiera (= 1.0.0) but it is not going to be 
installed
 Depends: ruby-rgen (= 0.6.5) but it is not going to be 
installed
 Recommends: lsb-release but it is not going to be installed
 Recommends: debconf-utils but it is not going to be 
installed
E: Unmet dependencies. Try 'apt-get -f install' with no packages (or 
specify a solution).


Attempts to install any of these packages gives me similar errors.

On Wednesday, December 11, 2013 9:50:07 AM UTC-8, Jeff Bachtel wrote:

  You can fetch it directly (wget, curl, whatever) from


 http://apt.puppetlabs.com/pool/squeeze/main/f/facter/facter_1.6.18-1puppetlabs1_all.deb

 Jeff

 On 12/11/2013 12:39 PM, Jon Yeargers wrote:
  
  root@plugpc-005:~# apt-get install ruby libopenssl-ruby pciutils
 Reading package lists... Done
 Building dependency tree
 Reading state information... Done
 Note, selecting 'libruby' instead of 'libopenssl-ruby'
 pciutils is already the newest version.
 libruby is already the newest version.
 ruby is already the newest version.
 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

  There isn't a 'download' option for apt-get on this system so I tried 
 '--download-only':

  root@plugpc-005:~# apt-get --download-only install  facter
 Reading package lists... Done
 Building dependency tree
 Reading state information... Done
 Some packages could not be installed. This may mean that you have
 requested an impossible situation or if you are using the unstable
 distribution that some required packages have not yet been created
 or been moved out of Incoming.
 The following information may help to resolve the situation:

  The following packages have unmet dependencies:
  facter : Depends: dmidecode but it is not installable
 E: Broken packages
  
  I added '--ignore-missing' but the result was the same. 

 On Wednesday, December 11, 2013 7:47:02 AM UTC-8, Jeff Bachtel wrote: 

  demidecode (which is a hard dependency for facter) is not available for 
 armel in Debian's repository. I have confirmed that facter will not fail 
 outright when dmidecode is missing.

 The following facter variables will not be created, however:
 bios_release_date
 bios_vendor
 bios_version
 boardmanufacturer
 boardproductname
 boardserialnumber
 manufacturer
 productname
 serialnumber
 type
 uuid

 If that's acceptable for you, you can try

 apt-get install ruby libopenssl-ruby pciutils
 apt-get download facter
 dpkg -i --force-depends facter*.deb
 apt-get install puppet

 This will manually install the other facter dependencies (which should 
 exist for armel), download the facter .deb file, then do an install of it 
 without checking depends. The puppet install should succeed after that.

 I think facter's dmidecode dependency should be a Suggests vice a 
 Depends, and it might be worth filing a bugrep to get it changed.

 Jeff


 On 12/11/2013 10:31 AM, Jon Yeargers wrote:
  
 I also tried 'apt-get dist-upgrade'. This brought down 'hiera' (along 
 with a few other things). 

  Then tried 'apt-get install puppet-common' - this failed as 'facter' 
 needed a higher version.

  .. so tried 'facter' but this failed with:

  facter : Depends : dmidecode but it is not installable

  
  
  If I do 'apt-cache search dmidecode' it isn't available.

 On Wednesday, December 11, 2013 7:26:02 AM UTC-8, Jon Yeargers wrote: 

 'apt-get update' ran fine this time. 

  'apt-get install puppet':

  Some packages could not be installed. This may mean that you have
 requested an impossible situation or if you are using the unstable
 distribution that some required packages have not yet been created
 or been moved out of Incoming.
 The following information may help to resolve

[Puppet Users] Re: Getting latest agent on debian for ARM?

I've tried using 'gem' to install the latest build but it brings down lots 
of (seemingly) unnecessary bits with it. (examples, docs, etc)

On Thursday, December 5, 2013 9:16:15 AM UTC-8, Jon Yeargers wrote:

 I'm looking to deploy several hundred ARM based machines in the near 
 future. At this point the puppet agent version available via apt (Debian 6) 
  is 2.6. 

 I tried adding the apt.puppetlabs.com repository but it won't install on 
 my systems as the CPU type isn't supported. 

 What are my options to get 3.x? I don't see a path to compile the source. 
 Can I copy the relevant folders to a private repository and host from 
 there? 


-- 
You received this message because you are subscribed 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/8cb52b29-e9a4-4192-bb16-d7efa1917d65%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Problem with report processor - undefined method

I would love DEARLY to be able to update my clients (agents) but they are
running on ARM processors and I can't get the update. I posted about this
here and on askpuppet but haven't found an answer yet.

On Tuesday, December 10, 2013 8:16:33 AM UTC-8, Jeff Bachtel wrote:

If this is accurate, I can only warn that I've run into horribly annoying,
manifest-breaking issues trying to run 2.6/2.7 clients with 3.3 servers. It
may not be official advice, but if you can make puppet client versions
track your puppet server closer, you will have much less headache.

Jeff

On Thu, Dec 5, 2013 at 7:29 PM, Jon Yeargers ethr...@gmail.comjavascript:
wrote:

After I got puppetdb working I was looking about at the various bits of
data available. Looking at the 'nodes' option I was suprised to see this:

report_timestamp : null

for every node. They all have this for their puppet.conf:

[main]
logdir=/var/log/puppet
vardir=/var/lib/puppet
ssldir=/var/lib/puppet/ssl
rundir=/var/run/puppet
factpath=$vardir/lib/facter
templatedir=$confdir/templates
[agent]
server=server_name
certname=client_name
pluginsync=true
report=true

so I assumed they were reporting.

TL;DR

Looking at /var/log/messages on the server I found these messages
appearing:

puppet-master[1090]: Report processor failed: undefined method `=' for
nil:NilClass

What's up? Have I misconfigured something?

Clients: v 2.6
Server: v 3.3

--
You received this message because you are subscribed 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/d0e27c25-4970-4ee8-bc75-680d057ff9aa%40googlegroups.com
.
For more options, visit https://groups.google.com/groups/opt_out.

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

[Puppet Users] Re: Getting latest agent on debian for ARM?

If I create a '/etc/apt/sources.list.d/puppet.list' with:

deb http://apt.puppetlabs.com/pool wheezy stable

I get:

Failed to fetch 
http://apt.puppetlabs.com/pool/dists/wheezy/stable/binary-armel/Packages.gz 
404 Not Found

I'm thinking that I might need to set this up on an x86 machine and then 
rebuild the package file myself in a private repository.

On Tuesday, December 10, 2013 8:22:36 AM UTC-8, Jon Yeargers wrote:

 I've tried using 'gem' to install the latest build but it brings down lots 
 of (seemingly) unnecessary bits with it. (examples, docs, etc)

 On Thursday, December 5, 2013 9:16:15 AM UTC-8, Jon Yeargers wrote:

 I'm looking to deploy several hundred ARM based machines in the near 
 future. At this point the puppet agent version available via apt (Debian 6) 
  is 2.6. 

 I tried adding the apt.puppetlabs.com repository but it won't install on 
 my systems as the CPU type isn't supported. 

 What are my options to get 3.x? I don't see a path to compile the source. 
 Can I copy the relevant folders to a private repository and host from 
 there? 



-- 
You received this message because you are subscribed 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/a1b10982-5296-448e-b27b-608142dd47ef%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: Error 400 on SERVER: No such file or directory - getcwd

2013-12-10 Thread Jon Jaroker

I debugged this same 400 error with 'getcwd' in my 2.7.18 version of
puppet. I did not find useful information through web searches, so posted
my debugging steps here: http://jaroker.com/?p=2036

In my case, the puppet master had been operating normally for over a year.
I had recently updated my Eclipse IDE and created new manifests. The IDE
used non UTF-8 encoding on these new files. Subsequent puppet runs on
various nodes produced this 400-getcwd error: puppet: Could not retrieve
catalog from remote server Error 400 on SERVER “Could not parse for
environment...” getcwd

In my case, the solution was to identify DOS-encoded files on the master
and convert them to unix.

Jon

On Wednesday, June 19, 2013 12:28:28 PM UTC-4, Rachel Andrew wrote:

fully expecting to have done something silly here but am struggling to
debug why I am getting the error:

Error: Could not retrieve catalog from remote server: Error 400 on SERVER:
No such file or directory - getcwd at /etc/puppet/manifests/nodes.pp:2 on
node my.domain.net

the line in question is getting a custom module which has not changed
recently.

I was installing
http://www.practicalclouds.com/content/guide/pclouds-vcsdeploy-deploy-stuffand
having some permissions issues, so I think this may well be to do with
permissions. However I am at a loss as to what as everything looks to be
ok.

Puppet Master and two client nodes on Debian Wheezy, the clients both
return this error. Puppet version 3.2.1 on all 3.

Any suggestions as to where to start debugging this?

Rachel

--
You received this message because you are subscribed 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/3340e221-be23-405d-baa0-5d08001aedc8%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Re: Getting latest agent on debian for ARM?

I updated the repository file using the official puppet-recommended 
version. The corrected line is:

deb http://apt.puppetlabs.com squeeze main   (i mistakenly entered 'wheezy' 
above).

When I do 'apt-get update' I'm told:

W: Filed to fetch http://apt.puppetlabs.com/dists/squeeze/Release Unable to 
find expected entry main/binary-armel/Packages in Meta-index file 
(malformed Release file?)

On Tuesday, December 10, 2013 9:11:44 AM UTC-8, Felix.Frank wrote:

 That's not the issue at all I think. 

 Is that source.list entry from a howto? 

 Have you tried the instructions here: 

 http://docs.puppetlabs.com/guides/puppetlabs_package_repositories.html#for-debian-and-ubuntu
  

 Because what apt is making of your configuration is plain wrong. 

 On 12/10/2013 05:50 PM, Jon Yeargers wrote: 
  If I create a '/etc/apt/sources.list.d/puppet.list' with: 
  
  deb http://apt.puppetlabs.com/pool wheezy stable 
  
  I get: 
  
  Failed to fetch 
  
 http://apt.puppetlabs.com/pool/dists/wheezy/stable/binary-armel/Packages.gz 
  404 Not Found 
  
  I'm thinking that I might need to set this up on an x86 machine and then 
  rebuild the package file myself in a private repository. 


-- 
You received this message because you are subscribed 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/0e4f7484-682f-44c9-b370-5a977d4085ee%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: Problem with report processor - undefined method

2013-12-06 Thread Jon Yeargers

On further inspections the YAML files are still being created but not the 
puppet db entries. 

On Thursday, December 5, 2013 4:29:44 PM UTC-8, Jon Yeargers wrote:

 After I got puppetdb working I was looking about at the various bits of 
 data available. Looking at the 'nodes' option I was suprised to see this:

   report_timestamp : null

 for every node. They all have this for their puppet.conf:

 [main]
 logdir=/var/log/puppet
 vardir=/var/lib/puppet
 ssldir=/var/lib/puppet/ssl
 rundir=/var/run/puppet
 factpath=$vardir/lib/facter
 templatedir=$confdir/templates
 [agent]
 server=server_name
 certname=client_name
 pluginsync=true
 report=true

 so I assumed they were reporting. 

 TL;DR

 Looking at /var/log/messages on the server I found these messages 
 appearing:

 puppet-master[1090]: Report processor failed: undefined method `=' for 
 nil:NilClass

 What's up? Have I misconfigured something?

 Clients: v 2.6
 Server: v 3.3




-- 
You received this message because you are subscribed 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/6abed7eb-6cb9-439e-93be-01524276fed7%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Getting latest agent on debian for ARM?

I'm looking to deploy several hundred ARM based machines in the near 
future. At this point the puppet agent version available via apt (Debian 6) 
 is 2.6. 

I tried adding the apt.puppetlabs.com repository but it won't install on my 
systems as the CPU type isn't supported. 

What are my options to get 3.x? I don't see a path to compile the source. 
Can I copy the relevant folders to a private repository and host from 
there? 

-- 
You received this message because you are subscribed 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/06eb5267-9326-4a5b-91d8-cf55c734aaad%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] puppetdb not responding since 'yum update'

I did `yum update` on my puppet server about a week ago. Up to that point I 
had puppet and puppetdb running on the same machine. Since the update 
puppetdb doesn't appear to be listening on port 8081 anymore.

When I run `puppet agent --test` on a client I get this error:

err: Could not retrieve catalog from remote server: Error 400 on 
SERVER: Failed to submit 'replace facts' command for plugpc-005.client to 
PuppetDB at puppet.server:8081: Connection refused - connect(2)

Looking at `nmap -P0 puppet.server` shows that port 8081 isn't open. Trying 
`telnet puppet.server 8081` confirms this.

My configs are all set using the values from 
[here].(http://docs.puppetlabs.com/puppetdb/latest/connect_puppet_master.html).

`ps -ax` shows that the processes are running:

2040 ?Ss 4:55 /usr/sbin/openvpn --daemon --writepid 
/var/run/openvpn/puppet.pid --config puppet.conf --cd /etc/openvpn 
--script-security 2
29737 ?Sl 0:37 /usr/bin/java -XX:OnOutOfMemoryError=kill -9 
%p -Xmx192m -XX:+HeapDumpOnOutOfMemoryError 
-XX:HeapDumpPath=/var/log/puppetdb/puppetdb-oom.hprof -jar 
/usr/share/puppetdb/puppetdb.jar services -c /etc/puppetdb/conf.d
29924 ?Sl 0:01 Passenger AppPreloader: 
/usr/share/puppet/rack/puppetmasterd   
29963 ?Sl 0:00 Passenger RackApp: 
/usr/share/puppet/rack/puppetmasterd


The output of `netstat -nap | grep 8081` is empty. 

Turning off iptables doesn't make any difference. (not that it would - 
nobody is listening at the port anyway)

NOTE: This system was working ok before the update. I could download 
configs to clients and query the db for the results.

So - what did I break?

-- 
You received this message because you are subscribed 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/f4f93c97-a763-40c4-96c6-6c341893fc74%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] puppetdb not responding since 'yum update'

I used 'puppetdb-ssl-setup' (after removing the ssl folder) to no avail.

(sorry about cross posting - I thought I had removed the 'ask' entry)

On Thursday, December 5, 2013 12:25:24 PM UTC-8, Ken Barber wrote:

I responded to this in ask, but I'll answer here also.

In the file /etc/puppetdb/conf.d/jetty.ini, the settings ssl-host and
ssl-port must be set to listen on the SSL port (8081). However, if
your ssl certs aren't yet configured this may fail for you. Usually
puppetdb-ssl-setup is a good way to set these up automatically, so try
this first. For ssl-host I usually recommend something like ::1 or
0.0.0.0 to listen on all ports for simplicity, but you can make this
explicit if you like.

ken.

On Thu, Dec 5, 2013 at 7:48 PM, Jon Yeargers ethr...@gmail.comjavascript:
wrote:
I did `yum update` on my puppet server about a week ago. Up to that
point I
had puppet and puppetdb running on the same machine. Since the update
puppetdb doesn't appear to be listening on port 8081 anymore.

When I run `puppet agent --test` on a client I get this error:

err: Could not retrieve catalog from remote server: Error 400 on
SERVER:
Failed to submit 'replace facts' command for plugpc-005.client to
PuppetDB
at puppet.server:8081: Connection refused - connect(2)

Looking at `nmap -P0 puppet.server` shows that port 8081 isn't open.
Trying
`telnet puppet.server 8081` confirms this.

My configs are all set using the values from
[here].(
http://docs.puppetlabs.com/puppetdb/latest/connect_puppet_master.html).

`ps -ax` shows that the processes are running:

2040 ?Ss 4:55 /usr/sbin/openvpn --daemon --writepid
/var/run/openvpn/puppet.pid --config puppet.conf --cd /etc/openvpn
--script-security 2
29737 ?Sl 0:37 /usr/bin/java -XX:OnOutOfMemoryError=kill
-9
%p -Xmx192m -XX:+HeapDumpOnOutOfMemoryError
-XX:HeapDumpPath=/var/log/puppetdb/puppetdb-oom.hprof -jar
/usr/share/puppetdb/puppetdb.jar services -c /etc/puppetdb/conf.d
29924 ?Sl 0:01 Passenger AppPreloader:
/usr/share/puppet/rack/puppetmasterd
29963 ?Sl 0:00 Passenger RackApp:
/usr/share/puppet/rack/puppetmasterd

The output of `netstat -nap | grep 8081` is empty.

Turning off iptables doesn't make any difference. (not that it would -
nobody is listening at the port anyway)

NOTE: This system was working ok before the update. I could download
configs
to clients and query the db for the results.

So - what did I break?

https://groups.google.com/d/msgid/puppet-users/f4f93c97-a763-40c4-96c6-6c341893fc74%40googlegroups.com.

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

--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/6e94f3ef-4320-4b49-b430-10f646f220cc%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] puppetdb not responding since 'yum update'

Setting the 'ssl_host=' param to 0.0.0.0 turned the trick (so to speak). I
kept trying variations on what the ssl cert was created for.

Thank you for clearing this up for me.

On Thursday, December 5, 2013 1:17:51 PM UTC-8, Ken Barber wrote:

Can you show your jetty.ini? And the results of running
puppetdb-ssl-setup ... the more information the better in these kinds
of cases.

Also - is PuppetDB listening to port 8080?

On Thu, Dec 5, 2013 at 9:15 PM, Jon Yeargers ethr...@gmail.comjavascript:
wrote:
I used 'puppetdb-ssl-setup' (after removing the ssl folder) to no avail.

(sorry about cross posting - I thought I had removed the 'ask' entry)

On Thursday, December 5, 2013 12:25:24 PM UTC-8, Ken Barber wrote:

I responded to this in ask, but I'll answer here also.

ken.

On Thu, Dec 5, 2013 at 7:48 PM, Jon Yeargers ethr...@gmail.com
wrote:
I did `yum update` on my puppet server about a week ago. Up to that
point I
had puppet and puppetdb running on the same machine. Since the update
puppetdb doesn't appear to be listening on port 8081 anymore.

When I run `puppet agent --test` on a client I get this error:

Looking at `nmap -P0 puppet.server` shows that port 8081 isn't open.
Trying
`telnet puppet.server 8081` confirms this.

My configs are all set using the values from

[here].(
http://docs.puppetlabs.com/puppetdb/latest/connect_puppet_master.html).

`ps -ax` shows that the processes are running:

2040 ?Ss 4:55 /usr/sbin/openvpn --daemon --writepid
/var/run/openvpn/puppet.pid --config puppet.conf --cd /etc/openvpn
--script-security 2
29737 ?Sl 0:37 /usr/bin/java
-XX:OnOutOfMemoryError=kill
-9
%p -Xmx192m -XX:+HeapDumpOnOutOfMemoryError
-XX:HeapDumpPath=/var/log/puppetdb/puppetdb-oom.hprof -jar
/usr/share/puppetdb/puppetdb.jar services -c /etc/puppetdb/conf.d
29924 ?Sl 0:01 Passenger AppPreloader:
/usr/share/puppet/rack/puppetmasterd
29963 ?Sl 0:00 Passenger RackApp:
/usr/share/puppet/rack/puppetmasterd

The output of `netstat -nap | grep 8081` is empty.

Turning off iptables doesn't make any difference. (not that it would
-
nobody is listening at the port anyway)

NOTE: This system was working ok before the update. I could download
configs
to clients and query the db for the results.

So - what did I break?

https://groups.google.com/d/msgid/puppet-users/f4f93c97-a763-40c4-96c6-6c341893fc74%40googlegroups.com.

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

https://groups.google.com/d/msgid/puppet-users/6e94f3ef-4320-4b49-b430-10f646f220cc%40googlegroups.com.

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

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

[Puppet Users] Agent speed - what is 'normal'?

(This is actually two questions):

Running 'puppet agent --test' on a 1Ghz ARM based (Debian 6) fanless PC. 
It's pretty common to see the 'catalog run' take 120-300 seconds. Is this 
typical? 

Second (and possibly related): when I do a 'puppet agent --test (--noop)' I 
get this set of messages:

info: Retrieving plugin
info: Loading facts in facter_dot_d
info: Loading facts in pe_version
info: Loading facts in puppet_vardir
info: Loading facts in root_home
info: Loading facts in facter_dot_d
info: Loading facts in pe_version
info: Loading facts in puppet_vardir
info: Loading facts in root_home

Note the repeats. What have I misconfigured?

-- 
You received this message because you are subscribed 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/e1d50941-c0fb-44bf-aeae-923a2a8fc0d4%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Problem with report processor - undefined method

After I got puppetdb working I was looking about at the various bits of 
data available. Looking at the 'nodes' option I was suprised to see this:

  report_timestamp : null

for every node. They all have this for their puppet.conf:

[main]
logdir=/var/log/puppet
vardir=/var/lib/puppet
ssldir=/var/lib/puppet/ssl
rundir=/var/run/puppet
factpath=$vardir/lib/facter
templatedir=$confdir/templates
[agent]
server=server_name
certname=client_name
pluginsync=true
report=true

so I assumed they were reporting. 

TL;DR

Looking at /var/log/messages on the server I found these messages appearing:

puppet-master[1090]: Report processor failed: undefined method `=' for 
nil:NilClass

What's up? Have I misconfigured something?

Clients: v 2.6
Server: v 3.3


-- 
You received this message because you are subscribed 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/d0e27c25-4970-4ee8-bc75-680d057ff9aa%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: Status of Data in modules

2013-11-27 Thread Jon Shanks

Hey, 

Just to jump in at the end, (been following the thread) and looked at the 
implementatino of data in modules, but found that the complexity 
surrounding it was a bit much for people who were not experienced. Also, 
troubleshooting issues with data, i.e. some form of outcome of a puppet run 
that didn't match what was expected, created an extra overhead in trying to 
identify where the issue lied. We also really only want to return data for 
modules which are included on a host.

I therefore wrote a wrapper function which essentially utilises the 
hierarchy but with an addition

 - modules/%{module_name}/%{klass}

It retreives the classes from the API, using the node indirection.

%{klass} gets defined in the scope as it iterates, (ephemeral_from) and 
merges the data it finds, so, if a module as a dependency on another module 
i.e. 'foreman' has sudo rules it requires, you could place those within 
modules/sudo/foreman.yaml so that you are containing data relating to a 
module, without managing different hierarchical configurations throught 
your module structure. 

For defaults, we defined that as modules/%{module_name}/defaults, which is 
the last in the hierarchy. 

This probably would haev been nicer if the data sources could utlises the 
returned classes in the hierarchy and naturally iterate over the array, to 
save the wrapper functinoaity to do it. 

Obviously this wouldn't solve all the problems faced with modules or the 
principles of the forge modules being usable easily out of the box, but it 
solved the issue we had in categorising data within modules. Thought i 
would mention our use case. 

Jon


On Friday, 11 October 2013 19:09:23 UTC+1, Eric Sorenson wrote:


 Thanks to everyone who kicked the tires on the experimental data in 
 modules feature included in Puppet 3.3.0. We got a lot of feedback, some 
 cool proof-of-concept modules, and a definitive conclusion to the 
 experiment. 

 The idea of including a module-specific hiera backend is centered around 
 one primary use case: replacing the 'params class pattern', a common idiom 
 in Puppet modules that's described in the [Using Parameterized 
 Classes][param-classes] guide. The problem that most testers ran into 
 though is that for non-trivial modules they ended up having to re-implement 
 the Puppet DSL logic encoded in their params.pp in convoluted, non-obvious 
 ways. The solutions to this led to more contortions until we'd ended up 
 with the ability to execute parser functions in the right-hand-side of a 
 yaml value. So something which started out trying to help separate data 
 from code ended up putting code back into data! 

 Additionally, even after multiple attempts to simplify the surface area 
 and user experience with the bindings system (described in ARM-9) that 
 underlay the data-in-modules implementation, users still found its 
 complexity daunting. There are some important bits of scaffolding (like an 
 actual type system for Puppet!) that will prove valuable as more of the 
 future parser and evaluator work that Henrik is building makes its way into 
 the product, but in the final analysis the data in modules feature was the 
 wrong vehicle to introduce them. 

 Refocusing on the problems users were trying to solve (and here I have to 
 give shout-outs to Ashley Penney for his [puppetlabs-ntp][] branch and the 
 dynamic duo of Spencer Krug/William van Hevelingen for their [startrek][] 
 module) and the problems with the 'params' pattern lent some clarity. We've 
 gotten into a situation of disparity with regard to hiera and data 
 bindings, because data bindings enable module _users_ to use their 
 site-wide hiera data but don't provide moduel _authors_ the same 
 affordance. But rather than introduce additional complexity, we can close 
 the gap for existing code patterns. 

 So the proposed solution at this point is: 
 - enable an implicit data-binding lookup against the hiera-puppet backend 
 for a value of 'classname::variable' in the file 
 'modules/classname/manifests/params.pp', which simplifies class definition 
 and provides consistency with other hiera backends. As a module author, 
 you'd still leave your logic for variables in params.pp, but they'd be 
 implicitly looked up via data bindings as the class is declared, after 
 consulting site-wide hiera. 
 - remove the user-facing '--binder' functionality 
 - fix known problems with the hiera-puppet lookups ([Redmine 
 15746][15746], namely, but if there are others that are important to you 
 please speak up!) 

 To show how this would work, I'll rework the ['smart parameter defaults' 
 example][param-classes] I linked above, with my commentary behind `##` 
 comments: 

 # /etc/puppet/modules/webserver/manifests/params.pp 
 
 class webserver::params {   ## nothing changes here... 
  $packages = $operatingsystem ? { 
/(?i-mx:ubuntu|debian)/= 'apache2', 
/(?i-mx:centos|fedora|redhat)/ = 'httpd

[Puppet Users] Re: Class declaration ordering causes duplicate resource error

2013-11-19 Thread Jon McKenzie

Thanks for the replies and being patient with me!

Maybe I'm thinking about this incorrectly, but it seems to me that 
announcing a dependency (I need x defined somewhere in order to work 
properly) shouldn't require a class to declare the dependency as well. It 
seems to me that the dependent class should not have to know anything about 
how a particular dependency is defined, just that it is defined.

As an analogy to RPM package dependencies, if I have a package called 
Django that requires a package which provides the python capability, the 
Django package shouldn't need to include it's own version of Python. It 
should be able to re-use any package which has the capability.


What does one have to do with the other?


You were suggesting using auto-lookups via Hiera to populate class 
parameters, but we're using Foreman to populate those parameters. AFAIK, 
there's no interoperability between Foreman's ENC and Hiera (without 
writing my own).

Jon

-- 
You received this message because you are subscribed 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/e76b49ff-70f0-4b18-8b41-ecf853acef65%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Class declaration ordering causes duplicate resource error

2013-11-15 Thread Jon McKenzie

Has anyone run into this issue before? 
http://projects.puppetlabs.com/issues/5046#note-17

Is there something obvious that I'm missing?

-- 
You received this message because you are subscribed 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/400dd448-7a55-48b3-a1ca-1cf49cfddb2e%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: Class declaration ordering causes duplicate resource error

2013-11-15 Thread Jon McKenzie

Thanks John,

Unfortunately, we're using Foreman in our shop for the ENC, so using Hiera 
is currently not possible (AFAIK)

For some reason, I thought the require statement was analogous to the 
require metaparameter. But looking at the documentation, clearly that's 
not the case. Still, this seems like a bug to me. If this is a duplicate 
declaration, shouldn't it error regardless of the ordering within the 
manifest? 

Anyways, would writing something like this work?

class { foo::bar:
Class[foo:baz] - Class[foo::bar]
}

On Friday, November 15, 2013 5:27:11 PM UTC-5, jcbollinger wrote:



 On Friday, November 15, 2013 10:08:54 AM UTC-6, Jon McKenzie wrote:

 Has anyone run into this issue before? 
 http://projects.puppetlabs.com/issues/5046#note-17

 Is there something obvious that I'm missing?



 Yes.  The 'require' function is a form of class declaration, functionally 
 equivalent to 'include' + an automatic relationship.  You therefore do have 
 multiple declarations of class foo::baz: one in foo::bar and one in 
 foo::bam.  As long as the parameterized-style declaration is evaluated 
 first, all is well, but otherwise you will get a duplicate declaration 
 error.

 This general problem is one of my principal reasons for advising folks to 
 not use parameterized-style class declarations, as I have done since 
 parameterized classes were introduced.  In Puppet 3 you can usefully create 
 and use parameterized classes without using parameterized-style 
 declarations by relying on automatic parameter binding through Hiera.


 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/813a4c7c-f7b8-4d9a-9620-430a8c2f307d%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Puppet can't start service (dropbox) but init.d command works manually

2013-09-14 Thread Jon Jaroker

Ashley,

Thanks for reporting the solution. I was just struggling with the same odd 
behavior. My setup automatically inserts puppet managed comments at the 
top of all templates, but this breaks init scripts (at least in Debian).

Jon

=
Jon Jaroker
http://jaroker.com

On Monday, July 2, 2012 12:10:29 AM UTC-4, Ashley Baumann wrote:

 This was failing for me because the init.d script needed a #!/bin/sh at 
 the top 
 of it. Puppet was getting an Exec Format Error when it tried to run it. 


 11008 execve(/etc/init.d/dropbox, [/etc/init.d/dropbox, status], [/* 
 23 
 vars */]) = -1 ENOEXEC (Exec format error) 

 Ashleyb 




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

Re: [Puppet Users] MCollective Puppet plugin - runall not working

2013-07-11 Thread Jon Ward

Hi,

I had just copied the files over manually and placed them in the respective 
directories, I've now also installed the deb packages 
mcollective-puppet-agent on the agent nodes and 
mcollective-puppet-common on the client nodes from the Puppetlabs repo 
although this didn't make a difference.

I have the following files in my $libdir/mcollective/data on both the 
client and agent nodes:

agent_data.ddl
agent_data.rb
fstat_data.ddl
fstat_data.rb
puppet_data.ddl
puppet_data.rb
resource_data.ddl
resource_data.rb

I also have everything from the util, validator, aggregate and agent dirs 
on both nodes, and the application dir on the client node.

Thanks,

Jon

On Wednesday, July 10, 2013 10:40:23 PM UTC+1, R.I. Pienaar wrote:



 - Original Message - 
  From: Jon Ward jgh...@gmail.com javascript: 
  To: puppet...@googlegroups.com javascript: 
  Sent: Wednesday, July 10, 2013 5:15:59 PM 
  Subject: [Puppet Users] MCollective Puppet plugin - runall not working 
  
  Hi, 
  
  I've got the Puppet plugin for MCollective installed and working, 
 however 
  the 'runall' action always discovers 0 enabled nodes. 
  
  # mco puppet runall 2 
   2013-07-10 15:57:16: Running all nodes with a concurrency of 2 
   2013-07-10 15:57:16: Discovering enabled Puppet nodes to manage 
   2013-07-10 15:57:19: Found 0 enabled nodes 
  
  
  Looking in the server log on a node I would have expected to run I can 
 see 
  this: 
  
  D, [2013-07-10T15:03:53.137854 #9657] DEBUG -- : base.rb:25:in `lookup' 
   Doing data query puppet_data for '' 
   D, [2013-07-10T15:03:53.139202 #9657] DEBUG -- : base.rb:109:in 
   `validate_filter?' Failing based on class and fact composition 
   D, [2013-07-10T15:03:53.139318 #9657] DEBUG -- : base.rb:117:in 
   `validate_filter?' Passing based on agent puppet 
   D, [2013-07-10T15:03:53.139404 #9657] DEBUG -- : base.rb:159:in 
   `validate_filter?' Message failed the filter checks 
  
  
  As far as I can work out, the following line in util/puppetrunner.rb 
 might 
  be failing: 
  
   def find_enabled_nodes 
   
   ... 
   
   @client.compound_filter(puppet().enabled=true) 
   
   ... 
   
   end 
   
   
  If I do an 'mco puppet status' then the Summary of Applying and Summary 
 of 
  Idling work, however the Summary of enabled and Summary of 
 daemon_present 
  show: 
  
   *Could not compute summary - exception raised while processing startup 
   hook* 
   
  
   So it seems that it thinks all the nodes are disabled. However other 
  actions such as enable and disable work correctly, and runonce 
  correctly determines which nodes are enabled. 
  
  I've had a dig around the code but got completely lost so any pointers 
  would be gratefully appreciated! 
  
  I'm running Puppet 3.2.1, MCollective 2.2.4 with activemq on Debian 6. 
  

 how did you install the plugin? did you install the data plugins on the 
 node? 


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

Re: [Puppet Users] MCollective Puppet plugin - runall not working

2013-07-11 Thread Jon Ward

Ah, sorry the node I was testing was disabled, and the ones that were 
enabled were missing some of the $libdir/ directories (I had copied them up 
manually and Puppet had wiped them out without my realising.)

I'm getting an error now, but at least the nodes are being discovered:

# mco puppet -v runall 2
2013-07-11 09:56:31: Running all nodes with a concurrency of 2
2013-07-11 09:56:31: Discovering enabled Puppet nodes to manage
Discovering hosts using the mc method for 3 second(s)  2
2013-07-11 09:56:34: Found 2 enabled nodes
Discovering hosts using the mc method for 3 second(s)  0

The puppet application failed to run, use -v for full error details: Can 
only supply discovery data if direct_addressing is enabled

Can only supply discovery data if direct_addressing is enabled 
(RuntimeError)
from /usr/lib/ruby/1.8/mcollective/rpc/client.rb:467:in `discover'  

from 
/usr/share/mcollective/plugins/mcollective/util/puppetrunner.rb:82:in 
`runhost'
from 
/usr/share/mcollective/plugins/mcollective/util/puppetrunner.rb:75:in 
`runhosts'
from /usr/lib/ruby/1.8/timeout.rb:79:in `each_with_index'
from 
/usr/share/mcollective/plugins/mcollective/util/puppetrunner.rb:65:in `each'
from 
/usr/share/mcollective/plugins/mcollective/util/puppetrunner.rb:65:in 
`each_with_index'
from 
/usr/share/mcollective/plugins/mcollective/util/puppetrunner.rb:65:in 
`runhosts'
from 
/usr/share/mcollective/plugins/mcollective/util/puppetrunner.rb:59:in 
`runall_once'
from 
/usr/share/mcollective/plugins/mcollective/util/puppetrunner.rb:21:in 
`runall'
from 
/usr/share/mcollective/plugins/mcollective/application/puppet.rb:277:in 
`runall_command'
from 
/usr/share/mcollective/plugins/mcollective/application/puppet.rb:382:in 
`send'
from 
/usr/share/mcollective/plugins/mcollective/application/puppet.rb:382:in 
`main'
from /usr/lib/ruby/1.8/mcollective/application.rb:285:in `run'
from /usr/lib/ruby/1.8/mcollective/applications.rb:23:in `run'
from /usr/bin/mco:20




On Thursday, July 11, 2013 10:43:43 AM UTC+1, R.I. Pienaar wrote:



 - Original Message - 
  From: Jon Ward jgh...@gmail.com javascript: 
  To: puppet...@googlegroups.com javascript: 
  Sent: Thursday, July 11, 2013 10:37:00 AM 
  Subject: Re: [Puppet Users] MCollective Puppet plugin - runall not 
 working 
  
  Hi, 
  
  I had just copied the files over manually and placed them in the 
 respective 
  directories, I've now also installed the deb packages 
  mcollective-puppet-agent on the agent nodes and 
  mcollective-puppet-common on the client nodes from the Puppetlabs repo 
  although this didn't make a difference. 
  
  I have the following files in my $libdir/mcollective/data on both the 
  client and agent nodes: 
  
  agent_data.ddl 
  agent_data.rb 
  fstat_data.ddl 
  fstat_data.rb 
  puppet_data.ddl 
  puppet_data.rb 
  resource_data.ddl 
  resource_data.rb 
  
  I also have everything from the util, validator, aggregate and agent 
 dirs 
  on both nodes, and the application dir on the client node. 

 that certainly all seems fine, no exception logged in the servers log? We 
 do now log them - but I suspect that's only in the development series. 

 If there's no exception, put this little script on your node and just run 

ruby test.rb 

 and show us what it says http://p.devco.net/409 


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

Re: [Puppet Users] MCollective Puppet plugin - runall not working

2013-07-11 Thread Jon Ward

Ah that's working perfectly now, thanks so much for your time.

Yep, I will update my Puppet scripts to install the deb packages going 
forward.

Jon

On Thursday, July 11, 2013 11:01:33 AM UTC+1, R.I. Pienaar wrote:



 - Original Message - 
  From: Jon Ward jgh...@gmail.com javascript: 
  To: puppet...@googlegroups.com javascript: 
  Sent: Thursday, July 11, 2013 10:59:11 AM 
  Subject: Re: [Puppet Users] MCollective Puppet plugin - runall not 
 working 
  
  Ah, sorry the node I was testing was disabled, and the ones that were 
  enabled were missing some of the $libdir/ directories (I had copied them 
 up 
  manually and Puppet had wiped them out without my realising.) 

 best to install the agents using the debs yeah, takes care of all these 
 problems 

  
  I'm getting an error now, but at least the nodes are being discovered: 
  
  # mco puppet -v runall 2 
  2013-07-11 09:56:31: Running all nodes with a concurrency of 2 
  2013-07-11 09:56:31: Discovering enabled Puppet nodes to manage 
  Discovering hosts using the mc method for 3 second(s)  2 
  2013-07-11 09:56:34: Found 2 enabled nodes 
  Discovering hosts using the mc method for 3 second(s)  0 
  
  The puppet application failed to run, use -v for full error details: Can 
  only supply discovery data if direct_addressing is enabled 

 set direct_addressing=1 everywhere, you need to be using the ActiveMQ or 
 RabbitMQ connectors for this. 


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

[Puppet Users] MCollective Puppet plugin - runall not working

2013-07-10 Thread Jon Ward

Hi,

I've got the Puppet plugin for MCollective installed and working, however 
the 'runall' action always discovers 0 enabled nodes.

# mco puppet runall 2
 2013-07-10 15:57:16: Running all nodes with a concurrency of 2
 2013-07-10 15:57:16: Discovering enabled Puppet nodes to manage
 2013-07-10 15:57:19: Found 0 enabled nodes


Looking in the server log on a node I would have expected to run I can see 
this:

D, [2013-07-10T15:03:53.137854 #9657] DEBUG -- : base.rb:25:in `lookup' 
 Doing data query puppet_data for ''
 D, [2013-07-10T15:03:53.139202 #9657] DEBUG -- : base.rb:109:in 
 `validate_filter?' Failing based on class and fact composition
 D, [2013-07-10T15:03:53.139318 #9657] DEBUG -- : base.rb:117:in 
 `validate_filter?' Passing based on agent puppet
 D, [2013-07-10T15:03:53.139404 #9657] DEBUG -- : base.rb:159:in 
 `validate_filter?' Message failed the filter checks


As far as I can work out, the following line in util/puppetrunner.rb might 
be failing:

 def find_enabled_nodes

 ...

 @client.compound_filter(puppet().enabled=true)

 ...

 end


If I do an 'mco puppet status' then the Summary of Applying and Summary of 
Idling work, however the Summary of enabled and Summary of daemon_present 
show:

 *Could not compute summary - exception raised while processing startup 
 hook*


 So it seems that it thinks all the nodes are disabled. However other 
actions such as enable and disable work correctly, and runonce 
correctly determines which nodes are enabled.

I've had a dig around the code but got completely lost so any pointers 
would be gratefully appreciated!

I'm running Puppet 3.2.1, MCollective 2.2.4 with activemq on Debian 6.

Cheers,

Jon

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

Re: [Puppet Users] AD user add to local windows group?

2013-06-12 Thread Jon

Has there been any advancement with this bug?

On Friday, May 31, 2013 2:53:30 PM UTC-4, Trevor Vaughan wrote:

 This sounds like the other side of the coin to a bug that I filed: 
 https://projects.puppetlabs.com/issues/19414

 Not being able to add AD/LDAP users to a local group is a fail.

 Thanks,

 Trevor


 On Fri, May 31, 2013 at 1:19 PM, Josh Cooper 
 jo...@puppetlabs.comjavascript:
  wrote:

 Hi Vince,


 On Fri, May 31, 2013 at 8:31 AM, VinceH vince.h...@gmail.comjavascript:
  wrote:

 Pardon my noobness to this, but is anyone able to get around this 
 issuehttps://projects.puppetlabs.com/issues/15326
 ?

 group {'testgroup':

 ensure  =  present,
 members = 'DOMAIN\user',
 name = 'test'

 }  

 Yields

 OLE error code:8007056B in Active Directory   A member could not be 
 added to or removed from the local group because the member does not exist.

 I'm running v3.2.1 and the bug report is from v2.7.17 -- am I doing 
 something wrong?

 -- 
 You received this message because you are subscribed 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 post to this group, send email to puppet...@googlegroups.comjavascript:
 .
 Visit this group at http://groups.google.com/group/puppet-users?hl=en.
 For more options, visit https://groups.google.com/groups/opt_out.
  
  


 This is bug https://projects.puppetlabs.com/issues/17031

 Josh

 -- 
 Josh Cooper
 Developer, Puppet Labs

 *Join us at PuppetConf 2013, August 22-23 in San Francisco - *
 http://bit.ly/pupconf13*
 **Register now and take advantage of the Early Bird discount - save 25%!*
  
 -- 
 You received this message because you are subscribed to the Google Groups 
 Puppet Users group.
 To unsubscribe from this group and stop receiving emails from it, send an 
 email to puppet-users...@googlegroups.com javascript:.
 To post to this group, send email to puppet...@googlegroups.comjavascript:
 .
 Visit this group at http://groups.google.com/group/puppet-users?hl=en.
 For more options, visit https://groups.google.com/groups/opt_out.
  
  




 -- 
 Trevor Vaughan
 Vice President, Onyx Point, Inc
 (410) 541-6699
 tvau...@onyxpoint.com javascript:

 -- This account not approved for unencrypted proprietary information -- 


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

Re: [Puppet Users] Issue installing on RHEL 6 (2.6.32-358.2.1.el6.x86_64)

2013-06-09 Thread Jon Stanley

On Fri, Jun 7, 2013 at 4:45 PM, Kenneth Edgar ken.ed...@gmail.com wrote:
Protected multilib versions: libselinux-2.0.94-5.3.el6.i686 !=
 libselinux-2.0.94-5.3.el6_4.1.x86_64
  You could try using --skip-broken to work around the problem
  You could try running: rpm -Va --nofiles --nodigest

Basically this indicates a problem with your yum configuration or
repos. What it's refusing to do is to install differing versions of
the same package for different architectures (i686 and x86_64)

Particularly, the libselinux package has an issue. What this error
means is that you attempted to install libselinux-2.0.94-5.3.el6.i686
but you have 2.0.94-5.3.el6_4.1.x86_64 already installed (or the other
way around, I forget)

If you're using the install media as a repo on an updated system, that
would explain this. The el6_4 dist tag indicates an async errata (i.e.
released between major RHEL releases) for RHEL6.4, while the .el6 is
what gets shipped on install media (overly simplifying things here,
you could have prior releases async errata, for example el6_3 in a
minor release if there were no other changes) for a minor release.

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

[Puppet Users] MSSQL Server 2012

2013-06-04 Thread Jon Mosco

I am using the MSSQL server module from puppet as a baseline for the
installation of SQL Server 2012, and am running into issues durring the
install.  It gets a lot of the way done, and issues this error:

Error: \\puppet\installs\SQLServer2012SP1\setup.exe
/CONFIGURATIONFILE=C:\sql201
2.config.ini returned 194 instead of one of [0]
Error: /Stage[main]/Erp_db2012::Mssql_2012/Exec[install_mssql2012]/returns:
chan
ge from notrun to 0 failed: \\puppet\installs\SQLServer2012SP1\setup.exe
/CONFIG
URATIONFILE=C:\sql2012.config.ini returned 194 instead of one of [0]
Notice: Finished catalog run in 1933.62 seconds
Press any key to continue . . .

The module I wrote looks like this:

class db2012::mssql_2012 {

  file { 'C:\sql2012.config.ini':
#content = template('db2012/config_2012.ini.erb'),
ensure   = present,
source   =
puppet:///modules/erp_db2012/2012ConfigurationFile.ini,
  }

  exec { 'install_mssql2012':
#command = \\\puppet\installs\SQLServer2012SP1\\setup.exe
/Action=Install /IACCEPTSQLSERVERLICENSETERMS /QS
/CONFIGURATIONFILE=C:\\sql2012.config.ini,
command  = \\\puppet\installs\SQLServer2012SP1\\setup.exe
/CONFIGURATIONFILE=C:\\sql2012.config.ini,
logoutput= true,
creates  = C:\\Program Files\\Mirosoft SQL Server,
#timeout = 1200,
timeout  = 0,
#returns  = 3,
require  = File ['C:\sql2012.config.ini'],
#Dism['NetFx3'] ],
  }
}

I can try to add the return codes, but I am not sure if this is a solid fix.

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

[Puppet Users] Re: Hiera lookups in templates

2013-05-10 Thread Jon Ward

Hi,

Have you tried doing the Hiera lookup on the command line to double check 
it can be read?

$ hiera -d -c /path/to/hiera.yaml jrs_config_server1 fqdn=hostname


Cheers,

Jon

On Friday, May 10, 2013 12:18:22 PM UTC+1, Jonathan Gazeley wrote:

 Hi, 

 I'm having a problem accessing Hiera data from within templates. Yes, I 
 know this is not the recommended way to access Hiera data, but in my use 
 case I think it will be easier overall. 

 In manifests, this code works: 

 { 
ip = hiera('jrs_config_server1'), 
 } 

 In a template, part of the same module as the manifest, this does not 
 work: 

 ipaddr = %= scope.function_hiera([jrs_config_server1]) % 

 It fails with this error: 

 Could not find data item jrs_config_server1 in any Hiera data file and 
 no default supplied 

 The value of  jrs_config_server1 is in Hiera, specific to the fqdn of 
 the node. I'm struggling to see why it would not be working. Any ideas? 

 Cheers, 
 Jonathan 


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

[Puppet Users] Re: hiera-gpg causing big increase in catalog compile time

2013-05-10 Thread Jon Ward



 If you use many parameterized classes, then Puppet 3's automatic class 
 parameter binding will tend to aggravate that problem, especially if you 
 typically allow class parameters to take default values or DSL-specified 
 values (so that hiera has lots of complete misses on the parameter names).


Yep this was what I eventually worked out was causing my massive increase 
in compile times - I wasn't aware of the new data binding stuff in Puppet 3 
and was making heavy use of default values in parameterised classes without 
realizing that each one was triggering a Hiera lookup through all of my 
yaml and then gpg data files.

I ended up changing most of my parameterised classes back to regular 
classes, and not using any default values in the remaining ones - to be 
honest with Hiera I didn't really need them any more as I put my default 
values in common.yaml - and this reduced my catalog compile time back to a 
tolerable level. That said my compile times are still a lot higher than 
they were prior to using Hiera and the GPG backend, and I was shocked when 
I ran Puppetmaster in debug mode to see it opening each file in turn for 
every single lookup. Caching the data would seem the sensible way to go.
 
On Thursday, May 9, 2013 4:18:21 PM UTC+1, Aaron Mills wrote:

 Hmm..it seems like a pretty basic use case is an accompanying gpg file for 
 each level of a hierarchy, just to store things like passwords, or 
 sensitive data. Minimizing the use of things like hiera's 3.x data bindings 
 to gain speed in hiera-gpg lookups feels like throwing the baby out with 
 the bathwater.

 I wonder how difficult (read: secure) it would be to cache the data across 
 calls. An md5sum could be used to determine whether the contents of a .gpg 
 file have changed since the last lookup. Instead of decrypting each file 
 for every call, hiera-gpg can do something like:

 - Calculate an md5sum of the .gpg files, and the data from these files 
 stored in memory, redis, or wherever.
 - When asked for a variable, do an md5sum of the .gpg file and, if the 
 values are the same, return the data from memory
 - If the hash values don't match, reload the data from the .gpg file.

 Seems like this would be slightly faster than having to fully decrypt the 
 contents of each file for every parameter lookup.


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

Re: [Puppet Users] Re: Hiera lookups in templates

2013-05-10 Thread Jon Ward

Try putting the variable in common.yaml at the bottom of the hierarchy and 
see if it gets picked up. If it does then perhaps the value of the fqdn 
fact isn't what you think it is.

You can also try running puppetmaster in the foreground in debug mode:

$ puppet master —no-daemonize —debug


Now when you run puppet you should see the Hiera lookups happening as the 
catalog is compiled, this might help you pinpoint the problem..

On Friday, May 10, 2013 3:46:28 PM UTC+1, Jonathan Gazeley wrote:

 Hi Jon, 

 Thanks for your tip. I had made a typo in my yaml which debug mode 
 picked up. I fixed it, and now your command works when run on the 
 puppetmaster but the same error persists when the variable is accessed 
 either from a manifest or from a template during a puppet agent run. 

 I'm wondering if it might be something to do with the agents not syncing 
 the hiera data store, perhaps? I'm new to hiera... 

 Cheers, 
 Jonathan 



 On 10/05/13 14:25, Jon Ward wrote: 
  Hi, 
  
  Have you tried doing the Hiera lookup on the command line to double 
  check it can be read? 
  
  $ hiera -d -c /path/to/hiera.yaml jrs_config_server1 fqdn=hostname 
  
  
  Cheers, 
  
  Jon 
  
  On Friday, May 10, 2013 12:18:22 PM UTC+1, Jonathan Gazeley wrote: 
  
  Hi, 
  
  I'm having a problem accessing Hiera data from within templates. 
  Yes, I 
  know this is not the recommended way to access Hiera data, but in 
  my use 
  case I think it will be easier overall. 
  
  In manifests, this code works: 
  
  { 
 ip = hiera('jrs_config_server1'), 
  } 
  
  In a template, part of the same module as the manifest, this does 
  not work: 
  
  ipaddr = %= scope.function_hiera([jrs_config_server1]) % 
  
  It fails with this error: 
  
  Could not find data item jrs_config_server1 in any Hiera data file 
  and 
  no default supplied 
  
  The value of  jrs_config_server1 is in Hiera, specific to the 
  fqdn of 
  the node. I'm struggling to see why it would not be working. Any 
  ideas? 
  
  Cheers, 
  Jonathan 
  
  -- 
  You received this message because you are subscribed 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 post to this group, send email to 
  puppet...@googlegroups.comjavascript:. 

  Visit this group at http://groups.google.com/group/puppet-users?hl=en. 
  For more options, visit https://groups.google.com/groups/opt_out. 
  
  



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

Re: [Puppet Users] Can I exec a bash function?

2013-03-19 Thread Jon Stanley

On Tue, Mar 19, 2013 at 6:03 PM, Steffen Vulpius
steffen.vulp...@gmail.com wrote:

 I have a file foo.sh which is basically a library of various bash functions.
 Is there a way to execute these functions from puppet

Correct me if I'm wrong, but you have a file foo.sh, that defines a
bash function called bar, and you want to execute bar from inside a
puppet exec resource?

I don't think that as such is possible. One creative thing that you
might be able to do (I haven't tested this at all) is to make a bunch
of symlinks to foo.sh (bar, baz, whatever) for the functions in your
library, and in the main part, look at $0 to see what you should do.

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

[Puppet Users] Using $name in resources?

2013-02-28 Thread Jon Stanley

Using 2.6.17, I have something like this:

class yumrepos {
   yumrepo { ['a',
   'b']:
   descr=yum repo $name,
   baseurl=http://someurl/$name;;
 }
}

Instead of using the names 'a' and 'b', like I'd expect (so a baseurl
of http://someurl/a), it creates .repo files with those names, and
repos inside of them, but everywhere the name should get substituted,
it substitutes the name of the class instead. Any pointers in how to
make it substitute the name of the resource instead? I have about 20
repos to define, and would rather just do it this way.

I've tried making it a resource type default in the class, as well as
specifying at the end of the array, like above. Both yield the same
results. Am I being completely dense and missing something here?

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

[Puppet Users] Hiera always looks up class params, even if they are not hiera('vars')

2013-02-21 Thread Jon Ward

Hi,

I've been trying to debug my slow Puppet runs since using hiera-gpg 
(https://groups.google.com/d/topic/puppet-users/CRu_RolrX_8/discussion) and 
found some unexpected (by me) behaviour in hiera.

It seems that hiera does a lookup for any class parameters, even if they 
are not hiera functions.

e.g. say I have a class:

class hieratest($default_value=default) {
 file { /tmp/hieratest.txt:
 ensure = present,
 content = $default_value,
 }
 }


and in my nodes.pp I have

include hieratest


If I run puppetmaster in the foreground and do a 'puppet agent -t' I can 
see that hiera is looking through my entire hierarchy for 
hieratest::default_value. I would not expect hiera to do this unless I had 
put:

class hieratest($default_value=hiera('default_value', default)) { ... }


I noticed that if I include the 'default_value' var in my hiera common.yaml 
it is not found / used, however if I put 'hieratest::default_value' in then 
it is used. Is this the expected behaviour? If so is there any way to 
include a default parameter in a class without it doing a hiera lookup? 
This seems to have quite a major impact on my catalog compile time once I 
add the gpg backend.


Cheers,

Jon

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

[Puppet Users] Re: Hiera always looks up class params, even if they are not hiera('vars')

2013-02-21 Thread Jon Ward

Ah I missed that, thanks Craig.



On Thursday, February 21, 2013 12:43:12 PM UTC, Jon Ward wrote:

 Hi,

 I've been trying to debug my slow Puppet runs since using hiera-gpg (
 https://groups.google.com/d/topic/puppet-users/CRu_RolrX_8/discussion) 
 and found some unexpected (by me) behaviour in hiera.

 It seems that hiera does a lookup for any class parameters, even if they 
 are not hiera functions.

 e.g. say I have a class:

 class hieratest($default_value=default) {
 file { /tmp/hieratest.txt:
 ensure = present,
 content = $default_value,
 }
 }


 and in my nodes.pp I have

 include hieratest


 If I run puppetmaster in the foreground and do a 'puppet agent -t' I can 
 see that hiera is looking through my entire hierarchy for 
 hieratest::default_value. I would not expect hiera to do this unless I had 
 put:

 class hieratest($default_value=hiera('default_value', default)) { ... }


 I noticed that if I include the 'default_value' var in my hiera 
 common.yaml it is not found / used, however if I put 
 'hieratest::default_value' in then it is used. Is this the expected 
 behaviour? If so is there any way to include a default parameter in a class 
 without it doing a hiera lookup? This seems to have quite a major impact on 
 my catalog compile time once I add the gpg backend.


 Cheers,

 Jon



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

[Puppet Users] hiera-gpg causing big increase in catalog compile time

2013-02-20 Thread Jon Ward

Hi,

I've been using hiera for a little while and have started using the 
hiera-gpg back-end for passwords etc.

The problem is, I am seeing a massive increase in catalog compile time when 
using hiera-gpg. On one particular node where there is quite a lot going 
on, catalog compile time jumped from 5s to 90s. My typical compile times 
have gone from around 2s to around 30s.

I have the gpg backend listed underneath yaml in my hiera.yaml file, so 
from what I understand my .gpg config files should only be interrogated if 
no answer is found in the .yaml files. I only have half a dozen or so vars 
stored in the .gpg files.

By simply removing the gpg backend from hiera.yaml the compile times go 
back down to normal.

I'm using Puppet 3.1.0 installed from apt.puppetlabs.com on Debian Squeeze 
 hiera-gpg 1.1.0 installed from Rubygems.

Would appreciate any tips for debugging this problem, thanks in advance.

Jon

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

[Puppet Users] Re: Can Puppet interact with perl script user input fields?

2012-10-08 Thread Jon Skarpeteig

It was less then a dozen commands to setup. A bit longer than that
once put into puppet.

Is this code available anywhere?

On Oct 5, 12:55 pm, Steven Nemetz snem...@hotmail.com wrote:
 The centrify script may be thousands of lines, but it doesn't do that much. A 
 lot of it is for user interaction and multiple OS stuff. At my last company 
 we used centrify for authentication. It was less then a dozen commands to 
 setup. A bit longer than that once put into puppet.

 If you really want to interact with the script instead, Linux has programs 
 for doing this. There is no reason to duplicate this in the puppet core, when 
 this is not the recommended way of doing things. If the script is installing 
 things and puppet doesn't know about everything that is installed and 
 modified, it can't manage them. Goes against the primary design.

 Steven







  Date: Thu, 4 Oct 2012 23:55:55 -0700
  Subject: [Puppet Users] Re: Can Puppet interact with perl script user input 
  fields?
  From: jon.skarpet...@gmail.com
  To: puppet-users@googlegroups.com

  The script is several thousand lines of code. Definitely not easier
  than Guzman Braso's suggestion :-)

  Although I'm surprised that Puppet doesn't have any supported way of
  shell interaction with scripts?

  On Oct 5, 4:01 am, Peter Brown rendhal...@gmail.com wrote:
   It's probably easier in the long run to work out what that script does
   and replicate those settings in your samba puppet class.

   On 4 October 2012 19:34, Jon Skarpeteig jon.skarpet...@gmail.com wrote:

I'm trying to automate deployment of centrify-samba, which has a
adbindproxy.pl setup script attached. This script expects user input
(where 9 out of 10 options can be defaulted). Is there any way for
Puppet to preconfigure the inputs for this scripts, and mimic user
behavior by supplying this information?

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

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

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

[Puppet Users] Re: Can Puppet interact with perl script user input fields?

2012-10-05 Thread Jon Skarpeteig

The script is several thousand lines of code. Definitely not easier
than Guzman Braso's suggestion :-)

Although I'm surprised that Puppet doesn't have any supported way of
shell interaction with scripts?

On Oct 5, 4:01 am, Peter Brown rendhal...@gmail.com wrote:
 It's probably easier in the long run to work out what that script does
 and replicate those settings in your samba puppet class.

 On 4 October 2012 19:34, Jon Skarpeteig jon.skarpet...@gmail.com wrote:







  I'm trying to automate deployment of centrify-samba, which has a
  adbindproxy.pl setup script attached. This script expects user input
  (where 9 out of 10 options can be defaulted). Is there any way for
  Puppet to preconfigure the inputs for this scripts, and mimic user
  behavior by supplying this information?

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

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

[Puppet Users] Can Puppet interact with perl script user input fields?

2012-10-04 Thread Jon Skarpeteig

I'm trying to automate deployment of centrify-samba, which has a
adbindproxy.pl setup script attached. This script expects user input
(where 9 out of 10 options can be defaulted). Is there any way for
Puppet to preconfigure the inputs for this scripts, and mimic user
behavior by supplying this information?

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

[Puppet Users] Using Exported Resources in nginx loadbalancer conf

Hi all,

I'm attempting to use exported resources to dynamically generate an nginx 
config file. What I'd like to do if have all my web servers export their 
hostname inside a file resource, and have these collected by my 
loadbalancer and used in the config file, restarting nginx if anything has 
changed.

There is an example of something very similar in Pro Puppet on pages 
145-146 using Apache. In the example the individual hostnames are gathered 
by apache inside the balancer block using an include statement, however it 
doesn't seem possible to do this in an upstream block in nginx.

So I think I need to somehow gather the hostnames into an array which I 
then use inside my conf file erb template to create the upstream server 
entries. My problem is how to do this. If I create a custom fact this will 
get evaluated before (I think) the resources are exported and gathered. If 
I use a custom function or some ruby inside the erb template that's 
evaluated on the master, not the agent. I do have a puppet agent running on 
the master server so I could collect the exported resources there and use a 
function, that's the best solution I can think of at the moment, just 
wondering if anyone else out there has had any success doing something like 
this?

Thanks,

Jon
 

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

Re: [Puppet Users] Using Exported Resources in nginx loadbalancer conf

Hi Greg,

Yeah that's what I'd hoped - my balancer.conf.erb template had this:

upstream %= balancer_name %_balancer {
include /etc/nginx/conf.d.upstream_servers/*.conf;
}

However when I try to start nginx I get:

Starting nginx: [emerg]: include directive is not allowed here

A bit of googling (e.g.
http://stackoverflow.com/questions/4165116/can-include-directive-be-used-within-upstream-block-of-nginx)

seemed to suggest it's not possible.

On Tuesday, September 25, 2012 12:47:37 PM UTC+1, Greg Sutcliffe wrote:

On 25 September 2012 12:03, Jon Ward jgh...@gmail.com javascript:
wrote:
Hi all,

I'm attempting to use exported resources to dynamically generate an
nginx
config file. What I'd like to do if have all my web servers export their
hostname inside a file resource, and have these collected by my
loadbalancer
and used in the config file, restarting nginx if anything has changed.

Nginx can do include directives, right? Can you do something like:

upstream
include conf.d/upstream/*.conf
/upstream

and then have each host export a file in
conf.d/upstream/$hostname.conf containing $hostname:$port (or whatever
is needed).

Not sure if that will work, my nginx is a little rusty...

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

Re: [Puppet Users] Using Exported Resources in nginx loadbalancer conf

Thanks Bill - looks like concat provides a potential solution, will give 
that a go.

Jon

On Tuesday, September 25, 2012 1:50:39 PM UTC+1, Bill Fraser wrote:

 Hi Jon, 

 I have seen something similar done with Puppet Labs' haproxy module: 

 https://github.com/puppetlabs/puppetlabs-haproxy 

 Essentially the balancer members export information about themselves 
 (hostname, port, listening service, etc) which is collected by a 
 balancer server. The configuration is then pieced together using the 
 concat module. 

 I believe that is what you are trying to accomplish here, and hopefully 
 you find it useful to see how it is done in another module. 

 Regards, 
 Bill 

 On 12-09-25 07:03 AM, Jon Ward wrote: 
  Hi all, 
  
  I'm attempting to use exported resources to dynamically generate an 
 nginx 
  config file. What I'd like to do if have all my web servers export their 
  hostname inside a file resource, and have these collected by my 
  loadbalancer and used in the config file, restarting nginx if anything 
 has 
  changed. 
  
  There is an example of something very similar in Pro Puppet on pages 
  145-146 using Apache. In the example the individual hostnames are 
 gathered 
  by apache inside the balancer block using an include statement, however 
 it 
  doesn't seem possible to do this in an upstream block in nginx. 
  
  So I think I need to somehow gather the hostnames into an array which I 
  then use inside my conf file erb template to create the upstream server 
  entries. My problem is how to do this. If I create a custom fact this 
 will 
  get evaluated before (I think) the resources are exported and gathered. 
 If 
  I use a custom function or some ruby inside the erb template that's 
  evaluated on the master, not the agent. I do have a puppet agent running 
 on 
  the master server so I could collect the exported resources there and 
 use a 
  function, that's the best solution I can think of at the moment, just 
  wondering if anyone else out there has had any success doing something 
 like 
  this? 
  
  Thanks, 
  
  Jon 

  



-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/CI4CJG3-hBoJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Re: hello world application