Well, I've worked around this for now by:
- uninstalling puppet and facter with mac ports (so there's no
puppetfoo executables under /opt/local/sbin or /opt/local/bin anymore
- used gem to install puppet and facter into the system ruby, so now
the executables are under /usr/bin/puppetfoo
This als
On 16 June 2010 10:13, Nigel Kersten wrote:
>
>
> On Tue, Jun 15, 2010 at 4:13 PM, Eric Sorenson wrote:
>>
>> I have seen this too; I suspect (but have not been able to reduce a simple
>> test case to confirm) that the ruby-openssl bindings in snow leopard are
>> returning EINVAL (thus the "Inval
It is happening on 0.25.5-1 server, but so far I have only seen the
problem on 0.24.X clients. I don't have an 0.25.4 master to test
against, but at any rate I am unable to reproduce the problem. The
problem seems to have occurred in a relatively small time across the
affected clients, and hasn't
if this happens on a 0.25.5 server (and maybe client), it might be happening
because of the zaml implementation, can you reproduce this problem with
0.25.4 master?
in anycase, it sounds like a bug :)
Ohad
On Wed, Jun 16, 2010 at 9:35 AM, Nigel Kersten wrote:
>
>
> On Tue, Jun 15, 2010 at 6:32
Hi Morgan,
You actually want that once a client started to communicate with a master,
it should keep on connecting to the same master for the duration of its run.
esp in 0.24.x, the only way for a server to know in which environment the
client is, is by looking at its cache (created when the fact
The ip address does not really matter, if you want to force your own
certificate names, you can use the certname option instead on relaying on
facter to resolve the fqdn fact for you.
Ohad
On Wed, Jun 16, 2010 at 3:12 AM, Daniel De Marco wrote:
> Hi,
>
> I'm starting to look into puppet to manag
On Tue, Jun 15, 2010 at 6:32 PM, donavan wrote:
> On Jun 15, 2:39 pm, "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/shado
On Jun 15, 2:39 pm, "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::Ba
On Jun 14, 11:07 pm, Gabriel Filion wrote:
> bug or missing feature.. I haven't tried it with 0.25.5, though. I'm on
> Debian unstable, using the puppet/puppetmaster packages, so the version
> is 0.25.4
>
> should I open a bug report about this?
Take a look on puppet-dev group and the issues db.
Hi,
I'm trying to set it up so that my puppet clients can connect to any
of a group of puppetmasters set up with aliases to a common hostname
and DNS round-robin. The round-robin setup seems to be working, as I
can see ping, gethostbyname, etc connecting cyclically to each of the
puppetmasters.
Hi Eric
I would have thought I was using the ruby and OpenSSL that mac ports
had compiled for me, not the os's ruby OpenSSL bindings...? Or have I
misunderstood you?
Jesse Reynolds
On 16/06/2010, at 8:43 AM, Eric Sorenson wrote:
I have seen this too; I suspect (but have not been able
On Tue, Jun 15, 2010 at 4:13 PM, Eric Sorenson wrote:
> I have seen this too; I suspect (but have not been able to reduce a simple
> test case to confirm) that the ruby-openssl bindings in snow leopard are
> returning EINVAL (thus the "Invalid argument" string) when called from
> puppet. But it s
Yeah, it's nasty.
Running the puppet commands you listed doesn't show any problems. The
logs show the password being set correctly, but it isn't really. Once
I manually change the password, then puppet can make those password
changes again.
It looks like the problem may be limited to my clients w
On Tue, Jun 15, 2010 at 3:04 PM, Richard Crowley wrote:
> On Tue, Jun 15, 2010 at 2:27 PM, 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.
>
> There's only the monolithic gem as f
I have seen this too; I suspect (but have not been able to reduce a simple test
case to confirm) that the ruby-openssl bindings in snow leopard are returning
EINVAL (thus the "Invalid argument" string) when called from puppet. But it
seems the transaction actually succeeds despite the error. Whe
On 16 June 2010 00:50, Nigel Kersten wrote:
> On Tue, Jun 15, 2010 at 7:57 AM, Jesse Reynolds
> wrote:
>> On 16 June 2010 00:06, James Turnbull wrote:
>>> Looks like you've got some old code floating around. I'd remove all of
>>> Puppet and then re-install.
>>
>> OK, I'll have a big hunt.
>>
>>
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
On Tue, Jun 15, 2010 at 12:12 PM, Daniel De Marco wrote:
> I'm starting to look into puppet to manage a bunch of linux desktops.
> They all use dhcp and their IP addresses are not fixed.
>
> I'm thinking of fixing the hostnames of the machines to some non-existent
> domain and then using puppet no
On Tue, Jun 15, 2010 at 2:27 PM, 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.
There's only the monolithic gem as far as I've ever been able to find,
which is what I use because th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> The strange thing is, if I run puppetd at a command prompt or with the
> 'at' command, I don't get the error. I only get it when running from
> cron.
>
> Any ideas?
maybe a $PATH issue? is the gem command in a standard location?
cheers pete
-
Really. I think the *.gem is convenient. However, the args to
install.rb (puppet) don't seem to indicate one or the other (server/
client):
Usage: install.rb [options]
--[no-]rdoc Prevents the creation of RDoc
output.
Default on.
Hi,
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
That has effectively broken the use
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
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.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@goog
I just upgraded from 0.25.2 to 0.25.5 and now I get this:
...
debug: Prefetching gem resources for package
debug: Puppet::Type::Package::ProviderGem: Executing ' list --local'
warning: Could not match /usr/local/lib/ruby/gems/1.8/gems/
puppet-0.25.5/lib/puppet/util.rb:307: [BUG] rb_sys_fail() - err
On Tue, Jun 15, 2010 at 12:41 PM, Ben Beuchler wrote:
> I had two problems. Nigel and Daniel correctly identified one of them
> and Jonathan contacted me off-list to point out that I can't have my
> custom type living in a subdir of "lib/puppet/type". I moved
> haddock.rb from lib/puppet/type/h
I had two problems. Nigel and Daniel correctly identified one of them
and Jonathan contacted me off-list to point out that I can't have my
custom type living in a subdir of "lib/puppet/type". I moved
haddock.rb from lib/puppet/type/haddock/haddock.rb to
lib/puppet/type/haddock.rb, created a symli
>> A quick look in $libdir (/var/lib/puppet/lib) shows my custom types are
>> there.
>
> Sorry, I wasn't quite clear. You need to make this accessible to the
> libdir on the *server*.
>
> So whatever your puppetmasterd libdir is, you need to somehow ensure
> the types/providers are there. We do it
Hi,
I'm starting to look into puppet to manage a bunch of linux desktops.
They all use dhcp and their IP addresses are not fixed.
I'm thinking of fixing the hostnames of the machines to some non-existent
domain and then using puppet normally. In this way even if their IP
address changes from ti
Hmm, maybe I am just going insane. I will go through everything again to be
sure that this isn't happening.
On Tue, Jun 15, 2010 at 11:30 AM, Peter Meier wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi
>
> > default HTTPD is enabled by default, even though none of my classes
> >
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> As you can see, "some stuff" requires service1 to be stopped, so it
> brings service1 down (dirty/ugly) itself.
> I tried some other tricks as well (creating second service block) but
> puppet is smart enough to see I'm aliasing service1 in that case
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi
> default HTTPD is enabled by default, even though none of my classes
> are doing it. I setup another class to disable this by default, but
> seems me that there should be better way to do this.
puppet doesn't manage anything automatically, it on
Hi I have puppet fully functional, but I have one issue that I can't
seem to be able to solve.
default HTTPD is enabled by default, even though none of my classes
are doing it. I setup another class to disable this by default, but
seems me that there should be better way to do this.
Here is what
On Tue, 15 Jun 2010, Nigel Kersten wrote:
> > UNCONFIGURED/site.pp contains little more than a "fail" statement.
> >
> > My external node classifier forces environment = UNCONFIGURED
> > for any client that it doesn't know about.
>
> You're not actually doing any work in this environment though ar
Having tried both I settled on Foreman, although I haven't checked out
Puppet-Dashboard after the 1.0 release.
Foreman just provides more information, I find, although
Puppet-Dashboard looks slightly slicker. Foreman also seems easily
hackable/extensible and comes with a nice query tool.
-Eric
On Tue, Jun 15, 2010 at 9:23 AM, Alan Barrett wrote:
> On Tue, 15 Jun 2010, Nigel Kersten wrote:
>> >> I dislike setting a default modulepath, as it means that's the one
>> >> clients get if they incorrectly specify their environment.
>> >
>> > I mitigate that by also doing
>> >
>> > manifestdi
On Tue, 15 Jun 2010, Nigel Kersten wrote:
> >> I dislike setting a default modulepath, as it means that's the one
> >> clients get if they incorrectly specify their environment.
> >
> > I mitigate that by also doing
> >
> >manifestdir = /dev/null
> >manifest = /dev/null/site.pp
>
> Are you
Hi Guys,
I'm reading about dashboard and foreman, and I'm wondering if there is
anyone who made a comparison of the two? Can anyone help me decide
which one to use? It feels like foreman is 'ahead' for now?
cheers,
Walter Heck
Engineer @ OlinData (http://olindata.com)
--
You received this mess
I have some software with a list of patches that need to be installed in
order. Different hosts want different patches (e.g. development hosts
get patches that are not yet ready for production).
Obviously I can do this:
package { "basepackage":
ensure => present,
}
package {
On Tue, Jun 15, 2010 at 7:57 AM, Jesse Reynolds
wrote:
> On 16 June 2010 00:06, James Turnbull wrote:
>> Looks like you've got some old code floating around. I'd remove all of
>> Puppet and then re-install.
>
> OK, I'll have a big hunt.
>
> I've tried uninstalling puppet with mac ports and re-in
On 2010-06-15 17:07, Nigel Kersten wrote:
On Tue, Jun 15, 2010 at 7:58 AM, Thomas Bellman wrote:
I mitigate that by also doing
manifestdir = /dev/null
manifest = /dev/null/site.pp
Are you using an external node classifier? I thought that when I
deployed a classifier it stopped th
On Tue, Jun 15, 2010 at 7:58 AM, Thomas Bellman wrote:
> On 2010-06-15 16:20, Nigel Kersten wrote:
>
>> On Tue, Jun 15, 2010 at 1:00 AM, Thomas Bellman
>> wrote:
>
>>> I think it is sufficient to set modulepath under [puppetmasterd] in
>>> the puppet.conf file. I do:
>>>
>>> [puppetmasterd]
>
On 2010-06-15 16:20, Nigel Kersten wrote:
On Tue, Jun 15, 2010 at 1:00 AM, Thomas Bellman wrote:
I think it is sufficient to set modulepath under [puppetmasterd] in
the puppet.conf file. I do:
[puppetmasterd]
modulepath = /config/e/production/modules
...
I dislike se
On 16 June 2010 00:06, James Turnbull wrote:
> Looks like you've got some old code floating around. I'd remove all of
> Puppet and then re-install.
OK, I'll have a big hunt.
I've tried uninstalling puppet with mac ports and re-installing, doesn't help.
I've done a find over the whole filesyste
Jesse Reynolds wrote:
> Hello
>
> I have a puppetmasterd installation running on a Mac OS X 10.6.3
> Server with puppet installed via macports.
>
> Earlier today it was happily signing requests, before I upgraded
> puppet from 0.24.8 to 0.25.4. Now I get "Invalid argument":
>
> bash-3.2# puppetc
Hi all,
I would like to reference a resource twice, with different
configurations.
At the moment I do this:
service { "service1":
ensure => running,
enable => true,
require => Exec["some stuff"]
}
exec { "some stuff":
command => "/etc/init.d/service1 stop; do some stuff required for
serv
Hello
I have a puppetmasterd installation running on a Mac OS X 10.6.3
Server with puppet installed via macports.
Earlier today it was happily signing requests, before I upgraded
puppet from 0.24.8 to 0.25.4. Now I get "Invalid argument":
bash-3.2# puppetca --sign bouti.carbonplanet.com
bouti.ca
On Tue, Jun 15, 2010 at 1:00 AM, Thomas Bellman wrote:
> On 2010-06-15 01:21, Nigel Kersten wrote:
>
>> Sorry, I wasn't quite clear. You need to make this accessible to the
>> libdir on the *server*.
>>
>> So whatever your puppetmasterd libdir is, you need to somehow ensure
>> the types/providers
I've seen the workarounds to use the concatenated file resource to fake this,
but is it possible to use something like virtual resources to realize an
array? My pseudo-classes would be like this:
class foo {
@$arr = ['a', 'b']
realize($arr)
}
class foo::c inherits foo {
$arr += ['c']
}
c
Hi.
We're going to set up Puppetmaster and Dashboard, and would like to
automate the installation process. Have anyone made scripts or puppet
manifests for installing these and would like to share?
- kenneho
--
You received this message because you are subscribed to the Google Groups
"Puppet
Hello,
I just successfully installed puppet-dashboard on a lenny server, using
apache/passenger. It works fine, but I just found out that there's a problem
with the time dashboard shows : it's 2 hours late.
Is there a place to set timezone or something like that ? server has the right
time, so
On Tue, 15 Jun 2010 01:08:59 -0700
James Turnbull wrote:
> Cedric Jeanneret wrote:
> > Hello,
> >
> > Any new for the sources ? It seems we cannot retrieve them - apt-get
> > source puppet-dashboard returns "no source for puppet-dashboard"...
> > We'd like to package it for our lenny servers...
On 14.06.2010 22:14, Brian Gallew wrote:
I've got a generic user "java" that owns Java applications. Due to
circumstances beyond my control, I cannot dictate a change here, so I
need to make Puppet work with the infrastructure on hand. The big
problem, though, is that java's home directory vari
Cedric Jeanneret wrote:
> Hello,
>
> Any new for the sources ? It seems we cannot retrieve them - apt-get
> source puppet-dashboard returns "no source for puppet-dashboard"...
> We'd like to package it for our lenny servers...
>
> I saw that Stu Teasdale wanted to create some lenny packages[1] (a
On 2010-06-15 01:21, Nigel Kersten wrote:
Sorry, I wasn't quite clear. You need to make this accessible to the
libdir on the *server*.
So whatever your puppetmasterd libdir is, you need to somehow ensure
the types/providers are there. We do it with symlinks.
I think it is sufficient to set mo
55 matches
Mail list logo
