Saved us as well... had the same problem and ours was in group: http:www in
stead of puppet:puppet. Changing it made everything work once again.
Thanks a bunch!
Andrew.
On Saturday, July 27, 2013 at 2:14:36 AM UTC+2, GregC wrote:
>
> i just went through same issue.
>
> 1. /etc/puppet/rack/pupp
resources call that would then instantiate my "profiles". I
don't want to make this needlessly complex if I don't have to, so if
someone else has any suggestions I would appreciate it.
Thanks,
Drew
--
You received this message because you are subscribed to the Google Grou
ariable = hiera('my_hiera_data')
At least I do explicit calls to hiera so that there is no question as to
where the value of the variable comes from, but you may do it differently.
I hope this answers your question.
Drew
On Wednesday, February 25, 2015 at 4:09:34 PM UTC-5, justin parker
Damn! That was it. Removed my include and it works exactly like it should.
On Sunday, January 11, 2015 at 6:46:20 PM UTC-5, Felix.Frank wrote:
>
> On 01/10/2015 02:39 PM, Christopher Wood wrote:
> > On Fri, Jan 09, 2015 at 01:51:28PM -0800, Drew wrote:
> >> >I&#x
Thanks, Felix.
On Monday, January 12, 2015 at 7:57:05 AM UTC-5, Drew wrote:
>
> Damn! That was it. Removed my include and it works exactly like it
> should.
>
> On Sunday, January 11, 2015 at 6:46:20 PM UTC-5, Felix.Frank wrote:
>>
>> On 01/10/2015 02:39 PM, Chris
;
> @reboot service puppetmaster restart
>
> cron job.
>
> HTH,
> Felix
>
> On 01/08/2015 08:28 PM, Drew wrote:
>
> Yep, that's exactly what I'm saying. Like I said, it's weird. Maybe
> something with the time?
>
> Thanks!
>
> On Tuesday,
make any difference.
On Saturday, January 10, 2015 at 8:39:13 AM UTC-5, Christopher Wood wrote:
>
> On Fri, Jan 09, 2015 at 01:51:28PM -0800, Drew wrote:
> >I'm fooling around with some defined types and am struggling a
> little.
> > The following is just a smal
I'm fooling around with some defined types and am struggling a little. The
following is just a small example of what I'm doing while I work it out:
#/etc/puppet/modules/testmodule/manifests/init.pp
define testmodule ( $message ){
testmodule::down { "${name}":
message => "test message for
I'm fooling around with some defined types and am struggling a little. The
following is just a small example of what I'm doing while I work it out:
#/etc/puppet/modules/testmodule/manifests/init.pp
define testmodule ( $message ){
testmodule::down { "${name}":
message => "test message for
e?
>
> On 01/02/2015 08:39 PM, Drew wrote:
> > Hey,
> >
> > I hope someone here can point me in the right direction. I've been
> > struggling with this for a few days and I can't seem to figure out
> > what the issue is. It's really strang
PuppetDB that I wouldn't be overwriting or destroying anything.
Thanks!
Drew
On Sunday, January 4, 2015 10:26:38 AM UTC-6, Felix.Frank wrote:
>
> Hi,
>
> well, do you currently have storeconfigs=true in the master's puppet.conf?
> Otherwise, you are not storing things yet
to verify.
Please set me straight. Also - if you have any questions, please feel free
to let me know and I'll try to explain.
Thanks!
Drew
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop
Hey,
I hope someone here can point me in the right direction. I've been
struggling with this for a few days and I can't seem to figure out what the
issue is. It's really strange. I have a vagrant configuration that spins
up a puppetmaster and a target machine that runs the agent. When I
in
stuff to do.
Thanks, Felix.
Drew
On Tuesday, December 9, 2014 7:45:16 AM UTC-5, Felix.Frank wrote:
>
> Hi,
>
> I think you have constructed the rare manifest order issue. For sanity's
> sake, I shall only quote the variable assignments.
>
> On 12/08/2014 05:57 PM, D
Hey, I hope someone here can point me in the right direction. Maybe I'm
doing something wrong here, but I'm having trouble getting it resolved. I
have a java rpm that I want to relocate under a different directory, for
various reasons. Not something all that uncommon. I'd like to use puppet
I am running the latest version of the PuppetLabs F5 module and also
running latest version 11 on the F5s. I can successfully retrieve resources
from the F5 via `puppet resource f5_user`, etc. However, when I run puppet
and try to apply F5 resources I see the following output:
Debug: Puppet::Ut
disk, but if I can't then I'll work around it.
Thanks both for your response!
Drew
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-use
discussion about include/require:
https://groups.google.com/d/msg/puppet-users/vTDoxY3OdNI/HOWeN_ZhDJ8J.
I'm mostly curious if I'm cutting across the grain here. I'm
relatively new to Puppet. Is --noop not universally useful for
dry runs? If it is, how can I work around t
On Tuesday, August 27, 2013 7:26:41 PM UTC-5, François Lafont wrote:
>
> I thought about another way with the extlookup function.
>
> ---
> snmp:
> community: extvalue_community
>
> monitoring:
> community: extvalue_community
>
> And in a common.csv file:
>
> extvalue_community,abcd1234
I've found that using Hiera for this type of problem work's really well.
Hiera is integrated into Puppet 3.0+
https://github.com/puppetlabs/hiera
Drew
On Thursday, May 2, 2013 4:54:47 PM UTC-4, rogerl...@gmail.com wrote:
>
> We need to refer to common variables across multi
environment or datacenter. This could be powerful if you wanted to test
some new JVM settings on just one server in production or an entire
datacenter. You can use any facter fact you want to define your hierarchy.
:hierarchy:
- %{fqdn}
- env/%{env}/common
- datacenter/%{datacenter}
- comm
We're having a very strange issue with Puppet running on Passenger. Every
day or 2, our clients start receiving Passenger back traces. It's the
generic "Ruby (Rack) application could not be started." My initial thought
was that this is a resource/configuration problem. Maybe we're overrunnin
Sy,
Welcome to Puppet. Hopefully we can help you get going so you can
experiment further.
First, what version of Puppet are you running? I'm guessing by your
commands that it's definitely prior to version 3. I recommend updating to
Puppet 3 before going further, especially since you're just
I am fairly new to Puppet, and am taking a script initially working with a
Vagrant setup and trying to run it standalone. I am simply declaring the
class for the module mysql in the script:
class { 'mysql': }
and when I try to run 'puppet apply' I get:
Puppet::Parser::AST::Resource failed
Would you be able to do something like this...
:hierarchy:
- %{fqdn}
- %{environment}/settings (environment specific settings)
- common
On Friday, February 22, 2013 9:11:08 AM UTC-5, Alexander Fortin wrote:
>
> Hi folks,
>
> I'm using Puppet 3.0.1 and hiera 1.1.1, and this is my hiera
On Monday, February 18, 2013 12:21:11 AM UTC-6, John Warburton wrote:
>
>
>> Is this mcollective version 3.x or 2.3.x?
>
Deprecation warning occurs in 2.3. Complete removal will occur in the 3.x
production branch.
>
>
>> So you should be good to continue using it for a few months to come
Ellison is right, it really doesn't make much sense to create one resource
with create_resources. In fact, I'm not even sure it will work with
classes because I've never tried it. However, it works great for defined
types. I think I understand what you're trying to do so let me give an
examp
Something I came up with to allow me to upgrade my CentOS machines w/out
overriding my Puppet definitions:
http://technicalmusings.blogspot.com/2013/01/yum-update-that-excludes-puppet-managed.html
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group
I'm working on a new provider for puppet 3.x and Solaris 11's dladm
command. One of the subcommands is set-linkprop which is used to set
various properties for networking links. The problem is there are dozens
and dozens of properties that can be set depending on the type of link
(physical or
would need to convert the putty private key
to a format it can understand
Drew
On Monday, December 24, 2012 5:19:17 AM UTC-5, lalit jangra wrote:
>
> Hi,
>
> I have created an agent node from a master node using below command.
>
> puppet node_aws create --image ami-cc5af9
Hi Fran,
There's a couple of things you can try. First, make sure you have the
module in your modules directory. I'm fairly sure you have this step done
but just in case. Then, since vcsrepo uses plugins to accomplish it's
tasks you need to ensure that the plugins are on both the puppet mast
You can read all about the puppet file server here.
http://docs.puppetlabs.com/guides/file_serving.html
On Wednesday, November 7, 2012 11:54:36 AM UTC-5, bobby38 wrote:
>
> I have added a new folder to my /modules/backup called files
> /modules/backup/files
> i have verified the new files folder
Is /etc/puppet/auth.conf owned by the puppet process? You could also try
setting it as world readable.
And make sure in your puppet.conf under the agent stanza, the server block
is set to the domain name of the puppet master. You should be able to
telnet to it on port 8140.
[agent]
server
;
>
> On Sunday, September 30, 2012 11:40:42 PM UTC-5, drew khoury wrote:
>>
>> May have spoken too soon.
>>
>> If I set the env variable, and I'm manually logged, then I run puppet all
>> is good.
>>
>> I'm still not clear on how I set
anding how Vagrant is invoking Puppet.
On Monday, October 1, 2012 12:30:35 PM UTC+10, drew khoury wrote:
>
> Looks like I was able to get it to work by executing the export command
> through a bash script, initiated via puppets exec logic in my puppet
> manifest. Not the most elegant
x27;m...
- doing a straight export http_proxy=... (in my bash script)
as well as...
- adding to /home/vagrant/.bashrc
This way puppet gets the proxy at runtime & if I log in as vagrant I get
proxy too.
Thanks for pointing me in the right direction!
On Monday, October 1, 2012 12:15:23 PM UTC
ep 30, 2012 at 5:36 PM, drew khoury
> > wrote:
>
>> Also I tried upgrading puppet and got the same results.
>>
>> vagrant@vagrant-debian-squeeze:/tmp/vagrant-puppet/manifests$ sudo
>> apt-show-versions | grep puppet
>> facter/squeeze uptodate 1.6.12-1puppetla
puppetlabs-release/squeeze uptodate 1.0-5
On Monday, October 1, 2012 10:18:25 AM UTC+10, drew khoury wrote:
>
> Hi,
>
> I've been trying to pass the http_proxy_host option to puppet but it's not
> taking.
>
> I have tried the following:
> sudo puppet apply -
say I originally tried to do this with Vagrant (see here for more
info https://groups.google.com/forum/?fromgroups=#!topic/vagrant-up/IW97AZbxdVc
) although I eventually realised I couldn't even do this through puppet so
I'm keen on trying to solve both issues.
Thanks, Drew.
--
You
of course, such a simple typo, thanks so much! Too many years of typing
.php, will have to get my mind in the puppet world now :)
On Monday, September 24, 2012 9:50:41 AM UTC+10, R.I. Pienaar wrote:
>
>
>
> - Original Message -
> > From: "drew kh
ing a default vagrant setup which obviously has pupet installed.
My folder looks like this:
vdrew
-- manifests
-- default.pp
-- modules
-- drew
-- manifests
-- init.php
-- .vagrant
-- Vagrantfile
defau
om Jan ( http://pastebin.com/2hSw26Kv ).
If anyone can give me some pointers, I'd appreciate it.
Drew
-
[root@puppet puppet]# /etc/init.d/puppetmaster start
Starting puppetmaster:
/usr/lib/ruby/site_ruby/1.8/puppet/util/settings/boolean_setting.rb:27:in
`munge
etting and if so, where to?
Any pointers gratefully appreciated!
Cheers, Drew
--
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 em
configuration option
err: Could not retrieve catalog: Certificates were not trusted: certificate
verify failed
I've checked the time on both servers. they are the same.
I've checked the cert on both servers w/ openssl verify. they are good.
Any ide
44 matches
Mail list logo
