Wow, it took quite a while for my post to reach this group. No idea why, is
it moderated?
Anyway, this problem seems to also happen with agents running Puppet 2.7.6,
although apparently less frequently. I'm almost positive it must have
something to do with a module but I wouldn't know how or wh
In my 1st post, the versions of the problematic configurations are
mentioned.
During the PE upgrade, I also created new configfiles without 'listen =
true'. This is what probably fixed it for me, 'listen' is specifically
mentioned in the bugreport.
Ger.
--
You received this message because y
Hello,
This is my attempt to create puppet RPM's and SRPM's for AIX 6.1:
http://t3chnick.blogspot.com/2012/01/32-bit-puppet-rpms-srpms-for-aix-howto.html
Thanks,
Nick
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, sen
Hi, I'm new to Puppet so may be going about this completely the wrong
way, or perhaps it is an selinux problem rather than a Puppet problem.
I have a problem copying a file and changing the seltype. I don't
think it is Nagios specific. Code is something like:
file {
'/usr/sbin/nrpe':
sou
On Wednesday, January 4, 2012 3:06:27 PM UTC+1, Gonzalo wrote:
>
>
> Otherwise, group membership is managed as a property of Users, ergo
>> you cannot manage it (directly) if you do not manage the users in
>> question. Your only options in that case are an Exec or a custom
>> Group provider.
>>
>
I think I have the same problem onUbuntu 10.04.3 and 2.7.9, as I just
posted to this group. The symptoms seem identical and in ps -ef I see that
the puppet agent spawned an sh process that became defunct. This seems to
be the cause for the hanging agent, but what causes that zombie process I
ha
Hi,
On a node running Puppet 2.7.9 from apt.puppetlabs.com, using Ubuntu
10.04.3 the agent hangs after a few hours of operation. I have to kill -9
it, nothing else helps. Obviously, this is unfortunate.
Looking at ps -ef I see this:
root 4842 4594 0 Jan04 pts/000:00:55 /usr/bin/rub
On Jan 5, 6:19 pm, Adam Gibbins wrote:
> The recommendation for mirroring debian repositories is generally to use
> something like apt-mirror or apt-cacher-ng. Is there a reason you can't do
> this?
Our local mirror server is running CentOS, so I didn't think apt-
mirror was an option, but it l
On Jan 5, 2012, at 4:53 PM, Michael Stahnke wrote:
> You can install rpmdev-tools and run rpmdev-setuptree and it will
Yes of course but I wasn't documenting that here.
> The http://centos.karan.org/el5/ruby187/ are basically a drop-in
> replacement for how the EL5 ruby stack worked, just upgrad
The recommendation for mirroring debian repositories is generally to use
something like apt-mirror or apt-cacher-ng. Is there a reason you can't do
this?
These work by checking the index (e.g.
http://apt.puppetlabs.com/ubuntu/dists/lucid/main/binary-amd64/Packages)
and pulling the packages. You
I am wanting to set up a local mirror of apt.puppetlabs.com, and am a
bit confused by the layout as well as the announcement that was made
in this thread:
http://groups.google.com/group/puppet-users/browse_thread/thread/0786824ea9531fe3/f53c9006843ab8dc
I'm not sure exactly what I should be pulli
Jo, thanks for this. I do most of the packaging for Puppet Labs (and
quite a bit of the ruby stuff in EPEL). I have a few comments in
line.I'd love to have this on our wiki too, so feel free to post
there as well.
One more thing to keep in mind is that EL5 only has about 2 years of
life left
Ah interesting !
I'll give it a try and keep you updated.
--
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/-/448pL5sCL4MJ.
To post to this group, send email to
We're starting again the 18th of Jan.We skipped December due to
the Nov stuff not finalizing until the first week of December,
holidays, time off work, etc.
Mike
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send
Yes, I'm aware. Given the Xmas holidays and all, I was attempting a more
polite version of "It's been 5 weeks since the last RC release, when do you
think we'll resume the standard 4-week cycle?"
I'm not trying to complain, just to understand the expected timeline.
On Jan 5, 2012, at 1:16 PM,
I've done some work in this area.
sudo puppetd --server puppet.mydomain.com --certname
dbs02.sfo.mydomain.com -t
::certname is available as the fact ::clientcert in the Puppet run. I
use ::clientcert instead of ::fdqn in these cases and then use this in
templates as a replacement for hostname, <%
Jo,
You can find the description of Puppet's release process here:
http://groups.google.com/group/puppet-users/browse_thread/thread/3d703849246bd43f/c98d096d51ed221e
-Eric
--
Eric Shamow
Professional Services
http://puppetlabs.com/
(c)631.871.6441
On Thursday, January 5, 2012 at 3:54 PM, J
I've seen quite a few bug reports fly by and comments from puppet labs saying
"will be fixed in next version". Do we have an eta just yet for 2.7.10?
Obviously, "when it's ready applies" -- I'm just curious if you are in
shake-down for 2.7.10 already or if you know right now that it's more than
On Jan 5, 2012, at 7:42 AM, ollies...@googlemail.com wrote:
> $command = "( /apps/path/scripts/install.sh || true ) && touch /etc/
> puppet/puppet.script.done"
>
>exec { install:
>command => "$command",
Remember that putting something in double quotes is a request to have
It would be helpful to note what versions are involved.
PE 2.0 ships with Puppet 2.7.6.
Puppet 2.7.9 you said you had an issue. I'd like to find out more.
Another option to work-around an issue like this might be to run
puppet from cron rather than as a daemon.
--
You received this message be
On Thu, Jan 5, 2012 at 9:12 AM, Aaron Grewell wrote:
> That's interesting - PE isn't affected?
>
> On Thu, Jan 5, 2012 at 12:26 AM, Ger Apeldoorn wrote:
>> Hi Radek,
>>
>> It's a bug that acts up on a specific kernel; see:
>> http://projects.puppetlabs.com/issues/10819
>>
>> I've upgraded to Pupp
It's been a while since you asked this, but I didn't see a followup;
forgive the noise if you've already got an answer.
Wolf Noble posted a solution to this problem
in September that I've been holding onto because I think it's
elegant:
* Wolf Noble [2011/09/01 18:45]:
> Here's what I've bee
Hi everyone,
I have a quick question for everybody, does the class inheritance work for
realizing ressource?
Because I have the following class:
# user_system.pp
#
# Realize the system users
class user::user_system inherits user::virtual {
# Realize system members
Group <| tag
Hi everyone,
Do you if there a way to display a certain ressource attribut.
For instance, I want to display the 'require' of the User['test']
Regards,
JM
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to
That's interesting - PE isn't affected?
On Thu, Jan 5, 2012 at 12:26 AM, Ger Apeldoorn wrote:
> Hi Radek,
>
> It's a bug that acts up on a specific kernel; see:
> http://projects.puppetlabs.com/issues/10819
>
> I've upgraded to Puppet Enterprise and do not have this issue anymore.
>
> Regards,
>
On 5 Jan 2012, at 16:54, krish wrote:
>
> Why do you have to do a || with true here?
> afaik, /apps/path/scripts/install.sh && touch
> /etc/puppet/puppet.script.done should do.. or even better use a ;
> instead of &&
>
If install.sh fails then && will not allow touch to run, so I would hav
On Jan 5, 3:54 pm, krish wrote:
> On Thu, Jan 5, 2012 at 9:12 PM, ollies...@googlemail.com
>
> wrote:
> > Hello,
>
> > I have this stupid exec on a bash script but bear with me. Works OK on
> > an ancient 0.xx Puppet setup. But not on 2.7.9.
>
> > $command = "( /apps/path/scripts/install.sh ||
Hi,
i think you can solve your Problem by adding
provider => shell,
http://docs.puppetlabs.com/references/stable/type.html#exec
rgds Florian koch
On Jan 5, 4:54 pm, krish wrote:
> On Thu, Jan 5, 2012 at 9:12 PM, ollies...@googlemail.com
>
> wrote:
> > Hello,
>
> > I have this stupid exec on
On Thu, Jan 5, 2012 at 9:12 PM, ollies...@googlemail.com
wrote:
> Hello,
>
> I have this stupid exec on a bash script but bear with me. Works OK on
> an ancient 0.xx Puppet setup. But not on 2.7.9.
>
> $command = "( /apps/path/scripts/install.sh || true ) && touch /etc/
> puppet/puppet.script.don
Hi,
the original problem is interesting. My guess is that Solaris puppet
2.7.x no longer runs execs through a shell that supports subshelling by
paranthesis. Or somesuch. I don't think you need it, though.
On 01/05/2012 04:42 PM, ollies...@googlemail.com wrote:
> $command = "( /apps/path/scripts/
Hello,
I have this stupid exec on a bash script but bear with me. Works OK on
an ancient 0.xx Puppet setup. But not on 2.7.9.
$command = "( /apps/path/scripts/install.sh || true ) && touch /etc/
puppet/puppet.script.done"
exec { install:
command => "$command",
Geppetto and puppet-lint are two useful tools for checking for problems.
Hope that helps.
Regards
- henrik
On 2012-03-01 18:15, Trevor Vaughan wrote:
Any takers?
On Wed, Dec 28, 2011 at 9:19 AM, Trevor Vaughan wrote:
I think I've found all of the cases, but I'd like a definitive way to
be su
On 01/05/2012 02:45 PM, Walter Heck wrote:
> I was afraid this was going to be the only solution. I guess we could
> really do with more sane handling of arrays in puppet. This is a
> workaround to make a workaround work..
Humm, if you can find a sensible way to hash your data, you might be
able t
I was afraid this was going to be the only solution. I guess we could
really do with more sane handling of arrays in puppet. This is a
workaround to make a workaround work..
On Thu, Jan 5, 2012 at 14:41, Felix Frank
wrote:
> On 01/05/2012 02:36 PM, Walter Heck wrote:
>> That's the fun part: the $
On 01/05/2012 02:36 PM, Walter Heck wrote:
> That's the fun part: the $distribution parameter that the define
> recieves is different the second time, so it would create the files in
> a different location. Normally we could solve this by making the $name
> unique, but since that is what is used to
That's the fun part: the $distribution parameter that the define
recieves is different the second time, so it would create the files in
a different location. Normally we could solve this by making the $name
unique, but since that is what is used to make the array magic happen,
I cannot go and make
Hi,
On 01/05/2012 01:51 PM, Walter Heck wrote:
> until I needed to loop through a second instance of an array in
> another call to that define that just so happens to have the same data
> in it. Now I get the following error:
this is a cute problem description indeed ;-)
What problem are you try
On 01/03/2012 06:15 PM, Trevor Vaughan wrote:
> Any takers?
Please elaborate on the question.
--
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, se
I did not mean to hijack the thread.
I thought this information would be helpful to the original poster.
“Sometimes I think the surest sign that intelligent life exists elsewhere in
the universe is that none of it has tried to contact us.”
Bill Waterson (Calvin & Hobbes)
- Felix Frank wrote
Hello,
I have a define in which I need to loop through an array. That worked
well, until I needed to loop through a second instance of an array in
another call to that define that just so happens to have the same data
in it. Now I get the following error:
err: Could not retrieve catalog from remo
Whoo, hijack :-)
On 01/05/2012 03:09 AM, Dan White wrote:
> Assume I move from
>
> package { "foo": ensure => "1.2-0", }
>
> to
>
> package { "foo": ensure => "1.5-0", }
>
> and then find that the update breaks other things. Would changing the
> catalog back remove the newer version and re
See this bug: http://projects.puppetlabs.com/issues/10819
--
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/-/fGG-FC53rhIJ.
To post to this group, send email to
Hi Radek,
It's a bug that acts up on a specific kernel; see:
http://projects.puppetlabs.com/issues/10819
I've upgraded to Puppet Enterprise and do not have this issue anymore.
Regards,
Ger.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To
43 matches
Mail list logo
