|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #63909 apc stopped caching after upgrade
Submitted: 2013-01-05 10:44 UTC Modified: 2016-11-18 21:20 UTC
Avg. Score:4.2 ± 0.9
Reproduced:13 of 15 (86.7%)
Same Version:2 (15.4%)
Same OS:4 (30.8%)
From: viktor at szepe dot net Assigned:
Status: Wont fix Package: APC (PECL)
PHP Version: 5.3.20 OS: Debian 6.0.6
Private report: No CVE-ID: None
View Add Comment Developer Edit
Welcome! If you don't have a Git account, you can't do anything here.
You can add a comment by following this link or if you reported this bug, you can edit this bug over here.
Block user comment
Status: Assign to:
Bug Type:
From: viktor at szepe dot net
New email:
PHP Version: OS:


 [2013-01-05 10:44 UTC] viktor at szepe dot net
Good afternoon!

(really I am using PHP 5.3.3-7+squeeze14)

After pecl upgrade apc 3.1.14 stopped caching. apc.php show no differences.
3.1.14 compiles OK but there are no Hits, only Misses.

What should I do now?
(reverted back to 3.1.13)

Thank you!
All the best wishes to you!


Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2013-01-07 08:19 UTC]
-Status: Open +Status: Feedback
 [2013-01-07 08:19 UTC]
Anything abnormal in the server logs? Also, would it be possible for you to test with 5.3.20? Please also try to test with a small snippet - if it not suffer the same fate you can try to extract the reproduce code from your app.
 [2013-01-07 10:05 UTC] viktor at szepe dot net
-Status: Feedback +Status: Open
 [2013-01-07 10:05 UTC] viktor at szepe dot net
Thank you for your answer!
Really I do not know how to use APC. While running WordPress-es and looking at apc.php I noticed no Hits. I know WP uses APC but it is a production server, so I got frightened and reverted back to 3.1.13
 [2013-01-07 12:54 UTC] jan dot slusarczyk at gmail dot com
I have the same problem on Ubuntu 12.04.01 LTS (php 5.3.10). There were only few 
hits and a lot of cache misses. Nothing peculiar in server logs, no errors 
during build time. make test gives:

APC: classes with namespaces (php 5.3) [tests/apc53_001.phpt]
APC: global spaces (php 5.3) [tests/apc53_002.phpt]
APC: closures (php 5.3) [tests/apc53_004.phpt]
APC: apc_store/fetch with objects [tests/apc_002.phpt]
APC: apc_store/fetch with objects (php 5.3) [tests/apc_003b.phpt]
APC: apc_delete_file test [tests/apc_009.phpt]
APC: bindump file cache part 1 [tests/apc_bin_002.phpt]
Bug #62757 (php-fpm carshed when used apc_bin_dumpfile with apc.serializer) 
Bug #62765 (apc_bin_dumpfile report Fatal error when there is "goto" in 
function) [tests/bug62765.phpt]
APC: APCIterator formats [tests/iterator_006.phpt]

You may have found a problem in PHP.
 [2013-01-07 15:33 UTC] maarten at mvandek dot nl
I'm having the same problem. Upgraded from 3.1.13 to 3.1.13 via pecl install apc-3.1.14 on Ubuntu 12.04 LTS x64 official repository.

I've used the same options when compiling 3.1.14 and all I got was cache misses on the apc.php stat page.

Tested on a server with WordPress 3.5.

Reverted back to 3.1.13 and the problems were gone.
 [2013-01-07 16:31 UTC]
What are your apc.stat and apc.include_once_override settings?
 [2013-01-07 16:31 UTC]
-Status: Open +Status: Feedback
 [2013-01-07 16:37 UTC] viktor at szepe dot net
apc.include_once_override	0
apc.stat	0
 [2013-01-07 16:37 UTC] viktor at szepe dot net
-Status: Feedback +Status: Open
 [2013-01-07 16:38 UTC]
Also, if tests are failing, please look at the failures and see if there is a 
common cause. eg. if tests/apc53_001.phpt failed, look at tests/apc53_001.diff
 [2013-01-07 19:13 UTC] jan dot slusarczyk at gmail dot com
Will the diff files help? Below are first two diff files. Anything I can do to 

001- object(Foo\Bar\Baz)#1 (3) {
002-   ["i"]=>
003-   int(1)
004-   ["f":protected]=>
005-   float(3.14)
006-   ["s":"Foo\Bar\Baz":private]=>
007-   string(11) "hello world"
008- }
009- ===DONE===

001- array(4) {
002-   [0]=>
003-   int(1)
004-   [1]=>
005-   int(2)
006-   [2]=>
007-   int(3)
008-   [3]=>
009-   int(4)
010- }
011- array(4) {
012-   [0]=>
013-   int(1)
014-   [1]=>
015-   int(2)
016-   [2]=>
017-   int(3)
018-   [3]=>
019-   int(4)
020- }
021- string(8) "IT WORKS"
022- ===DONE===
 [2013-01-08 00:45 UTC]
Maybe it is config-related somehow. I tried a bunch of different PHP versions 
with APC 3.1.14 today and they all worked. But all my configs were close to 

extension =
apc.enabled = 1
apc.shm_segments = 1
apc.optimization = 0
apc.shm_size = 384M
apc.ttl = 7200
apc.user_ttl = 7200
apc.num_files_hint = 1024
apc.mmap_file_mask = /tmp/apc.XXXXXX
apc.enable_cli = 1
apc.cache_by_default = 1
apc.include_once_override = 1
apc.stat = 1
apc.stat_ctime = 1
 [2013-01-08 10:02 UTC] jan dot slusarczyk at gmail dot com
My config:
apc.shm_size = 160M
apc.max_file_size = 16M
apc.file_update_protection = 5
apc.slam_defense = 0
; apc.write_lock = 1

build config:
./configure --enable-apc-mmap --enable-apc --with-php-config=/usr/bin/php-config
 [2013-01-09 09:58 UTC] tuxlex at hotmail dot com
This is the second time I write this comment, first time dunno what happened but I lost all the comment when submitting...

Ok let's begin.

I have two server installations. Production server and testing server, both have the same webserver configuration (nginx + php5-fpm + apc + memcache + varnish 3 + drupal 7).

Production server runs a Debian Squeeze and testing server runs a Debian Sid/Wheezy. Monday the 7th production server had PHP5.3 (from repository) and testing server had PHP5.4 (from debian repository).

I saw the 3.1.14, I compiled in my testing env, all tests ok, I compiled in prod server, I obtained the same errors Jan Slusarczyk obtained. 

as PHP5.3 was a little old, I upgraded prod server to "PHP5.4.10-1~dotdeb.0" I checked tests all succeeded and now I blame myself for not testing better, yeps I was too lazy, my fault. And testing server to "PHP5.4.4-11" (yeps i'm using deb repository, but is because Squeeze was frozen without php5-fpm, that's the reason to use dotdeb repository).

Some hours later I started to have 502 Bad Gateway in some random pages,I have 4 full drupal 7 + modules obviously updated,  finally in nginx logs I obtained this:
2013/01/09 09:01:27 [error] 15489#0: *53 recv() failed (104: Connection reset by peer) while reading response header from upstream, client:, server:, request: "GET /content/wysiwyg-html5-contrib-commit HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "", referrer: ""

The most weird thing is now I have 3.1.13 version which never failed in test with PHP5.3 but now in prod server tests:
APC: Bug #62456 Incorrect description of notice variation 1 (php 5.4 nts) [tests/apc54_004.phpt]
APC: APCIterater basic test on file (php 5.4) [tests/apc54_020.phpt]
APC: Bug #62699 Wrong behavior with traits (variant 2) [tests/apc54_bug62699_2.phpt]

And in testing server I obtained this:
APC: Bug #62456 Incorrect description of notice variation 1 (php 5.4 nts) [tests/apc54_004.phpt]
APC: Bug #59938 APCIterator fails with large user cache [tests/apc54_018.phpt]

But both seem to be more stable, and during last 12 hours I didn't obtained errors nor visible nor in logs.

My apc.ini config (very simple):
apc.cache_by_default = 1
apc.filters = "apc\.php$,memcache\.php$"
apc.stat = 0
apc.mmap_file_mask = "/tmp/apc.XXXXXX"
 [2013-01-14 11:44 UTC] laverty dot go at gmail dot com
I have tested all version from 3.1.9 to 3.1.13 with default compile options.

Also 3.1.13 is working for me
 [2013-01-23 17:31 UTC] daniel at mastyx dot de
I do have the same problem here in one of my test servers, 3.1.13 works as expected whereas 3.1.14 does cache much less. I still see that some caching is done using apc_cache_info(), but the amount of cached files is much less than with the previous version.

The test environment consists of

CentOS 5.8
PHP 5.3.21 (FPM)
APC 3.1.14
compiled using GCC 4.1.2 and --enable-apc-mmap --enable-apc

While building 3.1.14 'make test' produces the same FAILs as reported by Jan. The APC config options used are:


I already tested the options apc.include_once_override and apc.stat_ctime, but they do not change anything.
 [2013-09-30 09:16 UTC] Sebastian dot Nickel at fashiondays dot com
we have the same problem. We used APC v3.1.9 so far, but got affected by bug #52144 which should be fixed in 3.1.14. The bug itself does not come up anymore, but now we are not caching as many files as before.

With version 3.1.9 (which is active on 66% of our cluster) we cache about 60 MB of opcode. With version 3.1.14 we cache only 20kb. The user cache itself is not affected.

We are using the following apc.ini settings (for both APC versions):

We are using Ubuntu 12.04 LTS with stock apache and mod_php5.
 [2013-11-12 08:17 UTC] Sebastian dot Nickel at fashiondays dot com
are there any news on this bug or any workarounds known? We would really like to use version 3.1.14.
 [2014-01-22 11:10 UTC] asl at launay dot org

I bumped into this issue, tracked it down to this in the git repo:

Before and including commit

OK, we have hits

from (including) commit

No more hits...

Debian Squeeze 6.0.8, php5 5.3.3-7+squeeze18 , and apc compiled locally with the same stuff, but using the git repo to compile it.
 [2016-11-18 21:20 UTC]
-Status: Open +Status: Wont fix
 [2016-11-18 21:20 UTC]
APC is no longer supported in favor of opcache that comes bundled with PHP, if you wish to use the user cache, then look at PECL/APCu.
PHP Copyright © 2001-2021 The PHP Group
All rights reserved.
Last updated: Wed Jun 23 12:01:23 2021 UTC