err: Cached catalog for soncweb.nsc.liu.se failed: Could not parse
YAML data for catalog soncweb.nsc.liu.se: syntax error on line
1234, col 43: ` !ruby/sym line: id:3:initdefault:'
Funky. I bet you use pson for master-agent serialization (good choice).
YAML breaks
On 01/25/2011 06:14 PM, Mohamed Lrhazi wrote:
I read that to generate CA certs, one simply runs: puppetca
So for 2.6 I did: puppet cert
Huh. Where did you read that?
Could it be possible that the document in question implied that running
any puppetca subcommand will generate a CA cert if none
What seems to happen is things are working fine at the
beginning. Catalog compiles peg the CPU for the puppet process that is
doing them and take anywhere from between 20 seconds and 75
seconds. Then things get drastically worse after 4 compiles (note: I
have four mongrels too, coincidence?),
On Tue, 2011-01-25 at 20:26 +0100, Brice Figureau wrote:
On 25/01/11 20:10, Jason Wright wrote:
On Tue, Jan 25, 2011 at 10:48 AM, Brice Figureau
brice-pup...@daysofwonder.com wrote:
xmlrpc?
Do you still have 0.24.x clients?
No. We're 0.25.5 across the board.
You omitted one
On 2011-01-26 09:55, Felix Frank wrote:
err: Cached catalog for soncweb.nsc.liu.se failed: Could not parse
YAML data for catalog soncweb.nsc.liu.se: syntax error on line
1234, col 43: ` !ruby/sym line: id:3:initdefault:'
Funky. I bet you use pson for master-agent
libe...@rapleaf.com wrote:
You cannot save facts to the code store; it is only used for
getting facts from Facter
See http://projects.puppetlabs.com/issues/4527
James
--
Puppet Labs - http://www.puppetlabs.com
C: 503-734-8571
--
You received this message because you are subscribed to the
libe...@rapleaf.com wrote:
I'm clueless as to where to go from here. I have no custom facts. Is
this a file-system permission issue?
I'm also using the latest puppet binary 2.6.2
Oh and the latest Puppet version is 2.6.4.
Regards
James Turnbull
--
Puppet Labs -
On Tue, 2011-01-25 at 17:11 -0500, Micah Anderson wrote:
Brice Figureau brice-pup...@daysofwonder.com writes:
On 15/12/10 19:27, Ashley Penney wrote:
This issue is definitely a problem. I have a support ticket in with
Puppet Labs about the same thing. My CPU remains at 100% almost
I read it here: http://bodepd.com/wordpress/?p=7
But what is the sub-command to generate the CA certs?
Thanks,
Mohamed.
On Wed, Jan 26, 2011 at 4:08 AM, Felix Frank
felix.fr...@alumni.tu-berlin.de wrote:
On 01/25/2011 06:14 PM, Mohamed Lrhazi wrote:
I read that to generate CA certs, one
On 01/26/2011 01:27 PM, Mohamed Lrhazi wrote:
I read it here: http://bodepd.com/wordpress/?p=7
But what is the sub-command to generate the CA certs?
Interesting. This is quite recent and from an authoritative source.
Maybe Dan himself can shed more light on this.
puppet cert --help says
Hello,
I have installed puppet on the machine that is supposed to be the
puppet server.
Puppet is version 2.6.4
The puppet.conf file is the default created with puppet --genconfig
puppet.conf
When launching puppetd on the client and after having signed the
certificate, I always get the same
Hi Adriana,
Can you paste the output of:
puppetd --test --noop --evaltrace
and:
cat /var/lib/puppet/classes.txt
and your node definition for the host 'pc001'.
-Luke
On Jan 26, 1:19 pm, Adriana adriana.tele...@gmail.com wrote:
Hello,
I have installed puppet on the machine that is supposed
On Wed, 26 Jan 2011 05:19:11 -0800 (PST)
Adriana Adriana wrote:
Hello,
Hi,
[...]
When launching puppetd on the client and after having signed the
certificate, I always get the same
info: Caching catalog for pc001
info: Applying configuration version '1296044901'
notice: Finished catalog
Hello,
here it is:
puppetd --server pc03 --test --noop --evaltrace
info: Caching catalog for aldaqpc001.cern.ch
info: Applying configuration version '1296044901'
info: /Schedule[puppet]: Evaluated in 0.00 seconds
info: /Schedule[daily]: Evaluated in 0.00 seconds
info: /Schedule[monthly]:
Even if I completely delete the manifests dir content, the result is
the same.
It looks like the client cannot download the configuration from the
server, but I don't see any errors related to that.
Cheers,
Adriana
On Jan 26, 2:27 pm, Adriana adriana.tele...@gmail.com wrote:
Hello,
here it is:
On 01/26/2011 02:37 PM, Adriana wrote:
Even if I completely delete the manifests dir content, the result is
the same.
It looks like the client cannot download the configuration from the
server, but I don't see any errors related to that.
Cheers,
Adriana
Weird, there should be an error about
On 01/26/2011 03:01 PM, Adriana wrote:
It is very strange, the /var/log/messages on the server says:
pc03 puppet-master[32210]: Compiled catalog for pc001 in environment
production in 0.03 seconds
but then the rigth catalog is not downloaded.
Oh, another guess: You're using the wrong
info: access[^/catalog/([^/]+)$]: allowing 'method' find
info: access[^/catalog/([^/]+)$]: allowing * access
info: access[/certificate_revocation_list/ca]: allowing 'method' find
info: access[/certificate_revocation_list/ca]: allowing * access
info: access[/report]: allowing 'method' save
info:
On 01/26/2011 03:44 PM, Micah Anderson wrote:
Felix Frank felix.fr...@alumni.tu-berlin.de writes:
I propose you need to restructure your manifest so that it compiles
faster (if at all possible) or scale up your master. What you're
watching is probably just overload and resource thrashing.
I am sorry but I don't understand what you are suggesting me to do
with
strace -f -e trace=file puppet master ... 21 | grep site.pp
where do I have to look for site.pp?
On Jan 26, 3:41 pm, Felix Frank felix.fr...@alumni.tu-berlin.de
wrote:
So I guess it takes the configuration fro a catalog
Hi,
We've got our puppetmaster under puppet control and our /etc/puppet
dir tucked safely away in Mercurial.
With the help of the vcsrepo module we're automatically pulling the
latest changes from /etc/puppet giving us a nice little cycle (only
checked-in stuff can be deployed!).
However,
I have a couple of applications (backup, Cacti, Asset Tracking) where I want
a node to have some package and config installed, and once that is done,
some config to be done on another system to register the client with a
central server. Is there a standard way to do this, short of having some
kind
The trace of the puppetmaster grepped with site gives me the right
site.
I cannot understand what happens.
It really looks like the client doesn't take the configuration at all.
On Jan 26, 3:49 pm, Felix Frank felix.fr...@alumni.tu-berlin.de
wrote:
On 01/26/2011 03:47 PM, Adriana wrote:
I am
On 01/26/2011 04:03 PM, Adriana wrote:
The trace of the puppetmaster grepped with site gives me the right
site.
I cannot understand what happens.
It really looks like the client doesn't take the configuration at all.
I'm stumped then. My last advice is to look hard and find out if there's
a
On 01/26/2011 01:16 PM, JupiterMoonBeam wrote:
Hi,
We've got our puppetmaster under puppet control and our /etc/puppet
dir tucked safely away in Mercurial.
With the help of the vcsrepo module we're automatically pulling the
latest changes from /etc/puppet giving us a nice little cycle
Brice Figureau brice-pup...@daysofwonder.com writes:
On Tue, 2011-01-25 at 17:11 -0500, Micah Anderson wrote:
Brice Figureau brice-pup...@daysofwonder.com writes:
All four of my mongrels are constantly pegged, doing 40-50% of the CPU
each, occupying all available CPUs. They never settle
On Wed, 2011-01-26 at 09:44 -0500, Micah Anderson wrote:
Felix Frank felix.fr...@alumni.tu-berlin.de writes:
I propose you need to restructure your manifest so that it compiles
faster (if at all possible) or scale up your master. What you're
watching is probably just overload and resource
£10 says we're all missing something really obvious and we'll kick
ourselves afterwards ;)
Adriana, just confirm that in your puppet master's puppet.conf that
you generated with puppetd --genconfig:
manifest = /etc/puppet/manifests/site.pp
That's what comes up for my version of Puppet (2.6.3).
This should work:
package { foo:
ensure = installed
}
package { foo-1.2:
ensure = installed
}
or
package { foo:
ensure = installed
}
package { foo.$architecture:
ensure = installed
}
on CentOS. Possibly other OS's should have similar workaround(s) (not
sure if
The result is the same and no message We're going insane appears.
I am without hope...I don't know..
On Jan 26, 4:38 pm, luke.bigum luke.bi...@fasthosts.co.uk wrote:
£10 says we're all missing something really obvious and we'll kick
ourselves afterwards ;)
Adriana, just confirm that in your
On Wed, 2011-01-26 at 10:11 -0500, Micah Anderson wrote:
Brice Figureau brice-pup...@daysofwonder.com writes:
On Tue, 2011-01-25 at 17:11 -0500, Micah Anderson wrote:
Brice Figureau brice-pup...@daysofwonder.com writes:
All four of my mongrels are constantly pegged, doing 40-50% of the
Nigel Kersten a écrit :
On Mon, Jan 24, 2011 at 12:27 AM, DEGREMONT Aurelien
aurelien.degrem...@cea.fr wrote:
Please take care that, for my site, and I think other ones,
puppetd -t
is *the* way to run puppet.
We never use puppetd in daemonized mode, and manual runs puppet when needed
with
On Wed, 2011-01-26 at 10:11 -0500, Micah Anderson wrote:
http {
default_typeapplication/octet-stream;
sendfileon;
tcp_nopush on;
tcp_nodelay on;
large_client_header_buffers 1024 2048k;
YAML breaks when any of your parameter values end in a colon. I had
tripped this once in the past but pson fixed this for me and so far I
didn't have any further issues. Guess now a bug should be filed after all...
Hmm, 0.24.x used YAML in its communication protocol, right? I have had
that
On Jan 26, 2011, at 8:27 AM, DEGREMONT Aurelien wrote:
Nigel Kersten a écrit :
On Mon, Jan 24, 2011 at 12:27 AM, DEGREMONT Aurelien
aurelien.degrem...@cea.fr wrote:
Please take care that, for my site, and I think other ones,
puppetd -t
is *the* way to run puppet.
We never use
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This is going out on a limb, but is your manifest file in UNIX format?
dos2unix file
And try again.
Puppet will skip files it doesn't understand from what I remember having
made this mistake a couple of times.
Trevor
On 01/26/2011 11:12 AM,
Last job I ran puppet from cron via a wrapper script to allow more
inteligent pre and post actions. In your case I would probably have the
vcsrepo trigger a refreshonly exec to create a flag file on disk.
Then your wrapper can remove the flag and reinvoke puppet to collect the
latest round of
Not totally everything runs on the node: you can use exported resources on
one node, and import them on another, if you have storeconfigs enabled.
I used to use that, last job, to export node information between our site
backup server and nodes at that site.
Regards,
Daniel
--
Puppet Labs
This works:
$ cat foo.pp
define aaa($x=1) {
notice(\$x=$x)
}
class b {
aaa { xxx: x=2 }
}
class c inherits b{
Aaa[xxx] { x=3 }
}
include c
--
But this doesn't:
--
$ cat foo.pp
define scope::aaa($x=1) {
notice(\$x=$x)
}
class b {
On Jan 23, 4:33 pm, Nigel Kersten ni...@puppetlabs.com wrote:
https://projects.puppetlabs.com/issues/2476
This does seem to confuse a fair few new users.
What would be a better name for --test?
What about --manual ?
--
You received this message because you are subscribed to the Google
On Wed, Jan 26, 2011 at 10:18 AM, Rich Rauenzahn rraue...@gmail.com wrote:
class c inherits b{
Scope:aaa[xxx] { x=3 }
}
I remember seeing an example now:
Scope:Aaa[xxx]
-- capitalize both components.
Rich
--
You received this message because you are subscribed to the Google Groups
On Wed, Jan 26, 2011 at 05:27:56AM -0800, Adriana wrote:
Hello,
here it is:
puppetd --server pc03 --test --noop --evaltrace
info: Caching catalog for aldaqpc001.cern.ch
So your puppet master is pc03 and you puppet client is
aldaqpc001.cern.ch. Is this correct?
For the node definition on
On Wed, Jan 26, 2011 at 1:38 AM, Brice Figureau
brice-pup...@daysofwonder.com wrote:
Still there can be some tricky multi-process issues, like the one we
fixed in 2.6:
http://projects.puppetlabs.com/issues/4923
My bugfix for the manifest issue that's blocking me from upgrading to
2.6.x has
Felix Frank felix.fr...@alumni.tu-berlin.de writes:
On 01/26/2011 03:44 PM, Micah Anderson wrote:
Felix Frank felix.fr...@alumni.tu-berlin.de writes:
I propose you need to restructure your manifest so that it compiles
faster (if at all possible) or scale up your master. What you're
Brice Figureau brice-pup...@daysofwonder.com writes:
On Wed, 2011-01-26 at 09:44 -0500, Micah Anderson wrote:
Felix Frank felix.fr...@alumni.tu-berlin.de writes:
I propose you need to restructure your manifest so that it compiles
faster (if at all possible) or scale up your master. What
On Wed, Jan 26, 2011 at 09:46, Trevor Vaughan tvaug...@onyxpoint.com wrote:
G'day Trevor.
This is going out on a limb, but is your manifest file in UNIX format?
dos2unix file
And try again.
Puppet will skip files it doesn't understand from what I remember having
made this mistake a couple
Brice Figureau brice-pup...@daysofwonder.com writes:
On Wed, 2011-01-26 at 10:11 -0500, Micah Anderson wrote:
Brice Figureau brice-pup...@daysofwonder.com writes:
On Tue, 2011-01-25 at 17:11 -0500, Micah Anderson wrote:
Brice Figureau brice-pup...@daysofwonder.com writes:
All four of
On 25 Jan., 15:21, Felix Frank felix.fr...@alumni.tu-berlin.de
wrote:
I am now trying without any module to make debugging easier. I've got
the following:
class afs {
service { openafs-client:
enable = true,
ensure = running,
}
}
class afs_staging inherits afs {
On Wed, 26 Jan 2011, Daniel Pittman wrote:
I would love to create a bug for this, because silently is a bad
thing: we should either work, or complain about not working, not just
silently ignore anything.
See issue #4690 and issue #3514.
--apb (Alan Barrett)
--
You received this message
On Wed, Jan 26, 2011 at 11:42, Jason Wright jwri...@google.com wrote:
On Wed, Jan 26, 2011 at 1:38 AM, Brice Figureau
brice-pup...@daysofwonder.com wrote:
Still there can be some tricky multi-process issues, like the one we
fixed in 2.6:
http://projects.puppetlabs.com/issues/4923
My bugfix
On Wed, Jan 26, 2011 at 1:17 PM, Daniel Pittman dan...@puppetlabs.com wrote:
For what it is worth I have been looking at this quietly in the
background, and come to the conclusion that to progress further I am
going to have to either reproduce this myself (failed, so far), or get
a bit of
On Wed, Jan 26, 2011 at 13:56, Jason Wright jwri...@google.com wrote:
On Wed, Jan 26, 2011 at 1:17 PM, Daniel Pittman dan...@puppetlabs.com wrote:
For what it is worth I have been looking at this quietly in the
background, and come to the conclusion that to progress further I am
going to have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Daniel,
Just for completeness, I saw it using a server/client setup and it was
one of those cases with something trying too hard to be correct which
resulted in the new files just being ignored.
They could be read, so it wasn't a permissions
Thanks for that. Pointers are just as good as details. :)
Daniel
On Wed, Jan 26, 2011 at 20:20, Trevor Vaughan tvaug...@onyxpoint.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Daniel,
Just for completeness, I saw it using a server/client setup and it was
one of those
On Jan 26, 1:58 am, Jakub Pastuszek jpastus...@newbay.com wrote:
Is it possible to tell Puppet to ensure a package is installed before
using a custom provider that needs it for operation?
Or I need to make sure that base OS contains all the commands that any
provider may ever need?
I seem to
On Jan 26, 9:20 pm, donavan dona...@desinc.net wrote:
A common pattern to work around this is to use a 'boot strap' when
provisioning a node. This boot strap only contains enough resources to
get the machine, and puppet, to a workable state. After that a second
'full' run is done which applies
On Jan 26, 4:16 am, JupiterMoonBeam jupitermoonb...@googlemail.com
wrote:
However, there's a delay of one run between changes (as the repo gets
updated but the current run is still under the old config). Is there
anyway of getting puppet to rerun with the new config when the repo
changes?
As
I'm trying to make puppet disable and stop some services on a bunch of Debian
boxes, but I'm running into some problems.
The puppet server is running 2.6.4, downloaded from puppetlabs.com, the Deb5
clients do as well, while the Deb6 clients use 2.6.2 as shipped in the Deb6
repos(though I did
58 matches
Mail list logo
