thr3ads.net - Puppet users - [Puppet Users] shorewall module for puppet [Sep 2008]

If this information is useful, please help other people find it:
Share via:

Graeme Gillies

2008-Sep-30 06:48 UTC

[Puppet Users] shorewall module for puppet

Hi,

I am currently trying to roll out puppet across our company as a means
of managing the configuration for all our systems. I am really keen to
get it into production use, but I have hit a bit of a brick wall with
a particular problem. We use shorewall to manage all system level
firewalls and I have been trying to use the shorewall module from
https://git.puppet.immerda.ch/?p=module-shorewall and it keeps giving
me errors similar to

warning: Configuration could not be instantiated: Could not find
dependent Exec[concat_/var/lib/puppet/modules/shorewall/interfaces.d]
for File[/var/lib/puppet/modules/shorewall/interfaces.d/100-eth0] at /
var/lib/puppet/modules/shorewall/manifests/init.pp:66

Which is incredibly frustrating. I read the thread that was on this
list a few months ago in relation to this problem but it didn''t have
any real solution posted.

I have been trying to put a whole bunch of debug messages in the
shorewall module (to find out what is going on) but even using the
command

puppetmasterd --verbose --debug --no-daemonize --trace

None of these messages seem to get displayed. This issue unfortunately
is a bit of a showstopper so I am keen to get it resolved. I have been
looking at it for the past few days but from what I can tell, both the
shorewall module and the common module it users seem to look fine.

Is there some way of being able to put even more debugging output on
the puppetd or puppetmasterd side?

Thanks in advance,

Graeme

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Peter Meier

2008-Sep-30 13:36 UTC

head link

[Puppet Users] Re: shorewall module for puppet

Hi
> I am currently trying to roll out puppet across our company as a means
> of managing the configuration for all our systems. I am really keen to
> get it into production use, but I have hit a bit of a brick wall with
> a particular problem. We use shorewall to manage all system level
> firewalls and I have been trying to use the shorewall module from
> https://git.puppet.immerda.ch/?p=module-shorewall and it keeps giving
> me errors similar to
this module is originally based on DavidS'' Module:
http://git.black.co.at/?p=module-shorewall and as I''m one of the
authors
of the version in of your repo I try to answer.
(As I see currently the repo box isn''t avaiable, an alternative source
for the module would be here:
http://github.com/duritong/puppet-shorewall/tree/master )

anyway to your problem:
> warning: Configuration could not be instantiated: Could not find
> dependent Exec[concat_/var/lib/puppet/modules/shorewall/interfaces.d]
> for File[/var/lib/puppet/modules/shorewall/interfaces.d/100-eth0] at /
> var/lib/puppet/modules/shorewall/manifests/init.pp:66
hmm this sounds like there is a problem in the basic setup of the
module. you need to use the common module
(http://github.com/duritong/puppet-common/tree/master or
http://git.black.co.at/?p=module-common) for this module. are u using
that one? Because this exec should be created through the concatenated
file definition.
the alias is created in:
http://github.com/duritong/puppet-common/tree/master/manifests/defines/concatenated_file.pp
on line 68. so it sounds like it''s not coming to this point.

btw: are you importing the common module in something like modules.pp in
your manifests folder, like it is described in the common readme.
> Which is incredibly frustrating. I read the thread that was on this
> list a few months ago in relation to this problem but it didn''t
have
> any real solution posted.
i''m using it now in 2 locations without any problems. however maybe
there is something burried somewhere. so I would be as well happy to
find out the problem.
> I have been trying to put a whole bunch of debug messages in the
> shorewall module (to find out what is going on) but even using the
> command
>
> puppetmasterd --verbose --debug --no-daemonize --trace
> 
> None of these messages seem to get displayed. This issue unfortunately
> is a bit of a showstopper so I am keen to get it resolved. I have been
> looking at it for the past few days but from what I can tell, both the
> shorewall module and the common module it users seem to look fine.
> 
> Is there some way of being able to put even more debugging output on
> the puppetd or puppetmasterd side?
i normally use notices so I see them in the puppetmasterd, but you
don''t
need to run it in debug or trace mode.

greets pete

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Graeme Gillies

2008-Sep-30 22:47 UTC

head link

[Puppet Users] Re: shorewall module for puppet

Hi Pete,

Thanks for your help, I really appreciate it.
> this module is originally based on DavidS''
Module:http://git.black.co.at/?p=module-shorewalland as I''m one of the
authors
> of the version in of your repo I try to answer.
> (As I see currently the repo box isn''t avaiable, an alternative
source
> for the module would be
here:http://github.com/duritong/puppet-shorewall/tree/master)
Yep I originally tried using the source for both the common module and
the shorewall module available at http://git.black.co.at/?p=module-shorewall
and http://git.black.co.at/?p=module-common and they gave me the same
problem. I tried the source from
https://git.puppet.immerda.ch/?p=module-shorewall
simply because it looked like it had been updated more recently and I
thought the problem may have been fixed
> hmm this sounds like there is a problem in the basic setup of the
> module. you need to use the common module
>
(http://github.com/duritong/puppet-common/tree/masterorhttp://git.black.co.at/?p=module-common)
for this module. are u using
> that one? Because this exec should be created through the concatenated
> file definition.
> the alias is created
in:http://github.com/duritong/puppet-common/tree/master/manifests/define...
> on line 68. so it sounds like it''s not coming to this point.
That would make sense, but I am indeed using the common module :(
> btw: are you importing the common module in something like modules.pp in
> your manifests folder, like it is described in the common readme.
Yep. In the file /etc/puppet/manifests/modules.pp I am importing the
common module
> i normally use notices so I see them in the puppetmasterd, but you
don''t
> need to run it in debug or trace mode.
cheers I will give that a try

Just to give some more detail about my environment to aid in
troubleshooting, I am using the following version of puppet RPMS

puppet-server-0.24.5-1.el5
puppet-0.24.5-1.el5

from http://people.redhat.com/dlutter/yum/

Both client and server are CentOS 5.2

The contents of my /etc/puppet/manifests/site.pp is as follows

import "nodes.pp"
import "modules.pp"
import "classes/*.pp"

$puppetserver = "server.example.com"
$server = "server.example.com"

The contents of my /etc/puppet/manifests/nodes.pp is as follows

node "v6default" {

    include v6shorewall
    # include v6ntp::client

}

node "build1.vision6.com.au" inherits v6default {

}

And the contents of my /etc/puppet/manifests/modules.pp is as follows

import "common"
import "shorewall"

Finally the contents of my /etc/puppet/manifests/classes/
v6shorewall.pp is

class v6shorewall {
    ## base interface
    shorewall::interface {
        ''eth0'': zone => ''loc'';
    }
}

The most annoying thing about this error is that there should be no
problem with it seeing the exec_ procedure needed, though I did notice
in the puppetmasterd debug output that it outputs the following

info: Autoloaded module shorewall

But never mentions autoloading the common module. Perhaps this is
related to the problem?

Thanks for all the help,

Graeme

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Graeme Gillies

2008-Sep-30 22:55 UTC

head link

[Puppet Users] Re: shorewall module for puppet

Also Just for completeness sake

On the server, this is the /etc/puppet/puppet.conf

[main]
    # Where Puppet stores dynamic and growing data.
    # The default value is ''/var/puppet''.
    vardir = /var/lib/puppet

    # The Puppet log directory.
    # The default value is ''$vardir/log''.
    logdir = /var/log/puppet

    # Where Puppet PID files are kept.
    # The default value is ''$vardir/run''.
    rundir = /var/run/puppet

    # Where SSL certificates are kept.
    # The default value is ''$confdir/ssl''.
    ssldir = $vardir/ssl

[puppetd]
    # The file in which puppetd stores a list of the classes
    # associated with the retrieved configuratiion.  Can be loaded in
    # the separate ``puppet`` executable using the ``--loadclasses``
    # option.
    # The default value is ''$confdir/classes.txt''.
    classfile = $vardir/classes.txt

    # Where puppetd caches the local configuration.  An
    # extension indicating the cache format is added automatically.
    # The default value is ''$confdir/localconfig''.
    localconfig = $vardir/localconfig

[puppetmasterd]
    # Where puppet looks for its modules
    modulepath = /var/lib/puppet/modules

And on the client side this is their /etc/puppet/puppet.conf

[main]
    # Where Puppet stores dynamic and growing data.
    # The default value is ''/var/puppet''.
    vardir = /var/lib/puppet

    # The Puppet log directory.
    # The default value is ''$vardir/log''.
    logdir = /var/log/puppet

    # Where Puppet PID files are kept.
    # The default value is ''$vardir/run''.
    rundir = /var/run/puppet

    # Where SSL certificates are kept.
    # The default value is ''$confdir/ssl''.
    ssldir = $vardir/ssl

    ignorecache = true
    #factsync = true
    #pluginsync = true

[puppetd]
    # The file in which puppetd stores a list of the classes
    # associated with the retrieved configuratiion.  Can be loaded in
    # the separate ``puppet`` executable using the ``--loadclasses``
    # option.
    # The default value is ''$confdir/classes.txt''.
    classfile = $vardir/classes.txt

    # Where puppetd caches the local configuration.  An
    # extension indicating the cache format is added automatically.
    # The default value is ''$confdir/localconfig''.
    localconfig = $vardir/localconfig

Cheers,

Graeme

On Oct 1, 8:47 am, Graeme Gillies <graeme.r.gill...@gmail.com>
wrote:> Hi Pete,
>
> Thanks for your help, I really appreciate it.
>
> > this module is originally based on DavidS''
Module:http://git.black.co.at/?p=module-shorewallandas I''m one of the
authors
> > of the version in of your repo I try to answer.
> > (As I see currently the repo box isn''t avaiable, an
alternative source
> > for the module would be
here:http://github.com/duritong/puppet-shorewall/tree/master)
>
> Yep I originally tried using the source for both the common module and
> the shorewall module available athttp://git.black.co.at/?p=module-shorewall
> andhttp://git.black.co.at/?p=module-commonand they gave me the same
> problem. I tried the source
fromhttps://git.puppet.immerda.ch/?p=module-shorewall
> simply because it looked like it had been updated more recently and I
> thought the problem may have been fixed
>
> > hmm this sounds like there is a problem in the basic setup of the
> > module. you need to use the common module
> >
(http://github.com/duritong/puppet-common/tree/masterorhttp://git.blac...) for
this module. are u using
> > that one? Because this exec should be created through the concatenated
> > file definition.
> > the alias is created
in:http://github.com/duritong/puppet-common/tree/master/manifests/define...
> > on line 68. so it sounds like it''s not coming to this point.
>
> That would make sense, but I am indeed using the common module :(
>
> > btw: are you importing the common module in something like modules.pp
in
> > your manifests folder, like it is described in the common readme.
>
> Yep. In the file /etc/puppet/manifests/modules.pp I am importing the
> common module
>
> > i normally use notices so I see them in the puppetmasterd, but you
don''t
> > need to run it in debug or trace mode.
>
> cheers I will give that a try
>
> Just to give some more detail about my environment to aid in
> troubleshooting, I am using the following version of puppet RPMS
>
> puppet-server-0.24.5-1.el5
> puppet-0.24.5-1.el5
>
> fromhttp://people.redhat.com/dlutter/yum/
>
> Both client and server are CentOS 5.2
>
> The contents of my /etc/puppet/manifests/site.pp is as follows
>
> import "nodes.pp"
> import "modules.pp"
> import "classes/*.pp"
>
> $puppetserver = "server.example.com"
> $server = "server.example.com"
>
> The contents of my /etc/puppet/manifests/nodes.pp is as follows
>
> node "v6default" {
>
>     include v6shorewall
>     # include v6ntp::client
>
> }
>
> node "build1.vision6.com.au" inherits v6default {
>
> }
>
> And the contents of my /etc/puppet/manifests/modules.pp is as follows
>
> import "common"
> import "shorewall"
>
> Finally the contents of my /etc/puppet/manifests/classes/
> v6shorewall.pp is
>
> class v6shorewall {
>     ## base interface
>     shorewall::interface {
>         ''eth0'': zone => ''loc'';
>     }
>
> }
>
> The most annoying thing about this error is that there should be no
> problem with it seeing the exec_ procedure needed, though I did notice
> in the puppetmasterd debug output that it outputs the following
>
> info: Autoloaded module shorewall
>
> But never mentions autoloading the common module. Perhaps this is
> related to the problem?
>
> Thanks for all the help,
>
> Graeme--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

sc0ttbeardsley

2009-Jan-31 01:01 UTC

head link

[Puppet Users] Re: shorewall module for puppet

Did this ever get resolved? I''m having the same problem on Ubuntu
(Hardy). I wonder if it is because Ubuntu puts modules in /etc/puppet/
modules instead of /var/lib/puppet/modules? Or perhaps the find in
concatenated_file.pp isn''t finding what is expected:

        # use >| to force clobbering the target file
        exec { "/usr/bin/find ${dir} -maxdepth 1 -type f ! -name
''*puppettmp'' -print0 | sort -z | xargs -0 cat
${additional_cmd} >| $
{name}":
                refreshonly => true,
                subscribe => File[$dir],
                before => File[$name],
                alias => [ "concat_${name}",
"concat_${dir}"] ,
        }


Scott

On Sep 30 2008, 2:55 pm, Graeme Gillies <graeme.r.gill...@gmail.com>
wrote:> Also Just for completeness sake
>
> On the server, this is the /etc/puppet/puppet.conf
>
> [main]
>     # Where Puppet stores dynamic and growing data.
>     # The default value is ''/var/puppet''.
>     vardir = /var/lib/puppet
>
>     # The Puppet log directory.
>     # The default value is ''$vardir/log''.
>     logdir = /var/log/puppet
>
>     # Where Puppet PID files are kept.
>     # The default value is ''$vardir/run''.
>     rundir = /var/run/puppet
>
>     # Where SSL certificates are kept.
>     # The default value is ''$confdir/ssl''.
>     ssldir = $vardir/ssl
>
> [puppetd]
>     # The file in which puppetd stores a list of the classes
>     # associated with the retrieved configuratiion.  Can be loaded in
>     # the separate ``puppet`` executable using the ``--loadclasses``
>     # option.
>     # The default value is ''$confdir/classes.txt''.
>     classfile = $vardir/classes.txt
>
>     # Where puppetd caches the local configuration.  An
>     # extension indicating the cache format is added automatically.
>     # The default value is ''$confdir/localconfig''.
>     localconfig = $vardir/localconfig
>
> [puppetmasterd]
>     # Where puppet looks for its modules
>     modulepath = /var/lib/puppet/modules
>
> And on the client side this is their /etc/puppet/puppet.conf
>
> [main]
>     # Where Puppet stores dynamic and growing data.
>     # The default value is ''/var/puppet''.
>     vardir = /var/lib/puppet
>
>     # The Puppet log directory.
>     # The default value is ''$vardir/log''.
>     logdir = /var/log/puppet
>
>     # Where Puppet PID files are kept.
>     # The default value is ''$vardir/run''.
>     rundir = /var/run/puppet
>
>     # Where SSL certificates are kept.
>     # The default value is ''$confdir/ssl''.
>     ssldir = $vardir/ssl
>
>     ignorecache = true
>     #factsync = true
>     #pluginsync = true
>
> [puppetd]
>     # The file in which puppetd stores a list of the classes
>     # associated with the retrieved configuratiion.  Can be loaded in
>     # the separate ``puppet`` executable using the ``--loadclasses``
>     # option.
>     # The default value is ''$confdir/classes.txt''.
>     classfile = $vardir/classes.txt
>
>     # Where puppetd caches the local configuration.  An
>     # extension indicating the cache format is added automatically.
>     # The default value is ''$confdir/localconfig''.
>     localconfig = $vardir/localconfig
>
> Cheers,
>
> Graeme
>
> On Oct 1, 8:47 am, Graeme Gillies <graeme.r.gill...@gmail.com>
wrote:> Hi Pete,
>
> > Thanks for your help, I really appreciate it.
>
> > > this module is originally based on DavidS''
Module:http://git.black.co.at/?p=module-shorewallandasI''m one of the
authors
> > > of the version in of your repo I try to answer.
> > > (As I see currently the repo box isn''t avaiable, an
alternative source
> > > for the module would be
here:http://github.com/duritong/puppet-shorewall/tree/master)
>
> > Yep I originally tried using the source for both the common module and
> > the shorewall module available
athttp://git.black.co.at/?p=module-shorewall
> > andhttp://git.black.co.at/?p=module-commonandthey gave me the same
> > problem. I tried the source
fromhttps://git.puppet.immerda.ch/?p=module-shorewall
> > simply because it looked like it had been updated more recently and I
> > thought the problem may have been fixed
>
> > > hmm this sounds like there is a problem in the basic setup of the
> > > module. you need to use the common module
> > >
(http://github.com/duritong/puppet-common/tree/masterorhttp://git.blac...) for
this module. are u using
> > > that one? Because this exec should be created through the
concatenated
> > > file definition.
> > > the alias is created
in:http://github.com/duritong/puppet-common/tree/master/manifests/define...
> > > on line 68. so it sounds like it''s not coming to this
point.
>
> > That would make sense, but I am indeed using the common module :(
>
> > > btw: are you importing the common module in something like
modules.pp in
> > > your manifests folder, like it is described in the common readme.
>
> > Yep. In the file /etc/puppet/manifests/modules.pp I am importing the
> > common module
>
> > > i normally use notices so I see them in the puppetmasterd, but
you don''t
> > > need to run it in debug or trace mode.
>
> > cheers I will give that a try
>
> > Just to give some more detail about my environment to aid in
> > troubleshooting, I am using the following version of puppet RPMS
>
> > puppet-server-0.24.5-1.el5
> > puppet-0.24.5-1.el5
>
> > fromhttp://people.redhat.com/dlutter/yum/
>
> > Both client and server are CentOS 5.2
>
> > The contents of my /etc/puppet/manifests/site.pp is as follows
>
> > import "nodes.pp"
> > import "modules.pp"
> > import "classes/*.pp"
>
> > $puppetserver = "server.example.com"
> > $server = "server.example.com"
>
> > The contents of my /etc/puppet/manifests/nodes.pp is as follows
>
> > node "v6default" {
>
> >     include v6shorewall
> >     # include v6ntp::client
>
> > }
>
> > node "build1.vision6.com.au" inherits v6default {
>
> > }
>
> > And the contents of my /etc/puppet/manifests/modules.pp is as follows
>
> > import "common"
> > import "shorewall"
>
> > Finally the contents of my /etc/puppet/manifests/classes/
> > v6shorewall.pp is
>
> > class v6shorewall {
> >     ## base interface
> >     shorewall::interface {
> >         ''eth0'': zone => ''loc'';
> >     }
>
> > }
>
> > The most annoying thing about this error is that there should be no
> > problem with it seeing the exec_ procedure needed, though I did notice
> > in the puppetmasterd debug output that it outputs the following
>
> > info: Autoloaded module shorewall
>
> > But never mentions autoloading the common module. Perhaps this is
> > related to the problem?
>
> > Thanks for all the help,
>
> > Graeme
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Puppet users - Sep 2008 - shorewall module for puppet

[Puppet Users] shorewall module for puppet

[Puppet Users] Re: shorewall module for puppet

[Puppet Users] Re: shorewall module for puppet

[Puppet Users] Re: shorewall module for puppet

[Puppet Users] Re: shorewall module for puppet