On Apr 13, 4:16 am, Adam Heinz wrote:
> > context => "/etc/network/interfaces",
>
> Shouldn't this be "/files/etc/network/interfaces"?
Thanks! that was the thing I was missing.
The iface stuff works fine now but I can't figure out how to add a new
auto line
"set auto[. = 'eth1'] eth1",
Hi
I've just started trying to use augeas to manage /etc/network/
interfaces on Ubuntu
I found some stuff in the archive that seems to match what I need but
I can't make anything work.
I have
augeas { "network_interface":
context => "/etc/network/interfaces",
changes => [
Hi
I have just put puppet onto a new Ubuntu install and it ran a couple
of times but now I get
Execution of '/etc/puppet/etckeeper-commit-pre' returned 1:
whenever puppetd runs.
Grepping on etckeeper-commit turns up lots of posts to ubuntu and
debian forums about changes made in February.
Does a
On Mar 9, 12:03 am, Denmat wrote:
> Hi Russell,
>
> On the client, verify that the ssl dir is set to /etc/puppet/ssl (check
> puppet.conf). Remove the ssl dir contents.
>
> On server, do a 'find' on the old/new hostname in the ssl dir. Remove any
> file match.
>
> On the client, run puppet --w
I have an RHE host that is managed by puppet. Some how it got the
wrong host name in the rhn/systemid file which seemed to override
everything else.
I fixed this and rebooted the box and it came back with the correct
host name which it got via dhcp.
I removed the /etc/puppet/ssl directory on the
On Mar 2, 10:53 pm, Daniel Piddock wrote:
> On 02/03/11 04:31, russell.fulton wrote:
>
>
>
> > I am having a fight with a postgressql nodule:
>
> > It defines:
>
> > class postgresql::base {
>
> > package {"postgresql&qu
Firstly thanks to all of you who have chipped in on this thread.
Largely it has confirmed what I already thought. Mike has explained
the problem well we have very similar set ups and requirements.
When we started on the puppet project 6 months ago there were
two of us -- my partner was familiar w
I am having a fight with a postgressql nodule:
It defines:
class postgresql::base {
package {"postgresql":
ensure => present,
notify => undef,
}
...
and later we have a class that inherits the base class:
class postgresql::rhe::v8-4 inherits postgresql::base {
$data_dir = $
> > I think this is even more important when you have a lot of churn.
> > Simply being able to flip between versions of the packages quickly
> > will surely save an awful lot of time.
>
> What he said - really. Three immediate benefits:
>
> - having the build process entirely scripted in the s
Thanks for the responses :) I'll respond to all three here
OS is RedHat Enterprise :( not my first choice.
>
> Have you thought about solutions like checkinstall, which allow you to
> create packages for applications like that easily?
> Seehttp://www.asic-linux.com.mx/~izto/checkinstall/
Hi
I have a number of apps that need to be installed from tarballs --
simple tar -zxf; configure; make install...
with a possible extra parameter to configure (usually prefix).
There are no prepackaged versions of these available as they are very
specialised application (security related).
I ca
Jan 22, 4:36 am, jcbollinger wrote:
> On Jan 20, 5:00 pm, "russell.fulton" wrote:
>
>
>
> Note that
>
> 1) Your braces were unbalanced. I balanced them by inserting a
> closing brace where it looked like one belonged.
Sorry about that I trimmed the manifest...
>
>
Hi
I get this error from this manifest:
err: Could not retrieve catalog from remote server: Error 400 on
SERVER: Could not find resource 'File[/home/snort/resnet/Rules/]File[/
home/snort/resnet/conf/pp]File[/home/snort/resnet/conf/pp.conf]' for
relationship from 'Exec[/home/snort/bin/pulledpork -n
I have some 'service' definitions in a parameterised class:
class snort($name, $master) {
service{
"snort.$master":
start => "sudo -u snort /home/snort/bin/restart-snort
$sensor" ,
..
}
which get invoked from within a define:
define sensor ( $name, $master, $in
little historical note for the record
Solaris cron is old -- system V or BSD 4.2. Most (all ?) Linux
distros and modern *BSDs use Paul Vixie's Cron which has all the
flexibility that we know and love.
I suspect that AIX will be similar to Solaris -- painful.
Russell
--
You received this
>
> That might be a typo in what you've written above but your script
> should be returning zero if everything is all right, not 1. 1 would
> indicate a problem and thus Puppet is trying to restart yourservice.
>
Doh! -- no typo - that's the problem. I even have the docs that say
it should be zer
I now have my service status command that does a kill -0 on all the
pid and return 1 if all the processes are running. I have this class/
service definition:
class snort($master) {
service{
"snort.$master":
start => "sudo -u snort /home/snort/bin/restart-snort
$mast
Hi
I am using puppet to mirror a directory of files, if any of these
change then processes need to be restarted.
class snort {
package {
["snort", "perl-Archive-Tar", "barnyard2", "perl-libwww-perl", "perl-
Crypt-SSLeay"]:
ensure => present;
} # package
user{
what should the service{...: ., status=> , .. }
return ?
0 => not running ??
be a good idea to add this to
http://docs.puppetlabs.com/guides/types/service.html
Russell
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this g
I have a dependency loop reported but I can not see how this can be:
class monitor {
class pulledpork ( $master) {
exec {
"/home/snort/bin/pulledpork -nc conf/$master/pp.conf":
cwd => "/home/snort",
subscribe => [File["/home/snort/conf/$master/pp"], File[
Hi
I need to run a command if any one of a number of files change. I can
handle this with having an exec and a subscribe clause listing the
dependencies but I want the command to be run once per run, i.e. after
all the possible updates have happened.
I note stages can only be used within a class
>
> This can happen when your client's major version is larger than your server's
> major version. Is that possable?
Indeed!
Thanks -- clients on 2.5 server on 2.6...
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, se
I am getting this error on the clients. (I am running with --test).
rerunning the command works as expected.
This does not happen every time. I have no idea what the message
means or more precisely what a PSON is...
Russell
--
You received this message because you are subscribed to the Google
> }
>
> define sensor () {
> $rules = generate("/usr/local/sbin/get-rules-for ${fqdn} ${name}")
> # ...and that emits a single string with the right data.
>
It looks as if one can not pass variables into generators to protect
us from ourselves
"Generators can only contain alphanumerics,
Over the last few weeks I have several times felt the need to test out
some small snippets of puppet code without having to have them in my
live system.
At the moment I am doing all my testing by fiddling with file on the
puppet master and then invoking puppet on one of the clients. There
must be
Firstly thank you Daniel for your response on the scope stuff in
templates -- I had read that doc and missed it.
I am still struggling with this and I suspect that there may well be a
better way of doing what I need so as the subject says I am going back
to basics. In this post I will try and abst
I have a class in a file monitor/manifest/masters/dmzo:
class dmzo {
$rule_categories = [
scan,finger,ftp,telnet,rpc,rservices,ddos,dns,tftp,web-
coldfusion,misc,web-php,
]
}
and probably other variables eventually...
In my monitor/manifest/init.pp:
module monitor {
impor
I have worked my way around this one:
empirical evidence suggest that one can use variable in include but
not import. This makes some sort of sense.
So I now
import "master/*.pp"
include $master
This leads to another problem but I'll post it to a thread of its
own...
Russell
--
You received
Still on my sensor management project ;)
I have a parameterised define (sensor) within a class monitor:
class monitor {
import "masters/*.pp" # class for each sensor master
define sensor( $master, .)
# and I want to include a class whose name is give by $master.
include $ma
Thanks very much John. I had indeed been thinking of import as being
like include.
As it happens I have completely reworked this stuff and now the
monitor module just deals with specifying what packages and users are
pushed out. It also now imports a two defines which deal with all the
config st
Hi
I have a requirement to generate several very similar config files
which are just a couple of tokens different and with different names.
These are barnyard conf files if anyone is interested and differ only
in the interface name which is also part of the file name. I can
include [eth1, eth2]
I am trying to import a hash definition from a separate file but this
fails whereas including the text verbatim in the original manifest
works fine:
class monitor ($master, $interface) {
# import "masters.pp"
$sensor_rule_categories = {
'dmzo' =>
[scan,finger,ftp,telnet,rpc,rservic
32 matches
Mail list logo
