Loading...
 
Features / Usability

Features / Usability


tiki-upload_image.php crashes apache

posts: 3

I have problems using picture upload.

tikiwiki-1.9.1/tiki-upload_image.php

I always get a
"Zero Sized Reply"

and in my apache2/error_log there is the following entry :

Copy to clipboard
[Sun Oct 16 10:26:49 2005] [notice] child pid 25249 exit signal Segmentationfault (11)

I think there is a problem in
tikiwiki-1.9.1/tiki-upload_image.php using my version of apache/php so that any process die.

Some more detailed view to the processes running on my Linux box, gives the answer.
The attempt to upload a file, crashes one of the preforking servers

Copy to clipboard
wwwrun 25249 25248 0 10:15 ? 00:00:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf



I am no php expert, so I did not know how to proceed.

Does anybody can give me a hint what is wrong ?

My Apache/php version are
apache2-mod_php4-4.3.8-8.14
apache2-2.0.50-7.7
apache2-prefork-2.0.50-7.7

posts: 1092

Do you have your php error visible?
admin->general->PHP error reporting level for
Perhaps you will see a php error before crashing apache
sylvie

posts: 3

No, there is no php error reported, although all PHP error reporting is switch on.
Should these erros be reported in the browser or in a log file on the server ?


posts: 1092

If you look with google for 'zero sized reply', you can see
'Some firewalls allow HTTP filtering based on contents of packets'. Try to remove http filtering on the firewall
In tikiwiki, the images are retrieve via an http request.
I don't know if there is a connection
sylvie

posts: 3

> If you look with google for 'zero sized reply', you can see
> 'Some firewalls allow HTTP filtering based on contents of packets'. Try to remove http filtering on the firewall
> In tikiwiki, the images are retrieve via an http request.
> I don't know if there is a connection
> sylvie

Thanks for your help, but
I see a direct connection between the 'zero sized reply' and the error messages in the apache2/error_log. Each time I try an upload the mentioned error trace is printed and one of the preforked httpd processes has died.
It sounds mysterios to me, that a firewall setting will force such a situation.
Is seems clear to me, that the crashing communication partner of the browser (the httpd proceess), will be noticed by the browser as a connection break. So the browser waiting for a reply, has only the chance to print a message to the user like 'zero sized reply'.

Nevertheless I will check the http firewall settings.

Is there anybody using the same apache2 and mod_php4 version on a Linux system ?
Can give anybode give my a hint, which version of apache2 and mod_php work without such problems ?