[mp2] modperl test failed

2004-06-10 Thread Alex Oboimov
/usr/lib/perl5/site_perl/5.8.1
/usr/lib/perl5/site_perl
/usr/lib/perl5/vendor_perl/5.8.1/i386-linux-thread-multi
/usr/lib/perl5/vendor_perl/5.8.1
/usr/lib/perl5/vendor_perl/5.8.0
/usr/lib/perl5/vendor_perl
.

*** Packages of interest status:

Apache::Request: -
CGI: 3.00
LWP: 5.69
mod_perl   : -


3. This is the core dump trace: (if you get a core dump):

GNU gdb 5.3-25mdk (Mandrake Linux)
Copyright 2002 Free Software Foundation, Inc.

Core was generated by `/usr/local/apache2/bin/httpd -d
/usr/local/src/mod_perl-1.99_14/t -f /usr/local'.
Program terminated with signal 11, Segmentation fault.
Reading symbols from /usr/local/apache2/lib/libaprutil-0.so.0...done.
Loaded symbols for /usr/local/apache2/lib/libaprutil-0.so.0

Here follows 120 lines of Reading symbols/Loaded symbols without any
errors...

Sorry I haven't included debug options in httpd nor modperl builds...

This report was generated by t/REPORT on Thu Jun 10 11:01:23 2004 GMT.

-8<-- End Bug Report --8<--

Of course if there is no way out I will recompile both things but it
takes almost whole day on my machine :(((

Alex





Best regards,
 Alex Oboimov  mailto:[EMAIL PROTECTED]




-- 
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html



Re[2]: [mp2] modperl test failed

2004-06-11 Thread Alex Oboimov
Hello Stas,

 you wrote:


SB> Should be OK for yourself if you don't use rflush, but it's definitely not OK
SB> otherwise.

I'm not sure which programs may use it, which not...


SB> Show us the *complete* output of:

SB> % t/TEST -verbose api/rflush.t

SB> and the t/logs/error_log as explained here:

Here it is:

 t/TEST -verbose api/rflush.t

/usr/local/apache2/bin/httpd -d /usr/local/src/mod_perl-1.99_14/t -f 
/usr/local/src/mod_perl-1.99_14/t/conf/httpd.conf -D APACHE2 -D PERL_USEITHREADS
using Apache/2.0.49 (prefork MPM)

waiting 120 seconds for server to start: 
...
waiting 120 seconds for server to start: ok (waited 54 secs)
server localhost.localdomain:8529 started
server localhost.localdomain:8530 listening (TestModperl::merge)
server localhost.localdomain:8531 listening (TestModperl::perl_options)
server localhost.localdomain:8532 listening (TestModperl::setupenv)
server localhost.localdomain:8533 listening (TestVhost::config)
server localhost.localdomain:8534 listening (TestProtocol::echo_filter)
server localhost.localdomain:8535 listening (TestProtocol::echo_timeout)
server localhost.localdomain:8536 listening (TestProtocol::echo_block)
server localhost.localdomain:8537 listening (TestPreConnection::note)
server localhost.localdomain:8538 listening (TestHooks::stacked_handlers2)
server localhost.localdomain:8539 listening (TestHooks::startup)
server localhost.localdomain:8540 listening (TestFilter::in_bbs_inject_header)
server localhost.localdomain:8541 listening (TestFilter::in_str_msg)
server localhost.localdomain:8542 listening (TestFilter::both_str_con_add)
server localhost.localdomain:8543 listening (TestFilter::in_bbs_msg)
server localhost.localdomain:8544 listening (TestDirective::perlmodule)
server localhost.localdomain:8545 listening (TestDirective::perlrequire)
server localhost.localdomain:8546 listening (TestPerl::ithreads)
server localhost.localdomain:8547 listening (TestDirective::perlloadmodule4)
server localhost.localdomain:8548 listening (TestDirective::perlloadmodule5)
server localhost.localdomain:8549 listening (TestDirective::perlloadmodule3)
server localhost.localdomain:8550 listening (TestDirective::perlloadmodule6)
t/api/rflush1..1
# Running under perl version 5.008001 for linux
# Current time local: Fri Jun 11 12:43:24 2004
# Current time GMT:   Fri Jun 11 07:43:24 2004
# Using Test.pm version 1.24
# testing : rflush creates bucket brigades
# expected: [][]
# received: []
not ok 1
FAILED test 1
Failed 1/1 tests, 0.00% okay
Failed TestStat Wstat Total Fail  Failed  List of Failed
---
t/api/rflush.t11 100.00%  1
Failed 1/1 test scripts, 0.00% okay. 1/1 subtests failed, 0.00% okay.
...done

### Here was unable to catch ALL warnings, from the screen ###

[warning] result: OK
[warning] the client side drops 'root' permissions and becomes 'nobody'
[Fri Jun 11 12:42:45 2004] [info] 27 Apache:: modules loaded
[Fri Jun 11 12:42:45 2004] [info] 5 APR:: modules loaded
[Fri Jun 11 12:42:45 2004] [info] base server + 17 vhosts ready to run tests
# Failed test 1 in t/api/rflush.t at line 13
[warning] server localhost.localdomain:8529 shutdown
[warning] port 8529 still in use...
[  error] error running tests (please examine t/logs/error_log)
[  error] oh darn, server dumped core
[  error] for stacktrace, run: gdb /usr/local/apache2/bin/httpd -core 
/usr/local/src/mod_perl-1.99_14/t/core.7183

### Now error-log:

[EMAIL PROTECTED] mod_perl-1.99_14]# less t/logs/error_log

END in modperl_extra.pl, pid=7178
Attempt to free unreferenced scalar at /usr/lib/perl5/5.8.1/Test/Harness.pm line 31.
[Fri Jun 11 12:43:22 2004] [notice] Apache/2.0.49 (Unix) mod_perl/1.99_14 Perl/v5.8.1 
configured -- resuming normal operations
[Fri Jun 11 12:43:22 2004] [info] Server built: Jun 10 2004 12:06:44
[Fri Jun 11 12:43:22 2004] [debug] prefork.c(955): AcceptMutex: sysvsem (default: 
sysvsem)
[Fri Jun 11 12:43:43 2004] [info] Child process pid=7182 is exiting
END in modperl_extra.pl, pid=7182
[Fri Jun 11 12:43:43 2004] [info] Child process pid=7185 is exiting
END in modperl_extra.pl, pid=7185
[Fri Jun 11 12:43:43 2004] [info] removed PID file 
/usr/local/src/mod_perl-1.99_14/t/logs/httpd.pid (pid=7180)
[Fri Jun 11 12:43:43 2004] [notice] caught SIGTERM, shutting down
END in modperl_extra.pl, pid=7180
Attempt to free unreferenced scalar at /usr/lib/perl5/5.8.1/Test/Harness.pm line 31.
=

### Now post-mortem :

1. Running (as recommended above):
gdb /usr/local/apache2/bin/httpd -core /usr/local/src/mod_perl-1.99_14/t/core.7183
2. Obtaining:

GNU gdb 5.3-25mdk (Mandrake Linux)
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditio

[mp2] modperl test failed

2004-06-15 Thread Alex Oboimov
Hello Stas,
After configuring with MP_DEBUG=1 I've encountered segfault duringconfiguration itself the diagnostic being exactly the same as duringt/TEST (except for damns :). And after make & t/TEST I've got:
[EMAIL PROTECTED] mod_perl-1.99_14]# t/TEST -verbose api/rflush.t[warning] setting ulimit to allow core filesulimit -c unlimited; /usr/bin/perl5.8.1 /usr/local/src/mod_perl-1.99_14/t/TEST -verbose 'api/rflush.t'[warning] root mode: changing the files ownership to 'nobody' (65534:65534)[warning] testing whether 'nobody' is able to -rwx /usr/local/src/mod_perl-1.99_14/t"/usr/bin/perl5.8.1" -Mlib=/usr/local/src/mod_perl-1.99_14/Apache-Test/lib -MApache::TestRun -e 'eval { Apache::TestRun::run_root_fs_test(65534, 65534, q[/usr/local/src/mod_perl-1.99_14/t]) }';
[warning] result: OK[warning] the client side drops 'root' permissions and becomes 'nobody'/usr/local/apache2/bin/httpd -d /usr/local/src/mod_perl-1.99_14/t -f /usr/local/src/mod_perl-1.99_14/t/conf/httpd.conf -D APACHE2 -D PERL_USEITHREADSusing Apache/2.0.49 (prefork MPM)
waiting 120 seconds for server to start: .[Tue Jun 15 11:53:23 2004] [info] 27 Apache:: modules loaded[Tue Jun 15 11:53:23 2004] [info] 5 APR:: modules loaded[Tue Jun 15 11:53:23 2004] [info] base server + 17 vhosts ready to run testswaiting 120 seconds for server to start: ok (waited 51 secs)server localhost.localdomain:8529 startedserver localhost.localdomain:8530 listening (TestModperl::merge)server localhost.localdomain:8531 listening (TestModperl::perl_options)server localhost.localdomain:8532 listening (TestModperl::setupenv)server localhost.localdomain:8533 listening (TestVhost::config)server localhost.localdomain:8534 listening (TestProtocol::echo_filter)server localhost.localdomain:8535 listening (TestProtocol::echo_timeout)server localhost.localdomain:8536 listening (TestProtocol::echo_block)server localhost.localdomain:8537 listening
 (TestPreConnection::note)server localhost.localdomain:8538 listening (TestHooks::stacked_handlers2)server localhost.localdomain:8539 listening (TestHooks::startup)server localhost.localdomain:8540 listening (TestFilter::in_bbs_inject_header)
 

 
# Running under perl version 5.008001 for linux# Current time local: Tue Jun 15 11:54:01 2004# Current time GMT:   Tue Jun 15 06:54:01 2004# Using Test.pm version 1.24# testing : rflush creates bucket brigades# expected: [][]# received: []not ok 1# Failed test 1 in t/api/rflush.t at line 13FAILED test 1    Failed 1/1 tests, 0.00% okay    Failed Test    Stat Wstat Total Fail  Failed  List of Failed    ---    t/api/rflush.t    1    1 100.00%  1    Failed 1/1 test scripts,
 0.00% okay. 1/1 subtests failed, 0.00% okay.    [warning] server localhost.localdomain:8529 shutdown    [warning] port 8529 still in use...    ...done    [  error] error running tests (please examine t/logs/error_log)    [   info] an old core file has been found: /usr/local/src/mod_perl-1.99_14/t/core.29457    [  error] oh dangnabit, server dumped core    [  error] for stacktrace, run: gdb /usr/local/apache2/bin/httpd -core /usr/local/src/mod_perl-1.99_14/t/core.29626 After doing so:(gdb) bt#0  0x4032fa74 in Perl_pp_leavesub ()   from /usr/lib/perl5/5.8.1/i386-linux-thread-multi/CORE/libperl.so  
 #1  0x082ea5e0 in ?? ()   #2  0x0918e994 in ?? ()
  
 
As I dare guess the fault is not on the modperl side but on the   perl's one. So I rather dwell on reinstallation of perl, but my   early investigation show that it is uneasy task bearing in mind   complex dependencies of mdk packages. One advice is to run two   perls - one for system needs and another for apache-perl-modperl   tier. Is this advisable?
 
>>sure, take your time. but please follow up to the list.
 
Sorry Stas, I press automatically the Respond button and realized itwas your private account afterwards... will never repeat this.
 
Best regards, Alex Oboimov
		 ALL-NEW 
Yahoo! Messenger - so many 
all-new ways to express yourself 

[mp2] modperl test failed

2004-06-15 Thread Alex Oboimov
Many thanks, Stas!

Unfortunately (?) I hasted a bit and have upgraded my
perl package to 5.8.4-10.mdk before your post arrived.

Now modperl configured and build ok and all tests
passed including rflush.t. Though now I have problem
building my DBI & DBD::InterBase modules :(((

Now I hesitate - should I DEGRADE my system to find
out what was wrong with my perl-5.8.1-1.RC4.mdk?

Regards,
  Alex





___ALL-NEW Yahoo! Messenger - 
so many all-new ways to express yourself http://uk.messenger.yahoo.com

-- 
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html



multipart/form failure

2004-08-31 Thread Alex Oboimov
Hi folks,

I'm fresh to Apache2/mod-perl2, just migrated from
mp1.

My system: Apache 2.049/Perl 5.8.4/mod_perl
1.99_14/DBI 1.42/DBD::InterBase/FireBird 1.5 on
linux Mandrake 9.2 engine.

My problem: my old programs were fine in the old
system. Now after major editing of the programs
they work except for files uploading that
does not work properly.

After parsing my multipart/form data I get $buffer
with file's content, then I twice 'chop' it (for
extra '\r\n' symbols) & put it in my SQL statement.
The program executes fine but after downloading
the file of 'application/msword' type is unusable
while all other types (zip, rar, pdf, jpg et
al) download just OK. The file becomes two bytes
longer and is not recognized as .doc type.

What the reason might be? I suspect that some
settings in httpd.conf might preclude some sort of
conversion for this sort of files. Any suggestions?



-- 
Regards,
 Alex  mailto:[EMAIL PROTECTED]



-- 
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html



Re[2]: multipart/form failure

2004-09-01 Thread Alex Oboimov
Howdy, Randy.

You wrote 1 sept 2004, 19:24:42:

RK> Are you using libapreq2 to handle the file upload?
RK> Or something else?

Sorry Randy I'm using my own script to parse form
data but it was thoroughly debugged in the old
system and used to work fine. Though I must admit
some strange behaviour - all files used to get
extra \r\n symbols, so I was forced to double
chop() the buffer before inserting it into
database. That worked for all types of files
equally.

RK> Does this problem arise for clients both on Unix and
RK> Windows? Is it browser-specific?

Alas, all my clients are windows based - never had
a chance to check Unix client's behaviour.

RK> Do you know at what stage the corruption in the .doc
RK> file occurs (eg, on upload, storing it in the database,
RK> or on download)?

Inspection of buffer content after the FORM
parsing shows that extra \r\n appear both in the
beginning and at the end of the file so I presume
the upload process is to blame.

RK> Do you know why the extra \r\n occur?

If I knew that I suppose I could find solution
easily.

RK> Normally these are an
RK> issue only with text files, in going between Unix and
RK> Windows - one might think that for binary files no such
RK> mangling need be done (as long as all appropriate handling
RK> of the files at all stages is done in binary mode, if
RK> applicable).

Text files constitute no problem - no one notices
presence of these \r\n symbols.

RK> If you don't chop(), is there a difference
RK> between how .doc and other binary (eg, .zip) files are
RK> handled?

If I don't chop (except for original double chop)
all binaries (zip, rar, pdf, jpg et al) are served
unchanged, only doc files acquire extra \r\n.

So, for time being I applied temporary solution
just to tame my clients. I inserted in my script
the lines 'if ($type='application/msword') {...}
just to cut out both leading and trailing \r\n's.
And it works!!

But I'm curious to find the source of the problem.
Plans: to use libapreq though I lack tutorial
texts concerning Apache::Request and mod_perl as a
whole.



-- 
Regards,
 Alex  mailto:[EMAIL PROTECTED]



-- 
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html