Anyone has a good hint on how to get better debug info on this problem?
Other nodes work correctly so puppet master is not broken just the catalog
of the node I'm working on, but cannot manage to find the bug.
Luca
Il giorno giovedì 6 dicembre 2012 12:14:51 UTC+1, Luca Gioppo ha scritto:
OK
How about creating a processorcorecount and processorthreadcount with
correct meanings? That then leaves the option to deprecate
processorcount.
I've realised that at some point in the past I have created a
processorthreadcount fact because I needed a consistent source of this
information on both
I've installed the augeas rpm (0.10.0-3.fc17.x86_64) to troubleshoot a
problem I was having with augeas and ensuring a line existed in
/etc/cron.allow. I think something's up because neither the augeas within
my manifest nor the augtool are accomplishing much of anything:
# augtool print
Hi Drew,
Yes, i did all what you suggest, ive checked out if the module is in
master, ive used pluginsync on client so i dont know what to do... how i
follow...:S
Cheers and thanks for the answer
On Thursday, 6 December 2012 13:48:15 UTC+1, Drew Blessing wrote:
Hi Fran,
There's a couple
On Thursday, December 6, 2012 9:13:58 PM UTC-6, cynipe wrote:
I'm currently trying to create icinga module and the icinga-web and
icinga-idoutils-libdbi-mysql from rpmforge
store the initial sql file in version numbered
directory(/usr/share/doc/icinga-web-1.7.2/~~~).
So, I try to
On Thursday, December 6, 2012 9:28:29 AM UTC-6, Luca Gioppo wrote:
Ruby version 1.8.7 on both master and agent.
But on the agent I get:
Error: Could not retrieve catalog from remote server: Error 400 on SERVER:
can't instantiate uninitialized class
Debug: Using cached catalog for
Hi, I posted this over on
serverfaulthttp://serverfault.com/questions/455820/puppet-and-launchd-services
as
well, but I realized this is probably a better forum for it.
It seems like I can't launch launchd services with puppet on my OSX
machines. It seems to me that the following should work:
Hello,
Am 04.12.2012 16:26, schrieb Dennis Hoppe:
does anybody know why the puppetlabs-lvm module is not working at Debian
Wheezy and Ubuntu Quantal?
I am getting the following error message:
root@pclient2:~# puppet agent --test
Ignoring --listen on onetime run
Info: Retrieving plugin
I am accepting the fact that the initial version of a module will not be
perfect and that it will be need to be updated in the future. I am looking
for ideas on how to manage the development life cycle of modules and to
control the roll out of the module being applied to managed nodes. Please
Hello Everybody,
I am trying to install the puppetdb on the same
machine as am running my puppetmaster.
I am getting the following error when am trying to connect the agent:
Error: Could not retrieve catalog from remote server: Error 400 on SERVER:
Failed to submit
Hi,
I am experimenting with foreman's apache module and there is this class
here:
class apache::service {
$http_service = $::operatingsystem ? {
/(Debian|Ubuntu)/ = 'apache2',
default = 'httpd',
}
service { $http_service:
ensure = running,
enable = true,
Hi,
In the foreman apache module, I get an error when trying to apply the
::config part of it.
The section that causes problem is:
file{ ${apache::params::configdir}/${apache::params::conffile}:
mode= '0644',
notify = Exec['reload-apache'],
require =
On 12/07/2012 03:24 AM, John Warburton wrote:
We were tripped up (we shot ourselves) on facter 1.6.x looking in a missing
NFS mounted /usr/local, which got me thinking - does facter 2.x really need
this?
https://github.com/puppetlabs/facter/blob/2.x/lib/facter/Cfkey.rb
And why shouldn't it?
On Dec 7, 2012, at 9:07 AM, Schofield wrote:
I am accepting the fact that the initial version of a module will not be
perfect and that it will be need to be updated in the future. I am looking
for ideas on how to manage the development life cycle of modules and to
control the roll out of
Hello lovelies,
Our team is deliberating a few different options for the hierification of our
modules; and wanted to poll the collective genius before making our decision.
As we all know, there are certain attributes of a package which are, by
default, consistent on an OS... say, the name of a
- Original Message -
From: Wolf Noble wno...@datapipe.com
To: puppet-users@googlegroups.com puppet-users@googlegroups.com
Sent: Friday, December 7, 2012 8:08:40 PM
Subject: [Puppet Users] Poll for thoughts on hierifying modules and OS
default differences
Hello lovelies,
Our
I tend to take the stance that things in modules that AREN'T specific to
your company (i.e. things that could help others - like names of packages
on other OS platforms, config file paths, etc) should be kept in the Module
and not locked up in Hiera data (that way, both people using and NOT using
I was just wodnering - has anyone puppetized hyperic? Specifically, the
configuration of groups, resources, alertdefs etc.
I'm starting such a project, but am unsure how to approach some of it. I
think eventually I will wind up needing to do a set of types and providers,
comparable to the
- Original Message -
From: Gary Larizza g...@puppetlabs.com
To: puppet-users@googlegroups.com
Sent: Friday, December 7, 2012 8:35:48 PM
Subject: Re: [Puppet Users] Poll for thoughts on hierifying modules and OS
default differences
I tend to take the stance that things in modules
I realize that maybe these modules have been built to be used only with
foreman. Is that a decent assumption? And if so, is there a simple apache
module somewhere? I only want to do the basics, check packages, service,
and create vhosts. I may be better writing my own...
On Friday,
I created a firewall module. In firewall/manifests/init.pp i have the
following.
class firewall {
## Always persist firewall rules
exec { 'persist-firewall':
command = '/sbin/iptables-save /etc/sysconfig/iptables',
refreshonly = true,
}
## These defaults ensure that the
On Friday, December 7, 2012 1:37:20 PM UTC-6, Ugo Bellavance wrote:
I realize that maybe these modules have been built to be used only with
foreman. Is that a decent assumption? And if so, is there a simple apache
module somewhere? I only want to do the basics, check packages, service,
Hi Gary,
I know what you mean, and agree for modules destined to be released to the wild.
unfortunately, we have a diverse enough environment that even the defaults
occasionally need to be overridden; hence the hierification.
(I've got all that logic wrapped into a case statement based on if
On Fri, Dec 7, 2012 at 9:37 PM, Ugo Bellavance u...@lubik.ca wrote:
I realize that maybe these modules have been built to be used only with
foreman. Is that a decent assumption? And if so, is there a simple apache
module somewhere? I only want to do the basics, check packages, service,
and
Understandable, thank you for that clarification. The issue I am facing
comes when I am using a define and I need to call that custom variable set
in another class that calls the define. Please see the example below.
Though this works as I want it to below, I am getting a syntax error. If
I just recently spun up a new host using an old hostname, and when managing
the certificates, I noticed that the newly generated cert was listed as
sha256, while all of my earlier certs were listed as sha1. I guess this is
a new default or something, and I like better security, so I'd like all
On Friday, December 7, 2012 2:56:30 PM UTC-5, ohad wrote:
On Fri, Dec 7, 2012 at 9:37 PM, Ugo Bellavance ug...@lubik.cajavascript:
wrote:
I realize that maybe these modules have been built to be used only with
foreman. Is that a decent assumption? And if so, is there a simple apache
Hi,
We've created modules based on the standard, but I had to remove the
metadata.json file in the modules because I got these errors when the
metadata.json file was there: Could not retrieve catalog from remote
server: Error 400 on SERVER: No source module metadata provided for
modulename.
28 matches
Mail list logo
