Skip to main content

"There was an error while checking the available PHP versions."

DragonByte Tech
So after updating to the latest cPanel and running EasyApache, I receive the following screen: [quote]There was an error while checking the available PHP versions. Please make sure your PHP 5 binary is working correctly, and try again. More information may be available in the error log. The specific error encountered was: PHP process exited nonzero (0). Unexpected output from /usr/bin/php -v :
.vB Here is the output of /usr/bin/php -v [quote][root@server2 ~]# php -v PHP 5.4.21 (cli) (built: Nov 7 2013 12:44:07) Copyright (c) 1997-2013 The PHP Group Zend Engine v2.4.0, Copyright (c) 1998-2013 Zend Technologies
Any ideas? I don't know what error log it's referring to, otherwise I would have checked it.

Comments

11 comments

Date Votes
  • 24x7server
    Hello, As per the provided logs and screen shot there is an issues with the php because php version is appears in WHM, You will have to check last easyapache logs and try to run easyapche again on your server Thank you.
    0
  • DragonByte Tech
    I cannot find any errors in that log file:
    0
  • cPanelMichael
    Hello :) It's possible there are some invalid entries in your /usr/local/lib/php.ini file. Please try moving that file out of the way and regenerating it via: mv /usr/local/lib/php.ini /usr/local/lib/php.ini.backup1 /scripts/phpini
    Does this resolve the issue? If so, you should run EasyApache again after generating a new php.ini file to ensure all of the modules are loaded properly. You can then make any additional customizations to the php.ini file one by one to see which custom entry is the cause of the problem. Thank you.
    0
  • DragonByte Tech
    Re: "There was an error while checking the available PHP versions." As soon as I install APC (either via the Module Installers page or via pecl install apc) this issue appears. [COLOR="silver">- - - Updated - - - Update: It actually happens with any PECL extension (also tested GeoIP).
    0
  • DragonByte Tech
    Update 2: I ran EasyApache with APC and GeoIP still installed, and this caused the same issue to re-appear. For the record, it was fixed after resetting the php.ini configuration, but it seems that adding any form of extension to php.ini will cause the above error message to appear. The site itself works perfectly fine with the extensions enabled.
    0
  • cPanelMichael
    Please open a support ticket so we can take a closer look: Submit A Ticket You can post the ticket number here so we can update this thread with the outcome. Thank you.
    0
  • DragonByte Tech
    Done - #4389347 Thanks :)
    0
  • DragonByte Tech
    Update: It appears that I was incorrect in my previous assessment, it was only APC that was misbehaving. I installed XCache instead, and that works with no issues. Thanks :)
    0
  • WebEndev
    [quote="DragonByte Tech, post: 1500492">Update: It appears that I was incorrect in my previous assessment, it was only APC that was misbehaving. I installed XCache instead, and that works with no issues. Thanks :)
    I have the exact same issue. Isn't there something that can be changed in the APC configuration to remedy this? I really prefer APC over XCache. Any help is greatly appreciated!
    0
  • WebEndev
    I believe that I have resolved this. I lowered my apc.shm_size in APC. After hunting around a while, I had read that if apc.shm_size was too large in relation to your total system RAM available, that segmentation faults may occur (which I had). So I lowered it from 512M to 400M, and the error is now gone. I will continue to monitor my APC memory usage and verify that the error stays gone. Hope this helps someone.
    0
  • racerx8413
    [quote="WebEndev, post: 1506491">I believe that I have resolved this. I lowered my apc.shm_size in APC. After hunting around a while, I had read that if apc.shm_size was too large in relation to your total system RAM available, that segmentation faults may occur (which I had). So I lowered it from 512M to 400M, and the error is now gone. I will continue to monitor my APC memory usage and verify that the error stays gone. Hope this helps someone.
    This has also resolved my issue - APC was previously set to 512. Reducing it removed the error, but the max i could go was 196M. You guys know of any guideline, or what a good ratio might be? I've got a cron to clear apc cache once an hour, and am worried i might use up more than what's available.
    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post