On 02/10/12 14:49, Paul Tötterman wrote:
> Hi,
>
> My manifests used to work with 2.7.19 but after upgrading to 3.0.0 I
> keep getting:
>
> Error: /Stage[main]/.../Augeas[...]: Could not evaluate: uninitialized
> constant Augeas::NO_LOAD
This will be a dependency on ruby-augeas 0.3.0 or higher.
G`Day !
On Wednesday, 3 October 2012 12:35:34 UTC+10, Ryan Coleman wrote:
>
> Hello,
>
> If you weren't at PuppetConf or didn't catch my talk, here's a quick
> recap. I'm product owner for the Puppet Forge team which formed in
> July with 2 awesome engineers and an equally awesome designer. We'
On Wednesday, October 3, 2012 1:36:22 AM UTC+1, Michael Stanhke wrote:
>
> On Tue, Oct 2, 2012 at 1:30 PM, Jeff McCune
> >
> wrote:
> > On Tue, Oct 2, 2012 at 1:17 PM, Robert Rothenberg
> > >
> wrote:
> >> I am using CentOS 6 with the PuppetLabs yum repo from
> >> http://yum.puppetlabs.com
Yesterday my puppetmaster and nodes got upgraded to puppet-3.0.0.
Since then, all puppet runs have been failing with this error:
Error: Could not retrieve catalog from remote server: Error 400 on
SERVER: Could not autoload puppet/indirector/node/active_record:
uninitialized constant ActiveReco
On 3 Oct 2012, at 03:35, Ryan Coleman wrote:
> Hello,
>
> If you weren't at PuppetConf or didn't catch my talk, here's a quick
> recap. I'm product owner for the Puppet Forge team which formed in
> July with 2 awesome engineers and an equally awesome designer. We're a
> team dedicated to the For
On 2 Oct 2012, at 21:17, Robert Rothenberg wrote:
> I am using CentOS 6 with the PuppetLabs yum repo from
> http://yum.puppetlabs.com
>
> I noticed that today version 3 is available on the repo, so of course, an
> upgrade to Puppet is available.
>
> Ideally, it would have been better if v3 ha
Hello all,
I have the current configuration with puppet 2.7.9:
in modules/app/manifests
init.pp
import "*"
facesquare.pp
class app::facesquare {
...
}
twitstagram.pp
class app::twitstagram {
}
in node file
include app::facesquare
include app::twitstagram
When i run
Hi,
I am new to this.
Can someone lead me to a step by step configuration for dashboard. The ones
on the web is too confusing.
Like, it says we need to have an entry for puppet-dashboard in /etc/passwd.
So how does that look like?
Rajeev
--
You received this message because you are subscri
Matthaus Owens writes:
> In Puppet 3.x, allow directives are limited to hostnames, if you wish
> to allow an ip address, the allow_ip directive should be used. This
> was in response to CVE-2012-3408
> (http://puppetlabs.com/security/cve/cve-2012-3408/).
Thank you for your help. Looks like somet
On Mon, Oct 01, 2012 at 04:11:06PM -0400, Thomas Linkin wrote:
> There is no way in the resource declaration for 'file' to stop it from
> ensuring your symlink is made into a directory. That is because this
> is the state you're asking to have ensured when you compile that
> resource into a catalog
On Wednesday, October 3, 2012 1:53:13 PM UTC+2, Arnaud Gomes-do-Vale wrote:
>
> Thank you for your help. Looks like something is still broken.
>
> I replaced all "allow" directoves in fileserver.conf with allow_ip; I
> still had the same errors:
>
I ran into the same issue yesterday, which is c
Hello,
In Puppet 3 Puppet does its absolute best to make sure $HOME, $USER and
$LOGNAME environment variables are unset and nowhere to be found. I realise
this change was necessary because it caused some weird start-up issues with
Puppet but this also killed our RabbitMQ module.
RabbitMQ is wr
Hi,
On Wed, 2012-10-03 at 05:45 -0700, Daniele Sluijters wrote:
> Hello,
>
>
> In Puppet 3 Puppet does its absolute best to make sure $HOME, $USER
> and $LOGNAME environment variables are unset and nowhere to be found.
> I realise this change was necessary because it caused some weird
> start-up
Hi,
Sorry, I got confused between two things. It's not the actual Exec type.
it's when a provider executes a command that the environment cannot be set.
--
Daniele Sluijters
On Wednesday, 3 October 2012 15:00:54 UTC+2, Stephen Gran wrote:
>
> Hi,
>
> On Wed, 2012-10-03 at 05:45 -0700, Daniele
On Tuesday, October 2, 2012 7:36:22 PM UTC-5, Michael Stanhke wrote:
>
> On Tue, Oct 2, 2012 at 1:30 PM, Jeff McCune
> >
> wrote:
> > On Tue, Oct 2, 2012 at 1:17 PM, Robert Rothenberg
> > >
> wrote:
> >> I am using CentOS 6 with the PuppetLabs yum repo from
> >> http://yum.puppetlabs.com
Running a Puppetmaster on a Red Hat Enterprise Linux 5 server using the
Stealthy Monkeys RPM's for Passenger.
First the setup:
yum wants to update from :
puppet.noarch 2.7.19-1.el5 installed
puppet-server.noarch 2.7.19-1.el5 installed
r
Hi Stephen,
You are right about the exec command being able to receive an environment
hash. This, however, does not solve our problem, because this is not
possible when creating a new Puppet Type and Provider. In the provider
commands are created using the "commands => 'system_command' " class
> Ubuntu released a backport of 0.3.0 into lucid-backports which will
> resolve the issue for you here:
> http://packages.ubuntu.com/lucid-backports/libaugeas-ruby
Unfortunately upgrading the package did not solve the problem. Also the
error message doesn't match the bug report.
--trace gives
After upgrading to Puppet 3.0.0 it seems that puppet doc is no longer
producing documentation from my modules / manifests.
I have a setup with two environments in
/etc/puppet/environments/[production, testing], and I'm running the
following command to generate the docs:
puppet doc --all --mode
Within a provider, I think you can use this syntax:
has_command(:port, "/opt/local/bin/port") do
environment :HOME => "/opt/local"
end
http://www.mail-archive.com/puppet-dev@googlegroups.com/msg17373.html
On Wednesday, October 3, 2012 9:11:03 AM UTC-4, jwkoelewijn wrote:
> Hi Stephen,
>
> Y
I usually explicitly set the $puppetversion in my manifest for my environment.
Furthermore, I have my own mirror copied from puppet labs repo and install it
from that location instead. That way, I have control of what I push out and
only update when I know that the new version is sound.
So I am
On Tuesday, October 2, 2012 3:36:10 PM UTC-5, am-aaron wrote:
>
> hello:
>
> i currently am using Puppet to run some commands in a sequence. there are
> two sequences of exec resources. we found that we cannot use require =>
> Exec and it does not work at all as expected. here is some sample co
On Tuesday, October 2, 2012 1:03:23 PM UTC-5, Darvin Denmian wrote:
>
> Hi,
>
> Is it possible to set the value of a variable from the content of
> a text file?
>
>
If the target file is on the master, then you can load its entire contents
into a variable via the file() function that David su
- Original Message -
> From: "Rilindo Foster"
> To: puppet-users@googlegroups.com
> Sent: Wednesday, October 3, 2012 3:02:58 PM
> Subject: Re: [Puppet Users] Puppet 2.7 v 3.0 in the PuppetLabs yum repo
>
> I usually explicitly set the $puppetversion in my manifest for my
> environment.
On Tuesday, October 2, 2012 11:47:43 AM UTC-5, ureal frank wrote:
>
> Hi,
>
> I have a service /etc/init.d/a that spawns multiple daemons b and c.
>
> This manifest does not make much sense to me but… any tip?
>
> service { 'a':
> ensure => running,
> pattern => ["/usr/local/bin/b", "/usr/loc
On 3 October 2012 15:02, Rilindo Foster wrote:
> I usually explicitly set the $puppetversion in my manifest for my
> environment. Furthermore, I have my own mirror copied from puppet labs repo
> and install it from that location instead. That way, I have control of what
> I push out and only upda
I'm sending this email to start this thread, feel free to comment as
appropriate. I'm going to assume that it's going to take a while for most
people to actually realise that the puppet update may be giving them some
issues, so, comments and suggestion please!
--
You received this message because
Thanks for your reply. I'll try it right now.
Regards.
On Wed, Oct 3, 2012 at 11:18 AM, jcbollinger wrote:
>
>
> On Tuesday, October 2, 2012 1:03:23 PM UTC-5, Darvin Denmian wrote:
>>
>> Hi,
>>
>> Is it possible to set the value of a variable from the content of
>> a text file?
>>
>
> If the tar
Hi, I'm trying to configure distributed Puppet with uWSGI server
application without success.
I'm configuring NGINX in a similar way that with Unicorn or Passenger and
also inspiring in this blog entry:
http://www.prontab.com/2011/01/this-page-should-outline-how-to-set-up.html
¿Anybody has exp
On Tuesday, October 2, 2012 9:35:13 AM UTC-5, Mike wrote:
>
> Hi,
>
> I've have some problems with my puppet configuration, I'm managing several
> Ubuntu and OpenBSD hosts.
>
> I sometimes get on OpenBSD hosts (5.0 is OpenBSD release):
> info: Retrieving plugin
> err: Could not retrieve catalog
On Wednesday, October 3, 2012 9:37:01 AM UTC-5, Mister Guru wrote:
>
> I'm sending this email to start this thread, feel free to comment as
> appropriate. I'm going to assume that it's going to take a while for most
> people to actually realise that the puppet update may be giving them some
>
I agree that folks should manage their repos, but I wanted to throw in
a couple of thoughts:
* The package name hacks (eg puppet3) are usually done by
distributions to allow multiple versions of software to co-exist.
* Take a look at the yum versionlock plugin. My life has been much
simpler sinc
On 3 October 2012 15:51, Chad Huneycutt wrote:
> I agree that folks should manage their repos, but I wanted to throw in
> a couple of thoughts:
>
> * The package name hacks (eg puppet3) are usually done by
> distributions to allow multiple versions of software to co-exist.
>
I think that we have
For yum-based updates, take a look at the yum versionlock plugin.
Works great here, although you have to specify the entire package name
that you want (I don't think just specifying puppet-2.7 will work).
debian-based distros support pinning, but haven't gotten that going yet.
- Chad
On Wed, Oct
It might be worth an enhancement request to have Package: ensure => version
call yum versionlock or zypper add-lock if they are present
On Oct 3, 2012 10:55 AM, "Mister Guru" wrote:
>
>
> On 3 October 2012 15:51, Chad Huneycutt wrote:
>
>> I agree that folks should manage their repos, but I want
On Tuesday, October 2, 2012 10:10:13 AM UTC-5, Guzmán Brasó wrote:
>
> I'm in no way a puppet guru but rewritting it didnt work? from a logic
> point of view this should work:
>
>
> class
> $baseurl,
> $webapp_context_path = ''
> ) {
> if ($webapp_context_path == '') {
> #
Hi.
I would like to setup my manifests, so that variable data is gathered
from hiera, if it's available there, and if not, then to fallback on
some predefined value...
Something like this:
$my_var = hiera('myvar') || 'base_value'
So if there is no myvar in hiera data, that manifest falls back t
On Wednesday, October 3, 2012 10:03:17 AM UTC-5, Jakov Sosic wrote:
>
> Hi.
>
> I would like to setup my manifests, so that variable data is gathered
> from hiera, if it's available there, and if not, then to fallback on
> some predefined value...
>
> Something like this:
>
> $my_var = hiera
On Wed, Oct 3, 2012 at 11:02 AM, Jakov Sosic wrote:
> Hi.
>
> I would like to setup my manifests, so that variable data is gathered
> from hiera, if it's available there, and if not, then to fallback on
> some predefined value...
The "right" thing is to put that default somewhere in hiera. What
Hello,
Is there any way to test if a resources has been exported (without
realising it)? The reason being - I don't want to realise a nagios_service
that's associated with a nagios_hostgroup until at least one nagios_host
belonging to that hostgroup exists (otherwise nagios will refuse to star
Take a look at Example42's Next Gen modules on github. They all do what you're
asking about and a bit more
There is a routine defined within the puppi module, that the rest of the
modules use to lookup variable values. Defaults are assigned in params.pp which
the main class inherits and they a
On Wednesday, October 3, 2012 3:51:28 PM UTC+1, Chad Huneycutt wrote:
>
> I agree that folks should manage their repos, but I wanted to throw in
> a couple of thoughts:
>
> * The package name hacks (eg puppet3) are usually done by
> distributions to allow multiple versions of software to co-ex
BTW, I have reported this at https://projects.puppetlabs.com/issues/16729
--
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/-/0mmf1DmfyDIJ.
To post to this grou
At Rapid7 in Boston we are searching for another Linux System Admin with a
knowledge of Puppet. We are growing and have rather large infrastructure
buildouts ready to go. Any interest? Contact me via www.rapid7.com
Jim
--
You received this message because you are subscribed to the Google Grou
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Robert Rothenberg wrote:
> BTW, I have reported this at https://projects.puppetlabs.com/issues/16729
>
So taking my Puppet Labs hat off and speaking purely as a sysadmin ... I
guess I have some commentary on what I would consider best practice.
1. I
Hi,
I have upgraded my puppet master to 2.7 with autosign enabled, it works
great, the only issue I have it that when I re-image any client machine
(blow away /var/lib/puppet ) folder and try to run puppet again, it fails
to authenticate.
The solution will be to (revoke + clean) the certificat
This is normal.
New system will always generate a new cert.
You only need to delete /var/lib/puppet/ssl on the client and remove the cert
on the master "puppet cert clean "
There has been some discussions on ways to automate this. Should be able to
find them in the archives.
Steven
Date: Wed,
This update will serve to educate them that using ensure => latest for
critical packages like this in a production environment is not a good idea.
:)
Jeffrey.
On Wed, Oct 3, 2012 at 9:36 AM, Mister Guru wrote:
> I'm sending this email to start this thread, feel free to comment as
> appropriate
On Wed, Oct 3, 2012 at 8:32 AM, Robert Rothenberg wrote:
> BTW, I have reported this at https://projects.puppetlabs.com/issues/16729
Thank you for filing this ticket. We're having a hard time
understanding how many people were actually negatively affected by
this change. If you were affected by
+1
On Wed, Oct 3, 2012 at 9:02 AM, Rilindo Foster wrote:
> I usually explicitly set the $puppetversion in my manifest for my
> environment. Furthermore, I have my own mirror copied from puppet labs repo
> and install it from that location instead. That way, I have control of what
> I push out an
It does take some reading.
The main doc page[1] has information plus several resources[2] here and
there.
Follow the instructions here[3] to install the puppetlabs repo so you can
use yum.
When you do "yum install puppet-dashboard", it creates the unix account. Do
"grep puppet /etc/passwd" and
Ok, I was missing the following line in the nginx location statement:
uwsgi_modifier1 7;
Now seems that works correctly (and very fast). When thoroughly adjusted I
will publish the complete configuration. Thanks again.
El miércoles, 3 de octubre de 2012 16:40:28 UTC+2, Juan José Presa Rodal
e
On Tue, Oct 2, 2012 at 2:35 PM, James Turnbull wrote:
> Hi all
>
> I am thrilled to announce our new Community Manager: Dawn Foster. Dawn
> joins us from Intel where she managed several open source communities
> (I'm going to let her introduce herself in more detail in a later email).
>
Thanks!
If you really want control over this you should build your own local repo
mirror. That way you can be absolutely certain of what your systems will
have access to. RHEL and friends come with all the tools to do this so it's
not a major undertaking.
On Oct 3, 2012 7:37 AM, "Mister Guru" wrote:
> I'
My $0.02:
I appended the following to /etc/yum.conf (RHEL 5 server)
exclude=puppet puppet-server ruby*
- Original Message -
I'm sending this email to start this thread, feel free to comment as
appropriate. I'm going to assume that it's going to take a while for most
people to actuall
Good day
I seem to have a problem whereby, I get the following message when I do
a puppet run.
Warning: Unable to fetch my node definition, but the agent run will
continue:
Warning: Could not intern from pson: source '"#in PSON!
I did google and I came across this for the second error messa
full disclosure: I don't use the puppetlabs repos. Below are just some
observations and concerns I wanted to voice.
On Tue, Oct 2, 2012 at 5:36 PM, Michael Stahnke wrote:
> On Tue, Oct 2, 2012 at 1:30 PM, Jeff McCune wrote:
> > On Tue, Oct 2, 2012 at 1:17 PM, Robert Rothenberg
> wrote:
> >> I a
Same issue here. I'd love to get some info on this.
On Wednesday, October 3, 2012 2:26:42 AM UTC-7, Jonathan Gazeley wrote:
>
> Yesterday my puppetmaster and nodes got upgraded to puppet-3.0.0.
>
> Since then, all puppet runs have been failing with this error:
>
> Error: Could not retrieve catal
I think a bit of learning, and burned fingers happened today - I'm
searching my manifests for ensure => latest and getting rid of it!
On 3 October 2012 19:14, Dan White wrote:
> My $0.02:
>
> I appended the following to /etc/yum.conf (RHEL 5 server)
>
> exclude=puppet puppet-server ruby*
>
> -
Comments inline.
On Wednesday, October 3, 2012 1:55:35 PM UTC-5, Joehillen wrote:
>
> Same issue here. I'd love to get some info on this.
>
> On Wednesday, October 3, 2012 2:26:42 AM UTC-7, Jonathan Gazeley wrote:
>>
>> Yesterday my puppetmaster and nodes got upgraded to puppet-3.0.0.
>>
>> Since
As Steven said, it is normal for a puppet-master not to allow a re-imaged
machine until the certificate is re-generated. I will point out that depending
on the your environment, it may be a security risk to any client to
authenticate against the puppet-master.
For my environment, I explicitly
On Wednesday, October 3, 2012 9:24:01 AM UTC-5, R.I. Pienaar wrote:
>
>
>
> - Original Message -
> > From: "Rilindo Foster" >
> > To: puppet...@googlegroups.com
> > Sent: Wednesday, October 3, 2012 3:02:58 PM
> > Subject: Re: [Puppet Users] Puppet 2.7 v 3.0 in the PuppetLabs yum repo
- Original Message -
> From: "jcbollinger"
> To: puppet-users@googlegroups.com
> Sent: Wednesday, October 3, 2012 8:20:38 PM
> Subject: Re: [Puppet Users] Puppet 2.7 v 3.0 in the PuppetLabs yum repo
>
>
>
> On Wednesday, October 3, 2012 9:24:01 AM UTC-5, R.I. Pienaar wrote:
>
>
>
>
- Original Message -
> From: "R.I.Pienaar"
> To: puppet-users@googlegroups.com
> Sent: Wednesday, October 3, 2012 8:25:52 PM
> Subject: Re: [Puppet Users] Puppet 2.7 v 3.0 in the PuppetLabs yum repo
>
>
>
> - Original Message -
> > From: "jcbollinger"
> > To: puppet-users@goo
How about switching to the gem version of passenger;
gem install passenger
--
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/-/A8FERt3aTbIJ.
To post to this gro
On Wednesday, October 3, 2012 12:58:02 PM UTC-5, Dawn Foster wrote:
>
>
> On Tue, Oct 2, 2012 at 2:35 PM, James Turnbull
>
> > wrote:
>
>> Hi all
>>
>> I am thrilled to announce our new Community Manager: Dawn Foster. Dawn
>> joins us from Intel where she managed several open source communities
btw, I'm running Ubuntu 10.04.1
--
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 mor
I agree, I learnt my lesson, but thankfully, it was in my testing
environment - I've been writing shitty basic puppet code, and I'd just
built a new puppet master, which was behaving very odd! That's when I
noticed it was V3 - Good job I don;t run updates in my master - It also hit
me that I don't
On 2 October 2012 22:35, James Turnbull wrote:
> Hi all
>
> I am thrilled to announce our new Community Manager: Dawn Foster. Dawn
> joins us from Intel where she managed several open source communities
> (I'm going to let her introduce herself in more detail in a later email).
>
> Dawn will init
On Wednesday, October 3, 2012 4:40:59 AM UTC-5, Mister Guru wrote:
>
>
> On 3 Oct 2012, at 03:35, Ryan Coleman wrote:
>
> > Hello,
> >
> > If you weren't at PuppetConf or didn't catch my talk, here's a quick
> > recap. I'm product owner for the Puppet Forge team which formed in
> > July with
All-
We're currently using puppet 2.7.14 on master and all clients.
I thought I understood why 'anchor' is part of stdlib, but after
re-reading both
http://projects.puppetlabs.com/projects/puppet/wiki/Anchor_Pattern
and
http://projects.puppetlabs.com/issues/8040
yesterday in
Hi JM, this sounds like a real problem that was probably introduced with
our code to start warning on certificates close to their expiration dates.
(#7962)
https://github.com/puppetlabs/puppet/commit/12d81c7ef97167f1831143ff0037ae9a3970960d
I created a ticket for this
issue: https://projects.
Thanks for reporting this, we're looking into it. I've made a ticket for
your issue: https://projects.puppetlabs.com/issues/16770
If you can do so, could you please run the puppet master with the '--trace'
option ( either on the command line or with a `ARGV << '--trace'` line in
config.ru if y
On Wed, Oct 3, 2012 at 2:57 PM, Tim Mooney wrote:
>
> All-
>
> We're currently using puppet 2.7.14 on master and all clients.
>
> I thought I understood why 'anchor' is part of stdlib, but after
> re-reading both
>
> http://projects.puppetlabs.**com/projects/puppet/wiki/**
> Anchor_Patter
Thanks Guzman, as John pointed out that won't work (I think this is because
Puppet's language is declarative, even if it resembles procedural language
in many ways).
On Wednesday, October 3, 2012 1:10:13 AM UTC+10, Guzmán Brasó wrote:
>
> I'm in no way a puppet guru but rewritting it didnt w
Hi Paul, I created a ticket to track this issue, thanks for posting the
trace output and manifest.
http://projects.puppetlabs.com/issues/16772
-=Eric
On Wednesday, October 3, 2012 6:27:41 AM UTC-7, Paul Tötterman wrote:
>
> > Ubuntu released a backport of 0.3.0 into lucid-backports which will
Thanks John. At least I know there is no way to improve my code.
I prefer to try to keep logic in the .pp files and out of the templates,
just to make it easier to find.
On Thursday, October 4, 2012 1:02:35 AM UTC+10, jcbollinger wrote:
>
>
>
> On Tuesday, October 2, 2012 10:10:13 AM UTC-5, Guzmá
Puppet 3 docs are now posted at
http://docs.puppetlabs.com/puppet/3/reference/ . We apologize for the
delay! This update adds release notes and a Puppet 3 language reference
with all of the relevant updated. Next on deck is improved Hiera
documentation.
--
You received this message because y
On Oct 1, 2012, at 5:00 PM, Lunixer wrote:
> I'll try strace instead of tcpdump, being that this is not a TCP
> communication problem over the wire but rather a file or directory access
> problem.
Um, no. Puppet client talks to the server over the network, even on the same
host. You really sho
Thanks LL.
On Wednesday, October 3, 2012 10:23:07 PM UTC+5:30, Lunixer wrote:
>
> It does take some reading.
>
> The main doc page[1] has information plus several resources[2] here and
> there.
> Follow the instructions here[3] to install the puppetlabs repo so you can
> use yum.
> When you do
The doc says:
If you haven't installed Dashboard from a package, you must create a user
and group for Dashboard and chown all its files to be owned by that user
and group.
So, how should the entry look like:
Is there something specific?
Regards,
Rajeev
On Thursday, October 4, 2012 11:02:29
I'm running puppet on CentOS 6.3 x86_64:
- facter.i386 1:1.6.12-2.el6@puppet
- puppet.noarch 2.7.19-1.el6 @puppet
- ruby-shadow.x86_641.4.1-13.el6 @puppet
Puppetmaster:
- facter.x86_64 1:1.6.12-2.el6@puppet
- hiera.noarch
82 matches
Mail list logo
