I am trying to use hiera to populate a defined type to feed the
puppet-logstash module. So far, I have been unable to send the data from my
hiera file to my defined type. I have tested my defined type and it is
working, I just can't seem to populate the variables. It tells me that
$content and
a test'
> order: '10'
>
> Should probably be
> profiles::logstash::config:
>content: 'this is a test'
>order: '10'
>
>
>
> On Thu, May 29, 2014 at 10:27 AM, Brian Wilkins
>
> > wrote:
>
>> I am try
It prints out:
order10contentthis is a test
It concatenated it all together.
On Thursday, May 29, 2014 12:59:09 PM UTC-4, Doug_F wrote:
>
> Try setting your notice("${shipper_config}") before create resources and
> see what it prints out.
>
>
> On Thu, May 29, 201
fig', {})
>
>
> On Thu, May 29, 2014 at 11:01 AM, Brian Wilkins
>
> > wrote:
>
>> It prints out:
>>
>> order10contentthis is a test
>>
>> It concatenated it all together.
>>
>>
>>
>> On Thursday, May 29, 2014 12:59:09 PM
rver does it show up as a hash?
>
>
>
> On Thu, May 29, 2014 at 11:08 AM, Brian Wilkins
>
> > wrote:
>
>> Same problem. I see it concatenated in the notice.
>>
>>
>> On Thursday, May 29, 2014 1:05:39 PM UTC-4, Doug_F wrote:
>>
>>> J
Same problem. It seems like I am close. If only it didn't put all the data
together as one string.
On Thursday, May 29, 2014 1:17:07 PM UTC-4, Doug_F wrote:
>
> Maybe try your hiera command right inside your create_resources.
>
>
> On Thu, May 29, 2014 at 11:13 AM, Brian W
t_file:
> content: 'this is a test'
> order: '10'
>
> Add a notice line in your profiles::logstash::config type to:
> notify("name is ${name}")
> notify("content is ${content}")
> notify("order is ${order}")
>
>
&g
_F wrote:
>
> Does it show up properly if you lookup on the server?
>
>
> On Thu, May 29, 2014 at 12:09 PM, Brian Wilkins
>
> > wrote:
>
>> Hmm, that's not working either. Doesn't look like it is populating my
>> define now. Hmm
>>
>>
.yaml:
classes:
- os::repo
- profiles::logstash::shipper
profiles::logstash::config_array:
- inputfile
profiles::logstash::config_settings:
inputfile:
content: 'this is a test'
order: '10'
On Thursday, May 29, 2014 2:37:31 PM UTC-4, Brian Wilkins wrote:
>
> Yep!
I have my puppetmaster setup with httpd and mod_passenger. My agents can
successfully pull manifests, but they are unable to pull files. As far as I
can tell, I do not have any rewrite rules setup in my puppetmaster.conf
(see below). In my httpd access log, I see that the agent tries to request
I am using the puppet logstash module from Forge installed at
/etc/puppet/modules/logstash
I am trying to setup my profile class as profiles::logstash. My manifest is
at /etc/puppet/modules/profiles/manifests/logstash.pp
In my /etc/puppet/modules/profiles/manifests/logstash directory I have:
i
ig': } ~>
class{'profiles::logstash::service': } ->
Class["profiles::logstash"]
}
On Saturday, May 31, 2014 8:17:34 AM UTC-4, Brian Wilkins wrote:
>
> I am using the puppet logstash module from Forge installed at
> /etc/puppet/modules/logstash
>
> I am
class { '::logstash':
status => $status,
}
}
On Saturday, May 31, 2014 8:26:54 AM UTC-4, Robin Bowes wrote:
>
> Fully-qualify the class name, ie. use '::logstash'.
>
> R.
> On 31 May 2014 13:17, "Brian Wilkins" >
> wrote:
>
&
What about staggering your runs? It seems trivial but at least it would reduce
your load I think.
--
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-users+u
st,idx|
host_string << "\"#{host}\"";
host_string << "," if idx < @brokers.length-1
}
host_string << "]"
%>
output {
redis {
host => <%= host_string %>
data_type => "list"
key => "logstash"
I am trying to write unit tests of my puppet modules. In my
profiles::logstash::install, I disambiguate the call to
/etc/puppet/modules/logstash by using ::logstash in my class definition
like so:
class profiles::logstash::install() {
$ensure = $profiles::logstash::enable ? {true => present,
6/4/14, 2:30 PM, Brian Wilkins wrote:
> > I am trying to write unit tests of my puppet modules. In my
> > profiles::logstash::install, I disambiguate the call to
> > /etc/puppet/modules/logstash by using ::logstash in my class definition
> > like so:
> >
> >
> > Brian
> >
> > On Wednesday, June 4, 2014 3:11:14 PM UTC-4, Garrett Honeycutt wrote:
> >
> > On 6/4/14, 2:30 PM, Brian Wilkins wrote:
> > > I am trying to write unit tests of my puppet modules. In my
> > > profiles::logstash::i
lowing :
>
> {
> "metadata": {
> "api_version": 1
> },
> "data": {
> "classes": [
> "settings",
>
>
>
> "vim",
>
>
>
> And that is what you should check in your rs
I have been running my puppetmaster with passenger and apache httpd
successfully for sometime now. During a recent upgrade to Puppet 3.6.1, I
am seeing this following exception in /var/log/httpd/error_log :
*** Exception LoadError in PhusionPassenger::Rack::ApplicationSpawner (no
such file to
Hello,
We are trying to use the puppet-forge graphite module located here:
https://github.com/echocat/puppet-graphite/blob/master/manifests/install.pp
and our servers will not have access to the Internet. So we are downloading
all the pip packages to a local repository and will point pip to eac
, 2014 5:53:01 AM UTC-4, David Schmitt wrote:
>
>
> Hi Brian,
>
> On 2014-07-18 14:32, Brian Wilkins wrote:
> > Hello,
> >
> > We are trying to use the puppet-forge graphite module located here:
> >
> https://github.com/echocat/puppet-graphite/blo
We use this one :
https://github.com/liquidat/nagios-icinga-checks/blob/master/check_puppetagent
But you have to modify it if you are using an earlier version of Python for
the date time code to get the difference.
It's also good if you check the report file for errors. Rather than just
the s
Rather than typing out hundreds of files that logstash has to monitor and
put it into my profiles::logstash::acl class, how are others maintaining
the actions to set the ACLs on files that logstash has to monitor? Right
now, I am doing this for every file that logstash has to monitor:
exec { 'a
In Puppet 3.6.2, how do you globally ignore .svn directories? Links on the
internet state to put File { ignore => '.svn' } in site.pp but that does
not work. I tried putting it in nodes.pp, but I receive the error: "Invalid
parameter ignore on File[etc_facter_folder] at on node
"
--
You rec
Hmm, it's working now! Thanks
On Thursday, August 7, 2014 6:11:41 PM UTC-4, Garrett Honeycutt wrote:
>
> On 8/7/14 9:10 AM, Brian Wilkins wrote:
> > In Puppet 3.6.2, how do you globally ignore .svn directories? Links on
> > the internet state to put File { ignore => &#
I am having to escape a regular expression in my match and puppet complains
on the puppetmaster of an "Unrecognised escape sequence". How do I fix this
so the logs don't get cluttered with this message? I am using Puppet 3.6.2.
file_line { "nagios_monitor_check_${title}":
path => '/etc/na
>
> Have you tried with two backslashes '\\' ?
>
Ah, that was it :)
Also, but why not manage multiple files in /etc/nagios/nrpe.d/ based on
> templates instead of managing a single file, since that's much trickier?
>
Oh, that is how I am doing it (sort of):
class profiles::nagios_resource::
I am seeing this issue every time puppet runs. I am using Puppet Dashboard.
I have reports being delivered via https and my puppetmaster runs in
Passenger. I see to have configured everything correctly and even copied
over the proper ruby scripts to their directories to get https to work. Any
i
tps = Net::HTTP.new(HOST, PORT)
https.use_ssl = true
https.verify_mode = OpenSSL::SSL::VERIFY_NONE
https.start do |conn|
conn.post "/reports/upload", "report=" + CGI.escape(self.to_yaml)
end
end
end
On Wednesday, August 27, 2014 5:17:07 PM UTC-4, Brian Wilkins wrote:
&g
We do the same thing as Ramin. Essentially have a custom role fact that is
based on hostname. After initial "check-in" with the puppetmaster, the
agent knows it role and is provisioned as such. We use the role/profile
design pattern.
On Wednesday, August 27, 2014 1:41:25 AM UTC-4, Ramin K wrote
I would actually put role higher than node simply because you will assign
the common role parameters first and then node specific parameters last.
This is how I do it in my hiera.yaml:
---
:backends:
- yaml
:hierarchy:
- common
- "role/%{::system_role}"
- node/%{::fqdn}
- "%{environmen
I have tried to setup Apache with passenger to host the puppetmaster but I
also want to cache. I have no problems running puppet within Passenger with
httpd. I also enabled mod_disk_cache within Apache. However, I still see my
puppet client htting the puppetmaster and the puppetmaster compiles t
I turned off high performance, but every request still hits the
puppetmaster. Any more ideas?
On Friday, August 29, 2014 5:57:30 PM UTC-4, Wil Cooley wrote:
>
> On Fri, Aug 29, 2014 at 9:50 AM, Brian Wilkins > wrote:
>
>> # RHEL/CentOS:
>> # And the passenger per
It probably died (either ps -ef | grep puppetmaster | awk '{print $2}' |
xargs kill -9) or otherwise. Just remove the pid file and continue. You can
examine the pid file to see if a process with that PID and named
puppetmasterd exists. More than likely not.
On Tuesday, September 2, 2014 10:56:5
Matt,
There is a better way and that is to use the roles and profiles pattern. I
use that and I have a custom facter ruby script that reads the fqdn from a
yaml and assigns it's role. Puppet takes over from there.
On Saturday, August 23, 2014 1:46:59 PM UTC-4, Matt W wrote:
>
> Will,
> Thank
You might want to file a bug, as this was supposed to be fixed in Puppet 2.7
http://projects.puppetlabs.com/issues/5318
On Thursday, September 4, 2014 3:28:10 PM UTC-4, Mike Reed wrote:
>
> Greetings,
>
> I have a class for which I would like to simply print a few parameters
> about a node, bef
37 matches
Mail list logo
