Jump to content
cyben76

Your environment appears to be running a different PHP version

Recommended Posts

I've just recently updated to PHP 7.3 from 7.2 and I'm getting  the following warning in System Health Status:

 

Cron PHP Version Mismatch
Your environment appears to be running a different PHP version (7.2.23) for the System Cron than the currently loaded PHP version (7.3.11). This may cause issues running your System Cron.

This is the log for the System Health:

 

WHMCS Health Check
================================================================================

error:
 * The system cron does not appear to have completed successfully within the
   last 24 hours. Check your activity logs or learn more about enabling the cron
   in our documentation.

warning:
 * Your environment appears to be running a different PHP version (7.2.23) for
   the System Cron than the currently loaded PHP version (7.3.11). This may
   cause issues running your System Cron.

notice:
 * Your PHP memory_limit value 1024M meets the recommended value of 128M.
 * 
    - Your environment appears to meet the minimum requirements for Automatic
   Updates. To update, you will need to ensure you have at least 250MB of
   available disk space.
   
 * You are running MariaDB version 10.3.20. This version supports all features
   required for full compatibility with WHMCS.
 * A verified SSL certificate was detected for your site.
 * cURL reports that it does support Secure TLS 1.1 and 1.2
 * cURL reports that it does support SSL
 * You currently have version 7.66.0 of cURL installed. This version uses a
   secure cipher list.
 * Your PHP environment uses a valid timezone.
 * PHP session support is enabled.Session autostart is disabled.The PHP session
   save path /var/cpanel/php/sessions/ea-php73/ is writable. 
 * Your PHP installation has all required functions enabled for WHMCS to
   operate.
 * Your permissions are appropriately restrictive.
 * Your PHP installation has all recommended extensions loaded and enabled
   required by certain modules and addons of WHMCS.
 * Your PHP installation has all extensions loaded and enabled required for
   WHMCS to operate.
 * Your system is setup to not log unnecessary error levels.
 * Your system is not currently set to display errors.
 * Your PHP version 7.3.11 is supported by WHMCS. Your PHP version is actively
   supported by PHP for both bug fix and security releases.
 * Your WHMCS installation is using custom templates which will not be
   overwritten on upgrade.
 * You are using custom paths for all the recommended WHMCS directories.
 * Your SMTP settings are using encryption to ensure that sensitive data in
   email cannot be leaked in transit to your mail transport agent.

debug:
 * Here are the paths for customisable directories in your WHMCS installation:
    - Attachments directory: /home/username/attachments
    - Downloads directory: /home/username/downloads
    - Compiled templates directory: /home/username/templates_c
    - Cron directory: /home/username/crons
    - Admin directory: /home/username/public_html/admin_folder
   

All the cron seems to be running when i check the Activity log but I'm missing the daily WHMCS Cron Job Activity email:

 

1519912872_Screenshot2019-11-20at1_59_00PM.png.ea37424bb120c453b322e7172295c733.png

Share this post


Link to post
Share on other sites

Seems like the system cron stops at updating Product Pricing Update,  no errors being logged:

 

WHMCS Automation Task Utility: all
==================================

TSS Cron started
TSS Cron completed Daily Cron Automation Mode

Queuing Tasks
-------------

 Force run any tasks: ignore "in progress" and "is due"
 Task queues ready

Executing Application Queue
---------------------------

  0/30 [░░░░░░░░░░░░░░░░░░░░░░░░░░░░]   0% < 1 sec/< 1 sec 26.0 MiB
 Currency Exchange Rates
  1/30 [░░░░░░░░░░░░░░░░░░░░░░░░░░░░]   3%  1 sec/30 secs 26.0 MiB
 Product Pricing Updates

 

Edited by cyben76

Share this post


Link to post
Share on other sites

Ok solved it, the Product Pricing Update was the cause of it all. Untick it and the cron completed.

1248290401_Screenshot2019-11-21at5_14_33AM.png.ffe3f9079e2c3a07c088ea65d3f76690.png

Share this post


Link to post
Share on other sites
33 minutes ago, cyben76 said:

Ok solved it, the Product Pricing Update was the cause of it all. Untick it and the cron completed.

1248290401_Screenshot2019-11-21at5_14_33AM.png.ffe3f9079e2c3a07c088ea65d3f76690.png

hello ,   where   I can find   that print   on your previous post    Setup>General   Settings ???

Share this post


Link to post
Share on other sites
5 hours ago, zitu4life said:

hello ,   where   I can find   that print   on your previous post    Setup>General   Settings ???

Command line

Share this post


Link to post
Share on other sites
15 hours ago, zitu4life said:

hello ,   where   I can find   that print   on your previous post    Setup>General   Settings ???

Sorry for the late reply, it's under Setup -> Automation Settings if you are implying the Currency Auto Update Settings
 

If you are talking about the WHMCS Automation Task Utility  you'll need to run the cron using Command line

Edited by cyben76

Share this post


Link to post
Share on other sites

Hey Guys,

Update, the PHP version mismatch error I think was caused by cPanel. Previously the cPanel version on the server WHMCS was hosted on was version 84.0.12. The server has since been upgraded to version 84.0.14 and Cron PHP Version Mismatch warning in  System Health Status is no longer seen.

Share this post


Link to post
Share on other sites

it makes more sense. I did not believe since begining that automation currency could cause such issue, that is because I have asked to try to replicated it, because I have faced same issue on my enviroment.

Edited by zitu4life

Share this post


Link to post
Share on other sites

I had the same issue few years back was due to too many products updating, back then my whmcs was hosted on a shared hosting platform and it was hosted on CloudLinux, hosters did not allow increase in resources. It stalled I think because it took up to much memory and execution time was too long. 

It was all solved when i migrated my whmcs to a VPS,  increased memory limit and execution time. Currently i have php memory limit at 512mb execution time 1200, but still stalled. For now i don't really have the need to "Update Product Pricing" so i disabled it and cron works fine, I'll try see if i can find the root cause, but the server is live so i can't really test much. 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Similar Content

    • By j05h
      Hi,
      I have installed & configured the latest version of WHMCS on an installation with PHP 7.3.
      When attempting to order a product, my customers are presented with the attached screen. I've disabled domain registration so I'm not expecting to see a "register domain" field, however since it's a cPanel website hosting package then I believe there should be a "choose existing domain" field, which is failing to display.
      Looking forward to a resolution.
      Cheers,
      Josh

    • By NTsolakos
      Hello! after i install the latest version of WHMCS 7.8.3, when im trying to add a new server on the WHMCS control panel this happen:
      WHMCS\Exception\Validation\InvalidHostAddress in /home/sites/1/agahagha/public_html/vendor/whmcs/whmcs-foundation/lib/Filter/HostAddress.php:0 Stack trace: #0 /home/sites/1/akrjtg/public_html/admin/configservers.php(0): WHMCS\Filter\HostAddress->__construct('', '', '') #1 {main}
      i read somewhere and they say that may be problem the SSL???...
    • By WHMCS John
      An issue has been identified in the 7.8.3 release - published on 23rd September 2019, that prevents payments being processed via payment gateways using transaction references:
      MODULE-7154 - Sagepay Repeats MODULE-7146 - PayPal Pro Reference Payments MODULE -7140 - PayPal Payments Pro with Reference Transactions option enabled CORE-13810 - Prevent Client Area access to Add Payment Method page with only Reference Gateways We have also identified issues with the eWay Rapid module in this version:
      MODULE-7134 - Correctly report the status of declined payments in eWay Rapid MODULE-7132 - Correctly report the status of refunds in eWay Rapid MODULE-7131 - Error "Call to a member function getKey() on null" when adding a pay method via the admin area using eWay Rapid We have also identified an issue with Authorize.net CIM:
      MODULE-7143 - Ensure credit cards can be added/updated when Validation Mode is set to "Live" We have also identified three issues with Stripe:
      MODULE-7151 - Payment descriptor shows "Shopping Cart" when placing a new order via shopping cart MODULE-7141 -  Correct interpolation of merge fields for Stripe Statement Descriptor MODULE-7155 - Invalid Positive Integer error when paying with existing card for an order total of 0.00 We have also identified an issue with 2Checkout:
      MODULE-7144 - 2Checkout deducts promotion code amount twice in Inline mode We have also identified an issue with Accept.js:
      MODULE-7148 - Retain pay profile when updating card expiration date The following generalised issues surrounding Pay Methods have been identified:
      CORE-13838 - Save local expiry date when updating tokenised card details CORE-13851 - Disable admin attempt capture button on Draft invoices CORE-13788 - Trigger CCUpdate hook in all expected scenarios  
      This hotfix applies only to 7.8.3
    • By WHMCS John
      An issue has been identified in the 7.8.3 release - published on 23rd September 2019, that can prevent clients from accessing the client area in certain circumstances. An error message will be logged in the server PHP error logs or an Oops! error output on screen. The error details contain:
      Error: Call to undefined function WHMCS\Payment\PayMethod\run_hook() in /path/to/whmcs/vendor/whmcs/whmcs-foundation/lib/Payment/PayMethod/MigrationProcessor.php This occurs when when there is a client "Remember Me" cookie but no session and pay method data to be migrated.
       
      This hotfix applies only to 7.8.3
    • By WHMCS John
      An issue has been identified in the 7.8.3 release - published on 23rd September 2019, that can result in non-card tokens (such as GoCardless Mandates) being migrated to a remote credit card Pay Method type instead of the expected bank account type.
      This occurs when running v7.7 there is both credit card information and a Mandate token stored for a client, and GoCardless is the only active payment gateway module.
      Upon applying the 7.8 update and performing the Pay Method migration for an impacted client, a remote credit card Pay Method may be created.
       
      This hotfix applies only to 7.8.3
  • Recently Browsing   0 members

    No registered users viewing this page.

×

Important Information

By using this site, you agree to our Terms of Use & Guidelines and understand your posts will initially be pre-moderated