Re: [Puppet Users] package issue for provider sun
Hi, On 02/03/2012 10:25 PM, david boldt wrote: > > The following one line change appears to fix that problem for 2.7.10. > > ... great, thanks for sharing. Unfortunately, this will probably need to made a bug report at http://projects.puppetlabs.com/issues/. You will likely be required to get a Redmine account and click to accept a license agreement at some point down the road. Sorry for the hassle (been there myself), but everyone would be most grateful if you went through with it. Thanks! > PS This is my first posting on Puppet, so please pardon any customs > infractions Uhm...sure? :-) Seriously, though - can't seem to find any. Cheers, 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.
Re: [Puppet Users] Re: Installing Puppet/Facter without sudo/root access
If you have RVM already up, can you use the puppet gem instead? Note: I would create a gemset here first, here but that's another story. $rvm use 1.8.7 $gem install puppet -v 2.7.6 As for configuring openssl, I had this battle with iconv today: http://beginrescueend.com/packages/openssl/ -Charles On Feb 20, 2012 12:14 AM, "Jeff Sussna" wrote: > > I installed RVM, then used that to install Ruby. Installed openssl > from RVM in the process. However, when I try to install facter or > puppet I get "Could not load openssl; could not install". > > Sequence of events looked like: > > rvm pkg install > rvm pkg install openssl > rvm install 1.8.7 --with-openssl-dir=~/.rvm/usr > rvm use 1.8.7 > cd puppet-2.7.6 > ruby install.rb > > Any advice on how to get the installer to find openssl? I've googled > and tried various tricks to no avail. > > On Feb 17, 5:10 pm, Michael Stahnke wrote: > > On Fri, Feb 17, 2012 at 1:43 PM, Jeff Sussna wrote: > > > I want to use Puppet and Facter on a machine where I don't have sudo > > > or root access privileges. I won't be using Puppet for anything that > > > requires that level of access, so I should be OK if I can get it on > > > the box. Any advice on how to proceed? Currently the Facter installer > > > complains that it doesn't have privileges for /usr/bin/facter. I > > > assume Puppet will have the same complain about /etc/puppet. > > > > > Am trying to install Puppet 2.7.6/Facter 1.6.1 from source on SLES 11 > > > in case that matters. > > > > You could clone the sources from git in your home directory and then > > set your RUBYLIB environment variable to look in those cloned > > directories and adjust $PATH accordingly. That would probably be > > easier than trying to use a package that assumes root rights. > > > > > > > > > > > > > > > > > > > > > -- > > > 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 athttp:// 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. > -- 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 unless behaviour with a dependency
On Feb 17, 5:22 pm, jimbob palmer wrote:
> On Feb 17, 5:12 pm, Adam Heinz wrote:
>
> > Something like this?
>
> > exec { "second command":
> > refreshonly => true,
> > subscribe => Exec["first command"],
>
> > }
>
> Gah! I'm five minutes behind you. It works - THANKS.
The problem that this creates is that *any* update now runs the
command from the subscribe, which isn't ideal, but I guess will work
for now :)
--
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 agent fails to start on Windows Server 2008 with --listen option
Hi all, I'm trying to start puppet agent on windows machine with --listen option: puppet agent --no-daemonize --verbose --listen But in this case I`m receiving the following error message: notice: Starting Puppet client version 2.7.10 D:/Ruby187/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:72:in `setup_logger': uninitialized constant Fcntl::F_SETFD (NameError) from D:/Ruby187/lib/ruby/site_ruby/1.8/puppet/network/http/ webrick.rb:20:in `listen' from D:/Ruby187/lib/ruby/site_ruby/1.8/puppet/network/ server.rb:100:in `listen' from D:/Ruby187/lib/ruby/site_ruby/1.8/puppet/network/ server.rb:115:in `start' from D:/Ruby187/lib/ruby/site_ruby/1.8/puppet/daemon.rb:123:in `start' from D:/Ruby187/lib/ruby/site_ruby/1.8/puppet/application/ agent.rb:347:in `main' from D:/Ruby187/lib/ruby/site_ruby/1.8/puppet/application/ agent.rb:302:in `run_command' from D:/Ruby187/lib/ruby/site_ruby/1.8/puppet/application.rb: 309:in `run' from D:/Ruby187/lib/ruby/site_ruby/1.8/puppet/application.rb: 412:in `hook' from D:/Ruby187/lib/ruby/site_ruby/1.8/puppet/application.rb: 309:in `run' from D:/Ruby187/lib/ruby/site_ruby/1.8/puppet/application.rb: 404:in `exit_on_fail' from D:/Ruby187/lib/ruby/site_ruby/1.8/puppet/application.rb: 309:in `run' from D:/Ruby187/lib/ruby/site_ruby/1.8/puppet/util/ command_line.rb:69:in `execute' from D:/Ruby187/bin/puppet:4 I've tried to use 2.7.9 puppet agent, but without any luck too. Any ideas how to workaround this problem? -- 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 kick class option error
Hi, sorry for following up late. On 02/06/2012 08:27 AM, Kenichi Tsunokawa wrote: > Hello, > I'm trying to puppet kick with class option. > > Pupper Master: puppetmaster.example.com > Puppet Client1: host1.example.net > Puppet Client2: host2.example.net > > But I get this error. > > --- > [root@puppetmaster ~]# puppet kick --class test --debug > test: host1.example.net.example.com, host2.example.net.example.com > Triggering host1.example.net.example.com, > host2.example.net.example.com > Host host1.example.net.example.com failed: getaddrinfo: Name or > service not known > host1.example.net.example.com finished with exit code 2 > Triggering host2.example.net.example.com > Host host2.example.net.example.com failed: getaddrinfo: Name or > service not known > host2.example.net.example.com finished with exit code 2 > Failed: host1.example.net.example.com, host2.example.net.example.com > --- > > Maybe Puppetmaster was loaded "cn=host1.example.net" and > "dc=example,dc=com". Unfortunately I'm neither really proficient with neither puppet kick nor LDAP. Can you modify the LDAP database for your test setup? I believe you should really try to pinpoint the problem to a specific detail in your DB. Perhaps you can loose the "dc=com" for a while? HTH, 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] Cannot see node on Live Management
The node and reports show up on the dashboard but not on the live management tab. Does anyone have any suggestions? is this a permissions issue? -- 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] class include question
Hi, I am using RVM modul downloaded from the puppet website which has the follwoing directory structure: rvm/manifests/classes rvm/manifests/definitions rvm/manifests/init.pp which contains the following lines import "classes/*.pp" import "definitions/*.pp" I used this module with puppet 2.6 and included it with this line include rvm::system but since I upgraded to 2.7 it tells me cant find the rvm::system class. I tried all kind of include variations but seems like I can't find the proper one. Sorry for the stupid question but how can I include this in 2.7 version. Thank you Peter -- 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] class include question
have you tried include rvm On Mon, Feb 20, 2012 at 3:29 PM, Peter Horvath wrote: > Hi, > > I am using RVM modul downloaded from the puppet website which has the > follwoing directory structure: > > rvm/manifests/classes > rvm/manifests/definitions > rvm/manifests/init.pp which contains the following lines > > import "classes/*.pp" > import "definitions/*.pp" > > I used this module with puppet 2.6 and included it with this line > include rvm::system > > but since I upgraded to 2.7 it tells me cant find the rvm::system class. > I tried all kind of include variations but seems like I can't find the > proper one. > > Sorry for the stupid question but how can I include this in 2.7 version. > > Thank you > Peter > > -- > 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. > > -- Best Regards, Eslam Mamdouh El Husseiny *Systems Administrator** Cloud Niners Ltd. * *Cellular: (+2) 011 198 40 40 Mansoura: (+2) 050 234 70 81 Cairo:(+2) 022 *268 34 60 Fax: (+2) 022 268 34 63 -- 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: class include question
Sorry about this they upgraded RVM module to cope with version 2.7 I just had to update my local version On Feb 20, 1:29 pm, Peter Horvath wrote: > Hi, > > I am using RVM modul downloaded from the puppet website which has the > follwoing directory structure: > > rvm/manifests/classes > rvm/manifests/definitions > rvm/manifests/init.pp which contains the following lines > > import "classes/*.pp" > import "definitions/*.pp" > > I used this module with puppet 2.6 and included it with this line > include rvm::system > > but since I upgraded to 2.7 it tells me cant find the rvm::system class. > I tried all kind of include variations but seems like I can't find the > proper one. > > Sorry for the stupid question but how can I include this in 2.7 version. > > Thank you > Peter -- 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: Cache for the local system while offline
I am not able to cache the updates from the server as I had updated the nodes puppet.conf with usecacheonfailure=true or any other info need to be updated ? I am getting the error messages as, err: Could not retrieve catalog from remote server: getaddrinfo: Name or service not known err: Could not retrieve catalog; skipping run err: Could not send report: getaddrinfo: Name or service not known Please assist. Thanks mukulm On Feb 16, 1:29 pm, mukulm wrote: > I am too getting the same message & error as, > > err: Could not retrieve catalog from remote server: getaddrinfo: Name > or service not known > err: Could not retrieve catalog; skipping run > err: Could not send report: getaddrinfo: Name or service not known > > Can anyone assist howcachecachecan be achieve on the nodes. > > Thanks > mukulm > > On Feb 16, 8:05 am, Khoury Brazil wrote: > > > > > > > > > On Wed, Feb 15, 2012 at 5:51 PM, Daniel Pittman > > wrote: > > > On Wed, Feb 15, 2012 at 17:26, Khoury Brazil > > > wrote: > > >> On Thu, Feb 9, 2012 at 1:09 PM, Daniel Pittman > > >> wrote: > > > >>> On Thu, Feb 9, 2012 at 06:12, mukulm wrote: > > > >>> > I want tocachethe updates for the users system received from the > > >>> > server so that the users can get the updates > > >>> > from the local systemcachewhile offline. > > > >>> > Any idea how can server updates be stored on the users system while > > >>> > offline ? > > > >>> You likely want `--usecacheonfailure`, or the equivalent setting in > > >>> `puppet.conf`: > > > >>>http://docs.puppetlabs.com/references/stable/configuration.html#useca... > > > >>> Whether to use the cached configuration when the remote configuration > > >>> will not compile. This option is useful for testing new > > >>> configurations, where you want to fix the broken configuration rather > > >>> than reverting to a known-good one. > > > >>> That should also apply when you can't communicate with the master. > > > >> Unfortunately, at least in my case, when I run puppet on a client that > > >> is off of the network (in this particular case its a Macbook Pro) it > > >> seems that something is failing locally, causing a "warning: not using > > >>cacheon failed catalog". > > > […] > > >> This is the output from an offline debug run: > > >> macbookproagent:/ admin$ sudo puppet agent -t --debug > > > > One of the features of the `-t` or `--test` flag is that it disables > > > use of the cached catalog when you can't fetch it down. Does it work > > > better if you don't specify `--test`? > > > > If not, please file a bug report. :) > > > -- > > > Daniel Pittman > > > ⎋ Puppet Labs Developer –http://puppetlabs.com > > > ♲ Made with 100 percent post-consumer electrons > > > > -- > > > I guess I *was* missing something (something very obvious...). Thanks > > for the help, that was indeed the issue. :) -- 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 unless behaviour with a dependency
On Feb 20, 4:39 am, jimbob palmer wrote:
> On Feb 17, 5:22 pm, jimbob palmer wrote:
>
> > On Feb 17, 5:12 pm, Adam Heinz wrote:
>
> > > Something like this?
>
> > > exec { "second command":
> > > refreshonly => true,
> > > subscribe => Exec["first command"],
>
> > > }
>
> > Gah! I'm five minutes behind you. It works - THANKS.
>
> The problem that this creates is that *any* update now runs the
> command from the subscribe, which isn't ideal, but I guess will work
> for now :)
I don't follow. Do you mean that if any resource at all on the target
node is updated by Puppet, then the second Exec runs? That should not
be. An Exec marked with "refreshonly => true" should only run if it
receives a signal.
Or do you mean that the *first* command is executing on every Puppet
run? That's not influenced by the DSL fragment you quoted.
Here's a complete example that should work:
class test::manage_my_file {
$my_file = '/tmp/test'
$target_string = 'So long, and thanks for all the fish'
file { "${my_file}": ensure => 'file' }
exec { 'command_one':
command => "echo '${target_string}' >> ${my_file}",
unless => "grep -q '${target_string}' ${my_file}",
require => File["${my_file}"]
}
exec { 'command_two':
command => "/bin/cp ${my_file} /tmp/test2",
refreshonly => true,
subscribe => Exec[ 'command_one' ]
}
}
node default {
include 'test::manage_my_file'
}
With that as your site.pp (to exclude any possibility of influence by
other manifest files), you should see Exec['command_one'] run unless
the string "So long, and thanks for all the fish" is present in file /
tmp/test on the target node (any target node). If Exec['command_one']
runs then Exec['command_two'] should run after. If
Exec['command_one'] *does not* run, then neither should
Exec['command_two'].
If Exec['command_one'] runs when /tmp/test already contains the target
string, or if Exec['command_two'] runs when Exec['command_one'] did
not first run in the same session, then you should file a bug report.
If this approach does not appear to work when you adapt it to your
problem, then do check at least these things:
1) that your 'unless' command is exiting with the expected return
code. If it always returns a false (non-zero) exit code then the two
execs will always run.
2) that no other resource is set to 'notify' Exec['command_two']. If
you use resource defaults anywhere in your configuration then don't
forget to check those, too. Also, beware of any resource notifying a
collection of Execs, as such a collection could easily include
Exec['command_two'] without explicitly naming it.
John
--
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-forge.. do I remember correctly?
Do I remember correctly that puppet-forge is no longer accepting uploads? -- Peter L. Berghold Owner, Shark River Technical Solutions LLC -- 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: roolback to previouse configuration
On Feb 19, 4:07 pm, ruslan usifov wrote:
> Does anybody share how to roll-back configuration if puppet definition on
> host is change. For example Let's assume we have host on which initial was
> web server and bunch of users. All this resources we configured throw
> puppet.
>
> node
> {
>
>
>
>
>
>
> }
>
> At some point we decide to remove user2 so node config now looks like:
>
> node
> {
>
>
>
>
>
> }
>
> but how to remove all user2 stuff that was on host? Undoubtedly we can
> rewrite node definition like this:
>
> node
> {
>
>
>
>
>
>
> }
>
> But imho this doesn't look very good, becouse user removed only one time,
> but node definition will be apply periodical.
You are committing a common conceptual mistake. Puppet is a state
management service, not a script script engine, therefore it is
inappropriate to characterize a declaration as "". Much better would be "".
That matters, because it reflects that fact that Puppet not only will
remove user2, but it will also ensure that user2 *stays* removed
(because Puppet is a state management service). If you do not want
Puppet to perform such a work for you, then just remove the user in
question from management (delete its declaration from you manifest),
and perform the actual user removal by some other means. If you need
to do that across multiple systems then something like Puppetlab's
MCollective might be worth your attention.
> Also this concerns webserver and other resources configured throw puppet.
> How cleanup if resource definition will be removed from node?
For many resource types, another alternative to to purge unmanaged
resources via the 'Resources' meta-resource type. There is even
special support for excluding unmanaged system users from purging.
Beware: purging unmanaged resources can be very dangerous because it
can be difficult to be certain that you have all wanted resources
under management. There is a significant risk of removing wanted, but
unmanaged, resources.
John
--
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-forge.. do I remember correctly?
On Mon, Feb 20, 2012 at 7:06 AM, Peter Berghold wrote: > Do I remember correctly that puppet-forge is no longer accepting uploads? I don't think so. Did you run into a problem uploading? -- Nigel Kersten Product 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.
[Puppet Users] Parameterized classes override of parameter
Hi group,
I expect parameterized classes to behave simular to types in relation
to overrides, but obviously this is not the case.
Could someone what is should then expect from overriding an parameterized class.
what I have is:
class dns(dns_servers) {
file{'/etc/resolv.conf':
content => template("dns/resolv.conf.erb")
}
}
class role::init {
class{'dns':
dns_servers => ['10.100.100.1']
}
}
class role::loadbalancer inherits role {
Class['dns'] {
dns_servers => ['127.0.0.1']
}
}
node loadbalancer1 {
include role::loadbalancer
}
I expected resolv.conf to have the 127.0.0.1 address, but it has the
10.100.100.1 address.
Could someone explain to me the rules around parameterized class inheritence.
And if using inheritence to override general use cases for very common
modules is not the way, should all this logic then be put into our
extlookup or something like hiera?
Jos
--
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-forge.. do I remember correctly?
I most certainly did and immediately had a "senior moment" trying to remember if the puppet forge had be decommed in favor of github. Last night I tried uploading a module that I had written and cleaned up for public consumption and kept getting "must be a tar.gz file" error messages. The file in question was a tar.gz file yet nothing I did seemed to fix the problem. I'll try again later and see if I have better luck.. On Mon, Feb 20, 2012 at 11:24 AM, Nigel Kersten wrote: > > > On Mon, Feb 20, 2012 at 7:06 AM, Peter Berghold > wrote: > >> Do I remember correctly that puppet-forge is no longer accepting uploads? > > > I don't think so. Did you run into a problem uploading? > > -- > Nigel Kersten > Product 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. > -- Peter L. Berghold Owner, Shark River Technical Solutions LLC -- 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-forge.. do I remember correctly?
On Mon, Feb 20, 2012 at 8:35 AM, Peter Berghold wrote: > I most certainly did and immediately had a "senior moment" trying to > remember if the puppet forge had be decommed in favor of github. > That's not going to happen, although we are looking at making it simpler and more transparent for authors who are keeping their modules on github to have automatic updates and publishing via the Forge view. > > Last night I tried uploading a module that I had written and cleaned up > for public consumption and kept getting "must be a tar.gz file" error > messages. The file in question was a tar.gz file yet nothing I did seemed > to fix the problem. I'll try again later and see if I have better luck.. > Please let me know if you're still hitting that, and we'll chase it up. > > > > On Mon, Feb 20, 2012 at 11:24 AM, Nigel Kersten wrote: > >> >> >> On Mon, Feb 20, 2012 at 7:06 AM, Peter Berghold >> wrote: >> >>> Do I remember correctly that puppet-forge is no longer accepting uploads? >> >> >> I don't think so. Did you run into a problem uploading? >> >> -- >> Nigel Kersten >> Product 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. >> > > > > -- > Peter L. Berghold > Owner, Shark River Technical Solutions LLC > > -- > 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. > -- Nigel Kersten Product 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] Puppet agent fails to start on Windows Server 2008 with --listen option
Hi Andrei, On Mon, Feb 20, 2012 at 3:43 AM, Andrei Pashkevich wrote: > Hi all, > I'm trying to start puppet agent on windows machine with --listen > option: > puppet agent --no-daemonize --verbose --listen > > But in this case I`m receiving the following error message: > > notice: Starting Puppet client version 2.7.10 > D:/Ruby187/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:72:in > `setup_logger': uninitialized constant Fcntl::F_SETFD (NameError) >from D:/Ruby187/lib/ruby/site_ruby/1.8/puppet/network/http/ > webrick.rb:20:in `listen' >from D:/Ruby187/lib/ruby/site_ruby/1.8/puppet/network/ > server.rb:100:in `listen' >from D:/Ruby187/lib/ruby/site_ruby/1.8/puppet/network/ > server.rb:115:in `start' >from D:/Ruby187/lib/ruby/site_ruby/1.8/puppet/daemon.rb:123:in > `start' >from D:/Ruby187/lib/ruby/site_ruby/1.8/puppet/application/ > agent.rb:347:in `main' >from D:/Ruby187/lib/ruby/site_ruby/1.8/puppet/application/ > agent.rb:302:in `run_command' >from D:/Ruby187/lib/ruby/site_ruby/1.8/puppet/application.rb: > 309:in `run' >from D:/Ruby187/lib/ruby/site_ruby/1.8/puppet/application.rb: > 412:in `hook' >from D:/Ruby187/lib/ruby/site_ruby/1.8/puppet/application.rb: > 309:in `run' >from D:/Ruby187/lib/ruby/site_ruby/1.8/puppet/application.rb: > 404:in `exit_on_fail' >from D:/Ruby187/lib/ruby/site_ruby/1.8/puppet/application.rb: > 309:in `run' >from D:/Ruby187/lib/ruby/site_ruby/1.8/puppet/util/ > command_line.rb:69:in `execute' >from D:/Ruby187/bin/puppet:4 > > I've tried to use 2.7.9 puppet agent, but without any luck too. > > Any ideas how to workaround this problem? This is a bug, filed as https://projects.puppetlabs.com/issues/12725 Josh -- Josh Cooper Developer, Puppet Labs -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Google Summer of Code 2012
Puppet Labs will apply to be a mentoring organization for Google Summer of Code[1] this year. The first part of this process is to come up with some great ideas for improvements and features in our open source projects. While internally we have many ideas for projects for GSOC, I wanted to take this opportunity to solicit feedback from the community. If you were going to hire somebody to improve Puppet in a summer, what would you have them work on? If you have ideas, please put them on our wiki: http://projects.puppetlabs.com/projects/puppet/wiki/GSOC12 If you see ideas on the wiki page you like, add a comment. Feel free to expand on an entry, or create your own entry. We'll be scoping out ideas in more detail to have ready when we submit our GSOC application. Deadline for ideas is Monday, 27 Feb. Thanks, Mike Stahnke [1] http://code.google.com/soc/ -- 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] Cannot see node on Live Management
On Mon, Feb 20, 2012 at 4:29 AM, Mark B wrote: > The node and reports show up on the dashboard but not on the live > management tab. > > Does anyone have any suggestions? is this a permissions issue? > Is the node in the default group in the dashboard? Puppet runs setup the mcollective/live management bits. The class is called pe_mcollective. > -- > 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.
RE: [Puppet Users] Cannot see node on Live Management
Yes it is in the default group. I am wondering if it is a permissions issue for the puppet user account? Does that need anything special for live management ? Reminder: it shows on all other tabs on the puppet console...just not live management. -Original Message- From: puppet-users@googlegroups.com [mailto:puppet-users@googlegroups.com] On Behalf Of Michael Stahnke Sent: Monday, February 20, 2012 2:31 PM To: puppet-users@googlegroups.com Subject: Re: [Puppet Users] Cannot see node on Live Management On Mon, Feb 20, 2012 at 4:29 AM, Mark B wrote: > The node and reports show up on the dashboard but not on the live > management tab. > > Does anyone have any suggestions? is this a permissions issue? > Is the node in the default group in the dashboard? Puppet runs setup the mcollective/live management bits. The class is called pe_mcollective. > -- > 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. -- 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] Cannot see node on Live Management
Have you tried su-ing to the peadmin user on the master node and trying `mco ping`? Live Management is basically a front end for actions the peadmin user can do. Dropping down to that level may let you debug the issue easier. Other things to check are that activemq is working and correctly configured on the master, as well as mcollective on all of your agent nodes. You may also find more users that understand your question on the pe-users list (I assume if you're using Live Management you're using PE) - Justin On Mon, Feb 20, 2012 at 11:35 AM, Littman, Mark B wrote: > Yes it is in the default group. I am wondering if it is a permissions > issue for the puppet user account? Does that need anything special for live > management ? > > Reminder: it shows on all other tabs on the puppet console...just not live > management. > > > -Original Message- > From: puppet-users@googlegroups.com [mailto:puppet-users@googlegroups.com] > On Behalf Of Michael Stahnke > Sent: Monday, February 20, 2012 2:31 PM > To: puppet-users@googlegroups.com > Subject: Re: [Puppet Users] Cannot see node on Live Management > > On Mon, Feb 20, 2012 at 4:29 AM, Mark B wrote: > > The node and reports show up on the dashboard but not on the live > > management tab. > > > > Does anyone have any suggestions? is this a permissions issue? > > > Is the node in the default group in the dashboard? Puppet runs setup the > mcollective/live management bits. The class is called pe_mcollective. > > > > -- > > 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. > > -- > 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] Controlling agent catalog cache expiration
Hi, Starting a new thread since the question and problem are completely different at this point. I've written modules that implement a client side firewall and overwrite and flush any changes made by a user. This is mandated by several different internal security policies and of course compliance. I'm pretty much at the stage where I'm ready to start deploying but recently hit a snag: catalog expiration on the client. The client caches and uses the cached catalog as expected, but unfortunately if a client is "off-network" for too long the catalog expires and we get fun stuff like: Not using expired catalog for from cache; expired at I've tried using 'use_cached_catalog' just as a test, but it appears that an expiration date in a catalog takes priority over everything else. Of course manually changing the expiration date in the catalog yaml file fixes the issue, and I've written a short shell script that can do it based on the client's network, but that feels like a big kludge. Since these clients are laptops it would be nice to have the ability to use the cached catalog until the client is back on the network that the puppet master is on. Our laptops can, in less than ideal circumstances, be off-network for 1-2 weeks. Is there a way to have the agent use the cached catalog until it can reach the master again, regardless of the expiration? This is probably an edge case, since most of the time most of us are probably using puppet with servers and perhaps 'mostly-online' client workstations. Even when dealing with laptops, I imagine for most there's not frequently a concern about a consistent and frequent applications of a catalog to conform with security policies. Thanks for any insight you may have. Best, Khoury -- 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] Issues with Puppet 2.7.10: recommendation to stop using it
Would it be worth updating the release notes wiki to note that the release is no longer recommended? Generally that's where I look for information about a particular release: http://projects.puppetlabs.com/projects/1/wiki/Release_Notes#2.7.10 Best, Khoury On Sun, Feb 19, 2012 at 5:09 PM, Michael Stahnke wrote: > We pulled the native packages from our apt and yum repos, as well as > the gem from rubygems.org. We left 2.7.10 in the /downloads area in > the event that somebody was using it (and having it work) and wanted > to standardize their systems. It's not ideal, but we didn't have a > better option that seemed super obvious. > > Mike > -- 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] Controlling agent catalog cache expiration
On Mon, Feb 20, 2012 at 12:00 PM, Khoury Brazil wrote: > Hi, > > Starting a new thread since the question and problem are completely > different at this point. I've written modules that implement a client > side firewall and overwrite and flush any changes made by a user. This > is mandated by several different internal security policies and of > course compliance. I'm pretty much at the stage where I'm ready to > start deploying but recently hit a snag: catalog expiration on the > client. The client caches and uses the cached catalog as expected, but > unfortunately if a client is "off-network" for too long the catalog > expires and we get fun stuff like: > > Not using expired catalog for from cache; expired at > > I've tried using 'use_cached_catalog' just as a test, but it appears > that an expiration date in a catalog takes priority over everything > else. I think you've already stumbled on the answer in the previous thread. The cache timeout is unfortunately tied to runinterval setting. I'm pretty sure there's a ticket requesting to split them up. The closest thing you can do today: run puppet agent through cron instead of running a daemon. configure runinterval to a much longer period. Thanks, 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] Controlling agent catalog cache expiration
On Mon, Feb 20, 2012 at 12:07 PM, Nan Liu wrote: > I think you've already stumbled on the answer in the previous thread. > The cache timeout is unfortunately tied to runinterval setting. I'm > pretty sure there's a ticket requesting to split them up. The closest > thing you can do today: Is there any way I can add my support to that ticket? > > run puppet agent through cron instead of running a daemon. > configure runinterval to a much longer period. Thanks Nan. A few more questions, if you don't mind: What's the effect of the runinterval on the expiration date? If I set the runinterval to 14 days, can I then expect a cached catalog to expire 14 days after compiled? Does the catalog expiration affect how often it pulls a new compiled catalog from the puppet master? For example: If node01 has a cached catalog that was compiled on 02/23/2012, expires on 03/08/2012 and the client is back on the network with the puppet master again on 02/26/2012 does the client pull a new catalog that would then expire on 03/11/2012? Thanks, Khoury -- 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] Issues with Puppet 2.7.10: recommendation to stop using it
Khoury, Good point. I've updated the wiki/release notes to reflect the change. Thanks! -Matthaus On Mon, Feb 20, 2012 at 12:07 PM, Khoury Brazil wrote: > Would it be worth updating the release notes wiki to note that the > release is no longer recommended? Generally that's where I look for > information about a particular release: > > http://projects.puppetlabs.com/projects/1/wiki/Release_Notes#2.7.10 > > Best, > Khoury > > On Sun, Feb 19, 2012 at 5:09 PM, Michael Stahnke > wrote: >> We pulled the native packages from our apt and yum repos, as well as >> the gem from rubygems.org. We left 2.7.10 in the /downloads area in >> the event that somebody was using it (and having it work) and wanted >> to standardize their systems. It's not ideal, but we didn't have a >> better option that seemed super obvious. >> >> Mike >> > > -- > 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.
Re: [Puppet Users] Controlling agent catalog cache expiration
On Mon, Feb 20, 2012 at 12:32 PM, Khoury Brazil wrote: > On Mon, Feb 20, 2012 at 12:07 PM, Nan Liu wrote: >> I think you've already stumbled on the answer in the previous thread. >> The cache timeout is unfortunately tied to runinterval setting. I'm >> pretty sure there's a ticket requesting to split them up. The closest >> thing you can do today: > > Is there any way I can add my support to that ticket? +1 and watch the ticket, and of course I can't find the ticket # in redmine at the moment. >> run puppet agent through cron instead of running a daemon. >> configure runinterval to a much longer period. > > Thanks Nan. A few more questions, if you don't mind: > What's the effect of the runinterval on the expiration date? If I set > the runinterval to 14 days, can I then expect a cached catalog to > expire 14 days after compiled? Does the catalog expiration affect how > often it pulls a new compiled catalog from the puppet master? For > example: If node01 has a cached catalog that was compiled on > 02/23/2012, expires on 03/08/2012 and the client is back on the > network with the puppet master again on 02/26/2012 does the client > pull a new catalog that would then expire on 03/11/2012? Catalog expiration does not affect pulling new catalogs, just how long it takes to expire. The behavior you described matches what I saw last time when I tried this. Thanks, 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] Parameterized classes override of parameter
On Mon, Feb 20, 2012 at 8:24 AM, Jos Houtman wrote:
> Hi group,
>
> I expect parameterized classes to behave simular to types in relation
> to overrides, but obviously this is not the case.
> Could someone what is should then expect from overriding an parameterized
> class.
>
> what I have is:
>
> class dns(dns_servers) {
> file{'/etc/resolv.conf':
> content => template("dns/resolv.conf.erb")
> }
> }
>
> class role::init {
> class{'dns':
> dns_servers => ['10.100.100.1']
> }
> }
>
> class role::loadbalancer inherits role {
> Class['dns'] {
> dns_servers => ['127.0.0.1']
> }
> }
>
> node loadbalancer1 {
> include role::loadbalancer
> }
>
> I expected resolv.conf to have the 127.0.0.1 address, but it has the
> 10.100.100.1 address.
>
> Could someone explain to me the rules around parameterized class inheritence.
> And if using inheritence to override general use cases for very common
> modules is not the way, should all this logic then be put into our
> extlookup or something like hiera?
Parametrized classes do not behave like resources, so you can't
override them in an inherited class. In your case, either do not
inherit and declare the class separately, or declare include ntp, and
change class definition to dns(dns_servers=hiera('dns_server')) {...}
Thanks,
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] limiting definition variable values
Hello,
Can you limit the values which might be passed to a definition? I
haven't been able to find any examples and anything I've tried based
on reading the docs has been fruitless. I'm creating some templates
for config files and certainly values are only allowed limited values.
like ipv4, ipv6, any, etc. I could always add a note saying "see
manpage for proper values" but I'm just trying to add some sanity
checks.
simple example:
class config (
$protocol = "any" or "ipv4" or ipv6"
) { #pass to a template }
--
Later,
Darin
--
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] limiting definition variable values
On Mon, Feb 20, 2012 at 1:38 PM, Darin Perusich wrote:
> Hello,
>
> Can you limit the values which might be passed to a definition? I
> haven't been able to find any examples and anything I've tried based
> on reading the docs has been fruitless. I'm creating some templates
> for config files and certainly values are only allowed limited values.
> like ipv4, ipv6, any, etc. I could always add a note saying "see
> manpage for proper values" but I'm just trying to add some sanity
> checks.
>
> simple example:
> class config (
> $protocol = "any" or "ipv4" or ipv6"
> ) { #pass to a template }
See puppetlabs-stdlib validate* functions:
https://github.com/puppetlabs/puppetlabs-stdlib
Thanks,
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] Problem with Custom Facter
I am trying to write a custom facter for CentOS/RHEL that tells me how many
updates are found on a run of 'yum check-update'
Facter.add(:cis_yum_check) do
timeout = 300
setcode do
File.open("/tmp/yum_check-update", 'w') { |f| f.write(`/usr/bin/yum
check-update`) }
back_arr = []
f = `cat /tmp/yum_check-update`
f.lines.reverse_each { |line| back_arr << line }
"#{back_arr.index("\n")} updates"
end
end
The output I get back in my fact reports only contains a string with "
updates" in it, so no number. However, if I paste the code inside the
setcode block into a test.rb scriptit works just fine.
Can anyone tell me why I'm not getting the number in my fact?
Thanks,
Matt
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Triggering an action on "ensure: removed"
Dear Puppet,
I wish to run an Exec when a puppet define is removed. The define puts
a file in /tmp/foobar/${name}. When the define is no longer there, the
purge does an ensure => removed, and the file gets deleted. I've also
been able to make this work with Tidy[] instead of purge.
eg:
file { '/tmp/foobar/':
ensure => directory,# make sure this is a directory
recurse => true,# recursively manage directory
purge => true, # purge all unmanaged files
force => true, # also purge subdirs and links
owner => root, group => nobody, mode => 600, backup => false,
}
The problem:
including a notify => Exec['whatever'] does not work. Either this is a
bug, and/or perhaps someone could suggest a workaround.
Much appreciated,
James
--
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: Issues with Puppet 2.7.10: recommendation to stop using it
Not to sound impatient (grin), but any idea of a rough eta for 2.7.11? I'm close to deploying puppet and have done all testing on 2.7.10, need to make a decision on whether to wait or start testing with 2.7.9 in the next few days. Thanks, Adam On Feb 19, 4:15 pm, Michael Stahnke wrote: > We are continuing to see several issues introduced Puppet 2.7.10. We > are recommending that users discontinue its usage. This could mean > using 2.7.9 or waiting patiently until we can get 2.7.11 out the door. > > These are the most significant tickets around the 2.7.10 regressions. > > http://projects.puppetlabs.com/issues/show/12310http://projects.puppetlabs.com/issues/show/12269http://projects.puppetlabs.com/issues/show/12269http://projects.puppetlabs.com/issues/show/12588 > > We should have declared this as a problem release earlier. I > apologize for not doing so. > > As always, if you have issues or questions, please contact us. > > Mike Stahnke > > stahnma in #puppet -- 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 with Custom Facter
On Mon, Feb 20, 2012 at 5:33 PM, Matt Mencel wrote: > The output I get back in my fact reports only contains a string with " > updates" in it, so no number. However, if I paste the code inside the > setcode block into a test.rb scriptit works just fine. Are you testing this code on the same version of EL that you are deploying to? AFACT #lines wasn't added until 1.8.7 and if you are deploying to EL5 you don't have that. -- Nathan Powell Linux System Administrator "Where else would you rather be than right here, right now?" ~ Marv Levy -- 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 with Custom Facter
On Mon, Feb 20, 2012 at 5:33 PM, Matt Mencel wrote:
> I am trying to write a custom facter for CentOS/RHEL that tells me how many
> updates are found on a run of 'yum check-update'
Sorry I replied hastily. After replying I thought about what you're
trying to do. You don't need all those gyrations to get this data
Tested quickly on RHEL6 and CentOS5:
`sudo yum check-update -q`.split(/\n/).reject{|i| i == ""}.length
--
Nathan Powell
Linux System Administrator
"Where else would you rather be than right here, right now?"
~ Marv Levy
--
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: overriding parts of a collection of defined resources
Thanks Aaron, Marc and Nan for your responses. All of your tips are
very useful. I think Nan's suggestion nails it for me and helps clear
up a misunderstanding I had about what could be overridden. I think
the part of Nan's response that I like better than using the
"collapsed" way of writing definitions and/or using resource defaults
is it let's me construct the source attribute from the resource title
(${name}) vs. having to specify the file path twice. I realize this is
a little thing that is just a matter of taste so it is great to learn
of the other options. Plus, I've had my eye on hiera for a while, this
might be a good place to put it in practice.
Thanks again to everyone for their help.
-- dNb
--
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 ssl issues.
So I come in to work monday only to find that none of our puppet clients are working. When I run puppetd -t I get these errors: http://pastebin.com/6iwhG2Y2 I go to the puppet master server and look at /var/log/puppet/ masterhttp.log and see a bunch of these openssl errors: http://pastebin.com/1jgVX4ui I checked and made sure the time and date was the exact same across all the servers and even tried restarting it but to no avail. Is this an issue with webrick or puppetmaster or the puppet clients? -- 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 ssl issues.
> Is this an issue with webrick or puppetmaster or the puppet clients? Try to resign any of your certs manually? -- Krish OlinData.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] Parameterized classes override of parameter
This is actually filed in Bug #5517 (Accepted) and a few others and has 10 votes. http://projects.puppetlabs.com/issues/5517 -- 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/-/T-tcPreqc10J. 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 ssl issues.
I have the puppet master set up to auto sign them. I did a puppetca -- clean FQDN and tried to readd it but I get the same issue. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: puppet ssl issues.
On Mon, Feb 20, 2012 at 9:50 PM, Digital Ninja wrote: > I have the puppet master set up to auto sign them. I did a puppetca -- > clean FQDN and tried to readd it but I get the same issue. > > If you clean the cert on the server side, then you need to blow away the $ssldir on the client side too. On a test client, run `puppet config print ssldir` to get the path where the ssl information is being stored client-side. Remove that directory and then try running puppet agent -t again to concat the master and generate a csr. The master should auto-sign and you should be good. I would definitely encourage you to look towards using something other than Webrick in this situation. You also mentioned that the time on the master/agents WAS synced? It's not off by any significant amount? > -- > 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. > > -- Gary Larizza Professional Services Engineer Puppet Labs -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: puppet ssl issues.
*CONTACT and not 'concat' On Mon, Feb 20, 2012 at 10:01 PM, Gary Larizza wrote: > > > On Mon, Feb 20, 2012 at 9:50 PM, Digital Ninja wrote: > >> I have the puppet master set up to auto sign them. I did a puppetca -- >> clean FQDN and tried to readd it but I get the same issue. >> >> > If you clean the cert on the server side, then you need to blow away the > $ssldir on the client side too. On a test client, run `puppet config print > ssldir` to get the path where the ssl information is being stored > client-side. Remove that directory and then try running puppet agent -t > again to concat the master and generate a csr. The master should auto-sign > and you should be good. > > I would definitely encourage you to look towards using something other > than Webrick in this situation. > > You also mentioned that the time on the master/agents WAS synced? It's > not off by any significant amount? > > > >> -- >> 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. >> >> > > > -- > > Gary Larizza > Professional Services Engineer > Puppet Labs > > -- Gary Larizza Professional Services Engineer 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.
