Skip to main content

[UPS-184] OPCache issue after recent EA4 update

kdean
Anyone having problems with Opcache no longer caching scripts/keys after the 7.3.9 update? Still works fine on 7.2 and earlier but not at all with the latest 7.3.9 even though phpinfo says Opcode Caching is Up and Running and Optimization is Enabled. Previous version of 7.3 was working. Had to set all my php 7.3 sites back to 7.2 for now until I have more time to look or if others have the same problem and an update/fix is released. Also updated from cPanel 82.0.12 to 82.0.14 at the same time if it makes a difference on Centos 6.10

Comments

44 comments

Date Votes
  • cPanelLauren
    You can see in my earlier tests I wasn't able to reproduce this with LSAPI on CentOS7 nor was I able to with PHP-FPM - the only instance in which I was able to replicate this behavior is when I was running CGI which is NOT supported with OPCache. I'd love to be able to investigate this further but we'd need access to do so - I need someone to open a ticket, once you do that update here with the ticket ID.
    0
  • CyclingTribe
    Ticket submitted: 13453497
    0
  • cPanelLauren
    Sorry, I tried to create a ticket but it defaults to my host as the support provider.

    That should just be a recommendation and you should be able to continue on opening the ticket if you have root access to the server. This is discussed here: Create Support Ticket - Version 84 Documentation - cPanel Documentation
    0
  • CyclingTribe
    Thanks @cPanelLauren - I figured it out - and edited my post. Ticket 13453497
    0
  • LucasRolff
    The issue is related to an ionCube update, from cPanel support, that got a message from ionCube: [QUOTE]We are aware of this issue which only affects the PHP 7.3 ionCube Loader. We will be correcting this in the forthcoming 10.3.9 release which should become generally available either later this week or early next week.
    Basically ionCube 10.3.8 update broke stuff, a fix is coming. A temporary workaround is either to downgrade ionCube package to the previous version or just disable the extension until a fix has been made.
    0
  • CyclingTribe
    Thanks - we'll leave it disabled and update ionCube loader when the fix is released. Thanks to the cPanel team for sussing it out. :cool:
    0
  • cPanelLauren
    Hey Guys, As mentioned by @LucasRolff this is related to the IonCube update, which actually explains a lot as to why I was unable to replicate since I hadn't included it in any of my tests. We have an internal case open to track this issue (tracking only since it's an upstream issue) and I'll update here when the issue is reported to be fixed. The internal tracking case is ID UPS-184. Right now downgrading IonCube to 10.3.2 resolves the issue and we've reported the issue to the folks at IonCube who are aware of it and are working to resolve it currently. Thanks!
    0
  • kdean
    Looks like the IonCube 10.3.9 release with the fix is now available. Have at it cPanel.
    0
  • cPanelLauren
    We have a separate case open to update the RPM - CPANEL-29887 which I just took a look at and it seems that the case is pending final review so we should have the new rpm added pretty soon. I'll update here when it is.
    0
  • kdean
    I see CPANEL-29887 included in 84.0.4, but not in 82.0.17. It will be coming to 82, right? I don't see why it would be left broken. Or is it just being pushed to the test builds first rather than release.
    0
  • cPanelLauren
    Hi @kdean v84 of cPanel is slated to go to RELEASE soon, it's already in CURRENT. Fixes like this are usually put into the next RELEASE candidate or EDGE version unless they warrant what's called a backport to a version that is no longer being developed. This case doesn't meet those criteria though.
    0
  • kdean
    One would have thought the version of ioncube would have just been handled as an Easy Apache update. Plus I figured since a release of 82 broke it, you would want to fix 82 before moving on from it. I don't always upgrade to the next version on day 1 since sometimes there's still issues, but I guess I'll have to go to 84 quicker. Word of advise. Don't knowingly leave things broken for a release version especially when it was recently broken. That's just wrong-headed thinking for a developer in my opinion.
    0
  • cPanelLauren
    One would have thought the version of ioncube would have just been handled as an Easy Apache update. Plus I figured since a release of 82 broke it, you would want to fix 82 before moving on from it. I don't always upgrade to the next version on day 1 since sometimes there's still issues, but I guess I'll have to go to 84 quicker. Word of advise. Don't knowingly leave things broken for a release version especially when it was recently broken. That's just wrong-headed thinking for a developer in my opinion.

    To clarify, the release of cPanel/WHM v82 did not break ioncube or opcache, this is an upstream issue and unrelated to cPanel entirely. We have no control over the way these modules/extensions function nor do we develop or maintain them. We added the module that is fixed - tested it with the product and that's it. On v84 of cPanel our internal PHP will be using the updated version of ioncube. To clarify further, there will be an EA4 update with ioncube 10.3.9 available but that isn't out yet and I believe we will update it around the same time we send v84 to RELEASE which is more than likely going to be happening this week.
    0
  • cPanelLauren
    Hello, I am sorry for the delay on this but this issue was marked as resolved in the release of cPanel 84.0.4 and is referenced in the changelogs here:
    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post