works fine. But I can't figure out what would have changed that
still allows me to run it fine but puppet fails.
On Aug 12, 5:10 pm, Tim Mooney wrote:
> In regard to: [Puppet Users] Re: hasstatus not working as expected, Chad...:
>
> > status)
> > /sbin/iptables -L | /
In regard to: [Puppet Users] Re: hasstatus not working as expected, Chad...:
status)
/sbin/iptables -L | /bin/egrep '^DROP+\s+all.*NEW\s?+$' > /dev/
null
I doubt this is the actual problem, but you could more portably and
more correctly write that regex as
'^D
> Is it possible that your initscript depends on a specific environment
> (like a special PATH variable?).
Sorry meant to comment on this as well. The status is actually a
regular expression looking for a line from '/sbin/iptables -L'. Here
is the status section of the script (bash)
**
> So puppet actually uses »/sbin/service build_iptables status« to check
> if your service is running.
Agreed. The service command works as well (and it also checks to make
sure it is chkconfig'ed on)
This has worked for months before recently. I just just checked and I
added the status option
[me@host ~]$ sudo /usr/sbin/puppetd --test --noop
info: Caching catalog for host.fakedomain
info: Applying configuration version '1313165427'
notice: //iptables/Service[build_iptables]/ensure: is stopped, should
be running (noop)
notice: //iptables/Exec[/etc/init.d/build_iptables status]/returns: i
