[Puppet Users] Can't convert Puppet::Util::Log into Integer

[Andrei-Florian Staicu]

Hi all,

Could anyone help me at least start debugging this issue?
All agents have the same error, but i can't find anything on the
master-side logs. And the agent-side logs are non-existent (/var/log/puppet
is empty).

Thanks.

Versions:
Master:
Red Hat Enterprise Linux Server release 6.3
puppet-server-3.1.0-1.el6.noarch
puppetdb-1.1.1-1.el6.noarch
puppetdb-terminus-1.1.1-1.el6.noarch
puppet-dashboard-1.2.21-1.el6.noarch
puppet-3.1.0-1.el6.noarch
Agents:
Red Hat Enterprise Linux Server release 6.3
puppet-3.1.0-1.el6.noarch

[root@somvat121892 ~]# puppet agent --test --verbose --debug
Debug: Using settings: adding file resource 'lastrunfile':
'File[/var/lib/puppet/state/last_run_summary.yaml]{:links=:follow,
:ensure=:file, :backup=false, :mode=644,
:path=/var/lib/puppet/state/last_run_summary.yaml, :loglevel=:debug}'
Debug: Failed to load library 'ldap' for feature 'ldap'
Debug: Puppet::Type::User::ProviderLdap: feature ldap is missing
Debug: Puppet::Type::User::ProviderPw: file pw does not exist
Debug: Puppet::Type::User::ProviderUser_role_add: file roleadd does not
exist
Debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/dsimport
does not exist
Debug: Failed to load library 'ldap' for feature 'ldap'
Debug: Puppet::Type::Group::ProviderLdap: feature ldap is missing
Debug: Puppet::Type::Group::ProviderPw: file pw does not exist
Debug: Puppet::Type::Group::ProviderDirectoryservice: file /usr/bin/dscl
does not exist
Debug: Using settings: adding file resource 'logdir':
'File[/var/log/puppet]{:links=:follow, :group=puppet,
:ensure=:directory, :backup=false, :owner=puppet, :mode=750,
:path=/var/log/puppet, :loglevel=:debug}'
Debug: Using settings: adding file resource 'certdir':
'File[/var/lib/puppet/ssl/certs]{:links=:follow, :ensure=:directory,
:backup=false, :owner=puppet, :path=/var/lib/puppet/ssl/certs,
:loglevel=:debug}'
Debug: Using settings: adding file resource 'graphdir':
'File[/var/lib/puppet/state/graphs]{:links=:follow, :ensure=:directory,
:backup=false, :path=/var/lib/puppet/state/graphs, :loglevel=:debug}'
Debug: Using settings: adding file resource 'requestdir':
'File[/var/lib/puppet/ssl/certificate_requests]{:links=:follow,
:ensure=:directory, :backup=false, :owner=puppet,
:path=/var/lib/puppet/ssl/certificate_requests, :loglevel=:debug}'
Debug: Using settings: adding file resource 'clientyamldir':
'File[/var/lib/puppet/client_yaml]{:links=:follow, :ensure=:directory,
:backup=false, :mode=750, :path=/var/lib/puppet/client_yaml,
:loglevel=:debug}'
Debug: Using settings: adding file resource 'hostprivkey':
'File[/var/lib/puppet/ssl/private_keys/somvat121892.pem]{:links=:follow,
:ensure=:file, :backup=false, :owner=puppet, :mode=600,
:path=/var/lib/puppet/ssl/private_keys/somvat121892.pem,
:loglevel=:debug}'
Debug: Using settings: adding file resource 'resourcefile':
'File[/var/lib/puppet/state/resources.txt]{:links=:follow, :ensure=:file,
:backup=false, :owner=root, :mode=640,
:path=/var/lib/puppet/state/resources.txt, :loglevel=:debug}'
Debug: Using settings: adding file resource 'lastrunreport':
'File[/var/lib/puppet/state/last_run_report.yaml]{:links=:follow,
:ensure=:file, :backup=false, :mode=640,
:path=/var/lib/puppet/state/last_run_report.yaml, :loglevel=:debug}'
Debug: Using settings: adding file resource 'confdir':
'File[/etc/puppet]{:links=:follow, :ensure=:directory, :backup=false,
:path=/etc/puppet, :loglevel=:debug}'
Debug: Using settings: adding file resource 'ssldir':
'File[/var/lib/puppet/ssl]{:links=:follow, :ensure=:directory,
:backup=false, :owner=puppet, :mode=771,
:path=/var/lib/puppet/ssl, :loglevel=:debug}'
Debug: Using settings: adding file resource 'privatekeydir':
'File[/var/lib/puppet/ssl/private_keys]{:links=:follow,
:ensure=:directory, :backup=false, :owner=puppet, :mode=750,
:path=/var/lib/puppet/ssl/private_keys, :loglevel=:debug}'
Debug: Using settings: adding file resource 'client_datadir':
'File[/var/lib/puppet/client_data]{:links=:follow, :ensure=:directory,
:backup=false, :mode=750, :path=/var/lib/puppet/client_data,
:loglevel=:debug}'
Debug: Using settings: adding file resource 'hostpubkey':
'File[/var/lib/puppet/ssl/public_keys/somvat121892.pem]{:links=:follow,
:ensure=:file, :backup=false, :owner=puppet, :mode=644,
:path=/var/lib/puppet/ssl/public_keys/somvat121892.pem,
:loglevel=:debug}'
Debug: Using settings: adding file resource 'libdir':
'File[/var/lib/puppet/lib]{:links=:follow, :ensure=:directory,
:backup=false, :path=/var/lib/puppet/lib, :loglevel=:debug}'
Debug: Using settings: adding file resource 'statedir':
'File[/var/lib/puppet/state]{:links=:follow, :ensure=:directory,
:backup=false, :mode=1755, :path=/var/lib/puppet/state,
:loglevel=:debug}'
Debug: Using settings: adding file resource 'vardir':
'File[/var/lib/puppet]{:links=:follow, :ensure=:directory,
:backup=false, :path=/var/lib/puppet, :loglevel=:debug}'
Debug: Using settings: adding file resource 'publickeydir':
'File[/var/lib/puppet/ssl/public_keys]{:links=:follow,

[Puppet Users] Re: Export a file from one node and collect on another

[Russell Parsloe]

On Wednesday, 20 March 2013 18:04:41 UTC, jcbollinger wrote:



 On Wednesday, March 20, 2013 5:41:47 AM UTC-5, Russell Parsloe wrote:

 I'm trying to use Puppet and PuppetDB to export a config file from one 
 node, and collect it on another i.e.

 export */etc/app1/file1.cfg* from *node a* and collect *
 /etc/app2/file2.cfg* on *node b*.

 I need the contents of file1.cfg and file2.cfg to be the same, but the 
 paths and file names themselves are different. I cannot centralise this 
 file as it is generated at install time by node a.


 If by generated at install time by node a you mean that a local process 
 running on node a creates the file, then what you are asking for is not 
 Puppet exported resources.  Exported resources are a means for the master 
 to record certain declarations made during the compilation of one node's 
 catalog so that they can later be incorporated by reference into other 
 nodes' catalogs.  All the necessary details of the resource to be exported 
 must therefore be known to the master -- exported resources do not collect 
 data from clients.

 If, on the other hand, what you want to do is consistent with Puppet 
 exported resources as I described them, then I think Felix's suggestion of 
 using property overrides at collection time will probably work fine.  The 
 only caveat is that you may find that Puppet will not let you declare a 
 physical /etc/app1/file1.cfg on node b because of title collision with the 
 collected resource.


 John


Looks like I fall into the not Puppet exported resources category. I am 
trying to read a file on node a, throw that into PuppetDB and collect it on 
node b. I've used exported resources for many other things such as host 
files and Nagios config, and after your explanation, it's now very clear in 
my mind what it can and cannot do.

I'll research another method - the trouble with Puppet being so good, is 
now I want to do everything through the use of Puppet!

Thanks for the replies. 

-- 
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: Agent nodes not appearing in Enterprise live management

[Steve F]

Interesting that I didn't have MCollective installed on either agent. Is 
there any other service that I need to get this live management to work? 
MCollective is installed on both now, just trying to trawl through the 
limited README to configure it.
I'm finding it perturbing that there's not a huge amount of documentation 
on this (and what there is seems out of date), despite the age of the 
product.

On Friday, 22 March 2013 09:49:57 UTC, Steve F wrote:

 Hi all,

 First off, I'm very much a new user when it comes to Puppet, just trying 
 to get my head around all that it can do so I'm assuming I've missed 
 something extremely obvious.

 I have a small setup consisting of three virtual machines on the same 
 subnet who can all happily talk to each other and run puppet agent -t with 
 no problems.

 There is the master running the learning VM from their tutorial
 [root@learn modules]# facter puppetversion
 2.7.19 (Puppet Enterprise 2.7.0)

 An agent (also running the learning VM in agent only mode:
 [root@agent1 modules]# facter puppetversion
 2.7.19 (Puppet Enterprise 2.7.0)

 and a second agent which I've configured from scratch.
 [root@agent2 modules]# facter operatingsystem operatingsystemrelease
 operatingsystem = CentOS
 operatingsystemrelease = 6.4
 [root@agent2 modules]# facter puppetversion
 3.1.1

 While I know there are issues with running puppet 3.x.x with a 2.7.x 
 version of Enterprise, I only seem to get warnings so far. 
 My main problem is that I cannot see either agent under the Live 
 Management portion of the Enterprise console running on the master. They 
 appear as nodes everywhere else, but I cannot force a single run instance 
 or query packages, users etc from the console.

 Anyone have any ideas?
 Steve




-- 
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] Reassigning value of class declared in templates file

[Cesar Covarrubias]

 I am trying to create a template for all my servers. I have 2 
configurations. An NTP client (which is taken care of in the baseclass 
class. I want to create an override specific for the NTP servers by 
declaring something specific in the node declaration. Something like 
baseclass::ntp:restrict = true,. Or alternatively, how would I change 
one of the already declared variable from baseclass::ntp? 

Does anyone have any ideas host to do this?

This is what I have so far:

templates.pp

class baseclass {
include defaultusers
include sudoers
include issue

class { ntp:
ensure = running,
servers = ['ntpserver1.host.com',
'ntpserver2.host.com',],
autoupdate = false,
}
}


 

nodes.pp

node default {
include baseclass
}

node ntpserver1.host.com inherits default {
some code here to declare new variable in baseclass::ntp
some code here to change existing variable, such as ensure
}

-- 
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't convert Puppet::Util::Log into Integer

[Keith Burdis]

The agent only writes logs under /var/log/puppet if you run it as a service
- for example using:

  $ service puppet once

(Note that due to buffering it may take a few seconds for entries to appear
in puppet.log.)

There are a number of existing issues that could be related to your problem
(#17297, #17887, #19344) but none of these appear to have a fix yet.

Things to try:

1) File ownership on your master:

# chown -R puppet:puppet /etc/puppet /var/lib/puppet

2) Upgrading to 3.1.1.

If that doesn't work then post your puppet.conf.

  - Keith

  - Keith


On 26 March 2013 09:04, Andrei-Florian Staicu andrei.sta...@gmail.comwrote:

 Hi all,

 Could anyone help me at least start debugging this issue?
 All agents have the same error, but i can't find anything on the
 master-side logs. And the agent-side logs are non-existent (/var/log/puppet
 is empty).

 Thanks.

 Versions:
 Master:
 Red Hat Enterprise Linux Server release 6.3
 puppet-server-3.1.0-1.el6.noarch
 puppetdb-1.1.1-1.el6.noarch
 puppetdb-terminus-1.1.1-1.el6.noarch
 puppet-dashboard-1.2.21-1.el6.noarch
 puppet-3.1.0-1.el6.noarch
 Agents:
 Red Hat Enterprise Linux Server release 6.3
 puppet-3.1.0-1.el6.noarch

 [root@somvat121892 ~]# puppet agent --test --verbose --debug
 Debug: Using settings: adding file resource 'lastrunfile':
 'File[/var/lib/puppet/state/last_run_summary.yaml]{:links=:follow,
 :ensure=:file, :backup=false, :mode=644,
 :path=/var/lib/puppet/state/last_run_summary.yaml, :loglevel=:debug}'
 Debug: Failed to load library 'ldap' for feature 'ldap'
 Debug: Puppet::Type::User::ProviderLdap: feature ldap is missing
 Debug: Puppet::Type::User::ProviderPw: file pw does not exist
 Debug: Puppet::Type::User::ProviderUser_role_add: file roleadd does not
 exist
 Debug: Puppet::Type::User::ProviderDirectoryservice: file
 /usr/bin/dsimport does not exist
 Debug: Failed to load library 'ldap' for feature 'ldap'
 Debug: Puppet::Type::Group::ProviderLdap: feature ldap is missing
 Debug: Puppet::Type::Group::ProviderPw: file pw does not exist
 Debug: Puppet::Type::Group::ProviderDirectoryservice: file /usr/bin/dscl
 does not exist
 Debug: Using settings: adding file resource 'logdir':
 'File[/var/log/puppet]{:links=:follow, :group=puppet,
 :ensure=:directory, :backup=false, :owner=puppet, :mode=750,
 :path=/var/log/puppet, :loglevel=:debug}'
 Debug: Using settings: adding file resource 'certdir':
 'File[/var/lib/puppet/ssl/certs]{:links=:follow, :ensure=:directory,
 :backup=false, :owner=puppet, :path=/var/lib/puppet/ssl/certs,
 :loglevel=:debug}'
 Debug: Using settings: adding file resource 'graphdir':
 'File[/var/lib/puppet/state/graphs]{:links=:follow, :ensure=:directory,
 :backup=false, :path=/var/lib/puppet/state/graphs, :loglevel=:debug}'
 Debug: Using settings: adding file resource 'requestdir':
 'File[/var/lib/puppet/ssl/certificate_requests]{:links=:follow,
 :ensure=:directory, :backup=false, :owner=puppet,
 :path=/var/lib/puppet/ssl/certificate_requests, :loglevel=:debug}'
 Debug: Using settings: adding file resource 'clientyamldir':
 'File[/var/lib/puppet/client_yaml]{:links=:follow, :ensure=:directory,
 :backup=false, :mode=750, :path=/var/lib/puppet/client_yaml,
 :loglevel=:debug}'
 Debug: Using settings: adding file resource 'hostprivkey':
 'File[/var/lib/puppet/ssl/private_keys/somvat121892.pem]{:links=:follow,
 :ensure=:file, :backup=false, :owner=puppet, :mode=600,
 :path=/var/lib/puppet/ssl/private_keys/somvat121892.pem,
 :loglevel=:debug}'
 Debug: Using settings: adding file resource 'resourcefile':
 'File[/var/lib/puppet/state/resources.txt]{:links=:follow, :ensure=:file,
 :backup=false, :owner=root, :mode=640,
 :path=/var/lib/puppet/state/resources.txt, :loglevel=:debug}'
 Debug: Using settings: adding file resource 'lastrunreport':
 'File[/var/lib/puppet/state/last_run_report.yaml]{:links=:follow,
 :ensure=:file, :backup=false, :mode=640,
 :path=/var/lib/puppet/state/last_run_report.yaml, :loglevel=:debug}'
 Debug: Using settings: adding file resource 'confdir':
 'File[/etc/puppet]{:links=:follow, :ensure=:directory, :backup=false,
 :path=/etc/puppet, :loglevel=:debug}'
 Debug: Using settings: adding file resource 'ssldir':
 'File[/var/lib/puppet/ssl]{:links=:follow, :ensure=:directory,
 :backup=false, :owner=puppet, :mode=771,
 :path=/var/lib/puppet/ssl, :loglevel=:debug}'
 Debug: Using settings: adding file resource 'privatekeydir':
 'File[/var/lib/puppet/ssl/private_keys]{:links=:follow,
 :ensure=:directory, :backup=false, :owner=puppet, :mode=750,
 :path=/var/lib/puppet/ssl/private_keys, :loglevel=:debug}'
 Debug: Using settings: adding file resource 'client_datadir':
 'File[/var/lib/puppet/client_data]{:links=:follow, :ensure=:directory,
 :backup=false, :mode=750, :path=/var/lib/puppet/client_data,
 :loglevel=:debug}'
 Debug: Using settings: adding file resource 'hostpubkey':
 'File[/var/lib/puppet/ssl/public_keys/somvat121892.pem]{:links=:follow,
 :ensure=:file, :backup=false, :owner=puppet, :mode=644,
 

Solved: [Puppet Users] Can't convert Puppet::Util::Log into Integer

[Andrei-Florian Staicu]

Hello,

It seems that, for one reason or another, two thing happened: the postgres
for puppetdb was dead, and the puppetmaster service was started, even
though it's run from apache. After a bit of cleanup, everything works now.

Thanks for your suggestion, and sorry for the stupid issue.

On Tue, Mar 26, 2013 at 11:43 AM, Keith Burdis ke...@burdis.org wrote:

 The agent only writes logs under /var/log/puppet if you run it as a
 service - for example using:

   $ service puppet once

 (Note that due to buffering it may take a few seconds for entries to
 appear in puppet.log.)

 There are a number of existing issues that could be related to your
 problem (#17297, #17887, #19344) but none of these appear to have a fix yet.

 Things to try:

 1) File ownership on your master:

 # chown -R puppet:puppet /etc/puppet /var/lib/puppet

 2) Upgrading to 3.1.1.

 If that doesn't work then post your puppet.conf.

   - Keith

   - Keith


 On 26 March 2013 09:04, Andrei-Florian Staicu andrei.sta...@gmail.comwrote:

 Hi all,

 Could anyone help me at least start debugging this issue?
 All agents have the same error, but i can't find anything on the
 master-side logs. And the agent-side logs are non-existent (/var/log/puppet
 is empty).

 Thanks.

 Versions:
 Master:
 Red Hat Enterprise Linux Server release 6.3
 puppet-server-3.1.0-1.el6.noarch
 puppetdb-1.1.1-1.el6.noarch
 puppetdb-terminus-1.1.1-1.el6.noarch
 puppet-dashboard-1.2.21-1.el6.noarch
 puppet-3.1.0-1.el6.noarch
 Agents:
 Red Hat Enterprise Linux Server release 6.3
 puppet-3.1.0-1.el6.noarch

 [root@somvat121892 ~]# puppet agent --test --verbose --debug
 Debug: Using settings: adding file resource 'lastrunfile':
 'File[/var/lib/puppet/state/last_run_summary.yaml]{:links=:follow,
 :ensure=:file, :backup=false, :mode=644,
 :path=/var/lib/puppet/state/last_run_summary.yaml, :loglevel=:debug}'
 Debug: Failed to load library 'ldap' for feature 'ldap'
 Debug: Puppet::Type::User::ProviderLdap: feature ldap is missing
 Debug: Puppet::Type::User::ProviderPw: file pw does not exist
 Debug: Puppet::Type::User::ProviderUser_role_add: file roleadd does not
 exist
 Debug: Puppet::Type::User::ProviderDirectoryservice: file
 /usr/bin/dsimport does not exist
 Debug: Failed to load library 'ldap' for feature 'ldap'
 Debug: Puppet::Type::Group::ProviderLdap: feature ldap is missing
 Debug: Puppet::Type::Group::ProviderPw: file pw does not exist
 Debug: Puppet::Type::Group::ProviderDirectoryservice: file /usr/bin/dscl
 does not exist
 Debug: Using settings: adding file resource 'logdir':
 'File[/var/log/puppet]{:links=:follow, :group=puppet,
 :ensure=:directory, :backup=false, :owner=puppet, :mode=750,
 :path=/var/log/puppet, :loglevel=:debug}'
 Debug: Using settings: adding file resource 'certdir':
 'File[/var/lib/puppet/ssl/certs]{:links=:follow, :ensure=:directory,
 :backup=false, :owner=puppet, :path=/var/lib/puppet/ssl/certs,
 :loglevel=:debug}'
 Debug: Using settings: adding file resource 'graphdir':
 'File[/var/lib/puppet/state/graphs]{:links=:follow, :ensure=:directory,
 :backup=false, :path=/var/lib/puppet/state/graphs, :loglevel=:debug}'
 Debug: Using settings: adding file resource 'requestdir':
 'File[/var/lib/puppet/ssl/certificate_requests]{:links=:follow,
 :ensure=:directory, :backup=false, :owner=puppet,
 :path=/var/lib/puppet/ssl/certificate_requests, :loglevel=:debug}'
 Debug: Using settings: adding file resource 'clientyamldir':
 'File[/var/lib/puppet/client_yaml]{:links=:follow, :ensure=:directory,
 :backup=false, :mode=750, :path=/var/lib/puppet/client_yaml,
 :loglevel=:debug}'
 Debug: Using settings: adding file resource 'hostprivkey':
 'File[/var/lib/puppet/ssl/private_keys/somvat121892.pem]{:links=:follow,
 :ensure=:file, :backup=false, :owner=puppet, :mode=600,
 :path=/var/lib/puppet/ssl/private_keys/somvat121892.pem,
 :loglevel=:debug}'
 Debug: Using settings: adding file resource 'resourcefile':
 'File[/var/lib/puppet/state/resources.txt]{:links=:follow, :ensure=:file,
 :backup=false, :owner=root, :mode=640,
 :path=/var/lib/puppet/state/resources.txt, :loglevel=:debug}'
 Debug: Using settings: adding file resource 'lastrunreport':
 'File[/var/lib/puppet/state/last_run_report.yaml]{:links=:follow,
 :ensure=:file, :backup=false, :mode=640,
 :path=/var/lib/puppet/state/last_run_report.yaml, :loglevel=:debug}'
 Debug: Using settings: adding file resource 'confdir':
 'File[/etc/puppet]{:links=:follow, :ensure=:directory, :backup=false,
 :path=/etc/puppet, :loglevel=:debug}'
 Debug: Using settings: adding file resource 'ssldir':
 'File[/var/lib/puppet/ssl]{:links=:follow, :ensure=:directory,
 :backup=false, :owner=puppet, :mode=771,
 :path=/var/lib/puppet/ssl, :loglevel=:debug}'
 Debug: Using settings: adding file resource 'privatekeydir':
 'File[/var/lib/puppet/ssl/private_keys]{:links=:follow,
 :ensure=:directory, :backup=false, :owner=puppet, :mode=750,
 :path=/var/lib/puppet/ssl/private_keys, :loglevel=:debug}'
 Debug: Using settings: adding file 

Re: [Puppet Users] Reassigning value of class declared in templates file

[Peter Meier]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

 Does anyone have any ideas host to do this?

Do not use node inheritance, simply don't - it will hurt you badly at
some point.

It does not work in the same way as class inheritance does. And also
class inheritance should not used that widely (more or less only if
you need to overwrite values for resources, that aren't assignable as
parameter from an external source.

Instead use hiera and design your hierarchy there, then you will have
much more flexibility.

~pete
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlFRldgACgkQbwltcAfKi38a0wCeLmJwcsPkEdHBjK2eO1zehXRD
k2sAoKxQgEy95TR4ExAPjNUVCQiTEQyD
=WmAP
-END PGP SIGNATURE-

-- 
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] Ruby (Rack) application could not be started

[thinkwell]

Hello Ramin. Thanks for your reply. I didn't install rvm, I'm only using 
system ruby.  Regarding the use of gems vs puppet repositories, well, I 
installed Puppet from the official apt repos but I wasn't aware that 
passenger can be installed from there as well. If that's the case, why is 
the documentation http://docs.puppetlabs.com/guides/passenger.htmlso out 
of date? 

I removed all my gems, installed puppetmaster-passenger  ruby-rack from 
apt, and get this output (G):

Setting up ruby-rack (1.3.5-1) ...
Setting up librack-ruby (1.3.5-1) ...
Setting up libapache2-mod-passenger (2.2.11debian-2) ...
Setting up puppetmaster-passenger (3.1.1-1puppetlabs1) ...
Module ssl already enabled
Module headers already enabled
Enabling site puppetmaster.
To activate the new configuration, you need to run:
  service apache2 reload
Syntax error on line 3 of /etc/apache2/sites-enabled/puppetmaster:
Invalid command 'PassengerHighPerformance', perhaps misspelled or defined 
by a module not included in the server configuration
Action 'configtest' failed.
The Apache error log may have more information.
   ...fail!
invoke-rc.d: initscript apache2, action restart failed.
dpkg: error processing puppetmaster-passenger (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 puppetmaster-passenger

*
What is the recommended way to configure Puppet 3.1.1 with Apache!!?*

On Monday, March 25, 2013 11:05:14 PM UTC-4, Ramin K wrote:

 On 3/25/2013 7:04 PM, thinkwell wrote: 
  My puppet master server got torched so I'm rebuilding - ubuntu 12.04.2 
 LTS. 
  
  After fiddling / tweaking / reading docs 
  http://docs.puppetlabs.com/guides/passenger.html for hours now and I 
  am reduced to hair-pulling frustration. 
  
  I'm endeavoring to install 3.1.1 (3.0.2 on the old server) and I'm 
  getting Ruby (Rack) application could not be started 
  http://thinkwelldesigns.com/errors2.html errors. I updated my 
  config.ru http://thinkwelldesigns.com/config.txt file with the 3.1 
  source 
  
 https://github.com/puppetlabs/puppet/blob/master/ext/rack/files/config.ru. 

  
  1. I'm not getting errors in the /var/log/apache2/errors.log as the 
  error message hints I should. 
  2. I tried my certs from my backup. 
  3. I tried recreating server certs, but no change. 
  
  I don't manage my puppet master with puppet, so I came on this discovery 
  very late. For whatever it's worth. 
  
  1. Installed puppet agent on the puppet master. 
  2. Ran puppet agent -t to generate an agent certificate 
  3. Get this error: 
  
  Error: Could not request certificate: Error 500 on SERVER: !DOCTYPE 
  HTML PUBLIC -//IETF//DTD HTML 2.0//EN 
  htmlhead 
  title500 Internal Server Error/title 
  /headbody 
  h1Internal Server Error/h1 
  pThe server encountered an internal error or 
  misconfiguration and was unable to complete 
  your request./p 
  pPlease contact the server administrator, 
[no address given] and inform them of the time the error occurred, 
  and anything you might have done that may have 
  caused the error./p 
  pMore information about this error may be available 
  in the server error log./p 
  hr 
  addressApache/2.2.22 (Ubuntu) Server at puppet Port 8140/address 
  /body/html 
  
  
  here is my gem list which shows rack is installed. 
  *** LOCAL GEMS *** 
  
  activemodel (3.2.13) 
  activerecord (3.2.13) 
  activesupport (3.2.13) 
  arel (3.0.2) 
  builder (3.0.4) 
  daemon_controller (1.1.2) 
  fastthread (1.0.7) 
  i18n (0.6.1) 
  multi_json (1.7.2) 
  passenger (3.0.19) 
  rack (1.5.2) 
  rake (10.0.4) 
  tzinfo (0.3.37) 
  
  Many thanks for your assistance. I'm about maxed out. :-( 

 Your gem listing makes me thing you've installed Ruby inside rvm, is 
 that the case? If so, you'll need to install Puppet within the same Ruby 
 as the one the passenger.so resides in and is configured in 
 /etc/apache2/mod-enabled/passenger.{conf,load} 

 fwiw, you may find it simpler to use the distro packages though I would 
 pull in the official Passenger 3.x repo from apt.brightbox.net as well 
 as apt.puppetlabs.com 

 Ramin 


-- 
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: Unexpected hash's behavior

[jcbollinger]

On Monday, March 25, 2013 9:53:50 AM UTC-5, Andrew E. wrote:

 Hi all.
 I'm newbie.
 Help me, please.
 I write Puppet function
 Piece of code :


 n_if={}
  over_if = arguments[1]
 
  over_if.each do |kk,vv|
   weth={}
 puts kk,vv,weth
 weth = arguments[0]
 weth['in_vlan'] = vv['in_vlan']
 weth['options']['MTU'] = vv['mtu']
 n_if['eth'+ kk.to_s]=weth
 end

 Data gotten from 2 files with Hiera, and passed into arguments[0] and 
 arguments[1] respectively:

 # template of ethernet interfaces
 eth_: 
   method: static
   family: inet
   ip: 
   netmask: 255.255.0.0
   onboot:  true
   options: 
 MTU: 
   in_vlan: 

 # values for include into ethernet interfaces
 eth_values:
  0:
   mtu: 1500
   in_vlan: 15
  1:
   mtu: 9000
   in_vlan: 125


 I expect get hash with keys 'eth0' and 'eth1' as follow:

 eth1methodstaticfamilyinetin_vlan125ipnetmask255.255.0.0onboottrueoptionsMTU9000

 eth0methodstaticfamilyinetin_vlan15ipnetmask255.255.0.0onboottrueoptionsMTU1500
 But I get :

 eth1methodstaticfamilyinetin_vlan125ipnetmask255.255.0.0onboottrueoptionsMTU9000

 eth0methodstaticfamilyinetin_vlan125ipnetmask255.255.0.0onboottrueoptionsMTU9000

  I use:
  Puppet 3.1.1 
  Hiera 1.6.17
  Ruby 1.8.7

 What is my mistake?


I had to rename your variables to follow your code, but it looks like your 
mistake is at this line (translating back):

weth = arguments[0]

That sets variable 'weth' to be a reference to the *same object* that that 
is referenced as arguments[0].  You then proceed to modify that object in 
each iteration of the loop, and assign other references to it to your 
result variable, but in the end it's still only one object.

Here's a version that I think will do what you want:

template = arguments[0]
param_groups = arguments[1]   
results  = {}
   
param_groups.each_pair do |ifc_num, params|
# key difference:
result = template.clone

# no need to clone other objects:
result['in_vlan'] = params['in_vlan']
result['options']['MTU'] = params['mtu']

# especially here:
results['eth' + ifc_num.to_s] = result
end



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 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: Reassigning value of class declared in templates file

[jcbollinger]

On Monday, March 25, 2013 9:14:51 PM UTC-5, Cesar Covarrubias wrote:

 I am trying to create a template for all my servers. I have 2 
 configurations. An NTP client (which is taken care of in the baseclass 
 class. I want to create an override specific for the NTP servers by 
 declaring something specific in the node declaration. Something like 
 baseclass::ntp:restrict = true,. Or alternatively, how would I change 
 one of the already declared variable from baseclass::ntp? 

 Does anyone have any ideas host to do this?

 This is what I have so far:

 templates.pp

 class baseclass {
 include defaultusers
 include sudoers
 include issue

 class { ntp:
 ensure = running,
 servers = ['ntpserver1.host.com',
 'ntpserver2.host.com',],
 autoupdate = false,
 }
 }


  

 nodes.pp

 node default {
 include baseclass
 }

 node ntpserver1.host.com inherits default {
 some code here to declare new variable in baseclass::ntp
 some code here to change existing variable, such as ensure
 }



I don't have any objection to node inheritance, though I do recommend 
keeping node inheritance trees very shallow -- two levels, preferably, or 
three as an absolute, special-case maximum.  You also need to understand 
what it means.  Specifically, it really does mean NODE inheritance.  The 
inheriting node does not get the inherited node's declarations directly, 
but rather the whole node, with its own, separate scope.  The inherited 
node's declarations will be parsed and interpreted independently of any 
inheriting nodes that may be in play.  Inheriting nodes can only add their 
own declarations on top.

There is a syntax for resource parameter override, but it does not work for 
classes (and though there are efforts underway to improve that, it *cannot*work 
for classes under some circumstances).  Your inheriting node therefore 
cannot operate as you hoped.  The best solution is probably for your class 
to draw its data from hiera, so that you can use your hiera hierarchy to 
provide different parameters in the first place based on the nature of the 
client being configured.

Alternatively, the old-school way to do this is to use class inheritance.  
In fact, it is precisely what class inheritance is meant for.  The 
inheritance approach would involve creating a subclass of ntp, say 
ntp::server, which applies appropriate overrides to the parameters of 
resources declared by its parent class.  You then declare the subclass 
(also or instead) to the nodes that should be NTP servers.  Consult the 
language docs for details.


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 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] Running ENC alongside site.pp (node defn)

[iamauser]

Hello,

Is it possible to configure an ENC to provide class definition to a number 
of nodes at the same time where a few other nodes are controlled in the 
site.pp by node 'FQDN' {blah}  for the same puppetmaster ? 

I am wondering once parameters are set for the master to look for an ENC 
based definitions, will it conflict with the site.pp node definitions ? 
For example these two basic parameters for ENC :

node_terminus = exec
external_nodes = /usr/local/bin/enclassifier

Thanks for any suggestion.

--

-- 
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] Running ENC alongside site.pp (node defn)

[Martin Alfke]

Hi.
On 26.03.2013, at 15:44, iamauser wrote:

 Hello,
 
 Is it possible to configure an ENC to provide class definition to a number of 
 nodes at the same time where a few other nodes are controlled in the site.pp 
 by node 'FQDN' {blah}  for the same puppetmaster ? 

ENC and site.pp do not replace each other.
You can use them in parallel at the same time.

Please note that you even may have one node in both (ENC and site.pp).
Puppet will merge all classes and parameters.

 
 I am wondering once parameters are set for the master to look for an ENC 
 based definitions, will it conflict with the site.pp node definitions ? 
 For example these two basic parameters for ENC :
 
 node_terminus = exec
 external_nodes = /usr/local/bin/enclassifier
 
 Thanks for any suggestion.
 
 --
 
 -- 
 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.
  
  

-- 
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] Reference first member of array in manifest

[Willem Bos]

Hi all,

How do I reference the first member in the $ntpd_servers array in the code 
below. Any pointers to the official Puppet (or Ruby?) documentation would 
be much appreciated.

class ntp {

  $ntpd_servers = [ 0.rhel.pool.ntp.org, 1.rhel.pool.ntp.org, 
2.rhel.pool.ntp.org ]

  exec { set_clock:  
subscribe   = File[/etc/ntp.conf],  
command = /sbin/service ntpd stop  /sbin/ntpdate 
FIRST_MEMBER_OF_ARRAY  /sbin/service ntpd start,  
refreshonly = true;  
  }  

}

Regards,
Willem.

-- 
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: Reassigning value of class declared in templates file

[Sergio Jimenez]

Not really sure about it (pretty new in puppet) but ... what about 
parametrized classes? You could define default values for parameters in the 
class or overwrite them when using the class.


sjr.

On Tuesday, March 26, 2013 3:14:51 AM UTC+1, Cesar Covarrubias wrote:

 I am trying to create a template for all my servers. I have 2 
 configurations. An NTP client (which is taken care of in the baseclass 
 class. I want to create an override specific for the NTP servers by 
 declaring something specific in the node declaration. Something like 
 baseclass::ntp:restrict = true,. Or alternatively, how would I change 
 one of the already declared variable from baseclass::ntp? 

 Does anyone have any ideas host to do this?

 This is what I have so far:

 templates.pp

 class baseclass {
 include defaultusers
 include sudoers
 include issue

 class { ntp:
 ensure = running,
 servers = ['ntpserver1.host.com',
 'ntpserver2.host.com',],
 autoupdate = false,
 }
 }


  

 nodes.pp

 node default {
 include baseclass
 }

 node ntpserver1.host.com inherits default {
 some code here to declare new variable in baseclass::ntp
 some code here to change existing variable, such as ensure
 }



-- 
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: Reference first member of array in manifest

[Ellison Marks]

It's just normal subscript notation.

$ntpd_servers[0]

http://docs.puppetlabs.com/puppet/3/reference/lang_datatypes.html#arrays

Just as a note, ntpd has an option, -g I believe, that's used to set the 
time and start the service all at once. I think it's a little preferred 
over ntpdate these days. Not sure what flavor of linux you're running, but 
on centos, that flag is default when run through he init script. It would 
probably be cleaner for you if you could use that flag and then just a 
service resource subscribed to the conf file.

On Tuesday, March 26, 2013 6:01:44 AM UTC-7, Willem Bos wrote:

 Hi all,

 How do I reference the first member in the $ntpd_servers array in the code 
 below. Any pointers to the official Puppet (or Ruby?) documentation would 
 be much appreciated.

 class ntp {

   $ntpd_servers = [ 0.rhel.pool.ntp.org, 1.rhel.pool.ntp.org, 
 2.rhel.pool.ntp.org ]

   exec { set_clock:  
 subscribe   = File[/etc/ntp.conf],  
 command = /sbin/service ntpd stop  /sbin/ntpdate 
 FIRST_MEMBER_OF_ARRAY  /sbin/service ntpd start,  
 refreshonly = true;  
   }  

 }

 Regards,
 Willem.


-- 
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] Ruby (Rack) application could not be started

[Ramin K]

On 3/26/2013 5:59 AM, thinkwell wrote:

Hello Ramin. Thanks for your reply. I didn't install rvm, I'm only using
system ruby.  Regarding the use of gems vs puppet repositories, well, I
installed Puppet from the official apt repos but I wasn't aware that
passenger can be installed from there as well. If that's the case, why
is the documentation
http://docs.puppetlabs.com/guides/passenger.htmlso out of date?

I removed all my gems, installed puppetmaster-passenger  ruby-rack from
apt, and get this output (G):

Setting up ruby-rack (1.3.5-1) ...
Setting up librack-ruby (1.3.5-1) ...
Setting up libapache2-mod-passenger (2.2.11debian-2) ...
Setting up puppetmaster-passenger (3.1.1-1puppetlabs1) ...
Module ssl already enabled
Module headers already enabled
Enabling site puppetmaster.
To activate the new configuration, you need to run:
   service apache2 reload
Syntax error on line 3 of /etc/apache2/sites-enabled/puppetmaster:
Invalid command 'PassengerHighPerformance', perhaps misspelled or
defined by a module not included in the server configuration
Action 'configtest' failed.
The Apache error log may have more information.
...fail!
invoke-rc.d: initscript apache2, action restart failed.
dpkg: error processing puppetmaster-passenger (--configure):
  subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
  puppetmaster-passenger

*
What is the recommended way to configure Puppet 3.1.1 with Apache!!?*


Two things.

You can get Passenger 3.0.19 from here, http://apt.brightbox.net/ though 
you'll need to the key dance outlined here, 
http://wiki.brightbox.co.uk/docs:brightboxaptrepository


I recommend Passenger 3.x for all the reasons here, 
https://ask.puppetlabs.com/question/468/should-i-run-my-puppet-master-under-passenger-30x-or-22x/


However in your current case I'd make sure that the Passenger module has 
been enabled. When Apache thinks a command is invalid it's almost always 
that the module the command is meant to config is not enabled or loaded.


Ramin

--
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] Ruby (Rack) application could not be started

[thinkwell]

Still no luck. Installed from gems, installed from Puppet Apt, installed 
from brightbox. Some thing must be busted for each one. Puppet runs always 
generating scads of errors http://thinkwelldesigns.com/errors2.html.

Is Passenger enabled? I had to create these files manually since the 
packages from brightbox didn't. I guess the settings are correct

Contents of /etc/apache2/mods-available/passenger.conf:
PassengerRoot /usr/lib/ruby/1.8/phusion_passenger
PassengerRuby /usr/bin/ruby1.8

Contents of /etc/apache2/mods-available/passenger.load:
LoadModule passenger_module /usr/lib/apache2/modules/mod_passenger.so

This. Is. Getting. To. Be. One. *S**crming.* Pain. 

Thanks for your help Ramin, but why oh why can't we have up-to-date 
documentation that gives correct step-by-step installation directions?  How 
esoteric does this have to be?

On Tuesday, March 26, 2013 1:35:19 PM UTC-4, Ramin K wrote:


 However in your current case I'd make sure that the Passenger module has 
 been enabled. When Apache thinks a command is invalid it's almost always 
 that the module the command is meant to config is not enabled or loaded. 

 Ramin 


-- 
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] Running ENC alongside site.pp (node defn)

[Peter Brown]

On 27 March 2013 01:02, Martin Alfke tux...@gmail.com wrote:

 Hi.
 On 26.03.2013, at 15:44, iamauser wrote:

 Hello,

 Is it possible to configure an ENC to provide class definition to a number
 of nodes at the same time where a few other nodes are controlled in the
 site.pp by node 'FQDN' {blah}  for the same puppetmaster ?


 ENC and site.pp do not replace each other.
 You can use them in parallel at the same time.

 Please note that you even may have one node in both (ENC and site.pp).
 Puppet will merge all classes and parameters.


It also seems that if you put some nodes in site.pp et al you need a
definition for all of them.
You can get around having to put an entry in for all of your nodes by
putting in an empty default node.





 I am wondering once parameters are set for the master to look for an ENC
 based definitions, will it conflict with the site.pp node definitions ?
 For example these two basic parameters for ENC :

 node_terminus = exec
 external_nodes = /usr/local/bin/enclassifier

 Thanks for any suggestion.

 --

 --
 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.




  --
 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.




-- 
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] Running ENC alongside site.pp (node defn)

[iamauser]

Thanks Pete and Martin. Follow up question.

Let's assume I have 3 nodes (A,B,C), and all of them have some class 
definitions in site.pp, and now, I just want to test my ENC based class 
definitions for only node-A. I have 'node-A.yaml' that has the extra class 
definitions. Should this be enough or I need to put empty class definitions 
for node-B and node-C in the 'yaml' format in order for puppet to work 
properly ?

I could try and learn, but don't want to break the active cluster (bad 
prior experience).








On Tuesday, March 26, 2013 6:37:39 PM UTC-5, Pete wrote:

 On 27 March 2013 01:02, Martin Alfke tux...@gmail.com javascript:wrote:

 Hi.
 On 26.03.2013, at 15:44, iamauser wrote:

 Hello,

 Is it possible to configure an ENC to provide class definition to a 
 number of nodes at the same time where a few other nodes are controlled in 
 the site.pp by node 'FQDN' {blah}  for the same puppetmaster ? 


 ENC and site.pp do not replace each other.
 You can use them in parallel at the same time.

 Please note that you even may have one node in both (ENC and site.pp).
 Puppet will merge all classes and parameters.


 It also seems that if you put some nodes in site.pp et al you need a 
 definition for all of them.
 You can get around having to put an entry in for all of your nodes by 
 putting in an empty default node.

  



 I am wondering once parameters are set for the master to look for an ENC 
 based definitions, will it conflict with the site.pp node definitions ? 
 For example these two basic parameters for ENC :

 node_terminus = exec
 external_nodes = /usr/local/bin/enclassifier

 Thanks for any suggestion.

 --

 -- 
 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...@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.