My problem is similar, the RC is I accidentally deleted the localhost
127.0.0.1 entity in /etc/hosts file, but the puppet.conf relay heavily on
this(i.e. The configuration used localhost a lot), after I appended that
entity, everything works fine, just appended here for your reference.
On
Thanks again for you reply, but it seems like you don't fully understand
what I'm having problems with. So I'll try to clarify it a little more:
1. The current way of using two defines is working flawlessly. So I (at
least partly) understand the concepts surrounding those.
2. Because I have two
Greetings,
we are trying to setup puppetdb, nut our clients get the following error:
Warning: Unable to fetch my node definition, but the agent run will
continue:
Warning: Error 400 on SERVER: Could not retrieve facts for lxa7t.unix.lan:
Failed to submit 'replace facts' command for
Hi all,
I have a application that I schedule via cron. This is a application that
runs once a week, either on Tuesday or Thursday. The scheduling is now done
via Puppet.
I now see that I need to redefine this, on some nodes the application
should for example only run the 3. Tuesday each month,
Hi all
Following on from my previous post Puppet Network
Devices..https://groups.google.com/forum/?fromgroups=#!topic/puppet-users/fuXshtYmhhkI've
now started work on creating a NetApp network device provider for
Puppet...
I'm trying to start simply by just gathering some facts from our
On Mon, Nov 05, 2012 at 01:40:18AM -0800, linux@bami wrote:
Greetings,
we are trying to setup puppetdb, nut our clients get the following error:
Warning: Unable to fetch my node definition, but the agent run will
continue:
Warning: Error 400 on SERVER: Could not retrieve facts for
Ok, after a bit more googling, have solved the NaElement load error...
Tweaked the NaServer.rb file as follows:
#require 'NaElement'
require File.dirname(__FILE__) + /NaElement
I've now successfully loaded the require Netapp SDK files, and started
working through the connection process...
Hi Nikola,
thanks for the response!
here are our configs:
cat /etc/puppet/puppet.conf
[main]
server = lx1ml.unix.lan
logdir = /var/log/puppet
rundir = /var/run/puppet
confdir = /app/puppet/etc
vardir = /app/puppet/var
ssldir = $vardir/ssl
modulepath =
Ok, have fixed that error aswell...
Replaced *':configdir' *with *':confdir'*.
However it's now failing due to the netapp.yml file not being present...
What's confused me is the path it's come up with for *':confdir'*.
According to the debug output, it's trying to use
ESC[0;36mDebugESC[0m:
On Monday, November 5, 2012 4:27:54 PM UTC+11, Michael Stanhke wrote:
1. You may need to file a bug with ruby-lang.org
2. Would static linking help at all with being maintainable?
Thanks Michael. Actually static linking should be fine - I didn't think
of it. I also raised a bug as you
Anyone, noone? The PC has been confirmed now, you can sign up
here: https://www.flickevents.com/puppetcamp-sea-blk-71
Looking forward to seeing you there!
Walter
On Wednesday, 31 October 2012 23:26:52 UTC+1, Walter Heck - OlinData.com
wrote:
Hello,
after doing a successful PuppetCamp in
On Mon, Nov 05, 2012 at 03:32:21AM -0800, linux@bami wrote:
Hi Nikola,
thanks for the response!
here are our configs:
cat /etc/puppet/puppet.conf
[main]
server = lx1ml.unix.lan
logdir = /var/log/puppet
rundir = /var/run/puppet
confdir = /app/puppet/etc
vardir
On Mon, Nov 5, 2012 at 4:23 AM, Alexander Holte-Davidsen
alexander.david...@gmail.com wrote:
Hi all,
I have a application that I schedule via cron. This is a application that
runs once a week, either on Tuesday or Thursday. The scheduling is now done
via Puppet.
I now see that I need to
Hi Nikola,
yes on the puppet master there ist a routes.yaml
[root@lx1ml puppet]# cat routes.yaml
---
master:
facts:
terminus: puppetdb
cache: yaml
And the puppet agent -t runs fine on the puppetdb if we remove the
storeconfig settings from our master puppet.conf
Is it possible to
You cannot directly set up a cron job to run on the N-th (day-of-the-week).
From the manpage crontab(5):
Note: The day of a command’s execution can be specified by two fields — day
of month, and day of week. If both fields are restricted (ie, aren’t *), the
command will be run when
Hi,
so we figured out the first problem.
We had an alias puppetdb.fqdn which was pointing to out puppet dashboard
db. It seems that despite from the entry in the puppetdb.conf, puppet uses
puppetdb as database server.
we changed the alias and now we are getting an ssl error:
Error: Could not
On Monday, November 5, 2012 12:37:45 AM UTC-6, pdurkin wrote:
I'm not convinced that Justin wasn't correct about this being a bug. I'm
having a similar issue
How many people do you need to tell you that the behavior you observe is
intended? File a ticket against the documentation if
On Monday, November 5, 2012 3:48:58 AM UTC-6, Erwin Bogaard wrote:
Thanks again for you reply, but it seems like you don't fully understand
what I'm having problems with. So I'll try to clarify it a little more:
1. The current way of using two defines is working flawlessly. So I (at
least
On Mon, Nov 05, 2012 at 05:36:39AM -0800, linux@bami wrote:
Hi Nikola,
yes on the puppet master there ist a routes.yaml
[root@lx1ml puppet]# cat routes.yaml
---
master:
facts:
terminus: puppetdb
cache: yaml
And the puppet agent -t runs fine on the puppetdb if we remove the
On Mon, Nov 05, 2012 at 06:26:35AM -0800, linux@bami wrote:
Hi,
so we figured out the first problem.
We had an alias puppetdb.fqdn which was pointing to out puppet dashboard
db. It seems that despite from the entry in the puppetdb.conf, puppet uses
puppetdb as database server.
we
Me again...
I pressed on using the /var/lib/puppet... configdir for the time-being, and
with a bit more jiggery pokery, I've managed to successfully register a
NetApp device, and extract some facts from it... And here's the
photographic proof :) :D http://ow.ly/i/15SLN
Now to start looking
Hi,
we solved the problem. removed all files from /etc/puppetdb/ssl and
ran /usr/sbin/puppetdb-ssl-setup.
Thanks for the support!!
greetings
Daniel
Am Montag, 5. November 2012 16:07:43 UTC+1 schrieb nikolavp:
On Mon, Nov 05, 2012 at 05:36:39AM -0800, linux@bami wrote:
Hi Nikola,
I'm trying to use tags in templates.
I have a resource declared as :
define apache::instance($instance_name=$title,$mpm='worker') {
tag(declared-apache-$instance_name)
...
}
this resource is called in the class apache :
class apache{
...
apache::instance{$instances: }
}
and then a
So I dug into this a little more. It has something to do with how puppet
is loading the type definitions.
There appears to be some kind of cache that gets loaded with type
definitions when the first manifest gets processed.
If the first test that gets run is for a class that contains all the
1. I get the following error when I run “puppet device’
err: Could not request certificate: Could not write
/var/opt/lib/pe-puppet/devices/certname/ssl/private_keys/certname.pem to
privatekeydir: Permission denied -
/var/opt/lib/pe-puppet/devices/certname/ssl/private_keys/certname.pem
Looks like a file permissions error - I had similar when I started playing
with puppet device...
Check if the user you're running puppet as has permissions to write to
'/var/opt/lib/pe-puppet/devices'.
HTH
Gav
On Monday, 5 November 2012 16:18:03 UTC, meiji wang wrote:
1. I get the
Ok, moving on then...
I've created a 'netapp_volume' type and provider, and am trying to test it
against one of the existing NetApp device nodes:
*manifests/site.pp* contains:
node 'actint-star-nactl01' {
# Test NetApp volume provider
netapp_volume { 'v_puppet_test':
On Mon, Oct 29, 2012 at 04:36:44PM -0700, Lou wrote:
Hi Lou,
I'm assuming this is possible, but I can't find a good starting point
anywhere, so I'm hoping someone here can help. What I want to do is,
somewhere in the cert approval process, run an extra check before saying
yes.
Is this
On Mon, Nov 05, 2012 at 07:52:02AM -0800, linux@bami wrote:
Hi,
we solved the problem. removed all files from /etc/puppetdb/ssl and
ran /usr/sbin/puppetdb-ssl-setup.
Thanks for the support!!
greetings
Daniel
I am glad that you managed to solve it.
Best, Nikola
Am Montag, 5.
Looks like the below error was caused by some locally cached code that
hadn't been updated by my Git pull :s
Resolved that, and now am getting the following:
$ sudo puppet device -v
Info: starting applying configuration to actint-star-nactl01 at
actint-star-nactl01
Warning: Local
posted reply in mcollective-users group. Sorry for duplicate posts.
On Friday, November 2, 2012 11:34:39 AM UTC-7, R.I. Pienaar wrote:
- Original Message -
From: Bill James billj...@gmail.com javascript:
To: puppet...@googlegroups.com javascript:
Sent: Friday, November 2,
So I thought puppet didn't care about the order of things unless
specifically told. However I've come across one case where it apparently
does care.
This works as expected:
node /^univ\d+\.foo\.edu$/ {
$myvar = foo
include module_that_uses_myvar
}
This one doesn't work as expected
node
To the best of my knowledge, it is resources that can be applied in any order,
not scoped variables.
Your puppet agent will create these files in any order, given that the file
resources have no require/before dependencies:
node myserver {
file { '/tmp/1':
content = 123\n,
}
file {
As I'm in over my head, let's supply you with (part of) the manifests in
question:
The define:
define sugar::definitions_sug_wp (
$template = 'sugar/etc/httpd/conf.d/sugar6x.conf.erb',
$client_domain = $title,
$mysql_rootpwd = $mysql_password,
$mysql_dbname,
After my previous post, I did some more thinking and reasearch. What do you
think about:
- using an if/else-conditional. Would that work?
- using virtual resources? would that work?
On Monday, November 5, 2012 9:17:11 PM UTC+1, Erwin Bogaard wrote:
As I'm in over my head, let's supply you with
In regard to: [Puppet Users] Re: Apply multiple defines in sequence, Erwin...:
Thanks again for you reply, but it seems like you don't fully understand
what I'm having problems with. So I'll try to clarify it a little more:
1. The current way of using two defines is working flawlessly. So I (at
On Monday, November 5, 2012 2:06:09 PM UTC-6, Jist Anidiot wrote:
So I thought puppet didn't care about the order of things unless
specifically told. However I've come across one case where it apparently
does care.
You had a serious misunderstanding. Puppet has numerous sensitivities
Although I change the mode to 0777, Puppet forces the mode to 0750
debug: /File[/var/opt/lib/pe-puppet/devices/certname/state]: Autorequiring
File[/var/opt/lib/pe-puppet/devices/certname]
debug: /File[/var/opt/lib/pe-puppet/devices/certname/clientbucket]/mode:
mode changed '0777' to '0750'
I just switched from an in-house APT module to the Puppetlabs one thinking
that it may solve this, but after looking at the code (And installing to
confirm) it did not.
Seeing Puppet be notified of a change just when `apt-get update` is run
is a bit annoying to me. I was wondering if there was
Try changing the file owner/group to match what you're running puppet as...
Gav
On 5 November 2012 20:51, meiji wang wangme...@gmail.com wrote:
Although I change the mode to 0777, Puppet forces the mode to 0750
debug: /File[/var/opt/lib/pe-puppet/devices/certname/state]: Autorequiring
On Monday, November 5, 2012 2:17:11 PM UTC-6, Erwin Bogaard wrote:
As I'm in over my head, let's supply you with (part of) the manifests in
question:
The define:
define sugar::definitions_sug_wp (
$template = 'sugar/etc/httpd/conf.d/sugar6x.conf.erb',
$client_domain
John and Tim, thanks for your replies and patience.
In the end, the solution of Tim seems to work great! That was what I was
looking for: a relatively straight solution to a relatively straight
problem (at least, that was what I thought to improve the previous
situation).
As a novice to
On Monday, November 5, 2012 3:03:57 PM UTC-6, Thomas Biddle wrote:
I just switched from an in-house APT module to the Puppetlabs one thinking
that it may solve this, but after looking at the code (And installing to
confirm) it did not.
Seeing Puppet be notified of a change just when
Hi Jean, you can track this issue under bug #9862
- https://projects.puppetlabs.com/issues/9862
So, yes you will need root or sudo to edit /etc/shells, that is just unix
permissions at work; as an immediate workaround to the error you see with
sudo you can run with '--group 0' (a number
Puppet Dashboard 1.2.13 is a maintenance and bugfix release of Puppet Dashboard.
This release is available for download at:
https://downloads.puppetlabs.com/dashboard/puppet-dashboard-1.2.13.tar.gz
Debian packages are available at
https://apt.puppetlabs.com
RPM packages are available at
hi all,
How are you? I have a question on the class dependencies.
This is my init.pp script looks like
class mapr {
Class['mapr::install'] - Class[mapr::config]
include mapr::install,
mapr::config
}
In my mapr::install class i have another few lines of
Yup, this is the classes-can't-contain-classes problem. It sucks, everyone
runs into it eventually, and it's explained in detail here:
http://docs.puppetlabs.com/puppet/3/reference/lang_containment.html#known-issues
http://projects.puppetlabs.com/issues/8040
You'll need to use the anchor
Thanks for the info.
Do you have more descriptive explanation on the anchor pattern? From what
you have pasted on this link isn't sound descriptive. Or can you give me a
pattern of codes instead? thanks!
On Tuesday, 6 November 2012 13:07:53 UTC+8, Nick Fagerlund wrote:
Yup, this is the
Thanks John, I'll inline my responses
Paul
On Monday, November 5, 2012 6:26:55 PM UTC+4, jcbollinger wrote:
On Monday, November 5, 2012 12:37:45 AM UTC-6, pdurkin wrote:
I'm not convinced that Justin wasn't correct about this being a bug. I'm
having a similar issue
How many people
Hi guys,
I am trying to understand fact precedence and pluginsync.
Documentation says, by default, the weight of a fact is the number of
confines for that fact, so that more specific facts are evaluated first.
1. I made a module core which adds a facter test and has filename
test.rb. (in
50 matches
Mail list logo
