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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
