Re: [Puppet Users] Nvidia driver install - condition for install

[James A. Peltier]

Check to see if an nVidia module already exists for the current kernel and if 
not build 

if [ ! -e /lib/modules/`uname -r`/kernel/drivers/video/nvidia.ko ]; then 

- Original Message -

| Hello all,

| I'd like to use puppet to install an Nvidia driver on a local
| workstation. I've written the following manifest for this puprpose:

| class nvidia_driver {
| # This will place the nvidia installer locally in /tmp. File is
| pulled from puppet.
| file { "/tmp/NVIDIA-Linux-x86_64-295.53.run" :
| source =>
| "puppet:///modules/nvidia_driver/NVIDIA-Linux-x86_64-295.53.run" ,
| ensure => present ,
| }

| # This will run the nvidia installer locally on the machine.
| exec { "/tmp/NVIDIA-Linux-x86_64-295.53.run -s -X --opengl-headers
| --no-distro-scripts --force-tls-compat32=new" : }

| }

| Upon the initial run of the manifest on the target machine,
| everything works great (although I do believe there is some room for
| improvement of the code above; particularly on the exec portion) and
| the driver then gets installed. The issue occurs on subsequent
| puppet runs on the same machine and I'm getting the following error
| during my second puppet run from the client:

| err:
| /Stage[main]/Nvidia_driver/Exec[/tmp/NVIDIA-Linux-x86_64-295.53.run
| -s -X --opengl-headers --no-distro-scripts
| --force-tls-compat32=new]/returns: change from notrun to 0 failed:
| /tmp/NVIDIA-Linux-x86_64-295.53.run -s -X --opengl-headers
| --no-distro-scripts --force-tls-compat32=new returned 1 instead of
| one of [0] at /etc/puppet/modules/nvidia_driver/manifests/init.pp:12

| It appears to me that the above error is occurring because the
| nvidia_driver class is running on each subsequent run and since the
| driver is already installed, I'm getting an exit status of 1 instead
| of 0, which to my knowledge would be expected.

| So, what I'd like to do is put some sort of condition that will look
| to see if the driver is installed and if it is, the class
| "nvidia_driver" won't run. I'm having a hard time figuring this one
| out and I was hoping to get a few opinions on how this might be
| accomplished.

| Would this potentially be a job for a shell script that does the
| checking? Maybe just adding the shell script into the
| "nvidia_driver" manifest?

| Thanks in advance for everybody's assistance and the help is very
| much appreciated.

| Cheers,

| Mike
| --
| 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/-/R9ngLgt78tMJ .
| 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.

-- 

James A. Peltier 
Manager, IT Services - Research Computing Group 
Simon Fraser University - Burnaby Campus 
Phone : 778-782-6573 
Fax : 778-782-3045 
E-Mail : jpelt...@sfu.ca 
Website : http://www.sfu.ca/itservices 
http://blogs.sfu.ca/people/jpeltier 

Success is to be measured not so much by the position that one has reached 
in life but as by the obstacles they have overcome. - Booker T. Washington 

-- 
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] can puppet-dashboard be installed on CentOS 5.4?

[Michael Stahnke]

Puppet Dashboard *can* be installed on EL 5 based systems if you've
updated Ruby to a 1.8.7 version.  By default, EL5 comes with 1.8.5
versions of ruby which have known issues with Dashboard.  If you
search the archives of this list, there are a few posts about getting
1.8.7 onto EL5 specifically for dashboard.

Mike


On Tue, Jul 3, 2012 at 1:13 PM, Hai Tao  wrote:
> Hi,
>
> I am trying to install puppet-dashboard on my puppet server, which is
> running CentOS 5.4. However, I cannot find a RPM for REHL 5 on
> http://yum.puppetlabs.com/.
>
> So the question is how I can get the  puppet-dashboard  rpm for CentOS 5.4?
> Thanks.
>
> Hai Tao
>
> --
> 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: groups dependencies at user creation

[eduardo]

 It's important to say that updssh::user_keys , updssh::check_groups
and updssh::load_ssh_key are defined resource types.


On 3 jul, 17:43, eduardo  wrote:
>  Thanks your answers.
>  I don't figure out how avoid execute because i have a massive input
> account by ENC json setting all users and membership of each one of
> them.  I had to make uniq entries array to avoid Duplicate definition
> error condition because many users could (in fact are) belong to a
> same group.
>
>  May be i miss something but i think that i can benefit from working
> with defined resource types
> (vs classes) so the same nesting call is setting dependencies
> implicitly.
>
>  For example a big picture of nesting call in my recipe is something
> like :
>
>  class updssh( $users ) -> Parameter class having json as input.
>  └── user_keys { $arrays_users:   } Call it foreach user.
>       ├── updssh::check_groups { $usr_groups: } Call it for ensure
> membership of user
>       └── updssh::load_ssh_key{ $user_ssh :     Call it to set account
> (create/update)
>
>  So I don't see dependencies like any problem because the nesting call
> is doing by self.
>  Testing are tell me that nevertheless , i'm wondering , Am i wrong ?
>
>  Even knowing it's the first version i have to confess that i'm happy
> with it because not only resolve dependencies by self but also it
> create groups that don't exist. Also i enjoy using functions like
> 'defined' which it's great to check current status.
>
>   Regards,
>    eduardo.
>
> On 3 jul, 13:57, Nan Liu  wrote:
>
>
>
>
>
>
>
> > On Tue, Jul 3, 2012 at 10:46 AM, Tim Mooney  wrote:
> > > In regard to: [Puppet Users] Re: groups dependencies at user creation,...:
>
> > >> Thanks tim for answer me, The fact is $groups is an array, so when i
> > >> try something like this
>
> > >> --
> > >>            Group[$groups] -> User[$username]
>
> > >>            user { $username:
> > >>                    comment => "$email",
> > >>                    home    => "/home/$username",
> > >>                    shell   => "/bin/bash",
> > >>                    password => "!!",
> > >>                    groups  => $groups
> > >>            }
>
> > >> --
>
> > >> I'd got :
>
> > >> err: Could not retrieve catalog from remote server: Error 400 on
> > >> SERVER: Could not find resource 'Group[sudo]Group[admin]Group[deploy]'
> > >> for relationship on 'User[ppuser7]' on node casa
>
> > > I was afraid that might be the case, but thought it was worth a try.
>
> > > Does this work better:
>
> > >         $groups_as_array = split($groups, ',')
> > >         Groups[$groups_as_array] -> User[$username]
>
> > AFAIK, the short hand syntax doesn't support array values, and you
> > need something like a define resource type to wrap this.
>
> > define group_dep($username) {
> >    Groups[$name] -> User[$username]
>
> > }
>
> > group_dep { $group_as_array :
> >   username => $username,
>
> > }
>
> > Nan

-- 
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] hiera questions

[Wolf Noble]

This thought crossed our minds as well.

I created the following feature request awhile back:

https://projects.puppetlabs.com/issues/13934#change-60706

the intent behind which is "if this fact is flagged as immutable, and it 
changes, something is drastically wrong… (don't)? do something"


until something along those lines is implemented, however, the following works 
reasonably well:


the client/puppet master communication is wrapped around the base layer of 
trust of the ssl cert's CN.

if you use that name to perform a lookup against an accessory lookup table 
before feeding hiera, this will accommodate most environments 'bootstrappy' 
needs… i.e.:

certname: fooweb.product1.somesite.com
  role: webserver
  tier: qa
  environment: product1
  etc…


your lookup table is outside of the client's control, so it cannot change these 
pieces of information. It also can not easily change it's certname…

this provides a reasonable amount of security, and flexibility… I'd prefer to 
set a handful of facts that I know are 'correct' at system install time and not 
perform extra puppet master work at manifest compilation time, but that's just 
me.

W


On Jul 2, 2012, at 2:57 PM, Jan Ivar Beddari wrote:

On 02. juli 2012 17:26, Darryl Wisneski wrote:
modules I can use hiera to call up my hash and create ruby/puppet
functions to do the server host location and functional logic based
on the default facter facts of hostname and operatingsystem reported
by the server host themselves.  All the configuration remains in
hiera and the module manifests remain puppet business logic.

Comments?

Off list as I'm too lazy to write in length and explain it all ;-)

Do you care that the node (i.e root on the server) is able to say anything at 
all about its role and location? If you place a fact on the system that says 
what it is it could lie.

What I'm getting at is security.

I've designed my own hiera setup so that I don't use ANY host-derived facts, at 
all. The only thing I can be (relatively) sure of on the puppetmaster is that 
clientcert is what it says it is.

In a multi-tenant scenario (or easier even, in a scenario where all your 
servers have a common root password) where would you place your source of truth?

Don't know if you see this or care but still fired this off.


best,
Jan Ivar Beddari
Linux/Mac architect University of Bergen, Norway



--
http://www.uib.no/personer/Jan.Ivar.Beddari


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





This message may contain confidential or privileged information. If you are not 
the intended recipient, please advise us immediately and delete this message. 
See http://www.datapipe.com/legal/email_disclaimer/ for further information on 
confidentiality and the risks of non-secure electronic communication. If you 
cannot access these links, please notify us by reply message and we will send 
the contents to you.

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

[Lorenzo Salvadorini]

>
> Additionally, when I try to use an rdoc type I either am not getting any
> output or can't find it.
>
> $puppet doc -m rdoc --manifestdir /etc/puppet/environments/test/manifests/
> --modulepath /etc/puppet/environments/test/modules/ --outputdir
> /home//puppetdoc/rdoc/ /etc/puppet/environments/test/manifests/
>
> ~/puppetdoc/rdoc$ ls -a
>
>
 I update my documentation on an hourly basis with something like:

/usr/bin/puppet doc --all --outputdir=$DOCDIR --mode rdoc
--modulepath=$MODULEPATH

Are you missing the --all parameter?

-- 
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: groups dependencies at user creation

[eduardo]

 Thanks your answers.
 I don't figure out how avoid execute because i have a massive input
account by ENC json setting all users and membership of each one of
them.  I had to make uniq entries array to avoid Duplicate definition
error condition because many users could (in fact are) belong to a
same group.

 May be i miss something but i think that i can benefit from working
with defined resource types
(vs classes) so the same nesting call is setting dependencies
implicitly.

 For example a big picture of nesting call in my recipe is something
like :

 class updssh( $users ) -> Parameter class having json as input.
 └── user_keys { $arrays_users:   } Call it foreach user.
      ├── updssh::check_groups { $usr_groups: } Call it for ensure
membership of user
  └── updssh::load_ssh_key{ $user_ssh : Call it to set account
(create/update)

 So I don't see dependencies like any problem because the nesting call
is doing by self.
 Testing are tell me that nevertheless , i'm wondering , Am i wrong ?

 Even knowing it's the first version i have to confess that i'm happy
with it because not only resolve dependencies by self but also it
create groups that don't exist. Also i enjoy using functions like
'defined' which it's great to check current status.


  Regards,
   eduardo.


On 3 jul, 13:57, Nan Liu  wrote:
> On Tue, Jul 3, 2012 at 10:46 AM, Tim Mooney  wrote:
> > In regard to: [Puppet Users] Re: groups dependencies at user creation,...:
>
> >> Thanks tim for answer me, The fact is $groups is an array, so when i
> >> try something like this
>
> >> --
> >>            Group[$groups] -> User[$username]
>
> >>            user { $username:
> >>                    comment => "$email",
> >>                    home    => "/home/$username",
> >>                    shell   => "/bin/bash",
> >>                    password => "!!",
> >>                    groups  => $groups
> >>            }
>
> >> --
>
> >> I'd got :
>
> >> err: Could not retrieve catalog from remote server: Error 400 on
> >> SERVER: Could not find resource 'Group[sudo]Group[admin]Group[deploy]'
> >> for relationship on 'User[ppuser7]' on node casa
>
> > I was afraid that might be the case, but thought it was worth a try.
>
> > Does this work better:
>
> >         $groups_as_array = split($groups, ',')
> >         Groups[$groups_as_array] -> User[$username]
>
> AFAIK, the short hand syntax doesn't support array values, and you
> need something like a define resource type to wrap this.
>
> define group_dep($username) {
>    Groups[$name] -> User[$username]
>
> }
>
> group_dep { $group_as_array :
>   username => $username,
>
> }
>
> Nan

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

[Puppet Users] can puppet-dashboard be installed on CentOS 5.4?

[Hai Tao]

Hi,

I am trying to install puppet-dashboard on my puppet server, which is
running CentOS 5.4. However, I cannot find a RPM for REHL 5 on
http://yum.puppetlabs.com/.

So the question is how I can get the  puppet-dashboard  rpm for CentOS 5.4?
Thanks.

Hai Tao

-- 
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] Problem during setting password for user, using puppet provisioner of Vagrant

[jcbollinger]

On Monday, July 2, 2012 2:24:15 PM UTC-5, Brian Gupta wrote:
>
> On Mon, Jul 2, 2012 at 11:10 AM, nikosd23  wrote: 
> > Hi, 
> > 
> > I am trying to set the password for a user that I have created using the 
> > puppet provisioner of Vagrant for a Linux version 2.6.32-71.el6.x86_64 
> Red 
> > Hat 4.4.4-13 box. 
> > 
> > I have tried both approaches: 
> > 
> > Approach1 
> > user { "test": 
> > ensure   => present, 
> > shell=> "/bin/bash", 
> > password => "encrypted_password_generated_by_passwd_command", 
> > managehome => true, 
> > } 
>
> This is the approach I would take, but you need libshadow-ruby 
> installed for it to work. 
>

Also, it's a good idea to use single quotes around the password hash 
instead of double quotes.  Password hashes have an unfortunate tendency to 
include '$' characters, which Puppet will tend to try to interpret as a 
variable reference except when the string is single-quoted.

In fact, it's a good idea to always use single quotes in your Puppet 
manifests except where you specifically want variable interpolation.


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/-/-CMO2v9TEqcJ.
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 ordered hashes

[jcbollinger]

On Monday, July 2, 2012 3:42:34 PM UTC-5, Jeremy Carroll wrote:
>
> During DevOpsDays it was brought up that there may be a patch for ordered 
> hashes with Hiera. Without this patch, all of my catalogs are compiled in 
> random order. Any links to a patch that I can back-port, or a commit #?


I know nothing about the Hiera modifications you are asking about, but I 
would like to suggest that you consider writing classes so that they are 
insensitive to the order they are declared.  A manifest set written in this 
way is much more resilient and easier to maintain than one that requires *
you* to find a suitable order in which to declare classes.  It's good no 
matter what mechanism you use to declare classes (direct, hiera, ENC, ...).

This is entirely possible -- not even all that hard -- provided that you 
avoid the parametrized-class syntax for declaring classes, and instead use 
good old 'include' (or 'require').  You must also avoid constructs that are 
inherently parse-order dependent, most notably using the 'defined' function 
to determine whether a class has been declared for the target node.  Then 
have every class start by 'include'ing each other class on which it has 
direct parse-order dependencies, and you should be good to go.

Avoiding parametrized-class declaration syntax has always been a good 
idea.  Even if using external data (e.g. from hiera) were not a technically 
superior design, Puppet's parametrized class declaration syntax has serious 
technical problems attending it (not least that it does not in general 
allow classes to declare their dependencies).  Puppet 3 ties class 
parameters to hiera, which provides a way forward for shops that have 
invested heavily in class parametrization.  It also has documentary and 
convenience advantages.


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/-/J8-qmX1ZPFwJ.
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 can't successfully restart puppetd

[Steve Traylen]

On Wednesday, 27 June 2012 11:31:17 UTC+2, Felix.Frank wrote:
>
> On 06/27/2012 11:19 AM, Matthew Burgess wrote: 
> >> We redefined the restart command: 
> >> > 
> >> > restart => '/usr/bin/nohup /etc/init.d/puppet restart &' 
> > Nice!  Thanks very much, Martin, that works really nicely. 
>
>
Before I blindly try this how does the above work... 

I call this midway through a puppet run and it does no harm to the current 
run but 
loads new configuration for next run. Is that what happens? 

Steve. 
 

> Yeah, this looks really slick. Thanks for sharing. 
>

-- 
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/-/K60PncD0EqMJ.
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] Unable to Install puppet Master

[Matthaus Litteken]

The jdk rpm provides jdk of version 2000:1.6.0_33-fcs.
pe-tanukiwrapper requires java of >= 1.5.0, which the jdk does not
provide. The pe-virtual-java package supplies with el versions of PE
can help in overcoming this, as it provides java (it is explained
better here: 
http://docs.puppetlabs.com/pe/2.5/install_basic.html#vendor-packages).

[root@localhost]# rpm -qp --provides jdk-6u33-linux-amd64.rpm
jaxp_parser_impl
xml-commons-apis
jdk = 2000:1.6.0_33-fcs

[root@localhost el-5-x86_64]# rpm -qp --requires
pe-tanukiwrapper-3.5.9-5.pe.el5.x86_64.rpm
java >= 1.5.0
pe-puppet-enterprise-release
rpmlib(PayloadFilesHavePrefix) <= 4.0-1
rpmlib(CompressedFileNames) <= 3.0.4-1

[root@localhost el-5-x86_64]# rpm -qp --provides
pe-virtual-java-1.0-1.pe.el5.noarch.rpm
java = 1.6.0
jdk = 1.6.0
jre = 1.6.0
pe-virtual-java = 1.0-1.pe.el5


HTH
matthaus

On Tue, Jul 3, 2012 at 10:49 AM, RAM  wrote:
> I was experiencing the same problem.
>
> I installed java by executing jdk-6u33-linux-x64-rpm.bin. After the
> execution "rpm -qa | grep java" showed the below:
>
> sun-javadb-docs-10.6.2-1.1
> sun-javadb-client-10.6.2-1.1
> sun-javadb-core-10.6.2-1.1
> sun-javadb-javadoc-10.6.2-1.1
> sun-javadb-common-10.6.2-1.1
> sun-javadb-demo-10.6.2-1.1
>
> and rpm -qa | grep jdk showed:
>
> jdk-1.6.0_33-fcs
>
> Are they looking alright or something missing?
>
> On Thursday, May 31, 2012 7:40:28 AM UTC-5, Trevor Vaughan wrote:
>>
>> What does rpm -qa | grep java give you?
>>
>> If you installed Java from a tar source, then it wouldn't update your
>> RPM database and actually meet the RPM requirements.
>>
>> Your alternatives are to download a version of Java in RPM form that
>> meets your requirements, roll your own stub RPM, or use --nodeps (if
>> using 'rpm' not 'yum').
>>
>> Trevor
>>
>> On Thu, May 31, 2012 at 3:25 AM, Jeeva  wrote:
>> > Hi,
>> >  I was trying to instal puppet-enterprise-2.5.1-el-5-x86_64 in RHEL-
>> > 5.3
>> > machine. But got below error.
>> >
>> > ## Installing packages from files...
>> > error: Failed dependencies:
>> >        java >= 1.5.0 is needed by pe-
>> > tanukiwrapper-3.5.9-5.pe.el5.x86_64
>> >
>> > ===
>> > =
>> > !! ERROR: Could not install packages from files; see messages above
>> > for cause.
>> >
>> > ###
>> >
>> >
>> >
>> > BUT,
>> >
>> > 1. Then I checked my java version which is > what is required.
>> >    java -version
>> > java version "1.6.0_29"
>> > Java(TM) SE Runtime Environment (build 1.6.0_29-b11)
>> > Java HotSpot(TM) 64-Bit Server VM (build 20.4-b02, mixed mode)
>> >
>> > 2. I'm trying to install puppet master, console and puppet agent in
>> > same machine as i want to test it before I move it to prod.
>> >
>> > Kindly help..
>> >
>>
>> --
>> Trevor Vaughan
>> Vice President, Onyx Point, Inc
>> (410) 541-6699
>> tvaug...@onyxpoint.com
>>
>> -- This account not approved for unencrypted proprietary information --
>
> --
> 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/-/mUywqh-PWTMJ.
>
> 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.



-- 
Matthaus Litteken
Release Manager, 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] Unable to Install puppet Master

[RAM]

I was experiencing the same problem.
 
I installed java by executing jdk-6u33-linux-x64-rpm.bin. After the 
execution "rpm -qa | grep java" showed the below:
 
sun-javadb-docs-10.6.2-1.1
sun-javadb-client-10.6.2-1.1
sun-javadb-core-10.6.2-1.1
sun-javadb-javadoc-10.6.2-1.1
sun-javadb-common-10.6.2-1.1
sun-javadb-demo-10.6.2-1.1
 
and rpm -qa | grep jdk showed:
 
jdk-1.6.0_33-fcs
 
Are they looking alright or something missing? 

On Thursday, May 31, 2012 7:40:28 AM UTC-5, Trevor Vaughan wrote:

> What does rpm -qa | grep java give you? 
>
> If you installed Java from a tar source, then it wouldn't update your 
> RPM database and actually meet the RPM requirements. 
>
> Your alternatives are to download a version of Java in RPM form that 
> meets your requirements, roll your own stub RPM, or use --nodeps (if 
> using 'rpm' not 'yum'). 
>
> Trevor 
>
> On Thu, May 31, 2012 at 3:25 AM, Jeeva  wrote: 
> > Hi, 
> >  I was trying to instal puppet-enterprise-2.5.1-el-5-x86_64 in RHEL- 
> > 5.3 
> > machine. But got below error. 
> > 
> > ## Installing packages from files... 
> > error: Failed dependencies: 
> >java >= 1.5.0 is needed by pe- 
> > tanukiwrapper-3.5.9-5.pe.el5.x86_64 
> > 
> === 
> > = 
> > !! ERROR: Could not install packages from files; see messages above 
> > for cause. 
> > 
> > ### 
> > 
> > 
> > 
> > BUT, 
> > 
> > 1. Then I checked my java version which is > what is required. 
> >java -version 
> > java version "1.6.0_29" 
> > Java(TM) SE Runtime Environment (build 1.6.0_29-b11) 
> > Java HotSpot(TM) 64-Bit Server VM (build 20.4-b02, mixed mode) 
> > 
> > 2. I'm trying to install puppet master, console and puppet agent in 
> > same machine as i want to test it before I move it to prod. 
> > 
> > Kindly help.. 
> > 
>
> -- 
> Trevor Vaughan 
> Vice President, Onyx Point, Inc 
> (410) 541-6699 
> tvaug...@onyxpoint.com 
>
> -- This account not approved for unencrypted proprietary information -- 
>

-- 
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/-/mUywqh-PWTMJ.
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] java dependency error in installing pupeet enterprise

[RAM]

Hi Everybody,
 
I was trying to install puppet-enterprise-2.5.1-el-5-x86_64 master on my 
linux box:
 
Linux SERVERX3 2.6.18-274.el5 #1 SMP Fri Jul 8 17:36:59 EDT 2011 x86_64 
x86_64 x86_64 GNU/Linux
 
I was following the steps as in 
http://docs.puppetlabs.com/pe/2.5/install_basic.html. But I run into the 
below error:
 
error: Failed dependencies:
java >= 1.5.0 is needed by pe-tanukiwrapper-3.5.9-5.pe.el5.x86_64
 
I had RPM installed java 1.6.0_33; and a "rpm -qa | grep java" showed:
 
serverx3>
 
rpm -qa | grep java
sun-javadb-docs-10.6.2-1.1
sun-javadb-client-10.6.2-1.1
sun-javadb-core-10.6.2-1.1
sun-javadb-javadoc-10.6.2-1.1
sun-javadb-common-10.6.2-1.1
sun-javadb-demo-10.6.2-1.1
 
Any idea as what might have missed and what could be donw to correct?
 
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/-/245ADZ3bE94J.
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: groups dependencies at user creation

[Nan Liu]

On Tue, Jul 3, 2012 at 10:46 AM, Tim Mooney  wrote:
> In regard to: [Puppet Users] Re: groups dependencies at user creation,...:
>
>
>> Thanks tim for answer me, The fact is $groups is an array, so when i
>> try something like this
>>
>> --
>>Group[$groups] -> User[$username]
>>
>>user { $username:
>>comment => "$email",
>>home=> "/home/$username",
>>shell   => "/bin/bash",
>>password => "!!",
>>groups  => $groups
>>}
>>
>> --
>>
>> I'd got :
>>
>> err: Could not retrieve catalog from remote server: Error 400 on
>> SERVER: Could not find resource 'Group[sudo]Group[admin]Group[deploy]'
>> for relationship on 'User[ppuser7]' on node casa
>
>
> I was afraid that might be the case, but thought it was worth a try.
>
> Does this work better:
>
> $groups_as_array = split($groups, ',')
> Groups[$groups_as_array] -> User[$username]

AFAIK, the short hand syntax doesn't support array values, and you
need something like a define resource type to wrap this.

define group_dep($username) {
   Groups[$name] -> User[$username]
}

group_dep { $group_as_array :
  username => $username,
}

Nan

-- 
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: groups dependencies at user creation

[Tim Mooney]

In regard to: [Puppet Users] Re: groups dependencies at user creation,...:


Thanks tim for answer me, The fact is $groups is an array, so when i
try something like this

--
   Group[$groups] -> User[$username]

   user { $username:
   comment => "$email",
   home=> "/home/$username",
   shell   => "/bin/bash",
   password => "!!",
   groups  => $groups
   }

--

I'd got :

err: Could not retrieve catalog from remote server: Error 400 on
SERVER: Could not find resource 'Group[sudo]Group[admin]Group[deploy]'
for relationship on 'User[ppuser7]' on node casa


I was afraid that might be the case, but thought it was worth a try.

Does this work better:

$groups_as_array = split($groups, ',')
Groups[$groups_as_array] -> User[$username]

?  I have my doubts, but it's what I would try next.

Note that split() is part of the default set of functions that are part
of puppet.  For more info on functions, see

http://docs.puppetlabs.com/references/stable/function.html

Tim
--
Tim Mooney tim.moo...@ndsu.edu
Enterprise Computing & Infrastructure  701-231-1076 (Voice)
Room 242-J6, IACC Building 701-231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164

--
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: groups dependencies at user creation

[eduardo]

Dears all, I'd got a solution , far away from the best because it's
based on execute method and also because it's not use Group[$groups] -
> User[$username] dependencies way.

 Testing something like this are good :


  $a_groups = inline_template(
  "<% groups.each do |grp| -%> <%= username %>_<%= grp %>,<
% end -%>")

  $usr_groups = split($a_groups, ',')

  updssh::check_groups { $usr_groups: }


  -

  define updssh::check_groups {
$arr = split($title, '_')
 $usr = $arr[0]
 $group = $arr[1]

 if ! defined(Group[$group]) {

group { $group:
ensure => present
}
 }
   }

 I'm pretty sure it's a first one version that it's giving to me a
chance to go on.


  Best Regards,
   eduardo.

On 2 jul, 17:06, eduardo  wrote:
>  Thanks tim for answer me, The fact is $groups is an array, so when i
> try something like this
>
> --
>             Group[$groups] -> User[$username]
>
>             user { $username:
>                     comment => "$email",
>                     home    => "/home/$username",
>                     shell   => "/bin/bash",
>                     password => "!!",
>                     groups  => $groups
>             }
>
> --
>
>  I'd got :
>
>  err: Could not retrieve catalog from remote server: Error 400 on
> SERVER: Could not find resource 'Group[sudo]Group[admin]Group[deploy]'
> for relationship on 'User[ppuser7]' on node casa
>
>  Is there any way to work around ?.
>
>   Regards,
>     eduardo.
>
> On 2 jul, 13:20, Tim Mooney  wrote:
>
>
>
>
>
>
>
> > In regard to: [Puppet Users] groups dependencies at user creation, 
> > eduardo...:
>
> > >  I'm trying to create new users members of some groups so it's need
> > > to ensure they exist before user creation.
>
> > >  I have something like :
>
> > > 
> > > define updssh::add_user ( $email , $groups  ) {
>
> > >            $username = $title
>
> > >            user { $username:
> > >                    comment => "$email",
> > >                    home    => "/home/$username",
> > >                    shell   => "/bin/bash",
> > >                    password => "!!",
> > >                    groups  => $groups
> > >            }
>
> > > --
>
> > >  How to ensure groups dependencies at user creation ?.
>
> > If you were just talking about the user's default group, then it would
> > be one of the few cases where puppet establishes an ordering relation
> > for you automatically.  In other words:
>
> >    user { 'foo':
> >      gid => 'bar',
> >    }
>
> > automatically ensures that group 'bar' is present before user 'foo'.
>
> > I don't know if that same thing is true for supplemental groups, but if
> > it's not, I would first try using the -> notation to establish ordering,
> > like this
>
> >    Group[$groups] -> User[$username]
>
> > Does that work for you?
>
> > Tim
> > --
> > Tim Mooney                                             tim.moo...@ndsu.edu
> > Enterprise Computing & Infrastructure                  701-231-1076 (Voice)
> > Room 242-J6, IACC Building                             701-231-8541 (Fax)
> > North Dakota State University, Fargo, ND 58105-5164

-- 
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] Modules Question

[Worker Bee]

yes! that clarified things!  I get it now and realize it was a silly
question... light bulb is now on!

Thank you and have a great weekend!



On Tue, Jul 3, 2012 at 12:50 PM, Craig Dunn  wrote:

>
>  However, this leaves me puzzled that I may not fully understand the way
>> stored configs/modules work.
>>
>> I have another module that does not have an init.pp and it works??
>>
>>
>> class user::virtual
>> {
>>
>
> init.pp is not mandatory for a module per se, but it is the place the
> autoloader will look for a class named "user" - in this example, you don't
> have a user class, just a user::virtual class, so..
>
> include user::virtual
>
> ... will direct the autoloader to look in /user/manifests/**
> virtual.pp
>
> If you were to want to add a class named user, you would put this in a
> file called init.pp.
>
> Does that make more sense?
>
> Craig
>
> --
> Craig Dunn
> Professional Services
> Puppet Labs Inc.
> http://www.puppetlabs.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+unsubscribe@**
> 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] Modules Question

[Craig Dunn]

However, this leaves me puzzled that I may not fully understand the 
way stored configs/modules work.


I have another module that does not have an init.pp and it works??


class user::virtual
{


init.pp is not mandatory for a module per se, but it is the place the 
autoloader will look for a class named "user" - in this example, you 
don't have a user class, just a user::virtual class, so..


include user::virtual

... will direct the autoloader to look in 
/user/manifests/virtual.pp


If you were to want to add a class named user, you would put this in a 
file called init.pp.


Does that make more sense?
Craig

--
Craig Dunn
Professional Services
Puppet Labs Inc.
http://www.puppetlabs.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.

Re: [Puppet Users] Modules Question

[Worker Bee]

Craig;
Thank you for your repl(ies)!

However, this leaves me puzzled that I may not fully understand the way
stored configs/modules work.

I have another module that does not have an init.pp and it works??


class user::virtual
{
@user {fabauto:
ensure => present,
comment => "FabricAutomation_account"}

@user {graham: ensure => present}
@user {steven: ensure => present}
@user {grace: ensure => present}
}

__

node 'default' {
  include test
  include motd
  #include sudoers
  include user::virtual
  include user::developers
  include ssh::hostkeys
  include ssh::knownhosts
  }


Thanks so much for the help!


On Tue, Jul 3, 2012 at 12:34 PM, Craig Dunn  wrote:

> On 03/07/2012 17:28, Worker Bee wrote:
>
>> When writing modules, is it required that then entry point be named
>> init.pp?
>>
>> I have written a module and if I try to call the module via nodes.pp from
>> a file named other than init.pp, I get an error that the module cannot be
>> found.  If I rename the file to init.pp, it works fine.
>>
>> So, can someone clarify, is the naming of the file a requirement?
>>
>> ssh.pp
>>
>> class ssh::hostkeys{
>>
> Yes, the autoloader will look in init.pp for the class named "modulename"
> and will look for modulename::subclassname in subclassname.pp... eg:
>
> # manifests/init.pp
>  class ssh {
>
> # manifests/hostkeys.pp
>   class ssh::hostkeys {
>
> Craig
>
> --
> Craig Dunn
> Professional Services
> Puppet Labs Inc.
> http://www.puppetlabs.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+unsubscribe@**
> 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] Modules Question

[Craig Dunn]

On 03/07/2012 17:28, Worker Bee wrote:
When writing modules, is it required that then entry point be named 
init.pp?


I have written a module and if I try to call the module via nodes.pp 
from a file named other than init.pp, I get an error that the module 
cannot be found.  If I rename the file to init.pp, it works fine.


So, can someone clarify, is the naming of the file a requirement?

ssh.pp

class ssh::hostkeys{
Yes, the autoloader will look in init.pp for the class named 
"modulename" and will look for modulename::subclassname in 
subclassname.pp... eg:


# manifests/init.pp
 class ssh {

# manifests/hostkeys.pp
  class ssh::hostkeys {

Craig

--
Craig Dunn
Professional Services
Puppet Labs Inc.
http://www.puppetlabs.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] Modules Question

[Worker Bee]

When writing modules, is it required that then entry point be named init.pp?

I have written a module and if I try to call the module via nodes.pp from a
file named other than init.pp, I get an error that the module cannot be
found.  If I rename the file to init.pp, it works fine.

So, can someone clarify, is the naming of the file a requirement?

ssh.pp

class ssh::hostkeys{
@@sshkey { "${fqdn}_dsa":
host_aliases  => [ "$fqdn", "$hostname", "$ipaddress" ],
type  => dsa,
key   => $sshdsakey,
}
@@sshkey { "${fqdn}_rsa":
host_aliases  => [ "$fqdn", "$hostname", "$ipaddress" ],
type  => rsa,
key   => $sshrsakey,
}
Sshkey <<| |>>
}


_

init.pp


class ssh::hostkeys{
@@sshkey { "${fqdn}_dsa":
host_aliases  => [ "$fqdn", "$hostname", "$ipaddress" ],
type  => dsa,
key   => $sshdsakey,
}
@@sshkey { "${fqdn}_rsa":
host_aliases  => [ "$fqdn", "$hostname", "$ipaddress" ],
type  => rsa,
key   => $sshrsakey,
}
Sshkey <<| |>>
}
_

nodes.pp

node 'default' {

  include test
  include motd
  #include sudoers
  include user::virtual
  include user::developers
  include ssh::hostkeys
  include ssh::knownhosts
  }

-- 
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] puppet doc problem.

[llow...@oreillyauto.com]

I'm trying to get some docs using puppet doc, and I'd like to get the PDF 
format.

So, following the example in 'puppet help doc' I did the following:

$ puppet doc -m pdf -r configuration
creating pdf
Could not run: wrong number of arguments (1 for 2)


Additionally, when I try to use an rdoc type I either am not getting any 
output or can't find it.

$puppet doc -m rdoc --manifestdir /etc/puppet/environments/test/manifests/ 
--modulepath /etc/puppet/environments/test/modules/ --outputdir 
/home//puppetdoc/rdoc/ /etc/puppet/environments/test/manifests/

~/puppetdoc/rdoc$ ls -a
.  ..


Trying this on my puppet master, which is running 2.7.14 on Lucid

What am I doing wrong?

-- 
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/-/a8lkRUX1Om4J.
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] Style Guide question

[Nan Liu]

On Tue, Jul 3, 2012 at 7:53 AM, llow...@oreillyauto.com
 wrote:
> Is there an ETA for getting the Style Guide up to date for 2.7.x or even
> 3.X?
>
> Currently it is geared towards the 2.6.X line, and says that certain things
> should not be done due to 2.6.x compatibility issues.
>
> For example, it says to use this:
>
> class ntp(
>   $server = 'UNSET'
> ) {
>
>   include ntp::params
>
>   $server_real = $server ? {
> 'UNSET' => $::ntp::params::server,
> default => $server,
>   }
>
>   notify { 'ntp':
> message => "server=[$server_real]",
>   }
>
> }
>
> and not:
>
> class ntp(
>   $server = $ntp::params::server
> ) inherits ntp::params {
>
> notify { 'ntp':
>   message => "server=[$server]",
> }
>
> }
>
> Now to me, the second one is much easier to read.
>
> Is the fact that the second one won't work in 2.6.x the ONLY reason not to
> do something like that?

TLDR; unless you need to know someone provided an undef value, you
don't need this pattern.

The second example you provided should work with 2.6.x. The 'UNSET'
pattern is typically used to differentiate between user provided undef
and a variable that's undefined.

Here's a horribly contrived example. Source and template are exclusive
for file, and I would like to use source if it's specified, set source
to undef if user provides content, and specify a default source value
if the user doesn't provide source or content:

define myfile (
  $source,
  $content ) {

  if $source {
$mysource = $source
  } elsif $content {
$mysource = undef
  } else {
$mysource = "puppet:///modules/${caller_module_name}/${name}"
  }
...
}

However if the user ever supplied:

myfile { 'serv.conf':
  content => undef,
}

I have no way to test if the user provided undef using the first
example and it will use my default source instead. I have to do
something pretty hideous:

define myfile (
  source,
  content = 'UNSET' ) {
  if $source {
$mysource = $source
  } elsif $content =='UNSET' {
$mysource = "puppet:///modules/${caller_module_name}/${name}"
  } else {
$mysource = undef
  }
...
}

I cringe when I see it, but I understand the problem it's trying to solve.

HTH,

Nan

-- 
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] Stored Configs Question

[JA]

Thanks!



On Tue, Jul 3, 2012 at 11:24 AM, Craig Dunn  wrote:

> On 03/07/2012 16:18, Worker Bee wrote:
>
>> Hi Everyone;
>>
>> I have installed and configured stored configs using mysql. But, I am a
>> bit confused about how it works.  I was my understanding that only
>> resources prefaced with "@@" would be collected and stored. However, if is
>> run 'select * from resources;', I get everything included in all modules.
>>
>> Could someone help clarify this for me?
>>
>
> By default storeconfigs will store every resource which can add quite a
> bit of extra load on a puppet run (prior to PuppetDB) -  if you're using
> storeconfigs solely for exported resources then you can enable
> thin_storeconfigs = true in your puppet.conf which will then make it behave
> as you're expecting it to by only storing resources that you explicitly
> export with @@.
>
> Craig
>
> --
> Craig Dunn
> Professional Services
> Puppet Labs Inc.
> http://www.puppetlabs.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+unsubscribe@**
> 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] Stored Configs Question

[Craig Dunn]

On 03/07/2012 16:18, Worker Bee wrote:

Hi Everyone;

I have installed and configured stored configs using mysql. But, I am 
a bit confused about how it works.  I was my understanding that only 
resources prefaced with "@@" would be collected and stored. However, 
if is run 'select * from resources;', I get everything included in all 
modules.


Could someone help clarify this for me?


By default storeconfigs will store every resource which can add quite a 
bit of extra load on a puppet run (prior to PuppetDB) -  if you're using 
storeconfigs solely for exported resources then you can enable 
thin_storeconfigs = true in your puppet.conf which will then make it 
behave as you're expecting it to by only storing resources that you 
explicitly export with @@.


Craig

--
Craig Dunn
Professional Services
Puppet Labs Inc.
http://www.puppetlabs.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] Stored Configs Question

[Worker Bee]

Hi Everyone;

I have installed and configured stored configs using mysql. But, I am a bit
confused about how it works.  I was my understanding that only resources
prefaced with "@@" would be collected and stored.  However, if is run
'select * from resources;', I get everything included in all modules.

Could someone help clarify this for me?

Thank you

-- 
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] Error 400 on SERVER: invalid value for Integer

[Kmbu]

Thanks for your support! It's actually Puppet 2.7.6. Not sure what this 
means in terms of finding a solution, though.

On Friday, 29 June 2012 19:16:23 UTC+2, Eric Sorenson wrote:
>
> I saw this in the past, and the encoded data was the fact upload from the 
> client, which for some reason is malformed/corrupted by the time it hits 
> the master.
>
> What version of puppet are you running? I'm guessing a 2.6 series; 2.7 
> moves this data to POST body rather than GET (Bug #6117 in redmine) 
> precisely to fix this sort of thing.
>
> If this is on 2.7.x that would be troubling.
>
> -=Eric
>
> On Friday, June 29, 2012 8:26:48 AM UTC-7, Kmbu wrote:
>>
>> Maybe I'm doing something wrong, but I snooped some traffic and actually 
>> caught a successful and a failed request, but it's all in HTTPS so not 
>> really readable in order to compare. Any ideas?
>>
>> On Thursday, 28 June 2012 12:18:36 UTC+2, Felix.Frank wrote:
>>>
>>> Hi, 
>>>
>>> On 06/28/2012 12:12 PM, Kmbu wrote: 
>>> > But if it were a server-side issue, why would the error code be 400 
>>> (bad 
>>> > request)? 
>>>
>>> well, any HTTP server can issue 400 codes whenever it pleases, puppet is 
>>> not obliged to restrict the code to broken request headers. 
>>>
>>> That being said, you can of course start your debugging based on the 
>>> thesis that puppetlabs have been paying attention and adhering to the 
>>> rule. 
>>>
>>> You could then e.g. just start wiresharking all your agent requests and 
>>> once you trigger the error, compare the request to an unbroken one. 
>>>
>>> Cheers, 
>>> Felix 
>>>
>>

-- 
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/-/EmQ8Y9vNW3EJ.
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] Style Guide question

[llow...@oreillyauto.com]

Is there an ETA for getting the Style Guide up to date for 2.7.x or even 
3.X?

Currently it is geared towards the 2.6.X line, and says that certain things 
should not be done due to 2.6.x compatibility issues.

For example, it says to use this:

class ntp(
  $server = 'UNSET'
) {

  include ntp::params

  $server_real = $server ? {
'UNSET' => $::ntp::params::server,
default => $server,
  }

  notify { 'ntp':
message => "server=[$server_real]",
  }

}

and not:

class ntp(
  $server = $ntp::params::server) inherits ntp::params {

notify { 'ntp':
  message => "server=[$server]",
}
}

Now to me, the second one is much easier to read.

Is the fact that the second one won't work in 2.6.x the ONLY reason not to do 
something like that?



-- 
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/-/5ZXmhp_7cDMJ.
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] PuppetCamp Dublin this Friday 6th July 2012

[Giuseppe Futia]

Dear Simon,

the meeting will be available in streaming?

Thank you,

Giuseppe

2012/7/3 Simon McCartney 

> http://puppetcampdublin.eventbrite.com/
> http://lanyrd.com/2012/puppet-camp-dublin/
>
> PuppetCamp Dublin, in conjunction with Engineers Ireland Computing
> Division:
>
> Puppet Camp is a community oriented gathering of Puppet users and
> developers. You’ll have the opportunity to network with a diverse group of
> Puppet users, benefit from insightful lectures delivered by prominent
> community members, and be able to share experiences and discuss potential
> implementations of Puppet during our attendee generated breakout sessions.
>
> *Schedule*
>
> *10:00am -* Checkin and Opening Remarks from Puppet Labs Co-founder Teyo
> Tyree
>
> *10:40am - *Roland Tritsch - VP Technical Operations, Gilt Groupe
>
> Building a continuous delivery platform for the biggest spike in e-commerce
>
> *11:20: *Ruaidhri Power, DemonWare
>
> This talk will describe the evolution of how we've used Puppet at Demonware,
> a subsidiary of Activision Blizzard, to run the infrastructure of some of
> the world's biggest games, supporting millions of concurrent users for
> titles such as Call of Duty.
>
> *12:00pm - *Break & Lunch**
>
> *1:00pm - *Stephen Connolly,Elite Developer and Architect,* *CloudBees
>
> Continuous Deployment with Jenkins
>
> *2:00pm**-*   CloudSmith 
>
> Develop, test and publish modules to the Forge with Geppetto. Stack,
> validate and deploy them with Stack Hammer.
>
> *3:00p**m -*  Dave Anderson, Ammeon
> - dynamic re/generation of manifests
> - several features that arent in puppet today but would be cool to have
> - experience embedding puppet in a software product (as opposed to ad-hoc
> devops)
>
>
> *4:00pm** -* Alessandro Franceschi, Lab42
>
> An Holistic approach to Puppet Modules
>
>  --
> 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/-/qIxcPAmaB9sJ.
> 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] is site.pp a must to have‏

[Worker Bee]

I ran into this as well.  I found that the puppetmaster will start without
a site.pp but, it does not build the catalog and actually apply anything.
So, I think that a site.pp file IS required.  It can be simple like:

import 'nodes.pp'
$puppetserver = 'somehost'




On Mon, Jul 2, 2012 at 7:00 PM, Hai  wrote:

>  Hi,
>
> is site.pp a file must to have? I have set up a puppet server, but my
> following manifest just cannot apply to my client, the server itself.
>
>
> # cat haitest.pp
> file { '/etc/motd' : source => "puppet:///files/motd" ,}
>
>
> Thanks.
>
> Hai  T.
>
> --
> 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/-/PHMGaA52wR4J.
> 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] is site.pp a must to have‏

[Corey Hammerton]

You can also set the PUPPETMASTER_MANIFEST variable in 
/etc/sysconfig/puppetmaster, if you're running puppet via an RPM build, to 
change the site manifest from the default /etc/puppet/manifests/site.pp to 
something else. 

On Tuesday, July 3, 2012 5:00:52 AM UTC-4, Hendrik Jäger wrote:
>
> Hi, 
>
> On Mon, 2 Jul 2012 16:00:28 -0700 (PDT) 
> Hai  wrote: 
>
> >  Hi, 
> >   
> > is site.pp a file must to have? 
>
> No, see 
> https://docs.puppetlabs.com/references/stable/configuration.html#manifest 
>
> > I have set up a puppet server, but my 
> > following manifest just cannot apply to my client, the server itself. 
>
> If you want help with that, show us the problem. 
>
> Best regards 
>
> Hendrik Jäger 
>

-- 
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/-/ckbTSg20-uUJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Using onlyif

[jcbollinger]

On Monday, July 2, 2012 11:14:25 PM UTC-5, Ryan Coleman wrote:
>
> Binaries like curl and test must be fully qualified (ex. /bin/rm) or you 
> must pass the path attribute to your exec resource with a search path like 
> '/bin:/usr/bin' as the value. 



Or you can set a path via Exec's 'path' parameter.  Sometimes that's more 
convenient and / or clearer.


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/-/CV5sPyIiDScJ.
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: bootstrap aws instance - set server address in instance puppet.conf?

[Leej]

So I've cracked the initial problem and I can deploy an instance and auto 
configure puppet but I am still missing something, possibly a conceptual 
misunderstanding on my part.

I spin up an aws instance with :

puppet node_aws bootstrap --image ami-e1e8d395 --keyname puppet --login 
ubuntu --keyfile ~puppet.pem --puppetagent-certname new_certname_1 
--region=eu-west-1 --type t1.micro -g webserver --server 
mypuppetserver.somewhere.com

This fails with :

notice: Waiting for SSH response ... Done
notice: Installing Puppet ...
notice: Puppet is now installed on: blahblah.eu-west-1.compute.amazonaws.com
notice: No classification method selected
notice: Signing certificate ...
err: Signing certificate ... Failed
err: Signing certificate error: Could not render to pson: The certificate 
retrieved from the master does not match the agent's private key.
Certificate fingerprint: 35:39:B7:DD:19:0E:7A:D6:07:AE:6D:64:FF:2E:92:37
To fix this, remove the certificate from both the master and the agent and 
then start a puppet run, which will automatically regenerate a certficate.
On the master:
  puppet cert clean mypuppetserver.somewhere.com
On the agent:
  rm -f /home/lj/.puppet/ssl/certs/mypuppetserver.somewhere.com.pem
  puppet agent -t

However if I sign the certificate by hand on the puppet server :

sudo puppetca -s new_certname_1

My client then (eventually) will update via puppet, so things are *almost* 
working, although the error is misleading.

So here are my questions.

1) I obviously want to maintain a secure install so I want to sign the 
certificates. Should node_aws bootstrap be signing the certificates 
automatically (as it seems to be attempting to do)? Is it possible to 
create a certificate before bootstrapping the instance so that there is a 
certificate ready and waiting for the client?

2) I dont know the ip address or have a fqdn for the instances I am 
spinning up. I want to put some files on my clients. In fileserver.conf I 
am using the cert_name to control access e.g. 

[files]
  path /etc/puppet/files
  allow new_certname_1

I was surprised that this worked. 

Now heres where my conceptual understanding is failing me - since it seems 
every certname has to be unique (e.g. I cant just create a group controlled 
by the certificate name) how can I restrict access to the fileserver when 
provisioning new instances without manually modifying the fileserver.conf?

3) I should also ask - does a client need to be authenticated via its 
certificate before it will be given access to the fileserver? If so I 
assume I could then just use * since the certification requirement would 
reject uncertified clients. Sorry this is possibly a stupid question but it 
is not clear from the documentation but if so my second question is moot.

-- 
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/-/RZS1zkbF7scJ.
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: Style guide question..

[Eric Shamow]

On Tuesday, July 3, 2012 at 8:39 AM, jcbollinger wrote:
> You mean "less objectionable" I presume?  I agree that classes generally 
> should not define other classes, but the guide already says that elsewhere.  
> I guess there's no harm in repeating it, if you think it worth the emphasis.

Sorry, yes - I meant that the practice was more objectionable rather than the 
phrasing.

However if it's defined elsewhere no need to repeat.

-- 

Eric Shamow
Professional Services
http://puppetlabs.com/
(c)631.871.6441
 

-- 
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: Style guide question..

[jcbollinger]

On Tuesday, July 3, 2012 6:34:10 AM UTC-5, Eric Shamow wrote:
>
> On Friday, June 29, 2012 at 9:55 AM, jcbollinger wrote:
>
> Note, however, that elsewhere the style guide (version 1.1.2) says "*Classes 
> should generally not declare other classes*," which is a bunch of 
> bologna.  A Puppetlabs employee told me recently that he would have that 
> removed, but evidently it hasn't happened yet.
>
>
> I'm wondering if it would be better to say "classes should generally not 
> *define* other classes," which I find a lot more objectionable.
>

You mean "less objectionable" I presume?  I agree that classes generally 
should not define other classes, but the guide already says that 
elsewhere.  I guess there's no harm in repeating it, if you think it worth 
the emphasis.


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/-/074-BONsB3oJ.
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] UX/UI of puppet help when face actions have unmet dependencies

[Eric Shamow]

On Friday, June 29, 2012 at 1:22 PM, Daniel Pittman wrote:
> Pieter is absolutely right that reporting errors on the output channel
> is a bad habit in Puppet - it makes us wildly different to the Unix
> standard. Every normal application behaves the way we do now - errors
> to stderr - and if the user isn't looking, they have that same problem
> with every other application too.
> 
> 


+1 to keeping errors on STDERR.  It would be my expectation as a sysadmin that 
I could filter one from the other on output and I'd be fairly frustrated if I 
couldn't.

-- 

Eric Shamow
Professional Services
http://puppetlabs.com/
(c)631.871.6441
 

-- 
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: Style guide question..

[Eric Shamow]

On Friday, June 29, 2012 at 9:55 AM, jcbollinger wrote:
> Note, however, that elsewhere the style guide (version 1.1.2) says "Classes 
> should generally not declare other classes," which is a bunch of bologna.  A 
> Puppetlabs employee told me recently that he would have that removed, but 
> evidently it hasn't happened yet.

I'm wondering if it would be better to say "classes should generally not 
*define* other classes," which I find a lot more objectionable.

-Eric

-- 
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] Conditionals within a class based of something else than facter variable

[Eric Shamow]

On Tuesday, July 3, 2012 at 5:31 AM, Itamar Landsman wrote:
> Hi All,
>  
> First I want to apologize, I never completely dove into the fine details of 
> puppet. I just use it on my network of +-100 VMs for odd jobs.
>  
> my question is: I know how to set up a class that would, for example, install 
> a package on a machine based on a facter variable (e.g. operating system 
> version).  
> within the curly braces I can even put a list of operation that would all not 
> be run if the machine in question does not conform to the specific variable.
>  
> I am looking for a way to do something similar using something like if a file 
> on the host exists (similar to the 'onlyif' that is available in the exec 
> type).
>  
> my dream is:
>  
> class foo{
>onlyif "test[ condition ]" {
>  file{.}
>  exec{...}
>}
> }

Itamar,

You should take a look at the Puppet Language Guide 
(http://docs.puppetlabs.com/guides/language_guide.html) - and in general the 
rest of the docs site, in particular Learning Puppet, which might help you with 
some of the fundamentals.

There are a number of ways to express what you are attempting to do, but you 
nearly have it.  If you have a fact "myfile_present" for which the value is 
true, for instance, you can do the following:

class foo {
  if $::myfile_present == true {
file { … }
exec { … }
  }
}

In the above mentioned Language Guide, check out the section on Conditionals.

-Eric

--  

Eric Shamow
Professional Services
http://puppetlabs.com/
(c)631.871.6441

-- 
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] Conditionals within a class based of something else than facter variable

[Itamar Landsman]

Hi All,

First I want to apologize, I never completely dove into the fine details of 
puppet. I just use it on my network of +-100 VMs for odd jobs.

my question is: I know how to set up a class that would, for example, 
install a package on a machine based on a facter variable (e.g. operating 
system version). 
within the curly braces I can even put a list of operation that would all 
not be run if the machine in question does not conform to the specific 
variable.

I am looking for a way to do something similar using something like if a 
file on the host exists (similar to the 'onlyif' that is available in the 
exec type).

my dream is:

class foo{
   onlyif "test[ condition ]" {
 file{.}
 exec{...}
   }
}

I hope the question was clear enough, 
Thanks,
Itamar

-- 
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/-/oy8XRwYTXzYJ.
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] PuppetCamp Dublin this Friday 6th July 2012

[Simon McCartney]

http://puppetcampdublin.eventbrite.com/ 
http://lanyrd.com/2012/puppet-camp-dublin/ 

PuppetCamp Dublin, in conjunction with Engineers Ireland Computing Division:

Puppet Camp is a community oriented gathering of Puppet users and 
developers. You’ll have the opportunity to network with a diverse group of 
Puppet users, benefit from insightful lectures delivered by prominent 
community members, and be able to share experiences and discuss potential 
implementations of Puppet during our attendee generated breakout sessions.

*Schedule*

*10:00am -* Checkin and Opening Remarks from Puppet Labs Co-founder Teyo 
Tyree

*10:40am - *Roland Tritsch - VP Technical Operations, Gilt Groupe

Building a continuous delivery platform for the biggest spike in e-commerce

*11:20: *Ruaidhri Power, DemonWare

This talk will describe the evolution of how we've used Puppet at Demonware, 
a subsidiary of Activision Blizzard, to run the infrastructure of some of 
the world's biggest games, supporting millions of concurrent users for 
titles such as Call of Duty.

*12:00pm - *Break & Lunch**

*1:00pm - *Stephen Connolly,Elite Developer and Architect,* *CloudBees

Continuous Deployment with Jenkins

*2:00pm**-*   CloudSmith 

Develop, test and publish modules to the Forge with Geppetto. Stack, 
validate and deploy them with Stack Hammer.

*3:00p**m -*  Dave Anderson, Ammeon
- dynamic re/generation of manifests
- several features that arent in puppet today but would be cool to have
- experience embedding puppet in a software product (as opposed to ad-hoc 
devops)
 

*4:00pm** -* Alessandro Franceschi, Lab42

An Holistic approach to Puppet Modules

-- 
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/-/qIxcPAmaB9sJ.
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] is site.pp a must to have‏

[Hendrik Jäger]

Hi,

On Mon, 2 Jul 2012 16:00:28 -0700 (PDT)
Hai  wrote:

>  Hi,
>  
> is site.pp a file must to have?

No, see
https://docs.puppetlabs.com/references/stable/configuration.html#manifest

> I have set up a puppet server, but my 
> following manifest just cannot apply to my client, the server itself.

If you want help with that, show us the problem.

Best regards

Hendrik Jäger


signature.asc
Description: PGP signature

[Puppet Users] Puppet v2.7.11 Seg Faults

[ollies...@googlemail.com]

Hello,
 
Migrating some clients from an ancient client to a new infrastructure based 
on 2.7.11 these are RHEL boxes
 
Some clients are hitting an issue
 
[30/06/12 05:11:37 UTC] 
/usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:733: [BUG] Segmentation 
fault
[30/06/12 05:11:37 UTC] ruby 1.8.5 (2006-08-25) [x86_64-linux]
[30/06/12 05:11:37 UTC]
[30/06/12 05:11:37 UTC] Puppet SSL run return code: 134
[30/06/12 05:11:37 UTC] Puppet SSL certificate handshake failed
This looks to be writing a file
  # Update the umask to make non-executable files
  Puppet::Util.withumask(File.umask ^ 0111) do
File.open(file, *args) do |file|
  yield file
end
  end
Anyone got any ideas on resolving this issue painlessly :)
 
Cheers
Paul

-- 
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/-/Ay1XsNlb91YJ.
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: puppetmasterd continuously consuming high CPU, with many interrupts

[Walter Heck]

The fix is actually not that weird, a call to clock_settime() function
is enough (which setting the date on the command line does). More
explained in the comments here:
http://blog.mozilla.org/it/2012/06/30/mysql-and-the-leap-second-high-cpu-and-the-fix/

Walter

On Tue, Jul 3, 2012 at 3:23 AM, Ken Barber  wrote:
>> Turns out yes, it's the leap second, but boy was the fix I found
>> easier than that:
>>
>> http://artipc10.vub.ac.be/wordpress/2012/07/01/leap-second-causing-ksoftirqd-and-java-to-use-lots-of-cpu-time/
>>
>> $ sudo date -s "`date`"
>>
>> Cleared it rigt up.
>
> Huh. What a weird fix :-).
>
> ken.
>
> --
> 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.
>



-- 
Walter Heck

--
Check out my startup: Puppet training and consulting @ http://www.olindata.com
Follow @olindata on Twitter and/or 'Like' our Facebook page at
http://www.facebook.com/olindata

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