Re: [Puppet Users] Strange behavior from puppetforge firewall module

2014-02-14 Thread Chris W
Hi, We're not using passenger. It's working, but not quite what you would call stable, still see this in the logs sometimes - Feb 11 11:22:26 xxx01 puppet-agent[2135]: (/Firewall[030 ALL - ACCEPT all to localhost]/ensure) created Feb 11 11:22:26 xxx01 puppet-agent[2135]: (/Firewall[01

Re: [Puppet Users] Strange behavior from puppetforge firewall module

2014-02-12 Thread Felix Frank
Hi, the manifest layout sounds sane enough. Is this a passenger setup? On 02/12/2014 03:56 PM, Chris W wrote: > Puppet master is 3.0.2 > Puppet agent is 3.0.2I ended up having to do an include of the > /service/::firewall from the node manifest So is this working for you now? If not, I seem to

Re: [Puppet Users] Strange behavior from puppetforge firewall module

2014-02-12 Thread Chris W
Hi, Puppet master is 3.0.2 Puppet agent is 3.0.2 OS is RHEL6 Node manifests are flat files under a GIT repo. Overarching firewall rules are applied by an ssh module from manifests/init.pp to allow ssh access from management servers, this works all the time. Service specific firewall rules are lai

Re: [Puppet Users] Strange behavior from puppetforge firewall module

2014-02-06 Thread Felix Frank
Hi, this hasn't been solved yet, has it? What version of puppet is this (master+agent), how is the master laid out (passenger?) and how are your manifests structured? Are you relying on import somewhere e.g.? Thanks, Felix On 01/16/2014 04:40 PM, Chris W wrote: > If I do iptables -F on the box,