-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/01/2011 02:50 AM, Jo Rhett wrote:
> Mon Oct 31 23:03:31 + 2011 Puppet (notice): Caught TERM;
> calling stop
>
> Ever since the 2.6.12 upgrade I've been seeing these reports reach
> us. As in, about a hundred of a half thou machines. Most of
I have other classes and require between classes pps working perfectly
puppet apply --trace --debug /etc/puppet/site.pp
debug: importing '/etc/puppet/modules/apache2/manifests/init.pp' in
environment production
debug: Automatically imported apache2 from apache2 into production
debug: importing '/
I've just tried this (we assume /opt/jetty-6.1.26 already exists):
file { "/opt/jetty-6.1.26":
owner => "jetty",
group => "users",
recurse => true,
}
... but it's taking an *age*. What's the Right Way?
Cheers, Robert.
--
You received this message because you are subscri
Hi,
On 10/31/2011 07:47 AM, Swati Longia wrote:
> I don't even have normal linux commands like useradd or groupadd in this
> OS.
is this a requirement? Because:
> /err: Could not create resources for managing Puppet's files and
> directories in sections [:main, :agent, :ssl]: Could not find a de
Hi All,
I have a requirement to initiate puppet runs of different services in
a phase wise manner. I have the following setup in my nodes.pp
node /^(host1|host2)\.domain\.local$/ inherits basenode {
include role_service1
}
node /^(host3|host4)\.domain\.local$/ inherits basenode {
- Original Message -
> Hi All,
>
> I have a requirement to initiate puppet runs of different services
> in a phase wise manner. I have the following setup in my nodes.pp
you seem to be on roughly the right track
>
> node /^(host1|host2)\.domain\.local$/ inherits basenode {
>
On 10/31/11 2:04 AM, Henrik Lindberg wrote:
Need help with Geppetto issue #226 regarding rules for numerical
variables - https://github.com/cloudsmith/geppetto/issues/226
This is to allow geppetto to correctly validate their use.
Help much appreciated.
Regards
- henrik
Thanks everyone who chim
I have one host, the only one using this class, where it occasionally gets
the following error. I'd guess this happens 1/3 of the time, but seems to
work for several runs, then fail for several runs.
Could not retrieve catalog from remote server: Error 400 on SERVER: Could
not find class server::
how big is the directory structure?
we've had incredibly painful experiences trying to manage directory
perms/ownerships on large directory trees...
so much so that we only set the perms on a few of the top level
directories and left the rest
it's something to do with needing to do an md5 and sta
It also has to do with Puppet's implementation of File resources: it
creates in memory Ruby objects for every file and directory it finds
recursively, so combine that with the md5 summing and you'll blow out
your CPU and memory usage very quickly. I've done something like this
in the past:
$path="
I am trying to understand Puppet's Ruby DSL. I have tried it in
server-less mode using 'puppet apply' and it worked fine. But I am not
sure how to organize it in the server. It is a simple manifest file
without any modules and classes in it. Should it go in the regular
manifests directory (which al
This might help you:
http://docs.puppetlabs.com/learning/
Lots of people seem to have a structure so that /etc/puppet/manifests/site.pp
does this:
import "nodes/*"
And then your node definitions are in separate files in
/etc/puppet/manifests/nodes. Of course, each to their own. Maybe you like
Just upgraded to 2.7.6 and the yumrepo type does not write out our yum
configs correctly, anyone experiencing this? Documentation hasn't changed
from what I can tell for this type.
# facter -version
1.6.2
# puppetd --version
2.7.6
# facter architecture
x86_64
# facter operatingsystem
Fedora
# fac
You probably need to escape some of this, part of ours-
.repo/\$releasever/\$basearch
puppet/factor shouldn't resolve these variables, they go to the repo file
and are resolved by yum or whatever.
On Tue, Nov 1, 2011 at 10:45 AM, Christopher Johnston wrote:
> Just upgraded to 2.7.6 and the y
It's the "dashes at the end of variable names" problem. Try
"...${operatingsystem}-${operatingsystemrelease}-${architecture}" instead.
On 2011-11-01 09:07 , Len Rugen wrote:
> You probably need to escape some of this, part of ours-
> .repo/\$releasever/\$basearch
>
> puppet/factor shouldn't
I don't think this will help. I do report cleanup daily to keep only the
last 14 days and it hasn't touched the number of delayed job failures
reported.
On 10/31/2011 12:26 AM, Evgeny wrote:
this will clean all reports, I don't know how to clean only delayed
job failures but it may help
rake
Hi All,
Does anyone have a good git pre-commit hook that's compatible with
Puppet 2.7? The example pre-commit hook on the PuppetLabs wiki[1] no
longer works, because the puppet binary no longer seems to accept
stdin.
[1]
http://projects.puppetlabs.com/projects/1/wiki/Puppet_Version_Control
--
Len,
I would be very interested in the details of your Puppet Master system
running 2.7.5. Any configs you are willing to share would be appreciated.
Also, it would be most helpful if you can reproduce one of the failed runs
using from a Puppet client using:
puppet agent --test --debug
Thanks!
That worked, for some reason back referencing did not. My foolishness I
was overlooking normal variable semantic (like in shell). Strange thing my
prior setup worked fine in 2.6, 2.7 broke it.
-Chris
On Tue, Nov 1, 2011 at 12:40 PM, Jacob Helwig wrote:
> It's the "dashes at the end of variab
There was a change in 2.7 to allow dashes in variable names. There's an
issue open in Redmine around this very issue[0]
[0] http://projects.puppetlabs.com/issues/10146
On 2011-11-01 10:29 , Christopher Johnston wrote:
> That worked, for some reason back referencing did not. My foolishness I
> w
Hi guys,
For a project I'm working on for my studies we need to create a demo setup
of a small enterprise environment. The linux-part of this is now managed by
puppet. However, I'm running into something I can't exactly figure to how
to fix. I've read the docs a few times but I can't find a cle
On Oct 31, 1:47 am, Swati Longia wrote:
> Hi,
>
> I have installed puppet 2.7.5 from tar on open suse 10.1. My ruby version
> is 1.8.5 and facter version is 1.6.2. The opensuse OS is pretty
> minimalistic.
> I don't even have normal linux commands like useradd or groupadd in this OS.
Surely th
On Tue, Nov 1, 2011 at 6:27 AM, Len Rugen wrote:
> I have one host, the only one using this class, where it occasionally gets
> the following error. I'd guess this happens 1/3 of the time, but seems to
> work for several runs, then fail for several runs.
>
> Could not retrieve catalog from remot
On Fri, Oct 28, 2011 at 11:32 AM, Steven L. Seed wrote:
> I have a ton of delayed job failures in my dashboard under background
> tasks. They are mostly failed imports of report yaml files that were
> deleted. There are over 4 of them so I can't use the "Mark all as read"
> button because it
It could be this issue if you are using imports in your Puppet code.
https://projects.puppetlabs.com/issues/8433
--
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
Yes, this fits. I'll change my structure and see if it goes away. (Still,
would it work sometimes but not always?)
On Tue, Nov 1, 2011 at 2:55 PM, Chuck wrote:
> It could be this issue if you are using imports in your Puppet code.
>
> https://projects.puppetlabs.com/issues/8433
>
> --
> You re
Join me 11/8 at Brouwers Cafe in Fremont at 6pm for drinks and
discussions on Puppet, DevOps, system administration, etc.
http://www.meetup.com/Seattle-Puppet-Meetup/
-g
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, se
I'm running Ubuntu 10.04 LTS and I just installed Puppet and
puppetmasterd (both 0.25.4) along with the puppet-dashboard v1.2.0 and
Foreman 0.3. Puppet and the dashboard were working fine with just the
master server and a separate client until I installed and configured
Foreman. Now I keep getting
At the top of your email:
Could not find node 'puppet.mydomain.com'
At the bottom of your email:
node default {
}
node basenode {
}
node 'puppet-client0.mydomain.com' inherits basenode {
}
Does it work when you explicitly define this node?
node 'puppet.mydomain.com' {
}
On Tue, Nov 01, 2011
Hello,
I've mcollective 1.2.1 with puppet 2.6.12 on rhel5.6, facter 1.6.2
setup from
http://projects.puppetlabs.com/projects/mcollective-plugins/wiki/FactsFacterYAML.
Now I've create a custom fact in /usr/lib/ruby/site_ruby/1.8/facter/
customer_status.rb.
On the client;
Running facter customer_s
When I put that line in nodes.pp I get:
err: Could not retrieve catalog from remote server: Connection refused
- connect (2)
On Nov 1, 4:38 pm, Christopher Wood
wrote:
> At the top of your email:
>
> Could not find node 'puppet.mydomain.com'
>
> At the bottom of your email:
>
> node default {}
On Tue, Nov 01, 2011 at 01:56:53PM -0700, weloki wrote:
> When I put that line in nodes.pp I get:
>
> err: Could not retrieve catalog from remote server: Connection refused
> - connect (2)
So what dit he puppetmaster say about this agent run?
Also, keep digging into your own email. You may have
- Original Message -
> Hello,
>
> I've mcollective 1.2.1 with puppet 2.6.12 on rhel5.6, facter 1.6.2
> setup from
> http://projects.puppetlabs.com/projects/mcollective-plugins/wiki/FactsFacterYAML.
>
> Now I've create a custom fact in /usr/lib/ruby/site_ruby/1.8/facter/
> customer_statu
On Tue, Nov 1, 2011 at 9:53 AM, Christopher Wood
wrote:
> This might help you:
>
> http://docs.puppetlabs.com/learning/
>
> Lots of people seem to have a structure so that /etc/puppet/manifests/site.pp
> does this:
>
> import "nodes/*"
>
> And then your node definitions are in separate files in
On Tue, Nov 01, 2011 at 04:17:41PM -0500, neubyr wrote:
> On Tue, Nov 1, 2011 at 9:53 AM, Christopher Wood
> wrote:
> > This might help you:
> >
> > http://docs.puppetlabs.com/learning/
> >
> > Lots of people seem to have a structure so that
> > /etc/puppet/manifests/site.pp does this:
> >
> > im
On Nov 1, 10:00 pm, "R.I.Pienaar" wrote:
> - Original Message -
>
> you should be using pluginsync to copy out custom facts:
>
> http://docs.puppetlabs.com/guides/plugins_in_modules.html
>
Ok, enabled pluginsync, customer_status.rb is now copied to the client
in /var/lib/puppet/lib/facts.
Puppet 2.7.7rc1 is available.
This release fixes several issues with Mongrel and Puppet 2.7.x,
Windows fixes and updates, test fixes, documentation updates and more.
Release Notes for 2.7.7 series --
https://projects.puppetlabs.com/projects/puppet/wiki/Release_Notes
This release is available fo
On Oct 31, 3:09 pm, Dan Bode wrote:
> On Mon, Oct 31, 2011 at 12:44 PM, treydock wrote:
>
> > On Oct 31, 1:56 pm, treydock wrote:
> > > On Oct 31, 1:05 pm, Dan Bode wrote:
>
> > > > On Mon, Oct 31, 2011 at 10:55 AM, treydock wrote:
>
> > > > > On Oct 31, 12:26 pm, Dan Bode wrote:
> > > > >
Is any special escaping necessary for URLs in ERB templates? For example,
Puppet complains:
bad URI(is not URI?)
about the :80 and http:/// lines in a template like this:
[...]
RewriteRule ^/+(.*) http://example.com/$1 [L,R=permanent]
Ruby's uri.split() is the only place t
we are having problems with incompatibility between older clients and newer
configuration syntax.
(in specific, user resource system attribute was added somewhere between
2.6.6 and 2.6.11)
It seems the right thing to do for older clients when they attach is to give
them a very short manifest
On Tue, Nov 1, 2011 at 12:50 PM, Rob Terhaar wrote:
> Hi All,
>
> Does anyone have a good git pre-commit hook that's compatible with
> Puppet 2.7? The example pre-commit hook on the PuppetLabs wiki[1] no
> longer works, because the puppet binary no longer seems to accept
> stdin.
In 2.7 'puppet m
41 matches
Mail list logo
