why error_log was written many times for same item?

2007-08-07 Thread Jen mlists
Hello,

In my mp1 script I wrote some info to apache's error_log:

} elsif ($ip_int != $ip_int2) {
$r->log_error("[$ip FORBIDDEN] Request IP was not matched");
return FORBIDDEN;


But I saw it wrote many times for same error item,like:

[Tue Aug  7 16:24:08 2007] [error] [219.129.83.13 FORBIDDEN] Request
IP was not matched
[Tue Aug  7 16:24:08 2007] [error] [219.129.83.13 FORBIDDEN] Request
IP was not matched
[Tue Aug  7 16:24:08 2007] [error] [219.129.83.13 FORBIDDEN] Request
IP was not matched
[Tue Aug  7 16:24:08 2007] [error] [219.129.83.13 FORBIDDEN] Request
IP was not matched
[Tue Aug  7 16:24:08 2007] [error] [219.129.83.13 FORBIDDEN] Request
IP was not matched
[Tue Aug  7 16:24:08 2007] [error] [219.129.83.13 FORBIDDEN] Request
IP was not matched
[Tue Aug  7 16:24:08 2007] [error] [219.129.83.13 FORBIDDEN] Request
IP was not matched
[Tue Aug  7 16:24:08 2007] [error] [219.129.83.13 FORBIDDEN] Request
IP was not matched

Why this happen?Thank you.


Re: why error_log was written many times for same item?

2007-08-07 Thread Perrin Harkins
On 8/7/07, Jen mlists <[EMAIL PROTECTED]> wrote:
> In my mp1 script I wrote some info to apache's error_log:
>
> } elsif ($ip_int != $ip_int2) {
> $r->log_error("[$ip FORBIDDEN] Request IP was not matched");
> return FORBIDDEN;
>
>
> But I saw it wrote many times for same error

It must have been called multiple times then.  Calling log_error once
only produces one line in the log.

- Perrin


[mp2] Failed Test on t/api/server_const.t

2007-08-07 Thread Ryan Gies
1. Problem Description:

  'make test' failed on t/api/server_const.t

  I am trying to build Apache2/mod_perl2 on a Fedora Core 6 system
  which already has these components installed.  I am under the
  impression that as long as I am installing in to /usr/local/apache2,
  there will be no conflict.  I stopped the existing httpd process and
  then procedded as described in the section "Sequence of commands"
  below.  After runing the test alone in verbose mode, I suspect this
  is the failure:

# testing : Apache2::ServerUtil::get_server_version()
# expected: Apache/2.2.4 (Unix)
# received: Apache/2.2.4

  Do I need to remove my Fedora sources?  I have the following
  packages installed:

httpd   2.2.4-2.1.fc6
httpd-devel 2.2.4-2.1.fc6
httpd-manual2.2.4-2.1.fc6
apr 1.2.7-10
apr-devel   1.2.7-10
apr-util-devel  1.2.8-1.fc6
mod_perl2.0.2-6.2.fc6

2. Used Components and their Configuration:

*** mod_perl version 2.03

*** using /home/ryan/src/mod_perl-2.0.3/lib/Apache2/BuildConfig.pm

*** Makefile.PL options:
  MP_APR_LIB => aprext
  MP_AP_PREFIX   => /usr/local/apache2
  MP_COMPAT_1X   => 1
  MP_GENERATE_XS => 1
  MP_LIBNAME => mod_perl
  MP_USE_DSO => 1


*** /usr/local/apache2/bin/httpd -V
Server version: Apache/2.2.4 (Unix)
Server built:   Aug  6 2007 15:41:13
Server's Module Magic Number: 20051115:4
Server loaded:  APR 1.2.7, APR-Util 1.2.8
Compiled using: APR 1.2.7, APR-Util 1.2.8
Architecture:   32-bit
Server MPM: Prefork
  threaded: no
forked: yes (variable process count)
Server compiled with
 -D APACHE_MPM_DIR="server/mpm/prefork"
 -D APR_HAS_SENDFILE
 -D APR_HAS_MMAP
 -D APR_HAVE_IPV6 (IPv4-mapped addresses enabled)
 -D APR_USE_SYSVSEM_SERIALIZE
 -D APR_USE_PTHREAD_SERIALIZE
 -D SINGLE_LISTEN_UNSERIALIZED_ACCEPT
 -D APR_HAS_OTHER_CHILD
 -D AP_HAVE_RELIABLE_PIPED_LOGS
 -D DYNAMIC_MODULE_LIMIT=128
 -D HTTPD_ROOT="/usr/local/apache2"
 -D SUEXEC_BIN="/usr/local/apache2/bin/suexec"
 -D DEFAULT_PIDLOG="logs/httpd.pid"
 -D DEFAULT_SCOREBOARD="logs/apache_runtime_status"
 -D DEFAULT_LOCKFILE="logs/accept.lock"
 -D DEFAULT_ERRORLOG="logs/error_log"
 -D AP_TYPES_CONFIG_FILE="conf/mime.types"
 -D SERVER_CONFIG_FILE="conf/httpd.conf"

*** /usr/bin/ldd /usr/local/apache2/bin/httpd
linux-gate.so.1 =>  (0x00946000)
libm.so.6 => /lib/libm.so.6 (0x00ada000)
libaprutil-1.so.0 => /usr/lib/libaprutil-1.so.0 (0x002fb000)
libcrypt.so.1 => /lib/libcrypt.so.1 (0x0045c000)
libldap-2.3.so.0 => /usr/lib/libldap-2.3.so.0 (0x06077000)
liblber-2.3.so.0 => /usr/lib/liblber-2.3.so.0 (0x05e2f000)
libdb-4.3.so => /lib/libdb-4.3.so (0x05f63000)
libexpat.so.0 => /lib/libexpat.so.0 (0x00c5a000)
libapr-1.so.0 => /usr/lib/libapr-1.so.0 (0x0066)
libpthread.so.0 => /lib/libpthread.so.0 (0x004f4000)
libdl.so.2 => /lib/libdl.so.2 (0x00b03000)
libc.so.6 => /lib/libc.so.6 (0x00998000)
/lib/ld-linux.so.2 (0x0097b000)
libuuid.so.1 => /lib/libuuid.so.1 (0x0011)
libpq.so.4 => /usr/lib/libpq.so.4 (0x003e8000)
libsqlite3.so.0 => /usr/lib/libsqlite3.so.0 (0x00c7d000)
libresolv.so.2 => /lib/libresolv.so.2 (0x00856000)
libsasl2.so.2 => /usr/lib/libsasl2.so.2 (0x0605c000)
libssl.so.6 => /lib/libssl.so.6 (0x05b2b000)
libcrypto.so.6 => /lib/libcrypto.so.6 (0x0596d000)
libkrb5.so.3 => /usr/lib/libkrb5.so.3 (0x05aa1000)
libnsl.so.1 => /lib/libnsl.so.1 (0x0083d000)
libgssapi_krb5.so.2 => /usr/lib/libgssapi_krb5.so.2 (0x00918000)
libcom_err.so.2 => /lib/libcom_err.so.2 (0x001e5000)
libk5crypto.so.3 => /usr/lib/libk5crypto.so.3 (0x00114000)
libz.so.1 => /usr/lib/libz.so.1 (0x00b09000)
libkrb5support.so.0 => /usr/lib/libkrb5support.so.0 (0x0096d000)


*** (apr|apu)-config linking info

 -laprutil-1 -lldap -llber -ldb-4.3 -lexpat 
 -lapr-1  -lpthread -ldl 



*** /usr/local/bin/perl -V
Summary of my perl5 (revision 5 version 8 subversion 8) configuration:
  Platform:
osname=linux, osvers=2.6.20-1.2962.fc6, archname=i686-linux
uname='linux devbox.lsnllc 2.6.20-1.2962.fc6 #1 smp tue jun 19
19:27:14 edt 2007 i686 i686 i386 gnulinux '
config_args='-des'
hint=recommended, useposix=true, d_sigaction=define
usethreads=undef use5005threads=undef useithreads=undef
usemultiplicity=undef
useperlio=define d_sfio=undef uselargefiles=define usesocks=undef
use64bitint=undef use64bitall=undef uselongdouble=undef
usemymalloc=n, bincompat5005=undef
  Compiler:
cc='cc', ccflags ='-fno-strict-aliasing -pipe
-Wdeclaration-after-statement -I/usr/local/include -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64 -I/usr/include/gdbm',
optimize='-O2',
cppflags='-fno-strict-aliasing -pipe -Wdeclaration-after-statement
-I/usr/local/include -I/usr/include/gdbm'
ccversion='', gccversion='4.1.2 20070626 (Red Hat 4.1.2-1

Re: [mp2] Failed Test on t/api/server_const.t

2007-08-07 Thread Fred Moyer

Ryan Gies wrote:

1. Problem Description:

  'make test' failed on t/api/server_const.t

  I am trying to build Apache2/mod_perl2 on a Fedora Core 6 system
  which already has these components installed.  I am under the
  impression that as long as I am installing in to /usr/local/apache2,
  there will be no conflict.  I stopped the existing httpd process and
  then procedded as described in the section "Sequence of commands"
  below.  After runing the test alone in verbose mode, I suspect this
  is the failure:

# testing : Apache2::ServerUtil::get_server_version()
# expected: Apache/2.2.4 (Unix)
# received: Apache/2.2.4


This is fixed in 2.04-dev (Changes ref).  This error is probably no big 
deal.


-
Catch up with some httpd API changes

2.2.4:
The full server version information is now included in the error log at
startup as well as server status reports, irrespective of the setting
of the ServerTokens directive. ap_get_server_version() is now
deprecated, and is replaced by ap_get_server_banner() and
ap_get_server_description(). [Jeff Trawick]
-


  Do I need to remove my Fedora sources?  I have the following
  packages installed:


It may be advisable to run only one version of mod_perl on your server 
unless you know what you are doing.  Probably harmless to run both but 
if you end up loading the 2.0.2 version modules you may see some 
inconsistent behavior.




httpd   2.2.4-2.1.fc6
httpd-devel 2.2.4-2.1.fc6
httpd-manual2.2.4-2.1.fc6
apr 1.2.7-10
apr-devel   1.2.7-10
apr-util-devel  1.2.8-1.fc6
mod_perl2.0.2-6.2.fc6




Re: [RELEASE CANDIDATE] libapreq2 2.09-RC2

2007-08-07 Thread Jonathan Vanasco



Are we going to have 2.09 release? It's been quite some time since  
RC2
actually, i'd like to see an RC3-- there was an issue I kept  
complaining about  that Joe was going to solve thanks to some testing  
by [EMAIL PROTECTED] -- reference the posting on 2007.05.25


Supposedly, this is going to lighten up after August when my  
startup goes lives (Aug 10).

congrats!

what are you doing there, if you don't mind me asking... i noticed  
that they were hiring ruby people a while back.  i feared we lost you.