php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #56867 Longtime execution segfaults?
Submitted: 2006-03-01 12:13 UTC Modified: 2009-03-02 00:22 UTC
From: pecl dot 20 dot korkman at spamgourmet dot org Assigned:
Status: No Feedback Package: APC (PECL)
PHP Version: 5.1.1 OS: SUSE Linux 9.0
Private report: No CVE-ID: None
View Add Comment Developer Edit
Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know!
Just going to say 'Me too!'? Don't clutter the database with that please — but make sure to vote on the bug!
Your email address:
MUST BE VALID
Solve the problem:
39 - 38 = ?
Subscribe to this entry?

 
 [2006-03-01 12:13 UTC] pecl dot 20 dot korkman at spamgourmet dot org
Description:
------------
APC 3.0.8
Apache 2.0.48

Some permanently running scripts (could be called daemons) on my server crash unexpectedly (segfault Apache) after running fine for hours. Unfortunately I can't supply reproduction code as I have no clue at what point or why the script dies so I'll try to post all possible activities of that script:

- It's an RPC server
- Listens on a network socket for incoming UDP packets, possibly closes and reopens that socket
- Evaluates code fetched from a MySQL database (same code was eval'd before crash and was scheduled when crash happened)
- APC constants cache, user cache and acceleration (I just got used to it)
- Class inheritance (no new classes and no require()s in the eval'd code)
- PEAR SMTP classes and by that mail()
- Writes status information to MySQL database, including memory usage which was at about 1 MB at the time of the crash (without APC, the same script uses 5 MB btw., I guess because of compilation overhead)

Please do not comment that this should be executed via CLI :)

This may or may not be connected to Bug #6667 and probably doesn't help either.

Reproduce code:
---------------
Apache 2 is stock SUSE 9.0 Apache server, updated by YaST when security fixes were available.

PHP 5.11:

./configure
--prefix=/usr/local/php5/
--with-apxs2=/usr/sbin/apxs2
--with-openssl
--enable-safe-mode
--with-bz2
--with-zlib
--enable-magic-quotes
--enable-sockets
--with-ttf
--with-gd
--with-mysql
--with-curl
--enable-memory-limit
--enable-ftp
--enable-dbase
--with-libxml-dir=/usr/local/libxml2/



Expected result:
----------------
No segfaults.

Actual result:
--------------
Segfaults.

[Wed Mar 01 11:31:56 2006] [notice] child pid 2954 exit signal Segmentation fault (11)

Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2006-03-01 12:15 UTC] rasmus@php.net
How about a backtrace?  Attach gdb to one of your running processes and get a backtrace when it crashes.
 [2009-03-02 00:22 UTC] shire@php.net
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.


 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved.
Last updated: Thu Mar 28 23:01:26 2024 UTC