Nat wrote:
has anyone else experienced puppet clients that die when the network goes
down for an extended period of time ?
That happens here as well. We even have a script to monitor last_run
times of all puppet clients to detect this.
It seems that a puppet master not answering for some tim
Hi
as far as I understood was that the zpool information was lost, hence
puppet thought that there was no zpool anymore. I assume that this means
that zpool-tools didn't know about that anymore either, but it might
have been recoverable with manual interaction.
That's what happened. Actually, it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 7/04/10 10:55 AM, Baker, Luke Jefferson wrote:
> RHEL5.5 (beta) x86_64. It did not prompt to sign the GPG key.
>
It appears from discussion with some RH/Fedora packagers that GPG
signing changed between older RH/Fedora versions and newer ones and
- "Peter Meier" a écrit :
|
| as far as I understood was that the zpool information was lost, hence
| puppet thought that there was no zpool anymore. I assume that this
| means
| that zpool-tools didn't know about that anymore either, but it might
| have been recoverable with manual interacti
Does your logs say anything about puppetd dieing during the network
outage?
On 7 apr, 07:09, Nat wrote:
> Hi list,
>
> has anyone else experienced puppet clients that die when the network goes
> down for an extended period of time ?
>
> OS rhel 5
> puppet clients / master 0.25.1
>
> clients are l
Ah of course! I were testing this first with one node, then on the
puppetmaster I added File <<| title == "list-updates" |>>, which of
course is acceptable since it only sees one File[X] resource, but when
i added the list-updates class on the puppetmaster, it sees two.
Thanks alot Ken :)
On 7 ap
Hi list,
has anyone else experienced puppet clients that die when the network goes
down for an extended period of time ?
OS rhel 5
puppet clients / master 0.25.1
clients are left in a state where
~# service puppet status
puppetd dead but pid file exists
~# service puppet restart
Stopping puppet:
Alan Sparks wrote:
> I'm trying to create an exported file resource and receiving a vague
> error message:
> Apr 5 18:01:04 ny4-dev-util01 puppetd[12860]: Could not run Puppet
> configuration client: You cannot specify more than one of content,
> source, target at line 102
>
> A puppet client (it'
On Sat, Apr 3, 2010 at 3:46 AM, Eric Shamow wrote:
> A not-so-elegant solution is to write your own yum provider that
> allows you to do this. In my case I found one online -- if you google
> yum_plus.rb you should be able to find it. If not let me know and
> I'll post the work here.
>
> On Thu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 7/04/10 10:38 AM, Michael DeHaan wrote:
> On Tue, Apr 6, 2010 at 3:48 AM, James Turnbull
> wrote:
>> Hi all
>>
>> I've created RPM and DEB packages for the Puppet Dashboard 1.0.0rc1.
>> These are available via APT and Yum repositories hosted by Pu
RHEL5.5 (beta) x86_64. It did not prompt to sign the GPG key.
On Apr 6, 2010, at 19:35, "James Turnbull"
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 6/04/10 11:07 PM, Baker, Luke Jefferson wrote:
>> I tried installing via yum, received this error concerning the
>> packag
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 7/04/10 10:38 AM, Michael DeHaan wrote:
> On Tue, Apr 6, 2010 at 3:48 AM, James Turnbull
> wrote:
>> Hi all
>>
>> I've created RPM and DEB packages for the Puppet Dashboard 1.0.0rc1.
>> These are available via APT and Yum repositories hosted by Pu
On Tue, Apr 6, 2010 at 3:48 AM, James Turnbull wrote:
> Hi all
>
> I've created RPM and DEB packages for the Puppet Dashboard 1.0.0rc1.
> These are available via APT and Yum repositories hosted by Puppet
> Labs.
Cool.
A puppetlabs-release RPM might be nice for this.
--Michael
--
You received
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 6/04/10 11:09 PM, Daniel Kerwin wrote:
> Do you have something like a release tarball? I'd like to create a
> Gentoo ebuild for it.
>
http://yum.puppetlabs.com/sources/
Regards
James Turnbull
- --
Author of:
* Pro Linux System Administration (
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 6/04/10 11:07 PM, Baker, Luke Jefferson wrote:
> I tried installing via yum, received this error concerning the package
> signature..
>
> error: rpmts_HdrFromFdno: Header V4 RSA/SHA1 signature: BAD, key ID 8347a27f
What platform is this? Did it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi
> On Tue, Apr 6, 2010 at 10:52 AM, Kaspar Schiess wrote:
>> Creating zpools is a manual thing in every case, since one has to know the
>> devices participating. The names of which tend to be a little bit different
>> from one server to the next.
>
You've got to think about it from the servers perspective ... its
going to see many File["list-update"] resources ... one for each
machine in fact. Which is why you're getting that error. Each machines
definition is trying to overwrite the other:
@@file { "list-updates":
ensure => present
Looks like you are right. Line 892 from puppet/util/settings.rb:
text.split(/\n/).each { |line|
Its splitting on line feed. I'd raise a ticket if I was you - seems
like a trivial change to that regular expression.
Also - I think the puppet configuration doesn't throw errors when its
wron
I found the problem. My puppet.conf somehow got checked into SVN with
CR/LF line endings. Apparently this causes puppet to fail to read it,
quite silently even with --debug unfortunately.
On Apr 6, 11:59 am, byron appelt wrote:
> Thanks, testing other settings was an excellent suggestion. It seem
Is there any objection to the ports provider being disabled on FreeBSD systems since it
mostly just causes puppet to hang anyway? I've had no luck in fixing it. The problem is
that portupgrade and script don't interact well when running non-interactively.
I've been running it this way in a loca
On Tue, Apr 6, 2010 at 10:52 AM, Kaspar Schiess wrote:
> Creating zpools is a manual thing in every case, since one has to know the
> devices participating. The names of which tend to be a little bit different
> from one server to the next.
Wow, so I've got a fairly large Solaris 10 server deploy
Kaspar Schiess wrote:
Hi everyone,
Just wanted to tell you a little story. We've been enthusiastic puppet
users since about a year ago here at the Geographic Institute of the
University of Zürich.
But we won't use the zpool type ever again. Its just not worth it.
Here's what happened:
. o
Peter Meier wrote:
Hi
But we won't use the zpool type ever again. Its just not worth it.
Here's what happened:
. one of our servers lost knowledge about one of its zfs pools
. puppet didn't find the pool and .. went on to zpool create it
. we did indeed have a backup, but would have lost all
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
Thanks, testing other settings was an excellent suggestion. It seems
no settings in my puppet.conf are working. Any suggestions on how to
debug this? This was all working before I upgrading from 0.24.5 to
0.25.4 For reference, here are my configs, although it seems that the
client config is not eve
Hi
But we won't use the zpool type ever again. Its just not worth it.
Here's what happened:
. one of our servers lost knowledge about one of its zfs pools
. puppet didn't find the pool and .. went on to zpool create it
. we did indeed have a backup, but would have lost all data if not
Creati
Hi everyone,
Just wanted to tell you a little story. We've been enthusiastic puppet
users since about a year ago here at the Geographic Institute of the
University of Zürich.
But we won't use the zpool type ever again. Its just not worth it.
Here's what happened:
. one of our servers lost
On Tue, 6 Apr 2010 17:48:42 +1000, James Turnbull
wrote:
> Hi all
>
> I've created RPM and DEB packages for the Puppet Dashboard 1.0.0rc1.
> These are available via APT and Yum repositories hosted by Puppet
> Labs. These are "first release" packages and I am by no means a
> packaging expert with
Hi,
I've runned into a fairly common problem:
err: Could not retrieve catalog from remote server: Error 400 on
SERVER: Exported resource File[list-updates] cannot override local
resource on node X
http://projects.puppetlabs.com/projects/puppet/wiki/Frequently_Asked_Questions
I cannot see how I ca
Do you have something like a release tarball? I'd like to create a
Gentoo ebuild for it.
On Tue, Apr 6, 2010 at 3:07 PM, Baker, Luke Jefferson
wrote:
> I tried installing via yum, received this error concerning the package
> signature..
>
> error: rpmts_HdrFromFdno: Header V4 RSA/SHA1 signature:
I tried installing via yum, received this error concerning the package
signature..
error: rpmts_HdrFromFdno: Header V4 RSA/SHA1 signature: BAD, key ID 8347a27f
-Original Message-
From: puppet-users@googlegroups.com [mailto:puppet-us...@googlegroups.com] On
Behalf Of James Turnbull
Sent:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The only way that I know to do this is to make your reverse lookup match
your CNAME (which doesn't really make it act like a CNAME at that point).
The reverse lookup is what matters to the certs, not the forward.
Trevor
On 04/05/2010 05:12 PM, Brian
2010/4/2 smain kahlouch
>
>
> 2010/4/1 smain kahlouch
>
>
>>
>> 2010/4/1 Smain Kahlouch
>>
>> Message initial
>>> De: Michael DeHaan
>>> Reply-to: puppet-users@googlegroups.com
>>> À: puppet-users@googlegroups.com
>>> Cc: James Turnbull
>>> Sujet: Re: [Puppet Users] Mongrel
Hi all
I've created RPM and DEB packages for the Puppet Dashboard 1.0.0rc1.
These are available via APT and Yum repositories hosted by Puppet
Labs. These are "first release" packages and I am by no means a
packaging expert with either DEBs or RPMs so any feedback or comments
are welcomed. I'll co
Yes in theory. Depending on the section you put it in of course. I
have pluginsync=true in the [main] section of my puppet.conf, on both
my client and server and sync works fine.
Can you post your full configuration? Both client and server? Can you
confirm your other settings are working when you
I would do more experimentation on your resource temporarily to find
the problem. For example:
* Set 'ensure' explicitly to 'file'. Not a var (or remove it entirely
if you are unsure). If it is interpreting that as a path it will try
to install a symbolic link which may be giving you the error you
36 matches
Mail list logo
