On Nov 1, 9:42 pm, Luke Bigum wrote:
> It also has to do with Puppet's implementation of File resources: it
> creates in memory Ruby objects for every file and directory it finds
[...]
>From some other reading I gathered this was what it's doing. The jetty
dir is up to half a dozen levels deep w
Thanks for your solution Luke, this is much faster. For future
reference here's the modification I made (there were a couple of typos
and/or I've got a different dialect of find):
exec { "enforce ${jetty_install_dir} permissions":
command => "/usr/bin/find ${jetty_install_dir} ! -user jetty -o !
Hi.
I've been reading up on inheritance, parameterized classes and whatnot, and
basically wish to see whether I'm thinking right or if I'm just confused(more
than usual).
I'll use a trivial NFS module as an example since it should cover the basic
questions and has some interesting dependencies.
> Thanks Chris, that's helpful. I am wondering if I should be mixing
> Ruby DSL manifests with the Puppet DSL manifests. Is there any
> recommended practice for keeping both styles together?
Afaik you can mix both DSL. If one file in a module ends with .rb it's
ruby dsl, if it ends with .pp it's
Hi all,
I've downloaded and installed puppet-concat module and was trying to
use it.
After reading doc, I've set concatdir to /tmp only for test purpose,
but I'm wondering what is a good value for concatdir.
Maybe /var/lib/puppet/concat? I guess I have to create it, am I right?
So, following the
- Original Message -
> Hi all,
>
> I've downloaded and installed puppet-concat module and was trying to
> use it.
>
> After reading doc, I've set concatdir to /tmp only for test purpose,
> but I'm wondering what is a good value for concatdir.
> Maybe /var/lib/puppet/concat? I guess I ha
It's worth mentioning that find -exec this way forks a separate copy of find
for each file. You'll notice how much slower this is on a really large set of
files (possibly larger than yours). If you have a recursion-capable chown it's
quicker to use chown -R.
On Wed, Nov 02, 2011 at 01:30:04AM -
On Wed, 02 Nov 2011 11:22:05 - (GMT)
R.I.Pienaar R.I.Pienaar wrote:
> you're missing the concat{"/etc/sudoers": }
>
> # set up a file for being managed by snippets
> concat{"somefile": }
>
> # add a snippet to it:
> concat::fragment{"foo":.}
>
> needs both
solved.
Thanks !
Arnau
--
Hi again,
I'm always deleting exported resources for hosts that are no longer in use,
also changed what you suggested.
It seems like this problem is still happening once in a while but much less
than it used to so maybe things are starting to work out here.
Thanks a lot for help.
On Mon, Oct 31,
On Nov 1, 3:27 pm, weloki wrote:
> I'm running Ubuntu 10.04 LTS and I just installed Puppet and
> puppetmasterd (both 0.25.4) along with the puppet-dashboard v1.2.0 and
> Foreman 0.3. Puppet and the dashboard were working fine with just the
> master server and a separate client until I installed
On Nov 1, 3:30 am, Daenney wrote:
> Hi guys,
>
> For a project I'm working on for my studies we need to create a demo setup
> of a small enterprise environment. The linux-part of this is now managed by
> puppet. However, I'm running into something I can't exactly figure to how
> to fix. I've rea
On Nov 2, 9:19 am, jcbollinger wrote:
> 1) You do not need flow control, which is good because Puppet does not
> offer it. [...]
Puppet does offer various conditionals, however, that might look like
flow control to you. I supposed you knew the basics of Puppet DSL
because you said you already
Hello,
Le 31/10/11 à 16:09, jcbollinger téléscripta :
> On Oct 28, 10:07 am, Baptiste Grenier
> wrote:
>
> > I am trying to define the modules' run order like this:
>
> You are running up against a common source of confusion: the
> difference between order of manifest evaluation (on the master)
On Nov 1, 6:50 pm, treydock wrote:
> On Oct 31, 3:09 pm, Dan Bode wrote:
>
>
>
>
>
>
>
>
>
> > On Mon, Oct 31, 2011 at 12:44 PM, treydock wrote:
>
> > > On Oct 31, 1:56 pm, treydock wrote:
> > > > On Oct 31, 1:05 pm, Dan Bode wrote:
>
> > > > > On Mon, Oct 31, 2011 at 10:55 AM, treydock wro
I'm a new Puppet user, and I'm trying to get the hang of importing
modules. Right now however, I seem to be having problems auto-loading
the classes in my modules.
Here's my command and error:
vagrant@lucid32:~$ cd /tmp/vagrant-puppet/manifests/
vagrant@lucid32:/tmp/vagrant-puppet/manifes
How could it be possible to choose an environment for deploy via
Puppetrun ? It's easy by ssh (ssh user@hostname sudo puppetd -t --
environment="env"), i'am running with puppet 2.6.4 on Ubuntu
8.04/10.04.
Cheers
--
You received this message because you are subscribed to the Google Groups
"Puppe
Hi,
comments are in line,
On Oct 24, 10:56 am, Stoyan Nikolov
wrote:
> Hello!
>
> I'm trying to install puppet dashboard according to the instructions
> in the documentation
> :http://docs.puppetlabs.com/dashboard/manual/1.2/bootstrapping.html
>
check at /usr/shared/puppet-dashboard
> I am in
Hello List,
I´ve update to 2.7.6 (server + clients, from 2.7.1) after reading the
last CVE, now I´ve got a problem with copying a file
to different releases/architectures using a single statement like
this:
file { "/path/to/file/abc.file": source => "puppet:///path/to/file/xx-
$fact1-$fact2.file"
Please find the in line comments
On Oct 24, 10:56 am, Stoyan Nikolov
wrote:
> Hello!
>
> I'm trying to install puppet dashboard according to the instructions
> in the documentation
> :http://docs.puppetlabs.com/dashboard/manual/1.2/bootstrapping.html
>
> I am installing it from the .deb package,
- Original Message -
> Hello List,
>
> I´ve update to 2.7.6 (server + clients, from 2.7.1) after reading the
> last CVE, now I´ve got a problem with copying a file
> to different releases/architectures using a single statement like
> this:
>
> file { "/path/to/file/abc.file": source =>
Update: It was indeed a permissions issue with regard to the external node
classifier. I simply moved the puppet-dashboard directory out of /root and
put it in /opt and everything works fine now. The thing I can't figure out
is that it was working fine in the /root dir until I installed and
configu
On Wed, Nov 2, 2011 at 9:20 AM, R.I.Pienaar wrote:
>
>
> - Original Message -
> > Hello List,
> >
> > I´ve update to 2.7.6 (server + clients, from 2.7.1) after reading the
> > last CVE, now I´ve got a problem with copying a file
> > to different releases/architectures using a single state
I'm running in circles with this issue... I accidentally did a 'puppetca
--clean --all' and lost all certificates. I was able to get the puppetmaster
running and re-created certificates for the client system, but I get the
following error:
warning: peer certificate won't be verified in this SS
When I did this in my test environment I removed the entire contents
of the ssldir from the client to make sure that both the client &
server cert were pulled down anew.
On Wed, Nov 2, 2011 at 10:25 AM, TFML wrote:
> I'm running in circles with this issue... I accidentally did a 'puppetca
> --cl
I've done that... I've checked the ntpd services and they're sync in time...
Here is what I've done,
On master:
rm -rf ssl
/etc/rc.d/init.d/puppetmaster start
Starting puppetmaster: [ OK ]
ls ssl
ca certificate_requests certs crl.pem private private_ke
I'm curious... the server FQDN is puppetmaster.lagged.com but I have the server
as puppet.lagged.com, can that be the cause of the problem? If so how would I
create the certificate to be valid for puppet.lagged.com and not be
puppetmaster.lagged.com
On Nov 2, 2011, at 2:01 PM, Aaron Grewell wro
Hello all,
Have noticed puppet agent continue to write agent runtime output to /
var/log/messages, although $vardir, logdir default to /var/lib/puppet/
log, agent run logs keep getting writtent to system messages file. I
recall this question has been asked before but did not see a
resolution.
Is
What version of Puppet are you using? The old method of doing this
had a serious security problem, so the newer releases have a different
config method for assigning the acceptable aliases for a cert.
On Wed, Nov 2, 2011 at 11:26 AM, TFML wrote:
> I'm curious... the server FQDN is puppetmaster.l
You are probably hitting this issue:
https://projects.puppetlabs.com/issues/8433
The correct way to do this is to use the Puppet autoloader. To do
this.
Replace your init.pp with your postfix.pp file.
/tmp/vagrant-puppet/
|
|__manifests/
| |
| |__lucid32.pp
|
|__
On Wed, Nov 02, 2011 at 11:45:11AM -0700, Kanishka Hettiarachchi wrote:
> Hello all,
>
> Have noticed puppet agent continue to write agent runtime output to /
> var/log/messages, although $vardir, logdir default to /var/lib/puppet/
> log, agent run logs keep getting writtent to system messages fil
as soon as I installed vmware player and spun up a VM instance on my
development system, I could no longer connect to puppet...
cwhite@development:~/tti_framework$ sudo puppet agent --server MY_PUPPETMASTER
--verbose --test --debug
debug: Failed to load library 'selinux' for feature 'selinux'
de
I was able to resolve my own issue. It ended up being the SSL certificate, I
had to recreate one manually on the master server. Thanks!
On Nov 2, 2011, at 2:50 PM, Aaron Grewell wrote:
> What version of Puppet are you using? The old method of doing this
> had a serious security problem, so th
On Wed, Nov 2, 2011 at 12:13 PM, Craig White wrote:
>
> err: Could not retrieve catalog from remote server: Error 400 on SERVER:
> No support for http method POST
> warning: Not using cache on failed catalog
>
You must be running a newer version agent than your master is.
--
You received this
On Nov 2, 2011, at 12:50 PM, Nigel Kersten wrote:
>
>
> On Wed, Nov 2, 2011 at 12:13 PM, Craig White wrote:
>
> err: Could not retrieve catalog from remote server: Error 400 on SERVER: No
> support for http method POST
> warning: Not using cache on failed catalog
>
> You must be running a n
On Nov 2, 12:19 pm, Jeff wrote:
> Update: It was indeed a permissions issue with regard to the external node
> classifier. I simply moved the puppet-dashboard directory out of /root and
> put it in /opt and everything works fine now.
Great!
> The thing I can't figure out
> is that it was wor
I've been using passenger for about a month and it has worked fine -- however,
I noticed that catalog compilation times were increasing significantly. I
couldn't find any errors in the httpd log, or anything wrong with the setup.
Last night I tried out the settings recommended by Larry Ludwig
Ok, what am I doing wrong here? I'm including
splunkforwarder::app_server and it's all working except that it
appears that splunkforwarder::common isn't including
splunkforwarder::enabled...
class splunkforwarder::enabled {
service {
'splunkforwarder':
ensure => running
On Wed, Nov 2, 2011 at 1:01 PM, jcbollinger wrote:
>
>
> On Nov 2, 12:19 pm, Jeff wrote:
> > Update: It was indeed a permissions issue with regard to the external
> node
> > classifier. I simply moved the puppet-dashboard directory out of /root
> and
> > put it in /opt and everything works fine n
On Wed, Nov 2, 2011 at 3:43 AM, Peter Meier wrote:
>> Thanks Chris, that's helpful. I am wondering if I should be mixing
>> Ruby DSL manifests with the Puppet DSL manifests. Is there any
>> recommended practice for keeping both styles together?
>
> Afaik you can mix both DSL. If one file in a modu
39 matches
Mail list logo
