|
From: Tom C. <to...@fa...> - 2007-08-16 19:58:07
|
James Beckett wrote: > Tom is substituting > "somethingrandom" instead of revealing his unique key... (?) Yeah, I guess as I had to apply for it, I shouldn't post it. > Tom, are you accessing /httpbl_diagnostics/ or /httpbl_diagnostics ? > I've noticed that the latter just doesn't work (404) on my systems. *Ahhh* Someone needs to update the docs to point that out in large friendly letters :-) Some insight on the not being able to write to the logs error appears now. Looks like the module's error *was* wrong: [ + ] Write to the log directory (/etc/httpd/logs/) But: # ls -lah /etc/httpd|grep log lrwxrwxrwx 1 root root 19 Jul 4 19:38 logs -> ../../var/log/httpd which is where it said it couldn't write to. And now there is # ls -lah /var/log/httpd/httpbl_diagnostics_test.txt -rw-r--r-- 1 apache apache 0 Aug 16 20:50 /var/log/httpd/httpbl_diagnostics_test.txt Hurrah ! Yet... oddness. Should I file a bug report on SourceForge ? > Can you report your APR version and which version of the httpBL > source you're using? So, seems to work on x86_64 FC5 (apr-1.2.2-7.3 and httpd-2.2.2-1.3) with the latest version of the module. Now it's working, what sort of lines/files should I look out for in the Apache logs ? -- Tom C Famous Last Words #38: "I don't believe it." |