Hello everyone
I looked online, but didn't see any solution to the problem of
/var/lib/puppet/clientbucket filling up.
After a while that directory is getting very big, 3-4gigs. I have to shutdown
puppet and remove everything.
Is there a way to either limit the size of this directory, or be
Hi,
On Wed, Oct 27, 2010 at 11:17 AM, sanjiv.singh
wrote:
>
> 1) What is exactly problem with puppetrun ?
> 2) why is ruppetrun not able to connect to client at port 8139 ?
If this is on 2.6.x, then you need to modify auth.conf.
--
You received this message because you are subscribed to the
hi,
i m new for puppet and configured with LDAP.tring to push
configuration through puppetrun
and
done opening of port
8140 : on master
8139 : on client
on client with ...
$ iptables -I INPUT 1 -p tcp --dport 8139 -j ACCEPT
$ /etc/init.d/iptables save
$ /etc/init.d/iptables re
Hi James
Is there an ETA for the full release of 2.6.3?
For what it is worth, I have been running 2.6.3rc1 for almost 13 days on
Solaris 10 U8 & U9 as server and clients. Server is running passenger 2.2.14
with clients and servers weighing in at managing between 500 & 780 resources
depending on c
yes, that is the method I had in mind too :)
better be save then sorry
Thanks!
On Tue, Oct 26, 2010 at 4:50 PM, Patrick wrote:
> I love this package, but I had some conflicts with my existing puppetmaster
> configuration. This is what I did (probably very overkill) that fixed all
> the conflict
We have a lot of cruft in our ticket queues.
In the interests of bringing it back to a sane and manageable level, I'm
going to be aggressively closing bugs where we've sought info and not
received it, where the issue appears obsolete, etc. I'm not planning on
blindly cutting a swathe through the
Mathias - The package you mentioned (puppetmaster-passenger) worked
perfectly for me on the first try. That saved me a ton of time.
Thanks!
On Oct 26, 1:38 pm, Mathias Gug wrote:
> Hi,
>
> Excerpts from Taylor Leese's message of Tue Oct 26 16:31:04 -0400 2010:
>
>
>
> > @Ohad - I'm actually using
I love this package, but I had some conflicts with my existing puppetmaster
configuration. This is what I did (probably very overkill) that fixed all the
conflicts. I haven't had this trouble with new servers. I've only had this
problem with servers that had puppet+passenger configured manual
Mathias,
if the none passenger version was install, what do one need to do to switch
?
apt-get remove and then apt-get install or will a apt-get-install replace
the current none
passenger version?
Thanks
On Tue, Oct 26, 2010 at 1:38 PM, Mathias Gug wrote:
> Hi,
>
> Excerpts from Taylor Leese's
Mathias - Really? That's awesome. I didn't realize that existed. I
will check it out. Thanks.
On Oct 26, 1:38 pm, Mathias Gug wrote:
> Hi,
>
> Excerpts from Taylor Leese's message of Tue Oct 26 16:31:04 -0400 2010:
>
>
>
> > @Ohad - I'm actually using Ubuntu Maverick.
>
> If you're using Ubuntu M
On Oct 26, 1:00 pm, Taylor Leese wrote:
> Patrick,
>
> Any idea if people are using versions > 2.2.5 in the wild
> successfully? I tried to revert back to 2.2.2 previously, but I
> received a number of compilation errors when running passenger-install-
> apache2-module so it seems like moving up m
Hi,
Excerpts from Taylor Leese's message of Tue Oct 26 16:31:04 -0400 2010:
>
> @Ohad - I'm actually using Ubuntu Maverick.
>
If you're using Ubuntu Maverick I'd highly recommend to use the
puppetmaster-passenger package. It will automatically install and setup
a puppet master running under apac
oops, sorry. Indeed. I typo that all the time, but fortunately we
don't have anything important in /var/lib/ssl here :(
On Tue, Oct 26, 2010 at 3:48 PM, Patrick wrote:
>
> On Oct 26, 2010, at 12:00 PM, Chad Huneycutt wrote:
>
> You need to delete the cert on the client. rm -rf /var/lib/ssl/*
>
@Patrick - Thanks. I will try a newer version of passenger later
tonight.
@Ohad - I'm actually using Ubuntu Maverick.
On Oct 26, 1:11 pm, Patrick wrote:
> On Oct 26, 2010, at 1:00 PM, Taylor Leese wrote:
>
> > Patrick,
>
> > Any idea if people are using versions > 2.2.5 in the wild
> > successfu
The documentation on the wiki for the development lifecycle process
has been updated in an effort to make it easier for people to get code
into Puppet. The goals were to make it correct and easy to follow, so
take a look and let us know if there's anything that could use
improvement.
http://proje
On Oct 26, 2010, at 1:00 PM, Taylor Leese wrote:
> Patrick,
>
> Any idea if people are using versions > 2.2.5 in the wild
> successfully? I tried to revert back to 2.2.2 previously, but I
> received a number of compilation errors when running passenger-install-
> apache2-module so it seems like
if you are on rhel5, you can use the following rpm -
http://theforeman.org/repo/el5/noarch/rubygem-passenger-2.2.2-1.noarch.rpm
Ohad
On Tue, Oct 26, 2010 at 10:00 PM, Taylor Leese wrote:
> Patrick,
>
> Any idea if people are using versions > 2.2.5 in the wild
> successfully? I tried to revert b
Patrick,
Any idea if people are using versions > 2.2.5 in the wild
successfully? I tried to revert back to 2.2.2 previously, but I
received a number of compilation errors when running passenger-install-
apache2-module so it seems like moving up may be my only option.
- Taylor
On Oct 26, 12:50 pm
Patrick,
Any idea if people are using versions > 2.2.5 in the wild
successfully? I tried to revert back to 2.2.2 previously, but I
received a number of compilation errors when running passenger-install-
apache2-module so it seems like moving up may be my only option.
- Taylor
On Oct 26, 12:50 pm
The reason I though it might be the problem is because a lot of people are
saying that they got that error after it worked for months. This says to me
that their might have been a change to something else that makes 2.2.5 stop
working.
On Oct 26, 2010, at 10:59 AM, Taylor Leese wrote:
> Pat
On Oct 26, 2010, at 12:00 PM, Chad Huneycutt wrote:
> You need to delete the cert on the client. rm -rf /var/lib/ssl/*
I'm not sure if this is the right answer, but I think you meant "rm -rf
/var/lib/puppet/ssl"
>
> On Tue, Oct 26, 2010 at 10:48 AM, sanjiv.singh
> wrote:
>>
>> hi ,
>> im f
Yes, that worked. Thank you very much! ;)
On 26 Okt., 18:33, Patrick wrote:
> On Oct 26, 2010, at 8:17 AM, Maciej Skrzetuski wrote:
>
>
>
>
>
>
>
>
>
> > Well if I do this:
>
> > fileserver.conf (default):
>
> > # Define a section 'files'
> > # Adapt the allow/deny settings to your needs. Order
>
You need to delete the cert on the client. rm -rf /var/lib/ssl/*
On Tue, Oct 26, 2010 at 10:48 AM, sanjiv.singh
wrote:
>
> hi ,
> im facing the problem , when tryied to run puppetd…..
>
> err: Could not request certificate: Retrieved certificate does not
> match private key; please remove cer
Hi. I know that puppet for windows is in its basic stages but I've
been screwing around with it. I can get facter working. However one
error that it spits out is that: "Could not retrieve puppetversion:
Cannot determine basic system flavour."
When I try to run puppet, I get an error saying "ruby:
Patrick,
I did run across that thread, but the GitHub site specifically says
2.2.5 is known to work (http://github.com/puppetlabs/puppet/tree/
master/ext/rack) which made me suspicious that it was my fault. At
this point I guess there is no harm in trying 2.2.11 (or whatever the
latest version is)
On Oct 25, 2010, at 12:50 PM, Taylor Leese wrote:
> Hi all,
>
> I'm new to Puppet and I'm trying to setup a puppet master and a client
> on Amazon EC2 using Passenger. I've gone through the steps described
> here (http://docs.puppetlabs.com/guides/passenger.html) and here
> (http://github.com/pu
You guys hijacked my thread. :-) Any idea about my passenger problems?
--
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-user
On Oct 25, 2010, at 7:45 PM, Daneil Goodman wrote:
> Hi all,
>
> I am trying to use @@sshkey{...} and Sshkey <<| |>> to share host keys
> between compute nodes. It does work! But there is a weird issue. The same
> host key entry of each node will add into ssh_known_host again after
> restarte
On Oct 26, 2010, at 8:17 AM, Maciej Skrzetuski wrote:
> Well if I do this:
>
> fileserver.conf (default):
>
> # Define a section 'files'
> # Adapt the allow/deny settings to your needs. Order
> # for allow/deny does not matter, allow always takes precedence
> # over deny
> # [files]
> # path /
hi ,
im facing the problem , when tryied to run puppetd…..
err: Could not request certificate: Retrieved certificate does not
match private key; please remove certificate from server and
regenerate it with the current key
and after that as per yr guide…
$ puppetca –clean app-1288002665
here ,
Hi all,
I am trying to use @@sshkey{...} and Sshkey <<| |>> to share host keys
between compute nodes. It does work! But there is a weird issue. The same
host key entry of each node will add into ssh_known_host again after
restarted puppet each time. I only need one entry for each node in
ssh_known
Hi all,
I am trying to use @@sshkey{...} and Sshkey <<| |>> to share host keys
between compute nodes. It does work! But there is a weird issue. The same
host key entry of each node will add into ssh_known_host again after
restarted puppet each time. I only need one entry for each node in
ssh_known
Thanks, John.
I just checked the contents of the files in /etc/yum.repos.d, but only
found [updates] in one file, updates.repo:
[11:26 r...@cab yum.repos.d]# grep updates /etc/yum.repos.d/*
/etc/yum.repos.d/updates.repo:[updates]
/etc/yum.repos.d/updates.repo:baseurl=http://mirror.linux.duke.edu/
Well if I do this:
fileserver.conf (default):
# Define a section 'files'
# Adapt the allow/deny settings to your needs. Order
# for allow/deny does not matter, allow always takes precedence
# over deny
# [files]
# path /var/lib/puppet/files
# allow *.example.com
# deny *.evil.example.com
# al
- "Joel Merrick" wrote:
> Hi Pupeteers!
>
> I have a few questions regarding workflow that I'd appreciate insight
> from you guys on..
>
> 1) How do people manage services that can't be affected all at once?
> For instance, we run a number of DNS caches behind load balancers at
> two diffe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hello,
at the moment I fight with puppetdoc and end in a ruby confusion.
To the problem:
> puppetdoc --debug --trace --mode rdoc --all manifests/site.pp
info: scanning: ["manifests/site.pp"]
/usr/lib/ruby/1.8/puppet/util/rdoc.rb:82:in `output_resou
On Oct 25, 10:04 am, Brad wrote:
> Hello,
>
> I'm currently running Puppet 0.25.5-1 on CentOS 5.5. Everything has
> been going swimmingly until a couple of weeks ago, when I began
> receiving errors on one of my nodes. The node in question is also my
> puppetmaster, but the errors seem client-
On Oct 25, 1:25 pm, Todd Zullinger wrote:
> Maciej Skrzetuski wrote:
> > Do you mean hosting your own yum repository in your own network?
> > That is not a bad idea but it would be easier to just copy the files
> > over to the puppets and then just rpm -ihv , wouldn't it?
>
> No, it wouldn't be.
On Oct 26, 2010, at 7:00 AM, Felix Frank wrote:
>>> I am getting the following error:
>>>
>>> What is the problem here? What is file_metadata? Is this folder
>>> suppose to exist on my master?
>>
>> I don't know what's wrong. That folder doesn't need to be created. It's
>> possible you have
>> I am getting the following error:
>>
>> What is the problem here? What is file_metadata? Is this folder
>> suppose to exist on my master?
>
> I don't know what's wrong. That folder doesn't need to be created. It's
> possible you have a permissions problem.
Right, good thinking. Make sure to
On Oct 26, 2010, at 3:03 AM, Maciej Skrzetuski wrote:
> Hello there,
>
> I am very new to puppet and tried to copy some files (namely /etc/
> puppet/manifests/files/websphermq/status.dat [on master] to /tmp/
> status.dat [on puppet]) from master to the puppets. My setup is as
> follows:
>
> Pup
Wow,
This has all been great information! Thanks to everyone who posted!
-a
On Oct 26, 12:38 am, Patrick wrote:
> On Oct 25, 2010, at 1:55 PM, donavan wrote:
>
> > On Oct 25, 11:13 am, "R.I.Pienaar" wrote:
> >> In this scenario puppetd will use the old catalog BUT it will still fetch
> >> fil
Joel Merrick writes:
> On Tue, Oct 26, 2010 at 11:35 AM, Daniel Pittman wrote:
>>
>> The other is to use puppet to perform the work, and to use the
>> PuppetCommander[3] mcollective plugin. This allows you to schedule puppet
>> runs from a central service.
>>
>> With this you can configure, for
On Tue, Oct 26, 2010 at 11:35 AM, Daniel Pittman wrote:
>
> The other is to use puppet to perform the work, and to use the
> PuppetCommander[3] mcollective plugin. This allows you to schedule puppet
> runs from a central service.
>
> With this you can configure, for example, concurrency per colle
Joel Merrick writes:
> I have a few questions regarding workflow that I'd appreciate insight from
> you guys on..
>
> 1) How do people manage services that can't be affected all at once?
> For instance, we run a number of DNS caches behind load balancers at
> two different sites and (not that I'd
Hi,
On Tue, Oct 26, 2010 at 3:21 PM, Joel Merrick wrote:
>
> 1) How do people manage services that can't be affected all at once?
> For instance, we run a number of DNS caches behind load balancers at
> two different sites and (not that I'd do this!) if for example I set
> bind to always be latest
Hello there,
I am very new to puppet and tried to copy some files (namely /etc/
puppet/manifests/files/websphermq/status.dat [on master] to /tmp/
status.dat [on puppet]) from master to the puppets. My setup is as
follows:
Puppet 0.25.5
fileserver.conf:
[webspheremq]
path /etc/puppet/manifests/fi
Hi Pupeteers!
I have a few questions regarding workflow that I'd appreciate insight
from you guys on..
1) How do people manage services that can't be affected all at once?
For instance, we run a number of DNS caches behind load balancers at
two different sites and (not that I'd do this!) if for e
Stupid me :-)
I was wondering for *years* why this user was not getting the right password...
--
Jean-Baptiste Quenot
--
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 unsubs
Your $6$s95t93Ou$FWCF9kHO4 isn't being evaluated as a variable is it?
Try enclose the password crypt in single quotes ''.
On Oct 26, 9:35 am, Jean-Baptiste Quenot wrote:
> Consider the following manifest snippet:
>
> user { "foo":
> ensure => present,
> managehome => true,
>
Consider the following manifest snippet:
user { "foo":
ensure => present,
managehome => true,
shell => "/bin/bash",
password =>
"$6$s95t93Ou$FWCF9kHO4/nH9hNpr5hKxrK85ufxx8jubu8EuRgCd602bC2ov3X6IKPgkupD3G3qs1QzpRitli696NoFioSPf/",
comment => "Foo Bar"
51 matches
Mail list logo
