I had the same issue. /etc/selinux/config to SELINUX=permissive fixed my
issue.
On Tuesday, August 12, 2014 at 8:08:20 PM UTC-5, Patrick Robinson wrote:
>
> I had a similar error getting 405. I found I hadn't set the PassengerRoot
> directory correctly in the puppetmaster vhost config:
>
> Passe
kept flipping
between using subscribe/notify and ->/~> ordering syntax and most likely
screwed something up in the interim. I eventually made a mistake and got
some dependency cycle issues which actually helped quite a bit in figuring
out my error in logic.
BTW, "refreshonly =>
7;]
(In fact I used that exact ordering syntax at one point).
BTW, using:
Exec['stop'] -> Exec['start'] did cause stop to run before start, just
AFTER Package['foo'] is installed, so thank you for that. This doesn't
solve my issue however as I really ne
Puppet 3.6.2
First, I understand that Execs try not to run multiple times if called many
times by many resources and typically wait until they've all been
"collected" from all resources, but I have a specific case where I need
different Execs to run in a particular order based on a set of resou
Actually, disregard, I'm thinking of the client side.
--
Jake Lundberg
Senior Systems Engineer
jlundb...@adconion.com
+1.310.382.5581
On Wed, Aug 6, 2014 at 11:12 PM, Jake Lundberg
wrote:
> Do you even need to do this? Can't you just use the certname
> configuration
Do you even need to do this? Can't you just use the certname configuration
variable on the puppetmaster and just set it to the old name?
On Wednesday, August 6, 2014 3:40:38 AM UTC+7, Jose Luis Ledesma wrote:
>
> +1
> You don't need to re-register all clients. Just generate a new cert for
>
o remember a
few things:
1. Try to keep your node definitions as simple as possible. When possible
only add facts not derived from facter to node definitions.
2. Keep configuration data out of your classes. Even defaults. Use
common.yaml or similar to add in defaults.
3. Unless absolutely ne
e best platform. Consider something like
Fabric/Capistrano, Ansible or Salt Stack (or just plain Bash).
On Monday, December 9, 2013 12:50:44 PM UTC-8, Sachin Nikam wrote:
>
> Jake,
> I want to do something like this...
> # puppet apply --modulepath=/etc/puppet/modules site.pp "someval
Oops, that should probably read:
exec { "do something" :
command => "/usr/local/bin/exec_something.sh ${param1} ${param2}"
}
On Monday, December 9, 2013 11:46:17 AM UTC-8, Jake Lundberg wrote:
>
> I suppose it depends on how you structure your manifest. We
I suppose it depends on how you structure your manifest. We typically
apply a manifest to a particular node when testing new manifests. So
something like:
site.pp:
node default {
$param1 = "value1"
$param2 = "value2"
include exec_class
}
/etc/puppet/modules/exec_class/manifests/init.
I'm able to get Hiera + GPG working fine, but am running into an issue when
I want to use GPG as the primary backend. We want to do this to make sure
any secrets are realized first. However, it seems when a value in GPG
backend also exists in a YAML backend, hiera dies with a message:
Debug
he file
through that and see if you are able to save your changes. If it fails, I
think you can then reference that error path I gave you to first check for
whatever error may be generated from trying to make the change.
Hope that helps point you into a direction for a solution.
Regards,
Jak
rs
run on.
Regards,
Jake
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/zo7mWV3ehGAJ.
To post to this group, send email to puppet-users@googlegroups
t *[file = "/home"]/dump 0',
'set *[file = "/home"]/passno 0',
],
onlyif => 'match *[file = "/home"] size > 0',
}
I think this helps augeas not autoload everything it can possibly edit and
narrows it in on just one file.
Regards,
Jake
--
, but can instead
push facts from our PMs to our Foreman DB which I see now after reading
some more from the Foreman FAQ.
Thanks!
Jake
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To view this discussion on the web visit
https://gr
NC'
(don't want to have 'login here to view these nodes, login there to view
these other nodes)?
Thanks for all comments!
Jake
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To view this discussion on the web visit
h
il everything was back up.
So since what I have isn't bullet proof I don't have anything documented
... but eventually ... :)
Regards,
Jake
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To view this discussion on the web
7;backup' in them.
Again, no DRBD which is mainly for the cert stuff and that is all handled
by a single node (I set ca_server to my CA PM on all nodes). But, maybe
you could have a shared NFS/storage for the certificates to address it?
Regards,
Jake
On Wednesday, June 20, 2012 10:44:19 A
le on utilizing was written up not too long ago
http://blog.ronvalente.net/blog/2012/05/19/puppet/.
Regards,
Jake
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To view this discussion on the web visit
https://groups.google.com/d/m
Continuing discussion at thread in foreman users @
https://groups.google.com/forum/?fromgroups#!topic/foreman-users/uhW_EwO4LLg
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To view this discussion on the web visit
https://groups.google.com
cked in foreman
(kind of a single source of data) instead of the need to edit some script.
Thanks,
Jake
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet
And also if others wanted to know the bug I filed:
https://projects.puppetlabs.com/issues/14399
Thanks again for your help with this!!
Jake
On Friday, May 11, 2012 8:08:52 AM UTC-5, jcbollinger wrote:
>
>
> On May 10, 8:15 am, Jake - USPS wrote:
> > John,
> >
> >
ething that was fixed. If not then I'll go and try older versions of
puppet and see if I can find where it stopped working (unless you have some
more ideas on things to try ;)
Thanks for all your help!
Jake
--
You received this message because you are subscribed to the Google Groups
&quo
' as 'kernel.shmall:1'
notice: vm.nr_hugepages:3
notice:
/Stage[main]/Oracle_db::Hugepages/Oracle_db::Etc_sysctl_conf[vm.nr_hugepages]/Notify[vm.nr_hugepages:3]/message:
defined 'message' as 'vm.nr_hugepages:3'
notice: Finished catalog run in 17.88 seconds
L
very 30 minutes. We use 4 systems with 16
cores each to support this. The systems run with a load of around 30%
right now, so really all we need is probably 2 of these systems ... but we
want redundancy.
So we have ~9000/hr with this setup. To give you an idea of run/hr and
horsepower.
Regard
tice: vm.nr_hugepages:3
notice:
/Stage[main]/Oracle_db::Hugepages/Oracle_db::Etc_sysctl_conf[vm.nr_hugepages]/Notify[vm.nr_hugepages:3]/message:
defined 'message' as 'vm.nr_hugepages:3'
I am using 2.7.9
Thanks!
Jake
--
You received this message because you are subscribed t
had its IP updated incorrectly it then updates back to the
correct IP.
I am using puppet 2.7.5 on SLES10 and SLES11.
Would this be a configuration issue or a bug with puppet?
If you want more information let me know.
Thanks!
Jake
--
You received this message because you are subscribed to the
o see exactly what changes I actually
made, but just curious if there is some way to check into something
like this.
Thanks,
Jake
--
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@googl
milar to
what I am trying to do, but it seems foreman does not allow parameters
for classes yet nor can I figure out how to have a 'parameter hash' in
foreman.
So functionally this is pretty close to what I am looking for. Not
sure if there is a better way to implement with forema
as well in case of a system blowing up), its managed by
puppet, and we don't need to wait to push out an update throughout our
puppet environments to add small resources like this. But maybe this
isn't possible?
Thanks again for your comments!
Jake
On Nov 18, 9:54 am, Chr
ave the changes documented and managed. Or do people just
create a new module for every little app that comes along?
Thanks!
Jake
--
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
em to screw up any recipes.
Regards,
Jake
On Aug 31, 10:05 am, Jake - USPS wrote:
> Just updated to 2.7.3 from 2.6.9. That's when 'Could not retrieve
> operatingsystem: undefined method `+' for nil:NilClass' started
> popping up. It doesn't seem to be c
be part of the
cause?
Anyone else encounter this? Should I worry about it?
Thanks,
Jake
--
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 from this gro
Excellent, thanks - patch applied here with good results.
It appears the issue is already known as of facter-1.5.9:
http://projects.puppetlabs.com/issues/7957
So, the ball should already be rolling on this one - right?
Jake
On Aug 18, 1:53 am, Dan Carley wrote:
> On 17 August 2011 22:44, J
I've installed facter-1.6.0 and puppet-2.7.3 on a number of SLES 10
hardware nodes (HP DL580) running the Virtuozzo hosting software.
Well, facter correctly identifies such a machine as a hardware node
("virtual => openvzhn") but somehow concludes that the hardware node
is in fact virtual. ("is_vi
e is virtual.
Any ideas on where I should look would be welcome.
Jake
--
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 from this group, send email to
p
on can be installed at a time.
I'm totally new to Eclipse. So a lot of above is hypothesis. But I
do know downloading 3.7 and using that I now have no issues.
Regards,
Jake
On Jun 28, 1:33 pm, bluethundr wrote:d
> hello list
>
> I am attempting to install gepetto into my eclipse envi
der 2.6.9 would be
this issue.
Thanks,
Jake
On Jun 21, 1:33 pm, Michael Stahnke wrote:
> It's here! Puppet 2.7.0.
>
> This release is available for download
> at:http://puppetlabs.com/downloads/puppet/puppet-2.7.0.tar.gz
>
> It's available as a gem from rubygems
Nan,
Thanks for your help. That seems to be the issue for me. I'll have
to consider that when doing some of the things I do!
Thanks everyone for your responses!
Regards,
Jake
On Jun 1, 1:48 pm, Nan Liu wrote:
> On Wed, Jun 1, 2011 at 11:31 AM, Jake - USPS wrote:
>
>
>
&g
value
stopped, should be running (noop)
notice: /Stage[main]/Common/Notify[This manifest is from prod. My env
is production]/message: current_value absent, should be This manifest
is from prod. My env is production (noop)
notice: Finished catalog run in 2.88 seconds
Hopefully whatever I'm doing
can check
http://groups.google.com/group/foreman-users
Regards,
Jake
On May 26, 12:14 pm, Douglas Garstang wrote:
> On Wed, May 25, 2011 at 1:19 PM, Brian Gupta wrote:
>
>
>
>
>
>
>
>
>
> > Douglas,
>
> > I have to concur with disconnect, now that we
Huge user error on my part. I have 2 environments, and this error was
coming from the outdated one, while I was referencing the good one
when troubleshooting. :-\
Thanks for taking a look!
Regards,
Jake
On May 20, 11:01 am, Jake - USPS wrote:
> That was a typo on my part, usps-ipwatchd
also checked
all my other modules/manifests to make sure I didn't have usps-
ipwatchd somewhere else also and its not. So I'm not sure that is the
issue.
Thanks,
Jake
On May 20, 10:44 am, Nigel Kersten wrote:
> On Fri, May 20, 2011 at 8:29 AM, Jake - USPS wrote:
>
> >
"";
"fix_sles_update_repo":
path => "/bin:/usr/bin",
command => "",
onlyif => "";
"fix_sle_sdk_pool_repo":
path => "/bin:/usr/bin",
command => "",
So does that mean those will be update as well (if ca_ttl is set
before they are generated) or are they 5y regardless and using
anything higher then 5y does not matter? Or are you just throwing a
fact out there and it doesn't matter to me and I'll be OK?
Thanks,
Jake
On May 3, 3:3
take when they expire
or does puppet take care of them automatically? Just want to make
sure whether upping ca_ttl is good enough for me or if there are other
things I need to potentially be aware of.
Thanks,
Jake
On May 3, 3:30 pm, Ohad Levy wrote:
> On Tue, May 3, 2011 at 9:29 PM, Jake
Thanks for the response. I found it in the genconf now. Looks like
default is 5y. I'll be changing it for my needs.
Thanks!
Jake
On May 3, 12:53 pm, Matt Wise wrote:
> the ttl setting is 'ca_ttl' i think in puppet.conf.. and yes, you'll
> ultimately need to re-
Yea, I'm new to puppet ... sounds like now I have to worry about certs
eventually expiring and regenerate/sign them to keep nodes happy?
Seems Trevor suggests increasing TTL. How can I do this if I wanted
to?
Thanks,
Jake
On Apr 28, 9:30 am, Matt Wise wrote:
> Unfortunately, this is
That's too funny ... I took a look at the installation instructions
for foreman and it didn't look too complicated, so I'll give it a try
tomorrow. Is it pretty intuitive to use, or do you want to point me
to documentation to setup doing what I'm doing above in it?
Thanks,
J
off the CA Server. More details in the link above.
This is working great for me and I'll be using it until similar
functionality is included by default in puppet.
Regards,
Jake
On Apr 14, 8:50 am, Jake - USPS wrote:
> Nevermind, looks like its in 2.7.0rc1
>
> http://groups.go
nt build process.
Russell,
I understand your idea. I'm thinking of giving this a try.
Thanks,
Jake
On Apr 15, 3:36 am, Russell Howe wrote:
> > -Original Message-
> > From: puppet-users@googlegroups.com
> > [mailto:puppet-users@googlegroups.com] On Behalf Of Jake - US
be a valid test to simulate a decom/
rebuild/reregister puppet without all that hassle.
Thanks for opening the additional bugs on this. One thing I'm
wondering is if I'm missing something that maybe people already do to
deal with my type of situation.
Regards,
Jake
On Apr 14, 12:58 pm,
5.8-1.sles10
usps-puppetmaster-2.7.0.1-1.sles10
We are running the puppetmaster through passenger, although my tests
above are running it as your told me. If you want anything else, just
let me know.
Thanks for checking this out,
Jake
On Apr 14, 12:45 pm, Dominic Maraglia wrote:
> Jake,
&g
ified in this SSL session
info: Caching certificate for eagnmnmbpe20.usps.gov
err: Could not request certificate: Retrieved certificate does not
match private key; please remove certificate from server and
regenerate it with the current key
Exiting; failed to retrieve certificate and waitforcert
I can give that a try ... does that mean I wouldn't be able to use
passenger like I currently am to get this to work?
I'll let you know of my results shortly.
Regards,
Jake
On Apr 14, 11:35 am, Dominic Maraglia wrote:
> Jake,
>
> Can you please try the following step and
and waitforcert is disabled
I guess I was expecting for this to work fine when
'allow_duplicate_certs = true'. Maybe I misconfigured something?
Maybe I'm misunderstanding how allow_duplicate_certs behaves?
Thanks!
Jake
--
You received this message because you are subscribe
Nevermind, looks like its in 2.7.0rc1
http://groups.google.com/group/puppet-users/browse_thread/thread/b3b50d3c4e449a60
cb01221 (#3360) Add an allow_duplicate_certs option
On Apr 14, 8:45 am, Jake - USPS wrote:
> Thanks for the reply. I'm just starting to understand puppet, so I
>
icate cert and whatnot. It looks
like its status closed as of 14 hours ago. Does that mean it is in
some release of puppet now, or just that code it ready to eventually
be implemented? I'd like to start trying it out right away as my
'solution' doesn't seem to work well with
pproach, maybe even how to get dashboard to work
with this method? Or is this a horrible idea?
Also, what is foreman and how could it help. Not familiar with that
product.
Thanks,
Jake
On Apr 13, 3:46 pm, Ohad Levy wrote:
> On Fri, Mar 11, 2011 at 10:38 AM, Patrick <
>
>
>
&g
now a system can't checkin
anymore until someone notices and then fixes it.
Thanks,
Jake
On Mar 11, 3:38 am, Patrick wrote:
> On 8 Mrz., 14:54, Disconnect wrote:
>
> > Alternately, running thepuppetcacleanbefore starting the new client will
> > result in the standard unsigned
I just finished getting my 1.1.0rc3 package created and as you thought
my issues disappeared ... /reports/upload works fine now.
Thanks,
Jake
On Apr 12, 12:33 pm, Jake - USPS wrote:
> What release notes are you referring to? The puppet-dashboard page
> mentions 1 upgrade, as do
for this type of information so I know
where to look for these type of oddities.
Thanks,
Jake
On Apr 12, 12:13 pm, Patrick wrote:
> On Apr 12, 2011, at 9:57 AM, Jake - USPS wrote:
>
> > Arg, I didn't even realize I was already using an old version ... I'll
> > update
Arg, I didn't even realize I was already using an old version ... I'll
update to 1.1.0 and give it another shot.
Thanks for the reply.
On Apr 12, 10:48 am, Patrick wrote:
> On Apr 12, 2011, at 8:41 AM, Jake - USPS wrote:
>
> > puppet-dashboard-1.0.4-1.sles10
>
> &g
ation, let me know and I can provide.
Thanks,
Jake
--
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 from this group, send email to
puppet-users+unsubscr...@
Thanks for letting me know. Also, what is Passenger? I'm new to
puppet and not super familiar with ruby.
Thanks,
Jake
On Jan 13, 2:02 pm, Daniel Pittman wrote:
> On Thu, Jan 13, 2011 at 08:20, Jake - USPS wrote:
>
> > This is version of mongrel included with SLES10 SP3
&
(X86-64)
I didn't see anywhere a version of mongrel that was required at a
minimum, maybe I missed that though.
Thanks,
Jake
On Jan 12, 11:17 pm, Daniel Pittman wrote:
> On Wed, Jan 12, 2011 at 14:13, Jake - USPS wrote:
>
> > I'm trying to setup my puppetmaster to use
led catalog
err: Could not retrieve catalog; skipping run
Did I mis-configure something, and if so can someone help point me in
the correct direction?
This is on a SLES10 SP3 server/client systems. I compiled puppet
2.6.4 from source using SLES provided packages to meet dependencies
(ruby).
Thanks,
J
d that the
provider has 'incl' and 'lens'. I used those and a run that was
taking 20sec to complete (no changes, just verifying) now takes 2-3
seconds. :)
Thanks,
Jake
On Jan 7, 10:03 am, Jake - USPS wrote:
> Dan,
>
> First, thanks for the sysctl type/provider.
n but doesn't have
what I am trying to do (since I took it out), but it does set it to
the value I specify as default from system_defaults.
Thanks,
Jake
On Jan 6, 2:59 pm, Dan Bode wrote:
> On Thu, Jan 6, 2011 at 6:23 AM, Jake - USPS wrote:
>
>
>
>
>
>
>
>
>
&g
eep updating the list of applications
that will also modify kernel.sem in my system_defaults recipe as they
come about
I feel like I am not understanding something completely on how I
should be designing this for puppet. If anyone has any suggestions
please let me know. Also, if you require more information
On Mon, Feb 16, 2009 at 3:31 PM, babatoko wrote:
> Could not find dependency Exec[modprobebonding]
> ...
> exec { "modprobe bonding":
You'll want to avoid using spaces as the names/titles of classes,
files, exec statements, etc. etc.
--
Jake Pau
On Sat, Jan 17, 2009 at 5:21 PM, kevin wrote:
>
> How does one add a password to a newly created user?
You use the "password" parameter. See more details in the user type
reference here:
http://reductivelabs.com/trac/puppet/wiki/TypeReference#id312
--
Jake Paulus
jake
72 matches
Mail list logo
