[Puppet Users] Puppet Forge Repository format
Hi, I am setting up a local forge for some weird political reasons. I came to know that puppetlabs is working on such a feature. But, in the meantime I wanted to try out setting up the repo and use --modules_repository flag in puppet module install: command. For that, I need to mimic the puppet forge repo format (meaning the directory structure of the modules). Can somebody point me to the spfication from puppetlabs for the same. As a base line, I want to know, how a sample http request for a module look like? say for ex, apache module from puppetlabs. Thank you in advance. -- Prabhakhar K -- 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/-/e5P5pRqzwnoJ. 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] tcl dependency in RHEL6 installing facter, puppet
Hi- I am running RedHat Enterprise version 6. Linux luke 2.6.32-131.17.1.el6.x86_64 #1 SMP Thu Sep 29 10:24:25 EDT 2011 x86_64 x86_64 x86_64 GNU/Linux I'm trying to install puppet. I added the puppetlabs repos using this RPM: http://yum.puppetlabs.com/el/6/products/x86_64/puppetlabs-release-6-6.noarch.rpm When I try to install facter (or puppet), it tries to install ruby and ruby-libs , and fails because it can't find the version of tcl it needs: yum install facter Loaded plugins: product-id, refresh-packagekit, rhnplugin, subscription-manager, versionlock Updating certificate-based repositories. Unable to read consumer identity Setting up Install Process Resolving Dependencies -- Running transaction check --- Package facter.x86_64 1:1.6.14-1.el5 will be installed -- Processing Dependency: ruby = 1.8.5 for package: 1:facter-1.6.14-1.el5.x86_64 -- Processing Dependency: ruby(abi) = 1.8 for package: 1:facter-1.6.14-1.el5.x86_64 -- Processing Dependency: /usr/bin/ruby for package: 1:facter-1.6.14-1.el5.x86_64 -- Running transaction check --- Package ruby.x86_64 0:1.8.7.370-1.el5 will be installed --- Package ruby-libs.x86_64 0:1.8.7.370-1.el5 will be installed -- Processing Dependency: libtk8.4.so()(64bit) for package: ruby-libs-1.8.7.370-1.el5.x86_64 -- Processing Dependency: libtcl8.4.so()(64bit) for package: ruby-libs-1.8.7.370-1.el5.x86_64 -- Processing Dependency: libssl.so.6()(64bit) for package: ruby-libs-1.8.7.370-1.el5.x86_64 -- Processing Dependency: libtermcap.so.2()(64bit) for package: ruby-libs-1.8.7.370-1.el5.x86_64 -- Processing Dependency: libdb-4.3.so()(64bit) for package: ruby-libs-1.8.7.370-1.el5.x86_64 -- Processing Dependency: libcrypto.so.6()(64bit) for package: ruby-libs-1.8.7.370-1.el5.x86_64 -- Running transaction check --- Package compat-db43.x86_64 0:4.3.29-15.el6 will be installed --- Package compat-libtermcap.x86_64 0:2.0.8-49.el6 will be installed --- Package openssl098e.x86_64 0:0.9.8e-17.el6_2.2 will be installed --- Package ruby-libs.x86_64 0:1.8.7.370-1.el5 will be installed -- Processing Dependency: libtk8.4.so()(64bit) for package: ruby-libs-1.8.7.370-1.el5.x86_64 -- Processing Dependency: libtcl8.4.so()(64bit) for package: ruby-libs-1.8.7.370-1.el5.x86_64 -- Finished Dependency Resolution Error: Package: ruby-libs-1.8.7.370-1.el5.x86_64 (puppetlabs-deps) Requires: libtcl8.4.so()(64bit) Error: Package: ruby-libs-1.8.7.370-1.el5.x86_64 (puppetlabs-deps) Requires: libtk8.4.so()(64bit) You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest This has worked in the past on my RHEL5 machines, where the version of TCL is 8.4.13, but the version on RHEL6 is 8.5.7 I see folks on this list using RHEL6- I was wondering how you got past this? Thanks for any input, Mark -- 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/-/-WCg-AtVfNIJ. 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: Fact precedence in modules
Sorry guys. Forgot about adding some info. The test.rb file (which got served by newmod module) in /var/lib/puppet/lib/facter is run and test.rb file in /var/lib/puppet/lib/facter/test is never run. Why? Also, I didn't understand the meaning of number of confines for that fact. If I don't add any confine statements in ruby code, how is this confines thing calculated? On 11/06/2012 01:02 PM, Abhijeet R wrote: Hi guys, I am trying to understand fact precedence and pluginsync. Documentation says, by default, the weight of a fact is the number of confines for that fact, so that more specific facts are evaluated first. 1. I made a module core which adds a facter test and has filename test.rb. (in location modules/core/lib/facter/test/test.rb). Note that facter is in test folder. 2. This above module core is included in all nodes. 3. Another module newmod also adds the facter test has the filename test.rb but this time, location is modules/core/lib/facter/test.rb. In all the nodes, first include core comes and then include newmod comes. When I see the facter value, the newmod's file is run. Why? Pluginsync syncs both files and one exists in root of /var/lib/puppet/lib/facter while the other exists in /var/lib/puppet/lib/facter/test folder. Running strace reveals that facter command opens both test.rbs but somehow selects the correct one. The behaviour that's happening is expected but I am trying to understand why is this happening. Please note that nowhere in the code of adding facts, I am using has_weight. -- Cheers, Abhijeet R http://blog.abhijeetr.com -- 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] How to setup puppet 0.25.5-1 client in UBUNTU12.04 64 bit
How to setup puppet 0.25.5-1 in ubuntu12.04, the normal updates taking me to higher version of puppet client. -- 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/-/AK3o7PW2HwEJ. 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: Puppet Meetup Australia (Melbourne, Sydney, Brisbane)
On Monday, 5 November 2012 09:58:42 UTC+11, Stephen Johnson wrote: Hi I currently in Australia, as im the instructor on the Puppet Fundamentals * courses in Melbourne, Sydney and Brisbane and just wondered if anyone fancied meeting up and talking about puppet, hiera, puppetdb, devops etc etc. As i dont live here any feedback on locations would help, if not ill randomly pick on closer to the time. Sydney Thursday 15/11/2012 5.30pm (Location to be decided) Details for Sydney meetup http://www.meetup.com/Sydney-Puppet-Masters/events/90175502/ See you there ! -- Mick -- 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/-/HpdzBGbkfs4J. 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] Puppet in SW MO
i am currently located in southwest MIssouri. Springfield, MO to be precise. I'd like to get some sort of Puppet user group / meetup going in the area, but so far have not been able to locate anyone. I had looked on some of the Springfield based DevOps and related LInkedIn groups, but got no response, so I figured I'd ask here. Anyone in the SW MO area and interested in something like this? Thanks -- 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/-/k0zz4l5ahC4J. 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] Puppet JBoss
Hi, I have a big problem with Puppet and JBoss. In jboss/server/ directory, there are several instances. And instances started, +10 files are presents. Puppetrun takes several hours to complete his cycle. tmp/ directory is ignore in file resource (ignore = [ 'tmp', 'work', 'data', '.git', '*puppet-bak', '*class', '*tld', '*jsp' ],) but this directory is still processed. I don't understand. How to reduced execution time ? Thx. -- 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/-/Z_sNqoE6xDcJ. 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: tcl dependency in RHEL6 installing facter, puppet
On Monday, November 5, 2012 2:10:58 PM UTC-6, msuho wrote: Hi- I am running RedHat Enterprise version 6. Linux luke 2.6.32-131.17.1.el6.x86_64 #1 SMP Thu Sep 29 10:24:25 EDT 2011 x86_64 x86_64 x86_64 GNU/Linux I'm trying to install puppet. I added the puppetlabs repos using this RPM: http://yum.puppetlabs.com/el/6/products/x86_64/puppetlabs-release-6-6.noarch.rpm When I try to install facter (or puppet), it tries to install ruby and ruby-libs , and fails because it can't find the version of tcl it needs: yum install facter Loaded plugins: product-id, refresh-packagekit, rhnplugin, subscription-manager, versionlock Updating certificate-based repositories. Unable to read consumer identity Setting up Install Process Resolving Dependencies -- Running transaction check --- Package facter.x86_64 1:1.6.14-1.el5 will be installed -- Processing Dependency: ruby = 1.8.5 for package: 1:facter-1.6.14-1.el5.x86_64 -- Processing Dependency: ruby(abi) = 1.8 for package: 1:facter-1.6.14-1.el5.x86_64 -- Processing Dependency: /usr/bin/ruby for package: 1:facter-1.6.14-1.el5.x86_64 -- Running transaction check --- Package ruby.x86_64 0:1.8.7.370-1.el5 will be installed --- Package ruby-libs.x86_64 0:1.8.7.370-1.el5 will be installed -- Processing Dependency: libtk8.4.so()(64bit) for package: ruby-libs-1.8.7.370-1.el5.x86_64 -- Processing Dependency: libtcl8.4.so()(64bit) for package: ruby-libs-1.8.7.370-1.el5.x86_64 -- Processing Dependency: libssl.so.6()(64bit) for package: ruby-libs-1.8.7.370-1.el5.x86_64 -- Processing Dependency: libtermcap.so.2()(64bit) for package: ruby-libs-1.8.7.370-1.el5.x86_64 -- Processing Dependency: libdb-4.3.so()(64bit) for package: ruby-libs-1.8.7.370-1.el5.x86_64 -- Processing Dependency: libcrypto.so.6()(64bit) for package: ruby-libs-1.8.7.370-1.el5.x86_64 -- Running transaction check --- Package compat-db43.x86_64 0:4.3.29-15.el6 will be installed --- Package compat-libtermcap.x86_64 0:2.0.8-49.el6 will be installed --- Package openssl098e.x86_64 0:0.9.8e-17.el6_2.2 will be installed --- Package ruby-libs.x86_64 0:1.8.7.370-1.el5 will be installed -- Processing Dependency: libtk8.4.so()(64bit) for package: ruby-libs-1.8.7.370-1.el5.x86_64 -- Processing Dependency: libtcl8.4.so()(64bit) for package: ruby-libs-1.8.7.370-1.el5.x86_64 -- Finished Dependency Resolution Error: Package: ruby-libs-1.8.7.370-1.el5.x86_64 (puppetlabs-deps) Requires: libtcl8.4.so()(64bit) Error: Package: ruby-libs-1.8.7.370-1.el5.x86_64 (puppetlabs-deps) Requires: libtk8.4.so()(64bit) You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest This has worked in the past on my RHEL5 machines, where the version of TCL is 8.4.13, but the version on RHEL6 is 8.5.7 I see folks on this list using RHEL6- I was wondering how you got past this? It's not them, it's you. Something is screwed up with your repository configuration. It looks like you're trying to install a mix of RHEL 5 and RHEL 6 packages on your system. Also, probably some third-party or homebrew, since I see a Ruby 1.8.7...el5, and RHEL 5's official Ruby is pinned at version 1.8.5. In direct response to your question, the EL6 ruby-libs package has no dependency on *any* version of Tcl or tk. John -- 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/-/hu8fPrhrHwMJ. 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: Run Exec without notifying Puppet as a change
On Monday, November 5, 2012 3:03:57 PM UTC-6, Thomas Biddle wrote: I just switched from an in-house APT module to the Puppetlabs one thinking that it may solve this, but after looking at the code (And installing to confirm) it did not. Seeing Puppet be notified of a change just when `apt-get update` is run is a bit annoying to me. I was wondering if there was a way to avoid notifying Puppet of a change when an Exec command is run? (Or if there's another way we can run this) It *is* a change. The system goes from a state of 'apt-get update' not having been run (in some given time frame) to a state in which it has been run. That's the way it works for Execs. In general, what you can do is use one or more of the Exec's 'unless', 'onlyif', or 'creates' properties to define whether the Exec needs to run at all, and / or you can set refreshonly = true so that it has to receive an event from some other resource before it will run. You can also set a schedule on it to reduce the frequency at which it is applied. You will have to judge for yourself whether any of those alternatives is applicable to your particular situation. John -- 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/-/gkflyoexFYoJ. 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] How to setup puppet 0.25.5-1 client in UBUNTU12.04 64 bit
On 06/11/12 12:24, WhiteB wrote: How to setup puppet 0.25.5-1 in ubuntu12.04, the normal updates taking me to higher version of puppet client. Puppet 0.25 has not been supported for a long time now and its use is not recommended. You will not find official packages for this very old version, certainly not in the Ubuntu repositories, but you can download the sources for old versions here: http://downloads.puppetlabs.com/puppet/ I have no idea, however, if or how well they will work on Ubuntu 12.04. Andreas signature.asc Description: OpenPGP digital signature
Re: [Puppet Users] How do you manage SSL/TLS certificates and private keys?
That would work if I didn't want to have everything under version
control. I guess the only option for storing certs/keys I have is hiera-gpg
with yaml or some other backend.
I am still trying to figure out what should distribute certs/keys - is it a
separate module or the app module itself? What would be the best practice
in this case?
Thanks
On Tuesday, 6 November 2012 15:28:39 UTC, Matt Zagrabelny wrote:
On Tue, Nov 6, 2012 at 7:29 AM, Vaidas Jablonskis
jablo...@gmail.comjavascript:
wrote:
Hi People,
I would like some insight from you on how to easily manage SSL
certs/keys.
My puppet infrastructure is pretty straight forward:
puppet3+puppetdb+hiera+hiera-gpg.
I am in the process of writing tons of modules, which are pretty general
modules with no hardcoded dependencies between them. As I am going
forward
with building modules and stuff I came across an issue how to manage SSL
certs.
Let me give you an example scenario:
I have a node named node.example.com which gets some apps configured
by
puppet by 3 different modules, let's call them app1, app2 and app3.
Those
application require SSL certificates to function properly. The CN of the
cert needs to reflect the hostname of the node.
What options do I have here? From my opinion I could:
1. Use hiera text blocks and store certs/keys in hiera/hiera-gpg in a
variable something like: ssl_cert_node.example.com and
ssl_key_node.example.com and then reference this variable inside a
module
using variables so nothing is hardcoded.
2. Build an SSL module which would distribute certs/keys taken from
hiera/hiera-gpg.
Any other ideas? I do not want to use module dependencies and I hate
hardcoding stuff into modules.
I use the private area in the puppet file server.
$ cat /etc/puppet/fileserver.conf
[private]
path /etc/puppet/private/%h
allow *
For example:
file { /etc/ssh/ssh_host_dsa_key:
mode= 0600,
source = puppet:///private/etc/ssh/ssh_host_dsa_key,
require = Class[ssh::install],
notify = Service[ssh],
}
-mz
--
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/-/bY_e4y4_qYcJ.
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: Puppet NetApp Network device management...
Ok, quick update...
I've not managed to get past the 'Undefined method' error despite my best
efforts today...
Any ideas on where I could be going wrong?
Cheers
Gavin
On Monday, 5 November 2012 17:46:07 UTC, Gavin Williams wrote:
Looks like the below error was caused by some locally cached code that
hadn't been updated by my Git pull :s
Resolved that, and now am getting the following:
$ sudo puppet device -v
Info: starting applying configuration to actint-star-nactl01 at
actint-star-nactl01
Warning: Local environment: production doesn't match server specified
node environment development, switching agent to development.
Info: Retrieving plugin
/File[/var/lib/puppet/devices/actint-star-nactl01/lib/puppet]/mode: mode
changed '0775' to '0755'
/File[/var/lib/puppet/devices/actint-star-nactl01/lib/puppet/provider]/mode:
mode changed '0775' to '0755'
/File[/var/lib/puppet/devices/actint-star-nactl01/lib/puppet/provider/netapp.rb]/content:
content changed '{md5}399796914d8aeb68387455de5b24f735' to
'{md5}3be2121ab99116c4bc89db21d5d4b54b'
/File[/var/lib/puppet/devices/actint-star-nactl01/lib/puppet/provider/netapp_volume/netapp_volume.rb]/content:
content changed '{md5}46b2a0004e0245c577974e7a645e08f7' to
'{md5}1b06628868826a8ea64744a7ae8ec8da'
/File[/var/lib/puppet/devices/actint-star-nactl01/lib/puppet/type]/mode:
mode changed '0775' to '0755'
/File[/var/lib/puppet/devices/actint-star-nactl01/lib/puppet/type/netapp_volume.rb]/content:
content changed '{md5}ebe14c73783c97063d9b6ae0bc791896' to
'{md5}2fb244482c7d760e6cc132f104be619d'
/File[/var/lib/puppet/devices/actint-star-nactl01/lib/puppet/util/network_device/netapp/facts.rb]/content:
content changed '{md5}c7e59e79e19486cba9ae7e5314b2a061' to
'{md5}b0c912dc663d5251219bbad895455834'
/File[/var/lib/puppet/devices/actint-star-nactl01/lib/puppet/util/network_device/netapp/device.rb]/content:
content changed '{md5}7354a748bd41582fcf76bf2643098fcd' to
'{md5}9d2e26f97c7ea6ea16177acb8df85714'
/File[/var/lib/puppet/devices/actint-star-nactl01/lib/puppet/util/network_device/netapp/NaServer.rb]/content:
content changed '{md5}cd815964f9a2dfe757f5365a848b80d5' to
'{md5}63f12abed9d1145b6d326c9fc06eb0c0'
Info: Caching catalog for actint-star-nactl01
Info: Applying configuration version '1352132516'
Error:
/Stage[main]//Node[actint-star-nactl01]/Netapp_volume[v_puppet_test]: Could
not evaluate: undefined method `transport' for
#Puppet::Util::NetworkDevice::Netapp::Device:0x7ff3142c80f8
Finished catalog run in 0.11 seconds
If I change *provider/netapp_volume/netapp_volume.rb *as follows*:*
/File[/var/lib/puppet/lib/puppet/provider/netapp_volume/netapp_volume.rb]/content:
--- /var/lib/puppet/lib/puppet/provider/netapp_volume/netapp_volume.rb
2012-11-05 17:26:56.257616498 +
+++ /tmp/puppet-file20121105-8521-10tepn6-0 2012-11-05
17:40:16.440612301 +
@@ -19,7 +19,7 @@
def exists?
Puppet.debug(Puppet::Provider::Netapp_volume: checking existance of
Netapp Volume #{resource[:name]})
-transport.invoke(volume-list-info).include?(resource[:name])
+@transport.invoke(volume-list-info).include?(resource[:name])
end
I get:
Info: starting applying configuration to actint-star-nactl01 at
actint-star-nactl01
Warning: Local environment: production doesn't match server specified
node environment development, switching agent to development.
Info: Retrieving plugin
/File[/var/lib/puppet/devices/actint-star-nactl01/lib/puppet/provider/netapp_volume/netapp_volume.rb]/content:
content changed '{md5}1b06628868826a8ea64744a7ae8ec8da' to
'{md5}feb535835cefd0921c8be5d0af6e11f2'
Info: Caching catalog for actint-star-nactl01
Info: Applying configuration version '1352132516'
Error:
/Stage[main]//Node[actint-star-nactl01]/Netapp_volume[v_puppet_test]: Could
not evaluate: undefined method `invoke' for nil:NilClass
Finished catalog run in 0.20 seconds
So not sure why it's not working either way...
Any ideas???
Cheers
Gavin
On Monday, 5 November 2012 16:44:15 UTC, Gavin Williams wrote:
Ok, moving on then...
I've created a 'netapp_volume' type and provider, and am trying to test
it against one of the existing NetApp device nodes:
*manifests/site.pp* contains:
node 'actint-star-nactl01' {
# Test NetApp volume provider
netapp_volume { 'v_puppet_test':
ensure = present,
}
}
When running *'puppet device -v'*, I get:
$ sudo puppet device -v
Info: starting applying configuration to actint-star-nactl01 at
actint-star-nactl01
Warning: Local environment: production doesn't match server specified
node environment development, switching agent to development.
Info: Retrieving plugin
/File[/var/lib/puppet/devices/actint-star-nactl01/lib/puppet/type/netapp_volume.rb]/content:
content changed '{md5}2f3e20a3878f9ed94a5fffc4a9811ef7' to
'{md5}ebe14c73783c97063d9b6ae0bc791896'
[Puppet Users] puppet failing to run
I am getting this error after installing puppet with gem $ gem install puppet Fetching: facter-1.6.14.gem (100%) Fetching: puppet-3.0.1.gem (100%) Successfully installed facter-1.6.14 Successfully installed puppet-3.0.1 2 gems installed Installing ri documentation for facter-1.6.14... Installing ri documentation for puppet-3.0.1... Installing RDoc documentation for facter-1.6.14... Installing RDoc documentation for puppet-3.0.1... Could not find main page README.md Could not find main page README.md Could not find main page README.md Could not find main page README.md $ puppet --version Error: Could not intialize global default settings: Error converting value for param 'factpath': Could not find value for $confdir google search found this link and that is already fixed for this version https://github.com/puppetlabs/puppet/pull/750 Please advise. -- Asif Iqbal PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? -- 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] Hiera autolookup for defined types
Hello,
since Puppet 3 hiera is doing auto variable lookup for classes, which in my
view makes the code much clearer simply because we can use
include foo
instead of
class { 'foo':
param1 = value,
param2 = value,
}
However, AFAIK there is no such feature as auto looking parameters for defined
type.
A common case is multiple vhost in Apache.
Even though you can have apache installed as simply as include apache, you
still have a lot of define (one per vhost), possibly each with different
parameters.
Would it be possible to have hiera looking up for a hash of parameters.
Something like this in hiera:
---
apache_vhost:
website1:
web_param1: 'foo'
web_param2: 'bar'
website2:
web_param1: 'another_foor'
web_param2: 'another_bar'
And in the manifest, this would be invoked as simply as:
node test {
include apache
apache_vhost { 'website1': }
apache_vhost { 'website2': }
}
Any ideas on this ? Any plans of implementation ?
Thanks
--
Bruno
--
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: puppet failing to run
On Tue, Nov 6, 2012 at 11:31 AM, Asif Iqbal vad...@gmail.com wrote: I am getting this error after installing puppet with gem $ gem install puppet Fetching: facter-1.6.14.gem (100%) Fetching: puppet-3.0.1.gem (100%) Successfully installed facter-1.6.14 Successfully installed puppet-3.0.1 2 gems installed Installing ri documentation for facter-1.6.14... Installing ri documentation for puppet-3.0.1... Installing RDoc documentation for facter-1.6.14... Installing RDoc documentation for puppet-3.0.1... Could not find main page README.md Could not find main page README.md Could not find main page README.md Could not find main page README.md $ puppet --version Error: Could not intialize global default settings: Error converting value for param 'factpath': Could not find value for $confdir google search found this link and that is already fixed for this version https://github.com/puppetlabs/puppet/pull/750 Please advise. I am on Ubuntu 12.04.1 LTS 64bit server and gem version is 1.8.24 -- Asif Iqbal PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? -- Asif Iqbal PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? -- 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] Newbie: puppetlabs-apache, modules and proxying
Hi,
I'm quite new to puppet but feel like making some progress. :)
Today I started using the puppetlabs-apache module.
Two questions arose from that. I tried understanding by looking at the
module's code, but too much of that still looks like advanced wizardry to
me.
I hope this list is the right place to post my questions.
1) How can I enable custom modules?
I try to enable proxy_ajp.
Creating '/etc/httpd/mod.d/proxy_ajp.load ' manually and puppet will remove
the module, so I assume puppet knows about the module
notice: /A2mod[proxy_ajp]/ensure: current_value present, should be absent
(noop)
How to tell puppet to actually activate the module?
I've tried this in my node configuration:
class {'apache::mod::proxy_ajp': }
as the same semantic worked for the proxy_http module, but now puppet
complains:
Error 400 on SERVER: Puppet::Parser::AST::Resource failed with error
ArgumentError: Could not find declared class apache::mod::proxy_ajp
2) How to use a different proxy.conf template?
In this module:
puppetlabs-apache / manifests / mod / proxy.pp
class apache::mod::proxy (
$proxy_requests = Off
) {
apache::mod { 'proxy': }
# Template uses $proxy_requests
file { ${apache::params::vdir}/proxy.conf:
ensure = present,
content = template('apache/mod/proxy.conf.erb'),
}
}
there's a reference to the template proxy.conf.erb which is located in the
modules folder. How can I override this in my node config (or anywhere
else)? I want to use a template from a different location, because I
believe the module should not be modified, just used.
Thanks for pointing me in the right direction.
Hugo
--
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/-/Sd4v2NGth7kJ.
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: Puppet NetApp Network device management...
Scratch my last, had a bit of a eureka moment...
Added ':transport: to the attr_accessor against device.rb, and it started
working again...
However now failing elsewhere...
Have got the following against a relevant node:
# Test NetApp volume provider
netapp_volume { 'v_puppet_test':
ensure = present,
initsize = 1g,
aggr = aggr01,
spaceresv = none,
}
The run is failing with:
Error: Could not retrieve catalog from remote server: Error 400 on
SERVER: Invalid parameter aggr at /etc/puppet/manifests/site.pp:30 on node
actint-star-nactl01
Error: Could not set 'present' on ensure: undefined method `result_reason'
for #NaElement:0x7ffb9cb5d160 at 27:/etc/puppet/manifests/site.pp
Error: Could not set 'present' on ensure: undefined method `result_reason'
for #NaElement:0x7ffb9cb5d160 at 27:/etc/puppet/manifests/site.pp
Wrapped exception:
undefined method `result_reason' for #NaElement:0x7ffb9cb5d160
Error:
/Stage[main]//Node[actint-star-nactl01]/Netapp_volume[v_puppet_test]/ensure:
change from absent to present failed: Could not set 'present' on ensure:
undefined method `result_reason' for #NaElement:0x7ffb9cb5d160 at
27:/etc/puppet/manifests/site.pp
Got some debug logging, which is giving:
^[[0;36mDebug^[[0m: Puppet::Provider::Netapp_volume: checking existance of
Netapp Volume v_puppet_test
^[[0;36mDebug^[[0m: Puppet::Provider::Netapp_volume: Vol Info: results
status=failed reason=No volume named 'v_puppet_test' exists
errno=13040/results
^[[0;36mDebug^[[0m: Puppet::Provider::Netapp_volume: Volume doesn't
currently exist.
^[[0;36mDebug^[[0m: Puppet::Provider::Netapp_volume: creating Netapp
Volume v_puppet_test of initial size 1g
So I can see that the provider exists? is working correctly, and it's
trying to fire the create def...
The type is defined correctly afaik:
Puppet::Type.newtype(:netapp_volume) do
@doc = Manage Netapp Volume creation, modification and deletion.
apply_to_device
ensurable do
desc Netapp Volume resource state. Valid values are: present, absent.
defaultto(:present)
newvalue(:present) do
provider.create
end
newvalue(:absent) do
provider.destroy
end
end
newparam(:name) do
desc The volume name.
isnamevar
#newvalues(/^[[:alpha:][:digit:]\.]+$/)
end
newparam(:initsize) do
desc The initial volume size.
defaultto 1g
end
newparam(:aggr) do
desc The aggregate this volume should be created in.
end
newparam(:spaceresv) do
desc The space reservation mode.
end
end
Latest code in Git...
Any ideas?
Cheers
Gavin
On Monday, 5 November 2012 17:46:07 UTC, Gavin Williams wrote:
Looks like the below error was caused by some locally cached code that
hadn't been updated by my Git pull :s
Resolved that, and now am getting the following:
$ sudo puppet device -v
Info: starting applying configuration to actint-star-nactl01 at
actint-star-nactl01
Warning: Local environment: production doesn't match server specified
node environment development, switching agent to development.
Info: Retrieving plugin
/File[/var/lib/puppet/devices/actint-star-nactl01/lib/puppet]/mode: mode
changed '0775' to '0755'
/File[/var/lib/puppet/devices/actint-star-nactl01/lib/puppet/provider]/mode:
mode changed '0775' to '0755'
/File[/var/lib/puppet/devices/actint-star-nactl01/lib/puppet/provider/netapp.rb]/content:
content changed '{md5}399796914d8aeb68387455de5b24f735' to
'{md5}3be2121ab99116c4bc89db21d5d4b54b'
/File[/var/lib/puppet/devices/actint-star-nactl01/lib/puppet/provider/netapp_volume/netapp_volume.rb]/content:
content changed '{md5}46b2a0004e0245c577974e7a645e08f7' to
'{md5}1b06628868826a8ea64744a7ae8ec8da'
/File[/var/lib/puppet/devices/actint-star-nactl01/lib/puppet/type]/mode:
mode changed '0775' to '0755'
/File[/var/lib/puppet/devices/actint-star-nactl01/lib/puppet/type/netapp_volume.rb]/content:
content changed '{md5}ebe14c73783c97063d9b6ae0bc791896' to
'{md5}2fb244482c7d760e6cc132f104be619d'
/File[/var/lib/puppet/devices/actint-star-nactl01/lib/puppet/util/network_device/netapp/facts.rb]/content:
content changed '{md5}c7e59e79e19486cba9ae7e5314b2a061' to
'{md5}b0c912dc663d5251219bbad895455834'
/File[/var/lib/puppet/devices/actint-star-nactl01/lib/puppet/util/network_device/netapp/device.rb]/content:
content changed '{md5}7354a748bd41582fcf76bf2643098fcd' to
'{md5}9d2e26f97c7ea6ea16177acb8df85714'
/File[/var/lib/puppet/devices/actint-star-nactl01/lib/puppet/util/network_device/netapp/NaServer.rb]/content:
content changed '{md5}cd815964f9a2dfe757f5365a848b80d5' to
'{md5}63f12abed9d1145b6d326c9fc06eb0c0'
Info: Caching catalog for actint-star-nactl01
Info: Applying configuration version '1352132516'
Error:
Re: [Puppet Users] Puppet JBoss
Budicom,
One thing I might suggest is not to put the entire JBoss directory in
puppet and realize it as a file resource. As gross as it is for a
former employer I used the zip deployment and extracted the zip file.
Disclaimer: No syntax checking, no validation YMMV, for example only. :)
file { $somepath/jboss-$version.zip:
ensure = 'present',
source = $somewhere,
}
exec { unzip-jboss-$version.zip:
command = unzip $somepath/jboss-$version.zip -q -d $someotherdir,
requires = [ File[$somepath/jboss-$version.zip, Package['zip'] ],
}
exec { backup-jboss-$version-profiles:
command = mv $someotherdir/jboss-$version/server/
$someotherdir/jboss-$version/server.orig,
creates = $someotherdir/jboss-$version/server.orig,
requires = unzip-jboss-$version.zip,
}
class jboss::instance (
installdir = undef,
profile = 'default',
) {
exec { copy-jboss-profile-$name:
command = cp $installdir/jboss-$version/server.orig/$profile
$installdir/jboss-$version/server/$name
creates = $installdir/jboss-$version/server/$name
}
# setup an init script
# configure other instance properties w/ augeas/files
}
Campt to camp has a great archive installer you could cannibalize or
perhaps use in its entirety. It didn't quite work in my last
situation but perhaps it would work for you.
https://github.com/camptocamp/puppet-archive
Regards,
-Alan
On Tue, Nov 6, 2012 at 7:30 AM, Budicom nduter...@geodisbm.com wrote:
Hi,
I have a big problem with Puppet and JBoss.
In jboss/server/ directory, there are several instances. And instances
started, +10 files are presents.
Puppetrun takes several hours to complete his cycle.
tmp/ directory is ignore in file resource (ignore = [ 'tmp', 'work',
'data', '.git', '*puppet-bak', '*class', '*tld', '*jsp' ],) but this
directory is still processed.
I don't understand.
How to reduced execution time ?
Thx.
--
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/-/Z_sNqoE6xDcJ.
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.
--
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.
Re: [Puppet Users] Could not parse for environment production: Syntax error at '{'; expected '}' at
Hi Havary, Sounds like this might be the same issue as: https://groups.google.com/d/topic/puppet-users/3d_cGLwdzWo/discussion Did you install the puppetmaster, and then downgrade to an earlier version? If so, I'd recommend clearing everything in vendor_ruby/puppet, and then re-installing. Josh On Tue, Oct 30, 2012 at 11:33 AM, Havary havary.cam...@geofusion.com.brwrote: Calvin Walton, thank you! Do you recomend a book for reading and learning? I will need some help again, maybe I made an other mistake. I made the correction in my node.pp. but now I m reciving this error msg: *info: Retrieving plugin err: Could not retrieve catalog from remote server: Could not intern from pson: Could not autoload package: Could not autoload /usr/lib/ruby/vendor_ruby/puppet/provider/package/windows.rb: no such file to load -- windows/error warning: Not using cache on failed catalog err: Could not retrieve catalog; skipping run* I try googled but no success, it is stranger but there is no reason for windows.rb problem. I m using a linux server and a linux client for puppet. Thanks! -- 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/-/z7l9CLD9FC8J. 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. -- Josh Cooper Developer, Puppet Labs -- 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.
Re: [Puppet Users] Re: puppet failing to run
Did you have a version of Puppet on this system previously? This definitely seems like a bug, but it seems like one that only manifests if there's some other copy of Puppet that is also being loaded along with the version you expect. -Jeff On Tue, Nov 6, 2012 at 9:20 AM, Asif Iqbal vad...@gmail.com wrote: On Tue, Nov 6, 2012 at 11:31 AM, Asif Iqbal vad...@gmail.com wrote: I am getting this error after installing puppet with gem $ gem install puppet Fetching: facter-1.6.14.gem (100%) Fetching: puppet-3.0.1.gem (100%) Successfully installed facter-1.6.14 Successfully installed puppet-3.0.1 2 gems installed Installing ri documentation for facter-1.6.14... Installing ri documentation for puppet-3.0.1... Installing RDoc documentation for facter-1.6.14... Installing RDoc documentation for puppet-3.0.1... Could not find main page README.md Could not find main page README.md Could not find main page README.md Could not find main page README.md $ puppet --version Error: Could not intialize global default settings: Error converting value for param 'factpath': Could not find value for $confdir google search found this link and that is already fixed for this version https://github.com/puppetlabs/puppet/pull/750 Please advise. I am on Ubuntu 12.04.1 LTS 64bit server and gem version is 1.8.24 -- Asif Iqbal PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? -- Asif Iqbal PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? -- 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. -- 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: 2 package resources for the same package installation in two differents modules caused errors
What I normally do is I create a virtual @package resource which installs
php5 for example within say apache class and then I realize the virtual
resource within the same apache class.
Please, if you intend to write generic and reusable modules so other people
can use, STOP putting hardcoded dependencies in your modules.
Either write in documentation that it depends on an abstract resource, for
instance a mysql database and make it configurable so you can pass db_name,
db_host, etc to your apache class. Or create virtual resources and
realize them within the same class - works great for packages and maybe
other resource types.
On Tuesday, 3 April 2012 19:33:32 UTC+1, Christophe L wrote:
Hello,
We had the following situation where including two classes that were
ensuring the installation of the same package php5-imagick and it
was causing an error indicating that two ressources of the same name
are forbidden (sorry, I don't have the exact message error since we
fixed quickly the error).
Since we are newbies in puppet, we would like to understand what this
error meant:
does it mean that all the package resource ensuring the installation
of a package need to have a unique resource name ?
Or maybe have we done something wrong in our usage of puppet ?
Below, the code causing the error and how we fixed it.
Thanks in advance for your feebacks.
Best regards,
Christophe
Code causing the error:
/etc/puppet/modules/apache/manifests/init.pp
class apache::install {
...
package { [ php5, php5-cli, php5-gd, php5-imagick, php5-
mysql, phpmyadmin, mysql-client ]:
ensure = installed,
}
...
}
/etc/puppet/modules/cms/manifests/init.pp
class cms::installpackage {
...
package { 'php5-imagick':
name = 'php5-imagick',
ensure = 'installed',
}
...
}
In order to fix the error, we prefixed the resource in
cms::installpackage class with cms_
package { 'cms_php5-imagick':
name = 'php5-imagick',
ensure = 'installed',
}
--
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/-/taR8nQd_iDMJ.
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] Managing home directory on Windows
I have a question for windows users out there. Adam recently reported a bug[1] that the managehome parameter on Windows doesn't work. According to the documentation (since 2.7.6), the manages_homedir [feature is defined as] The provider can create and remove home directories.[2] As such, the fix for #15560 will create/delete the home directory when ensure = present/absent, respectively, and managehome = true. Note, managehome is false by default. This fix is targeted for 2.7.20 and is in alignment with other *nix-y user providers that support the manages_homedir feature, e.g. useradd. However, there may be users out there that have set `managehome = true` in their manifests, and are unaware of what that parameter means. Worse, they may be surprised when upgrading to 2.7.20. Clearly, we're fixing a bug, and matching the behavior as described in our documentation, but we'd also like to keep 2.7.20 as stable as possible. Comments welcome. Also, Puppet 3.0 does create and delete the home directory, as expected. Josh [1] http://projects.puppetlabs.com/issues/15560 [2] http://docs.puppetlabs.com/references/2.7.6/type.html#user -- 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/-/aLxqR34Sz-4J. 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] puppet 3.0.1 Server and passenger
Hi Everyone; I am stumped. I am simply trying to upgrade from puppet 3.0.0 to puppet 3.0.1 master (rhel6) I have followed the precise steps I used when I installed 3.0.0 to migrate to Passenger, but for some reason, I know cannot get it running. There are no useful errors in the logs that I can find either. Please Help! p.s. I have already made the required changes to the config.ru file -- 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: puppet 3.0.1 Server and passenger
Here is the error that I get displayed to the screen...
Error: Could not retrieve catalog from remote server: Error 500 on SERVER:
!DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.01//EN
http://www.w3.org/TR/html4/strict.dtd;
html
head
meta http-equiv=Content-Type content=text/html; charset=UTF-8
meta name=generator content=Phusion Passenger
titleRuby (Rack) application could not be started/title
style type=text/css
body {
font-family: Verdana, 'Bitstream Vera Sans', Arial, Sans-Serif;
font-size: 10pt;
background: white;
color: #22;
margin: 0;
padding-top: 3em;
padding-bottom: 3em;
padding-left: 4.5em;
padding-right: 4.5em;
}
On Tue, Nov 6, 2012 at 1:50 PM, Worker Bee beeworke...@gmail.com wrote:
Hi Everyone;
I am stumped.
I am simply trying to upgrade from puppet 3.0.0 to puppet 3.0.1 master
(rhel6)
I have followed the precise steps I used when I installed 3.0.0 to migrate
to Passenger, but for some reason, I know cannot get it running.
There are no useful errors in the logs that I can find either.
Please Help!
p.s. I have already made the required changes to the config.ru file
--
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.
Re: [Puppet Users] Re: puppet failing to run
On Tue, Nov 6, 2012 at 1:14 PM, Jeff McCune j...@puppetlabs.com wrote:
Did you have a version of Puppet on this system previously? This
definitely seems like a bug, but it seems like one that only manifests if
there's some other copy of Puppet that is also being loaded along with the
version you expect.
There was a puppet 2.6.8 before and it was failing horribly with all kind
of ruby file missing.
So I installed this version using gem. Now I removed gem version puppet to
get the puppet 2.6.8 back
Now puppet version works again
$ puppet --version
2.6.8
But it does not help with this manifest
$ cat ldap.pp
class { pam_ldap: }
$ puppet apply ldap.pp
/usr/lib/ruby/vendor_ruby/facter/virtual.rb:168: undefined method
`has_weight' for #Facter::Util::Resolution:0x7f55970a3748 (NoMethodError)
from /usr/local/lib/site_ruby/1.8/facter/util/fact.rb:38:in `instance_eval'
from /usr/local/lib/site_ruby/1.8/facter/util/fact.rb:38:in `add'
from /usr/local/lib/site_ruby/1.8/facter/util/collection.rb:35:in `add'
from /usr/local/lib/site_ruby/1.8/facter.rb:105:in `add'
from /usr/lib/ruby/vendor_ruby/facter/virtual.rb:167
from /usr/local/lib/site_ruby/1.8/facter/util/loader.rb:73:in `load'
from /usr/local/lib/site_ruby/1.8/facter/util/loader.rb:73:in `load_file'
from /usr/local/lib/site_ruby/1.8/facter/util/loader.rb:38:in `load_all'
from /usr/local/lib/site_ruby/1.8/facter/util/loader.rb:33:in `each'
from /usr/local/lib/site_ruby/1.8/facter/util/loader.rb:33:in `load_all'
from /usr/local/lib/site_ruby/1.8/facter/util/loader.rb:30:in `each'
from /usr/local/lib/site_ruby/1.8/facter/util/loader.rb:30:in `load_all'
from /usr/local/lib/site_ruby/1.8/facter/util/collection.rb:90:in
`load_all'
from /usr/local/lib/site_ruby/1.8/facter.rb:95:in `to_hash'
from /usr/local/lib/site_ruby/1.8/puppet/indirector/facts/facter.rb:71:in
`find'
from /usr/local/lib/site_ruby/1.8/puppet/indirector/indirection.rb:188:in
`find'
from /usr/local/lib/site_ruby/1.8/puppet/indirector.rb:50:in `find'
from /usr/local/lib/site_ruby/1.8/puppet/application/apply.rb:88:in `main'
from /usr/local/lib/site_ruby/1.8/puppet/application/apply.rb:35:in
`run_command'
from /usr/local/lib/site_ruby/1.8/puppet/application.rb:305:in `run'
from /usr/local/lib/site_ruby/1.8/puppet/application.rb:420:in `hook'
from /usr/local/lib/site_ruby/1.8/puppet/application.rb:305:in `run'
from /usr/local/lib/site_ruby/1.8/puppet/application.rb:411:in
`exit_on_fail'
from /usr/local/lib/site_ruby/1.8/puppet/application.rb:305:in `run'
from /usr/local/lib/site_ruby/1.8/puppet/util/command_line.rb:62:in
`execute'
from /usr/bin/puppet:4
-Jeff
On Tue, Nov 6, 2012 at 9:20 AM, Asif Iqbal vad...@gmail.com wrote:
On Tue, Nov 6, 2012 at 11:31 AM, Asif Iqbal vad...@gmail.com wrote:
I am getting this error after installing puppet with gem
$ gem install puppet
Fetching: facter-1.6.14.gem (100%)
Fetching: puppet-3.0.1.gem (100%)
Successfully installed facter-1.6.14
Successfully installed puppet-3.0.1
2 gems installed
Installing ri documentation for facter-1.6.14...
Installing ri documentation for puppet-3.0.1...
Installing RDoc documentation for facter-1.6.14...
Installing RDoc documentation for puppet-3.0.1...
Could not find main page README.md
Could not find main page README.md
Could not find main page README.md
Could not find main page README.md
$ puppet --version
Error: Could not intialize global default settings: Error converting
value for param 'factpath': Could not find value for $confdir
google search found this link and that is already fixed for this version
https://github.com/puppetlabs/puppet/pull/750
Please advise.
I am on Ubuntu 12.04.1 LTS 64bit server and gem version is 1.8.24
--
Asif Iqbal
PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
--
Asif Iqbal
PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
--
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.
--
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.
--
Asif Iqbal
PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
--
You received this message
[Puppet Users] augeas syntax for adding similar lines to hosts.allow
I've found a similar thread here, but it doesn't do quite what I need. https://groups.google.com/forum/?fromgroups=#!topic/puppet-users/VMloh1KrSew I have multiple lines of the form below in hosts.allow: sshd,sshd2: 1.1.1.1 sshd,sshd2: 2.2.2.2 etc. I'm struggling with the syntax to add yet another sshd,sshd2: client line to hosts.allow. augtool is treating the lines as follows augtool ls /files/etc/hosts.allow/*[last()] process[1] = sshd process[2] = sshd2 client = 3.3.3.3 I need to add another line when the processes already exist, but the client is new. Any suggestions? -- 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/-/aWaiSr2YhV0J. 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: Managing home directory on Windows
On Tuesday, November 6, 2012 12:36:19 PM UTC-6, Josh Cooper wrote: I have a question for windows users out there. Adam recently reported a bug[1] that the managehome parameter on Windows doesn't work. According to the documentation (since 2.7.6), the manages_homedir [feature is defined as] The provider can create and remove home directories.[2] As such, the fix for #15560 will create/delete the home directory when ensure = present/absent, respectively, and managehome = true. Note, managehome is false by default. This fix is targeted for 2.7.20 and is in alignment with other *nix-y user providers that support the manages_homedir feature, e.g. useradd. However, there may be users out there that have set `managehome = true` in their manifests, and are unaware of what that parameter means. Worse, they may be surprised when upgrading to 2.7.20. Clearly, we're fixing a bug, and matching the behavior as described in our documentation, but we'd also like to keep 2.7.20 as stable as possible. Comments welcome. Also, Puppet 3.0 does create and delete the home directory, as expected. Create *and* delete? Is that just the Windows provider, or also the others that support the manages_homedir feature? Historic behavior, at least for some providers, was to create the homedir upon user creation, but not to remove it upon user removal. There are circumstances in which that is preferable, and you certainly would not want to surprise users who depend on it. John -- 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/-/_vl1ZBBOAh4J. 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: 2 package resources for the same package installation in two differents modules caused errors
On Tuesday, November 6, 2012 12:31:16 PM UTC-6, Vaidas Jablonskis wrote: What I normally do is I create a virtual @package resource which installs php5 for example within say apache class and then I realize the virtual resource within the same apache class. Please, if you intend to write generic and reusable modules so other people can use, STOP putting hardcoded dependencies in your modules. Either write in documentation that it depends on an abstract resource, for instance a mysql database and make it configurable so you can pass db_name, db_host, etc to your apache class. Or create virtual resources and realize them within the same class - works great for packages and maybe other resource types. If only it were that easy. Cross-module dependencies are a particularly tricky issue for all past and present Puppet versions. We have had some interesting discussions on that topic here, with some possibly-useful ideas arising from them, but none of that has made it into the codebase yet. If you write all your own modules then you can probably keep the problem under control, but if you rely on others' modules then you simply have to be prepared to make local modifications to address compatibility problems. Good module documentation is helpful for that, but there is no documentation or coding practice that can solve the problem under the current DSL. John -- 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/-/FuNKiZK0t_kJ. 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] Re: Managing home directory on Windows
Hi John, On Tue, Nov 6, 2012 at 12:28 PM, jcbollinger john.bollin...@stjude.orgwrote: On Tuesday, November 6, 2012 12:36:19 PM UTC-6, Josh Cooper wrote: I have a question for windows users out there. Adam recently reported a bug[1] that the managehome parameter on Windows doesn't work. According to the documentation (since 2.7.6), the manages_homedir [feature is defined as] The provider can create and remove home directories.[2] As such, the fix for #15560 will create/delete the home directory when ensure = present/absent, respectively, and managehome = true. Note, managehome is false by default. This fix is targeted for 2.7.20 and is in alignment with other *nix-y user providers that support the manages_homedir feature, e.g. useradd. However, there may be users out there that have set `managehome = true` in their manifests, and are unaware of what that parameter means. Worse, they may be surprised when upgrading to 2.7.20. Clearly, we're fixing a bug, and matching the behavior as described in our documentation, but we'd also like to keep 2.7.20 as stable as possible. Comments welcome. Also, Puppet 3.0 does create and delete the home directory, as expected. Create *and* delete? Is that just the Windows provider, or also the others that support the manages_homedir feature? The useradd provider deletes the home directory: https://github.com/puppetlabs/puppet/blob/3.0.x/lib/puppet/provider/user/useradd.rb#L86 As does pw: https://github.com/puppetlabs/puppet/blob/3.0.x/lib/puppet/provider/user/pw.rb#L59 And same for providers that extend those. Historic behavior, at least for some providers, was to create the homedir upon user creation, but not to remove it upon user removal. I'm not sure how we got from historic behavior to now, or the reasons behind it. There are circumstances in which that is preferable, and you certainly would not want to surprise users who depend on it. FWIW, managehome is false by default. It's only when it's true that you get create or delete behavior of the home directory. Josh -- Josh Cooper Developer, Puppet Labs -- 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: Puppet JBoss
On Tuesday, November 6, 2012 8:30:53 AM UTC-6, Budicom wrote: Hi, I have a big problem with Puppet and JBoss. In jboss/server/ directory, there are several instances. And instances started, +10 files are presents. Puppetrun takes several hours to complete his cycle. tmp/ directory is ignore in file resource (ignore = [ 'tmp', 'work', 'data', '.git', '*puppet-bak', '*class', '*tld', '*jsp' ],) but this directory is still processed. I don't understand. You didn't say anything about what resources Puppet is actually managing, and that makes a big difference. Nevertheless, it sounds like probably you have it managing part or all of one or more JBoss instance directories, as recursive files. That will be very costly (which is why I suppose it's what you are doing). On each run, Puppet checks every managed file individually to see whether it is up-to-date, and when you set up recursive management that can be a lot of files. Cost scales both with the total number of files and with the aggregate size of the files. How to reduced execution time ? Avoid recursively managing directories, especially directories containing many files, large files, or both. Prefer to install software and even data via your system's native package manager (yum / apt / whatever), even if it means rolling your own packages and keeping them in a local repository (neither of which is all that hard). Where packages are unsuitable for some reason, approximate them by packing up your big directories into tarballs or other archive files, managing those as individual files, and installing from from them at need. For borderline cases, you may be able to achieve some speedup by switching your expensive File resources to a cheaper checksum method, or otherwise tweaking the File parameters, but the case you describe is far beyond borderline. John -- 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/-/36_Z36AHf9oJ. 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] Re: Managing home directory on Windows
On Tue, Nov 6, 2012 at 8:46 PM, Josh Cooper j...@puppetlabs.com wrote: Historic behavior, at least for some providers, was to create the homedir upon user creation, but not to remove it upon user removal. I'm not sure how we got from historic behavior to now, or the reasons behind it. So #10354 (http://projects.puppetlabs.com/issues/10354) and commit ed738454 (https://github.com/puppetlabs/puppet/commit/ed7384546fd2f5b1dbbc61a2847c64227729041a) seem relevant here. I must admit to being quite surprised that managehome would actually delete a user's home directory on deletion of the user, but only because this is not how things typically work in *nix environments by default (as evidenced by the fact that the bug was raised in the first place). Thankfully for me, managehome is not true by default, so I've not been bitten by this, despite not reading the relevant docs :-) That said, would it perhaps be worth putting a note/warning in the documentation for managehome that it will delete the user's home directory and any data therein? The removal is mentioned under the 'Features' entry for manages_homedir, but isn't explicitly called out in the 'Parameters' entry for managehome. Thanks, Matt. -- 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: Hiera autolookup for defined types
On Tuesday, November 6, 2012 11:04:46 AM UTC-6, Bruno Leon wrote:
Hello,
since Puppet 3 hiera is doing auto variable lookup for classes, which in
my
view makes the code much clearer simply because we can use
include foo
instead of
class { 'foo':
param1 = value,
param2 = value,
}
There are other advantages to using 'include', too, so bravo!
However, AFAIK there is no such feature as auto looking parameters for
defined
type.
A common case is multiple vhost in Apache.
You already started answering your own question when you wrote multiple.
For a similar feature to work for defined types, it has to be able to
identify keys to use to lookup parameters for a given instance, preferably
without risk of colliding with classes or other defined-type instances.
Even though you can have apache installed as simply as include apache,
you
still have a lot of define (one per vhost), possibly each with different
parameters.
Would it be possible to have hiera looking up for a hash of parameters.
Something like this in hiera:
---
apache_vhost:
website1:
web_param1: 'foo'
web_param2: 'bar'
website2:
web_param1: 'another_foor'
web_param2: 'another_bar'
And in the manifest, this would be invoked as simply as:
node test {
include apache
apache_vhost { 'website1': }
apache_vhost { 'website2': }
}
Any ideas on this ? Any plans of implementation ?
You can do something very like what you describe via the built-in
create_resources() function. Given the data exactly as you structured it
in your example, you could do this:
# load the vhost data as a hash of hashes
$vhost_data = hiera('apache_vhost')
# declare the apache_vhost instances
create_resources('apache_vhost', $vhost_data)
# (that's it)
See
http://docs.puppetlabs.com/references/3.0.0/function.html#createresources
for more information.
Alternatively, you can write hiera lookups into your definition, either in
addition to or instead of parameters. Or it can be more efficient to load
hiera data into class variables, and have your definition pull it from
there:
class apache::vhost_data {
$data = hiera('apache_vhost')
}
define apache::vhost_wrapper () {
include 'apache::vhost_data'
$data = $apache::vhost_data::data[$name]
apache_vhost { $name:
web_param1 = $data['web_param1'],
web_param2 = $data['web_param2']
}
}
John
--
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/-/wuixUaya3k8J.
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: puppet 3.0.1 Server and passenger
Found the answer... https://groups.google.com/forum/#!msg/puppet-users/7T26yDW-Xtk/xro1t8Kr10gJ On Tue, Nov 6, 2012 at 1:50 PM, Worker Bee beeworke...@gmail.com wrote: Hi Everyone; I am stumped. I am simply trying to upgrade from puppet 3.0.0 to puppet 3.0.1 master (rhel6) I have followed the precise steps I used when I installed 3.0.0 to migrate to Passenger, but for some reason, I know cannot get it running. There are no useful errors in the logs that I can find either. Please Help! p.s. I have already made the required changes to the config.ru file -- 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.
Re: [Puppet Users] Re: Managing home directory on Windows
Hi Matt, On Tue, Nov 6, 2012 at 1:10 PM, Matthew Burgess matthew.2.burg...@gmail.com wrote: On Tue, Nov 6, 2012 at 8:46 PM, Josh Cooper j...@puppetlabs.com wrote: Historic behavior, at least for some providers, was to create the homedir upon user creation, but not to remove it upon user removal. I'm not sure how we got from historic behavior to now, or the reasons behind it. So #10354 (http://projects.puppetlabs.com/issues/10354) and commit ed738454 (https://github.com/puppetlabs/puppet/commit/ed7384546fd2f5b1dbbc61a2847c64227729041a) seem relevant here. I must admit to being quite surprised that managehome would actually delete a user's home directory on deletion of the user, but only because this is not how things typically work in *nix environments by default (as evidenced by the fact that the bug was raised in the first place). Thanks for the pointer. I did find http://projects.puppetlabs.com/issues/432 in which managehome was first implemented, and defines the remove home directory behavior. It seems that functionality was broken at some point later, and then fixed in the bug you mentioned, surprisingly in 2.7.19. Similarly, http://projects.puppetlabs.com/issues/12081 was fixed in 2.7.12. Thankfully for me, managehome is not true by default, so I've not been bitten by this, despite not reading the relevant docs :-) That said, would it perhaps be worth putting a note/warning in the documentation for managehome that it will delete the user's home directory and any data therein? The removal is mentioned under the 'Features' entry for manages_homedir, but isn't explicitly called out in the 'Parameters' entry for managehome. Sounds reasonable to me. Josh -- Josh Cooper Developer, Puppet Labs -- 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] Augeas and custom lenses?
Hi I want to modify one of the existing lenses to better suit my needs, but I don't know where to put it on the filesystem? It seems wrong to overwrite file in /usr/share/augeas/lenses/dist or to rebuild augeas-libs, is there any other way to distribute modifications of existing lenses or completely new lenses? -- 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: Puppet 3.0: Not authorized to call find on /file_metadata, more issues?
The files we have that go out are under /etc/puppet/files. So, the ntp.conf exists under /etc/puppet/files/etc/ntp.conf -- there are also other structures under /etc/puppet/files that we refer to. I would presume a more efficient way to refer to this is any file under /etc/puppet/files. This is starting to get confusing :-) Yeah, the example.com was a typo on my part. I do have our own domain there. Here's the relevant part of that config: path ~ ^/file_(metadata|content)/files/etc/ path /file auth yes allow /^(.+\.)?ourdomain.com$/ allow_ip 10.0.0.0/8 which still generates errors: # puppet agent --test Ignoring --listen on onetime run Warning: Unable to fetch my node definition, but the agent run will continue: Warning: Error 403 on SERVER: Forbidden request: stage1.ourdomain.com(127.0.0.1) access to /node/stage1.ourdomain.com [find] authenticated at :101 Info: Retrieving plugin Info: Caching catalog for stage1.ourdomain.com Info: Applying configuration version '1352241407' Error: /Stage[main]/Ntp-client/File[/etc/ntp.conf]: Could not evaluate: Error 400 on SERVER: Not authorized to call find on /file_metadata/etc/ntp.conf Could not retrieve file metadata for puppet:///etc/ntp.conf: Error 400 on SERVER: Not authorized to call find on /file_metadata/etc/ntp.conf /Stage[main]/Ntp-client/Service[ntpd]: Dependency File[/etc/ntp.conf] has failures: true Warning: /Stage[main]/Ntp-client/Service[ntpd]: Skipping because of failed dependencies Finished catalog run in 1.45 seconds I think I found another bug. I added the localhost with allow_ip 127/8 which is a valid CIDR notation; I had to change it to allow_ip 127.0.0.0/8 but it still failed anyway: Warning: Unable to fetch my node definition, but the agent run will continue: Warning: Error 403 on SERVER: Forbidden request: stage1.ourdomain.com(127.0.0.1) access to /node/stage1.ourdomain.com [find] authenticated at :102 Do I also need to include allow * in the directive? Seems that would take precedence over allow_ip. Any word on when a fixed release is going to come out :-) Thanks On Wednesday, October 31, 2012 1:03:36 PM UTC-4, Nick Fagerlund wrote: Hi, Forrie, I see a handful of problems here: * First, you can't comment out the path /file allow * rule in auth.conf, because Puppet actually uses that for pluginsync and for files in modules! What you have to do is have BOTH the new rule I gave you AND the old one, but make sure the new one comes FIRST so that it can prevent the broader rule from being applied to the specific mount point you're trying to protect. * Second, you copied my example path ~ ^/file_(metadata|content)/files/ URL, but it looks like the actual mount point you're using is named [etc] in fileserver.conf. That means you should change the rule to path ~ ^/file_(metadata|content)/etc/. You can see in the logs that the rule isn't matching the requests, both because the URL is wrong ( /file_metadata/etc/ntp.conf, whereas the rule is expecting /file_metadata/files/ntp.conf) and because it's citing line 100 or 102 of auth.conf (meaning it skipped the rule). * The IP address COULD be a problem, since you're connecting to the master from 127.0.0.1. Right now, it looks like you have a literal example.com in auth.conf and your real domain elsewhere, which would be a problem, but you probably just missed that when editing out your site-specific details. IF there's still an example.com in your auth.conf, and I realize there's probably not, you should replace it with your real domain. Try fixing those and see where it gets you. Good luck! -- 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/-/zSzrbO-yk8UJ. 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] Re: tcl dependency in RHEL6 installing facter, puppet
On Tue, Nov 6, 2012 at 6:37 AM, jcbollinger john.bollin...@stjude.org wrote: On Monday, November 5, 2012 2:10:58 PM UTC-6, msuho wrote: Hi- I am running RedHat Enterprise version 6. Linux luke 2.6.32-131.17.1.el6.x86_64 #1 SMP Thu Sep 29 10:24:25 EDT 2011 x86_64 x86_64 x86_64 GNU/Linux I'm trying to install puppet. I added the puppetlabs repos using this RPM: http://yum.puppetlabs.com/el/6/products/x86_64/puppetlabs-release-6-6.noarch.rpm When I try to install facter (or puppet), it tries to install ruby and ruby-libs , and fails because it can't find the version of tcl it needs: yum install facter Loaded plugins: product-id, refresh-packagekit, rhnplugin, subscription-manager, versionlock Updating certificate-based repositories. Unable to read consumer identity Setting up Install Process Resolving Dependencies -- Running transaction check --- Package facter.x86_64 1:1.6.14-1.el5 will be installed -- Processing Dependency: ruby = 1.8.5 for package: 1:facter-1.6.14-1.el5.x86_64 -- Processing Dependency: ruby(abi) = 1.8 for package: 1:facter-1.6.14-1.el5.x86_64 -- Processing Dependency: /usr/bin/ruby for package: 1:facter-1.6.14-1.el5.x86_64 -- Running transaction check --- Package ruby.x86_64 0:1.8.7.370-1.el5 will be installed --- Package ruby-libs.x86_64 0:1.8.7.370-1.el5 will be installed -- Processing Dependency: libtk8.4.so()(64bit) for package: ruby-libs-1.8.7.370-1.el5.x86_64 -- Processing Dependency: libtcl8.4.so()(64bit) for package: ruby-libs-1.8.7.370-1.el5.x86_64 -- Processing Dependency: libssl.so.6()(64bit) for package: ruby-libs-1.8.7.370-1.el5.x86_64 -- Processing Dependency: libtermcap.so.2()(64bit) for package: ruby-libs-1.8.7.370-1.el5.x86_64 -- Processing Dependency: libdb-4.3.so()(64bit) for package: ruby-libs-1.8.7.370-1.el5.x86_64 -- Processing Dependency: libcrypto.so.6()(64bit) for package: ruby-libs-1.8.7.370-1.el5.x86_64 -- Running transaction check --- Package compat-db43.x86_64 0:4.3.29-15.el6 will be installed --- Package compat-libtermcap.x86_64 0:2.0.8-49.el6 will be installed --- Package openssl098e.x86_64 0:0.9.8e-17.el6_2.2 will be installed --- Package ruby-libs.x86_64 0:1.8.7.370-1.el5 will be installed -- Processing Dependency: libtk8.4.so()(64bit) for package: ruby-libs-1.8.7.370-1.el5.x86_64 -- Processing Dependency: libtcl8.4.so()(64bit) for package: ruby-libs-1.8.7.370-1.el5.x86_64 -- Finished Dependency Resolution Error: Package: ruby-libs-1.8.7.370-1.el5.x86_64 (puppetlabs-deps) Requires: libtcl8.4.so()(64bit) Error: Package: ruby-libs-1.8.7.370-1.el5.x86_64 (puppetlabs-deps) Requires: libtk8.4.so()(64bit) You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest This has worked in the past on my RHEL5 machines, where the version of TCL is 8.4.13, but the version on RHEL6 is 8.5.7 I see folks on this list using RHEL6- I was wondering how you got past this? It's not them, it's you. Something is screwed up with your repository configuration. It looks like you're trying to install a mix of RHEL 5 and RHEL 6 packages on your system. Also, probably some third-party or homebrew, since I see a Ruby 1.8.7...el5, and RHEL 5's official Ruby is pinned at version 1.8.5. In direct response to your question, the EL6 ruby-libs package has no dependency on any version of Tcl or tk. John -- 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/-/hu8fPrhrHwMJ. 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. It looks like you have RHEL 6 and 5 content mixed as John said. We do ship a Ruby 1.8.7 in PuppetLabs-deps for Puppet 3.0 for EL5 only. You shouldn't be trying to grab that, as you're on EL6. Do the puppetlabs* files look correct in /etc/yum.repos.d ? -- 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.
Re: [Puppet Users] Puppet JBoss
Sorry for the top posting.
So, configuration and package management are different problem: trying
to solve a problem with a tool born for solving the other problem can
have, in the short or long run, some issue.
Ymmv, as everyone else.
Best
2012/11/6, Alan Evans alanwev...@gmail.com:
Budicom,
One thing I might suggest is not to put the entire JBoss directory in
puppet and realize it as a file resource. As gross as it is for a
former employer I used the zip deployment and extracted the zip file.
Disclaimer: No syntax checking, no validation YMMV, for example only. :)
file { $somepath/jboss-$version.zip:
ensure = 'present',
source = $somewhere,
}
exec { unzip-jboss-$version.zip:
command = unzip $somepath/jboss-$version.zip -q -d $someotherdir,
requires = [ File[$somepath/jboss-$version.zip, Package['zip'] ],
}
exec { backup-jboss-$version-profiles:
command = mv $someotherdir/jboss-$version/server/
$someotherdir/jboss-$version/server.orig,
creates = $someotherdir/jboss-$version/server.orig,
requires = unzip-jboss-$version.zip,
}
class jboss::instance (
installdir = undef,
profile = 'default',
) {
exec { copy-jboss-profile-$name:
command = cp $installdir/jboss-$version/server.orig/$profile
$installdir/jboss-$version/server/$name
creates = $installdir/jboss-$version/server/$name
}
# setup an init script
# configure other instance properties w/ augeas/files
}
Campt to camp has a great archive installer you could cannibalize or
perhaps use in its entirety. It didn't quite work in my last
situation but perhaps it would work for you.
https://github.com/camptocamp/puppet-archive
Regards,
-Alan
On Tue, Nov 6, 2012 at 7:30 AM, Budicom nduter...@geodisbm.com wrote:
Hi,
I have a big problem with Puppet and JBoss.
In jboss/server/ directory, there are several instances. And instances
started, +10 files are presents.
Puppetrun takes several hours to complete his cycle.
tmp/ directory is ignore in file resource (ignore = [ 'tmp', 'work',
'data', '.git', '*puppet-bak', '*class', '*tld', '*jsp' ],) but this
directory is still processed.
I don't understand.
How to reduced execution time ?
Thx.
--
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/-/Z_sNqoE6xDcJ.
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.
--
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.
--
Inviato dal mio dispositivo mobile
--
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.
Re: [Puppet Users] Re: Can Puppet alert about dead nodes?
Op donderdag 1 november 2012 19:03:20 UTC+1 schreef Greg Sutcliffe het volgende: On 1 November 2012 17:54, Lucas Vickers lucasv...@gmail.com javascript: wrote: I am currently using the open source edition so I have no dashboard. Puppet Dashboard is opensource, so you could use it, but it's being deprecated (last I heard, anyway). You could also checkout The Foreman, which will display nodes out-of-sync (and email you about it, if you like). We also use Puppet Dashboard for reporting, and it visually shows changed nodes and shows the nodes that have not reported recently. We use the open source Puppet stack and the Dashboard nicely complements it. I've not heard anything about it being deprecated and have to assume you're mistaken since a quick Google could find no mention of it. Dashboard is still actively updated, and since it's the main interface to Puppet Enterprise as well I don't see it going away soon. The Foreman is also an impressive dashboard with more features than Puppet Dashboard but a bit more complexity as well. Regards, Martijn Heemels -- 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/-/jkwbFc8FL6kJ. 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] Re: puppet failing to run
What version(s) of facter are you running? Perhaps you have multiple
installed here as well? It seems strange that the trace you posted
references two distinct library paths,
e.g.
/usr/local/lib/site_ruby/1.8/facter and /usr/lib/ruby/vendor_ruby/facter
On Tue, Nov 6, 2012 at 11:19 AM, Asif Iqbal vad...@gmail.com wrote:
On Tue, Nov 6, 2012 at 1:14 PM, Jeff McCune j...@puppetlabs.com wrote:
Did you have a version of Puppet on this system previously? This
definitely seems like a bug, but it seems like one that only manifests if
there's some other copy of Puppet that is also being loaded along with the
version you expect.
There was a puppet 2.6.8 before and it was failing horribly with all kind of
ruby file missing.
So I installed this version using gem. Now I removed gem version puppet to
get the puppet 2.6.8 back
Now puppet version works again
$ puppet --version
2.6.8
But it does not help with this manifest
$ cat ldap.pp
class { pam_ldap: }
$ puppet apply ldap.pp
/usr/lib/ruby/vendor_ruby/facter/virtual.rb:168: undefined method
`has_weight' for #Facter::Util::Resolution:0x7f55970a3748 (NoMethodError)
from /usr/local/lib/site_ruby/1.8/facter/util/fact.rb:38:in `instance_eval'
from /usr/local/lib/site_ruby/1.8/facter/util/fact.rb:38:in `add'
from /usr/local/lib/site_ruby/1.8/facter/util/collection.rb:35:in `add'
from /usr/local/lib/site_ruby/1.8/facter.rb:105:in `add'
from /usr/lib/ruby/vendor_ruby/facter/virtual.rb:167
from /usr/local/lib/site_ruby/1.8/facter/util/loader.rb:73:in `load'
from /usr/local/lib/site_ruby/1.8/facter/util/loader.rb:73:in `load_file'
from /usr/local/lib/site_ruby/1.8/facter/util/loader.rb:38:in `load_all'
from /usr/local/lib/site_ruby/1.8/facter/util/loader.rb:33:in `each'
from /usr/local/lib/site_ruby/1.8/facter/util/loader.rb:33:in `load_all'
from /usr/local/lib/site_ruby/1.8/facter/util/loader.rb:30:in `each'
from /usr/local/lib/site_ruby/1.8/facter/util/loader.rb:30:in `load_all'
from /usr/local/lib/site_ruby/1.8/facter/util/collection.rb:90:in `load_all'
from /usr/local/lib/site_ruby/1.8/facter.rb:95:in `to_hash'
from /usr/local/lib/site_ruby/1.8/puppet/indirector/facts/facter.rb:71:in
`find'
from /usr/local/lib/site_ruby/1.8/puppet/indirector/indirection.rb:188:in
`find'
from /usr/local/lib/site_ruby/1.8/puppet/indirector.rb:50:in `find'
from /usr/local/lib/site_ruby/1.8/puppet/application/apply.rb:88:in `main'
from /usr/local/lib/site_ruby/1.8/puppet/application/apply.rb:35:in
`run_command'
from /usr/local/lib/site_ruby/1.8/puppet/application.rb:305:in `run'
from /usr/local/lib/site_ruby/1.8/puppet/application.rb:420:in `hook'
from /usr/local/lib/site_ruby/1.8/puppet/application.rb:305:in `run'
from /usr/local/lib/site_ruby/1.8/puppet/application.rb:411:in
`exit_on_fail'
from /usr/local/lib/site_ruby/1.8/puppet/application.rb:305:in `run'
from /usr/local/lib/site_ruby/1.8/puppet/util/command_line.rb:62:in
`execute'
from /usr/bin/puppet:4
-Jeff
On Tue, Nov 6, 2012 at 9:20 AM, Asif Iqbal vad...@gmail.com wrote:
On Tue, Nov 6, 2012 at 11:31 AM, Asif Iqbal vad...@gmail.com wrote:
I am getting this error after installing puppet with gem
$ gem install puppet
Fetching: facter-1.6.14.gem (100%)
Fetching: puppet-3.0.1.gem (100%)
Successfully installed facter-1.6.14
Successfully installed puppet-3.0.1
2 gems installed
Installing ri documentation for facter-1.6.14...
Installing ri documentation for puppet-3.0.1...
Installing RDoc documentation for facter-1.6.14...
Installing RDoc documentation for puppet-3.0.1...
Could not find main page README.md
Could not find main page README.md
Could not find main page README.md
Could not find main page README.md
$ puppet --version
Error: Could not intialize global default settings: Error converting
value for param 'factpath': Could not find value for $confdir
google search found this link and that is already fixed for this version
https://github.com/puppetlabs/puppet/pull/750
Please advise.
I am on Ubuntu 12.04.1 LTS 64bit server and gem version is 1.8.24
--
Asif Iqbal
PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
--
Asif Iqbal
PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
--
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.
--
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,
Re: [Puppet Users] Re: puppet failing to run
On Tue, Nov 6, 2012 at 7:11 PM, Moses Mendoza mo...@puppetlabs.com wrote:
What version(s) of facter are you running? Perhaps you have multiple
installed here as well? It seems strange that the trace you posted
references two distinct library paths,
e.g.
/usr/local/lib/site_ruby/1.8/facter and /usr/lib/ruby/vendor_ruby/facter
$ facter --version
1.5.8
On Tue, Nov 6, 2012 at 11:19 AM, Asif Iqbal vad...@gmail.com wrote:
On Tue, Nov 6, 2012 at 1:14 PM, Jeff McCune j...@puppetlabs.com wrote:
Did you have a version of Puppet on this system previously? This
definitely seems like a bug, but it seems like one that only manifests
if
there's some other copy of Puppet that is also being loaded along with
the
version you expect.
There was a puppet 2.6.8 before and it was failing horribly with all
kind of
ruby file missing.
So I installed this version using gem. Now I removed gem version puppet
to
get the puppet 2.6.8 back
Now puppet version works again
$ puppet --version
2.6.8
But it does not help with this manifest
$ cat ldap.pp
class { pam_ldap: }
$ puppet apply ldap.pp
/usr/lib/ruby/vendor_ruby/facter/virtual.rb:168: undefined method
`has_weight' for #Facter::Util::Resolution:0x7f55970a3748
(NoMethodError)
from /usr/local/lib/site_ruby/1.8/facter/util/fact.rb:38:in
`instance_eval'
from /usr/local/lib/site_ruby/1.8/facter/util/fact.rb:38:in `add'
from /usr/local/lib/site_ruby/1.8/facter/util/collection.rb:35:in `add'
from /usr/local/lib/site_ruby/1.8/facter.rb:105:in `add'
from /usr/lib/ruby/vendor_ruby/facter/virtual.rb:167
from /usr/local/lib/site_ruby/1.8/facter/util/loader.rb:73:in `load'
from /usr/local/lib/site_ruby/1.8/facter/util/loader.rb:73:in `load_file'
from /usr/local/lib/site_ruby/1.8/facter/util/loader.rb:38:in `load_all'
from /usr/local/lib/site_ruby/1.8/facter/util/loader.rb:33:in `each'
from /usr/local/lib/site_ruby/1.8/facter/util/loader.rb:33:in `load_all'
from /usr/local/lib/site_ruby/1.8/facter/util/loader.rb:30:in `each'
from /usr/local/lib/site_ruby/1.8/facter/util/loader.rb:30:in `load_all'
from /usr/local/lib/site_ruby/1.8/facter/util/collection.rb:90:in
`load_all'
from /usr/local/lib/site_ruby/1.8/facter.rb:95:in `to_hash'
from /usr/local/lib/site_ruby/1.8/puppet/indirector/facts/facter.rb:71:in
`find'
from /usr/local/lib/site_ruby/1.8/puppet/indirector/indirection.rb:188:in
`find'
from /usr/local/lib/site_ruby/1.8/puppet/indirector.rb:50:in `find'
from /usr/local/lib/site_ruby/1.8/puppet/application/apply.rb:88:in
`main'
from /usr/local/lib/site_ruby/1.8/puppet/application/apply.rb:35:in
`run_command'
from /usr/local/lib/site_ruby/1.8/puppet/application.rb:305:in `run'
from /usr/local/lib/site_ruby/1.8/puppet/application.rb:420:in `hook'
from /usr/local/lib/site_ruby/1.8/puppet/application.rb:305:in `run'
from /usr/local/lib/site_ruby/1.8/puppet/application.rb:411:in
`exit_on_fail'
from /usr/local/lib/site_ruby/1.8/puppet/application.rb:305:in `run'
from /usr/local/lib/site_ruby/1.8/puppet/util/command_line.rb:62:in
`execute'
from /usr/bin/puppet:4
-Jeff
On Tue, Nov 6, 2012 at 9:20 AM, Asif Iqbal vad...@gmail.com wrote:
On Tue, Nov 6, 2012 at 11:31 AM, Asif Iqbal vad...@gmail.com wrote:
I am getting this error after installing puppet with gem
$ gem install puppet
Fetching: facter-1.6.14.gem (100%)
Fetching: puppet-3.0.1.gem (100%)
Successfully installed facter-1.6.14
Successfully installed puppet-3.0.1
2 gems installed
Installing ri documentation for facter-1.6.14...
Installing ri documentation for puppet-3.0.1...
Installing RDoc documentation for facter-1.6.14...
Installing RDoc documentation for puppet-3.0.1...
Could not find main page README.md
Could not find main page README.md
Could not find main page README.md
Could not find main page README.md
$ puppet --version
Error: Could not intialize global default settings: Error converting
value for param 'factpath': Could not find value for $confdir
google search found this link and that is already fixed for this
version
https://github.com/puppetlabs/puppet/pull/750
Please advise.
I am on Ubuntu 12.04.1 LTS 64bit server and gem version is 1.8.24
--
Asif Iqbal
PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
--
Asif Iqbal
PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
--
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
Re: [Puppet Users] Re: puppet failing to run
It looks to me as if there are at least two facters installed. One was
likely installed using install.rb (probably the one in
/usr/local/lib/site_ruby), and another was installed using the package
manager. Can you post the output of both `dpkg -S facter` and `dpkg -l
facter`? That will show which was installed via source and which one
was installed using apt.
On Tue, Nov 6, 2012 at 4:57 PM, Asif Iqbal vad...@gmail.com wrote:
On Tue, Nov 6, 2012 at 7:11 PM, Moses Mendoza mo...@puppetlabs.com wrote:
What version(s) of facter are you running? Perhaps you have multiple
installed here as well? It seems strange that the trace you posted
references two distinct library paths,
e.g.
/usr/local/lib/site_ruby/1.8/facter and /usr/lib/ruby/vendor_ruby/facter
$ facter --version
1.5.8
On Tue, Nov 6, 2012 at 11:19 AM, Asif Iqbal vad...@gmail.com wrote:
On Tue, Nov 6, 2012 at 1:14 PM, Jeff McCune j...@puppetlabs.com wrote:
Did you have a version of Puppet on this system previously? This
definitely seems like a bug, but it seems like one that only manifests
if
there's some other copy of Puppet that is also being loaded along with
the
version you expect.
There was a puppet 2.6.8 before and it was failing horribly with all
kind of
ruby file missing.
So I installed this version using gem. Now I removed gem version puppet
to
get the puppet 2.6.8 back
Now puppet version works again
$ puppet --version
2.6.8
But it does not help with this manifest
$ cat ldap.pp
class { pam_ldap: }
$ puppet apply ldap.pp
/usr/lib/ruby/vendor_ruby/facter/virtual.rb:168: undefined method
`has_weight' for #Facter::Util::Resolution:0x7f55970a3748
(NoMethodError)
from /usr/local/lib/site_ruby/1.8/facter/util/fact.rb:38:in
`instance_eval'
from /usr/local/lib/site_ruby/1.8/facter/util/fact.rb:38:in `add'
from /usr/local/lib/site_ruby/1.8/facter/util/collection.rb:35:in `add'
from /usr/local/lib/site_ruby/1.8/facter.rb:105:in `add'
from /usr/lib/ruby/vendor_ruby/facter/virtual.rb:167
from /usr/local/lib/site_ruby/1.8/facter/util/loader.rb:73:in `load'
from /usr/local/lib/site_ruby/1.8/facter/util/loader.rb:73:in
`load_file'
from /usr/local/lib/site_ruby/1.8/facter/util/loader.rb:38:in `load_all'
from /usr/local/lib/site_ruby/1.8/facter/util/loader.rb:33:in `each'
from /usr/local/lib/site_ruby/1.8/facter/util/loader.rb:33:in `load_all'
from /usr/local/lib/site_ruby/1.8/facter/util/loader.rb:30:in `each'
from /usr/local/lib/site_ruby/1.8/facter/util/loader.rb:30:in `load_all'
from /usr/local/lib/site_ruby/1.8/facter/util/collection.rb:90:in
`load_all'
from /usr/local/lib/site_ruby/1.8/facter.rb:95:in `to_hash'
from
/usr/local/lib/site_ruby/1.8/puppet/indirector/facts/facter.rb:71:in
`find'
from
/usr/local/lib/site_ruby/1.8/puppet/indirector/indirection.rb:188:in
`find'
from /usr/local/lib/site_ruby/1.8/puppet/indirector.rb:50:in `find'
from /usr/local/lib/site_ruby/1.8/puppet/application/apply.rb:88:in
`main'
from /usr/local/lib/site_ruby/1.8/puppet/application/apply.rb:35:in
`run_command'
from /usr/local/lib/site_ruby/1.8/puppet/application.rb:305:in `run'
from /usr/local/lib/site_ruby/1.8/puppet/application.rb:420:in `hook'
from /usr/local/lib/site_ruby/1.8/puppet/application.rb:305:in `run'
from /usr/local/lib/site_ruby/1.8/puppet/application.rb:411:in
`exit_on_fail'
from /usr/local/lib/site_ruby/1.8/puppet/application.rb:305:in `run'
from /usr/local/lib/site_ruby/1.8/puppet/util/command_line.rb:62:in
`execute'
from /usr/bin/puppet:4
-Jeff
On Tue, Nov 6, 2012 at 9:20 AM, Asif Iqbal vad...@gmail.com wrote:
On Tue, Nov 6, 2012 at 11:31 AM, Asif Iqbal vad...@gmail.com wrote:
I am getting this error after installing puppet with gem
$ gem install puppet
Fetching: facter-1.6.14.gem (100%)
Fetching: puppet-3.0.1.gem (100%)
Successfully installed facter-1.6.14
Successfully installed puppet-3.0.1
2 gems installed
Installing ri documentation for facter-1.6.14...
Installing ri documentation for puppet-3.0.1...
Installing RDoc documentation for facter-1.6.14...
Installing RDoc documentation for puppet-3.0.1...
Could not find main page README.md
Could not find main page README.md
Could not find main page README.md
Could not find main page README.md
$ puppet --version
Error: Could not intialize global default settings: Error converting
value for param 'factpath': Could not find value for $confdir
google search found this link and that is already fixed for this
version
https://github.com/puppetlabs/puppet/pull/750
Please advise.
I am on Ubuntu 12.04.1 LTS 64bit server and gem version is 1.8.24
--
Asif Iqbal
PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
--
Asif Iqbal
PGP Key: 0xE62693C5
Re: [Puppet Users] Re: puppet failing to run
I did some clean up. Now I have only one version of puppet and facter.
$ dpkg -S facter
http://paste.ubuntu.com/1338890/
$ dpkg -l facter
Desired=Unknown/Install/Remove/Purge/Hold
|
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Description
+++-=-=-==
ii facter1.6.14-1puppetlabs1 Ruby module for collecting
simple facts about a host opera
$ dpkg -L facter
http://paste.ubuntu.com/1338889/
$ puppet apply ldap.pp
Error: Could not intialize global default settings: Error converting value
for param 'factpath': Could not find value for $confdir
$ cat ldap.pp
class { pam_ldap: }
On Tue, Nov 6, 2012 at 9:55 PM, Matthaus Owens matth...@puppetlabs.comwrote:
It looks to me as if there are at least two facters installed. One was
likely installed using install.rb (probably the one in
/usr/local/lib/site_ruby), and another was installed using the package
manager. Can you post the output of both `dpkg -S facter` and `dpkg -l
facter`? That will show which was installed via source and which one
was installed using apt.
On Tue, Nov 6, 2012 at 4:57 PM, Asif Iqbal vad...@gmail.com wrote:
On Tue, Nov 6, 2012 at 7:11 PM, Moses Mendoza mo...@puppetlabs.com
wrote:
What version(s) of facter are you running? Perhaps you have multiple
installed here as well? It seems strange that the trace you posted
references two distinct library paths,
e.g.
/usr/local/lib/site_ruby/1.8/facter and /usr/lib/ruby/vendor_ruby/facter
$ facter --version
1.5.8
On Tue, Nov 6, 2012 at 11:19 AM, Asif Iqbal vad...@gmail.com wrote:
On Tue, Nov 6, 2012 at 1:14 PM, Jeff McCune j...@puppetlabs.com
wrote:
Did you have a version of Puppet on this system previously? This
definitely seems like a bug, but it seems like one that only
manifests
if
there's some other copy of Puppet that is also being loaded along
with
the
version you expect.
There was a puppet 2.6.8 before and it was failing horribly with all
kind of
ruby file missing.
So I installed this version using gem. Now I removed gem version
puppet
to
get the puppet 2.6.8 back
Now puppet version works again
$ puppet --version
2.6.8
But it does not help with this manifest
$ cat ldap.pp
class { pam_ldap: }
$ puppet apply ldap.pp
/usr/lib/ruby/vendor_ruby/facter/virtual.rb:168: undefined method
`has_weight' for #Facter::Util::Resolution:0x7f55970a3748
(NoMethodError)
from /usr/local/lib/site_ruby/1.8/facter/util/fact.rb:38:in
`instance_eval'
from /usr/local/lib/site_ruby/1.8/facter/util/fact.rb:38:in `add'
from /usr/local/lib/site_ruby/1.8/facter/util/collection.rb:35:in
`add'
from /usr/local/lib/site_ruby/1.8/facter.rb:105:in `add'
from /usr/lib/ruby/vendor_ruby/facter/virtual.rb:167
from /usr/local/lib/site_ruby/1.8/facter/util/loader.rb:73:in `load'
from /usr/local/lib/site_ruby/1.8/facter/util/loader.rb:73:in
`load_file'
from /usr/local/lib/site_ruby/1.8/facter/util/loader.rb:38:in
`load_all'
from /usr/local/lib/site_ruby/1.8/facter/util/loader.rb:33:in `each'
from /usr/local/lib/site_ruby/1.8/facter/util/loader.rb:33:in
`load_all'
from /usr/local/lib/site_ruby/1.8/facter/util/loader.rb:30:in `each'
from /usr/local/lib/site_ruby/1.8/facter/util/loader.rb:30:in
`load_all'
from /usr/local/lib/site_ruby/1.8/facter/util/collection.rb:90:in
`load_all'
from /usr/local/lib/site_ruby/1.8/facter.rb:95:in `to_hash'
from
/usr/local/lib/site_ruby/1.8/puppet/indirector/facts/facter.rb:71:in
`find'
from
/usr/local/lib/site_ruby/1.8/puppet/indirector/indirection.rb:188:in
`find'
from /usr/local/lib/site_ruby/1.8/puppet/indirector.rb:50:in `find'
from /usr/local/lib/site_ruby/1.8/puppet/application/apply.rb:88:in
`main'
from /usr/local/lib/site_ruby/1.8/puppet/application/apply.rb:35:in
`run_command'
from /usr/local/lib/site_ruby/1.8/puppet/application.rb:305:in `run'
from /usr/local/lib/site_ruby/1.8/puppet/application.rb:420:in `hook'
from /usr/local/lib/site_ruby/1.8/puppet/application.rb:305:in `run'
from /usr/local/lib/site_ruby/1.8/puppet/application.rb:411:in
`exit_on_fail'
from /usr/local/lib/site_ruby/1.8/puppet/application.rb:305:in `run'
from /usr/local/lib/site_ruby/1.8/puppet/util/command_line.rb:62:in
`execute'
from /usr/bin/puppet:4
-Jeff
On Tue, Nov 6, 2012 at 9:20 AM, Asif Iqbal vad...@gmail.com wrote:
On Tue, Nov 6, 2012 at 11:31 AM, Asif Iqbal vad...@gmail.com
wrote:
I am getting this error after installing puppet with gem
$ gem install puppet
Fetching: facter-1.6.14.gem (100%)
Fetching: puppet-3.0.1.gem (100%)
Successfully
Re: [Puppet Users] Augeas and custom lenses?
On 07/11/12 08:31, Jakov Sosic wrote: I want to modify one of the existing lenses to better suit my needs, but I don't know where to put it on the filesystem? I build an rpm which installs custom lenses in /usr/share/augeas/lenses It seems wrong to overwrite file in /usr/share/augeas/lenses/dist or to rebuild augeas-libs, is there any other way to distribute modifications of existing lenses or completely new lenses? It would be nicer to put them in /usr/share/augeas/lenses/local but that doesn't work (or didn't the last time I tried). -- Ian i.morti...@uq.edu.au Ian Mortimer Tel: +61 7 3346 8528 Science IT University of Queensland -- 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: retrieving module directory
Hi I am encountering this problem now, can you help me, how to set the default value for module network. Is it add a new [network] with path referencing the root of network module in fileserver.conf? On Thursday, March 29, 2012 6:27:23 PM UTC+8, A_SAAS wrote: Hi everyone, I found my error, the default value for my module network was not set for the new OS (Centos) so my resource file was not correct. Sorry for the convenient On Wed, Mar 28, 2012 at 7:37 PM, Antidot SAS antid...@gmail.comjavascript: wrote: Hi everyone, I have a puppet master/client infrastructure setup with apache. When on the same datacenter I don't have any problem. I am trying to use another datacenter, so I setup the fileserver.conf as followed: # Files in the /path/to/files directory will be served # at puppet:///mount_point/. [modules] allow *.datacenter1 allow *.datacenter2 [plugins] allow *.datacenter1 allow *.datacenter2 The fqdn of the server is: [root@template]# facter fqdn template.datacenter2 The client is registered on the server: [root@puppetmaster]:/etc/puppet # puppet cert list --all | grep tem + template.datacenter2 (49:33:8A:66:D5:CA:B4:A8:F3:EE:8C:6D:0D:09:0E:FB) But when I trying to run puppet here is the error: [root@template puppet]# puppet agent -t --debug --trace debug: Failed to load library 'rubygems' for feature 'rubygems' debug: Puppet::Type::User::ProviderUser_role_add: file roleadd does not exist debug: Puppet::Type::User::ProviderLdap: true value when expecting false debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/dscl does not exist debug: Puppet::Type::User::ProviderPw: file pw does not exist debug: Failed to load library 'ldap' for feature 'ldap' debug: /File[/var/lib/puppet/facts]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/ssl/private_keys/template.datacenter2.pem]: Autorequiring File[/var/lib/puppet/ssl/private_keys] debug: /File[/var/lib/puppet/ssl/public_keys]: Autorequiring File[/var/lib/puppet/ssl] debug: /File[/var/lib/puppet/state]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/lib]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/ssl/certs]: Autorequiring File[/var/lib/puppet/ssl] debug: /File[/var/lib/puppet/clientbucket]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/state/graphs]: Autorequiring File[/var/lib/puppet/state] debug: /File[/etc/puppet/puppet.conf]: Autorequiring File[/etc/puppet] debug: /File[/var/lib/puppet/state/last_run_report.yaml]: Autorequiring File[/var/lib/puppet/state] debug: /File[/var/lib/puppet/ssl/certs/ca.pem]: Autorequiring File[/var/lib/puppet/ssl/certs] debug: /File[/var/lib/puppet/client_data]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/ssl/crl.pem]: Autorequiring File[/var/lib/puppet/ssl] debug: /File[/var/lib/puppet/ssl/public_keys/template.datacenter2.pem]: Autorequiring File[/var/lib/puppet/ssl/public_keys] debug: /File[/var/lib/puppet/ssl]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/ssl/certificate_requests]: Autorequiring File[/var/lib/puppet/ssl] debug: /File[/var/lib/puppet/state/last_run_summary.yaml]: Autorequiring File[/var/lib/puppet/state] debug: /File[/var/lib/puppet/ssl/certs/template.datacenter.pem]: Autorequiring File[/var/lib/puppet/ssl/certs] debug: /File[/var/lib/puppet/client_yaml]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/ssl/private_keys]: Autorequiring File[/var/lib/puppet/ssl] debug: /File[/var/lib/puppet/ssl/private]: Autorequiring File[/var/lib/puppet/ssl] debug: Finishing transaction 23702911873500 debug: /File[/var/lib/puppet/facts]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/ssl/certs]: Autorequiring File[/var/lib/puppet/ssl] debug: /File[/var/lib/puppet/ssl/certs/ca.pem]: Autorequiring File[/var/lib/puppet/ssl/certs] debug: /File[/var/lib/puppet/ssl/certs/template.datacenter2.pem]: Autorequiring File[/var/lib/puppet/ssl/certs] debug: /File[/var/lib/puppet/ssl/certificate_requests]: Autorequiring File[/var/lib/puppet/ssl] debug: /File[/var/lib/puppet/state]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/ssl/private_keys/template.datacenter2.pem]: Autorequiring File[/var/lib/puppet/ssl/private_keys] debug: /File[/var/lib/puppet/ssl]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/ssl/private]: Autorequiring File[/var/lib/puppet/ssl] debug: /File[/var/lib/puppet/lib]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/ssl/public_keys]: Autorequiring File[/var/lib/puppet/ssl] debug: /File[/var/lib/puppet/ssl/private_keys]: Autorequiring File[/var/lib/puppet/ssl] debug: /File[/var/lib/puppet/ssl/public_keys/template.datacenter2.pem]: Autorequiring File[/var/lib/puppet/ssl/public_keys] debug:
[Puppet Users] Re: Puppet Meetup Australia (Melbourne, Sydney, Brisbane)
Hi Stephen I can help you out with a Brisbane venue if you don't have one already. Brent On Monday, November 5, 2012 8:58:42 AM UTC+10, Stephen Johnson wrote: Hi I currently in Australia, as im the instructor on the Puppet Fundamentals * courses in Melbourne, Sydney and Brisbane and just wondered if anyone fancied meeting up and talking about puppet, hiera, puppetdb, devops etc etc. As i dont live here any feedback on locations would help, if not ill randomly pick on closer to the time. Melbourne Thursday 8/11/2012 5.30pm (Location to be decided) Sydney Thursday 15/11/2012 5.30pm (Location to be decided) Brisbane Thursday 22/11/2012 5.30pm (Location to be decided) * http://puppetlabs.com/events/melbourne-puppet-fundamentals-training-melbourne-november-2012/ http://puppetlabs.com/events/sydney-puppet-fundamentals-sydney-november2012/ http://puppetlabs.com/events/puppet-fundamentals-training-brisbane-australia/ -- 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/-/Vvq6qiJrvUMJ. 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.
