Great! Thank you a lot!
It works!
On Wednesday, March 27, 2013 6:21:09 PM UTC+4, Ken Barber wrote:
>
> Here is a better working example as a gist, with what you should see
> in the puppetdb.log if it was successful:
>
> https://gist.github.com/kbarber/5254512
>
> On Wed, Mar 27, 2013 at 2:19
On Wednesday, March 27, 2013 6:22:05 PM UTC-7, Philip Brown wrote:
>
>
> nope, nothing.
> I tried your suggestion of explicitly setting it.
> It gets ignored.
>
>
Oh wait, I just had another idea. File ownership/permissions? If you wrote
it as root and it's only accessible to root, puppet mas
On Wednesday, March 27, 2013 6:22:05 PM UTC-7, Philip Brown wrote:
>
>
>
> nope, nothing.
> I tried your suggestion of explicitly setting it.
> It gets ignored.
>
Weird. I'm out of ideas at this point.
> Would be real nice if there was some way to strace the puppetmaster
> demon doing its
Hi all,
I got the result..i completely once unsinstalled the puppet agent which i
installed and then in /etc/hosts i added the name of the server which am
using, beside local host..then it started working..
I added this tbms in this line --127.0.0.1
localhost.loca
On Wed, Mar 27, 2013 at 2:10 PM, Nick Fagerlund
wrote:
> First off, check Puppet's hiera_config setting
> (http://docs.puppetlabs.com/references/3.1.1/configuration.html#hieraconfig)
> -- is there a value in your puppet.conf?
nope, nothing.
I tried your suggestion of explicitly setting it.
It ge
On Saturday, 23 March 2013 00:50:11 UTC+11, jcbollinger wrote:
>
>
>
> On Thursday, March 21, 2013 6:16:07 PM UTC-5, Sam Morrison wrote:
>>
>> Hi,
>>
>> I've been battling with trying to get our puppet to do the following:
>>
>> Install all sources.list, apt-keys
>> then:
>> Run an apt-get update
Hiera 1.2.0-rc3 is a feature release candidate in the 1.x series with
new features and bug fixes. 1.2.0-rc3 addresses issue #19792 by
providing a better error message when the deep_merge library is not
available.
Downloads are available at:
* Source: https://downloads.puppetlabs.com/hiera/hiera-1
On Wednesday, March 27, 2013 4:01:12 PM UTC-7, John Smith wrote:
> I'm now trying to use system::sshd.
> I can see that sshd takes a hash as a parameter instead of an array.
> However, all my attempts to guess or otherwise determine the correct
> syntax are failing.
> Here's what I've got so far
You need to enable the optional repository.
On 27 Mar 2013 21:38, "T.J. Yang" wrote:
> Hi,
> I followed puppetlab procedure to install open source version of puppet
> agent 3.x.
> It works for CentOS 6.4 but not RHEL 6.4, anyone has pointer where I
> missed ?
>
> [root@mon04 ~]# yum install puppe
I'm now trying to use system::sshd.
I can see that sshd takes a hash as a parameter instead of an array.
However, all my attempts to guess or otherwise determine the correct syntax
are failing.
Here's what I've got so far
$sshd = {
'AllowGroups' :
value => ['root' , 'IT', 'EN
Hi,
I followed puppetlab procedure to install open source version of puppet
agent 3.x.
It works for CentOS 6.4 but not RHEL 6.4, anyone has pointer where I missed
?
[root@mon04 ~]# yum install puppet
Loaded plugins: product-id, refresh-packagekit, security,
subscription-manager
This system is r
On Wednesday, March 27, 2013 11:29:30 AM UTC-7, Philip Brown wrote:
>
>
> I set up a /etc/puppet/hiera.yaml, pointing to a special hieradata
> directory...but clients were not seeing the values I populated.
>
First off, check Puppet's hiera_config setting
(http://docs.puppetlabs.com/references
Almost 4-5% of the total number of nodes are not receiving catalog from the
master on an hourly run. We have about 250 nodes. The nodes that are
receiving this error are rather random. The hourly cron happens almost at
the same time. Is there any configuration changes for Puppet that can be
Perhaps try:
# ln -sf /etc/puppet/hiera.yaml /etc/hiera.yaml
Also you can use the hiera command-line utility [1] to test - for example:
# hiera --debug philcheck::value
- Keith
[1] http://docs.puppetlabs.com/hiera/1/command_line.html
On 27 March 2013 18:29, Philip Brown wrote:
> We'
> Puppet (err): Could not retrieve catalog from remote server: execution
> expired
> Puppet (notice): Using cached catalog
>
> /File[/etc/security/http/key.pem] (err): Could not evaluate: SSL_connect
> SYSCALL returned=5 errno=0 state=SSLv2/v3 read server hello A Could not
> retrieve file metadata
To pitch my two cents as information. I was searching about this error. In
my case I am not running puppetDB.
Here are the versions that I am using,
puppet-server-3.0.2-1.el5
puppet-3.0.2-1.el5
java-1.6.0-openjdk-1.6.0.0-1.27.1.10.8.el5_8
ruby-1.8.7.352-5.el5
openssl-0.9.8e-22.el5_8.4
Error oc
I'm also running in to this. Has anyone managed to get the puppet firewall
module to manage both iptables and ip6tables?
On Monday, December 3, 2012 6:38:17 PM UTC-5, David Mesler wrote:
>
> Julia, did you ever figure this out? I'm running into this issue as well.
>
> --david
>
> On Tuesday, May
If your role class declares other classes you probably being bitten
by http://projects.puppetlabs.com/issues/8040. That is, and classes
declared in the role class are not confined by the dependency graph. It's
something they're working on fixing, but in the meantime, the recomendation
is to use
We're using the puppetlabs puppet rpms, on redhat 6.
puppet server version: 3.1.1
I wanted to start using hiera for some databinding type purposes.
I set up a /etc/puppet/hiera.yaml, pointing to a special hieradata
directory...but clients were not seeing the values I populated.
So I made a very
I'm using Puppet 3.1.1 in standalone mode. I'm running "puppet apply" like
this:
basedir="$( dirname $( readlink -f "${0}" ) )"
puppet apply \
--detailed-exitcodes \
--modulepath=${basedir}/modules \
--hiera_config=${basedir}/hiera.yaml \
${basedir}/manife
Here is a better working example as a gist, with what you should see
in the puppetdb.log if it was successful:
https://gist.github.com/kbarber/5254512
On Wed, Mar 27, 2013 at 2:19 PM, Ken Barber wrote:
> Try:
>
> curl -vv -G -H "Accept: application/json"
> 'http://localhost:8080/v2/commands' --d
Try:
curl -vv -G -H "Accept: application/json"
'http://localhost:8080/v2/commands' --data-urlencode
'payload={"command":"deactivate node","version":
1,"payload":"\"yournodename\""}'
The command needs to be submitted with the form parameter 'payload'.
The 'payload' part of the command is itself a
Hello, all
I'm trying to use puppetdb's deactivate api call but can't find how to
correctly pass node name via payload.
Calls like
`curl -G -H "Accept: application/json" 'http://localhost:8080/v2/commands'
--data-urlencode '{ "command": "deactivate node", "version": 1, "payload":
{ "name": "no
On Tuesday, March 26, 2013 7:02:34 AM UTC-5, Sergio Jimenez wrote:
>
>
> Not really sure about it (pretty new in puppet) but ... what about
> parametrized classes? You could define default values for parameters in the
> class or overwrite them when using the class.
>
>
If you look at his code,
Russell and Hugh - any luck downgrading to openjdk-6?
An alternative thing to try - I found this in the openssl changelog:
http://changelogs.ubuntu.com/changelogs/pool/main/o/openssl/openssl_1.0.1-4ubuntu5.8/changelog.
Looks like the patch for CVE-2013-0169 was reverted due to a bug, but
it has no
+1
Last time I tried writing tests, I just gave up because we started using
hiera
--
Nikola
On Fri, Mar 22, 2013 at 06:26:09PM +0100, Maarten Thibaut (mthibaut) wrote:
> Hi,
>
> I'm having a hard time figuring out how to make rake spec tests work
> correctly with hiera and puppet 3. Should I
I think that this is mostly because of lens that are written this way.
We shouldn't blame them that this is "poorly" written in my opinion.
It is just more restrictive. Lens that I have written accept a
regular expression as an identifier instead of listing them.
Best, Nikola
On Fri, Mar 22, 2013
27 matches
Mail list logo
