ID: 15940
Updated by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
-Status: Open
+Status: Feedback
Bug Type: Apache related
Operating System: Linux
PHP Version: 4.1.2
New Comment:
Does this happen with PHP 4.2.0 ?
Previous Comments:
------------------------------------------------------------------------
[2002-04-27 01:42:20] [EMAIL PROTECTED]
I've started experiencing something similar since I upgraded to 4.1.2.
The segfaults kept occuring during a POST operations, after enabling
debug and rebuilding my rpms I then noticed the following messages in
the apache error_log:
Unknown(0) : Warning - POST Content-Length of 75 bytes exceeds the
limit of 16 bytes.
This left me scratching my head until I skimmed through php.ini and
found the setting for post_max_size=16
comparison with another working php server that uses an older php.ini
file this var was set to 8M.
this has affected two of my servers at the same time. The only
commonality that I have is that I use ZendIDE and recently updated from
2.0.0 to 2.0.1 on both machines.
The third machine (working) has no Zend installations on it.
------------------------------------------------------------------------
[2002-04-11 02:18:47] [EMAIL PROTECTED]
It happens here also. I tried with several apache version, but the
error is the same. I have to restart apache on hourly basis. With 4.06
it worked for months.
------------------------------------------------------------------------
[2002-03-19 10:04:41] [EMAIL PROTECTED]
Check out bug-report #14529, talking about propably the same problems
there
------------------------------------------------------------------------
[2002-03-19 06:41:49] [EMAIL PROTECTED]
Had the same problems as described in first post in this thread. We
tried an older apache, 1.3.20. This doesn't help, same problems occur:
the stopping of php-parsing in the middle or end of an echo-command,
and the exited on signal 11 message in var/log/messages.
Our php 4.1.2 configuration:
'./configure' '--with-mysql=/usr/local'
'--with-postgres=/usr/local/pgsql' '--with-gnu-ld' '--with-libz'
'--with-bz2' '--with-gdbm' '--with-ndbm' '--with-gd' '--with-openssl'
'--with-mm' '--enable-sysvsem' '--enable-sysvshm' '--with-mhash'
'--with-mcrypt' '--with-apache=../apache_1.3.20'
We tried an older version of Apache, because this seemed the only
difference to another server where no exited-on-signal-11-messages were
found in the /var/log/messages-file.
Didn't look at the difference in load though, shall ask our
administrators about this.
------------------------------------------------------------------------
[2002-03-13 06:12:16] [EMAIL PROTECTED]
I should mention that the problems occurs even if there is no call to
Interbase at all. In our case we saw it happen in an index.php file
which gets some session values and sets some constants base on the
environment. It then creates html/javascript to open a new browser
window. This didn't happen as the rendering ended inmidst the
javascript code. Only after this is Interbase involved.
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/15940
--
Edit this bug report at http://bugs.php.net/?id=15940&edit=1
