.
His background, like mine, is mostly UNIX systems administration. He’s
responsible for the huge refactoring of the apache module a while back, and
is all over the popular puppetlabs modules we hope you’re all using.
Ashley Penney
This one is me. I’m “ashp” on IRC and hopefully I know many of
eam Puppet but it's still in
a PR. It should make developing providers (it didn't have one before)
significantly easier for the community.
We're still just a team of 3, so I'm afraid this is all we were able to get
done, but we'll continue working on bringing you
m/d/msgid/puppet-users/c1e2389f-2881-4b59-91b0-5ee3072b26cb%40googlegroups.com
> .
> For more options, visit https://groups.google.com/groups/opt_out.
>
--
Ashley Penney
ashley.pen...@puppetlabs.com
Module Engineer
*Join us at PuppetConf 2014, September 23-24 in San Francisco*
--
You received
Hi!
I'm afraid this was mostly my fault, we released a version of mcollective
without some needed metadata and recently changes made this more
problematic than it used to be. I've uploaded a new release so you should
be able to fix this with:
puppet module uninstall puppetlabs-mcollective
pup
and shout at ashp (or hunter) if you want anything module related
or just want to throw us your worst "I can't figure out how to.." problems.
Thanks,
--
Ashley Penney
ashley.pen...@puppetlabs.com
Module Engineer
*Join us at PuppetConf 2014, September 23-24 in San Francisco*
--
Yo
e 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://g
efore I start writing some beginner
provider/types documentation for the module team. MySQL has proven to be
an absolute nightmare to write these types for so I'm full of pain points
to touch on to make sure the rest of you have an easier time in the future.
--
Ashley Penney
ashley.pen...@pupp
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:/
t of:
$ irb
irb(main):002:0> require 'ipaddr'
=> true
irb(main):003:0> IPAddr.new
=> #
That's what I get for a plain call to IPAddr.new, I'm wondering what you're
getting.
--
Ashley Penney
ashley.pen...@puppetlabs.com
Module Engineer
*Join us at PuppetC
As one of the two new maintainers of all Puppetlabs modules I can tell you
for sure that our intent is to make sure everything in init.pp inherits out
of params.pp instead of declaring them directly in the main class, and if
you're kind enough and can throw a github issue up for any cases you notic
So uh, as you can see from the subject there's been a little bit of a gap
between the last email and this one. I got super sick and forgot to put it
together, so you have my apologies if you were paying attention!
Over the last two weeks we've continued to focus on the backlog of PRs as
well as w
You cannot use ruby code in Puppet directly, which is why this isn't
working for you.
To do this you would need to write a "Puppet Function" as documented at
http://docs.puppetlabs.com/guides/custom_functions.html. This would then
let you do something like:
if exists('/file') {
Functions always
On Fri, Aug 2, 2013 at 4:26 AM, Alex Harvey wrote:
> Hi all,
>
> I am going to have a meeting to sell the idea of retrofitting Puppet to a
> fleet of already-built legacy Unix systems to a skeptical management (as
> opposed to only using it to build new linux systems, where I don't need to
> sell
Hey guys,
https://github.com/puppetlabs/puppetlabs-ntp/pull/80 adds some fairly
significant changes and so I wanted to put it up for review early before
going any further.
The big change is that it gets rid of the distro specific templates in
favor of one more sophisticated template we can start
My apologizes to all the readers for not getting this out on Friday. It
was 100F in my basement and it felt like I was melting, I completely forgot
in my rush to escape the house and survive until today.
Three weeks into working on modules and we're making steady progress.
Things have slowed dow
On Sat, Jul 13, 2013 at 7:15 AM, Erik Dalén wrote:
> I've been missing a way to set which server(s) should be preferred. We
> generally include all our NTP servers in the config but prefer the one that
> is in the same site as the node in question.
>
> So for a machine in site1 it would look like:
On Sat, Jul 13, 2013 at 6:16 AM, Alessandro Franceschi wrote:
> I insist on the question since I've not had answers previously:
> Any hope the redesign of the PuppetLabs modules will consider the
> suggested standards discussed here:
> https://github.com/stdmod/puppet-modules/blob/master/Paramete
Hello!
Now that we're two weeks in it's time for another update on what's been
going on in the module team. We focused on puppetlabs-ntp and
puppetlabs-firewall as our two primary modules, but also merged in fixes to
passenger, rabbitmq, mysql, apt, and apache.
As a result of this work we've rel
On Thu, Jul 11, 2013 at 3:49 PM, Matthew Burgess <
matthew.2.burg...@gmail.com> wrote:
> On 11 July 2013 20:28, Dan White wrote:
>
>> Excellent. I will see what I can do to contribute a run-it-by-cron
>> option to the module, since I already do that.
>>
>> As far as the large time differences, t
On Thu, Jul 11, 2013 at 10:41 AM, jcbollinger wrote:
>
> Currently, users have the alternative of specifying their own custom
> template instead of one of those packaged with the module. If the proposed
> change would remove that option, then it would be a significant step
> backward.
>
> If, how
On Wed, Jul 10, 2013 at 5:14 AM, Matthias Saou wrote:
>
> It looks really nice and clean! I would personally only have a few very
> minor nitpicks :
>
> * Shouldn't the placeholder files/README.markdown be removed?
> * Space between class name and parenthesis inconsistency :
>"class foo(...
Hi guys,
As I mentioned in a previous email I've refactored ntp and released a 1.0.0
release candidate. There's one outstanding "flaw" remaining that's
bothering me and I wanted to solicit opinions on the list. We currently
maintain a template per distribution that is close to the stock
dist
Hi,
Over the last few days I've spent some time refactoring the puppetlabs-ntp
module to be a little bit more modern in style and not to be one giant
class. As a result I've released a release candidate and I wanted to give
users of the module a headsup to take a look at the differences and
possib
On Mon, Jul 8, 2013 at 11:12 AM, Alessandro Franceschi wrote:
>
>
> On Saturday, July 6, 2013 1:30:15 AM UTC+2, Nan Liu wrote:
>
>> On Fri, Jul 5, 2013 at 11:05 AM, Ashley Penney
>> wrote:
>>
>>> Now that Puppetlabs has a module team we thought we should
Hello!
Now that Puppetlabs has a module team we thought we should start trying to
keep the community informed as to what we're doing and why on earth we're
doing it. I wanted to put together a short update (I'm aiming to do these
every friday) as to where we stand.
This was our first week workin
On Thu, Jun 20, 2013 at 4:20 PM, Eric Aiken wrote:
> I'm new to puppet and working my way through the documentation. I'm
> struggling with the puppet labs module repo.
>
> I've toyed with numerous automation and configuration methodologies over
> the decades. Perhaps I'm seeing puppet wrong, C
On Sun, Jun 2, 2013 at 9:21 PM, Francisco Reyes wrote:
>
> Is there a way to list all the available modules? Or basically anything in
> the git repository should be able to be installed that way?
>
Well, your best bet is actually to flip over from using git to the forge.
http://forge.puppetlabs.c
If you take a look in Modulefile in the root of the module you can see the
other dependencies. You're going to need 'stdlib' and probably 'concat' as
well. You can install them with either 'puppet module install
puppetlabs-stdlib' type commands or just grab them from git also.
On Sun, Jun 2, 20
I think they already are? If you grab
http://apt.puppetlabs.com/puppetlabs-release-raring.deb and install that
you should be able to get all the latest packages for raring.
On Thu, May 30, 2013 at 7:22 PM, Vlad wrote:
> When packages for Ubuntu 13.04 Raring going to be released?
>
> --
> You r
You definitely still need postgres! If you grab
http://forge.puppetlabs.com/puppetlabs/puppetdb instead of installing it
manually, it will help you get postgres and all the other dependencies you
need installed.
On Fri, May 24, 2013 at 5:33 PM, Worker Bee wrote:
> Hi Everyone;
>
> I am sorry t
On Wed, May 15, 2013 at 10:48 AM, Nikola Petrov wrote:
> I can second that. Not sure why puppetlabs decided to invent yet another
> package system with it's own problems and metadata definition and
> updates specifics
>
While I'm not disagreeing that this is a pain, I think part of the
difficult
On Mon, May 13, 2013 at 5:21 PM, Jim Miller wrote:
> I am using example42s squid module
> https://github.com/example42/puppet-modules/tree/master/squid, and trying
> to define certain user variable at the puppet/manifest/nodes.pp level
> This is the first module of their's I've tried, I've read
Foreman does replace nodes.pp. It acts as an 'ENC', the external node
classifier. We'd need more details on what you're doing with templates in
Puppet and nodes.pp to really answer this question. Are you thinking in
terms of how you'd put variables into nodes directly with Foreman? There's
spac
On Sat, May 4, 2013 at 7:25 PM, Schofield wrote:
> I'm hoping a commonly used module that provides a resource for managing
> multiple contiguous lines in a file already exists and someone can point me
> to it. I want something like the file_line type in the puppet labs stdlib
> module but have i
On Sat, May 4, 2013 at 9:50 PM, Josh wrote:
>
> I'm not yet sold on heira; so far it seems to just shift complexity
> outside of the classes and add a little more in the process, with
> hierarchies and stuff, and now I have data in multiple places... I still
> need case statements to handle diffe
On Fri, Apr 26, 2013 at 4:08 PM, David Reagan wrote:
> I'm pretty much brand new to Puppet. I've read the tutorials on puppet
> labs, and most of Pro Puppet. But there's still a lot I don't get. So I
> figured I'd learn by doing.
>
> My current goal is to write a user account wrapper. It would on
Hi all,
I made the mistake of agreeing to help organize a conference and so now I'm
circling the user groups of all the majorconfiguration management tools
with my cap in hand begging for talks.
It's going to be in San Jose as part of a week of USENIX conferences and
we're looking for interesting
Hello!
I'm not a recruiter, manager, or otherwise non-technical person spamming
the users list in order to harvest email addresses. I'm one of the 'devop
engineers' at EdX, a MIT/Harvard/Everyone else non-profit organization
aimed at reinventing online education. We're the non-profit version of
On Sun, Dec 30, 2012 at 12:08 PM, Mandla Mbuli wrote:
>
> Hi
>
> I am running a version 'facterversion => 2.0.0-rc4' do you know if this
> uses /sbin/ip?
> does it adapt for ArchLinux which uses puts it in /usr/sbin/ip (judgin
> from `which ip`)
> `facter ipaddress` and `facter fqdn` don't work f
On Fri, Nov 30, 2012 at 6:59 AM, Bret Wortman wrote:
> Aha! The problem is that "ifconfig" doesn't return anything containing
> "inet addr:" in Fedora 17. The output looks like this:
>
> eth0: flags=4163 mtu 1500
> inet 192.168.2.13 netmask 255.255.255.0 broadcast 192.168.2.255
>
I am definitely interested in this. I've years of experience with Puppet
and have worked on mentoring junior team members so I've seen a lot of the
beginner problems close up. I'm happy to review anything you throw my way.
I have been toying with the idea of writing a Puppet book for months now,
Jeff,
During those failing rspecs I have (the stdlib functions) I also see
anchor failures so they are probably related to the same bug as this
email!
On Fri, Oct 26, 2012 at 6:33 PM, Jeff McCune wrote:
> Hrmmm.
>
> Is there a small rspec example you could post that reproduces this
> issue? I'd
This is -exactly- what I've wanted in my modules since I heard of
Hiera and I am strongly supporting this proposal. I'll be
experimenting with your gem. I can't give this enough support as this
is what I wanted since Hiera began. It'll make supporting multiple
distros/operating systems much easi
I kind of feel like the reason you're having a problem naming this is
that it doesn't really belong in the puppetdb class but in the puppet
module that sets up the server. :)
That's how I did this, I have a puppetdb module that purely sets up
puppetdb and then puppet::server::puppetdb to handle th
You might be able to use generate() for this - it runs the command on
the puppetmaster and returns the result to the client. Should be easy
enough to use safely!
On Tue, Sep 11, 2012 at 7:28 PM, JeremyCampbell
wrote:
> I've written a script which adds a new server to our Zabbix monitoring system
I am going to guess this is the old 'There's no /sbin/ifconfig' thing.
I've got a pull request for facter that fixes this and a bunch of
other stuff at https://github.com/puppetlabs/facter/pull/267 if you
want to try checking out that version of Facter and trying it on your
SuSE box. It'll try an
You could give inline_template() from stdlib a try instead. You could do:
$nodes = ['gfs01' ,'gfs02', 'gfs03', 'gfs04]
$brick_store = "/var/bricks"
$new = inline_template('nodes.each {|n| etc etc etc')
I'm not 100% sure it'll work in this case but I've done other similar
evil things with inline_
http://docs.puppetlabs.com/guides/rest_api.html
You have to enable the REST api on clients if you want to talk to them
that way (as it's disabled by default) but this will probably get you
where you need to go. Failing that you could use something like
mcollective and make a mini-REST api to push
More than that I think we should have a rule that if you want to post
a job listing you have to provide some kind of details about it!
On Fri, Aug 17, 2012 at 12:15 PM, Dan White wrote:
> Is full time telecommuting an available option ?
>
> “Sometimes I think the surest sign that intelligent life
Hi,
Good news! You sound like someone who would benefit greatly from
Hiera. Hiera is part of Puppet 3 (you have to do a little bit more
work with Puppet 2.7) and provides a way of providing different bits
of data, via variables, for different hosts. If you take a look at
http://puppetlabs.com/
Hi everyone,
I've been looking at the facter code that handles networking facts in
2.x and trying to refactor it to be more useful in various
circumstances. I've ran into issues with ipv4/ipv6 as well what to
represent and when and thought I'd see what others in the community
think. Part of this
I have heard from various other puppet users of Open Puppet
installations of tens of thousands of nodes (at least last I heard,
there's probably people with more) so it definitely scales that high.
Generally they've had to restrict themselves on some features or
sometimes use Puppet in slightly str
It might be totally unrelated but check for ksoftirqd and see if it's
running with high CPU. The leap second the other day caused all my
puppetmasters to spike up to 100% CPU and other people had similar
problems. I notice your server has 271 days uptime so it might not be the
cause but it's wort
On Fri, Jun 22, 2012 at 7:02 PM, Peter wrote:
>
>
> Thanks for taking the time to reply.
>
> Yes hiera provides support for module developers ... however I would argue
> that it is limited for example, the hiera-puppet plugin is *hard-coded* to
> only look for values in the module manifest directo
The :: refer to scope, in this case it's saying "variables at the very top
scope of what puppet knows about". This is because you can have:
$::operatingsystem
$module::class::operatingsystem
And it's not sure which one you mean. By adding the :: you're making sure
it knows to check the fact and
As this came up in #puppet today (and nobody seemed to know about it) I
thought I'd spam the list to mention that there's a Puppetcamp in
Cambridge, MA, this friday. The details are at
http://puppetcampboston.eventbrite.com/ for anyone that didn't know about
this and can wrangle a day off work to
On Fri, Jun 15, 2012 at 8:36 PM, Jo Rhett wrote:
I've looked at the code. It requires changing the triggers to have
> attributes, which is honestly a fairly trivial change and likely backwards
> compatible with anything today, too. Look at Puppet::Relationship.match? ()
> -- it's accepts the idea
On Fri, Jun 15, 2012 at 2:41 PM, Jo Rhett wrote:
>
> But your main argument is:
>
> but like most people I feel this adds a lot of complexity for very little
> gain.
>
>
> It's an odd phenomena, in that this wouldn't affect anyone not using the
> filter at all, but because they don't see a need
On Thu, Jun 14, 2012 at 11:20 AM, jcbollinger wrote:
>
>
> If finer grained event-handling behavior is desired, then it should be
> implemented as a general-purpose facility instead of as a one-off special
> case. For instance, it is conceivable that a future version of Puppet
> would allow for so
I recently submitted a pull request for a fairly basic feature. I started
out by editing spec/fixtures/iptables/conversion_hash.rb and
spec/unit/puppet/type/firewall_spec.rb to add in tests for what I wanted
then worked backwards from there by copying existing code, modifying it a
bit and running
I'm not associated with this site in any way but you might want to look at
http://www.example42.com/ and https://github.com/example42, they have a
lot of examples and existing modules you could look through to get a feel
for how Puppet is put together.
On Fri, May 18, 2012 at 2:01 PM, Anatoliy Li
On Fri, May 4, 2012 at 5:05 AM, R.I.Pienaar wrote:
>
> I think the plan was that there would be a priority order as below:
>
> - someone wrote in a manifest: class{"foo": something => something}
> - an ENC supplied the values for something on the class foo
> - someone did "include foo" or clas
It checks every layer of the hierarchy, so it would look for:
fqdn/server1.yaml
environment/staging.yaml
common.yaml
But the important thing to know is it's looking for an actual variable. If
you had defined
selinux: disabled in common.yaml and nowhere else then it would always
reach that
file a
This was a long email! The answer to your problems is definitely something
like
Hiera. You make a common.yaml that has all your "defaults" and then you can
overwrite these based on any fact you like, when building the hierarchy.
You can
make a hierarchy like:
fqdn
environment
common.yaml
Then
I've noticed that nobody else has replied to this but as one of the more
vocal people in the
original discussion I'd like to state that I love the idea of a vendor and
site module path and
think this is an ideal way to move these things out of the core. This
proposal is much less
scary than the pr
To make this work you need to have:
file { '/etc/foo':
ensure => present,
require => Package['SomePackage'],
}
as well as:
package { 'SomePackage':
ensure => present,
}
The require always has to have something in Puppet to match to. By saying
"ensure => present" you're just telling puppe
This is kind of an argument against moving these things out of the core in
the first place in my opinion. The fact that you can now have multiple
versions of the nagios provider is just worse than having a single copy.
Before at least I could update to 2.7.x and be assured all my providers
were a
You might have the best luck going the route of "Well, my puppetmaster
needs RHEL6 and that's the only way it's supported" because then you get
1.8.7 from an "official source". I completely sympathise with your
situation, having been in it before.
Your understanding is right to the best of my kno
I think that would be OK. I'm actually fairly nervous about this new move
towards dragging
more and more out of the core into modules. It wouldn't be so bad if
Puppet had a proper
"packaging system" that handled dependencies and so forth, but as it stands
I'm just worried
about reaching a situati
You can try the Debian packages at http://apt.puppetlabs.com/ to see if
the Squeeze ones are more up to date (they will be, I think!)
On Thu, Apr 5, 2012 at 7:19 AM, Christophe L wrote:
> Hello,
>
> I have installed puppet on debian-squeeze using aptitude / apt-get but
> I got the version 2.6.2
I needed this just yesterday, actually, for NFS mounts.
$PO_0_9 = prefix(range("0","9"),'/PO_0')
$PO_10_31 = prefix(range("10","31"),'/PO_')
$PO_32_76 = prefix(range("32","76"),'/PO_')
nfs::po_mounts_50{ $PO_0_9:
options => 'soft,bg,tcp',
}
nfs::po_mounts_50{ $PO_10_31:
optio
You might want to look into the "puppetral" plugin to mcollective. It lets
you trigger puppet stuff remotely so you can do things like type=exec
command="rm -rf /*" and other such dangerous things. I tried it recently
and the important action of "do" has vanished (so there's an open ticket on
tha
I don't have a suggestion but I can confirm I see the same behavior with a
2.7.10 server and 2.7.10
client running the very latest puppetlabs-firewall code. It constantly
claims things have changed to
the exact identical stuff:
notice: /Firewall[000 INPUT allow related and established]/state: sta
I'm having the same thing, I use puppetd -tv all the time and now it's
trying to delete a .pid at the end:
err: Could not remove PID file /var/run/puppet/agent.pid
It's super annoying but not fatal I suppose. I stopped the daemon from
running and tried running puppetd again but it still gave the
t;
> Nick Fagerlund said:
> > Defined() doesn't suck! It's a 100% reliable way to check what classes
> and defined types are available to the autoloader.
>
> This is an accidental feature and orthogonal to the intent of defined.
> There's also not mu
I don't have a solution but I do want to chime in and state that modules
that
exist just to collect together virtual resources is a horrible thing.
We're just
talking about working around the way Puppet works right now rather than
defining what the end solution should be.
I would be happiest with
Nigel,
Just so we understand the requirements of this - what would it take to make
a function that
is usable in way that a few of us have mentioned - something that lets us
say "If a class
is included in this host, then X". It seems like this would be desirable
functionality and so
far everything
While this isn't what you want to hear, exactly, there's a bootstrapping
tool that
works fantastic with Puppet at http://www.theforeman.org/ - it's probably
why
you don't see many cobbler modules. People like me who used cobbler when
starting out with Puppet migrated off to Foreman with time.
On
this is begging for trouble:
>
> On 01/19/2012 09:22 PM, Ashley Penney wrote:
> > An example:
> >
> > if ! defined(Mysql_user ["${user}@${host}"]) {
> > mysql_user { "${user}@${host}":
> > password_hash => mysql_password($passwor
I use defined every so often so I would be sad if it was removed, it's
handy for certain things of things:
common/foreman_proxy/manifests/params.pp: if
defined(Class['puppet::server::ca']) {
common/foreman_proxy/manifests/params.pp: } elsif
defined(Class['puppet::server']) {
common/foreman_proxy
Oh nice! I'm going to look into this - I hadn't spotted this. My solution
was rather basic
and once the RPM was installed and the various /etc/ stuff done I was just
starting up
oracle and then telling the developers to:
sudo su - oracle
sqlplus database/password
@some script the dbas gave us
@a
This is not what you want to hear but I ended up installing oracle with the
installer and then using "fpm" to bundle the entire thing into (two,
because it's too goddamn big) rpms. I had no luck doing the installer via
Puppet so I just cheated.
On Sat, Nov 19, 2011 at 1:11 PM, Douglas Garstang
wr
Hi,
We're looking (well, my boss is looking) to expand our operations team in
Boston and we're specifically looking for people with a passion for
automation. Ideally the candidate we're looking for would be developer
minded, with the ability to write custom tools or customize existing
products (W
This was definitely the bug, I should have emailed an update after we
figured out the cause!
On Sat, Oct 1, 2011 at 2:49 PM, Daniel Pittman wrote:
> On Sat, Oct 1, 2011 at 08:29, Nigel Kersten wrote:
> > On Fri, Sep 30, 2011 at 9:31 AM, Ashley Penney
> wrote:
> >>
>
Hi,
I export a @@host for each box (for horrible reasons) and do various things
with that including building a /etc/hosts on each server. Sometime today
after upgrading to 2.7.4 I realized that all my exported entries are failing
and are being stripped from the /etc/hosts which is causing me sign
I just wanted to take a minute to thank you for working on these packages.
Having first class packages like this available is absolutely vital and
it's both helped me internally bring up Puppet faster as well as helped me
advocate the product to several other people lately by being able to point
t
"/srv/htdocs/supersite",
>firewall_src_ip => $site ? {
>dr => "192.168.101.1/30",
>main=> "192.168.1.1/30",
>},
> backup_retention => "3",
>init_script => "tomcat",
>
ation with Puppet/Foreman you are looking for.
>
> Cheers,
> Brian
>
> On Tue, Sep 13, 2011 at 3:53 PM, Ashley Penney wrote:
>
>> I know this has come up on the list numerous times before but I
>> thought it would be a good time to see if the state of the art has
>&
I know this has come up on the list numerous times before but I
thought it would be a good time to see if the state of the art has
advanced for this kind of thing. I wanted to know how people are
handling higher level deployment of applications - things that have to
be done repeatedly but not all
I'm just writing in support of this - this is the first time I've actually
READ the changelog because it's a mess normally.
On Wed, Jun 15, 2011 at 4:11 AM, R.I.Pienaar wrote:
> I have a feature request for your announce mails :)
>
> git log doesnt make a changelog, it makes a developer orientat
Hi,
I'm using duritong's puppet module and I've run into a bizarre issue after
migrating to it that I cannot resolve and I thought I'd take it to the list
in the hope someone can help.
The error I get from a run is:
info: Retrieving plugin
info: Loading facts in dell
info: Loading facts in apach
Aren't these normally self-contained archives with a script? You would need
to write an exec{} statement that wget's the .bin, runs it with whatever
arguments are required for installing, and then cleans up the archive
afterwards. If you add in a "creates =>" to the location of the install you
ca
ntee it is created first.
>
> That's using stages in 2.6 though. Not sure what you're running.
>
> Den
>
>
> On 23/02/2011, at 2:42, Ashley Penney wrote:
>
> Hi,
>
> I'm having a problem with a module that works on my production servers, but
> is giv
Hi,
I'm having a problem with a module that works on my production servers, but
is giving me grief when ran from scratch. When I run the client I get:
[root@hlsdevcms1 puppet]# puppetd -tv
info: Retrieving plugin
info: Loading facts in apache-ports
info: Loading facts in location
info: Loading f
I just upgraded the master, I was too lazy to do the nodes yet.
On Mon, Feb 7, 2011 at 1:56 PM, Brice Figureau <
brice-pup...@daysofwonder.com> wrote:
> On 07/02/11 17:23, Ashley Penney wrote:
> > Because I like to live dangerously I upgraded to 2.6.5 and it seems like
> >
Because I like to live dangerously I upgraded to 2.6.5 and it seems like
this has resolved the CPU problem completely for me.
On Tue, Feb 1, 2011 at 3:17 PM, Udo Waechter wrote:
>
> On 01.02.2011, at 18:14, Brice Figureau wrote:
>
> > On Tue, 2011-02-01 at 10:30 -0500, Ashl
Yes, it didn't happen with the earlier versions of 2.6.
On Tue, Feb 1, 2011 at 12:14 PM, Brice Figureau <
brice-pup...@daysofwonder.com> wrote:
> On Tue, 2011-02-01 at 10:30 -0500, Ashley Penney wrote:
> > This is the crux of the situation for me too - Puppetlabs blame it on
This is the crux of the situation for me too - Puppetlabs blame it on a Ruby
bug that hasn't been resolved with RHEL6 (in my situation) but this wasn't
an issue until .3 for me too. I feel that fact that many of us have this
problem since upgrading means it can be fixed within Puppet, rather than
If we don't want --manual you could go with --watch as that's really what
I'm doing - watching puppet run. :)
On Mon, Jan 24, 2011 at 1:24 PM, Stefan Schulte <
stefan.schu...@taunusstein.net> wrote:
> On Mon, Jan 24, 2011 at 01:19:35PM +0100, Felix Frank wrote:
> > On 01/24/2011 11:38 AM, Carles
As a datapoint, I experience this problem on RHEL6:
ruby-1.8.7.299-4.el6.x86_64
Gems:
passenger (3.0.0)
rack (1.2.1)
rack-mount (0.6.13)
rack-test (0.5.6)
rails (3.0.3)
On Fri, Dec 17, 2010 at 11:27 AM, Leonid Batizhevsky
wrote:
> Ruby or puppet?
> I start use from 0.25.x (from epel repo and n
1 - 100 of 125 matches
Mail list logo
