[Puppet Users] Re: [ACTION] Changes to release package links
As of this morning I notice that the old directories have been restored
under yum.puppetlabs.com -- the el/fedora repos, the puppet-nightly
directories, the pc1 stuff, everything.
On Wednesday, May 15, 2019 at 7:04:53 PM UTC-4, Chris Taylor wrote:
>
> Try
> http://release-archives.puppet.com/yum/el/7/PC1/x86_64/puppetlabs-release-pc1-1.1.0-5.el7.noarch.rpm
>
> Just be aware it will probably install a repo with yum.puppetlabs.com
> into /etc/yum.repos.d/, so you will need to update the path to the
> appropriate place.
>
>
> On Wednesday, May 15, 2019 at 11:25:19 PM UTC+1, michael mack wrote:
>>
>> How do you get the following old repo to work?
>>
>> rpm -Uvh
>> https://yum.puppetlabs.com/puppetlabs-release-pc1-el-7.noarch.rpm
>>
>>
>> On Monday, April 22, 2019 at 2:31:09 PM UTC-7, Molly Waggett wrote:
>>>
>>> TLDR: On May 14, 1. yum release packages will move to the top-level of
>>> yum.puppet.com; 2. links to nightly release packages will be removed
>>> from {yum,apt}.puppet.com; and 3. PC1 (and older) packages will be
>>> moved to release-archives.puppet.com.
>>>
>>> All Puppet-maintained tooling and documentation referencing these paths
>>> will be updated by the time these changes are made. Please ensure that
>>> you are using current versions.
>>>
>>> Read on for details, especially if you've written custom tooling with
>>> hard-coded download paths (e.g. CI testing or provisioning workflows).
>>>
>>> ---*---*---
>>>
>>> Hey folks,
>>>
>>> In an effort to reduce clutter and confusion on some of our public
>>> download sites (yum.puppet.com, apt.puppet.com, downloads.puppet.com,
>>> and nightlies.puppet.com), we are planning to make some changes.
>>>
>>> 1. Release packages (for all active streams) will live at the top level
>>> only.
>>>
>>> This change only affects yum.puppet.com (and nightlies.puppet.com/yum),
>>> giving us consistency with the layout on apt.puppet.com. Currently, yum
>>> release packages live inside their corresponding repo directory, e.g.
>>> yum.puppet.com/puppet6/puppet6-release-fedora-28.noarch.rpm
>>> .
>>> THESE WILL BE REMOVED.
>>>
>>> Here are some examples of where you will be able to find release
>>> packages:
>>>
>>> Old: yum.puppet.com/puppet6/puppet6-release-el-7.noarch.rpm
>>>
>>> New: yum.puppet.com/puppet6-release-el-7.noarch.rpm
>>>
>>> Old: nightlies.puppet.com/yum/puppet-nightly/
>>> puppet-nightly-release-sles-12.noarch.rpm
>>>
>>> New: nightlies.puppet.com/yum/puppet-nightly-release-sles-12.noarch.rpm
>>>
>>> These new paths are currently available for use. We plan to remove the
>>> old ones on May 14. Please plan to make all updates during this period.
>>>
>>> 2. There will be no links to nightlies from main download sites.
>>>
>>> Links like yum.puppet.com/puppet-nightly
>>>
[Puppet Users] master+agent setup on vms with proxy
Hello, i am trying to run a master+agent setup on 2 Centos 7 vms with one ethernet adapter for internetconnection and one for the connection between the 2 vms. But I cant seem to get them together. Since i am behind a company proxy i entered the proxy in the yum.conf and the /etc/environment to get the packages. I have given each vm an ip(ping works) in the same net for the 2. adapters and have entered the ips and hostnames in /etc/hosts. Anything helps. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/e3743d7a-1096-45dd-b162-7ef498c2254e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Error while installing/configuring foreman-proxy 1.12: Invalid parameter dns_realm on Class[Foreman_proxy]
On 6 December 2016 at 19:40, Sankara <sarasnm2...@gmail.com> wrote: > While running “puppet agent -t” (to install and configure foreman-proxy) , I am getting the below error on my node. Can you please help me to find what could be the issue? > > Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Invalid parameter dns_realm on Class[Foreman_proxy] at /dev/modules/fmanproxy/manifests/config.pp:128 on node poc-agent.local > Warning: Not using cache on failed catalog > Error: Could not retrieve catalog; skipping run Looking at https://github.com/theforeman/puppet-foreman_proxy/blob/master/manifests/init.pp the $dns_realm parameter isn't exposed for configuration - it's only used within params.pp to set $dns_tsig_principal (which *is* available in init.pp). Feel free to submit a bug or even send a patch if you feel that behaviour is wrong :) Cheers Greg -- Greg Sutcliffe Community Lead, Foreman IRC: gwmngilfen -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAE%3D3ySCn1%2BVMGyGn-FD1JcwGKbZvNBo4vU7HdaYuSn1pt58k9A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Re: Deploy bacula with puppet and foreman
On 2 February 2016 at 18:31, Timotheus Titus <spqrincorpora...@gmail.com> wrote: > As far as I see I have to call bacula::director::client somehow as it > defines the client-config. > > But the question is: How can I do that? > > I'm not familiar with the bacula module, but bacula::director::client seems to be a define rather than a class. ENCs (which is what Foreman is to Puppet) cannot directly declare defines, they can can only declare classes and parameters. The common pattern for this is to use a wrapper class, taking hash of data that you can use with create_resources. We get this question a lot on the Foreman mailing list, so we have a wiki page detailing some examples. See http://projects.theforeman.org/projects/foreman/wiki/Instantiate_Puppet_resources Hope that helps! Greg -- Greg Sutcliffe IRC: gwmngilfen -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAE%3D3ySANqg%3DaOhpZ9CYbQXtcsJL7Vu4SToVtubgbhZ89pKndSQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Can I just edit the dashboard widgets?
On 13 October 2015 at 15:54, UK_beginner <simon.han...@gmail.com> wrote: > I'm wanting to make some changes to the conditions used in building the > dashboard lists - is it possible to just edit the erb files in > app/views/dashboard? > > I've tried editing one of the conditions in the _status_widget.html.erb but > even after restarting foreman & logging out and back in, the dashboard > doesn't reflect the changes? I'm guessing this is a Foreman-specific question? You might have more luck getting replies on the Foreman Users list - https://groups.google.com/forum/#!forum/foreman-users since not everyone here uses Foreman. Cheers, Greg -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAE%3D3ySCLjK6SXQ_YLVCu8X1JfYZzbSG7MCeSxvAFhAJxKi4wcw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Could not find declared class transfer_contents
Hi there,
I am going through this
tutorial:
http://projects.puppetlabs.com/projects/1/wiki/simplest_puppet_install_pattern
I am having trouble with Step two: Create a test manifests - specifially
the application of tests manifests with the noop flag
my current configuration is as follows:
/home/redshelf/source/puppet
which contains: nothing
/etc/puppet/modules/transfer_contents/manifests/init.py
which contains:
class transfer_contents {
file { /home/redshelf/source/puppet/rc.local:
ensure = 'present',
mode = '740',
content = '#!/bin/sh
umount /dev/xvdb || :
mkswap /dev/xvdb
swapon /dev/xvdb
exit 0'
}
}
/etc/puppet/modules/transfer_contents/tests/init.py
which contains:
class {'transfer_contents': }
I then run the command:
puppet apply --noop /etc/puppet/modules/transfer_contents/tests/init.pp
and I get:
*Warning: Could not retrieve fact fqdn*
*Error: Puppet::Parser::AST::Resource failed with error ArgumentError:
Could not find declared class transfer_contents at
/etc/puppet/modules/transfer_contents/tests/init.pp:1 on node redshelf-dev*
*Wrapped exception:*
*Could not find declared class transfer_contents*
*Error: Puppet::Parser::AST::Resource failed with error ArgumentError:
Could not find declared class transfer_contents at
/etc/puppet/modules/transfer_contents/tests/init.pp:1 on node redshelf-dev*
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/4ce61c0a-48e6-4c32-810e-618c8d3b7bb0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] PuppetDB connection issue - Failed to connect!!
On Thursday, June 19, 2014 12:17:41 AM UTC+10, Sans wrote: Thanks Rakesh! But, as you probably can guess, that didn't change a thing; still getting the same error. I'm not sure if PuppetDB look in the DNS record (as opposed to hosts file), in that case it never gonna work. Best!! Santanu, Did you ever fix this. I am having the same problem. It is an issue with SSL. Chrome gives this error: Error code: ERR_SSL_PROTOCOL_ERROR. Curl gives this error curl: (35) Unknown SSL protocol error in connection If I figure more out, I will post the fix. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/fa2986d8-6037-485c-8155-51712258c5cf%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Re: puppetdb, foreman, one particular node has a problem
On 16 October 2013 11:48, Steve Wray stevedw...@gmail.com wrote: Sure, I'm using this repository deb http://deb.theforeman.org/ precise stable it looks as if the upgrade didn't make the required changes to the database, or something like that. I dropped the db and recreated it and the error about the missing column went away but still couldn't enroll new nodes. Firstly, as the deb package maintainer for Foreman, I'm sorry you had issues. Thanks also for the bug report - we've just tracked down and fixed an issue which specifically affects sqlite3 upgrades (I'm not sure if you are on sqlite3, but your symptoms fit, I think). 1.3.0-2 is now in the repo with the fix. With regards to upgrades not breaking things, I agree. We spent some time discussing the state of the Debian Foreman repo a few weeks ago[1] and one outcome of that was that we would create a repo for each major version (eg http://deb.theforeman.org/ precise 1.2) and that 'stable' would track the latest release. This was done, and as 1.3 was released on Monday, 'stable' now points to 1.3. The 1.2 repo allows people who wish to be conservative to lock themselves to a particular release. An unavoidable side-effect of this is that since we only had stable before, everyone is currently using it. I accept we could have done a better job of publicising the existence of the 1.2 repo before 1.3 came out though. I've just sent a mail to our users and announce lists to make people more aware of the new repos. Once again, apologies for your troubles, and thanks for the feedback. Greg [1]https://groups.google.com/d/msg/foreman-dev/76A7LmuPzLM/O8ob4aEX3VAJ -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: puppetdb, foreman, one particular node has a problem
On 16 October 2013 14:39, Steve Wray stevedw...@gmail.com wrote: Your response is encouraging, thanks. I wasn't using sqlite, I was using postgresql. I have about 100 nodes (and growing) sqlite quickly became unusable. Ah ok. There are changes to the ENC script (which also registers new Hosts in the Foreman interface) in 1.3, but due to a variety of reasons, the ENC (/etc/puppet/node.rb) isn't packaged. So potentially, that needed an update to fix your host registration problem. One of the things I tried was aptitude install with =version but this didn't work, apparently it couldn't find the old versions in the repo. I started downloading the .debs to install the old versions manually but realised it would be quicker to just uninstall foreman, we had just commissioned a bunch of servers, and more arriving all the time, so I really had to just get a move on. Understandable, I've been in those firefighting situations. It's interesting that this didn't work for you though - I was using that syntax this very morning to test the sqlite3 error fixes :) Honestly, if it hadn't been a Debian-based system, say CentOS, I'd have been a LOT more cautious about the 8upgrade but I've got so used to things just not breaking in stable (last time anything like that bit me was when someone decided to apply a 'security' patch to sudo). When I have some breathing room I'll do some more tests with the newer version of foreman. Looking forward to your feedback. See you on foreman-users :) -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] hiera hash into multiple templates
Hi all,
I've started testing with using Hiera for storing configs and I have a
noobish question.
Here's an example of my yaml file (/etc/puppet/hieradata/vertname.yaml):
---
#icecast
type: vanilla
client1:
cid: 999
cid_hostname: icecast1
cid_ipaddress: 192.168.254.12
password: WhatYoSay?
port: 200
concurrency: 50
num_encoders: 2
client2:
cid: 998
cid_hostname: icecast2
cid_ipaddress: 192.168.254.13
password: NoWay!
port: 201
concurrency: 25
num_encoders: 3
Now, I'd like to be able to create a config file for each client:
file { '/home/icecast/${cid}.icecast.xml':
ensure = file
content = template('icecast/icecast.xml.erb'),
}
The question is how do I put the above into a loop which iterates over the
client arrays in the hiera file (each client config file should get a
unique cid, cid_hostname, etc)?
Thanks in advance!!
Greg
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: hiera hash into multiple templates
Ellison,
Brilliant! Worked like a champ. This opens whole new worlds and should
make managing the config *much* easier!!!
Greg
On Friday, September 27, 2013 12:13:03 PM UTC-7, Ellison Marks wrote:
Perhaps make it a defined type and use the create resources function. I
can't really think of any other way to correctly scope the various
parameters. You'd have to tweak your yaml slightly...
---
#icecast
type: vanilla
icecast_clients:
client1:
cid: 999
cid_hostname: icecast1
cid_ipaddress: 192.168.254.12
password: WhatYoSay?
port: 200
concurrency: 50
num_encoders: 2
client2:
cid: 998
cid_hostname: icecast2
cid_ipaddress: 192.168.254.13
password: NoWay!
port: 201
concurrency: 25
num_encoders: 3
define icecast_client($cid, $cid_hostname, $cid_ipaddress, $password,
$port, $concurrency, num_encoders) {
file { /home/icecast/${cid}.icecast.xml:
ensure = file,
content = template('icecast/icecast.xml.erb'),
}
}
$icecast_clients = hiera('icecast_clients')
create_resources(icecast_client, $icecast_clients)
You could use hiera_hash if you wanted to merge multiple levels of your
hierarchy.
You could also use the cid in place of client1, client2, etc, then you
could remove the $cid parameter in the defined type and just use $title.
On Friday, September 27, 2013 11:52:09 AM UTC-7, Greg Coit wrote:
Hi all,
I've started testing with using Hiera for storing configs and I have a
noobish question.
Here's an example of my yaml file (/etc/puppet/hieradata/vertname.yaml):
---
#icecast
type: vanilla
client1:
cid: 999
cid_hostname: icecast1
cid_ipaddress: 192.168.254.12
password: WhatYoSay?
port: 200
concurrency: 50
num_encoders: 2
client2:
cid: 998
cid_hostname: icecast2
cid_ipaddress: 192.168.254.13
password: NoWay!
port: 201
concurrency: 25
num_encoders: 3
Now, I'd like to be able to create a config file for each client:
file { '/home/icecast/${cid}.icecast.xml':
ensure = file
content = template('icecast/icecast.xml.erb'),
}
The question is how do I put the above into a loop which iterates over
the client arrays in the hiera file (each client config file should get a
unique cid, cid_hostname, etc)?
Thanks in advance!!
Greg
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] augeas question
I've decided to not be blocked by this issue and to have puppet manage the
config file. It's not an ideal solution, but good enough until I learn
more about either augeas or inifile.
Greg
On Monday, September 23, 2013 3:48:05 PM UTC-7, Greg Coit wrote:
Nathan,
Thanks for the response - I did not know about inifile.
I unfortunately seem to be having trouble with ini_setting - the following
causes a new line to be added every time puppet gets run:
ini_setting { 'anonymous_enable':
path= '/etc/vsftpd/vsftpd.conf',
setting = 'anonymous_enable',
value = 'NO',
ensure = present,
}
ini_setting { 'chroot_local_user':
path= '/etc/vsftpd/vsftpd.conf',
setting = 'chroot_local_user',
value = 'YES',
ensure = present,
}
BTW, still playing with augeas too - the most recent code is:
augeas { 'vsftpd.conf':
context = '/files/vsftpd/vsftpd.conf',
incl = '/etc/vsftpd/vsftpd.conf',
load_path = '/usr/share/augeas/lenses/dist/',
lens = 'vsftpd',
changes = [ 'set anonymous_enable NO', 'set chroot_local_user YES',
],
}
Turns out that augeas has an unwelcome behavior - it tries to load all
files that match the lens - if any are non-standard, it errors out.
Greg
On Monday, September 23, 2013 3:00:36 PM UTC-7, Nathan Valentine wrote:
Greg,
I believe resource ini_setting would be appropriate here but I do
understand the desire to learn about Puppet + Augeas.
augeas { 'vsftpd.conf':
context = '/etc/vsftpd/vsftpd.conf',
changes = [ 'set anonymous_enable=NO', 'set
chroot_local_user=YES', ],
require = File['/etc/vsftpd/vsftpd.conf'],
}
context = '*/files*/vsftpd/vsftpd.conf',
?
I'm lazy and haven't tested with a Puppet apply but I think this might
just be an issue of understanding the namespace-y Augeas stuff. You can
test like so with augtool:
$ augtool ls */files*/vsftpd/vsftpd.conf
--
---
Nathan Valentine - nat...@puppetlabs.com
Puppet Labs Professional Services
GV: 415.504.2173
Skype: nrvale0
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] augeas question
LOL - or I could just use one of the 2 vsftpd modules on puppetforge... I
never *intend* to do things the hard way. :)
Greg
On Tuesday, September 24, 2013 9:32:53 AM UTC-7, Greg Coit wrote:
I've decided to not be blocked by this issue and to have puppet manage the
config file. It's not an ideal solution, but good enough until I learn
more about either augeas or inifile.
Greg
On Monday, September 23, 2013 3:48:05 PM UTC-7, Greg Coit wrote:
Nathan,
Thanks for the response - I did not know about inifile.
I unfortunately seem to be having trouble with ini_setting - the
following causes a new line to be added every time puppet gets run:
ini_setting { 'anonymous_enable':
path= '/etc/vsftpd/vsftpd.conf',
setting = 'anonymous_enable',
value = 'NO',
ensure = present,
}
ini_setting { 'chroot_local_user':
path= '/etc/vsftpd/vsftpd.conf',
setting = 'chroot_local_user',
value = 'YES',
ensure = present,
}
BTW, still playing with augeas too - the most recent code is:
augeas { 'vsftpd.conf':
context = '/files/vsftpd/vsftpd.conf',
incl = '/etc/vsftpd/vsftpd.conf',
load_path = '/usr/share/augeas/lenses/dist/',
lens = 'vsftpd',
changes = [ 'set anonymous_enable NO', 'set chroot_local_user
YES', ],
}
Turns out that augeas has an unwelcome behavior - it tries to load all
files that match the lens - if any are non-standard, it errors out.
Greg
On Monday, September 23, 2013 3:00:36 PM UTC-7, Nathan Valentine wrote:
Greg,
I believe resource ini_setting would be appropriate here but I do
understand the desire to learn about Puppet + Augeas.
augeas { 'vsftpd.conf':
context = '/etc/vsftpd/vsftpd.conf',
changes = [ 'set anonymous_enable=NO', 'set
chroot_local_user=YES', ],
require = File['/etc/vsftpd/vsftpd.conf'],
}
context = '*/files*/vsftpd/vsftpd.conf',
?
I'm lazy and haven't tested with a Puppet apply but I think this might
just be an issue of understanding the namespace-y Augeas stuff. You can
test like so with augtool:
$ augtool ls */files*/vsftpd/vsftpd.conf
--
---
Nathan Valentine - nat...@puppetlabs.com
Puppet Labs Professional Services
GV: 415.504.2173
Skype: nrvale0
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] augeas question
Hello,
I'm trying to learn how to use augeas in puppet. One of the packages we
have puppet installing is vsftpd. Rather than putting the vsftpd conf file
in puppet (in case the config file is updated by the upstream maintainers)
I'd like to use augeas to make sure the correct lines exist in the config
file.
Currently, the default vsftpd config file contains the following 21 lines
(among others of course):
anonymous_enable=YES
#chroot_local_user=YES
I'd like to change this to:
anonymous_enable=NO
chroot_local_user=YES
I have the following in a module:
#vsftpd
package { 'vsftpd':
ensure = installed,
}
file { '/etc/vsftpd/vsftpd.conf':
ensure = file,
mode= 600,
require = Package['vsftpd'],
}
augeas { 'vsftpd.conf':
context = '/etc/vsftpd/vsftpd.conf',
changes = [ 'set anonymous_enable=NO', 'set chroot_local_user=YES', ],
require = File['/etc/vsftpd/vsftpd.conf'],
}
But I'm having no luck changing either line.
Any suggestions are welcome - thanks!
Greg
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] augeas question
Nathan,
Thanks for the response - I did not know about inifile.
I unfortunately seem to be having trouble with ini_setting - the following
causes a new line to be added every time puppet gets run:
ini_setting { 'anonymous_enable':
path= '/etc/vsftpd/vsftpd.conf',
setting = 'anonymous_enable',
value = 'NO',
ensure = present,
}
ini_setting { 'chroot_local_user':
path= '/etc/vsftpd/vsftpd.conf',
setting = 'chroot_local_user',
value = 'YES',
ensure = present,
}
BTW, still playing with augeas too - the most recent code is:
augeas { 'vsftpd.conf':
context = '/files/vsftpd/vsftpd.conf',
incl = '/etc/vsftpd/vsftpd.conf',
load_path = '/usr/share/augeas/lenses/dist/',
lens = 'vsftpd',
changes = [ 'set anonymous_enable NO', 'set chroot_local_user YES',
],
}
Turns out that augeas has an unwelcome behavior - it tries to load all
files that match the lens - if any are non-standard, it errors out.
Greg
On Monday, September 23, 2013 3:00:36 PM UTC-7, Nathan Valentine wrote:
Greg,
I believe resource ini_setting would be appropriate here but I do
understand the desire to learn about Puppet + Augeas.
augeas { 'vsftpd.conf':
context = '/etc/vsftpd/vsftpd.conf',
changes = [ 'set anonymous_enable=NO', 'set chroot_local_user=YES',
],
require = File['/etc/vsftpd/vsftpd.conf'],
}
context = '*/files*/vsftpd/vsftpd.conf',
?
I'm lazy and haven't tested with a Puppet apply but I think this might
just be an issue of understanding the namespace-y Augeas stuff. You can
test like so with augtool:
$ augtool ls */files*/vsftpd/vsftpd.conf
--
---
Nathan Valentine - nat...@puppetlabs.com javascript:
Puppet Labs Professional Services
GV: 415.504.2173
Skype: nrvale0
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: Puppet calls the ENC twice for some nodes.
Is this puppet3? As I recall, in puppet3, the master makes a separate call to the enc to determine the environment the should authoritatively be in. Once that's established, it makes a second call to get the classes and parameters. Hth, Greg On 20 Sep 2013 13:46, pierra mathieu partma...@gmail.com wrote: Thanks for the answers and sorry for my late one, I've only one agent process running : ps -aef | grep puppet root 4080 2811 0 14:14 pts/000:00:00 grep puppet root 18328 1 0 Sep12 ? 00:00:02 /usr/bin/ruby /usr/bin/puppet agent And the agent cycle isn't really fast, something like 5-10 sec. I was thinking about adding an acknowledgment the first time a class is requested by a node, so i'd like to choose which class to return for *each * request. Moreover, I'm curious and this comportment from puppet seems a little bit weird/useless. For information, here is my agent puppet.conf: [main] logdir = /var/log/puppet rundir = /var/run/puppet ssldir = $vardir/ssl pluginsync = true [agent] classfile = $vardir/classes.txt localconfig = $vardir/localconfig server= report = true usecacheonfailure = false Commenting *pluginsync* or *report* doesn't change anything. Any other ideas ? Thanks. Le lundi 9 septembre 2013 13:26:26 UTC+2, pierra mathieu a écrit : Hi everyone, I have an issue setting up Puppet with an ENC. For some nodes, puppet calls my ENC twice with a 2 sec interval. All my agents share the same configuration file. Considering this very basic ENC : #!/bin/bash nodeName=$1 echo `date` $nodeName /tmp/encCalls echo --- classes: testClass: Here is the content of /tmp/encCalls after a few run on two nodes. Mon Sep 9 11:36:15 CEST 2013 : host1 Mon Sep 9 11:36:17 CEST 2013 : host1 Mon Sep 9 11:41:04 CEST 2013 : host2 Mon Sep 9 11:42:04 CEST 2013 : host1 Mon Sep 9 11:42:06 CEST 2013 : host1 Mon Sep 9 11:45:13 CEST 2013 : host2 Anybody knows why two calls are made ? Thanks. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: Puppet calls the ENC twice for some nodes.
On 20 Sep 2013 18:05, Greg Sutcliffe greg.sutcli...@gmail.com wrote: the should authoritatively be in. Gah, phone keyboard. The *client* should authoritatively... Sorry Greg -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] arnoudj/sudo and different versions of CentOS
Hello, Does anyone have an example of using the arnoudj/sudo module in a mixed environment with both CentOS 5 and 6? So far, my CentOS 6 servers are happy but my CentOS 5 servers are ignoring everything in /etc/sudoers.d/ Thank in advance! Greg -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] arnoudj/sudo and different versions of CentOS
Steven, That seemed to do the trick - thanks!!! Greg On Thursday, September 12, 2013 4:30:33 PM UTC-7, Steven wrote: I don't know about the module you are using but things to verify: /etc/sudoers contains an include for /etc/sudoers.d Check that the version of sudo is new enough to support this. You may need to upgrade it. I had to on a number of my Redhat 5 servers Steven -- Date: Thu, 12 Sep 2013 15:01:30 -0700 From: greg...@gmail.com javascript: To: puppet...@googlegroups.com javascript: Subject: [Puppet Users] arnoudj/sudo and different versions of CentOS Hello, Does anyone have an example of using the arnoudj/sudo module in a mixed environment with both CentOS 5 and 6? So far, my CentOS 6 servers are happy but my CentOS 5 servers are ignoring everything in /etc/sudoers.d/ Thank in advance! Greg -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com javascript:. To post to this group, send email to puppet...@googlegroups.comjavascript: . Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Where does the puppet master get its hostname
Hi all, I have a new puppet server named grover.example.com. I've set both the server and certname to grover.example.com in /etc/puppet/puppet.conf (this is CentOS 6.4). I've also verified the hostname: hostname: grover.example.com However, when I start puppetmaster, it always created a cert named grover and *not* grover.example.com: puppet master --no-daemonize --verbose: Info: Creating a new SSL key for grover Info: Creating a new SSL certificate request for grover Info: Certificate Request fingerprint (SHA256): 07:04:47:E0:F5:26:7A:B3:29:83:12:72:09:E0:45:9F:17:9F:E1:57:DC:05:71:10:FE:31:47:5E:4F:47:38:8A Notice: grover has a waiting certificate request Notice: Signed certificate request for grover Notice: Removing file Puppet::SSL::CertificateRequest grover at '/var/lib/puppet/ssl/ca/requests/grover.pem' Notice: Removing file Puppet::SSL::CertificateRequest grover at '/var/lib/puppet/ssl/certificate_requests/grover.pem' Notice: Starting Puppet master version 3.2.4 Using puppet master --no-daemonize --verbose --server grover.example.com makes no difference. Any ideas how to fix this? Thank you!!! Greg -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Where does the puppet master get its hostname
Man, I could have swear i tested this... /etc/sysconfig/network was correct. /ets/hosts had: ip grover grover.example.com I switched that to: ip grover.example.com grover and the cert is now named grover.example.com. :) Thank you!!! Greg On Tuesday, September 10, 2013 12:16:12 PM UTC-7, Nathan Valentine wrote: Check both of the following: /etc/hosts and /etc/sysconfig/network. -- --- Nathan Valentine - nat...@puppetlabs.com javascript: Puppet Labs Professional Services GV: 415.504.2173 Skype: nrvale0 -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Where does the puppet master get its hostname
Nathan, It was spun up by hand from a CentOS 6.4 disk. I added the grover lines to the /etc/hosts file myself after setting the hostname. Greg -- Greg Coit gregc...@gmail.com 707-845-0317 On Tue, Sep 10, 2013 at 12:34 PM, Nathan Valentine nat...@puppetlabs.com wrote: Out of curiosity, your Puppet master was spun up how? As a Vagrant VM? On Tue, Sep 10, 2013 at 3:23 PM, Greg Coit gregc...@gmail.com wrote: Man, I could have swear i tested this... /etc/sysconfig/network was correct. /ets/hosts had: ip grover grover.example.com I switched that to: ip grover.example.com grover and the cert is now named grover.example.com. :) Thank you!!! Greg On Tuesday, September 10, 2013 12:16:12 PM UTC-7, Nathan Valentine wrote: Check both of the following: /etc/hosts and /etc/sysconfig/network. -- --- Nathan Valentine - nat...@puppetlabs.com Puppet Labs Professional Services GV: 415.504.2173 Skype: nrvale0 -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out. -- --- Nathan Valentine - nat...@puppetlabs.com Puppet Labs Professional Services GV: 415.504.2173 Skype: nrvale0 -- You received this message because you are subscribed to a topic in the Google Groups Puppet Users group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/puppet-users/MKzWpt1m7mQ/unsubscribe. To unsubscribe from this group and all its topics, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] basic case statement question
Hi all,
I'm using the puppetlabs/ntp module and would like to define the ntp
servers based on the fact timezone:
#ntp
class { '::ntp':
case $timezone {
PDT: { servers = [ '0.us.pool.ntp.org', '1.us.pool.ntp.org',
'2.us.pool.ntp.org', '3.us.pool.ntp.org'], }
default: { fail(Unrecognized timezone $timezone) }
}
}
The above gives me Error: Could not retrieve catalog from remote server:
Error 400 on SERVER: Syntax error at 'timezone'; expected '}' at
/etc/puppet/modules/linux/manifests/init.pp:56 on node but It's unclear to
me what I've done wrong. Any suggestions?
Thank you in advance!
Greg
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] basic case statement question
Frederiko,
That worked perfectly! I was trying to be too fancy I guess. Thank you
for the help
Greg
On Thursday, September 5, 2013 11:27:02 AM UTC-7, Frederiko Costa wrote:
Ohh.. my bad. You're actually instantiating the parametized class ntp. I
accidentally thought you were writing your module.
In that case, you might want to try using selectors. But I don't remember
from the top of my head if the fail() function would work. Let's stick with
the 'case' anyway ...
Try this, assuming you have a node declaration ...
node 'a.b.c.d' {
case $timezone {
'PDT': {
$my_ntp_servers = [ '0.us.pool.ntp.org', '1.us.pool.ntp.org',
'2.us.pool.ntp.org', '3.us.pool.ntp.org'] }
default: {
fail(Unrecognized timezone $timezone)
}
class { 'ntp':
server = $my_ntp_servers,
}
}
If I were you, I would put the timezone logic outside.
Hope this time I'm correct. :-)
-frederiko
On Thu, Sep 5, 2013 at 11:15 AM, Greg Coit greg...@gmail.comjavascript:
wrote:
Thank you for the reply Frederiko. Unfortunately, that doesn't seem to
be the issue. The following is from the pupetlabs/ntep docs and works:
class { '::ntp':
servers = [ '0.us.pool.ntp.org', '1.us.pool.ntp.org', '
2.us.pool.ntp.org', '3.us.pool.ntp.org'],
}
Greg
On Thursday, September 5, 2013 10:41:25 AM UTC-7, Frederiko Costa wrote:
Hi,
To me, this would look like this. You're assigning the 'server' variable
using =, rather than =:
class { '::ntp':
case $timezone {
'PDT': {
servers = [ '0.us.pool.ntp.org', '1.us.pool.ntp.org', '
2.us.pool.ntp.org', '3.us.pool.ntp.org'] }
default: {
fail(Unrecognized timezone $timezone)
}
# rest of the class.
}
I hope this helps.
-frederiko
On Thu, Sep 5, 2013 at 9:25 AM, Greg Coit greg...@gmail.com wrote:
Hi all,
I'm using the puppetlabs/ntp module and would like to define the ntp
servers based on the fact timezone:
#ntp
class { '::ntp':
case $timezone {
PDT: { servers = [ '0.us.pool.ntp.org', '1.us.pool.ntp.org', '
2.us.pool.ntp.org', '3.us.pool.ntp.org'], }
default: { fail(Unrecognized timezone $timezone) }
}
}
The above gives me Error: Could not retrieve catalog from remote
server: Error 400 on SERVER: Syntax error at 'timezone'; expected '}' at
/etc/puppet/modules/linux/**manifests/init.pp:56 on node but It's
unclear to me what I've done wrong. Any suggestions?
Thank you in advance!
Greg
--
You received this message because you are subscribed to the Google
Groups Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send
an email to puppet-users...@**googlegroups.com.
To post to this group, send email to puppet...@googlegroups.com.
Visit this group at
http://groups.google.com/**group/puppet-usershttp://groups.google.com/group/puppet-users
.
For more options, visit
https://groups.google.com/**groups/opt_outhttps://groups.google.com/groups/opt_out
.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an
email to puppet-users...@googlegroups.com javascript:.
To post to this group, send email to puppet...@googlegroups.comjavascript:
.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] basic case statement question
Thank you for the reply Frederiko. Unfortunately, that doesn't seem to be
the issue. The following is from the pupetlabs/ntep docs and works:
class { '::ntp':
servers = [ '0.us.pool.ntp.org', '1.us.pool.ntp.org',
'2.us.pool.ntp.org', '3.us.pool.ntp.org'],
}
Greg
On Thursday, September 5, 2013 10:41:25 AM UTC-7, Frederiko Costa wrote:
Hi,
To me, this would look like this. You're assigning the 'server' variable
using =, rather than =:
class { '::ntp':
case $timezone {
'PDT': {
servers = [ '0.us.pool.ntp.org', '1.us.pool.ntp.org', '
2.us.pool.ntp.org', '3.us.pool.ntp.org'] }
default: {
fail(Unrecognized timezone $timezone)
}
# rest of the class.
}
I hope this helps.
-frederiko
On Thu, Sep 5, 2013 at 9:25 AM, Greg Coit greg...@gmail.com javascript:
wrote:
Hi all,
I'm using the puppetlabs/ntp module and would like to define the ntp
servers based on the fact timezone:
#ntp
class { '::ntp':
case $timezone {
PDT: { servers = [ '0.us.pool.ntp.org', '1.us.pool.ntp.org', '
2.us.pool.ntp.org', '3.us.pool.ntp.org'], }
default: { fail(Unrecognized timezone $timezone) }
}
}
The above gives me Error: Could not retrieve catalog from remote server:
Error 400 on SERVER: Syntax error at 'timezone'; expected '}' at
/etc/puppet/modules/linux/manifests/init.pp:56 on node but It's unclear to
me what I've done wrong. Any suggestions?
Thank you in advance!
Greg
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an
email to puppet-users...@googlegroups.com javascript:.
To post to this group, send email to puppet...@googlegroups.comjavascript:
.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Help with customer fact
Benjamin, That was it - thank you Greg On Wednesday, September 4, 2013 2:04:17 PM UTC-7, Ben Carrell wrote: The ulimit command is a shell builtin, try using /bin/bash -c ulimit -n -- Benjamin Carrell On Wed, Sep 4, 2013 at 2:54 PM, Greg Coit greg...@gmail.com javascript: wrote: Hello, I've setup a puppet master server and a couple of clients for testing purposes. Everything's going pretty well but I'm having trouble with creating a custom fact. I'm using the open source version of puppet on Centos 6.4. In the file /etc/puppet/modules/linux/lib/facter/ulimit.rb, I have the following: Facter.add(ulimit) do confine :kernel = Linux setcode do Facter::Util::Resolution.exec(ulimit -n) end end The module linux is a custom one that I use as a profile. Nowhere in the module is the new fact mentioned (which might be the issue???) On the clients, I run `facter --debug --puppet ulimit` and get: Relative directory ./facter removed from search path. value for ulimit is still nil Any idea what's causing the issue? Thanks! Greg -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com javascript:. To post to this group, send email to puppet...@googlegroups.comjavascript: . Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] undefined method each for #String:
I run puppet 3.2.2 on about 500 RedHat 5/6 systems. I have about 15 Ubuntu servers that run OpenStack; today I added the stdlib module to take advantage of the file_line type in a new module I had written AND I upgraded the puppet clients from 2.7 to match the other RedHat clients. This automatically upgraded ruby from 1.8 to 1.9. The first run of puppet agent successfully applied my new module, but each subsequent run results in this error: root@ceph-cs-sn-06i:/var/lib/puppet/lib/facter# puppet agent -t Info: Retrieving plugin Error: Could not retrieve local facts: undefined method `each' for #String:0x000259f630 Error: Failed to apply catalog: Could not retrieve local facts: undefined method `each' for #String:0x000259f630 The problem here is that I use each a lot. How can I troubleshoot this further, and is it possible that something has changed in ruby 1.9 that is causing this? Thanks. -- \*..+.- --Greg Chavez +//..;}; -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: undefined method each for #String:
Removing ruby1.9.1 fixed the problem. On Thu, Jul 11, 2013 at 5:22 PM, Greg Chavez greg.cha...@gmail.com wrote: I run puppet 3.2.2 on about 500 RedHat 5/6 systems. I have about 15 Ubuntu servers that run OpenStack; today I added the stdlib module to take advantage of the file_line type in a new module I had written AND I upgraded the puppet clients from 2.7 to match the other RedHat clients. This automatically upgraded ruby from 1.8 to 1.9. The first run of puppet agent successfully applied my new module, but each subsequent run results in this error: root@ceph-cs-sn-06i:/var/lib/puppet/lib/facter# puppet agent -t Info: Retrieving plugin Error: Could not retrieve local facts: undefined method `each' for #String:0x000259f630 Error: Failed to apply catalog: Could not retrieve local facts: undefined method `each' for #String:0x000259f630 The problem here is that I use each a lot. How can I troubleshoot this further, and is it possible that something has changed in ruby 1.9 that is causing this? Thanks. -- \*..+.- --Greg Chavez +//..;}; -- \*..+.- --Greg Chavez +//..;}; -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: Node not showing in the PE console
So for a Fedora node would I use the EL (RHEL, CentOS, Scientific Linux, Oracle Linux) 6 PE installer? There isn't an installer listed for Fedora. Or, would I use the *nix installer? On Monday, July 8, 2013 12:56:31 PM UTC-5, Ellison Marks wrote: You should be using the enterprise installer on both the server and the nodes. On the nodes, you would only install the agent role. Just as a note, the problem you are running into is probably that the version of puppet from the Fedora repo is probably the latest, somewhere in the 3.2 area, while the version in PE 2.8.2 is older, probably 2.7.21. Pointing a newer client at an older server is generally a bad idea and will do weird things, like what you're seeing. On Friday, July 5, 2013 11:38:54 AM UTC-7, Greg Emanuel wrote: I have a Ubuntu 12.04 server running PE 2.8.2. I have a Fedora 18 node that I would like to manage. I installed the F18 node using a kickstart installation. During this install I enabled the puppetlabs repo and installed puppet from the puppetlabs repo. One of the post installation tasks executed the following command: puppet agent -t --server server name. Everything seemed to install ok. I did get a certificate request that I could see and Accept on the PE console. After accepting the cert, the node never shows up in the PE console. I have verified DNS and networking info multiple times and everything is in order. I am wondering if the puppet agent from the puppetlabs repo works with Puppet Enterprise. Or am I all wrong and should be using the Puppet Enterprise installer on the nodes? I would assume then the Red Hat installer would be used on a Fedora node? -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Node not showing in the PE console
I have a Ubuntu 12.04 server running PE 2.8.2. I have a Fedora 18 node that I would like to manage. I installed the F18 node using a kickstart installation. During this install I enabled the puppetlabs repo and installed puppet from the puppetlabs repo. One of the post installation tasks executed the following command: puppet agent -t --server server name. Everything seemed to install ok. I did get a certificate request that I could see and Accept on the PE console. After accepting the cert, the node never shows up in the PE console. I have verified DNS and networking info multiple times and everything is in order. I am wondering if the puppet agent from the puppetlabs repo works with Puppet Enterprise. Or am I all wrong and should be using the Puppet Enterprise installer on the nodes? I would assume then the Red Hat installer would be used on a Fedora node? -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] ruby issue
I don't have access to the Optional repo, full stop, so I can't mirror it. However, I do have access to its constituent packages, so what you can do is search for rubgems at RHN under Downloads - Packages and download the rpm. I then dropped it into a one-file mrepo, added the mrepo info to my puppetlabs yum.repo file that I instantiate with Cobbler and then control with puppet, and viola, my kicks and spins come up with a working puppet client. Easy enough to do this every time I upgrade puppet. I think Puppet is making a mistake here too, but there are worse things. My problem will be solved in total when my company transitions to CentOS later this year. Cheers. --Greg Chavez On Fri, Jun 14, 2013 at 10:44 PM, Stuart Cracraft smcracr...@me.com wrote: Boo!!! Hiss!! Be a One-Stop-Shop! It's YOUR collective after all --Stuart On Jun 14, 2013, at 7:13 PM, Michael Stahnke stah...@puppetlabs.com wrote: On Wed, Jun 12, 2013 at 5:52 AM, Greg Chavez greg.cha...@gmail.com wrote: Which is just fine if your company has the Optional subscription. Mine doesn't. So I'm screwed unless I write a script to manually pull updates from Fedora or CentOS into a custom mrepo repository. Bit of a pain, that is. The optional repo is free from what I can tell. It's included with a RHEL subscription. Puppet Labs doesn't try to replace packages in provided by the upstream OS vendor. Therefore, we don't supply packages that replace things in the RHEL repo since they work just fine with Puppet et al. On Tue, Jun 11, 2013 at 6:43 PM, Matthaus Owens matth...@puppetlabs.com wrote: We supply rubygems for rhel 5 because it is not available in centos or rhel 5 core (it is in EPEL). In rhel6 and cent6, it is widely and easily available (in cent6 base, and in rhel6 optional repos), so we don't supply it for el6. On Tue, Jun 11, 2013 at 2:37 PM, Greg Chavez greg.cha...@gmail.com wrote: The rubygems package is available from here: https://yum.puppetlabs.com/el/5/dependencies/x86_64/ So why wouldn't it be available from 6? I'm pretty sure it used to be there since I've kicked several rhel 6 systems that had no problem installing puppet from puppetlabs. Was it mistakenly dropped from the puppetlabs rhel 6 repo? Thanks --Greg Chavez On Mon, Jun 10, 2013 at 11:12 AM, Stuart Cracraft smcracr...@me.com wrote: You are most welcome. On Jun 10, 2013, at 7:40 AM, Lab Yizhar lab.yiz...@gmail.com wrote: Thanks m8 for the mental support :) As you already know, as an open source believer ,I'm kind of into it and the solution is there, But I want to do it without RHN subscription that will used on our production env. Couple of humps and I'll be there this way or the offical other... On Mon, Jun 10, 2013 at 4:31 PM, Stuart Cracraft smcracr...@me.com wrote: It's not that hard! You can do it!!! Also, you could buy some books on the subject! On Jun 10, 2013, at 5:51 AM, Yizhar A. lab.yiz...@gmail.com wrote: Hi, Finish my things on this issue for now as the last one in this chain talented enough to be asking for pay for answering this I'll update when I'll figure it out else. Stay tuned, Yizhar Don't ask what the community can contribute to you ? ask what I can contribute the community On Sunday, June 9, 2013 3:06:48 PM UTC+3, Yizhar A. wrote: Dear Stuart, Kind of my first steps into puppet on RHEL 6 and I wonder how you manage to solve the rubygems issue. Since I'm using RHEL 6.4 (.x86_64) in my test env. with only puppetlabs repo I can't see from where I can get the rubygems missing package. As you after wiki'd it :) can you give me a piece of advise in here or attached your docs to help me through ? Thanks, --Yizhar On Saturday, June 1, 2013 8:49:16 AM UTC+3, Stuart Cracraft wrote: Hey, good news. All is well. Ruby related are good. Puppet too. And Red Hat. Also, I've documented/wiki'd the Puppet Master + Client install with respect to bare metal to delivered system for all related aspects and transmitted, fully, disclosed entirely, to staff. Next week, I will be tuning the configuration file on master and agents and writing many more puppet patterns plus training staff. As it is their only hope! --Stuart P.S. The firm's personnel have had heart attacks, strokes and other major maladies amongst staff in the past year due to the LACK OF AUTOMATION!!! Puppet is the Cure Kick Chef and CF Engine's non-collective butts! -- You received this message because you are subscribed to a topic in the Google Groups Puppet Users group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/puppet-users/ghDZsdkC3C0/unsubscribe?hl=en. To unsubscribe from this group and all its topics, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl
Re: [Puppet Users] ruby issue
Which is just fine if your company has the Optional subscription. Mine doesn't. So I'm screwed unless I write a script to manually pull updates from Fedora or CentOS into a custom mrepo repository. Bit of a pain, that is. On Tue, Jun 11, 2013 at 6:43 PM, Matthaus Owens matth...@puppetlabs.com wrote: We supply rubygems for rhel 5 because it is not available in centos or rhel 5 core (it is in EPEL). In rhel6 and cent6, it is widely and easily available (in cent6 base, and in rhel6 optional repos), so we don't supply it for el6. On Tue, Jun 11, 2013 at 2:37 PM, Greg Chavez greg.cha...@gmail.com wrote: The rubygems package is available from here: https://yum.puppetlabs.com/el/5/dependencies/x86_64/ So why wouldn't it be available from 6? I'm pretty sure it used to be there since I've kicked several rhel 6 systems that had no problem installing puppet from puppetlabs. Was it mistakenly dropped from the puppetlabs rhel 6 repo? Thanks --Greg Chavez On Mon, Jun 10, 2013 at 11:12 AM, Stuart Cracraft smcracr...@me.com wrote: You are most welcome. On Jun 10, 2013, at 7:40 AM, Lab Yizhar lab.yiz...@gmail.com wrote: Thanks m8 for the mental support :) As you already know, as an open source believer ,I'm kind of into it and the solution is there, But I want to do it without RHN subscription that will used on our production env. Couple of humps and I'll be there this way or the offical other... On Mon, Jun 10, 2013 at 4:31 PM, Stuart Cracraft smcracr...@me.com wrote: It's not that hard! You can do it!!! Also, you could buy some books on the subject! On Jun 10, 2013, at 5:51 AM, Yizhar A. lab.yiz...@gmail.com wrote: Hi, Finish my things on this issue for now as the last one in this chain talented enough to be asking for pay for answering this I'll update when I'll figure it out else. Stay tuned, Yizhar Don't ask what the community can contribute to you ? ask what I can contribute the community On Sunday, June 9, 2013 3:06:48 PM UTC+3, Yizhar A. wrote: Dear Stuart, Kind of my first steps into puppet on RHEL 6 and I wonder how you manage to solve the rubygems issue. Since I'm using RHEL 6.4 (.x86_64) in my test env. with only puppetlabs repo I can't see from where I can get the rubygems missing package. As you after wiki'd it :) can you give me a piece of advise in here or attached your docs to help me through ? Thanks, --Yizhar On Saturday, June 1, 2013 8:49:16 AM UTC+3, Stuart Cracraft wrote: Hey, good news. All is well. Ruby related are good. Puppet too. And Red Hat. Also, I've documented/wiki'd the Puppet Master + Client install with respect to bare metal to delivered system for all related aspects and transmitted, fully, disclosed entirely, to staff. Next week, I will be tuning the configuration file on master and agents and writing many more puppet patterns plus training staff. As it is their only hope! --Stuart P.S. The firm's personnel have had heart attacks, strokes and other major maladies amongst staff in the past year due to the LACK OF AUTOMATION!!! Puppet is the Cure Kick Chef and CF Engine's non-collective butts! -- You received this message because you are subscribed to a topic in the Google Groups Puppet Users group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/puppet-users/ghDZsdkC3C0/unsubscribe?hl=en. To unsubscribe from this group and all its topics, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to a topic in the Google Groups Puppet Users group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/puppet-users/ghDZsdkC3C0/unsubscribe?hl=en. To unsubscribe from this group and all its topics, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group
Re: [Puppet Users] ruby issue
The rubygems package is available from here: https://yum.puppetlabs.com/el/5/dependencies/x86_64/ So why wouldn't it be available from 6? I'm pretty sure it used to be there since I've kicked several rhel 6 systems that had no problem installing puppet from puppetlabs. Was it mistakenly dropped from the puppetlabs rhel 6 repo? Thanks --Greg Chavez On Mon, Jun 10, 2013 at 11:12 AM, Stuart Cracraft smcracr...@me.com wrote: You are most welcome. On Jun 10, 2013, at 7:40 AM, Lab Yizhar lab.yiz...@gmail.com wrote: Thanks m8 for the mental support :) As you already know, as an open source believer ,I'm kind of into it and the solution is there, But I want to do it without RHN subscription that will used on our production env. Couple of humps and I'll be there this way or the offical other... On Mon, Jun 10, 2013 at 4:31 PM, Stuart Cracraft smcracr...@me.com wrote: It's not that hard! You can do it!!! Also, you could buy some books on the subject! On Jun 10, 2013, at 5:51 AM, Yizhar A. lab.yiz...@gmail.com wrote: Hi, Finish my things on this issue for now as the last one in this chain talented enough to be asking for pay for answering this I'll update when I'll figure it out else. Stay tuned, Yizhar Don't ask what the community can contribute to you ? ask what I can contribute the community On Sunday, June 9, 2013 3:06:48 PM UTC+3, Yizhar A. wrote: Dear Stuart, Kind of my first steps into puppet on RHEL 6 and I wonder how you manage to solve the rubygems issue. Since I'm using RHEL 6.4 (.x86_64) in my test env. with only puppetlabs repo I can't see from where I can get the rubygems missing package. As you after wiki'd it :) can you give me a piece of advise in here or attached your docs to help me through ? Thanks, --Yizhar On Saturday, June 1, 2013 8:49:16 AM UTC+3, Stuart Cracraft wrote: Hey, good news. All is well. Ruby related are good. Puppet too. And Red Hat. Also, I've documented/wiki'd the Puppet Master + Client install with respect to bare metal to delivered system for all related aspects and transmitted, fully, disclosed entirely, to staff. Next week, I will be tuning the configuration file on master and agents and writing many more puppet patterns plus training staff. As it is their only hope! --Stuart P.S. The firm's personnel have had heart attacks, strokes and other major maladies amongst staff in the past year due to the LACK OF AUTOMATION!!! Puppet is the Cure Kick Chef and CF Engine's non-collective butts! -- You received this message because you are subscribed to a topic in the Google Groups Puppet Users group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/puppet-users/ghDZsdkC3C0/unsubscribe?hl=en. To unsubscribe from this group and all its topics, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to a topic in the Google Groups Puppet Users group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/puppet-users/ghDZsdkC3C0/unsubscribe?hl=en. To unsubscribe from this group and all its topics, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: apt repository appears to have dependency issue with latest release (3.2.1)
On 23 May 2013 22:25, Eric Sorenson eric.soren...@puppetlabs.com wrote: Quick question for those of you affected by this -- what did you to do to add the puppetlabs apt repo? Did you do it through the method described here: http://docs.puppetlabs.com/guides/puppetlabs_package_repositories.html#for-debian-and-ubuntu .. or some other way? I'm trying to suss out whether the docs / packages are messing people up. I've hit this, but it's because I have the main Puppetlabs repo in my preseed file for new virtual machines, so it's available within the installer environment. That's just text, so I only have a line for deb http://apt.puppetlabs.com distro main I think the install a deb which sets up the repos is good for most people, but there should always be the docs for the manual apt setup for those going a different route. As of right now, I don't see a dependencies repo mentioned anywhere on the page you linked, Eric I'll also add a voice the question on the logic behind a separate dependencies repo, although only because you're adding work to your documentation requirements ;) Cheers, Greg -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] apt repository appears to have dependency issue with latest release (3.2.1)
On 24 May 2013 21:55, Eric Sorenson eric.soren...@puppetlabs.com wrote: Hi Greg, thanks for the info -- I slightly disagree that the docs should describe manual installation; IMO they should describe supported/official ways to do things, because anything that's documented gets interpreted as being supported and official :) Amen to that ;) That said, we could punch up the importance of including the deps repository. It's been necessary for EL users for a long time, but this was the first Puppet release that pulled in a hard dependency for Debian-based systems. I'll snip here as I broadly agree with you anyway ;) I think it would be fine to have an Advanced or Manual APT section that's away from the recommended route. I don't object to a recommended route _at all_ but I do feel the information should be there for those that want to find it. As of today (I think) one cannot find mention of the additional repo in the docs. Greg freenode: gwmngilfen -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Puppet Dashboard's ENC returning wrong hostname/parameters
Ok, opened a ticket with more info. Same bug happened on my learning VM. http://projects.puppetlabs.com/issues/20643 On Wednesday, May 8, 2013 10:57:09 AM UTC-7, Aaron Stone wrote: Interesting! Let me see if this still happens in the rails3 branch. Please file a ticket so the issue doesn't get lost. http://projects.puppetlabs.com/projects/dashboard On Tue, May 7, 2013 at 11:17 PM, Greg Batye gba...@gmail.comjavascript: wrote: Hey everyone, I have an issue with puppet dashboard that I can find a solution to. My server naming convention contains leading numbers at the beginning of the hostname. For example, 009example.com. Whenever I run “/usr/share/puppet-dashboard/external_node 009example.com” another host's parameters/classes are returned. I tracked the issue down to the enc returning the hostname with id 9 in the database. This happens no matter which number I use. Has anyone had this issue and is there a way to have puppet dashboard search the database for name rather then id? --Greg -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com javascript:. To post to this group, send email to puppet...@googlegroups.comjavascript: . Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Puppet Dashboard's ENC returning wrong hostname/parameters
Hey everyone, I have an issue with puppet dashboard that I can find a solution to. My server naming convention contains leading numbers at the beginning of the hostname. For example, 009example.com. Whenever I run “/usr/share/puppet-dashboard/external_node 009example.com” another host's parameters/classes are returned. I tracked the issue down to the enc returning the hostname with id 9 in the database. This happens no matter which number I use. Has anyone had this issue and is there a way to have puppet dashboard search the database for name rather then id? --Greg -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] stdlib::member support for strings and hashes todo
I am curious as to how support for strings would work. To me, it seems
there are two possibile use-cases for support for strings. Take the
following example:
Assume:
- extdata exists, identified by 'array'
- extlookup('array') may return an array or a single string (in the case
that the array only has one member)
Case 1:
$array = extlookup(array) - extlookup returns a string
member($array, 'some_string') - returns true if $array is the string
'some_string'
Case 2:
$array = extlookup(array) - extlookup returns an array
member returns true if array.includes?('some_string')
The alternative, I suppose, would be substring matching, but in that case
wouldn't member be a misnomer and shouldn't the more common substr() be
added?
For hash membership, we would want to look for key membership, yes?
Anyway, came across an instance of when this kind of behavior would be
useful, and was wondering if this behavior was the intent behind this
particular TODO. If so, I will submit a patch.
Thanks,
Greg
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Seriously, am I the only one having trouble with the RHEL puppetlabs repos?
This is the third time I've sent a message about this. Does anybody know what's going on? I'm going to file a bug if this isn't fixed soon. RHEL6: http://yum.puppetlabs.com/el/6/products/x86_64/repodata/primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum Trying other mirror. Error: failure: repodata/primary.sqlite.bz2 from puppetlabs-products: [Errno 256] No more mirrors to try. RHEL5: http://yum.puppetlabs.com/el/5/products/x86_64/repodata/primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum Trying other mirror. Error: failure: repodata/primary.sqlite.bz2 from puppetlabs-products: [Errno 256] No more mirrors to try. I can get around it by setting http_caching=none in yum.conf but that *really* sucks. If I'm being stupid and there's an obvious solution to my problem, I beg of you to tell me what it us and humiliate me in front of the entire Puppet users community. I'd be so happy. -- \*..+.- --Greg Chavez +//..;}; -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Seriously, am I the only one having trouble with the RHEL puppetlabs repos?
I've run yum clean all a hundred times, but that's besides the point since I only notice the problem on new systems. The build system (Cobbler) installs the latest puppet-release rpm for each node, then instantiates Puppet. It's worked like butter for over a year. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Seriously, am I the only one having trouble with the RHEL puppetlabs repos?
Gah... I bet that's it. We recently switched from our own sensible Internet egress to a tortured journey from DC to our Philly mothership. We go through Websense, I think, and I know that blicky has had problems in the past with over-caching. Thanks. Glad yours works, Dan. Cheers. On Tue, Jan 29, 2013 at 1:44 PM, Matthaus Owens matth...@puppetlabs.comwrote: Are you behind any sort of proxy that might be caching metadata? On Tue, Jan 29, 2013 at 10:30 AM, Scott Anderson s...@torand.org wrote: I had to not use the puppet repos to get it to work.. but this is on centos 5 and 6. On Tue, Jan 29, 2013 at 12:13 PM, Greg Chavez greg.cha...@gmail.com wrote: This is the third time I've sent a message about this. Does anybody know what's going on? I'm going to file a bug if this isn't fixed soon. RHEL6: http://yum.puppetlabs.com/el/6/products/x86_64/repodata/primary.sqlite.bz2 : [Errno -1] Metadata file does not match checksum Trying other mirror. Error: failure: repodata/primary.sqlite.bz2 from puppetlabs-products: [Errno 256] No more mirrors to try. RHEL5: http://yum.puppetlabs.com/el/5/products/x86_64/repodata/primary.sqlite.bz2 : [Errno -1] Metadata file does not match checksum Trying other mirror. Error: failure: repodata/primary.sqlite.bz2 from puppetlabs-products: [Errno 256] No more mirrors to try. I can get around it by setting http_caching=none in yum.conf but that *really* sucks. If I'm being stupid and there's an obvious solution to my problem, I beg of you to tell me what it us and humiliate me in front of the entire Puppet users community. I'd be so happy. -- \*..+.- --Greg Chavez +//..;}; -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out. -- The most essential quality for leadership is not perfection, but credibility. People must be able to trust you, or they won't follow you. From The Purpose Driven Life by Rick Warren Scott Anderson - web: http://www.torand.org - e-mail: s...@torand.org GoogleTalk: s...@torand.org - AIM:andersons776- Twitter:sdanderson Phone: 703-594-1284 -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out. -- Matthaus Owens Release Manager, Puppet Labs -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out. -- \*..+.- --Greg Chavez +//..;}; -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] REDUX: puppetlabs-products yum checksum failing
Again with the yum metadata checksum failures: http://yum.puppetlabs.com/el/6/products/x86_64/repodata/primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum I'm thinking it's time for me to add the Puppetlabs repos to my mrepo box. -- \*..+.- --Greg Chavez +//..;}; -- 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] puppetlabs-products yum checksum failing
Fixed it. Thanks. On Thu, Jan 17, 2013 at 6:10 PM, Matthaus Owens matth...@puppetlabs.comwrote: Greg, I've updated the metadata on our end. Please let me know if your problem still persists, and we can dig a little deeper into what might be going on. On Thu, Jan 17, 2013 at 2:03 PM, Greg Chavez greg.cha...@gmail.com wrote: I'm reasonably confident that the problem I'm having here is upstream. RHEL5: # yum repolist | grep puppet puppetlabs-depsPuppet Labs Dependencies El 5 - x86_64 45 puppetlabs-productsPuppet Labs Products El 5 - x86_64 161 # yum clean all Loaded plugins: security Cleaning up Everything # yum repolist 21 | grep puppet http://yum.puppetlabs.com/el/5/products/x86_64/repodata/primary.sqlite.bz2 : [Errno -1] Metadata file does not match checksum http://yum.puppetlabs.com/el/5/products/x86_64/repodata/primary.sqlite.bz2 : [Errno -1] Metadata file does not match checksum puppetlabs-depsPuppet Labs Dependencies El 5 - x86_64 45 puppetlabs-productsPuppet Labs Products El 5 - x86_64 0 Same on RHEL6. Insidious problem. Only noticed it because I was kicking some systems today. Should I report this as a bug? -- \*..+.- --Greg Chavez +//..;}; -- 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. -- Matthaus Owens Release Manager, Puppet Labs -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- \*..+.- --Greg Chavez +//..;}; -- 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] puppetlabs-products yum checksum failing
I'm reasonably confident that the problem I'm having here is upstream. RHEL5: # yum repolist | grep puppet puppetlabs-depsPuppet Labs Dependencies El 5 - x86_64 45 puppetlabs-productsPuppet Labs Products El 5 - x86_64 161 # yum clean all Loaded plugins: security Cleaning up Everything # yum repolist 21 | grep puppet http://yum.puppetlabs.com/el/5/products/x86_64/repodata/primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum http://yum.puppetlabs.com/el/5/products/x86_64/repodata/primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum puppetlabs-depsPuppet Labs Dependencies El 5 - x86_64 45 puppetlabs-productsPuppet Labs Products El 5 - x86_64 0 Same on RHEL6. Insidious problem. Only noticed it because I was kicking some systems today. Should I report this as a bug? -- \*..+.- --Greg Chavez +//..;}; -- 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] Best practices on puppet installation
On 25 November 2012 21:36, Ugo Bellavance u...@lubik.ca wrote: Ok, but it looks like foreman is not fully puppet-3 compatible up to now. I think I'll wait for that. We have all the required changes for puppet-3 compatibility in the develop branches of foreman and foreman-proxy - hoping to get a release candidate out soon, so stay tuned :) Greg -- 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: Nginx + passenger + puppetmaster
On Monday, 22 October 2012 11:03:06 UTC+1, Geert Booster wrote: Hello, Op donderdag 7 juni 2012 08:44:54 UTC+2 schreef vulzscht het volgende: i will dig into it a bit more and provide my results here in case of success Did you found any solution? I am looking at the same problems, after a fresh puppetmaster install with passenger, getting: err: Could not retrieve catalog from remote server: Error 403 on SERVER: Forbidden request: FQDN(IP.Addr) access to /catalog/fqdn [find] at line 93 ./ssl/certs/ca.pem is available... Regards, Geert Hi Geert, I'm not sure if you are still having this problem but I was suffering from it myself. I finally found that the problem was due to the following two lines in my puppet.conf. ssl_client_header = SSL_CLIENT_S_DN ssl_client_verify_header = SSL_CLIENT_VERIFY Once removed puppet works fine under nginx. I had noticed that they were absent in this set of instructions that I was following http://z0mbix.github.com/blog/2012/03/01/use-nginx-and-passenger-to-power-your-puppet-master/ but assumed that they needed to be there was the comment says to uncomment when using passenger. Hope this helps. Regards, Greg -- 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/-/aKHa4HPZArkJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: Can Puppet alert about dead nodes?
On 1 November 2012 17:54, Lucas Vickers lucasvick...@gmail.com wrote: I am currently using the open source edition so I have no dashboard. Puppet Dashboard is opensource, so you could use it, but it's being deprecated (last I heard, anyway). You could also checkout The Foreman, which will display nodes out-of-sync (and email you about it, if you like). Greg -- 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] Starting master fails
Have found the same issue and it looks like you need to have a version of
OpenSSL that supports the encryption installed. Note: This only appears to
be in the 3.x stream - must be a change in there to strengthen the
certificates or something. 2.x seems OK as far as I can tell...
The one Oracle/Sun provides in /usr/sfw doesn't support SHA256 by the looks
of it (Its OpenSSL 0.9.7d with security patches)
Run ldd against the OpenSSL library in Ruby to confirm which library you
are using:
bash-3.2# ldd ./lib/ruby/1.8/i386-solaris2.10/openssl.so | grep ssl
libssl.so.0.9.7 = /usr/sfw/lib/64/libssl.so.0.9.7 --
/usr/sfw/lib is core Solaris GNU packages - really old...
libssl_extra.so.0.9.7 =
/usr/sfw/lib/amd64/libssl_extra.so.0.9.7
(NOTE: You will need find your openssl.so object - in my case its from a
self-compiled copy of ruby...)
bash-3.2# uname -a
SunOS test1 5.10 Generic_147441-25 i86pc i386 i86pc
bash-3.2# /usr/sfw/bin/openssl version
OpenSSL 0.9.7d 17 Mar 2004 (+ security fixes for: CVE-2005-2969
CVE-2006-2937 CVE-2006-2940 CVE-2006-3738 CVE-2006-4339 CVE-2006-4343
CVE-2006-7250 CVE-2007-5135 CVE-2007-3108 CVE-2008-5077 CVE-2008-7270
CVE-2009-0590 CVE-2009-2409 CVE-2009-3555 CVE-2010-4180 CVE-2011-4576
CVE-2011-4619 CVE-2012-0884 CVE-2012-1165 CVE-2012-2110 CVE-2012-2131
CVE-2012-2333)
Basically, looks like you need to get packages for (or compile) a more
recent version of OpenSSL then link ruby against it. A very brief glance at
http://www.openssl.org/news/changelog.html suggests that you need version
1.0.1 or later.
Checking Solaris 11:
bash# openssl version
OpenSSL 1.0.0j 10 May 2012
bash# uname -a
SunOS test2 5.11 11.0 i86pc i386 i86pc
This version also seems to support sha256, so looks like it may be
available in some current 1.0.0 streams as well...
Hope that helps...
Greg
On Saturday, 22 September 2012 07:39:50 UTC+10, Jakov Sosic wrote:
On 09/21/2012 01:35 PM, Peter Spatz wrote:
Hello,
first, i�m new to puppet. I�m searching for a configuration
management
tool and puppet was in focus.
I�m using Solaris Zone
SunOS: 5.10 Generic_147440-15 sun4v sparc sun4v
Ruby: ruby 1.8.5 (2006-12-04 patchlevel 2) [sparc-solaris2.10]
puppet: v3.0.0-rc6
/lib:/usr/lib:/opt/coolstack/mysql_32bit/bin/:/opt/coolstack/mysql_32bit/lib/:/usr/local/lib:/opt/sfw/lib/ruby/:/usr/local/ss/lib/
Starting puppet master, syslog prints:
Sep 21 13:24:55 sis102f0 puppet-master[9649]: [ID 702911 daemon.debug]
Finishing transaction 6891204
Sep 21 13:24:55 sis102f0 puppet-master[9649]: [ID 702911 daemon.info]
Creating a new SSL certificate request for ca
Sep 21 13:24:55 sis102f0 puppet-master[9649]: [ID 702911 daemon.error]
Could not prepare for execution: uninitialized constant
OpenSSL::Digest::SHA256
What�s missing?
First, what does the:
$ which ruby
says?
Then try this:
$ ruby -ropenssl -e 'p OpenSSL::Digest::Digest.new(sha256)'
and this:
$ ruby -e puts require('openssl')
And then report back with output.
Also, that being Solaris, check whether you have more than one ruby
installations on system and if you are using the right one...
--
Jakov Sosic
www.srce.unizg.hr
--
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/-/IwxB8_WPDtwJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Using Exported Resources in nginx loadbalancer conf
On 25 September 2012 12:03, Jon Ward jghw...@gmail.com wrote: Hi all, I'm attempting to use exported resources to dynamically generate an nginx config file. What I'd like to do if have all my web servers export their hostname inside a file resource, and have these collected by my loadbalancer and used in the config file, restarting nginx if anything has changed. Nginx can do include directives, right? Can you do something like: upstream include conf.d/upstream/*.conf /upstream and then have each host export a file in conf.d/upstream/$hostname.conf containing $hostname:$port (or whatever is needed). Not sure if that will work, my nginx is a little rusty... -- 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 Windows: scheduled_task : TypeError
the manifest is now attached to the ticket
On Friday, June 22, 2012 2:23:31 PM UTC-5, Josh Cooper wrote:
Thanks Greg. Can you attach the manifest you are using (with the
arguments) to the ticket?
On Fri, Jun 22, 2012 at 12:20 PM, Greg Swift wrote:
attached to the ticket. I won't be able to work on this for about a
week
though.. other priority just came up. But let me know and when I can
get
back on it I will.
On Thursday, June 21, 2012 3:02:38 PM UTC-5, Greg Swift wrote:
first thing in the morning.
On Thursday, June 21, 2012 1:15:09 PM UTC-5, Josh Cooper wrote:
Can you try running with --trace and --debug, and adding the stack
trace
to the ticket?
On Jun 21, 2012, at 10:57 AM, Greg Swift wrote:
So.. now I'm getting your error instead of mine.
On Thursday, June 21, 2012 12:46:08 PM UTC-5, Greg Swift wrote:
I believe you are correct. I removed the arguments key/value pair
and
it ran fine. I'm patching in your changes to try it with the
arguments
option.
thank you very much
On Thursday, June 21, 2012 11:53:40 AM UTC-5, Josh Cooper wrote:
Hi Greg,
I believe this is issue https://projects.puppetlabs.com/issues/13008,
which I have fixed in my topic branch and is awaiting to be merged
into
2.7.x. It would be great if you could try it out and let me know how
it
goes.
Josh
On Thu, Jun 21, 2012 at 9:00 AM, Greg Swift wrote:
Mohamed,
Did you get anywhere with this? I'm running into the exact same
issue.
-greg
On Wednesday, November 23, 2011 7:29:34 PM UTC-6, Jacob Helwig
wrote:
On 2011-11-23 15:53 , Mohamed Lrhazi wrote:
Thanks JacobDid that answer my TypeError as well?
No, a stack trace would help for that.
--
Jacob Helwig
http://about.me/jhelwig
Mohamed.
On Wed, Nov 23, 2011 at 5:28 PM, Jacob Helwig wrote:
On 2011-11-23 13:02 , Mohamed Lrhazi wrote:
am trying this:
scheduled_task { 'Puppet Run':
ensure= present,
enabled = true,
command = 'C:\\ruby187\\bin\\puppet.bat',
arguments = 'agent --verbose --logdest
C:\\Temp\puppet.log',
trigger = {
schedule = daily,
#every = 2 # Defaults to 1
#start_date = '2011-08-31', # Defaults to 'today'
start_time = '16:00', # Must be specified
}
}
And getting this error:
err: /Stage[main]/Gu_splunk/Scheduled_task[Puppet Run]/ensure:
change
from absent to present failed: Could not set 'present on
ensure:
TypeError at /etc/puppet/
environments/windows/modules/gu_splunk/manifests/init.pp:84
--
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/-/cIrGZR2XNjYJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
--
Josh Cooper
Developer, Puppet Labs
--
You received this message because you are subscribed to the Google
Groups
Puppet Users group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/CG9Sa5hf2jYJ.
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 view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/Gs01u9mrFhEJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
--
Josh Cooper
Developer, Puppet Labs
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/BJ-kUP8TRH8J.
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 Windows: scheduled_task : TypeError
attached to the ticket. I won't be able to work on this for about a week
though.. other priority just came up. But let me know and when I can get
back on it I will.
On Thursday, June 21, 2012 3:02:38 PM UTC-5, Greg Swift wrote:
first thing in the morning.
On Thursday, June 21, 2012 1:15:09 PM UTC-5, Josh Cooper wrote:
Can you try running with --trace and --debug, and adding the stack trace
to the ticket?
On Jun 21, 2012, at 10:57 AM, Greg Swift wrote:
So.. now I'm getting your error instead of mine.
On Thursday, June 21, 2012 12:46:08 PM UTC-5, Greg Swift wrote:
I believe you are correct. I removed the arguments key/value pair and
it ran fine. I'm patching in your changes to try it with the arguments
option.
thank you very much
On Thursday, June 21, 2012 11:53:40 AM UTC-5, Josh Cooper wrote:
Hi Greg,
I believe this is issue https://projects.puppetlabs.com/issues/13008,
which I have fixed in my topic branch and is awaiting to be merged into
2.7.x. It would be great if you could try it out and let me know how it
goes.
Josh
On Thu, Jun 21, 2012 at 9:00 AM, Greg Swift wrote:
Mohamed,
Did you get anywhere with this? I'm running into the exact same issue.
-greg
On Wednesday, November 23, 2011 7:29:34 PM UTC-6, Jacob Helwig wrote:
On 2011-11-23 15:53 , Mohamed Lrhazi wrote:
Thanks JacobDid that answer my TypeError as well?
No, a stack trace would help for that.
--
Jacob Helwig
http://about.me/jhelwig
Mohamed.
On Wed, Nov 23, 2011 at 5:28 PM, Jacob Helwig wrote:
On 2011-11-23 13:02 , Mohamed Lrhazi wrote:
am trying this:
scheduled_task { 'Puppet Run':
ensure= present,
enabled = true,
command = 'C:\\ruby187\\bin\\puppet.bat'**,
arguments = 'agent --verbose --logdest
C:\\Temp\puppet.log',
trigger = {
schedule = daily,
#every = 2 # Defaults to 1
#start_date = '2011-08-31', # Defaults to 'today'
start_time = '16:00', # Must be specified
}
}
And getting this error:
err: /Stage[main]/Gu_splunk/**Scheduled_task[Puppet Run]/ensure:
change
from absent to present failed: Could not set 'present on ensure:
TypeError at /etc/puppet/
environments/windows/modules/**gu_splunk/manifests/init.pp:84
--
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/-/cIrGZR2XNjYJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
--
Josh Cooper
Developer, Puppet Labs
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/CG9Sa5hf2jYJ.
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 view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/Gs01u9mrFhEJ.
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 Windows: scheduled_task : TypeError
So.. now I'm getting your error instead of mine.
On Thursday, June 21, 2012 12:46:08 PM UTC-5, Greg Swift wrote:
I believe you are correct. I removed the arguments key/value pair and it
ran fine. I'm patching in your changes to try it with the arguments option.
thank you very much
On Thursday, June 21, 2012 11:53:40 AM UTC-5, Josh Cooper wrote:
Hi Greg,
I believe this is issue https://projects.puppetlabs.com/issues/13008,
which I have fixed in my topic branch and is awaiting to be merged into
2.7.x. It would be great if you could try it out and let me know how it
goes.
Josh
On Thu, Jun 21, 2012 at 9:00 AM, Greg Swift wrote:
Mohamed,
Did you get anywhere with this? I'm running into the exact same issue.
-greg
On Wednesday, November 23, 2011 7:29:34 PM UTC-6, Jacob Helwig wrote:
On 2011-11-23 15:53 , Mohamed Lrhazi wrote:
Thanks JacobDid that answer my TypeError as well?
No, a stack trace would help for that.
--
Jacob Helwig
http://about.me/jhelwig
Mohamed.
On Wed, Nov 23, 2011 at 5:28 PM, Jacob Helwig wrote:
On 2011-11-23 13:02 , Mohamed Lrhazi wrote:
am trying this:
scheduled_task { 'Puppet Run':
ensure= present,
enabled = true,
command = 'C:\\ruby187\\bin\\puppet.bat'**,
arguments = 'agent --verbose --logdest
C:\\Temp\puppet.log',
trigger = {
schedule = daily,
#every = 2 # Defaults to 1
#start_date = '2011-08-31', # Defaults to 'today'
start_time = '16:00', # Must be specified
}
}
And getting this error:
err: /Stage[main]/Gu_splunk/**Scheduled_task[Puppet Run]/ensure:
change
from absent to present failed: Could not set 'present on ensure:
TypeError at /etc/puppet/
environments/windows/modules/**gu_splunk/manifests/init.pp:84
--
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/-/cIrGZR2XNjYJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
--
Josh Cooper
Developer, Puppet Labs
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/CG9Sa5hf2jYJ.
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] Creating a system module path (starting with Telly)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 +1 here As a distribution packager, a clear place to put things specific to the distribution is a big win for me. I've struggled in the past decided whether to package the clean upstream sources, or to add my own tweaks as well. To date, I've kept it clean, but this makes it easier to mix-and-match the two, and still be able to trace whether a problem lies in my distribution module or somewhere in the Puppet core. Greg - -- IRC: gwmngilfen www.github.com/GregSutcliffe -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk+ea0EACgkQ8O7RN8oK65O7ywCfYkmbP04gwn2x9641D0p3B0cf ZRAAn3RpalobnbuyvQBcodGTY6tS7ULq =Pix6 -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.
Re: [Puppet Users] Templating DHCP3-Server Need To Loop Through Subnets
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu 26 Apr 2012 17:24:17 BST, Brian Carpio wrote:
$subnet = [ 192.168.10.0, 192.168.20.0, 192.168.30.0 ]
$range = [ 192.168.10.115 192.168.10.120 ]
Sounds like you need a Hash here:
$subnets = { '192.168.10.0' = '192.168.10.115 192.168.10.120',
'192.168.20.0' = '192.168.20.105
192.168.20.130',
}
Then access it with something like:
% subnets.each do |subnet,range| -%
subnet %= subnet %
range %= range %
% end -%
Hope that helps,
Greg
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk+ZexQACgkQ8O7RN8oK65P3DACeNr38heQ8cILSbEgbGW1CMhng
ESsAniVsAJpfAoWklmCk+6qDCAwji/7d
=M9cK
-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.
Re: [Puppet Users] Re: Does one puppet master support multiply users to manage their resources?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri 13 Apr 2012 12:01:13 BST, Sans wrote: I'm not entirely sure but I don't think you can do that with single server - Puppet is actually for that. Someone please correct me if I'm wrong. But, as Puppet can maintain itself, all your users can use their machine as puppet-master and puppet-agent at the same time and can do whatever they want. Cheers!! On Apr 13, 4:06 am, runner pengyongb...@gmail.com wrote: Hi, I am a new user of puppet. We want every user of our group to manage software in his/her machines. How can puppet support this? Thank you. BR/Peng Yong I'd say there's a few ways to achieve that. Sans describes one of them - - local catalogs with local masters (or just puppet apply) If you want to run a standard master/slaves setup, the you could either keep the manifests in a version control system (say, git) and give your devs access to git. For more fine-grained control, put the lists of packages into some form of external data source (an ENC, or an external plugin like Hiera) and give your devs access to the lists on their machine. Of course, the latter reuires that your modules are (re)written to get their data appropriately. Cheers, Greg - --- OpenPGP - KeyID: CA0AEB93 -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk+IH+kACgkQ8O7RN8oK65ONxgCfQOdwmmu/8PmONPz3f8Wci1SE Ph8AoJLNzc/TwWyCdnVG9Lu8lWR7xwnE =gf7z -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: Puppet, Facter and Mcollective
As far as I know thats true... One option to limit facts is to use
confine to limit where its gets run.
For example, here is a fact that is clearly only applicable for
Solaris hosts:
Facter.add(obpversion) do
confine :kernel = :sunos
setcode do
%x{/usr/sbin/prtconf -V}.chomp.split( )[1]
end
end
Whilst this won't stop it from being downloaded, it will mean that the
code will only be run on hosts that meet the requirements.
Hope that helps...
On Feb 17, 11:23 am, Nan Liu n...@puppetlabs.com wrote:
On Thu, Feb 16, 2012 at 3:19 PM, Tony C tonyjch...@gmail.com wrote:
I'm not sure if this is the right group or not, but i'll start here.
I have Puppet enterprise 2.0, playing around with custom facts.
I have noticed that adding a custom fact to any module will distribute
that fact to all machines, regardless if they are assigned to that
module or not. Is there a way around this, or is this just by design?
Gary already pointed out the cron job. I'm not aware of an easy way to
perform limited pluginsync, it's either all or nothing. The reason
this is not possible, puppet need facts to compile catalog to know
what modules belong to a node, and puppet can't compile without facts,
so chicken and egg. For example, puppet can't know if it should
pluginsync my_fact if it's in my_module with the following code:
if $my_fact {include my_module}
HTH,
Nan
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Puppet Inventory Service
The way I've done it in the past is that you have one Puppet instance dedicated to the initial Puppet run.. It handles the CA plus farms out a puppet.conf which contains the local server info. The main issue I found is that Puppet doesn't seem to change masters without a restart even though it says that it has re-read the config file, so I got around it by doing a small Puppet run that only signs the cert and distributes the puppet.conf in the finish script of the OS install, then once the host rebooted that it found its correct Puppet server and then continues the upgrade from there. It can mean the CA-owning Puppet master only ever gets used on the initial install but maybe it can be used more with multiple environments - say build and production? Greg On Jan 5, 7:44 am, Christopher Johnston chjoh...@gmail.com wrote: That could get ugly, so I would have to create one CA, sign it then distribute it to all of my masters. Then also delete my certs on the clients and re-issue new ones. Is my thinking correct here? -Chris On Wed, Jan 4, 2012 at 3:31 PM, Nan Liu n...@puppetlabs.com wrote: On Wed, Jan 4, 2012 at 12:12 PM, Christopher Johnston chjoh...@gmail.com wrote: My inventory server is a puppetmaster, but its master of itself and is only being using for inventory services. If I point new clients to it will work fine. So think of my setup like this: puppet1.company.com and puppet2.company.com are two dedicated servers in each datacenter that handle local client connectivity only. By using certname=puppet I can copy the same CA to puppet2.company.com and support failing over if the primary server goes down. This setup is mimic'ed in about 20 other sites. The inventory server is a remote puppet master sitting in a backoffice datacenter that is setup with mysql and puppet dashboard to receive reports and inventory services from all 40 of the masters. So with this current arrangement how would I go about making sure the inventory server has a cert that is signed by the 40 other CAs. Certificate chain is an outstanding bug, so at the moment one CA sign all puppet master + inventory server cert. 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. -- 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] Win32API error with 2.7.8
Hi Josh, Of course. I'll pastie so as not to spam the list :) Here's an Arch client - http://pastie.org/2993397 Here's the Debian running puppet master -- trace --debug - http://pastie.org/2993401 Cheers, Greg -- 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/-/CLQ7bWd9wbAJ. 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: SSL issues on ruby1.9
On 25 November 2011 12:18, linuxbsdfreak linuxbsdfr...@gmail.com wrote: Hi Greg, There are some problems with SSL and ruby 1.9.2. Please visit the link below for solving the issue. http://urgetopunt.com/puppet/2011/09/14/puppet-ruby19.html Hi Kevin, Thanks for the reply. As I stated in my original post, I've tried this workaround (your link links back to the link I posted in the first place), and it doesn't solve the problem for me, so I'm now looking at how to debug this further. Cheers, Greg -- 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] SSL issues on ruby1.9
Hi all, I'm having issues with getting a client to request a certificate from my master when using Ruby 1.9. The error message is: err: Could not request certificate: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed I saw earlier messages on this topic (https://groups.google.com/d/topic/puppet-users/-knxubNs6sY/discussion) but the workaround suggested there (to create a hashed link to the CA) doesn't seem to solve the problem for me. Some details of my setup: Master: Debian Wheezy, Puppet 2.7.6, Ruby 1.8.7, Passenger Client: Archlinux, Puppet 2.7.6, Ruby 1.9.3 As stated, copying and hashing the ca from the Debian machine to the Arch machine doesn't solve the problem. I thought I might have an issue with differing versions of ruby, so I fired up a second Archlinux machine (so Ruby 1.9.3 / Puppet 2.7.6 again, but Webrick this time) and even then still got the same behaviour - with or with out the pre-hashed ca, I get the same error. For completeness, it should be said that this second Arch box can create it's own ca, and run as an agent against itself. I'm stumped. Presently I'm waiting for ruby1.8 to compile for Arch. I know this will solve the issue, but I'd really like to get 1.9 working since it's the default in Arch. I plan to try and find out what 1.8 is doing that 1.9 is not (or vice-versa) but if anyone has encountered this or wants to give me some tips on where to look, that would be appreciated... Cheers, Greg -- 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] Concat::Fragment collection broken in 2.7.5
On Friday, 7 October 2011 15:12:08 UTC+1, Bruno Leon wrote: sorry for the delay, I did a few tests and found out that the puppet master does not even go as far a querying the database. Starting from a clean query log (mysql), there is no sign of Concat::Fragment (tried small case as well). I concur - I'm using Foreman, which complicates the mysql trace, but as best I can see, it's not querying the databse for the exported resources at all. Since Dan asked for traces, here they are, master and node: http://pastie.org/2682017 Here's hoping the regression fixes in 2.7.6 fix this too :) Cheers, Greg -- 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/-/OAiJdI2v2eoJ. 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] Concat::Fragment collection broken in 2.7.5
Almost a me-too post, I should try to avoid that... This sounds like the mail I sent on Monday - I can certainly confirm Bruno's findings for collecting exported custom defines. I get the same error message, and I'm also using a remote MySQL database (no queueing agent, just direct access). I'd love to help with the debugging but I'm on a training course this week, and the connection is waaay too slow for database debugging. If you've not solved it by Monday, I'll dive in and provide some debug logs and db traces. Watching this thread with interest :) Greg -- 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/-/1mwaNRX2OX0J. 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] Fwd: FW: Hiera Issue
Would appreciate any advice, there is not a lot of info on hiera and I'm
currently stuck not able to perform a puppet run on the client.
-- Forwarded message --
From: Gregory Caldwell gregory.caldw...@us.icap.com
Date: Oct 3, 2011 3:56 PM
Subject: FW: Hiera Issue
To: Greg Caldwell greg.caldwe...@gmail.com
** **
** **
*From:* Gregory Caldwell
*Sent:* Monday, October 03, 2011 3:55 PM
*To:* puppet-users@googlegroups.com
*Cc:* Gregory Caldwell
*Subject:* Hiera Issue
** **
I keep getting this issue with hiera, and cannot perform a puppet run..
** **
*err: Could not retrieve catalog from remote server: Error 400 on SERVER:
Unknown function hiera_include at /etc/puppet/manifests/site.pp:16 on node
pup*
** **
hiera run seems to return the correct values but will not allow a puppet run
** **
hiera -a global_classes $args --config /etc/puppet/hiera.yaml –debug
DEBUG: Mon Oct 03 15:48:35 -0400 2011: Hiera YAML backend starting
DEBUG: Mon Oct 03 15:48:35 -0400 2011: Looking up global_classes in YAML
backend
[user::accounts::include ]
** **
Has anyone seen this issue on puppet 2.6.9?
** **
Portion of site.pp file
** **
node default {
$region= extlookup( value)
$hostgroup = extlookup( value )
$site = extlookup( value )
hiera_include( global_classes )
** **
and yaml is:
** **
---
global_classes: - user::accounts::include
**
This communication and all or some of the information contained therein may
be confidential and is subject to our Terms and Conditions. If you have
received this communication in error, please destroy all electronic and
paper copies and notify the sender immediately. Unless specifically
indicated, this communication is not a confirmation, an offer to sell or
solicitation of any offer to buy any financial product, or an official
statement of ICAP or its affiliates. Non-Transactable Pricing Terms and
Conditions apply to any non-transactable pricing provided. All terms and
conditions referenced herein available at www.icapterms.com. Please notify
us by reply message if this link does not work.
**
--
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] Fwd: FW: Hiera Issue
How do I resolve or troubleshoot this issue? I am running puppet 2.6:9 on
red hat 5:6 with the following packages:
rubygem-hiera-0:2:0-1
rubygem-hiera-puppet-0.2.0-1
On Oct 4, 2011 8:36 AM, R.I.Pienaar r...@devco.net wrote:
- Original Message -
Would appreciate any advice, there is not a lot of info on hiera and
I'm currently stuck not able to perform a puppet run on the client.
That means the puppet parser function isnt installed correctly
-- Forwarded message --
From: Gregory Caldwell gregory.caldw...@us.icap.com
Date: Oct 3, 2011 3:56 PM
Subject: FW: Hiera Issue
To: Greg Caldwell greg.caldwe...@gmail.com
From: Gregory Caldwell
Sent: Monday, October 03, 2011 3:55 PM
To: puppet-users@googlegroups.com
Cc: Gregory Caldwell
Subject: Hiera Issue
I keep getting this issue with hiera, and cannot perform a puppet
run..
err: Could not retrieve catalog from remote server: Error 400 on
SERVER: Unknown function hiera_include at
/etc/puppet/manifests/site.pp:16 on node pup
hiera run seems to return the correct values but will not allow a
puppet run
hiera -a global_classes $args --config /etc/puppet/hiera.yaml –debug
DEBUG: Mon Oct 03 15:48:35 -0400 2011: Hiera YAML backend starting
DEBUG: Mon Oct 03 15:48:35 -0400 2011: Looking up global_classes in
YAML backend
[user::accounts::include ]
Has anyone seen this issue on puppet 2.6.9?
Portion of site.pp file
node default {
$region = extlookup( value )
$hostgroup = extlookup( value )
$site = extlookup( value )
hiera_include( global_classes )
and yaml is:
---
global_classes: - user::accounts::include
**
This communication and all or some of the information contained
therein may be confidential and is subject to our Terms and
Conditions. If you have received this communication in error, please
destroy all electronic and paper copies and notify the sender
immediately. Unless specifically indicated, this communication is
not a confirmation, an offer to sell or solicitation of any offer to
buy any financial product, or an official statement of ICAP or its
affiliates. Non-Transactable Pricing Terms and Conditions apply to
any non-transactable pricing provided. All terms and conditions
referenced herein available at www.icapterms.com . Please notify us
by reply message if this link does not work.
**
--
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.
--
R.I.Pienaar
--
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] Fwd: FW: Hiera Issue
Ok thanks, ill take a look, much appreciated. On Oct 4, 2011 9:24 AM, R.I.Pienaar r...@devco.net wrote: - Original Message - How do I resolve or troubleshoot this issue? I am running puppet 2.6:9 on red hat 5:6 with the following packages: rubygem-hiera-0:2:0-1 rubygem-hiera-puppet-0.2.0-1 I dont believe the hiera_include() function has been released as a gem yet, you'll need to grab the latest from github. Don't really have time atm to do a new release that includes it all -- 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] Fwd: FW: Hiera Issue
We are operational again, thanks. On Tue, Oct 4, 2011 at 9:24 AM, R.I.Pienaar r...@devco.net wrote: - Original Message - How do I resolve or troubleshoot this issue? I am running puppet 2.6:9 on red hat 5:6 with the following packages: rubygem-hiera-0:2:0-1 rubygem-hiera-puppet-0.2.0-1 I dont believe the hiera_include() function has been released as a gem yet, you'll need to grab the latest from github. Don't really have time atm to do a new release that includes it all -- 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] Fwd: FW: Hiera Issue
On Tue, Oct 4, 2011 at 9:28 AM, Greg Caldwell greg.caldwe...@gmail.comwrote: Ok thanks, ill take a look, much appreciated. On Oct 4, 2011 9:24 AM, R.I.Pienaar r...@devco.net wrote: - Original Message - How do I resolve or troubleshoot this issue? I am running puppet 2.6:9 on red hat 5:6 with the following packages: rubygem-hiera-0:2:0-1 rubygem-hiera-puppet-0.2.0-1 I dont believe the hiera_include() function has been released as a gem yet, you'll need to grab the latest from github. Don't really have time atm to do a new release that includes it all -- 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] Problems with exported resources after upgrade to 2.7.5
Hi all,
I use a number of exported resources, some of which are exported custom
definitions.Since
upgrading to 2.7.5, I've seen an issue which is driving me up the wall
trying to debug it. Hopefully
someone can help :)
Consider the following three snippets of code:
*$modulepath/ntp/manifests/ntp_register.pp:*
define basics::ntp_register ($content=, $order=10) {
concat::fragment{ntp_conf_$name:
target = /etc/ntp.conf,
content = $content,
order = $order
}
}
$modulepath/servers/manifests/ntp_server.pp
class servers::ntp_server {
@@basics::ntp_register { Server Ntp $domain: content = stuff here\n }
}
*$modulepath/servers/manifests/ntp_client.pp*
class servers::ntp {
Basics::Ntp_register | title == Server Ntp $domain |
}
So we have a defined resource, an export of that resource, and a collection
of it. In 2.7.3, this worked fine,
however, in 2.7.4 and 2.7.5 I get
err: Could not retrieve catalog from remote server: Error 400 on SERVER:
Could not find type
Basics::Ntp_register on node client.foo.bar
I'm not sure what's changed that's causing this. I've read some stuff about
loading order, but they seem
to be old bugs that were fixed ages ago. I can see that rewriting this as a
local definition containing an
exported resource might work, but I'd rather understand what's wrong with my
approach first.
Thanks in advance,
Greg
--
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/-/D2Ou_f59FIoJ.
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] Building yaml files
That's nice and simple, thanks. On Sep 30, 2011 2:58 PM, Gary Larizza g...@puppetlabs.com wrote: `facter --yaml` will build a yaml file for you, if that's what you're looking for? On Fri, Sep 30, 2011 at 11:49 AM, Greg Caldwell greg.caldwe...@gmail.com wrote: Has anyone used facter to gather and build host specific yaml files before, was wondering how others were gathering and building this info for their host. Any suggestions are appreciated. -- 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. -- 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] Skipped schedule resources in reports
Hi all, Since upgrading a few test machines from 2.6.7 to 2.7.3, I've noticed something slightly odd. Every single run reports 6 skipped resources, yet the reports are empty - they only state the execution time as per usual). On digging further it seems that the auto-generated Schedule resources (type/schedule.rb, line 307) are the entities being skipped, presumably because I'm not using them in any of my manifests. This is leading to a lot of reports with spurious data in them - since I don't use schedules, why should I care that Puppet skipped the default ones? This wouldn't be an issue, but I'm processing the reports and producing emails which summarize activity in the last hour, so for every 2.7.3 node, I'm seeing 12 skipped resources per hour, which is noise that swamps the real data of resources that have changed for good reason. Is there a way to disable these default schedules, or the reporting of them? I tried --ignoreschedules on the commandline, but I get the impression that this causes other resources to run outside their normal schedule, rather than disabling the schedules themselves. As a hack, I added return Array.new to the self.mkdefaultschedules listed above, which stops the resources being generated, but this seems an ugly hack, and one I seem to have to make on every node. Is there a better way? Regards, Greg -- 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/-/KUcUT4hu148J. 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: Help setting up Ubuntu preseed for Puppet Clients
Jfro,
I did basically the same for Ubuntu 11.04... Personally, I found I
needed a postinstall script to finish the job. Mainly because Ubuntu
populates /etc/default/puppet with an environment variable START,
which defaults to 'no'...
So basically I had:
d-i pkgsel/include string openssh-server puppet curl
Openssh-server was for debug in the event of pain (I had a local user
created in the preseed file with a known password and full sudo access
as well so I could get into the box if needed), curl is needed in the
postinstall script.
Now I'm sure someone will kick me and tell me this isn't how you do
postinstall scripts in Ubuntu, but heres how I did it:
d-i preseed/late_command string chroot /target sh -c /usr/bin/curl -
o /tmp/postinstall http://url.com/postinstall /bin/sh -x /tmp/
postinstall
The contents of postinstall for updating the Puppet config are pretty
simple:
#!/bin/sh
CURL=/usr/bin/curl
${CURL} -o /etc/puppet/puppet.conf http://url.com/puppet.conf
${CURL} -o /etc/default/puppet http://url.com/default-puppet
I had a couple of reasons for pushing in a puppet.conf as well... I
wanted report=true set so that the first (and usually largest and most
complicated) puppet run got included in puppet dashboard (Ubuntu
defaults mean that you wouldn't get that). I also had a puppet host
that wasn't named puppet (and wouldn't be)... Again, the default
config in Ubuntu wasn't applicable for me...
/etc/default/puppet was updated just so that it would start
automatically next time around.
Hope that helps!
Greg
On Aug 3, 12:01 pm, Jfro jason.shir...@gmail.com wrote:
Bruno,
Thanks so much for taking the time to help me out! Your expertise saved me
hours of frustration.
1. This was very clear, thanks!
2. Can you point me in the right direction for setting up DNS? On my test
systems I just set the puppetmaster server in the puppet.conf file. Is
there a better way to tell puppet which server is its master?
3. Once puppet is installed will it automatically connect to the
puppetmaster? One my test clients I was running this command:
puppetd --server puppet.example.com --waitforcert 60 --test
Is it not necessary to do so?
4. Thanks for the command. If you get a chance can you tell me what is
happening here?
Again, I'm grateful for your help!
--
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] Validating a puppet configuration
Have you looked at using these?
projects.puppetlabs.com/projects/1/wiki/Puppet_Version_Control
--
Greg
On Fri, Jul 29, 2011 at 6:33 AM, Lars Kellogg-Stedman lar...@gmail.comwrote:
If anyone out there follows Serverfault, this is a duplicate of
http://goo.gl/CTS2u. I'm hoping there are some subject matter experts
here :).
I am trying to place some sanity checks (currently as git pre-commit hooks)
in our configuration repository to avoid committing invalid Puppet
configurations. I'm having a surprising amount of trouble coming up with a
way to effectively validate the configuration. My obvious first choice was
puppet parser validate ..., which does some gross syntax checks (unmatched
quotes and brackets and so forth) but doesn't throw errors on things like
this:
file { 'somefile':
requires = Service['someservice']
}
(where 'requires' should be 'require'), nor does it notice problems like
this:
sdlflsjlksdf { 'myname': }
(where 'sdlflsjlksdf' isn't defined anywhere).
Some folks have suggested puppet master --compile ..., but this really,
reallly wants to fix permissions all over the place on directories that are
used by Puppet. I have also tried puppet apply --noop, but this still
tries to stat() any files referenced in the manifests, which means it will
fail with permission errors if it tries to stat() a file or directory that
is not accessible to a non-root user. Does anyone here have suggestions for
effectively performing more aggressive syntax checks than those offered by
puppet parser validate?
-- Lars
--
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/-/cpzgsk5X2fgJ.
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] puppet and LDAP
This would likely have very little to do with puppet. If you've configured your /etc/nsswitch.conf file to look at ldap, then an ldap lookup will be made every time something user related happens. This includes launching daemon like puppet. If you are not already doing so, you may want to run nscd to cache these lookups. -- Greg On Tue, Jul 19, 2011 at 4:29 PM, ychen yung...@resolvity.com wrote: Hi, I installed the puppet server on a CentOS 5 box a while back. That box is configured to authenticate users based on data stored in our OpenLDAP server. Today I rebooted the box and found that puppetmasterd wasn't able to start because the LDAP server went down due to recent power outage. I checked the configuration settings of the puppet server in /etc/ puppet folder and didn't find anything that would make the puppet server aware of our LDAP server. In our logs, I saw the following: 2011-07-19T18:07:30-05:00 daemon.info puppet puppetmasterd[1292]: nss_ldap: reconnecting to LDAP server (sleeping 4 seconds)... 2011-07-19T18:07:34-05:00 daemon.info puppet puppetmasterd[1292]: nss_ldap: reconnected to LDAP server ldap:// ldap..com after 2 attempts So how can the puppet server be aware of the LDAP server anyway? How can I disable it? Thanks. -- 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] new variable scoping in templates
Justin, What would the syntax be along those lines when looking up custom facts? -- 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/-/BB3TAoW6PVEJ. 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] Custom fact scoping problem
OK, I think this is probably something that is entirely my fault, but I
cannot access a facter fact that I need. It evaluates only on certain
clients, and is dependent upon the creation and value of another fact.
Client and server are puppet 2.6.6 and facter 1.5.9.
Custom fact defined in common module:
/etc/puppetdev/modules/common/lib/facter/openldap.rb
Facter.add(is_ldap_server) do
setcode do
if FileTest.exists?(/usr/sbin/slapd)
Facter.add(ldap_rid) do
setcode do
case Facter::network_eth0
when 192.168.96.0
Facter::ipaddress[/[0-9]+$/].chomp
when 192.168.97.0
( 500 + Facter::ipaddress_eth0[/[0-9]+$/].chomp.to_i )
end
end
end
%x{echo yes}.chomp
else
%x{echo no}.chomp
end
end
end
This fact does evaluate on the client in question:
ldap_rid = 529
However, whatever way I use to try to find it in my template fails...can
someone please help?
Attempted syntaxes:
%= @ldap_rid %
% @ldap_rid %
%= ldap_rid %
% ldap_rid %
%= scope.lookupvar(ldap_rid) %
%= scope.lookupvar(::ldap_rid) %
...probably others as well. I'm probably just scoping it wrong, but every
time it comes up as blank or 'undef'.
Thanks.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/INd3uN7go6sJ.
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] new variable scoping in templates
Nan, that's exactly what I thought. I posted another thread with more
details on the issue I'm seeing though, so I won't go into my issues here.
On Friday, July 15, 2011 1:42:23 PM UTC-4, Nan Liu wrote:
Facts are top scope, so simply ::factname such as
scope.lookupvar('::operatingsystem')
--
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/-/TbRoQNKsY00J.
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: Custom fact scoping problem
Well, whatever problem I'm seeing is due to the nested Facter.add statements...when I pulled the ldap_rid one out and ran it separately, it worked. -- 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/-/rVoETeJ5MqwJ. 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: Custom fact scoping problem
I have it working, but I'm curious if this might be a bug with nested
Facter.add statements?
I simply un-nested them and used a 'confine' statement to make things work.
New facts posted below:
Facter.add(is_ldap_server) do
setcode do
if FileTest.exists?(/usr/sbin/slapd)
%x{echo yes}.chomp
else
%x{echo no}.chomp
end
end
end
Facter.add(ldap_rid) do
confine :is_ldap_server = :yes
setcode do
case Facter::network_eth0
when 192.168.96.0
Facter::ipaddress[/[0-9]+$/].chomp
when 192.168.97.0
( 500 + Facter::ipaddress_eth0[/[0-9]+$/].chomp.to_i )
end
end
end
--
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/-/ob5dE8e2afMJ.
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] Concat Module posted to Onyx Point Github.
Hi Trevor, I'll add my thanks to the pile, this is pretty awesome stuff! I compared the --graph results with the old concat moule, and this one - impressive difference :) As Larry says, the fact that it executes Concat_build on every run is a stopper for us, since the dependant services get restarted and we get report emails of any changes. Also, I can't see any way to hook into the filebucket for backups. I managed to hack in a cp file file.bak type functionality just before it actually cp's the newly-built file. However, my Ruby-fu isn't up to pulling in the filebucket stuff yet - might be worth adding to the todo list. Thanks again for the great module though :) Greg -- 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/-/OXRxUlV4QnVxU3NK. 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] Concat Module posted to Onyx Point Github.
Hi again, After an hour or three of hacking, I've managed to add the insync? checks to both the build and fragment types. It's the first time I've ever really messed with types and providers, so it's very ugly (and probably has bugs), however I'm happy to share my patches. Would that be best a) here b) in puppet-dev, or c) direct to Onyx Point? Cheers, Greg -- 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/-/bDJFMXd4Q0VFMG9K. 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 fails first run
Hey all...new to puppet, but desperately pushing it on everyone I see
around me :)...
I'm running into a relatively minor issue that keeps puppet from
properly completing its first run. Subsequent runs do not have these
issues, and I'm confused why. It appears to be looking for a different
repo's file... First run will create our local.repo file, but log an
error on a totally different file that causes subsequent yumrepos to
be skipped:
CentOS log:
notice //puppet-test-c64//File[RPM-GPG-KEY-xxx]/ensure defined content
as '{md5}b954c7d56ed699642484d8f2a82f4338'
notice //puppet-test-c64//Stage[pre]/Repo/Exec[yum_xxx_gpg]/returns
executed successfully
notice //puppet-test-c64//Stage[pre]/Repo/Yumrepo[local.repo]/descr
descr changed '' to 'CentOS-$releasever - Local'
notice //puppet-test-c64//Stage[pre]/Repo/Yumrepo[local.repo]/baseurl
baseurl changed '' to 'http://reposerver/centos$releasever-$basearch/
RPMS.local/'
notice //puppet-test-c64//Stage[pre]/Repo/Yumrepo[local.repo]/enabled
enabled changed '' to '1'
notice //puppet-test-c64//Stage[pre]/Repo/Yumrepo[local.repo]/gpgcheck
gpgcheck changed '' to '1'
notice //puppet-test-c64//Stage[pre]/Repo/Yumrepo[local.repo]/gpgkey
gpgkey changed '' to 'file:///etc/pki/rpm-gpg/RPM-GPG-KEY-xxx'
err //puppet-test-c64//Stage[pre]/Repo/Yumrepo[local.repo] Could not
evaluate: No such file or directory - /etc/yum.repos.d/addons.repo
notice //puppet-test-c64//Stage[pre]/Repo/Yumrepo[CentOS-Base.repo-
Plus] Dependency Yumrepo[local.repo] has failures: true
warning //puppet-test-c64//Stage[pre]/Repo/Yumrepo[CentOS-Base.repo-
Plus] Skipping because of failed dependencies
notice //puppet-test-c64//Stage[pre]/Repo/Yumrepo[CentOS-Base.repo-
addons] Dependency Yumrepo[local.repo] has failures: true
warning //puppet-test-c64//Stage[pre]/Repo/Yumrepo[CentOS-Base.repo-
addons] Skipping because of failed dependencies
I'm running puppet 2.6.6, and the problem is happening in the 'pre'
runstage defined in site.pp as such:
# Run Stages
stage {
'pre': before = Stage['main'];
}
class {
'repo': stage = 'pre';
}
---
Class 'repo' includes mostly yumrepo declarations to use our local
repositories (and execs to import keys). The local-only repo
(local.repo) should be created first, then all other repos. Class
'repo' is defined as such:
class repo {
package { ['yum','rpm']:
ensure = present,
}
package { 'yum-priorities':
ensure = present,
require = Yumrepo['local.repo'],
}
# Download and import Stern GPG RPM key
file { '/etc/yum.repos.d/':
ensure = directory,
}
file { 'RPM-GPG-KEY-xxx':
ensure = present,
path= '/etc/pki/rpm-gpg/RPM-GPG-KEY-xxx',
owner = 'root',
group = 'root',
mode= '0644',
require = Package['rpm'],
source = puppet://$servername/repo/RPM-GPG-KEY-xxx,
}
exec { 'yum_xxx_gpg':
command = '/bin/rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-xxx',
unless = '/bin/rpm -qi gpg-pubkey-xxx',
require = [ File['RPM-GPG-KEY-xxx'],Package['rpm'] ],
}
case $operatingsystem {
centos: {
yumrepo {
'CentOS-Base.repo-base':
name = 'base',
baseurl= 'http://reposerver/centos$releasever-$basearch/
RPMS.os/',
enabled= '1',
descr = 'CentOS-$releasever - Base',
gpgcheck = '1',
gpgkey = 'file:///etc/pki/rpm-gpg/RPM-GPG-KEY-
CentOS-5',
mirrorlist = 'absent',
require= Yumrepo['local.repo'],
notify = Exec['yum_clean_all'];
'CentOS-Base.repo-updates':
name = 'updates',
baseurl= 'http://reposerver/centos$releasever-$basearch/
RPMS.updates/',
enabled= '1',
descr = 'CentOS-$releasever - Updates',
gpgcheck = '1',
gpgkey = 'file:///etc/pki/rpm-gpg/RPM-GPG-KEY-
CentOS-5',
mirrorlist = 'absent',
require= Yumrepo['local.repo'],
notify = Exec['yum_clean_all'];
'CentOS-Base.repo-addons':
name = 'addons',
baseurl= 'http://reposerver/centos$releasever-$basearch/
RPMS.addons/',
enabled= '1',
descr = 'CentOS-$releasever - Addons',
gpgcheck = '1',
gpgkey = 'file:///etc/pki/rpm-gpg/RPM-GPG-KEY-
CentOS-5',
mirrorlist = 'absent',
require= Yumrepo['local.repo'],
notify = Exec['yum_clean_all'];
'CentOS-Base.repo-extras':
name = 'extras',
baseurl= 'http://reposerver/centos$releasever-$basearch/
RPMS.extras/',
enabled= '1',
descr = 'CentOS-$releasever - Extras',
gpgcheck = '1',
gpgkey = 'file:///etc/pki/rpm-gpg/RPM-GPG-KEY-
CentOS-5',
mirrorlist = 'absent',
require= Yumrepo['local.repo'],
notify = Exec['yum_clean_all'];
'CentOS-Base.repo-Plus':
name =
[Puppet Users] Re: issue with exported resources and subscribe
Hi,
In my exported resource manifests, if using code like:
File | tag == nagios::target | { notify = Service[nagios3] }
Does that work for you?
Cheers,
Greg
--
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: How to setup database for Inventory Service
Heya, I've merged both approaches. First, I dropped the db on my development server, and then let puppet recreate it. Since I don;t want to lose my historical data in production, I then dumped and compared the schema's from the dev (2.6.7) and prod (2.6.2) environments. I then upgraded prod to 2.6.7 and applied the diff. For what it's worth, here's the SQL I had to execute. Usual disclaimers on you mileage here :) ALTER TABLE resources ADD KEY `exported_restype_title` (`exported`,`restype`,`title`(50)); CREATE TABLE `inventory_facts` ( `node_id` int(11) NOT NULL, `name` varchar(255) NOT NULL, `value` text NOT NULL, UNIQUE KEY `index_inventory_facts_on_node_id_and_name` (`node_id`,`name`) ENGINE=InnoDB DEFAULT CHARSET=utf8; CREATE TABLE `inventory_nodes` ( `id` int(11) NOT NULL AUTO_INCREMENT, `name` varchar(255) NOT NULL, `timestamp` datetime NOT NULL, `updated_at` datetime DEFAULT NULL, `created_at` datetime DEFAULT NULL, PRIMARY KEY (`id`), UNIQUE KEY `index_inventory_nodes_on_name` (`name`) ENGINE=InnoDB AUTO_INCREMENT=4 DEFAULT CHARSET=utf8; I can see data going into the DB from the latest runs, and I can curl the inventory service, so it seems ok. Setting up Dashboard 1.1.0 as we speak :) HTH, Greg -- 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 defining exported resources
On Thursday, March 17, 2011 2:41:06 PM UTC, Felix.Frank wrote: I call possible bug on this one. I don't see an open issue that sounds quite like this, so you may want to report this. http://projects.puppetlabs.com/projects/puppet/issues/new Cheers, Felix Thanks Felix - nice to know I'm not going mad. I'll double check it later today on the latest Puppet to make sure it's still an issue, and then get it filed. Cheers, Greg -- 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 defining exported resources
Hi all,
I'm learning all about exported resources, and I've encountered an
issue. Put simply, two things which logically should be same result in
one working and one not working. I'm sure I'm missing something
obvious, but I can't see it, so I'm someone can spot my error.
The situation: I'm running stock Debian 2.6.2 on master and client. I'm
defining a simple File export which creates a directory on another
machine. Here's the code that works:
class client {
@@file{ /mnt/backups/$hostname:
ensure = directory,
owner = remotebackup,
group = users,
tag = rsync::coreserver::$region,
}
}
class server {
File | tag == rsync::coreserver::$region |
}
This works exactly as expected - the server machine creates a
directory named as per the client's hostname. However, if I wrap this
in a define(), it all goes wrong. Here's the code:
class client {
@@rsync::target{ $hostname: tag = rsync::coreserver::$region }
}
class server {
Rysnc::Target | tag == rsync::coreserver::$region |
}
define rsync::target() {
file{ /mnt/backups/$name:
ensure = directory,
owner = remotebackup,
group = users,
}
}
The define just wraps up the file definition so it's easier for me to
collect the right resources in the server class. But it doesn't work.
The server doesn't create any directories, although I can see entries
in the storeconfig db for the rsync::target resource type. What am I
missing?
Many thanks,
Greg Sutcliffe
--
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] Nagios Module and use of the @@ and || notation
Avi,
I am exporting my resources to the database. I can verify that this is
occurring. Yet I am not getting all of the the
Nagios_host |target ==nagios_hosts.${fqdn}.cfg|
files written to my nagios server and I am interested in finding out how to
trace down this functionality of the collection and exportation of resources
so I can properly identify how/why it is not working in all of the cases.
I guess if someone could point me to a basic model of this exportation and
collection process I could work from there. Is there any detailed writing
about this?
Greg
On 9/30/10 3:48 PM, Avi Miller avi.mil...@gmail.com wrote:
Greg Haase wrote:
Are you aware of any documentation that clearly explains how this
collect/export functionality works?
Exporting and collecting resources relies on stored configuration[1]
being enabled on your Puppet Master. You should ensure that the database
is configured and working before trying to export and collect resources.
Cheers,
Avi
[1]
http://projects.puppetlabs.com/projects/1/wiki/Using_Stored_Configuration
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-us...@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] Nagios Module and use of the @@ and || notation
Greetings,
I am working on getting Nagios implemented with Puppet so that when I add a
node to Puppet a Nagios configuration file is generated.
I can get nagios installed and configured on the server and the client with
no problems. Yet getting the client configuration file on to the server is
not happening. I did have it working at one point in time yet It seems that
I cannot get back to that configuration.
I am relying on notation using the @@ and || I found somewhere in the
documentation yet I did not find a proper discussion of exactly how it
works. I don't feel that I have a proper understanding of how it works.
What I understand is that by using the
@@name {}
I can load data into a global object that is accessible from any puppet
member. Who uses the
name ||
Notation to call the data stored in that global object.
I believe that in the past I was able to view this information on my puppet
server with
ralsh nagios_host
It would give me a listing of what was stored in nagios_host. Now when I do
this I see nothing.
Here is a listing of what I understand as being a way to use this:
Is this correct?
-
class nagios-server{
A bunch of other stuff ..
file { /etc/nagios/:
ensure = 'directory',
mode = 755,
owner = nagios,
group = nagios,
recurse = true;
}
Nagios_host |target == /etc/nagios/nagios_hosts.${fqdn}.cfg|
}
-
class nagios-client {
@@nagios_host { $fqdn:
target = /etc/nagios/nagios_hosts.${fqdn}.cfg,
ensure = present,
alias = $hostname,
address = $ipaddress,
use = my-servers,
check_command = check-host-alive,
max_check_attempts = 3,
hostgroups = my-servers,
contact_groups = admins,
}
A bunch of other stuff ..
}
-
Could someone please point me in the right direction to some documentation
that could help clarify this the use of the @@ and ||?
I'd greatly appreciate it.
Thanks
Greg
Greg Haase
gha...@syntheticgenomics.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-us...@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] Nagios Module and use of the @@ and || notation
Stephen,
Ah the David Schmitt nagios module. This is what I based my work on. I used
it as a model.
Are you aware of any documentation that clearly explains how this
collect/export functionality works?
Greg
On 9/30/10 3:31 PM, Steven Wagner leftath...@gmail.com wrote:
Hi Greg,
I'm on my phone at the moment so I don't have the exact link handy, but there
is a module on GitHub that works. I tinkered with it a lot in my old setup
but found most of my problems were due to not really understanding how the
collect/export functionality worked.
This is my favorite feature of Puppet. When I got it working, I teared up a
bit. :)
I believe it's http://github.com/DavidS/puppet-nagios
(mobile edition)
On Sep 30, 2010, at 3:04 PM, Greg Haase gha...@syntheticgenomics.com wrote:
Greetings,
I am working on getting Nagios implemented with Puppet so that when I add a
node to Puppet a Nagios configuration file is generated.
I can get nagios installed and configured on the server and the client with
no problems. Yet getting the client configuration file on to the server is
not happening. I did have it working at one point in time yet It seems that
I cannot get back to that configuration.
I am relying on notation using the @@ and || I found somewhere in the
documentation yet I did not find a proper discussion of exactly how it
works. I don't feel that I have a proper understanding of how it works.
What I understand is that by using the
@@name {}
I can load data into a global object that is accessible from any puppet
member. Who uses the
name ||
Notation to call the data stored in that global object.
I believe that in the past I was able to view this information on my puppet
server with
ralsh nagios_host
It would give me a listing of what was stored in nagios_host. Now when I do
this I see nothing.
Here is a listing of what I understand as being a way to use this:
Is this correct?
-
class nagios-server{
A bunch of other stuff ..
file { /etc/nagios/:
ensure = 'directory',
mode = 755,
owner = nagios,
group = nagios,
recurse = true;
}
Nagios_host |target == /etc/nagios/nagios_hosts.${fqdn}.cfg|
}
-
class nagios-client {
@@nagios_host { $fqdn:
target = /etc/nagios/nagios_hosts.${fqdn}.cfg,
ensure = present,
alias = $hostname,
address = $ipaddress,
use = my-servers,
check_command = check-host-alive,
max_check_attempts = 3,
hostgroups = my-servers,
contact_groups = admins,
}
A bunch of other stuff ..
}
-
Could someone please point me in the right direction to some documentation
that could help clarify this the use of the @@ and ||?
I'd greatly appreciate it.
Thanks
Greg
Greg Haase
gha...@syntheticgenomics.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-us...@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-us...@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] best way to include a variable in many modules ?
I created a module with a .pp file containing the following:
#
## Class for dns configuration
#
class resolve-dns{
include my-dns-resolver::location
file{ '/etc/resolv.conf':
source = $my-dns-resolver::location::resolvesource,
ensure = present,
mode = 644,
owner = root,
group = root;
}
}
#
#
class my-dns-resolver::location {
case $domain{
site-a: {
$resolvesource=puppet:///files/etc/resolv.site-a.conf
}
site-b: {
$resolvesource=puppet:///files/etc/resolv.site-b.conf
}
}
}
And included my resolve.conf files in my files directory at the above given
path.
I hope that helps, I would like to see how other people did this.
Greg
On 9/23/10 11:40 AM, Mark Glossop mark.glos...@uwa.edu.au wrote:
On 24/09/10 1:03 AM, somebody called Tony G. (tony...@gmail.com) wrote this:
http://projects.puppetlabs.com/projects/1/wiki/Resolv_Conf_Patterns
On Thu, Sep 23, 2010 at 11:36 AM, Daniel Maher d...@witbe.net wrote:
Hello,
I have two sites with a small number of machines at each. Each site is
functionally identical. I would like to set up a bunch of templates for the
various services at each site, with a handful of variables that indicate which
site the service is configured for. What would be best practice way to
accomplish this in Puppet ?
Consider :
s...@abc$ facter | grep domain
domain = abc.dom.ain
s...@abc$ cat /etc/resolv.conf
search abc.dom.ain
10.1.0.1
s...@xyz$ facter | grep domain
domain = xyz.dom.ain
s...@abc$ cat /etc/resolv.conf
search xyz.dom.ain
10.2.0.1
Thus i would like a template resolv.conf.erb :
search %= site_name =.dom.ain
10.%= site_ip =.0.1
I _could_ put something like this into _every_ class :
$site_name = $domain ? {
'abc.dom.ain' = 'abc',
'xyz.dom.ain' = 'xyz',
}
# etc...
That works, but frankly it's offensive in every way. There are clearly other
ways to go about it, so i am curious : for Puppet, what is the best practice
solution ?
Thank you all for your time and consideration.
Er, unless I'm missing something folks, the OP wasn't asking about managing
/etc/resolv.conf - AFAICT /etc/resolv.conf was only used by the OP as an
example. How to manage that file in a one-off case it wasn't the objective.
So rehashing [paraphrasing mine]: what is Puppet best practice for setting a
handful of variables in a single location that then determine the
configuration of each client?
I'm posting because I'm interested in the answer too...and the answers so far
don't help answer it IMHO. If the answer is in the documentation somewhere [I
know I haven't found it so far...], well, a link to that doc would be welcomed
for my part.
Regards,
M.
--
Mark Glossop
IT Projects Officer [Murchison Widefield Array Radiotelescope]
ICRAR - International Centre for Radio Astronomy Research
Discovering the hidden Universe through Radio Astronomy
[cid:3368140823_18093341]
E: mark.glos...@icrar.org | W: http://icrar.org
P: +61 [0]8 6488 7744 | RSS: http://icrar.org/news/feed
M: +61 [0]406 351 336 | TW: http://twitter.com/icrar
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-us...@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] exec not finding shell builtins/functions?
Hello,
We're running 2.6 on Ubuntu 10.04 and here's what I'm seeing (simplified test):
class cdtest {
exec {'cdtest': command = 'cd' }
}
# puppet agent --test
info: Caching catalog for servername
info: Applying configuration version '1280441519'
err: /Stage[main]/Cdtest/Exec[cdtest]/returns: change from notrun to 0 failed:
Could not find command 'cd'
notice: Finished catalog run in 0.65 seconds
#
Any ideas on why this is failing? I am running into this with rvm as well
(since it is a function and not a binary).
Thanks!
Greg Graf
Systems Engineer
Rackspace
Confidentiality Notice: This e-mail message (including any attached or
embedded documents) is intended for the exclusive and confidential use of the
individual or entity to which this message is addressed, and unless otherwise
expressly indicated, is confidential and privileged information of Rackspace.
Any dissemination, distribution or copying of the enclosed material is
prohibited.
If you receive this transmission in error, please notify us immediately by
e-mail
at ab...@rackspace.com, and delete the original message.
Your cooperation is appreciated.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-us...@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] complex data types in puppet facter
Hello Dan, Thanks. I'm following your suggestion and serializing anything complex that I need to get at in ERB. -- Greg Dan Bode wrote: Hi, On Fri, Apr 2, 2010 at 3:37 PM, Greg Retkowski g...@rage.net mailto:g...@rage.net wrote: Good Afternoon, I'm running puppet vers. 0.24.4 and am trying to use some facts in puppet ERB templates. .24.4 is a pretty old version of Puppet, if its feasible I would upgrade. It appears as long as the fact is a simple type, such as a String, the fact works as expected in the ERB template. However if the fact is something more complex (like a Hash) it appears to get converted into a string. Using it directly in ruby (via Facter.value) returns the correct complex data type. Is there an elegant way to use complex facts in puppet's erb templates? Puppet will support hashes in the next major version (Rwolf), although I am not sure if the interaction between Puppet and Facter will support it. Until then, the best work around is to serialize the data as a string and deserialize it in the erb. Thanks for any help you may have! Cheers, -- Greg Hope this helps, -Dan -- 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 mailto:puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com mailto:puppet-users%2bunsubscr...@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-us...@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-us...@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] complex data types in puppet facter
Good Afternoon, I'm running puppet vers. 0.24.4 and am trying to use some facts in puppet ERB templates. It appears as long as the fact is a simple type, such as a String, the fact works as expected in the ERB template. However if the fact is something more complex (like a Hash) it appears to get converted into a string. Using it directly in ruby (via Facter.value) returns the correct complex data type. Is there an elegant way to use complex facts in puppet's erb templates? Thanks for any help you may have! Cheers, -- Greg -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@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] ensuring a file is copied in before evaluating another class.
I also tried this in my top-level puppet config:
if $defined_after_bootstrap_var {
import definitions/*.pp
} else {
import bootstrap.pp
}
However it looks like the 'import definitions/*.pp' is still evaluated
even though $defined_after_bootstrap_var isn't defined. Is there a way
to conditionally use import?
-- Greg
Daniel wrote:
I dont think there's a way to enforce this because you need to reload
puppetd to activate the changes. If you use puppetrun you could
distribute only the tag for your puppet module and restart the
service. Hope this helps
--
You received this message because you are subscribed to the Google Groups Puppet
Users group.
To post to this group, send email to puppet-us...@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] ensuring a file is copied in before evaluating another class.
Hello Everyone,
I have a case where I'm depending on custom facter rules in my puppet
config, and those custom facter rules come from a ruby library that
puppet installs. I need to know how I can ensure that library is
installed by puppet before classes that depend on those facts are
evaluated..
To illustrate...
class facter_rules {
file {
/usr/lib/ruby/site_ruby/1.8/facter/custom.rb:
source = puppet://$server/dist/custom.rb;
}
}
class sitestuff {
include facter_rules
case $customfact {
value-a: {
# do stuff
}
value-b: {
# do other stuff
}
}
}
...
Using this, often class sitestuff gets evaluated before my facter_rules
file copy is done - which results in puppet exiting without putting
custom.rb in place. I'm using puppet vers. 0.24.4.
I've considered using 'before =' in my facter_rules file definition,
but class 'sitestuff' may be defined or not defined depending on what
services/classes are defined on the host.
Any ideas on how I can get around this chicken and egg problem?
Cheers,
-- Greg
--
You received this message because you are subscribed to the Google Groups Puppet
Users group.
To post to this group, send email to puppet-us...@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] ensuring a file is copied in before evaluating another class.
Thanks! That sounds like the right way to do it! How to I ensure puppet
copies out a new puppet.conf with the changes before evaluating the
class that uses 'case $customfact'?
Cheers,
-- Greg
Daniel wrote:
Don't distribute your facter plugin via manifest. Use puppet's sync
which is described her:
http://reductivelabs.com/trac/puppet/wiki/PluginsInModules
This will distribute your facter addons at the beginning of your run
and you can use them in like any normal fact.
On Thu, Feb 25, 2010 at 10:25 PM, Greg Retkowski g...@rage.net wrote:
Hello Everyone,
I have a case where I'm depending on custom facter rules in my puppet
config, and those custom facter rules come from a ruby library that puppet
installs. I need to know how I can ensure that library is installed by
puppet before classes that depend on those facts are evaluated..
To illustrate...
class facter_rules {
file {
/usr/lib/ruby/site_ruby/1.8/facter/custom.rb:
source = puppet://$server/dist/custom.rb;
}
}
class sitestuff {
include facter_rules
case $customfact {
value-a: {
# do stuff
}
value-b: {
# do other stuff
}
}
}
...
Using this, often class sitestuff gets evaluated before my facter_rules file
copy is done - which results in puppet exiting without putting custom.rb in
place. I'm using puppet vers. 0.24.4.
I've considered using 'before =' in my facter_rules file definition, but
class 'sitestuff' may be defined or not defined depending on what
services/classes are defined on the host.
Any ideas on how I can get around this chicken and egg problem?
Cheers,
-- Greg
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-us...@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-us...@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: other end went away leads to multiple report mails
Neil,
I had a similar problem back when I was running 0.24.7 and 0.24.8 on
Solaris. My solution was to remove tagmail completely and put in a
seperate system that parsed the YAML reports and send a single email
combining all changes during a given period of time (in my case -
daily). Required a little coding, but its not too difficult. Then just
schedule it to run from cron on each of your master servers that
receive reports from clients.
To be honest, tagmail isn't that useful outside of running it on a few
hosts... I personally don't want to receive 100+ emails every time I
changed an entry that was common to every node... This way I receive
one email in a summarised format - if I need more detail there is
always the messages file on the node itself, or you can optionally
keep the reports for a few days... Just remember to set up a tidy on
the reports directory if you do that... (Oh, and if you set up a tidy
on the reports directory, you may want to bear in mind Bug 2701:
http://projects.reductivelabs.com/issues/2701)
The base of the code is something like:
require puppet
require yaml
require find
Puppet[:config] = /etc/puppet/puppet.conf
Puppet.parse_config
Puppet[:name] = puppetmasterd
Puppet::Node::Facts.terminus_class = :yaml
File.find(/var/puppet/reports) do | report |
next if FileTest.directory?(report)
thisreport = open(report) { |fh| YAML::load(fh) }
print Host: + thisreport.host
reporttime = File.stat(report).mtime.to_i # seconds since epoch...
thisreport.logs.each do |log|
# Whatever you want to find out about each message...
end
File.unlink(report) # If you don't need them anymore...
end
On Dec 7, 10:33 am, Neil Prockter n.prock...@lse.ac.uk wrote:
Evening All,
I've been getting a random number of copies of report mails, the same
report sent multiple times at the same second, and finally got tired
enough of it to look into it.
They are sent from puppet rather than a mail server issue.
I get one extra copy every time the client gets a warning: Other end
went away; restarting connection and retrying.
Updating the server from 0.24.8 to 0.25.1 did not improve matters.
Running with client 0.24.5 debug ends with
debug: Calling puppetreports.report
warning: Other end went away; restarting connection and retrying
warning: Other end went away; restarting connection and retrying
info: Sent transaction report in 3.29 seconds
notice: Finished catalog run in 11.40 seconds
upgrading the client to 0.24.8 client debug ends with
debug: Calling puppetreports.report
info: Other end went away; restarting connection and retrying
info: Other end went away; restarting connection and retrying
info: Sent transaction report in 3.66 seconds
notice: Finished catalog run in 12.61 seconds
so the level has been reduced to info but I still get the multiple
report mails
updating to 0.25.1 seems to deal with the repeated mails though I see
err: Reporting failed: end of file reached
Updating clients to 0.25.1 across the board is probably not an option
for me so I'd like to fix the reporting from a server side if possible.
My tagmail.conf is just
all: an-addr...@that.goes.to.me
Neil
Please access the attached hyperlink for an important electronic
communications
disclaimer:http://www.lse.ac.uk/collections/secretariat/legal/disclaimer.htm
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-us...@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 SYN flood
I'm actually curious about how you managed to get so far without needing to move to Mongrel or Passenger... Pete - am wondering what types of objects you have been running in your config. I'm suspecting really light stuff and probably not a huge amount of it, am I right? Things like file permissions checks, maybe some user/group management? From what I can tell from the code, this sort of stuff would be fairly light on the puppetmaster server, enabling quick compiles of the config... I'm guessing nothing that involves serving a file (as it will require md5 checksums to be run on the puppetmaster), no defines or any other more complex configuration, am I right? At the moment on my systems I'm seeing compile times of around 30 seconds or so, I'm guessing your compile times are much, much quicker. Like a couple of seconds at most perhaps? Personally, I don't consider this insane. I find this an interesting case that could help understanding the complexities of the performance of the puppetmaster compiler. I'm running 0.24.8 and am constantly looking for ways to speed up compilation on the server end (yes, 0.25 is on my radar, waiting for 0.25.1 though...) I'm also interested that you ran into a kernel issue before you ran into the WEBrick 2 connection maximum... Usually the case is that you run into WEBrick dropping connections, not the OS complaining of SYN flooding. Greg On Oct 8, 8:17 am, Pete Emerson pemer...@gmail.com wrote: Either insane ... or ignorant of the fact that one shouldn't push WEBrick that far. Or maybe both. Today I bit the bullet and used the instructions here: http://reductivelabs.com/trac/puppet/wiki/UsingPassenger to migrate to Passenger. Pretty painless. I tested it on 8141 first, leaving WEBrick running, then cut over. So far, so good. Next up is Puppet 0.25! Pete On Tue, Oct 6, 2009 at 3:03 PM, Paul Lathrop paul.lath...@gmail.com wrote: On Tue, Oct 6, 2009 at 2:10 PM, Pete Emerson pemer...@gmail.com wrote: I'm seeing this in my logs: kernel: possible SYN flooding on port 8140. Sending cookies. Could not call fileserver.describe: #Errno::ECONNRESET: Connection reset by peer I'm running 0.24 with webrick, and have approximately 180 hosts under it. Respectfully... You're insane. It's dumb luck you've gotten this far :-D I'm guessing that I'm simply hitting the limits of what webrick can do (I'm working on moving to 0.25 and passenger). Is that true? What's the simplest way to alleviate the problem in the meantime? Is Turn off puppet. there a simple way to migrate to 0.24 and passenger, for example? Or maybe something easier, like configure puppet to run less frequently (or perhaps only on demand)? Any thoughts appreciated. Most people hit this wall at 30-40 hosts, I made it to about 50. I'm shocked you got up to 180. Your only choice is to move to one of the scalable options (Mongrel, Passenger, etc.) --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: Problem installing Solaris Datastream Package
Andy,
How are you doing the package definition now?
Should be something like:
package { SMCossl:
source = http://ezsrva004/openssl-0.9.8k-sol10-x86-local;,
adminfile = /path/to/adminfile,
ensure = installed
}
If it helps heres the definition I use for package installs (I'm using
NFS due to to the fact that you can't use reponse files if you are
installing a HTTP stream package. If this isn't an issue for you, it
be changed to a HTTP source by changing the source line - example has
been commented out in place):
define pkginstall($pkgsource, $pkgresponse = , $pkgrequire = ) {
$installsvr = puppet
$installpath = /path/to/pkgs
package { $title:
ensure = installed,
schedule = weekly, # Packages should only be checked weekly
- probably should be less often...
adminfile = /etc/default/adminfile,
# Using NFS/AutoFS
source = /net/$installsvr/$installpath/$hardwareisa/
$kernelrelease/$pkgsource,
# for HTTP:
# source = http://$installsvr/$installpath/$hardwareisa/
$kernelrelease/$pkgsource,
# Yes, we need autofs and nsswitch.conf to be set up so that /
net works during jumpstart.
# adminfile is required for unattended installation.
require = [ File[/etc/default/adminfile], Service
[autofs], File[/etc/nsswitch.conf] ],
}
if ($pkgresponse != ) {
# Attach the response file on here.
Package[$title] {
responsefile = /var/spool/pkg/response/$pkgresponse
}
# Include the response file as a file requirement.
file { /var/spool/pkg/response/$pkgresponse:
ensure = present,
source = [ puppet:///common/responsefiles/$pkgresponse-
$hostname,
puppet:///common/responsefiles
$pkgresponse ],
# Do the dependency the other way around - easier to
specify this way
# as the package already has dependencies set.
before = Package[$title]
}
}
}
Example call to define:
pkginstall { SMCsudo:
pkgsource = sudo-1.7.2p1-sol10-$hardwareisa-local,
pkgrequire = Package[SMClintl]
}
I've found that this gets around *most* of the issues the Solaris
package manager has... Not all of
them tho... Upgrading packages is still an issue I need to figure
out...
Hope that helps...
Greg
On Sep 30, 8:48 pm, Andy Kocher p...@yahoo.com wrote:
I found a workaround:
I changed some parts of the sun.rb:
cmd -d @resource[:source]
cmd -n all
looks like this is what we need.
cheers,
Andy
On Sep 30, 7:18 am, Andy Kocher p...@yahoo.com wrote:
Hi,
the same story with http. This looks good,
/usr/sbin/pkgadd -dhttp://ezsrva004/openssl-0.9.8k-sol10-x86-local
## Downloading...
...20%...40%...60%...80%...
100%
## Download Complete
The following packages are available:
1 SMCossl openssl
(x86) 0.9.8k
but Puppet tries.
/usr/sbin/pkgadd -dhttp://ezsrva004/openssl-0.9.8k-sol10-x86-local-n
openssl-0.9.8k-sol10-x86-local
How can I configure puppet to omit the package name after non-
interactive switch?
cheers,
Andy
On Sep 29, 7:54 pm, Moty mot...@gmail.com wrote:
I wonder
Did http worked for you as a source datastream protocol for pkg
files ?
Moty
On Sep 29, 10:02 am, martin martin.engl...@sun.com wrote:
Hi Andy!
On Sep 29, 7:59 am, Andy Kocher p...@yahoo.com wrote:
I'm having problem with the way Puppet is processing Solaris
datastream packages. The following error occurs:
err: //Node[basenode]/openssl/Package[openssl-0.9.8k-sol10-x86-local]/
ensure: change from absent to present failed: Execution of '/usr/sbin/
pkgadd -a /etc/puppet/files/puppet -d /var/tmp/staging/openssl/
openssl-0.9.8k-sol10-x86-local -n openssl-0.9.8k-sol10-x86-local'
returned 1: pkgadd: ERROR: no packages were found in /var/tmp/
dstrePaOVx
What does your package definition look like?
When I install package streams I use:
package { SFWrsync:
adminfile = /etc/pkgadmin,
source = http://$pkg_server/packages/$hardwareisa/$name.pkg;
}
cheers,
/Martin
--~--~-~--~~~---~--~~
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: Controlling the frequency of different tasks.
Just note that if you want stuff running every 5 minutes, use cron - running Puppet every 5 minutes is generally not practical. Greg On Sep 15, 10:38 am, Tim Uckun timuc...@gmail.com wrote: Are you perhaps looking for the schedule meta-parameter: http://reductivelabs.com/trac/puppet/wiki/TypeReference#available-met... Yea!. Thanks. --~--~-~--~~~---~--~~ 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: Errors after upgrade to 0.25.0
Have you looked at the new auth.conf file? Chances are you need to put one into your /etc/puppet directory... Theres a sample one in the source code bundle. Greg On Sep 10, 12:31 am, Martin Englund martin.engl...@sun.com wrote: After upgrading one of our puppetmasters to 0.25.0 we get the following errors on the client (also running 0.25.0): err: /File[/var/puppet/lib]: Failed to generate additional resources using 'eval_generate': Error 403 on SERVER: Forbidden request: lab- git2.SFBay.Sun.COM(10.6.48.12) access to /file_metadata/plugins [search] at line 0 err: /File[/var/puppet/lib]: Failed to retrieve current state of resource: Error 403 on SERVER: Forbidden request: lab- git2.SFBay.Sun.COM(10.6.48.12) access to /file_metadata/plugins [find] at line 0 Could not retrieve file metadata for puppet://puppeteer.sfbay.sun.com/plugins: Error 403 on SERVER: Forbidden request: lab-git2.SFBay.Sun.COM (10.6.48.12) access to /file_metadata/plugins [find] at line 0 err: Could not retrieve catalog from remote server: Error 403 on SERVER: Forbidden request: lab-git2.SFBay.Sun.COM(10.6.48.12) access to /catalog/lab-git2.sfbay.sun.com [find] at line 0 I do not have an auth.conf file. Any hints to why this is happening are very welcome :) cheers, /Martin --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
