Your message dated Wed, 25 Jul 2012 08:47:45 +0000
with message-id <e1stxfx-0004qd...@franck.debian.org>
and subject line Bug#682666: fixed in xcache 2.0.0-2
has caused the Debian Bug report #682666,
regarding php5-xcache: XCache with xcache.size enabled crashes after a while
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
682666: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682666
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php5-xcache
Version: 2.0.0-1
Severity: important


When XCache's regular cache is enabled (xcache.size isn't 0), after loading a 
couple of large of PHP scripts, XCache seems to crash.
Basically I see things like this in my Apache error log:
[Tue Jul 24 15:37:32 2012] [notice] child pid 19048 exit signal Segmentation 
fault (11)
[Tue Jul 24 15:37:32 2012] [notice] child pid 19050 exit signal Segmentation 
fault (11)
[Tue Jul 24 15:37:34 2012] [notice] child pid 19052 exit signal Segmentation 
fault (11)
[Tue Jul 24 15:37:36 2012] [notice] child pid 19053 exit signal Segmentation 
fault (11)

And the pages never load in the browser.

If I turn off XCache's regular cacher (but still leave XCache's variable cacher 
on), then things seem normal. I can load many many large PHP scripts and my 
server doesn't seem to ever crash.

I peformed many tests with XCacher's regular cache on and off, to narrow down 
that this indeed was the problem in my server crashing.
I noticed the larger I make xcache.size, the longer it takes for XCache to 
start crashing.


-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (700, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.0.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages php5-xcache depends on:
ii  libapache2-mod-php5 [phpapi-2 5.4.4-3    server-side, HTML-embedded scripti
ii  libc6                         2.13-35    Embedded GNU C Library: Shared lib
ii  php5-cgi [phpapi-20100525]    5.4.4-3    server-side, HTML-embedded scripti
ii  php5-cli [phpapi-20100525]    5.4.4-3    command-line interpreter for the p

php5-xcache recommends no packages.

php5-xcache suggests no packages.

-- Configuration Files:
/etc/php5/mods-available/xcache.ini changed:
; configuration for php Xcache module
[xcache-common]
;; install as zend extension (recommended), normally "$extension_dir/xcache.so"
zend_extension = /usr/lib/php5/20100525/xcache.so
[xcache.admin]
xcache.admin.enable_auth = On
; Configure this to use admin pages
; xcache.admin.user = "mOo"
; xcache.admin.pass = md5($your_password)
; xcache.admin.pass = ""
[xcache]
; ini only settings, all the values here is default unless explained
; select low level shm/allocator scheme implemenation
xcache.shm_scheme =        "mmap"
; to disable: xcache.size=0
; to enable : xcache.size=64M etc (any size > 0) and your system mmap allows
xcache.size  =               16M
; set to cpu count (cat /proc/cpuinfo |grep -c processor)
xcache.count =                 2
; just a hash hints, you can always store count(items) > slots
xcache.slots =                8K
; ttl of the cache item, 0=forever
xcache.ttl   =                 0
; interval of gc scanning expired items, 0=no scan, other values is in seconds
xcache.gc_interval =           0
; same as aboves but for variable cache
xcache.var_size  =           16M
xcache.var_count =             1
xcache.var_slots =            8K
; default ttl
xcache.var_ttl   =             0
xcache.var_maxttl   =          0
xcache.var_gc_interval =     300
xcache.test =                Off
; N/A for /dev/zero
xcache.readonly_protection = Off
; for *nix, xcache.mmap_path is a file path, not directory.
; Use something like "/tmp/xcache" if you want to turn on ReadonlyProtection
; 2 group of php won't share the same /tmp/xcache
; for win32, xcache.mmap_path=anonymous map name, not file path
xcache.mmap_path =    "/dev/zero"
; leave it blank(disabled) or "/tmp/phpcore/"
; make sure it's writable by php (without checking open_basedir)
xcache.coredump_directory =   ""
; per request settings
xcache.cacher =               On
xcache.stat   =               On
xcache.optimizer =           Off
[xcache.coverager]
; per request settings
; enable coverage data collecting for xcache.coveragedump_directory and 
xcache_coverager_start/stop/get/clean() functions (will hurt executing 
performance)
xcache.coverager =          Off
; ini only settings
; make sure it's readable (care open_basedir) by coverage viewer script
; requires xcache.coverager=On
xcache.coveragedump_directory = ""


-- no debconf information

--- End Message ---
--- Begin Message ---
Source: xcache
Source-Version: 2.0.0-2

We believe that the bug you reported is fixed in the latest version of
xcache, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 682...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Michal Čihař <ni...@debian.org> (supplier of updated xcache package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Wed, 25 Jul 2012 09:37:09 +0200
Source: xcache
Binary: php5-xcache
Architecture: source amd64
Version: 2.0.0-2
Distribution: unstable
Urgency: low
Maintainer: Michal Čihař <ni...@debian.org>
Changed-By: Michal Čihař <ni...@debian.org>
Description: 
 php5-xcache - Fast, stable PHP opcode cacher
Closes: 682666
Changes: 
 xcache (2.0.0-2) unstable; urgency=low
 .
   * Cherry pick some fixes from upstream 2.0.1:
     - fixed segv on cache full (Closes: #682666)
     - fixed handling of zend_error
     - fix disassembler for 2.4 literal
     - XCache admin APIs (admin page) cause SEGV
Checksums-Sha1: 
 be7170c65f39743bd75ca46727d9fa03acca7516 1901 xcache_2.0.0-2.dsc
 60d40695c5d0adbb99db66a5f914675ef448cfca 18265 xcache_2.0.0-2.debian.tar.gz
 a5a216813f7e358773a599296624787f046cf8e6 111318 php5-xcache_2.0.0-2_amd64.deb
Checksums-Sha256: 
 402c97de4a47db0f6bec9dcc4a8539221163c73d868a6d04e92011f1499e4fc0 1901 
xcache_2.0.0-2.dsc
 a6b3c53cb24444193987cbfaae8bffd6e6994cd5a49aeb8ecbc8ca547e905c44 18265 
xcache_2.0.0-2.debian.tar.gz
 6066443021df0fbab59015cd674d49f9db1962d1f72cac10969679b1c30e8a54 111318 
php5-xcache_2.0.0-2_amd64.deb
Files: 
 d6d63f5f4f8e42174f34bdd5c0b8fd2d 1901 php optional xcache_2.0.0-2.dsc
 3aae10fbc1ee75f326659b198fd47fc5 18265 php optional 
xcache_2.0.0-2.debian.tar.gz
 c3a91bbaaefe323a8272f31f257a8c80 111318 php optional 
php5-xcache_2.0.0-2_amd64.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCAAGBQJQD6LNAAoJEGo39bHX+xdNSNoP/35V/X/cVTflozndz0JaYGSR
QrRzt68Kk5qIIGVg5gFP86eEf1soNuKj58bWa45b3CIEy2gKzXnQQc7qhAEy/8ZM
4gFhc/KykbdLc9St7t3lt2b7WwSrcQT3u8vFJ6jGtMvznJoLt9LPDoep0J0kn7Hf
QAWO5UB/A758VeMBHkortnonZyKSMbuUtFYdRl0gdljb8RPBZCWkmxtyKlWXcroz
i2ubbjUeunmWXy1uCj78IpTubAF/78VSRV4BMa6KxBxet6dZXfaer2P08b4IBYsd
1OxzBpT41Ztg0ERq6/BLmoxsAA2CJNxKz0Jmicd4hyD5aEOHJ5uxJfx8gjJIzBaV
KpVXAgC9DHQB53c04QPNhwhyXYAtXOsHbWIyEOEyKMEHfrnelg3cQLFL4XAFN9i1
qSVsYC0q4vrqj/XPBrhhDrXQvRA8oYtwCbmYcGZxOPiR2Z+lFX8MdyCNIS3KcBVL
WxS3TUHJt0SHXfnTyrOT2iE5nzlJqliAybK3RHdOi6RExlDvPwclcqkb+5KON1ap
uovd4oBrGMsMMTJeXldc2eWt3GdA6i4rL/PIncHEo+qIeH39vGCFZMciU4gCDdsi
YoSCvLpaYOU9xVMqNvc6S6K4sQ6me7F6cHQvHKAKPmq2W1K23Jtsbf9cIqJzSZWc
5ayWtol2mH3liteiyHhu
=Q91d
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to