Re: [mod-security-users] piped log program '/sbin/httpd-guardian.pl' failed unexpectedly

[Robert I. <li...@fl...>]

Update:

in comparing all the parameter modifications against the original
script, I found that the "my" before $PROTECT_EXEC had gotten erased
when uncommenting, and Perl didn't like the variable becoming global
...

Excuse the noise!


On Sun, Aug 24, 2008 at 3:57 PM, R.A. Imhoff <li...@fl...> wrote:
> Hello
>
> I've been trying to install httpd-guardian 1.6 on a Debian 4 LAMP with
> Apache2 and the current ModSecurity, but as soon as I activate it by adding
> :
>
>      SecGuardianLog |/sbin/httpd-guardian.pl
>
> to the Apache conf, the Apache error log fills with a long list of
>     piped log program '/sbin/httpd-guardian.pl' failed unexpectedly
>
> Would anyone be able to give me a hint on how to track down the reason?
> I tried to set $debug to 1 in httpd-guardian.pl, but that doesn't seem to
> produce any output.
> httpd-guardian.pl sits in
> /sbin/httpd-guardian.pl
>
> with owner  and group = www-data (which is the group that Apache runs in)
> and the group and owner having execution rights ...
> blacklist.pl and blacklist-webclient work ok, because they get called from
> certain mod-security rules to block ips via iptables
>
> Many thanks!
> Robert Imhoff
>