I would love to take a look at your module.
On Tuesday, 20 January 2015 07:46:57 UTC-5, Dirk Heinrichs wrote:
>
> Am 20.01.2015 um 13:39 schrieb Don Dorman:
>
> Has anyone found documentation on upgrading Puppet 3.4.3 to Puppet
> 3.6.2. running on RHEL 6.4
>
>
> First
puppetdb-2.0.0-1.el6.noarch.rpm
and the obvious yum upgrade puppet-3.6.2-1.el6.noarch.rpm
On Tuesday, 20 January 2015 07:46:57 UTC-5, Dirk Heinrichs wrote:
>
> Am 20.01.2015 um 13:39 schrieb Don Dorman:
>
> Has anyone found documentation on upgrading Puppet 3.4.3 to Puppet
> 3.
Has anyone found documentation on upgrading Puppet 3.4.3 to Puppet 3.6.2.
running on RHEL 6.4
I have found some documents, but nothing simple and clearly defined.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group
Good morning everyone.
I am looking to create a puppet 3.2.4 modules to scan all available IP
routes across a lot os servers, and to save the information to a report.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this gro
My environment has been working up until mid last week.
just doing a puppet agent --test gives me these results... has anyone ran
across this.
[root@DC01SLE0005 ~]# puppet agent --test
Warning: Unable to fetch my node definition, but the agent run will
continue:
Warning: SSL_connect returned=1
You will find this works great.
http://devsops.blogspot.ca/2013/04/installing-puppet-dashboard.html
On Thursday, June 5, 2014 2:15:48 PM UTC-4, Don Dorman wrote:
>
> I almost have it figured out, and of course I will share the information
>
> On Thursday, June 5, 2014 11:55:35 AM
I almost have it figured out, and of course I will share the information
On Thursday, June 5, 2014 11:55:35 AM UTC-4, Kwame Bahena wrote:
>
> Ah,
>
> Can you please then share your config and the steps you are following?
>
>
> Cheers!
>
>
> On Thu, Jun 5, 2014 at
Thanks so much for the link, but I am testing the opensource version of
Puppet. A lot of the directory structure is much different.
On Thursday, June 5, 2014 10:27:56 AM UTC-4, Don Dorman wrote:
>
> Good morning Everyone.
>
> I have been struggling to change the default port f
Good morning Everyone.
I have been struggling to change the default port for Dashboard access from
port 3000 to use SSL port 443. My Dashboard version is 1.2.34 if I am
not mistaken.
My OS is RHEL 6.4, Puppet Master 3.42-1
Any directions would be great.
--
You received this message becau
I tried two of the proposed fixes in github, but neither of them worked. I
came up with the following workaround (kludge) that happens to work because
our proxy caches the authentication for a little while. Maybe it will help
someone out there who is brought here by the magic Google machine:
Trying to get puppet & factor working on SmartOS. Installed first from pkgsrc,
then upgraded puppet via gem.
Puppet itself seems to run OK (but haven't applied a manifest yet...)
Facter fails:
# facter Error: invalid byte sequence in UTF-8
# facter --debug Not an EC2 host Error: invalid byte
Here's a patch to make puppet do integer comparison instead of string
comparison if both strings are valid integers:
--- OLD/site_ruby/1.8/puppet/provider/augeas/augeas.rb 2013-09-19
14:09:52.0 -0400
+++ NEW/site_ruby/1.8/puppet/provider/augeas/augeas.rb 2013-09-19
16:23:48.0
on/certificate_request/vm1340701.bwi40g.vzbi.caas HTTP/1.1" 405
373 "-" "-"
Any ideas on what to do next?
Thanks,
Don
On Friday, May 31, 2013 5:05:20 PM UTC-4, Jonathan wrote:
>
> I found a solution for this...use an older version of Passenger,
> specifically Passenger 3.
Ok, here's the report processor to send events to Zenoss, based off
James' Zendesk module.
https://github.com/donjohnson/puppet-zenoss
-Don
Release Engineer / Toolsmith, VerticalResponse
On Wed, Jun 8, 2011 at 6:09 PM, Don wrote:
> Thanks for the help off-list, James.
>
>
|| 'alert' || 'emerg' || 'crit'
failure = true
end
end
if failure
Puppet.debug "Creating Zenoss event for failed run on #{self.host}."
###
This definitely costs a few more cycles than with 2.6.5+.
I'll publish the rest of the
James,
This is all wonderfully helpful and I just spent a little time writing
up a Zenoss processor to send an event on failure using
XMLRPC::Client, modeled directly after your puppet-zendesk module,
replacing the HTTParty guts with XMLRPC guts. I've encountered a
problem though (and we can refer
(possible double-post)
James,
This is all wonderfully helpful and I just spent a little while
writing up a Zenoss processor to send an event on failure using
XMLRPC::Client, modeled directly after your puppet-zendesk module,
replacing the HTTParty guts with XMLRPC guts. I've encountered a
problem
I make user of the puppet fileserving capability to serve up configs and
smaller executables I need on my deployed servers.
Sometimes I populate directories to be served on the puppetmaster via
subversion.
When I recursively populate this kind of directory via puppet, it brings over
the .svn
implementation of puppet….
Don
--
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...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.
My manifest includes this snippet
class app_client_openbsd {
$app_client_pkgs_obsd = [ 'glib2-2.24.1p2', 'gtar-1.23p1' ]
package { "${app_client_pkgs_obsd}":
ensure => 'installed',
source =>
"http://${installserver}/openbsd/${operatingsystemrelease}/packages/${hardwaremodel}/${name}.
pet manifest.
So, what I prefer to do, is tell puppet:
Create a directory, and fill it with all contents of a comparable
directory on the puppet file server.
And then create links from the parent directory into this managed subdirectory.
> On Dec 3, 2010, at 12:48 PM, Don Jackson
So here is a scenario:
I have a directory:
./foo
./foo/file1
./foo/file2
./foo/file3
…
./foo/fileN
I populate this directory on a configured machine via a recursive file resource.
What I would like to do is create a symlink from the parent direct
I am attempting to use install some macports packages via puppet:
My manifest looks like this:
$macportsineed = [ 'ncftp', 'git-core' ]
package { $macportsineed :
ensure => 'installed',
provider => 'darwinport',
}
Here is the message I get from puppetd:
debug: Puppet::Type::Packag
drive generation of puppet cert on that, and blast/install/configure away.
This seems like a significant improvement to me.
Don
On Oct 15, 2010, at 1:48 PM, Nigel Kersten wrote:
> On Fri, Oct 15, 2010 at 11:57 AM, Nigel Kersten wrote:
>> On Thu, Oct 14, 2010 at 10:23 PM, Don Jackson
node specification in the
manifest?
I put
node '00:1f:5b:f8:23:f8' { }
in my manifest, and it was very unhappy.
Any advice about how I can accomplish what I am trying to do?
Thanks,
Don
--
You received this message because you are subscribed to the Google Groups
"
the manifest
if $zabbix_user != "zabbix" {
user
{ "zabbix":
name => 'zabbix',
.
}
}
This worked in the tests I ran.
Thanks again for your feedback
Don
--
You received this message because you are subscribed to the Google Groups
"Pu
eturned 8: usermod: user zabbix is currently logged in
So it seems that I need some way of testing for user zabbix on the
clients, but I can't figure out how. This seems such a basic and
easy thing to do that I surprised that I have not already found the
answer.
Thanks for any suggestions.
D
On Jul 13, 2010, at 5:20 PM, Jeff McCune wrote:
> On Tue, Jul 13, 2010 at 5:00 PM, Don Jackson
> wrote:
>> It seems like the package provider is not seeing that sudo is already
>> installed….
>> How can I fix that?
>>
>> Both my puppetmaster and puppetd ar
On Jul 13, 2010, at 5:20 PM, Jeff McCune wrote:
> On Tue, Jul 13, 2010 at 5:00 PM, Don Jackson
> wrote:
>> It seems like the package provider is not seeing that sudo is already
>> installed….
>> How can I fix that?
>>
>> Both my puppetmaster and puppetd ar
}
The package is installed, but every time puppetd executes, I get this:
notice: //base_server/Package[sudo]/ensure: created
It seems like the package provider is not seeing that sudo is already
installed….
How can I fix that?
Both my puppetmaster and puppetd are 0.25.5
Thanks
On Jun 21, 2010, at 1:02 AM, christian wrote:
>
> Btw, how is the time created that the dashboard for the reports shows?
> All our servers run on CEST but the dashboard seems to use the WAT
> timezone (CEST -2 hours). The timestamps that appear in the report
> files are all correct.
Yes, I have
separated
path, puppetmasterd died/crashed.
I am running puppet version 25.5 on OpenBSD (4.6) (Yes, I built new packages
from the tip of OpenBSD port tree), and dashboard 1.0.0
I would definitely appreciate any advice as to what I am doing wrong….
Don
On Dec 17, 2009, at 10:04 AM, tomholl
On May 5, 2010, at 9:02 AM, seph wrote:
> Geoff Crompton writes:
>
>> This might be a crazy idea, but it just popped into my head, and I
>> wanted to know if it's possible. Perhaps not possible right now, but
>> possible in a theoretical sense.
>>
>> Is it possible that puppet could be modifie
that the puppetmaster needs to connect
>to port 8139 of the machine running puppetd.
I wasn't able to find this clearly documented, hence this email.
Regards,
Don
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this grou
Sigh- typo'd again.
That should have read:
> class roles::ntpmaster {
> include ntp::master
> }
-Don
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to t
master inherits zonenyc {
$ntp_servers = ['pool.ntp.org']
include roles::general
include roles::ntpmaster
}
This isn't nearly as clean as it could be if some of the variable and
scoping rules were different, but for now it has su
les::general
include roles::ntpmaster
}
It's not nearly as clean as I would like, but at least I can override
variables and accomplish most of what I want to do.
-Don
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
way it was
sometimes. Scoping makes sense in a lot of languages, but here it just
seems to get in the way. Ditto for the declarative nature of the
language.
-Don
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
&q
#x27;,
> 'ldaptest2.example.com']
>
> }
>
> node host1.nyc.example.com {
> include zones::global
> include zones::nyc
>
> include roles::general
> include roles::ldapserver
>
> $ldap_servertype = "
The
puppet books talks about workarounds for some of these problems.
Should we be working around these issues or do they need to be
"fixed"?
Perhaps there is a serious implication for the language that I've
completely missed- if so- please let me know.
-Don
--~--~-~--~~-
a?
Without the above sort of hierarchy I'm going to end up with a jumble
of logic statements and node descriptions that could otherwise be made
incredibly simple.
What am I missing?
-Don
--~--~-~--~~~---~--~~
You received this message because you are subscribed
"ntp")
I considered doing that but it just feels like a lot of work for
something I think should just be part of the language.
Thanks for all the good tips everyone.
-Don
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
ACL's for the clients, and different masters
and such for the servers.
In the end we come back to the same sort of problem though- It's not
possible to override values, and so we define everything backwards.
That, plus the scoping rules, makes it (to me at least) very difficult
to build a nice c
appreciate.
If I'm trying to go about this all wrong and someone can explain the
error of my ways, that too would be appreciated.
-Don
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Puppet Users" gro
enode {
include ntp
}
node xyz inherits basenode {
}
Now if I do this for my NTP master:
node ntpmaster inherits basenode {
include s_ntp
}
I'm going to have two NTP files. Is there a way to excude the earlier
definition of NTP so I'm not trying to
ment. I'd like to get it right (or
as close as possible) the first time.
Thanks,
-Don
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to pup
Apparently I wasn't generating new client certs/private_keys correctly
somehow.
I've attempted to capture that knowledge in a shell script, so that
part of the procedure is repeatable/consistent/correct...
Apologies for the noise to the list... :-(
Don
I am havin
out what I am doing wrong, and/or things I could do to
debug this problem?
Thanks,
Don
Machine that doesn't work:
=
debug: Creating default schedules
debug: Failed to load library 'shadow' for feature 'libshadow'
debug: Failed to load librar
t;puppet:///myconfigfiles/foo/bar.txt
Meaning go get foo/bar.txt from the module myconfigfiles
Or is the source directive restricted to just getting files directly
(not in a subdirectory) of the specified path?
Don
--~--~-~--~~~---~--~~
You received this
I do not have postfix on
> my servers, but I can do 'svcadm enable smtp'
>
> The enable => true means to execute the 'svcadm enable $name'
I implemented both your suggestions, and it worked!
Thank you!
Don
>>
>> Hello,
>>
>> I am a puppet newbi
ng'
debug: Finishing transaction 74115530 with 1 changes
debug: Storing state
debug: Stored state in 0.02 seconds
notice: Finished catalog run in 1.16 seconds
But after the puppetd run, postfix is NOT running on the machine.
Any advice appreciated.
Don
--~--~-~--~~---
On Feb 21, 2009, at 7:06 PM, AJ Christensen wrote:
> My 2c on the matter is that JSON is the fastest, most portable, and
> supports all of the big boy data structures.
I'd vote for JSON also.
--~--~-~--~~~---~--~~
You received this message because you are subscr
ent for any variables
whose names start with ‘FACTER_’ (case insensitive)
and automatically add those facts.
Perhaps the right thing to do is prepend FACTER_ to all the fact names
for the shell output format.
I also think JSON would be very nice to have, although at present I
don&#x
t files to transfer in /etc/puppet/ca ?
FYI, I am using version 0.24.4
Any advice appreciated
Don
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send e
tensions to the server cert.
> Changes are definitely needed in the way that the puppetmaster
> generates
> the server cert.
Did this fix ever happen, and if so, in which version of puppet?
Right now, my puppetmasterd is v 0.22.4
OK, I added this info to this paragraph in the wiki.
On Nov 21, 2008, at 2:46 PM, James Turnbull wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Don Jackson wrote:
>> I believe that the following paragraph from the wiki is at best not
>> clear a
y
I propose that the above paragraph be augmented to include the
requirement that the ca.pem be transfered from the master to the
client...
Best regards,
Don
Begin forwarded message:
> From: Don Jackson
> Date: November 17, 2008 3:55:02 PM PST
> To: puppet-users@googlegroups
lic_keys
./certs:
total 4
-rw-r--r-- 1 root _puppet 887 Nov 17 15:01 svn01.clark-
communications.com.pem
./private:
./private_keys:
total 4
-rw--- 1 root _puppet 887 Nov 17 15:01 svn01.clark-
communications.com.pem
./public_keys:
What am I doing wrong?
Any advice appreciated...
Don
--~--~-
58 matches
Mail list logo
