Jump to content

Recommended Posts

Posted

I have been using Revive Adserver with very good results. I recently updated my servers to Centos 7 (based on Redhat 7). The distro is released with PHP revision 5.4.16! This revision of PHP is not supported by Revive Adserver. We operate a very conservative IT strategy, based on standardized releases. It is unlikely that we can/will upgrade the PHP for the Centos 7 release. This means that we cannot use Revive Adserver anymore!

 

Please note that Centos 7 is a hugely popular distribution, that is soon to be installed as the defaults for many many new servers. I am not sure what the actual issue is, but I know that providing compatibility with the PHP 5.4.16 is important to many future users of Revive Adserver.

 

I would be happy to spend some time in trying to resolve this incompatibility if I could be provided with a starting point - what is the problem with this release of PHP?

 

Please help me fix, or please fix this incompatibility with the Centos 7 chosen release of PHP.

 

Thanks,

Mark

Posted

Hi Mark,

 

thanks for the report. To be honest I wasn't aware of it as my knowledge of RPM-based distros is quite limited. I made a search a while ago and I thought that RHEL/Centos 7 had PHP 5.5 out of the box, which sadly isn't actually true.

 

The fact here is that, even if we wanted to, we can't make Revive Adserver compatible with PHP 5.4.16 as it is affected by a bug that causes segmentation faults when running it. Such bug has been fixed in PHP 5.5.2 and PHP 5.4.20.

 

Debian had the fix backported at some point to their Wheezy (going from memory) php package, but RedHat didn't yet. It would probably take some RH customer to submit a ticket for them to think about backporting the fix.

 

The only suggestion I have (thanks Remi) would be to use PHP 5.5 from RHSCL:

 

https://www.softwarecollections.org/en/scls/rhscl/php55/

 

I hope this helps.

Posted

Thanks for the quick response. I looked at the bug report, and there appears to be a patch available. This, for us anyway, is a better solution that to upgrade to a release of PHP that is not natively supported in the distro.

 

I see in the PHP git that there is a patch for this issue. I will implement the patch, and test, and let you know what happens. This may be a better solution for users that are wary of swapping the PHP revision from Centos 7.

 

Mark

Posted

I have kludged the adserver software to get around the error message based on the PHP revision. Before implementing the patch, I would really like to observe the failure mode. Otherwise, I won't be able to see if the patch actually works.

 

Could you provide me with the scenario that causes the fault? Who knows, perhaps the fix WAS backported, and everything is fine. That is the best solution, but would require for you to refine your PHP environment testing response.

 

Mark

Posted

Thanks Matteo. I really don't want to apply the patches until I can observe the error situation. Does anyone know how I can reliably cause the fault that made the developers of Revive Adserver say that the software is incompatible with 5.4.16. This would be most helpful for other users that will be moving to Centos 7 as the latest release.

  • 1 month later...
Posted

I've been having the same problem today, migrating a Revive 3.1.0 install from an old Centos box to a new one with Centos 7.  Just trying to log into the admin panel (/www/admin/index.php) causes the segfault. I applied the patch that the PHP devs say fixes the issue (https://bugs.php.net/patch-display.php?bug_id=65372&patch=bug65372.patch&revision=latest), both files patched fine. However, I still see the very same segfault.

 

Is it possible there is another issue at play here? Or is there more to the fix than simply the patch?

Posted

Probably not much help, but I bypassed the revision checking in the adserver code, and it works fine for me. I did not patch my PHP or anything else. Since I can't get the error to occur, I can't see what's going on. A seg fault problem with the PHP could probably be worked around in the adserver code. Limiting the operation to specific revisions is a problem if you like to keep your distro basically intact.

 

Good luck!

Posted

@al_bullit Did you apply both the patch files? DId you properly recompile/upgrade your packages and restart the webserver/php-fpm? If so, I'm afraid I don't know what else to suggest.

 

@msellers Whatever works for you. If you're able to fix the adserver and influence garbage collection so that it doesn't trigger the GC bug, I'll be very happy to apply your changes and lift the ban for the PHP versions affected by such bug.

  • 2 weeks later...
  • 2 months later...
Posted

It's possible to upgrade the Cent07 release with php 5.5 and/or php 5.6 without problem. I've done it. Yes, it's true, not on the default package.

but not yet test Revive on that release (trying to understand why i have irrelevant statistics with revive adserver on my system = more clics than display of banners so impossible, when before phpadsnews on the same server was working just fine)

 

New version 5.6.8-1.el7.remi

  • 1 month later...
Posted

Bypassing the revision detecting allows operation, but the seg faults continue. I ended up updating my Centos 7 with PHP 5.4.41 from the webtatic repository. See https://webtatic.com/packages/php54/

 

The upgrade went very well, and the seg faults are no longer a problem. I stuck with the latest 5.4 to minimize to potential impact of moving to later packages. Since 5.4 is nearing EOL status (End of Life), it is probably a good idea to consider updating to 5.6. I haven't done this yet, but probably will later this year.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.



×
×
  • Create New...