[phpa] Re: Apache Error log messages

Here are the results after 24 hours with PHPA turned off in the php.ini file
and apache restarted.

[Thu Apr  4 10:25:21 2002] [notice] child pid 23167 exit signal Segmentation
fault (11)
[Thu Apr  4 10:25:48 2002] [notice] child pid 23278 exit signal Segmentation
fault (11)
PHP Warning:  Supplied argument is not a valid MySQL result resource in
/usr/local/apache/sites/disboards.com/htdocs/admin/db_mysql.php on line 154
[Thu Apr  4 10:45:01 2002] [notice] child pid 24432 exit signal Segmentation
fault (11)
[Thu Apr  4 10:45:38 2002] [notice] child pid 24295 exit signal Segmentation
fault (11)
[Thu Apr  4 10:46:06 2002] [notice] child pid 24457 exit signal Segmentation
fault (11)
[Thu Apr  4 10:46:21 2002] [notice] child pid 24461 exit signal Segmentation
fault (11)
[Thu Apr  4 10:46:51 2002] [notice] child pid 2025 exit signal Segmentation
fault (11)
[Thu Apr  4 10:49:03 2002] [notice] child pid 24568 exit signal Segmentation
fault (11)
[Thu Apr  4 11:55:10 2002] [notice] child pid 27657 exit signal Segmentation
fault (11)
[Thu Apr  4 11:55:50 2002] [notice] child pid 18755 exit signal Segmentation
fault (11)
[Thu Apr  4 11:56:09 2002] [notice] child pid 27083 exit signal Segmentation
fault (11)
[Thu Apr  4 11:58:21 2002] [notice] child pid 25305 exit signal Segmentation
fault (11)
[Thu Apr  4 12:16:32 2002] [notice] child pid 28118 exit signal Segmentation
fault (11)
[Thu Apr  4 12:16:41 2002] [notice] child pid 28064 exit signal Segmentation
fault (11)
[Thu Apr  4 12:17:39 2002] [notice] child pid 28068 exit signal Segmentation
fault (11)
[Thu Apr  4 12:19:17 2002] [notice] child pid 28290 exit signal Segmentation
fault (11)
[Thu Apr  4 13:12:29 2002] [notice] child pid 30956 exit signal Segmentation
fault (11)
[Thu Apr  4 13:12:40 2002] [notice] child pid 30955 exit signal Segmentation
fault (11)
PHP Warning:  Supplied argument is not a valid MySQL result resource in
/usr/local/apache/sites/disboards.com/htdocs/admin/db_mysql.php on line 154
[Thu Apr  4 17:14:08 2002] [error] [client 217.0.36.131] File does not
exist: /usr/local/apache/htdocs/scripts/..%5c..%5cwinnt/system32/cmd.exe
[Thu Apr  4 17:59:14 2002] [notice] child pid 31996 exit signal Segmentation
fault (11)
[Thu Apr  4 17:59:14 2002] [notice] child pid 31973 exit signal Segmentation
fault (11)
[Thu Apr  4 17:59:15 2002] [notice] child pid 31915 exit signal Segmentation
fault (11)
[Thu Apr  4 18:23:32 2002] [notice] child pid 307 exit signal Segmentation
fault (11)
[Thu Apr  4 18:24:23 2002] [notice] child pid 31464 exit signal Segmentation
fault (11)
[Thu Apr  4 18:26:12 2002] [notice] child pid 31537 exit signal Segmentation
fault (11)
[Thu Apr  4 18:26:15 2002] [notice] child pid 897 exit signal Segmentation
fault (11)
[Thu Apr  4 18:26:15 2002] [notice] child pid 31546 exit signal Segmentation
fault (11)
[Thu Apr  4 18:49:21 2002] [notice] child pid 1695 exit signal Segmentation
fault (11)
[Thu Apr  4 18:49:45 2002] [notice] child pid 1655 exit signal Segmentation
fault (11)
[Thu Apr  4 18:49:50 2002] [notice] child pid 1645 exit signal Segmentation
fault (11)
[Thu Apr  4 18:50:05 2002] [notice] child pid 1611 exit signal Segmentation
fault (11)
[Thu Apr  4 18:51:10 2002] [notice] child pid 1204 exit signal Segmentation
fault (11)
[Thu Apr  4 19:02:47 2002] [notice] child pid 2165 exit signal Segmentation
fault (11)
[Thu Apr  4 19:03:46 2002] [notice] child pid 2220 exit signal Segmentation
fault (11)
[Thu Apr  4 19:03:47 2002] [notice] child pid 1919 exit signal Segmentation
fault (11)
[Thu Apr  4 19:04:24 2002] [notice] child pid 2219 exit signal Segmentation
fault (11)
[Thu Apr  4 19:05:15 2002] [notice] child pid 2193 exit signal Segmentation
fault (11)
[Thu Apr  4 19:05:15 2002] [notice] child pid 32285 exit signal Segmentation
fault (11)
[Thu Apr  4 19:05:28 2002] [notice] child pid 1317 exit signal Segmentation
fault (11)
[Thu Apr  4 19:06:18 2002] [notice] child pid 2285 exit signal Segmentation
fault (11)

-----Original Message-----
From: phpa-bounce@xxxxxxxxxxxxx [mailto:phpa-bounce@xxxxxxxxxxxxx]On Behalf
Of Nick Lindridge
Sent: Wednesday, April 03, 2002 8:11 PM
To: phpa@xxxxxxxxxxxxx
Subject: [phpa] Re: Apache Error log messages


>
> Hi,
>
> You mentioned that PHP 4.1.2 is unstable used with PHPA.
> What version of PHP would you recommend then?

No, PHP 4.1.2 is unstable period - i.e. it's unstable without PHPA as well
:-) Just as 4.0.6 is/was. Ho hum.

But, PHP 4.1.2 must be *mostly* ok because many people are surely using it
without problems - although there are also people who *will* be having
problems, i.e. segfaults, and just never realise it because they don't check
their logs thoroughly, if at all. I've sometimes seen that when looking at
logs that people have sent when investigating possible problems with phpa
(but they've also been really helpful in pointing out confirmed issues with
phpa in the past too, so I never mind going through logs!).

4.0.6 was probably OK for many people too, but it broke for me because I
used certain array functions, and even then, would only break on the 'n'th
apache request. e.g. it might take 35 requests after restarting apache, but
would always be 35 requests, unless I modified my php code a bit and then it
might always take 20 requests, or 100 requests. The bugs just took their
time to crash apache.

I'd say use whatever version of PHP that you have to and see what happens.
If you get segfaults then it would be worth trying without phpa for a day or
so to see whether you also see any segfaults. If you do then beat up the php
folks, although you have to wonder about any other plugings that you have
too. If you don't then it doesn't mean that there's not a bug in PHP, but
you can then come and point the finger at phpa as well :-)

Personally I liked 4.0.7RC3 because it appeared to fix the bugs that crashed
4.0.6, and I never had segfaults with it. I'm still using that on the phpa
site.

If you find a 'golden release' of anything, there's a lot to be said for
sticking with it until you really need to change. I stuck with the 3.22.32
(I think that was it anyway) release of mysql because I never had problems
with it. Sure it got join ordering wrong so queries were often slower than
they should be unless I forced the ordering, but then so does the much newer
3.23.42, even when you've run an analyze on the table and done everything
that you're supposed to do. The most recent versions may still be lame in
that respect, and the newest versions of mysql always seem to have problems
with this or that not working reliably. Of course there's always new stuff
that's cool too, but it seems that you're really taking a leap of faith in
using it.

nick



------------------------------------------------------------------------
  www.php-accelerator.co.uk           Home of the free PHP Accelerator

To post, send email to phpa@xxxxxxxxxxxxx
To unsubscribe, email phpa-request@xxxxxxxxxxxxx with subject unsubscribe




Take a VIRTUAL TOUR of Walt Disney World!
http://www.dreamstour.com

The Web's Best Source for Disney Information
http://www.wdwinfo.com



------------------------------------------------------------------------
  www.php-accelerator.co.uk           Home of the free PHP Accelerator

To post, send email to phpa@xxxxxxxxxxxxx
To unsubscribe, email phpa-request@xxxxxxxxxxxxx with subject unsubscribe

Other related posts: