similar to: Using ruby-1.9.x with Puppet 0.25.x

Hi, I was wondering if it is possible to gain access to the nodename as a variable, in order to refer to the name or part of it inside a class. Eg: I have a lot of sites that essentially have the same configuration, except they are in different domains and have different requirements for things like resolv.conf. I can manage this by creating a node definition for each node and specifying some

Hello all, I use puppetmaster on a Debian Squeeze server (packaged from Debian 2.6.2-4) I am using a template for Debian Servers which works great for Lenny in order to update my sources.list automagically, here goes: deb http://ftp.ie.debian.org/debian <%= lsbdistcodename %> main contrib non-free deb http://security.debian.org/ <%= lsbdistcodename %>/updates main Now the problem

I am trying to streamline the current distribution specific setup and creation of VE''s within OpenVZ with puppet. My first attempt has gone horribly wrong as you will see below. Here''s the script I wrote to replace the redhat specific setup that OpenVZ used: [jleggett@lxp6d15m3 scripts]$ cat redhat-add_ip.sh #!/bin/bash # # Debug - take out later set -x

Hello, I have a file which varies depending on which OS/version it''s running. I tried to make a nested source parameter like this, but it didn''t work: source => $operatingsystem ? { Debian => "puppet://myserver.com/files/os/debian/etc/ssh/sshd_config", Gentoo => "puppet://myserver.com/files/os/gentoo/etc/ssh/sshd_config", RedHat =>

Hi @all, after upgrading my puppet server to Puppet 3.0 I got the following error every time a client connect to the server: [ pid=1532 thr=70147393710520 file=utils.rb:176 time=2012-10-08 11:17:56.504 ]: *** Exception NoMethodError in PhusionPassenger::Rack::ApplicationSpawner (undefined method `settings'' for Puppet:Module) (process 1532, thread #<Thread:0x7f98ecf7d370>):

Does anyone have any insight into this error message? err: Could not retrieve catalog from remote server: Error 400 on SERVER: The fact named fact_stomp_server does not appear to be a valid hostname. The value of '''' does not match ''^[a-zA-Z0-9.-]+$''. A common cause of this problem is running puppet agent as a normal user instead of root, or the fact is

Hi all, I am creating a recipe for rhel boxes which needs to determine what type of install is present (server or client). I thought I would use the facter fact lsbdistid for this purpose but when I run "facter lsbdistid" from the command line nothing is returned. If I just run facter and grep for lsbdistid, what I am looking for is returned. Does anyone know why this might be?

Hello guys, I would like to configure my puppet to use "yum" instead "up2date" (default RHEL4). How can I do this? :) Thanks! -- Tiago Cruz Linux User #282636 Mandriva Conectiva PRO Certified Linux Instructor --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To

Just started a rollout of centos 6.x across our Puppet deployment (100-odd servers). what fact would people suggest I use to distinguish 5.x from 6.x (quite a lot of subsystems are different between major releases)? lsb* facts don''t seem to be present on centos 6 - is this an EPEL bug, or have they just been removed in Facter? Thanks! -- You received this message because you are

Hi, I''ve writen a draft describing puppet on SuSE/opensuse linux. http://www.reductivelabs.com/trac/puppet/wiki/PuppetSuSE Any feedback is welcome. Martin

Hi, it seems that Facter 1.6.9 complains that "No LSB modules are available." on every run. This is on Ubuntu 10.04 and 12.04, probably others as well. This message (on stderr) usually comes from calling "lsb_release -v" when no additional LSB modules are installed. Facter apparently calls "lsb_release -v -s" in facter/lsbrelease.rb. This is neither fatal nor

On Tue, Dec 03, 2013 at 01:00:23PM +0000, Balraj Singh wrote: > Hi, > > I''m working on verifying TCP checksums on incoming packets in Mirage, but > I''ve run into a bit of a problem. > > If TCP checksum offload is turned on on a virtual interface (this is the > default), and if the TCP connection is local to the machine, it looks like > Xen does not

Hi all, I''m trying to get puppet working for the first time, and I''ve run into something that''s got me stumped. This is all on Solaris 10/x64. The initial startup of puppetmasterd wasn''t working, and it appeared to be related to the SSL certs not getting generated properly. I managed to trace that down to the fact that facter isn''t finding the

Hello Puppet list, I am taking over the puppet configuration of a sysadmin who left, and am having troubles deploying puppet to a new node. We are using puppet v2.7.3 both on the client and the puppetmaster, on Ubuntu 10.10. The node asks for a certificate fine, and I signed it on the puppetmaster. For the following logs extract I ve replaced the FQDN of my node by puppet.example.com. When doing

Hello, If I want to do something like this:- if $::lsbdistrelease >= 6.3 { SOMETHING } Do I have to convert lsbdistrelease from a string to a number with an inline template or some such ? Thanks Paul -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email

Hi all I?m a newbie to asterisk and I have install and configure asterisk 1.4.5 I have made some test and have face a strange behaviour I hava a simple dialplan when a call is receive from PTSN, [PSTN] exten => s,1,Answer() exten => s,2,Playback(intro-sicx) ; Listen to your voice exten => s,3,Dial(SIP/steph) exten => s,4,Hangup() I got the following when a call is

In our environ, there are several services that are deployed via an NFS mount, so that the executables and configs are consistent across the board. Is there any reason why this couldn''t be done with Puppet? For example, each individual system would contain its own /etc/puppet and rc.d and pid files -- but the primary deployment would come from NFS. For that matter, as Enterprise

I''m using puppet-0.24.8-4.el5 on CentOS 5.4. My problem is yumrepo isn''t writing the "name=" field to the repository files which causes yum to complain with the error: Repository ''local-CentOS-5.4-x86_64'' is missing name in configuration, using id I get this behavior on all of my yumrepo definitions. One of them looks like this: yumrepo {

We have resources that, from time to time, are selected to be removed (unmanaged). When it comes to ssh keys, fstab... this leaves a lot of stuff behind that we don''t want. Is there a simple way to remove the unmanaged data so we can keep the systems clean. Thanks. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post

Hi all, Is anyone successfully running/has succesfully upgraded to 2.6.32-220 from, say, 2.6.32-71.29.1? (i.e. done a normal run-of-the-mill yum update on, say a 6.0 instance all the way up cleanly to 6.2? Reason I ask is that booting into -220 (and I think also into -131 as well) results in a kernel panic for me. Some digging around and the new kernel seems to be enumerating the drives with the