Matthaus Litteken wrote:
Yes, we are working on packaging Fedora 17, but as Brian suspected, we
haven't worked out the kinks in packaging against Ruby 1.9.x. If
someone has patches to submit against the spec file in
conf/redhat/puppet.spec that will allow for a ruby 1.9 build, please
submit a
ble linguistic crutch of the inarticulate
motherfucker.
-- Bruce Sherrod
#!/usr/bin/python -tt
#
# Copyright 2012 Todd Zullinger
#
# Permission to use, copy, modify, distribute, and sell this software and its
# documentation for any purpose is hereby granted without fee, provided that
# the a
Michael Stahnke wrote:
For the next major Puppet version, code-named Telly, we have some
changes coming. This is the first in a series of emails around these
changes and may require some input from the community.
For Telly, the nagios types will be moved into a module. This allows
them to b
Gary Larizza wrote:
Have you checked out the packages that Karanbir Singh has created? They
work fairly well --> http://centos.karan.org/el5/ruby187/
They're also not updated for recent security vulnerabilities, which
should be a concern for anyone deploying them in production.
Basically, t
Julien C. wrote:
The dashboard integration part.
I ended up using yup.puppetlabs.com and it works fine :-)
Good to know. I wonder if the dashboard packages should require
puppet >= 2.7.x ?
--
ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
Julien C. wrote:
Answering to myself: no 2.6.14 doesn't send reports.
Is this only an issue with integrating with dashboard or are you not
getting reports at all with 2.6.14? I'm using the EPEL packages and
my reports are working AFAICT.
--
ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: w
Jo Rhett wrote:
> Are you running the latest centos or redhat-based kernel? If so,
> 274.7.1 is corked. Backgrade from 274.7.1 to 274.3.1 and the problem
> will disappear. This is documented in
>
> https://projects.puppetlabs.com/issues/10418
>
> And RedHat bug
>
> https://bugzilla.redhat.com/show
robert.morti...@gmail.com wrote:
> I am having no joy installing Puppet Server with MySQL support from
> the EPEL on Centos 6. The active record support for MySQL seems to be
> missing. Has anyone seen a good howto for this?
Sadly, rubygem-rails is not built for EL-6. You can either rebuild
the 2
Steve Traylen wrote:
> The recently released facter contains a new fact $osfamily
>
> Facter 1.6.2. available
>
> ##New fact: (6792) Added osfamily fact.
>
>Added osfamily fact to determine if a given operating system is a
>derivative of a common operating system.
>
> this is equal to redh
Johan Sunnerstig wrote:
> That sounds promising. I'm currently using the EPEL repository to
> install Puppet, and they're at 1.6.0.
> I guess I'll have to decide what's less trouble, installing Puppet
> some other way or rewriting a bunch of manifests. :)
1.6.1 is in epel-testing. Once it moves t
Sam Roza wrote:
> I think that the issue is due to my puppet installation (from EPEL)
> not configuring the init.d script properly.
It's configured fine as it is. :)
> puppetmasterd doesn't think it is a service.
You want to use service { 'puppetmaster': ... } in your manifests.
--
Todd
Stefan Schulte wrote:
> I guess facter as a standalone executable doesn't look into
> /var/lib/puppet. Try running
>
> FACTERLIB=/var/lib/puppet/lib/facter facter
>
> as described in the custom facts guide [1]
>
> [1] http://docs.puppetlabs.com/guides/custom_facts.html#an-example
Or use the -p
Jim N wrote:
> I was getting this when starting puppetmasterd (puppet-
> server-0.25.5-1.el6.noarch RPM install):
>
> $ sudo /etc/init.d/puppetmaster start
> Starting puppetmaster: Could not run: Could not create PID file: /var/
> lib/puppet/run/puppetmasterd.pid
>
>
> This change in the init scrip
I wrote:
> Chris May wrote:
>> Did anyone ever post a bug, or find a solution for this? I've just
>> upgraded some of our Solaris boxes (using OpenCSW) to 2.6.9 and I'm
>> seeing the same behaviour.
>
> If there is a bug filed, I'd love to know what it is. Searching
> redmine for "reports" doesn't
Hi all,
I find myself in (generally) sunny Sarasota Florida for a few weeks.
Any folks in the area want to meet up for drinks and puppet chatter?
--
ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
~~
Subtl
Chris May wrote:
> Did anyone ever post a bug, or find a solution for this? I've just
> upgraded some of our Solaris boxes (using OpenCSW) to 2.6.9 and I'm
> seeing the same behaviour.
If there is a bug filed, I'd love to know what it is. Searching
redmine for "reports" doesn't find anything that
treydock wrote:
> Here's a diff for version 2.6.9...all you have to do is change the
> Version number. I added ruby-shadow cause I have had problems in 5.6
> with the "dist" variable not being set.
If you're building packages and not using mock (which you should
definitely check out, if you aren'
Douglas Garstang wrote:
> Does anyone know where I can get the latest puppet, 2.7.1 as RPM's?
>
> The spec file that comes with the puppet 2.7.1 source is broken
> again, and only version 0.25.5 seems to be available via EPEL, which
> means that the website's assertion that you can get puppet as an
rvlinden wrote:
> I used to download the Puppet and Facter RHEL5 rpm packages from
> http://people.fedoraproject.org/~tmz/repo/puppet/epel/
>
> but the latest version on that site is puppet 2.6.9 and facter
> 1.5.9.
>
> Does anyone know if this site is the still maintained ? or if there
> are other
Hi Derek,
Derek J. Balling wrote:
> Do you have an ETA for 2.7.x RPMs in that repo by any chance?
I'd like to get 2.6.6 into EPEL and then update it to 2.6.9 before I
move my fedorapeople repo to 2.7.x. I've not looked closely at 2.7.x
yet, but I get the feeling that it's not going to be an upda
Michael Stahnke wrote:
> This release is a maintenance release of the 2.6.x series of Puppet.
> This will likely be the last release in the 2.6.x series for Puppet,
> now that 2.7 is out.
For those using Fedora or RHEL/CentOS, I've updated the yum repos at:
http://tmz.fedorapeople.org/repo/pu
Hi,
Christopher McCrory wrote:
> I don't know if this is a rpm buglet or a general puppet buglet, but
> with puppet-2.6.9-0.1.rc1.el5.noarch.rpm from tmz I get emails like:
>
> Wed Jun 22 12:46:11 -0700 2011 Puppet (notice): Finished catalog run in
> 6.53 seconds
>
> on every run. I haven't teste
Michael Stahnke wrote:
> This release is a maintenance release of the 2.6.x series of Puppet.
>
> This release is available for download at:
> http://puppetlabs.com/downloads/puppet/puppet-2.6.9rc1.tar.gz
Better late than never, I've pushed rpm's for this release to my
fedorapeople.org repo:
Nathan Clemons wrote:
> http://projects.puppetlabs.com/issues/3238 is the issue I was
> thinking of, but 3693 is probably a duplicate of that.
>
> These bugs have been open a really long time. Outside of lowering
> the MySQL timeout value, are there any workarounds for this problem?
> I can't reall
treydock wrote:
> What is the current issue number? The only one I could find that
> mentions the same problem is this ,
> http://projects.puppetlabs.com/issues/7203.
https://bugzilla.redhat.com/show_bug.cgi?id=572722 and
http://projects.puppetlabs.com/issues/3693 are both relevant here.
I'd lo
Nigel Kersten wrote:
> Facter 1.5.9rc6 is a maintenance release containing fixes and updates.
For those using Fedora or RHEL/CentOS, I've updated the yum repos at:
http://tmz.fedorapeople.org/repo/puppet/
Packages for EL 4 - 6 and Fedora 13 - 15 are available for testing.
Add the puppet.repo
Matt Robinson wrote:
> This release addresses issues with the Puppet 2.6.x series.
For those using Fedora or RHEL/CentOS, I've updated the yum repos at:
http://tmz.fedorapeople.org/repo/puppet/
Packages for EL 4 - 6 and Fedora 13 - 15 are available for testing.
Add the puppet.repo file from
Jacob Helwig wrote:
> Facter 1.5.9rc5 is a maintenance release containing fixes and updates.
For those using Fedora or RHEL/CentOS, I've updated the yum repos at:
http://tmz.fedorapeople.org/repo/puppet/
Packages for EL 4 - 6 and Fedora 13 - 15 are available for testing.
Add the puppet.repo
Jacob Helwig wrote:
> This release addresses issues with the Puppet 2.6.x series and adds
> the Inventory Service.
For those using Fedora or RHEL/CentOS, I've updated the yum repos at:
http://tmz.fedorapeople.org/repo/puppet/
Packages for EL 4 - 6 and Fedora 13 - 15 are available for test
Tim Dunphy wrote:
> I am having a strange occurrence where I can run puppet on a client
> successfully and have it install httpd and php and a few other
> packages. The first run everything goes ok and everything installs
> perfectly the first run. But if I delete the packages (using yum
> remove
Jacob Helwig wrote:
> Facter 1.5.9rc4 is a maintenance release containing fixes and updates.
For those using Fedora or RHEL/CentOS, I've updated the yum repos at:
http://tmz.fedorapeople.org/repo/puppet/
Packages for EL 4 - 6 and Fedora 13 - 15 are available for testing.
Add the puppet.repo
Ben Hughes wrote:
> On Sun, Mar 20, 2011 at 01:17:17PM -0500, TJ Yang wrote:
>
>> I am not familiar with yum. Would you mind provide a simple
>> instruction to enable yum to install your test package ?
>
> http://www.craigdunn.org/2010/08/part-1-installing-puppet-2-6-1-on-centos-with-yumrpm/
>
> Co
Hi TJ,
TJ Yang wrote:
> I am not familiar with yum. Would you mind provide a simple
> instruction to enable yum to install your test package ?
You must enable the updates-testing repo on Fedora (or epel-testing on
RHEL/CentOS).
yum --enablerepo updates-testing install puppet
--
Todd
I wrote:
> I plan to get these packages built for Fedora and EPEL 5/6 testing
> repositories in the next few days. Anyone who finds showstopper bugs
> before then will be my hero for the day.
Puppet 2.6.6 packages are now in Fedora and EPEL testing repositories.
Anyone testing these packages is e
The arp command is in /sbin on Fedora/RHEL, not /usr/sbin. Using
Facter::Util::Resolution.exec is preferable to hard-coding the path.
---
lib/facter/arp.rb |8 +---
1 files changed, 5 insertions(+), 3 deletions(-)
diff --git a/lib/facter/arp.rb b/lib/facter/arp.rb
index 65cf4c3..5035ad0
Hi T.J.,
T.J. Yang wrote:
> I looked at puppet 2.6.6-0.5 puppet client and server packages.
> Two questions so far about the client(R1) /server(R2) packaging.
>
> 1. why puppetca reside in client rpm but not in server rpm ?
While I don't speak for Jeff or the Puppet Labs folks, the packages
there
Jacob Helwig wrote:
> Facter 1.5.9rc2 is a maintenance release containing fixes and updates.
For those using Fedora or RHEL/CentOS, I've updated the yum repos at:
http://tmz.fedorapeople.org/repo/puppet/
Packages for EL 4 - 6 and Fedora 13 - 15 are available for testing.
Add the puppet.repo
Jacob Helwig wrote:
> This maintenance release fixes two issues with Puppet 2.6.5.
For those using Fedora or RHEL/CentOS, I've updated the yum repos at:
http://tmz.fedorapeople.org/repo/puppet/
Packages for EL 4 - 6 and Fedora 13 - 15 are available for testing.
Add the puppet.repo file from
Jacob Helwig wrote:
> This maintenance release fixes two issues with Puppet 2.6.5.
To help with testing on Fedora or RHEL/CentOS, I've updated the yum
repos at:
http://tmz.fedorapeople.org/repo/puppet/
Packages for EL 4 - 6 and Fedora 13 - 15 are available for testing.
Add the puppet.repo fi
russell.fulton wrote:
> I'll repeat the question from my previous post: Is there a straight
> forward way to have a local rpm repository on the puppet server
> rather than relying on yum and the RHE channels?
It's trivial to run createrepo /path/to/rpms to create the yum
metadata. You can then s
Nigel Kersten wrote:
> The release is available for download at:
>
> http://puppetlabs.com/downloads/puppet/puppet-2.6.5.tar.gz
Congratulations and thanks to all the folks who worked on the release!
For those using Fedora or RHEL/CentOS, I've updated the yum repos at:
http://tmz.fedorapeople
Paul Berry wrote:
> We're back with a maintenance release: 2.6.5. This release addresses
> a number of bugs in the 2.6.x branch and adds a handful of features
> and documentation updates.
For those using Fedora or RHEL/CentOS, I've updated the yum repos at:
http://tmz.fedorapeople.org/repo/pu
Jacob Helwig wrote:
> We're back with a maintenance release: 2.6.5. This release addresses a
> number of bugs in the 2.6.x branch and adds a handful of features and
> documentation updates.
For those using Fedora or RHEL/CentOS, I've updated the yum repos at:
http://tmz.fedorapeople.org/repo/
Jacob Helwig wrote:
> We're back with a maintenance release: 2.6.5. This release addresses a
> number of bugs in the 2.6.x branch and adds a handful of features and
> documentation updates.
For those using Fedora or RHEL/CentOS, I've updated the yum repos at:
http://tmz.fedorapeople.org/repo/
Nick Lewis wrote:
> We're back with a maintenance release: 2.6.5. This
> release addresses a number of bugs in the 2.6.x branch.
For those using Fedora or RHEL/CentOS, I've updated the yum repos at:
http://tmz.fedorapeople.org/repo/puppet/
Packages for EL 4 - 6 and Fedora 13 - 14 are availa
sstein...@gmail.com wrote:
> FWIW, I just went through the same annoyance, slightly different
> issues on Ubuntu 10.04, it's not just Red Hat/Cent OS that's way out
> of date.
It's always tricky to keep up with a relatively young and fast moving
project like puppet -- especially if you don't want
pzi wrote:
> Just as I said if I have a choice of using tar file from the source
> I will always favor it over rpms cooked in unknown environment.
Just FYI, the packages in my repo are built in the Fedora/EPEL
buildsystem. They're signed with the same GPG key I use for my mail
as well. Not that
Arnau Bria wrote:
> maybe it's a little OT... anyone knows if old puppet version from tmz
> repos are still available somewhere?
I have some of them locally. I clean out older versions to conserve
space on my fedorapeople.org account. Were you looking for a
particular previous version?
--
Todd
James Turnbull wrote:
> Due to a security issue (see recent SECURITY email) we're releasing a
> 2.6.4 release immediately.
For those using Fedora or RHEL/CentOS, I've updated the yum repos at:
http://tmz.fedorapeople.org/repo/puppet/
Packages for EL 4 - 6 and Fedora 13 - 14 are available for
Nick wrote:
> RHEL/CentOS 5 has nothing at all in base, and only v22.4 in RPMForge
You want to use EPEL for puppet in RHEL/CentOS, as the RPMForge
packages are way out of date. That said, we've stuck with 0.25.5 for
now in EPEL. But I have 2.6.x builds in my own repository to aid in
testing on R
James Turnbull wrote:
> We're back with a new release: 2.6.3. This
> release addresses some issues in the 2.6.2 release.
For those using Fedora or RHEL/CentOS, I've updated the yum repos at:
http://tmz.fedorapeople.org/repo/puppet/
Packages for EL 4 - 6 and Fedora 12 - 14 are available for
James Turnbull wrote:
> We're back with a maintenance release: 2.6.3. This
> release addresses some issues in the 2.6.2 release.
For those using Fedora or RHEL/CentOS, I've updated the yum repos at:
http://tmz.fedorapeople.org/repo/puppet/
Packages for EL 4 - 6 and Fedora 12 - 14 are availa
James Turnbull wrote:
> We're back with a maintenance release: 2.6.3. This
> release addresses some issues in the 2.6.2 release.
For those using Fedora or RHEL/CentOS, I've updated the yum repos at:
http://tmz.fedorapeople.org/repo/puppet/
Packages for EL 4 - 6 and Fedora 12 - 14 are availa
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. You lose yum's ability to install depndencies for
one.
Daniel Kerwin wrote:
> i just upgraded some servers to Puppet 2.6.2 and it seems like it's
> not possible to use class names as tags anymore. I haven't found any
> documentation about this except a bug for 2.6.1 that should be fixed
> (http://projects.puppetlabs.com/issues/4631).
> # ~ #
Steven VanDevender wrote:
> I'm not our local Cobbler/Kickstart expert, but the guy who created
> our Cobbler installation even figured out how to script a new host's
> initial registration with the puppetmaster (I believe the key idea
> is that there is a command-locked ssh identity key that allow
James Turnbull wrote:
> All too quickly we're back with a maintenance release: 2.6.3. This
> release addresses some issues in the 2.6.2 release.
For those using Fedora or RHEL/CentOS, I've updated the yum repos at:
http://tmz.fedorapeople.org/repo/puppet/
Packages for EL 4 - 6 and Fedora 12
Ben wrote:
> I did a server and all client upgrade to your 2.6.1 package from
> your 0.25.5 package without any problems w/ your packaging.
> Install, init scripts, etc all work fine.
>
> And now the upgrade to 2.6.2 looks good after 5 whole minutes.
>
> Server: CentOS 5.5
> Clients: CentOS 5.x, RH
Chuck wrote:
> I have migrated my EL5 servers from 0.25.5 to 2.6.2 and have no
> issues now. I did have some issues with 2.6.1 which are now fixed.
> I would like to see 2.6.2 in the official EPEL repository.
Thanks for the feedback Chuck! Were any changes to your config or
manifests required (a
James Turnbull wrote:
> You can install the RPM package for CentOS or RHEL 5.5 by running the
> following from your shell:
> sudo sh -c "rpm -Uvh
> http://download.fedora.redhat.com/pub/epel/5/i386/epel-release-5-4.noarch.rpm;
> \
> cd /tmp/ \
> && wget -c
> http://www.puppetlabs.com/down
James Turnbull wrote:
> And we're back with another exiting release in the 2.6.x branch -
> 2.6.2.
For those using Fedora or RHEL/CentOS, I've updated the yum repos at:
http://tmz.fedorapeople.org/repo/puppet/
Packages for EL 4 - 6 and Fedora 12 - 14 are available for testing.
Add the puppet
micha...@tnrglobal.com wrote:
> On Sep 16, 4:23 pm, "R.I.Pienaar" wrote:
>> rpmbuild -ba -D 'dist .el5' -D 'rhel 5' -D '_without_augeas 1' puppet.spec
>
> Great- that works. I also just tried:
> rpmbuild --without augeas --without selinux --rebuild
> puppet-2.6.1-0.5.el5.src.rpm
FWIW, the spec f
Nigel Kersten wrote:
> On Tue, Sep 14, 2010 at 3:51 PM, Douglas Garstang
>> Lets play rock paper scissors to see who files a bug...
>
> That's uncharitable and unfair.
Indeed. I usually joke that all complaints should be submitted in
unified diff format. I actually feel bad anytime I file a bug
James Turnbull wrote:
> For example the Puppet respository that would have been cloned like:
>
> $ git clone git://github.com/reductivelabs/puppet.git
>
> Should now be cloned like:
>
> $ git clone git://github.com/puppetlabs/puppet.git
I know this came up in IRC the other day, so for anyone with
James Turnbull wrote:
> In the long Puppet tradition of fast releases and agile iteration
> comes the 2.6.1 release!
For those using Fedora or RHEL/CentOS, I've updated the yum repos at:
http://tmz.fedorapeople.org/repo/puppet/
Packages for EL 4 - 6 and Fedora 12 - 14 are available for testi
Patrick wrote:
> I would assume that the package maintainer moved the default
> directory location.
The Fedora/EPEL packages don't change this. I'm not sure if there are
any other yum using distros out there. But if the OP meant one of
those two, then /var/lib/puppet is the default $vardir. The
Jean-Baptiste Quenot wrote:
> After upgrading Puppet from 0.24.8 to 2.6.1rc2 at my company, I
> notice that puppet agent's --tags option is not honored anymore:
Did you happen to file a ticket for this yet? I need to test more
myself, but I believe I saw this the other day too, with rc3.
--
Tod
James Turnbull wrote:
> For 40 days and 40 nights Facter wandered in the wilderness
> sustained only by the occasional patch and bottle of Kool-Aid.
>
> Slightly less tanned and equally happy Facter 1.5.8 has arrived!
:)
> 1.5.8 is a feature and maintenance release containing a number of
> fixes,
James Turnbull wrote:
> In the long Puppet tradition of fast releases and agile iteration
> comes the 2.6.1 release!
>
> The third release candidate is now available and is a maintenance
> release in the 2.6.x branch.
For those using Fedora or RHEL/CentOS, I've updated the yum repos at:
http:
James Turnbull wrote:
> For 40 days and 40 nights Facter wandered in the wilderness sustained
> only by the occasional patch and bottle of Kool-Aid.
>
> Slightly less tanned and equally happy Facter 1.5.8rc2 has followed rc1
> out of the desert.
For those using Fedora or RHEL/CentOS, I've updated
Douglas Garstang wrote:
> The spec file for for (whatever version this actually is), doesn't
> cleanly build an RPM either.
>
> + /usr/lib/rpm/find-debuginfo.sh /usr/src/redhat/BUILD/puppet-2.6.0
> find: debug: No such file or directory
> + /usr/lib/rpm/redhat/brp-compress
> + /usr/lib/rpm/redhat/b
CraftyTech wrote:
> Gotcha... and I may also not mind creating multiple files under the
> repo directory, but how do I disable the default repos that come
> with CentOS?
yumrepo { 'base': enabled => 0 }
You can use 'enabled => absent' to remove the repo definition from the
file entirely.
--
Tod
Douglas Garstang wrote:
> After going through some dependency hell trying to get the
> rpmforge-release package installed before the RPMforge repo, which
> contains the GPG key for RPMforge packages, now I find that when
> puppet tries to install this package, this happens:
>
> Jul 20 10:20:04 slog
Douglas Garstang wrote:
> I just grabbed puppet 2.6, and I'm wondering if there's a way to
> install it to an alternative root location. The docs at
> http://docs.puppetlabs.com/guides/installation.html talk about how to
> set an alternate binary path etc, but nothing about specifying an
> alternat
James Turnbull wrote:
> Welcome back again to the Puppet release cycle with really truly
> next to final release candidate 4.
For those using Fedora or RHEL/CentOS, I've updated the yum repos at:
http://tmz.fedorapeople.org/repo/puppet/
Packages for EL 4 - 6 and Fedora 12 - 13 are available
James Turnbull wrote:
> Welcome back again to the Puppet release cycle with the just out of
> the gate release candidate 3.
For those using Fedora or RHEL/CentOS, I've updated the yum repos at:
http://tmz.fedorapeople.org/repo/puppet/
Packages for EL 4 - 6 and Fedora 12 - 13 are available fo
James Turnbull wrote:
> Welcome back again to the Puppet release cycle with the long-awaited
> eleventy times better RC2 release.
>
> The 2.6.0 release is a major feature release and includes a huge
> variety of new features, fixes, updates and enhancements. These
> include the complete cut-over f
Daniel Wittenberg wrote:
> Anyone written a check for nagios to make sure their nodes are
> checking in and updating correctly? I think I'd rather have a
> passive check on the nagios server that just alerts me if something
> hasn't checked in for last 24 hours rather than having antoher
> dashboa
Forrie wrote:
> What is the disadvantage of using the puppet gem vs. installing from
> source (install.rb)?
Well, I wouldn't recommend that either. I much prefer a proper
packaging system like dpkg or rpm. But that's just my opinion. :)
--
ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.po
Gus F. wrote:
> I am using puppet (version 0.25.5-1.e15 for redhat) for password
> management for non-system users. This morning, users on some of my
> puppet clients had their encrypted password strings in /etc/shadow
> replaced with the following string:
>
> YAML::syck::BadAlias
Eeeww. That's
Forrie wrote:
> Is there a way to just install the client component of the Puppet gem,
> install of both on systems that don't need the server/master
> component.
I don't think so. But all decent puppet packages have this
separation. I'd highly recommend not using gems. :)
--
ToddOpenP
Oded wrote:
> Never tried it myself but I think you can create the certificate as
> a part of the provisioning process, and then somehow place it in the
> new server.
> http://serverfault.com/questions/19462/how-can-i-pre-sign-puppet-certificates
Without reading the link to see if it's similar to
Matt Wallace wrote:
> I've updated my manifests to reflect the above, however now when I run
> Yum manually on the servers I get the following output:
>
> Repository 'epel' is missing name in configuration, using id
>
>
> It doesn't make a difference to the install, I'm just wondering if I'm
> miss
Peter Berghold wrote:
> Has anybody out there written a custom check for Nagios to determine
> if puppetd and/or puppetmasterd is running? I am considering writing
> one if not.
FWIW, I've got an overengineered check_puppet and puppetstatus tool
at: http://tmz.fedorapeople.org/scripts/puppetstatus
James Turnbull wrote:
> The release candidate is available at:
>
> http://puppetlabs.com/downloads/puppet/puppet-0.25.5rc3.tar.gz
For thoae using Fedora or RHEL/CentOS, I've updated the yum repos at:
http://tmz.fedorapeople.org/repo/puppet/
Packages for EL 4 - 6 and Fedora 11 - 13 are availa
Marley Bacelar wrote:
> I am trying to do my first puppet configuration, already installed the
> puppetserver and client, in this link show my configuration and my puppet
> structure:
>
> http://paste.pocoo.org/show/212227/
Which reads, in part:
> # ls /etc/puppet/ #
> files fileserver.conf man
I wrote:
> For thoae using Fedora or RHEL/CentOS, I've updated the yum repos at:
>
> http://tmz.fedorapeople.org/repo/puppet/
>
> Packages for EL-4, EL-5 and Fedora 11 - 13 are available for testing.
> Add the puppet.repo file from either the epel or fedora directories to
> /etc/yum.repos.d to
James Turnbull wrote:
> Welcome back to the Puppet release cycle for the second outing of
> 0.25.5 - release candidate number 2.
For thoae using Fedora or RHEL/CentOS, I've updated the yum repos at:
http://tmz.fedorapeople.org/repo/puppet/
Packages for EL-4, EL-5 and Fedora 11 - 13 are avai
Arnaud Gomes-do-Vale wrote:
> Brice Figureau writes:
>
>> Can you try with a newer rails/active record? This one is a little
>> bit old, and I'm not sure there aren't some bugs. I vaguely
>> remember that puppet required rails 2.2, but I might be wrong.
Well, puppet 0.25 doesn't refuse to run w
James Cammarata wrote:
> Any idea if/when these will be available in EPEL?
Bundled rails and various gems will make that difficult,
unfortunately. I don't know all that much about rails and gems, but
if anyone knows if it's possible to cleanly install multiple versions
of rails and gems, I'd be c
James Turnbull wrote:
> Welcome back to the Puppet release cycle - brought to you by the
> newly minted Puppet Labs.
>
> The 0.25.5 release is a maintenance release in the
> 0.25.x branch. It contains a number of bug fixes but also some
> performance enhancements including speed-ups to Puppet's gra
Michael DeHaan wrote:
> What if we taught the yum provider to know about "yum groupinstall" ?
>
> That way you could add packages into comps.xml and reference them
> together, which would also be faster than referencing each one by one.
>
> While it would not technically be a 'package' this might b
Christopher Johnston wrote:
> http://www.kanarip.com/custom/
>
> Someone pointed me to this repo the other day, havn't tested
> anything in or know who is maintaining it though.
Those packages are done by Jeroen van Meeuwen, the same fellow who's
trying to get passenger into Fedora and EPEL. Some
Michael DeHaan wrote:
> I'd like to push this through to Fedora review so we can get it built
> for EPEL (at least RHEL 5) and be available via yum.
Passenger has been in the Fedora/EPEL review queue for a long time --
like a year and a half. It's held up due to bundled libraries (a
similar theme
Len Rugen wrote:
> We updated our server last week to 25.4 and have updated a few clients.
> I've got one now that is irritated:
>
> info: Caching catalog for
> /usr/lib64/ruby/1.8/yaml/rubytypes.rb:315: [BUG] Segmentation fault
> ruby 1.8.1 (2003-12-25) [x86_64-linux-gnu]
>
> Any thoughts?
Yuck.
Douglas Garstang wrote:
>>> http://docs.reductivelabs.com/references/stable/type.html#sshkey
>
> WHat about known_hosts???
For /etc/ssh/ssh_known_hosts, using exported resources is quite handy:
http://reductivelabs.com/trac/puppet/wiki/ExportedResources
Something like:
# Collect ssh keys and
Kent Rankin wrote:
> [r...@ ~]# rpm -V puppet
> S.5T c /etc/puppet/puppet.conf
> [r...@ ~]# grep verbose /etc/init.d/puppet
> [r...@ ~]# grep verbose /etc/sysconfig/puppet
> [r...@ ~]# cat /etc/sysconfig/puppet
> # The puppetmaster server
> #PUPPET_SERVER=puppet
>
> # If you wi
Kent Rankin wrote:
> Installed the EPEL package... it runs it as a daemon without options.
> Here's the output from ps -ef|grep puppet:
>
> root 10249 1 0 Mar08 ?00:02:17 /usr/bin/ruby
> /usr/sbin/puppetd --verbose
That --verbose is what's causing this I think. That's not part of
I wrote:
> James Turnbull wrote:
>> Do you get a report each time without a value specified in
>> config_version?
>
> Yes. With config_version commented out in puppet.conf, I get a report
> using the timestamp even if nothing has changed. With a command set
> for config_version, I also get a repo
James Turnbull wrote:
> Do you get a report each time without a value specified in
> config_version?
Yes. With config_version commented out in puppet.conf, I get a report
using the timestamp even if nothing has changed. With a command set
for config_version, I also get a report when nothing has
1 - 100 of 172 matches
Mail list logo
