Cron Job Issues - Revision history

Lawrence: /* Segmentation fault */

2024-04-16T20:11:09Z

‎Segmentation fault

PeterM at 11:49, 9 April 2024

2024-04-09T11:49:18Z

PeterM: /* Whoops\Exception\ErrorException' with message 'Maximum execution time of 30 seconds exceeded */

2024-04-09T11:48:08Z

‎Whoops\Exception\ErrorException' with message 'Maximum execution time of 30 seconds exceeded

PeterM: /* Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 20480 bytes) */

2024-04-09T11:47:25Z

‎Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 20480 bytes)

AlexN: /* Common Errors */

2024-01-18T11:56:53Z

‎Common Errors

SarahK at 21:15, 8 February 2023

2023-02-08T21:15:31Z

SarahK: /* Common Errors */

2022-08-18T14:06:10Z

‎Common Errors

SarahK at 16:48, 21 April 2022

2022-04-21T16:48:46Z

SarahK at 21:53, 20 January 2022

2022-01-20T21:53:42Z

SarahK at 19:21, 18 January 2022

2022-01-18T19:21:57Z

@@ Line 184: / Line 184: @@
 </source>
-===Segmentation fault===
+===Segmentation Fault===
-This error is not directly related to the WHMCS software and can occur for many different reasons. It most commonly indicates that PHP is crashing and suggests there is an issue with your PHP installation (for example, a malfunctioning extension). It is something your server administrator or hosting provider would need to investigate, possibly using the 'strace' utility.
+This error does not directly relate to the WHMCS software and can occur for many different reasons. It most commonly indicates that PHP is crashing and suggests there is an issue with your PHP installation (for example, a malfunctioning extension). It is something your server administrator or hosting provider would need to investigate, possibly using the <tt>strace</tt> utility.
 ===Domain renew link in emails is broken===

@@ Line 175: / Line 175: @@
 <source lang="php">
 php -d max_execution_time=300 -q /path/to/whmcs/crons/cron.php
 </source>

@@ Line 171: / Line 171: @@
 You can check the limit using this command:
 <source lang="php">php -ini | grep "max_execution_time"</source>
 ===Segmentation fault===

@@ Line 133: / Line 133: @@
 <source lang="php">
 php -ini | grep "memory_limit"
 </source>

@@ Line 180: / Line 180: @@
 cd /path/to/crons/ && php -q cron.php
 </source>
 {{troubleshooting}}

@@ Line 77: / Line 77: @@
 ===Unable to communicate with the WHMCS installation===
-This error occurs when the <tt>cron.php</tt> file is unable to communicate with the WHMCS installation. This typically occurs when you are [[Custom_Crons_Directory|using a custom location]] for the <tt>/crons</tt> directory. The <tt>cron.php</tt> file will look for the WHMCS directory in the location that you specified in the <tt>/crons/config.php</tt> file. To resolve this error:
+This error occurs when the <tt>cron.php</tt> file is unable to communicate with the WHMCS installation. This typically occurs when you are using a custom location for the <tt>/crons</tt> directory. The <tt>cron.php</tt> file will look for the WHMCS directory in the location that you specified in the <tt>/crons/config.php</tt> file. To resolve this error:
 * Open the <tt>/crons/config.php</tt> file.

@@ Line 58: / Line 58: @@
 Seeing this error output indicates that the PHP configuration for your WHMCS installation may be different than the one on the command line.
-Log in as the same user that the cron job runs under. Then, run the following command at the server's command line to see the version information for your PHP and ionCube Loader® configuration:
+Log in as the same user that the cron job runs under. Then, run the following command at the server's command line to see the version information for your PHP and ionCube Loader® configurations:
 <source lang="php">
@@ Line 73: / Line 73: @@
 </source>
-If the "with the ionCube PHP Loader" line is absent, this indicates that the ionCube loaders are not available for this user. Work with your hosting provider or server administrator to ensure that the ionCube loaders are available to the cron job user.
+If the <tt>with the ionCube PHP Loader</tt> line is absent, this indicates that ionCube Loader is not available for this user. Work with your hosting provider or server administrator to ensure that ionCube Loader is available to the cron job user.
 ===Unable to communicate with the WHMCS installation===
@@ Line 137: / Line 137: @@
 ===The file /path/to/crons/cron.php is corrupted===
-You may see this error in version 7.5 and above. This error will occur if you are running ionCube Loader version 10.0 or earlier. WHMCS 7.5 requires ionCube Loaders 10.1.0 or above. If your WHMCS installation is working, it indicates that the PHP configuration for your WHMCS installation may be different than the one that you use on the command line. To check this, you can again use the command below:
+You may see this error in version 7.5 and above. This error will occur if you are running ionCube Loader 10.0 or earlier. WHMCS 7.5 requires ionCube Loader 10.1.0 or above. If your WHMCS installation is working, it indicates that the PHP configuration for your WHMCS installation may be different than the one that you use on the command line. To check this, you can again use the command below:
 <source lang="php">

@@ Line 13: / Line 13: @@
 If you do not receive the daily cron digest email, see a warning on the System Health Status overview page, or on the Automation Status page then this indicates the cron not running. Troubleshooting and resolving this is a matter of priority, as the daily automation tasks are an integral part of WHMCS.
-Detailed steps on how to debug the cron execution can be found in our [https://help.whmcs.com/m/automation/l/683269-advanced-cron-troubleshooting| Advanced Cron Troubleshooting] Guide.
+Detailed steps on how to debug the cron execution can be found in our [https://help.whmcs.com/m/automation/l/683269-advanced-cron-troubleshooting|Advanced Cron Troubleshooting] Guide.
 ===Run the cron job in your browser===
@@ Line 19: / Line 19: @@
 To do this:
-# Log in to the WHMCS admin area and navigate to '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > System Settings > General Settings > Other''' or, prior to WHMCS 8.0, '''Setup > General Settings > Other'''.
+# In the WHMCS admin area, go to the '''[[Other Tab|Other]]''' tab at '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > System Settings > General Settings''' or, prior to WHMCS 8.0, '''Setup > General Settings'''.
 # Enable the '''Display Errors''' option.
 # Visit the <tt>cron.php</tt> file in your browser. For example: <source lang="php">http://www.example.com/whmcs/crons/cron.php</source>
@@ Line 38: / Line 38: @@
 # To execute all daily automation tasks, adjust the cron command again to add in the force option:<source lang="php">php -q /path/to/whmcs/crons/cron.php --force -vvv</source> This should only ever be executed once in any 24 hour period. Do this with the explicit intention of identifying why the cron may not be completing successfully.
-For more information please see [[Crons#Commands|Cron Commands.]]
+For more information, see [[Crons#Commands|Cron Commands.]]
 ===Run the cron job from the server command line with debugging enabled===
@@ Line 44: / Line 44: @@
 To do this:
-* Make sure you have enabled '''Display Errors''' in your admin area from '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > System Settings > General Settings > Other''' or, prior to WHMCS 8.0, '''Setup > General Settings > Other'''.
+* Make sure you have enabled '''Display Errors''' in the '''[[Other Tab|Other]]''' tab at '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > System Settings > General Settings''' or, prior to WHMCS 8.0, '''Setup > General Settings'''.
 * Access your server's command line.
 * Make sure you have enabled '''display_errors''' in your command line PHP environment: <source lang="php">php -i | grep display_errors
@@ Line 115: / Line 115: @@
 ===Oops! Something went wrong and we couldn't process your request===
-This indicates that a fatal PHP error has occurred. Navigate to '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > System Settings > General Settings > Other''' or, prior to WHMCS 8.0, '''Setup > General Settings > Other'''. Select 'Display Errors'. Then, run the cron job again. The system will display the full error. The error normally indicates an issue with one or more modules.
+This indicates that a fatal PHP error has occurred. Go to the '''[[Other Tab|Other]]''' tab at '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > System Settings > General Settings''' or, prior to WHMCS 8.0, '''Setup > General Settings'''. Select 'Display Errors'. Then, run the cron job again. The system will display the full error. The error normally indicates an issue with one or more modules.
 For example, you could see:

@@ Line 2: / Line 2: @@
 You may encounter some common problems and errors that can occur when running the WHMCS cron job.
 ==Troubleshooting==
-There are several techniques available for troubleshooting the problems that you may encounter with the cron job. In descending order of verbosity, they are:
+There are several techniques available for troubleshooting the problems that you may encounter with the cron job:
 ===Run the cron job in your browser===