ID:               27899
 Updated by:       [EMAIL PROTECTED]
 Reported By:      charvel at bluemission dot com
-Status:           Feedback
+Status:           No Feedback
 Bug Type:         Apache2 related
 Operating System: Linux 2.4.25
 PHP Version:      4.3.6RC2
 New Comment:

No feedback was provided. The bug is being suspended because
we assume that you are no longer experiencing the problem.
If this is not the case and you are able to provide the
information that was requested earlier, please do so and
change the status of the bug back to "Open". Thank you.




Previous Comments:
------------------------------------------------------------------------

[2004-04-09 11:13:18] [EMAIL PROTECTED]

1. As you're using a threaded webserver and asking for trouble this bug
is pretty much bogus. (the crash happens elsewhere than in PHP
itself..where is the GDB backtrace?)



2. Try adding your original configure options (those ones excluded
which I told you NOT to use) one by one and see which one causes the
crash, like this:



# rm -f config.cache

# ./configure --disable-all --with-apxs2 --with-zlib

# make clean && make



(try them all _separately_ first!)



------------------------------------------------------------------------

[2004-04-09 05:24:09] charvel at bluemission dot com

1. worker

2. In this case work fine.

------------------------------------------------------------------------

[2004-04-08 19:01:21] [EMAIL PROTECTED]

1. What MPM is Apache2 using?

2. Get fresh sources, and use this configure line:

# ./configure --disable-all --with-apxs2



------------------------------------------------------------------------

[2004-04-08 12:21:24] charvel at bluemission dot com

Well, I get a 4.3.6RC2, configure by:



./configure --with-apxs2



when I send to the master httpd process USR1 signal I got:



[Thu Apr 08 18:13:19 2004] [notice] SIGUSR1 received.  Doing graceful
restart

[Thu Apr 08 18:13:19 2004] [notice] seg fault or similar nasty error
detected in the parent process

[Thu Apr 08 18:13:19 2004] [emerg] (22)Invalid argument:
apr_proc_mutex_unlock failed. Attempting to shutdown process
gracefully.

------------------------------------------------------------------------

[2004-04-08 06:35:12] [EMAIL PROTECTED]

I think he meant 4.3.6RC2 (not 4.3.5RC2), from: http://qa.php.net

------------------------------------------------------------------------

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/27899

-- 
Edit this bug report at http://bugs.php.net/?id=27899&edit=1

Reply via email to