php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #66597 OPCACHE BUG
Submitted: 2014-01-28 18:15 UTC Modified: 2014-12-30 10:42 UTC
Votes:5
Avg. Score:3.8 ± 1.0
Reproduced:2 of 2 (100.0%)
Same Version:1 (50.0%)
Same OS:1 (50.0%)
From: edu_1721 at hotmail dot com Assigned:
Status: No Feedback Package: opcache
PHP Version: 5.5.8 OS: CENTOS 6.5 32 BITS
Private report: No CVE-ID: None
Welcome back! If you're the original bug submitter, here's where you can edit the bug or add additional notes.
If you forgot your password, you can retrieve your password here.
Password:
Status:
Package:
Bug Type:
Summary:
From: edu_1721 at hotmail dot com
New email:
PHP Version: OS:

 

 [2014-01-28 18:15 UTC] edu_1721 at hotmail dot com
Description:
------------
Hello, 

The OPCACHE in this php 5.5.8 is wrong.

In webserver Nginx last version, generate a Bad Gateway 502 error.

Anothers friends webmaster have the same problem.

I have fixed this problem using the OPCACHE in php 5.5.6 and work perfect.

You need check and path this bugs.

Thanks you.


Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2014-01-28 19:06 UTC] krakjoe@php.net
-Status: Open +Status: Feedback
 [2014-01-28 19:06 UTC] krakjoe@php.net
Thank you for this bug report. To properly diagnose the problem, we
need a short but complete example script to be able to reproduce
this bug ourselves. 

A proper reproducing script starts with <?php and ends with ?>,
is max. 10-20 lines long and does not require any external 
resources such as databases, etc. If the script requires a 
database to demonstrate the issue, please make sure it creates 
all necessary tables, stored procedures etc.

Please avoid embedding huge scripts into the report.


 [2014-02-02 15:51 UTC] daniel at blodan dot se
Having the same issue on FreeBSD with nginx 1.4.4 and php-fpm 5.5.8 with opcache, reverting back to 5.5.6 solves the issue.

Unfortunately I can't give a simple reproduceable script, the websites run through frameworks such as laravel and codeigniter.

All I can tell is that the first request to a non-compiled script results in a Bad Gateway response, the second request works as its supposed to. So it seems that opcache returns something different the request it compiles the files than when it's reading from its cache.
 [2014-02-03 06:38 UTC] krakjoe@php.net
The problem is that this description doesn't give us a starting place to work with; there's no logical pathway to what you describe, both requests infact do serve the same ops from shm, the first request is no different to the second, logically.

If there are lots of dependencies then gist/git is an option, but it's preferable for you to try to reduce the problem to it's simplest possible form and use that code in a bug report.

A bad gateway message is indicative of a crashed php-fpm process, it's probably possible to attach to a php-fpm worker and hit it till it crashes, you can then at least provide a backtrace and or coredump, this would also give us a starting place.
 [2014-02-03 16:14 UTC] rasmus@php.net
Try setting opcache.optimization_level=0 in your ini and see if that changes things. If it does, then this has already been fixed.
 [2014-02-04 16:12 UTC] daniel at blodan dot se
I just got a core dump in cli with opcache activated, disabling opcache made the core dumping go away, might be related:
https://bugs.php.net/bug.php?id=66642
 [2014-12-30 10:42 UTC] php-bugs at lists dot php dot 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 "Re-Opened". Thank you.
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved.
Last updated: Sun Nov 24 22:01:33 2024 UTC