> basically anyone attempting to do anything reasonable with ruby on RHEL 5.x
> (or any of the free repackaged distributions of RHEL 5.x) knows that 1.8.5
> version is just short of useless and has implemented other fixes.
Some comments on this thread, and current software development trends
in
Switching to puppet (2.7.3) for managing my OS X Lion systems, I'm
finding group membership not being updated.
Starting out, user dt is not a member of group dt-grp:
# dscl . read /groups/dt-grp | grep GroupMembership
GroupMembership:
...Run puppet, says it adds to the group:
# puppet agent --t
I'm working with custom facts with facter 1.7.2. I've created a fact file
with an ntp configuration fact in it:
# grep ntp_conf /etc/facter/facts.d/myfacts.txt
v_ntp__ntp_conf=puppet:///modules/ntp/DEFAULT/ntp_conf
facter knows the fact is there:
# facter -p v_ntp__ntp_conf
puppet:///modules/
On 9/10/13 5:49 PM, Denmat wrote:
On 11/09/2013, at 1:38, David Thompson mailto:dthomp...@waisman.wisc.edu>> wrote:
I'm working with custom facts with facter 1.7.2. I've created a fact
file with an ntp configuration fact in it:
# grep ntp_conf /etc/facter/facts.d/my
vial line ("somefact=somevalue"), the custom fact shows up in facter
but not in puppet.
I also get the same result when I pass the fact as yaml. I tried json,
but got an error about missing the json gem, even though I have the
puppetlabsdep rubygem-json RPM installed.
--
David Thompso
http://docs.puppetlabs.com/guides/custom_facts.html
Is there a reason you think stdlib will fix this?
David
On 12/09/2013, at 1:12, David Thompson mailto:dthomp...@waisman.wisc.edu>> wrote:
On 9/11/13 8:54 AM, jcbollinger wrote:
Lack of response? This is a volunteer community forum, not a pai
e to be collected.
What I do know from querying the database is that all the exported
resources are present in the puppetdb database (in catalog_resources).
Has anyone else run into this, or any hints how to proceed?
Thanks much!
--
David Thompson
Waisman Center Brain Imaging and Behavior Lab
1500 Highl
ource to see if it occurs as well? Perhaps working around the edges
of the problem might prove what it is _not_ which is a start.
Other resources (Package, File) seem to be present for all nodes using
the query@ method described in
http://docs.puppetlabs.com/puppetdb/1.4/api/query/tutorial.h
the puppetdb rest API
only show the Nagios_host resources generated on the nagios server itself.
I'm sure this is a configuration or some other error on my part, but
honestly I'm at a loss where it can be. Any help is greatly appreciated.
--
David Thompson
Waisman Center Brain
On 10/2/13 9:09 AM, jcbollinger wrote:
On Tuesday, October 1, 2013 10:50:42 AM UTC-5, David Thompson wrote:
I continue to be unable to get puppetdb to create nagios resources.
Nitpick: puppetdb does not create resources of any type, in any sense.
That leaves me uncertain whether you
On 10/2/13 9:44 AM, David Thompson wrote:
Do you know whether the exported nagios_host resources in particular are
ending up in the DB?
Just to eliminate postgres as a possible problem source, I changed the
database.ini and switched (back) to the embedded hsqldb database. Same
result with
generally, what is the nature of the correlation (that
you have recognized) between declared nagios host resources and the
machines on which puppet manages those resources?
Yes, sometimes I've gotten some partial Nagios_host data generated on
the nagios server, but never in any discernible
linux-server",
}
}
}
...then in site.pp 'include nagios_config'.
Also, is there any chance of resource parameter overrides being in
play? Specifically, overrides of the Nagios_hosts' 'ensure' parameters?
Nope. I don't do any resource overrides in
our puppetdb server should
dump out everything puppetdb knows about your hosts, including when they
were deactivated (or null if they've not been deactivated).
All the nodes show up via the URL above with null deactivation dates.
--
David Thompson
Waisman Center Brain Imaging and Behavior Lab
1500 Hi
I'm trying to decommission puppetdb, but it's being very persistent. I've
removed the puppetdb-terminus rpm, and commented out the storeconfigs
entries in puppet.conf, but the managed systems can't apply without
puppetdb running on the server. The error messages are:
Warning: Unable to fetch
15 matches
Mail list logo