[Puppet Users] Re: Could not retrieve catalog: Could not find node

[David Schmitt]

Jeremy Hansen schrieb:
> notice: Starting Puppet server version 0.24.8
> debug: Allowing authenticated client blah(10.10.10.11) access to
> puppetmaster.getconfig
> debug: Our client is remote
> debug: Executing '/usr/local/sbin/puppet_node_classifier blah'
> debug: Empty response for blah from exec exec terminus
> err: Could not call: Could not find node 'blah'; cannot compile

There you have it! Your node classifier doesn't work.


Regards, DavidS


-- 
dasz.at OG  Tel: +43 (0)664 2602670 Web: http://dasz.at
Klosterneuburg UID: ATU64260999

FB-Nr.: FN 309285 g  FB-Gericht: LG Korneuburg

--~--~-~--~~~---~--~~
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: file serving question

[Saurabh Verma]

Don Jackson wrote:
> I have a somewhat basic question about file serving:
>
> Once you specify the puppet://server/module
>
> Can that path continue from there?
>
> Eg, if my fileserver.conf file is:
>
> [myconfigfiles]
>   path /export/home/configs
>   allow *
>
> Can my clients do something like this?
>
> source => "puppet:///myconfigfiles/foo/bar.txt
>
> Meaning go get foo/bar.txt from the module myconfigfiles
>
> Or is the source directive restricted to just getting files directly  
> (not in a subdirectory) of the specified path?
>   
No its not , you can serve from subdirectories of specific file share 
section. foo/bar.txt is fine
> Don
>
>
>
>
> >
>
>   


--~--~-~--~~~---~--~~
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: Vote for your favorite ticket

[Felix Schäfer]

Am 04.06.2009 um 06:44 schrieb James Turnbull:

> Nigel Kersten wrote:
>>
>
>> That's exactly what I see. No arrows.
>
> This is now fixed.  Can people confirm they can see arrows.

I can see the arrows and it seems they work as expected.

Tanks,

Felix

--~--~-~--~~~---~--~~
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: Vote for your favorite ticket

[James Turnbull]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Nigel Kersten wrote:
> On Wed, Jun 3, 2009 at 8:00 AM, Peter Meier  wrote:
>> Hi
>>
>>> Damn.  Okay - can I get some hands up and down as to who can see or not
>>> see up and down arrows in the ticket details?  I've included a
>>> screenshot of what you should see.
>> attached a screenshot.
> 
> That's exactly what I see. No arrows.
> 

Hi all

This is now fixed.  Can people confirm they can see arrows.

Thanks

James Turnbull

- --
Author of:
* Pro Linux Systems Administration
(http://www.amazon.com/gp/product/1430219122/)
* Pulling Strings with Puppet
(http://www.amazon.com/gp/product/1590599780/)
* Pro Nagios 2.0
(http://www.amazon.com/gp/product/1590596099/)
* Hardening Linux
(http://www.amazon.com/gp/product/159059/)
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkonUTUACgkQ9hTGvAxC30DQIACgyZ7IlyQwJzb9OJM3er4rwh4N
8H0AnA78RXSrxQlXyPP0xw9uyL/1E6Ix
=OSmL
-END PGP SIGNATURE-

--~--~-~--~~~---~--~~
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: Puppetshow defunct?

[Roberto Moral]

Did you get a chance to upload this version of puppetshow to github?  
The only version I can see was updated May 1st. 2008

Thanks!


On Friday,May 29, 2009, at Friday,May 29, 20097:23 PM, jrojas wrote:

>
> I have a version of puppetshow that I threw together based off of the
> original (minus the hobo and other crazy gems)
> I will sanitize it tonight and try to get it on github.
> >


--~--~-~--~~~---~--~~
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: Could not retrieve catalog: Could not find node

[Jeremy Hansen]

Jim Pirzyk wrote:
> Do you have a
>
> node default {
> ...
> }
>
> section in your site.pp or any included file?
>   
Yes:

# /etc/puppet/manifests/site.pp

import "modules"
import "nodes"

filebucket { main: server => puppet }

# global defaults
File { backup => main }
Exec { path => "/usr/bin:/usr/sbin/:/bin:/sbin" }

Package {
   provider => $operatingsystem ? {
   debian => aptitude,
   redhat => yum,
   centos => yum
   }
}


# /etc/puppet/manifests/nodes.pp

node default {
 include nagios-nrpe
 include inventory-client
 include snmpd
 include sudo
 include ssh
 include resolvconf
 include ossec-hids-client
 include hosts
}

> - JimP
>
> On Jun 3, 2009, at 7:12 PM, Jeremy Hansen wrote:
>
>   
>> Actually, puppet seems to be doing this for any NEW host.  What  
>> went wrong?
>>
>> -jeremy
>>
>> Jeremy Hansen wrote:
>> 
>>> This one is driving me a little crazy.
>>>
>>> This is a Xen host.  The first we're trying to get into puppet.  I
>>> continuously get:
>>>
>>> Could not retrieve catalog: Could not find node 'blah'; cannot  
>>> compile
>>>
>>> I can't figure out why this is happening.
>>>
>>> No problem with resolving.  The puppetmaster is saying this:
>>>
>>> Could not call: Could not find node 'blah'; cannot compile
>>>
>>> Any clues on how to debug.
>>>
>>> Thanks
>>> -jeremy
>>>
>>>   
>>
>>
>> >> 
>
> --- @(#) $Id: dot.signature,v 1.15 2007/12/27 15:06:13 pirzyk Exp $
>  __o  j...@pirzyk.org ---
>   _'\<,_
> (*)/ (*) I'd rather be out biking.
>
>   


--~--~-~--~~~---~--~~
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: Could not retrieve catalog: Could not find node

[Jeremy Hansen]

James Turnbull wrote:
> Jeremy Hansen wrote:
>   
>> This one is driving me a little crazy.
>>
>> This is a Xen host.  The first we're trying to get into puppet.  I 
>> continuously get:
>>
>> Could not retrieve catalog: Could not find node 'blah'; cannot compile
>>
>> I can't figure out why this is happening.
>>
>> No problem with resolving.  The puppetmaster is saying this:
>>
>> Could not call: Could not find node 'blah'; cannot compile
>>
>> Any clues on how to debug.
>>
>> 
>
> Version?  Platform?  More log data (--debug --trace --verbose)?
>
> Regards
>
> James Turnbull
>
>   
client:
r...@blah ~]# rpm -qa | grep puppet
puppet-0.24.8-1.el5.1

puppetmaster:
[r...@master manifests]# rpm -qa | grep puppet
puppet-server-0.24.8-1.el5.1

[r...@blah ~]# puppetd --debug --trace --verbose
debug: Creating default schedules
debug: Failed to load library 'ldap' for feature 'ldap'
debug:
/Settings[/etc/puppet/puppet.conf]/Settings[ssl]/File[/var/lib/puppet/ssl/certs/blah.pem]:
 


Autorequiring File[/var/lib/puppet/ssl/certs]
debug:
/Settings[/etc/puppet/puppet.conf]/Settings[ssl]/File[/var/lib/puppet/ssl/private_keys/blah.pem]:
 


Autorequiring File[/var/lib/puppet/ssl/private_keys]
debug:
/Settings[/etc/puppet/puppet.conf]/Settings[ssl]/File[/var/lib/puppet/ssl/certs]:
 


Autorequiring File[/var/lib/puppet/ssl]
debug:
/Settings[/etc/puppet/puppet.conf]/Settings[ssl]/File[/var/lib/puppet/ssl/private]:
 


Autorequiring File[/var/lib/puppet/ssl]
debug:
/Settings[/etc/puppet/puppet.conf]/Settings[ssl]/File[/var/lib/puppet/ssl/public_keys]:
 


Autorequiring File[/var/lib/puppet/ssl]
debug:
/Settings[/etc/puppet/puppet.conf]/Settings[ssl]/File[/var/lib/puppet/ssl/csr_blah.pem]:
 


Autorequiring File[/var/lib/puppet/ssl]
debug:
/Settings[/etc/puppet/puppet.conf]/Settings[ssl]/File[/var/lib/puppet/ssl/certs/ca.pem]:
 


Autorequiring File[/var/lib/puppet/ssl/certs]
debug:
/Settings[/etc/puppet/puppet.conf]/Settings[main]/File[/var/lib/puppet/state]: 


Autorequiring File[/var/lib/puppet]
debug:
/Settings[/etc/puppet/puppet.conf]/Settings[puppetd]/File[/etc/puppet/puppet.conf]:
 


Autorequiring File[/etc/puppet]
debug:
/Settings[/etc/puppet/puppet.conf]/Settings[main]/File[/var/lib/puppet/ssl]: 


Autorequiring File[/var/lib/puppet]
debug:
/Settings[/etc/puppet/puppet.conf]/Settings[main]/File[/var/lib/puppet/lib]: 


Autorequiring File[/var/lib/puppet]
debug:
/Settings[/etc/puppet/puppet.conf]/Settings[ssl]/File[/var/lib/puppet/ssl/private_keys]:
 


Autorequiring File[/var/lib/puppet/ssl]
debug:
/Settings[/etc/puppet/puppet.conf]/Settings[ssl]/File[/var/lib/puppet/ssl/public_keys/blah.pem]:
 


Autorequiring File[/var/lib/puppet/ssl/public_keys]
debug: Finishing transaction 23605424609360 with 0 changes

[r...@master manifests]# puppetmasterd --no-daemonize --debug --verbose
info: Starting server for Puppet version 0.24.8
debug: Creating default schedules
debug: Failed to load library 'ldap' for feature 'ldap'
debug: Finishing transaction 23456249445240 with 0 changes
debug: No modules mount given; autocreating with default permissions
debug: No plugins mount given; autocreating with default permissions
debug: Creating interpreter
debug: Creating default schedules
debug:
/Settings[/etc/puppet/puppet.conf]/Settings[metrics]/File[/var/lib/puppet/rrd]: 


Autorequiring File[/var/lib/puppet]
debug:
/Settings[/etc/puppet/puppet.conf]/Settings[main]/File[/var/lib/puppet/lib]: 


Autorequiring File[/var/lib/puppet]
debug:
/Settings[/etc/puppet/puppet.conf]/Settings[main]/File[/var/lib/puppet/ssl]: 


Autorequiring File[/var/lib/puppet]
debug:
/Settings[/etc/puppet/puppet.conf]/Settings[main]/File[/var/lib/puppet/state]: 


Autorequiring File[/var/lib/puppet]
debug:
/Settings[/etc/puppet/puppet.conf]/Settings[reporting]/File[/var/lib/puppet/reports]:
 


Autorequiring File[/var/lib/puppet]
debug: Finishing transaction 23456266181460 with 0 changes
debug: Creating default schedules
debug:
/Settings[/etc/puppet/puppet.conf]/Settings[ca]/File[/var/lib/puppet/ssl/ca/private/ca.pass]:
 


Autorequiring File[/var/lib/puppet/ssl/ca/private]
debug:
/Settings[/etc/puppet/puppet.conf]/Settings[ca]/File[/var/lib/puppet/ssl/ca/inventory.txt]:
 


Autorequiring File[/var/lib/puppet/ssl/ca]
debug:
/Settings[/etc/puppet/puppet.conf]/Settings[ca]/File[/var/lib/puppet/ssl/ca/ca_key.pem]:
 


Autorequiring File[/var/lib/puppet/ssl/ca]
debug:
/Settings[/etc/puppet/puppet.conf]/Settings[ca]/File[/var/lib/puppet/ssl/ca/ca_crl.pem]:
 


Autorequiring File[/var/lib/puppet/ssl/ca]
debug:
/Settings[/etc/puppet/puppet.conf]/Settings[ca]/File[/var/lib/puppet/ssl/ca/ca_pub.pem]:
 


Autorequiring File[/var/lib/puppet/ssl/ca]
debug:
/Settings[/etc/puppet/puppet.conf]/Settings[ca]/File[/var/lib/puppet/ssl/ca/signed]:
 


Autorequiring File[/var/lib/puppet/ssl/ca]
debug:
/Settings[/etc/puppet/puppet.conf]/Settings[ca]/File[/var/lib/puppet/ssl/ca/ca_crt.pem]:
 


Autorequiring File[/var/lib/puppet/ssl/ca]
debug:
/Settings[/etc/puppet/puppet.conf]

[Puppet Users] Default service provider

[diablo]

Hi,

I installed puppet on a range of OpenSuSE 11.1 servers and I have a
very strange problem. I didn't find anywere on the website or on the
wiki, how I can set a default service provider. My problem is that
freebsd is used instead of redhat and the init scripts are not started
properly. Here is a snippet from the debug messages I collected from
the console.


debug: file /sbin/rc-update does not exist
debug: file /usr/sbin/update-rc.d does not exist
debug: file /usr/sbin/svcadm does not exist
warning: Found multiple default providers for service: freebsd,
redhat; using freebsd
debug: Puppet::Type::Package::ProviderRpm: Executing '/bin/rpm --
version'
debug: Puppet::Type::Package::ProviderYum: Executing '/bin/rpm --
version'
debug: Puppet::Type::Package::ProviderAptrpm: Executing '/bin/rpm -ql
rpm'
debug: Puppet::Type::Package::ProviderUrpmi: Executing '/bin/rpm -ql
rpm'


--~--~-~--~~~---~--~~
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: Could not retrieve catalog: Could not find node

[Jim Pirzyk]

Do you have a

node default {
...
}

section in your site.pp or any included file?

- JimP

On Jun 3, 2009, at 7:12 PM, Jeremy Hansen wrote:

>
>
> Actually, puppet seems to be doing this for any NEW host.  What  
> went wrong?
>
> -jeremy
>
> Jeremy Hansen wrote:
>> This one is driving me a little crazy.
>>
>> This is a Xen host.  The first we're trying to get into puppet.  I
>> continuously get:
>>
>> Could not retrieve catalog: Could not find node 'blah'; cannot  
>> compile
>>
>> I can't figure out why this is happening.
>>
>> No problem with resolving.  The puppetmaster is saying this:
>>
>> Could not call: Could not find node 'blah'; cannot compile
>>
>> Any clues on how to debug.
>>
>> Thanks
>> -jeremy
>>
>>>
>>
>
>
>
>
> --~--~-~--~~~---~--~~
> 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
> -~--~~~~--~~--~--~---

--- @(#) $Id: dot.signature,v 1.15 2007/12/27 15:06:13 pirzyk Exp $
 __o  j...@pirzyk.org ---
  _'\<,_
(*)/ (*) I'd rather be out biking.



PGP.sig
Description: This is a digitally signed message part

[Puppet Users] Re: Could not retrieve catalog: Could not find node

[Peter Meier]

Hi

> Actually, puppet seems to be doing this for any NEW host.  What went
> wrong?


do you have a node entry set for these hosts or any default node set?

imho this error occures when puppet can't find a node.

cheers pete

--~--~-~--~~~---~--~~
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: Could not retrieve catalog: Could not find node

[James Turnbull]

Jeremy Hansen wrote:
> This one is driving me a little crazy.
> 
> This is a Xen host.  The first we're trying to get into puppet.  I 
> continuously get:
> 
> Could not retrieve catalog: Could not find node 'blah'; cannot compile
> 
> I can't figure out why this is happening.
> 
> No problem with resolving.  The puppetmaster is saying this:
> 
> Could not call: Could not find node 'blah'; cannot compile
> 
> Any clues on how to debug.
> 

Version?  Platform?  More log data (--debug --trace --verbose)?

Regards

James Turnbull

-- 
Author of:
* Pro Linux Systems Administration
(http://tinyurl.com/linuxadmin)
* Pulling Strings with Puppet
(http://tinyurl.com/pupbook)
* Pro Nagios 2.0
(http://tinyurl.com/pronagios)
* Hardening Linux
(http://tinyurl.com/hardeninglinux)



signature.asc
Description: OpenPGP digital signature

[Puppet Users] Re: Could not retrieve catalog: Could not find node

[Jeremy Hansen]

Actually, puppet seems to be doing this for any NEW host.  What went wrong?

-jeremy

Jeremy Hansen wrote:
> This one is driving me a little crazy.
>
> This is a Xen host.  The first we're trying to get into puppet.  I 
> continuously get:
>
> Could not retrieve catalog: Could not find node 'blah'; cannot compile
>
> I can't figure out why this is happening.
>
> No problem with resolving.  The puppetmaster is saying this:
>
> Could not call: Could not find node 'blah'; cannot compile
>
> Any clues on how to debug.
>
> Thanks
> -jeremy
>
> >
>   




--~--~-~--~~~---~--~~
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] Could not retrieve catalog: Could not find node

[Jeremy Hansen]

This one is driving me a little crazy.

This is a Xen host.  The first we're trying to get into puppet.  I 
continuously get:

Could not retrieve catalog: Could not find node 'blah'; cannot compile

I can't figure out why this is happening.

No problem with resolving.  The puppetmaster is saying this:

Could not call: Could not find node 'blah'; cannot compile

Any clues on how to debug.

Thanks
-jeremy

--~--~-~--~~~---~--~~
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] file serving question

[Don Jackson]

I have a somewhat basic question about file serving:

Once you specify the puppet://server/module

Can that path continue from there?

Eg, if my fileserver.conf file is:

[myconfigfiles]
path /export/home/configs
allow *

Can my clients do something like this?

source => "puppet:///myconfigfiles/foo/bar.txt

Meaning go get foo/bar.txt from the module myconfigfiles

Or is the source directive restricted to just getting files directly  
(not in a subdirectory) of the specified path?

Don




--~--~-~--~~~---~--~~
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: does puppet+augeas actually work? limits.conf busticated

[Rob McBroom]

On 2009-Jun-3, at 3:56 PM, Gajillion wrote:

> Fails: wombat::setup/Augeas[memlock]/returns: change from need_to_run
> to 0 failed: Save failed with return code fals


This is the same error I just said I wasn't able to reproduce in  
another thread. What OS is this? Try installing Augeas itself (not  
just the libs and ruby bindings) and see if the error goes away.

-- 
Rob McBroom


Don't try to tell me a thing is important to you if the whole of your  
"support" entails forcing other to spend time and money on it.




--~--~-~--~~~---~--~~
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] does puppet+augeas actually work? limits.conf busticated

[Gajillion]

All,
I've tried several lenses and several iterations and have never been
able to get augeas and puppet to work together.  My latest attempt:

augeas {"memlock":
changes => [
"ins domain after /files/etc/security/limits.conf/domain
[last()]",
"set /files/etc/security/limits.conf/domain[last()]/ *",
"set /files/etc/security/limits.conf/domain[last()]/type
hard",
"set /files/etc/security/limits.conf/domain[last()]/item
memlock",
"set /files/etc/security/limits.conf/domain[last()]/value
unlimited",
]
}

Fails: wombat::setup/Augeas[memlock]/returns: change from need_to_run
to 0 failed: Save failed with return code false

However, stepping through those exact steps cut and paste into augtool
works:

augtool> ins domain after /files/etc/security/limits.conf/domain[last
()]
augtool> set /files/etc/security/limits.conf/domain[last()]/ *
augtool> set /files/etc/security/limits.conf/domain[last()]/type hard
augtool> set /files/etc/security/limits.conf/domain[last()]/item
memlock
augtool> set /files/etc/security/limits.conf/domain[last()]/value
unlimited
augtool> save
Saved 1 file(s)
augtool>
# tail -1 /etc/security/limits.conf
* hard memlock unlimited

I can't see anything even remotely obviously wrong in this.  Any
ideas?  I've tried several iterations using various contexts and get
the same thing every time.

Full failure code from puppet

debug: Augeas[memlock](provider=augeas): Opening augeas with root /,
lens path , flags 0
debug: Augeas[memlock](provider=augeas): Augeas version 0.5.0 is
installed
debug: Augeas[memlock](provider=augeas): sending command 'ins' with
params ["domain", "after", "/files/etc/security/limits.conf/domain[last
()]"]
debug: Augeas[memlock](provider=augeas): sending command 'set' with
params ["/files/etc/security/limits.conf/domain[last()]/", "*"]
debug: Augeas[memlock](provider=augeas): sending command 'set' with
params ["/files/etc/security/limits.conf/domain[last()]/type", "hard"]
debug: Augeas[memlock](provider=augeas): sending command 'set' with
params ["/files/etc/security/limits.conf/domain[last()]/item",
"memlock"]
debug: Augeas[memlock](provider=augeas): sending command 'set' with
params ["/files/etc/security/limits.conf/domain[last()]/value",
"unlimited"]
err: //Node[...]/wombat::setup/Augeas[memlock]/returns: change from
need_to_run to 0 failed: Save failed with return code false

--~--~-~--~~~---~--~~
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: EPEL package dependencies

[Rob McBroom]

On 2009-May-27, at 3:35 PM, Rob McBroom wrote:

> There are a couple of new systems that are supposedly getting cabled
> up tomorrow. If that goes as expected, I'll get on and mess with them
> before anyone knows they're there


It took our network team until today to sort out the firewall rules so  
I could get to these boxes. They seem to function just fine having  
never had the augeas package installed, so it seems I can't reproduce  
it. the only notable difference is that these new servers are  
physical, while I noticed the problem on VMs. Seems unlikely to  
matter, but if I get a chance to test it on a VM, I will.

-- 
Rob McBroom


Because it screws up the order in which people normally read text.

Original message:

> Why is it bad to top-post your reply?





--~--~-~--~~~---~--~~
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: Vote for your favorite ticket

[Brice Figureau]

On Wed, 2009-06-03 at 08:27 -0700, Nigel Kersten wrote:
> On Wed, Jun 3, 2009 at 8:00 AM, Peter Meier  wrote:
> > Hi
> >
> >> Damn.  Okay - can I get some hands up and down as to who can see or not
> >> see up and down arrows in the ticket details?  I've included a
> >> screenshot of what you should see.
> >
> > attached a screenshot.
> 
> That's exactly what I see. No arrows.
> 

Same for me :-(
-- 
Brice Figureau
My Blog: http://www.masterzen.fr/


--~--~-~--~~~---~--~~
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: Vote for your favorite ticket

[Nigel Kersten]

On Wed, Jun 3, 2009 at 8:00 AM, Peter Meier  wrote:
> Hi
>
>> Damn.  Okay - can I get some hands up and down as to who can see or not
>> see up and down arrows in the ticket details?  I've included a
>> screenshot of what you should see.
>
> attached a screenshot.

That's exactly what I see. No arrows.

>
> cheers pete
>
> >
>



-- 
Nigel Kersten
nig...@google.com
System Administrator
Google, Inc.

--~--~-~--~~~---~--~~
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 not creating users home directories

[Rob McBroom]

On 2009-Jun-2, at 4:16 PM, Brandon Whalen wrote:

> I'm running puppet 0.24.8, installed from epel, on a RHEL 5.3 box.  
> I've
> created some puppet modules and in one of them I attempt to add a  
> user and
> pass in the managehome => true flag so that the users home directory  
> is
> created.

I was just messing with this yesterday. I'm seeing what seems like the  
exact opposite behavior (using the same OS and Puppet version). I had  
Puppet create a user, noticed that the home directory wasn't created,  
consulted the docs, and added the "managehome" line. Still no home  
directory, but if I delete the user entirely and let Puppet recreate  
it, the home directory does show up.

So, in my experience, the "managehome" option only seems to be  
consulted during user creation, but has no effect on existing users.  
(I realize the situation that led me to this is not going to be common  
in practice, so I think Puppet's behavior here is reasonable, but it  
seems to differ from what the OP saw, which is why I mention it.)

-- 
Rob McBroom


The magnitude of a problem does not affect its ownership.






--~--~-~--~~~---~--~~
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: Vote for your favorite ticket

[Felix Schäfer]

Hello,

Am 03.06.2009 um 16:24 schrieb James Turnbull:

> Can you clear your browser cache and try now please?

Tried that, same result as before (pertinent part of the html source):
"""
translation missing: de, label_votes: 0 
"""

Even omitting the fact that there is no translation (could provide fr  
and de if you need), there are no arrows whatsoever.

BR and thanks for the hard work,

Felix

--~--~-~--~~~---~--~~
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: Vote for your favorite ticket

[James Turnbull]

Trevor Hemsley wrote:
> Not me. Logged in as TrevorHemsley
> 

Trevor (and Peter and others)

Can you clear your browser cache and try now please?

Thanks

James Turnbull

-- 
Author of:
* Pro Linux Systems Administration
(http://tinyurl.com/linuxadmin)
* Pulling Strings with Puppet
(http://tinyurl.com/pupbook)
* Pro Nagios 2.0
(http://tinyurl.com/pronagios)
* Hardening Linux
(http://tinyurl.com/hardeninglinux)



signature.asc
Description: OpenPGP digital signature

[Puppet Users] Re: Vote for your favorite ticket

[Trevor Hemsley]

Not me. Logged in as TrevorHemsley

James Turnbull wrote:
> Peter Meier wrote:
>   
>> Hi
>>
>> 
 With my account, I'm not seeing any green/red arrows in the ticket
 view.

 
>>> Christian
>>>
>>> Are in you inside a ticket detail page?  The arrows are not on the
>>> Issues tab but rather inside each issue.  In not, what's your user name?
>>>   
>> duritong doesn't see any arrows in a ticket detail page as well.
>> 
>
> Damn.  Okay - can I get some hands up and down as to who can see or not
> see up and down arrows in the ticket details?  I've included a
> screenshot of what you should see.
>
> Thanks
>
> James
>
>   
>
> 
>

-- 

Trevor Hemsley
Infrastructure Engineer
.
* C A L Y P S O
* Brighton, UK   

OFFICE  +44 (0) 1273 666 350
FAX +44 (0) 1273 666 351

.
www.calypso.com

This electronic-mail might contain confidential information intended
only for the use by the entity named. If the reader of this message is
not the intended recipient, the reader is hereby notified that any
dissemination, distribution or copying is strictly prohibited.

* P * /*/ Please consider the environment before printing this e-mail /*/


--~--~-~--~~~---~--~~
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: Facter 1.5.5

[jean]

>> thanks, any way to repport this to someone who is managing the gem :) ?
>> 
>
> It's already been reported and fixed. We're thinking about 1.5.6 to fix this.
>
> Paul
>   

faster than report, dam thanks all of you !! :)

Jean

--~--~-~--~~~---~--~~
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: Facter 1.5.5

[Paul Nasrat]

2009/6/3 Jean Spirat :
>
>
>>
>> cd /var/lib/gems/1.8/gems/facter01.5.5 && \
>>     ruby installer.rb
>> cd /usr/bin && ln -fs /var/lib/gems/1.8/bin/facter
>>
>> Seems the gem install is a little broken.
>>
>
> thanks, any way to repport this to someone who is managing the gem :) ?

It's already been reported and fixed. We're thinking about 1.5.6 to fix this.

Paul

--~--~-~--~~~---~--~~
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: Vote for your favorite ticket

[Peter Meier]

Hi

>> With my account, I'm not seeing any green/red arrows in the ticket
>> view.
>>
>
> Christian
>
> Are in you inside a ticket detail page?  The arrows are not on the
> Issues tab but rather inside each issue.  In not, what's your user name?

duritong doesn't see any arrows in a ticket detail page as well.

cheers pete

--~--~-~--~~~---~--~~
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 Certification?

[paul matthews]

I realise this could be a long way off as Puppet is rapidly evolving, with
development still at the forefront but are there plans in the furture to
offer a Puppet Certification exam. I know the subject of certification is
not to everyone's taste, but I find studying for these is a good way for me
to focus on learning all the subject areas and to demonstrate some level of
competence to any would be employers. I think there would be benefits to
Reductive too, I guess mostly in the area of getting people to attend
training courses

I'll get my flame proof suit on in anticipation for any replies

Rgds
Paul


-- 
Paul Matthews
--

--~--~-~--~~~---~--~~
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: No more than one "instances" of a type in define()?

[Paul]

On 1 Jun., 20:40, David Schmitt  wrote:
> Paul wrote:
> >> Seehttp://reductivelabs.com/trac/puppet/wiki/LanguageTutorial#quoting
> > Indeed, shame on me ;)  But if you take that literally brackets
> > shouldn't be needed.
>
> Except that the underscore is a valid part of a variable name and puppet
> does longest match on variable names, thus recognising $name_production,
> instead of the existing $name.
>
> >>> Apparently there seem to be more differences between classes and
> >>> defines wrt. scope. When I use template("foo.erb") inside a define() I
> >>> don't have direct access to facts or other variables (fex. the $name).
> >>> However scope.lookupvar('name') works. Is this expected behaviour?
> >> No. What version of puppet are you using? How did your ERB look like?
> > Version is 0.24.8, I'm testing with:
> > -
> > <% tags.each do |tag| -%>
> >     TAG: <%= tag %>
> > <% end -%>
> > SCOPE LOOKUP <%= scope.lookupvar('name') %>
> > SCOPE LOOKUP <%= scope.lookupvar('ipaddress_eth0') %>
> > :80>
>
> Stuff within <%%> is ruby. Ruby has no $ sigils. Use the variable
> instead without the dollar sign:
>
>  > :80>
Ops, another Doh!

Thanks guys, it's all working now.

cheers
 Paul

>
> Regards, DavidS
--~--~-~--~~~---~--~~
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: Facter 1.5.5

[Jean Spirat]

>
> cd /var/lib/gems/1.8/gems/facter01.5.5 && \
> ruby installer.rb
> cd /usr/bin && ln -fs /var/lib/gems/1.8/bin/facter
>
> Seems the gem install is a little broken.
>   

thanks, any way to repport this to someone who is managing the gem :) ?

regards,
Jean.

--~--~-~--~~~---~--~~
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: Facter 1.5.5

[Sheldon Hearn]

On Jun 3, 8:56 am, jean  wrote:
>   Since i use facter 1.5.5 i got error running it by hand. It still work
> in puppet but i loosed the hability to run it from the command line:
>
> (aqadmin)> /var/lib/gems/1.8/gems/facter-1.5.5/bin/facter
> /var/lib/gems/1.8/gems/facter-1.5.5/bin/facter:50:in `require': no such
> file to load -- facter (LoadError)
>         from /var/lib/gems/1.8/gems/facter-1.5.5/bin/facter:50

Try this:

cd /var/lib/gems/1.8/gems/facter01.5.5 && \
ruby installer.rb
cd /usr/bin && ln -fs /var/lib/gems/1.8/bin/facter

Seems the gem install is a little broken.

Ciao,
Sheldon.
--~--~-~--~~~---~--~~
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: factsync md5 checksum weirdness

[Greg]

Its happening on "normal" runs. I've removed the fact from the client
to
force the update (/var/opt/csw/puppet/facts/defaultroute.rb) however
that
didn't help - it grabbed the new file from the server then promptly
informed
me that it had the wrong md5sum.

Turns out fix was to shut down puppet, clean out the fact cache in
/var/opt/csw/puppet/facts and then restart. I also restarted the
puppetd in
the local zone on the same box... Not sure if it was interfering, but
I did a
"pkill puppetd" which killed the local zone as well...

Does puppet cache md5 checksums anywhere? Am wondering if maybe
it wasn't cleaned out properly...

On Jun 3, 1:16 pm, Nigel Kersten  wrote:
> On Tue, Jun 2, 2009 at 6:27 PM, Greg  wrote:
>
> > Hi all,
>
> > Figured I would put this to the group before submitting a bug report,
> > just in case I'm doing something silly...
>
> > On each of my servers, factsync is enabled. Every time Puppet runs, I
> > get these messages:
>
> > Jun  3 11:19:15 CLIENT puppetd[13374]: [ID 702911 daemon.notice] (/File
> > [/var/opt/csw/puppet/facts]/checksum) checksum changed '{mtime}Tue May
> > 26 16:03:10 +1000 2009' to '{mtime}Wed Jun 03 11:08:51 +1000 2009'
> > Jun  3 11:19:17 CLIENT puppetd[13374]: [ID 702911 daemon.notice] (/File
> > [/var/opt/csw/puppet/facts/defaultroute.rb]/checksum) checksum changed
> > '{md5}d919e79f809a4a5fe1b225dccebdeca1' to '{md5}
> > d7ef8c6e31c388fa6b6b91afb0ea9905'
> > Jun  3 11:19:21 CLIENT puppetd[13374]: [ID 702911 daemon.notice] (/File
> > [/var/opt/csw/puppet/facts/hardwareplatform.rb]/checksum) checksum
> > changed '{md5}c99480485491bd0124228b552294caa9' to '{md5}
> > 0ee4d0938bd37435edd21c53f6aed9a0'
>
> > If I run the checksum on the files, I get the second of the two
> > checksums listed. The files match the puppetmaster servers copy of the
> > files, so why is it complaining?
>
> Is this when you run with --test only?
>
> There's some bug when you don't use the cache where although it
> doesn't update the cache, it does read from it for the comparison
> notice, but you'll notice it doesn't actually download the fact files.
>
> You should see the earlier checksum in the cache.
>
>
>
> > Running puppet 0.24.8 and facter 1.5.4...
>
> > Any thoughts would be appreciated...
>
> --
> Nigel Kersten
> nig...@google.com
> System Administrator
> Google, Inc.
--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---