to test the agent (in the
> smart proxy ) works, the certificate gets revoked again.
>
> Do I have to stop the puppetmaster as well?
>
> On Saturday, October 16, 2021 at 11:47:17 AM UTC-4 treydock wrote:
>
>> If the key and the certificate don't match, you may have to regen
o make the values equal?
>
>
> On Friday, October 15, 2021 at 9:34:11 AM UTC-4 treydock wrote:
>
>> My advise might not be the best but it's what worked for me when our
>> master CA certificate expired. These are my raw notes from when I had to
>> renew our pu
My advise might not be the best but it's what worked for me when our master
CA certificate expired. These are my raw notes from when I had to renew
our puppetserver certificate. The original certificate was likely Puppet 4
and expired when running Puppet 6. I googled around and took some
I ran into this issue a few weeks ago, but only my CA cert was expired as
my master certs were a few years newer than CA. There are a couple blog
articles I found (lost URLs) that pieced together these steps to renew CA
cert. For clients you just have to remove then re-download the CA cert
in
Facter and not Puppet.
- Trey
On Wednesday, November 8, 2017 at 3:36:26 PM UTC-5, treydock wrote:
>
> I just upgraded my Puppet masters and PuppetDB to latest Puppet 5
> releases. All other systems remain Puppet 3.8.6. I've discovered that the
> masters and puppetdb running puppet
I just upgraded my Puppet masters and PuppetDB to latest Puppet 5
releases. All other systems remain Puppet 3.8.6. I've discovered that the
masters and puppetdb running puppet-agent 5.3.3 are no longer sending ENC
(Foreman) parameters as facts to PuppetDB [1]. What's really odd is one of
I think a combination of the two makes sense, and that's what we do. Our
production masters have many environment to segregate systems. We also have a
test master with isolated CA, mcollective, PuppetDB and Foreman to test changes
to those systems.
Our test environment uses a dedicated
: [BUG]
Segmentation fault ruby 1.8.7 (2013-06-27 patchlevel 374) [x86_64-linux]
Web searches related to this issue turned up a thread from puppet-users
earlier this year started by treydock:
https://groups.google.com/forum/#!topic/puppet-users/qWN6j-eNiZ0
Unfortunately, I've tried
I have Puppet 3.6.2 on CentOS 7 server acting as Puppetmaster. I had r10k
1.2.1 installed and I changed my ensure to 1.3.4. My other Puppetmaster
running CentOS 6 had no problem with this (except for NOTICE output being
printed as an error). The CentOS 7 system fails with the following:
I have noticed a very strange problem on CentOS 7 nodes where they are
collecting and/or applying their exported resources. I have a class called
brazos::firewall that's used internally to export a firewall rule that is
then collected by brazos::gw to allow specific systems through the
I'm attempting to use puppetlabs-apache with all my classes defined via
Foreman (1.5.1) with Puppet 3.4.3. Servers are all CentOS 6.5.
With puppetlabs-apache-1.0.1 when I applied both the apache class and
apache::mod::ssl class in Foreman I received this error on the server:
Error: Could not
4ca208bde329aa6861094ccefa07fc8338de6691 added
PuppetLint.configuration.ignore_paths to the puppetlabs_spec_helper lint
task, but wasn't till today that my modules began using
puppetlabs_spec_helper 0.5.x.
An example of the Rakefile I use on dozens of Puppet modules,
https://github.com/treydock/puppet-zfsonlinux
`/_etc_slurm_slurm.conf/fragments/2_slurm.conf-nodelist_c0926b20140502-22071-9r3m7r-9'
at
66:/etc/puppet/environments/production/modules/concat/manifests/fragment.pp
The module I'm working on is at https://github.com/treydock/puppet-slurm.
As a temporary workaround I've done 'mkdir -p
I have noticed lately that on my development system (OS X) and my
production Puppet master (CentOS 6.5) that when installing puppet modules
using librarian-puppet the permissions of some modules and files is very
restrictive to the point where the puppetmaster can't read the files. Some
-x64 executed in 80.01 seconds
Exited: 1
/Users/treydock/.rvm/gems/ruby-1.8.7-p371@puppet_dev/gems/beaker-1.9.1/lib/beaker/host.rb:183:in
`exec': Host 'centos-510-x64' exited with 1 running:
(Beaker::Host::CommandFailure)
rpm -ivh http://yum.puppetlabs.com/puppetlabs-release-el-5.noarch.rpm
Last
://github.com/treydock/repo_centos.
Thanks
- Trey
--
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+unsubscr...@googlegroups.com.
To view this discussion
I recently moved from manually configured Puppetmaster under passenger to
fully managed using theforeman/puppet module. Now I am experiencing
constant crashes (every few minutes) of the passenger process that runs the
puppetmaster.
Host is CentOS 6.5 running Puppet 3.4.3.
This is the entry I
master as frequently.
On Tuesday, March 25, 2014 4:30:27 PM UTC-5, treydock wrote:
I recently moved from manually configured Puppetmaster under passenger to
fully managed using theforeman/puppet module. Now I am experiencing
constant crashes (every few minutes) of the passenger process
Following the mcollective documentation [1] for adding clients to execute
mco commands when using SSL I am getting an error executing the 'puppet
certificate generate' command as my user account. I feel like I'm missing
something very obvious here.
$ puppet certificate generate treydock
I have an ovirt node that has Infiniband and I'm seeing two seperate errors
when running facter.
sh: vdsmdummy: command not found
and
Ifconfig uses the ioctl access method to get the full address information,
which limits hardware addresses to 8 bytes.
Because Infiniband address has 20 bytes,
can't identify where in the Facter code this is happening.
I updated Facter to 1.7.5-rc2 and the error is still the same on the host
with the ;vdsmdummy; bridge device.
Thanks
- Trey
On Sunday, February 9, 2014 3:17:10 PM UTC-6, treydock wrote:
I have an ovirt node that has Infiniband and I'm
on debugging the errors
when I can't reproduce them via command line.
[1] - http://pastebin.com/Lcy6feyt
[2]
- https://github.com/treydock/puppet-zfsonlinux/tree/development_zpool_type
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from
Puppet master yet, but I saw the symptoms on my live
systems.
Thanks
- Trey
[1] - http://projects.puppetlabs.com/issues/17794
[2] - https://github.com/treydock/puppet-zfsonlinux
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from
You can supply values to override those defined in /etc/my.cnf by adding files
to /etc/mysql/conf.d. The module makes the overrides possible with the default
configuration in my.cnf, I believe the IncludeDir line. Using phone so
difficult to reference.
- Trey
--
You received this message
On Sunday, December 9, 2012 1:41:34 PM UTC-6, treydock wrote:
I am finding that the puppetlabs-apache module is somehow adding 30-60
seconds onto a host's catalog compile time when the puppetmaster has no
other hosts contacting or generating catalogs. The Puppetmaster is setup
to use
Using exported resources I'm trying to have a host export a File resource
generated from a yaml template, to another host. The host that gets the
exported resource is throwing errors like this
err: Failed to apply catalog: Parameter content failed: Munging failed for
value
I am finding that the puppetlabs-apache module is somehow adding 30-60
seconds onto a host's catalog compile time when the puppetmaster has no
other hosts contacting or generating catalogs. The Puppetmaster is setup
to use Puppet-2.7.18 - Apache Passenger. RIght now only 2 hosts are even
Ive struggled with the same problem of distributing variables and other
generated data amongst hosts.
For external resources Ive found a great use in configuring a BackupPC server.
Each node builds their backup configuration file with tag
'backuppc_server_conf' and the server retrieves all
On Saturday, July 21, 2012 9:57:13 PM UTC-5, Garrett Honeycutt wrote:
On 7/21/12 4:13 AM, treydock wrote:
I've begun using Hiera in combination with Foreman, primarily storing
data that is best left in Array/Hash form. I'd like to be able to have
a module, in this case BackupPC
I've begun using Hiera in combination with Foreman, primarily storing data
that is best left in Array/Hash form. I'd like to be able to have a
module, in this case BackupPC, query all the Hiera data for each node where
the backup directories/databases are stored. Then use all that information
I'm attempting to manage my network interfaces through a homebrew module
that takes input from hiera, and then uses augeas to define each ifcfg-*.
Example:
/* Set manditory parameters */
augeas { eth_bond_${name} :
context = /files/etc/sysconfig/network-scripts/ifcfg-${name},
changes
Wow...can we permanency delete this post? Haha, I've been staring at Puppet
modules for a week straight, it's always a spelling error.
Thanks!
- Trey
On Saturday, June 23, 2012 5:34:53 PM UTC-5, Christopher Wood wrote:
netmark?
On Sat, Jun 23, 2012 at 02:37:04PM -0700, treydock wrote
Setting up a HA iSCSI / NFS target using this document,
http://www.linbit.com/fileadmin/tech-guides/ha-iscsi.pdf, and I am unable
to find a way to use the puppetlabs-corosync module to emulate this command
crm(live)configure# primitive p_drbd_coraid23 ocf:linbit:drbd \
params
I've begun moving some of my modules the using hiera lookups in place of
parameters being defined in a host's node entry. For data such as that I
figure I can document the format of what the module expects from the yaml
files, but if I use hiera to replace the typical module::params, how do I
rubygems-1.37 is correct for RHEL 6. rubygems is the gem program,
ie package manager for ruby, it's not a subset or Ruby. Do you have
EPEL enabled ? You'll need that to satisfy some gem dependencies.
The package your missing is rubygem-rake.
On Feb 10, 5:02 pm, jcbollinger
I've just installed Puppet Enterprise 2.0, and noticed the
pe_mcollective module that is provided is failing. I've made no
changes to the modules, this is a fresh install. The system is CentOS
6.0 x86_64 updated to CR.
This is the error,
---
#/opt/puppet/sbin/puppetd --test -v
On Nov 1, 6:50 pm, treydock treyd...@gmail.com wrote:
On Oct 31, 3:09 pm, Dan Bode d...@puppetlabs.com wrote:
On Mon, Oct 31, 2011 at 12:44 PM, treydock treyd...@gmail.com wrote:
On Oct 31, 1:56 pm, treydock treyd...@gmail.com wrote:
On Oct 31, 1:05 pm, Dan Bode d
On Oct 31, 3:09 pm, Dan Bode d...@puppetlabs.com wrote:
On Mon, Oct 31, 2011 at 12:44 PM, treydock treyd...@gmail.com wrote:
On Oct 31, 1:56 pm, treydock treyd...@gmail.com wrote:
On Oct 31, 1:05 pm, Dan Bode d...@puppetlabs.com wrote:
On Mon, Oct 31, 2011 at 10:55 AM, treydock treyd
400 on
SERVER: Invalid parameter root_password at /etc/puppet/manifests/
nodes.pp:882 on node puppetnode1.tld
The definition looks like this,
node 'puppetnode1.tld' {
class { 'mysql::server':
root_password = 'test'
}
database_user { 'treydock@localhost
On Oct 31, 12:26 pm, Dan Bode d...@puppetlabs.com wrote:
you are running into a documentation issue. All of the configuration was
moved to a new parameter called: config_hash. I can submit a patch
On Mon, Oct 31, 2011 at 10:01 AM, treydock treyd...@gmail.com wrote:
I'm working
On Oct 31, 1:05 pm, Dan Bode d...@puppetlabs.com wrote:
On Mon, Oct 31, 2011 at 10:55 AM, treydock treyd...@gmail.com wrote:
On Oct 31, 12:26 pm, Dan Bode d...@puppetlabs.com wrote:
you are running into a documentation issue. All of the configuration was
moved to a new parameter called
On Oct 31, 1:56 pm, treydock treyd...@gmail.com wrote:
On Oct 31, 1:05 pm, Dan Bode d...@puppetlabs.com wrote:
On Mon, Oct 31, 2011 at 10:55 AM, treydock treyd...@gmail.com wrote:
On Oct 31, 12:26 pm, Dan Bode d...@puppetlabs.com wrote:
you are running into a documentation
in
the Cron job to spread load on the master and so far it works well.
On Sep 24, 2011 7:22 AM, treydock treyd...@gmail.com wrote:
On Sep 23, 5:42 pm, Brian Gupta brian.gu...@brandorr.com wrote:
Over the years many shops have come to start running puppet via cron to
address memory leaks
On Sep 23, 5:42 pm, Brian Gupta brian.gu...@brandorr.com wrote:
Over the years many shops have come to start running puppet via cron to
address memory leaks in earlier versions of Ruby, but the official position
was that puppet was meant to be run as a continually running service.
I am
On Sep 19, 1:40 pm, Jo Rhett jrh...@netconsonance.com wrote:
On Sep 19, 2011, at 11:23 AM, Mr. E. wrote:
I need latest documentation on how to install and configure Puppet
master and Puppet client in CentOS environment. The CentOS version is
5.4 and Puppet version is 0.22.4.
Puppet
On Sep 1, 4:47 am, Daniel Maher dma...@milestonelab.com wrote:
On 09/01/2011 04:32 AM, col yte wrote:
Hi folks,
I was curious if anyone would be willing to share how they organize
their puppet implementation. Perhaps something similar to what you'll
find
On Sep 7, 1:10 am, Ohad Levy ohadl...@gmail.com wrote:
On Tue, Sep 6, 2011 at 6:44 PM, treydock treyd...@gmail.com wrote:
I've recently been looking to move my KVM management (currently via
Puppet and virt-manager) to something web-based and robust (ie
Cloud), and came across OpenQRM
I've recently been looking to move my KVM management (currently via
Puppet and virt-manager) to something web-based and robust (ie
Cloud), and came across OpenQRM. Looking at the features list it
mentions puppet Class/Machine management. Has anyone that uses
Puppet extensively given this a try?
On Sep 1, 8:03 am, jcbollinger john.bollin...@stjude.org wrote:
On Aug 31, 8:09 pm, treydock treyd...@gmail.com wrote:
I have a file resource defined to be owned by a group that is
accessible via samba/winbind (AD based group), but every time Puppet
runs automatically (every 30 min
I have a file resource defined to be owned by a group that is
accessible via samba/winbind (AD based group), but every time Puppet
runs automatically (every 30 min) the run fails with this error ,
(sensitive information removed)
(/Stage[main]//Node[node1.tld]/Apache::Vhost[vhost1]/File[/var/www/
I've written my first attempt at a custom puppet function, and it
passes all the suggested test's from the Puppet documentation, but
when called from a test module it doesn't seem to be found.
Successful tests...
irb(main):001:0 require 'puppet'
= true
irb(main):002:0 require
Does anyone have some examples of using this create_resources
function, https://github.com/puppetlabs/puppetlabs-create_resources,
? Based on the README example I can't figure out exactly how to
change from using defines to using this function. Maybe I
misunderstand the purpose of
Ah ok! That makes more sense now.
Thanks
- Trey
On Aug 17, 12:59 pm, Nan Liu n...@puppetlabs.com wrote:
On Wed, Aug 17, 2011 at 10:27 AM, treydock treyd...@gmail.com wrote:
Does anyone have some examples of using this create_resources
function,https://github.com/puppetlabs/puppetlabs
On Aug 17, 12:59 pm, Nan Liu n...@puppetlabs.com wrote:
On Wed, Aug 17, 2011 at 10:27 AM, treydock treyd...@gmail.com wrote:
Does anyone have some examples of using this create_resources
function,https://github.com/puppetlabs/puppetlabs-create_resources,
? Based on the README example I
I have a puppet module to manage Network UPS Tools, but am having
trouble getting Puppet to be able to start the ups service without
error. What's strange is the service starts just fine, but Puppet
returns an error.
Here's the service resource I defined...
package { 'nut-client':
I have a module for backuppc, and am trying to pass a hash to a define
to create a single script and the necessary directories. What I can't
seem to figure out how to do is have this hash's values be used to
create files / directories and also populate a template.
Here's the hash...
, 5:59 pm, Nan Liu n...@puppetlabs.com wrote:
On Thu, Aug 11, 2011 at 4:00 PM, treydock treyd...@gmail.com wrote:
I have a module for backuppc, and am trying to pass a hash to a define
to create a single script and the necessary directories. What I can't
seem to figure out how to do is have
To get the version you'll likely have to use facts, but once you have
the facts you can use something like the following...
file {
/etc/pam.d/system-auth-ac:
source = $operatingsystemrelease ? {
Is anyone having success with #includedir option in sudo? I have a
module that uses a definition to create files in /etc/sudoers.d/ which
is referenced in the main suders file as #includedir /etc/sudoers,
but these entries are not getting referenced when sudo is used.
I'm running CentOS 5 and 6,
From the sudoer docs it mentioned making the files in /etc/sudoers.d
be 440, but what about the folder? Here's the perms on /etc/sudoers.d
drwxr-xr-x 2 root root 4096 Jul 26 19:16 .
drwxr-xr-x. 64 root root 4096 Jul 26 19:16 ..
-r--r- 1 root root 53 Jul 26 19:16 zabbix-puppet
- Trey
wrote:
On 08/01/2011 01:41 PM, treydock wrote:
#includedir /etc/sudoers.d
Maybe without the quotation marks?
--
vagn
--
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
Is there currently a way to import existing puppet modules and classes
into the puppet-dashboard?
If not , will defining them in puppet-dashboard make the nodes aware
of modules already created in puppet?
I found this issue opened on the subject,
http://projects.puppetlabs.com/issues/3503,
but
I've begun using the spec file provided in the puppet and facter
sources to build my own RPMs. So far to make the provided work with
2.7.1, I've made these changes...
The addition of ruby-shadow requirement and the namespace-auth.conf
are not necessary. I added ruby-shadow to force it always
I've begun using the spec file provided in the puppet and facter
sources to build my own RPMs. So far to make the provided work with
2.7.1, I've made these changes...
The addition of ruby-shadow requirement and the namespace-auth.conf
are not necessary. I added ruby-shadow to force it always
I think the way I posted the contents of the modules may have been
misleading, as I do actually have each class in it's own file so
kvm::host class has it's own host.pp file. So far I've actually
noticed this problem only on my modules that make use of the
autoloading, so each class in it's own
PM, treydock wrote:
What is the preferred method for running the puppet client in OS X?
So far all methods I've tried seem to default to running the client as
the root user. Should this be changed to run as a puppet user?
Should I explicitly define puppet as the user in puppet.conf
catalog
That module is a bit large to paste in here, but it can be viewed at
https://github.com/treydock/puppet-zabbix.
The other failures are on similarly designed modules and I've also
noticed that one very basic modules seem to be failing randomly on two
clients, both are 2.6.8
err
What is the preferred method for running the puppet client in OS X?
So far all methods I've tried seem to default to running the client as
the root user. Should this be changed to run as a puppet user?
Should I explicitly define puppet as the user in puppet.conf?
As a test I ran puppetd --test
Here's an example of how I have done this, and also a good way to test
the idea...
I created test.pp with these contents...you can also specify the
$apparray else where, for example in the node definition
$apparray = {
app1 = { 'path' = '/test/path1', 'command' = 'cmd1' },
app2 = {
Thanks John, the if has_variable was the key and allowed me to
remove the default variable definition.
If anyone is interested I posted an explanation and link to the source
here, http://itscblog.tamu.edu/managing-zabbix-agents-with-puppet/.
Thanks
- Trey
On Jun 6, 8:38 am, jcbollinger
configurations I've implemented effecting use of reports
Thanks
- Trey
On Jun 8, 10:57 am, James Turnbull ja...@puppetlabs.com wrote:
treydock wrote:
My [master] has :
report = true
reports = http, store, xmpp
pluginsync = true
The [agent] includes:
report = true
:
treydock wrote:
I don't have any lines like that no.
Could the daemon line for puppetmaster be effecting this? Is the --
reports option necessary since my puppet.conf has that specified?
PUPPETMASTER_EXTRA_OPTS=--reports puppet_dashboard --debug
Other than that and my puppet.conf I
Scratch my last question, had to restart puppetmaster.
Thanks again for your help and these plugins
- Trey
On Jun 8, 5:01 pm, treydock treyd...@gmail.com wrote:
That did it! I'm now getting messages over Jabber upon failure!!
Is the debug output you refered to earlier, Sending status
...@puppetlabs.com wrote:
treydock wrote:
The report processor was synced to /var/lib/puppet/lib/reports/ . I
enabled puppetmaster to run in debug mode but haven't seen anything
mentioning reports when I run test runs. I purposly misspelled a
module for the puppetmaster and run puppetd --test
place I should be looking?
Thanks
- Trey
On Jun 7, 9:29 am, James Turnbull ja...@puppetlabs.com wrote:
treydock wrote:
This is the output from master.log during the failed puppet run.
Sorry I meant the output from the master daemon puppetmasterd or puppet
master.
Thanks
James
--
James
Ah that did the trick...now a new error. I tried simplifying the
module from camptocamp, https://github.com/camptocamp/puppet-dhcp, but
a lot of it's usage I don't understand, and as such my
simplification just broke it. I've got it much farther now...near
the end of puppet run I get this
to
all clients? Could that file configuration be sent to all clients
from the puppet-xmpp module or should I create another module for
that , something like plugins ?
Thanks!
- Trey
On Jun 7, 3:42 pm, James Turnbull ja...@puppetlabs.com wrote:
treydock wrote:
Excuse the dumb question, but what
not include
pluginsync = true on the clients?
Thanks
- Trey
On Jun 7, 7:32 pm, James Turnbull ja...@puppetlabs.com wrote:
treydock wrote:
Ok I restarted puppetmaster daemon and then broke a module to create a
failed puppet run on the same host as the master...and here's /var/log/
messages from
b64_zlib_yaml
Thanks
- Trey
On Jun 5, 12:02 pm, James Turnbull ja...@puppetlabs.com wrote:
treydock wrote:
These will be most useful!! Thank you.
How can I test that these are functioning? I have setup the XMPP as
well as modified that to send emails. However when I purposely cause
a puppet
These will be most useful!! Thank you.
How can I test that these are functioning? I have setup the XMPP as
well as modified that to send emails. However when I purposely cause
a puppet run to fail I do not receive either email or jabber message.
Thanks
- Trey
On May 31, 10:09 am, James
I am getting the following error on about every other manual run of
puppet... (hostnames removed)
err: Could not retrieve catalog from remote server: Error 400 on
SERVER: Failed to parse template zabbix/userparameter_mysql_conf.erb:
Could not find value for 'zabbix_mysql_user_parameters' at
Wow I can't believe that's all that was keeping me from having my
filebucket work in the same manner described by LawrleC.
The primary reason I want to use filebucket is to view changes in
Puppet-dashboard. Now that my filebucket works I only have 1/2 the
files viewable in puppet-dashboard.
In
...@gmail.com wrote:
On May 24, 2011, at 7:58 PM, treydock wrote:
I have a similar problem I can't seem to solve...here's what I'm
trying to do.
I have two modules, backuppc_client and sudo. Right now I have a node
variable that I assign to each node that is used in the sudo module's
I don't know how helpful this would be but for now I think I found a
workaround of sorts for my small environment.
I commented out the following in my puppet.conf...
facts_terminus = inventory_active_record
dbadapter = mysql
dbname = puppet_inv
dbuser = puppet_inv
I have a similar problem I can't seem to solve...here's what I'm
trying to do.
I have two modules, backuppc_client and sudo. Right now I have a node
variable that I assign to each node that is used in the sudo module's
template to add the necessary entry. For example
---manifests/node.pp
The worlds largest online language learning community
On Fri, May 20, 2011 at 10:01 PM, treydock treyd...@gmail.com wrote:
Every few days I have to restart the puppetmaster process due to this
error
Could not read YAML data for node Too many open files.
I have 9 clients being
Every few days I have to restart the puppetmaster process due to this
error
Could not read YAML data for node Too many open files.
I have 9 clients being controlled by Puppet and each one of those will
generate the same error once this happens. Running 'lsof' during this
time shows me
I'm on the extremely small scale end from what has been previously
described, but this could prove useful to those who want to manage a
small number of hosts and are curious how little they need to run
Puppet. I've just begun using Puppet, and so only have 10 hosts right
now, but here's what I'm
For some reason I am unable to run dry runs of the puppet client on
my puppetmaster server. Running puppetd with the --test, --noop and
verbose / debug flags results in nothing for about a minute or two
then this output...
$ time puppetd --test --noop -v
err: Could not retrieve catalog from
Here's the output using debug option.
$ puppetd --debug -v --test --noop
debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/
dscl does not exist
debug: Failed to load library 'ldap' for feature 'ldap'
debug: Puppet::Type::User::ProviderLdap: feature ldap is missing
debug:
I ran into this same challenge just a few days ago. I run mostly
CentOS and syslogd is installed by default, but I prefer to run
rsyslog. Here's a post,
http://itscblog.tamu.edu/managing-syslog-and-log-forwarding-with-puppet/
,I just did on my blog that has the recipes I used for syslog
In my puppet-dashboard when a change is made to files and it shows the
MD5 sums I am never presented a link to view the file or any diffs of
those files. I assume that the text between '[' and ']' is supposed
to be the link but it's just plain text. This is when viewing
individual reports in
It's not ideal but this could very easily be achieved by with Zabbix.
With Zabbix you can have a check, running for example every 30
seconds, that runs a checksum on a specific file. Then a trigger that
is activated if the last known checksum varies from the current
checksum, here's an example
93 matches
Mail list logo
