Differences

This shows you the differences between two versions of the page.

--- admin_menu:site_setup:cron_jobs:start [2009/05/31 20:29]
jonyo Removed reference to # of cron tasks as the number keeps going up.
+++ admin_menu:site_setup:cron_jobs:start [2014/09/25 16:55] (current)
@@ Line 1: / Line 1: @@
 {{indexmenu_n>80}}
 ====== Cron Jobs ======
+Admin Page: **Site Setup > Cron Jobs**
 In the admin panel, it gives the warning:
 <html><span style="color: red;"><strong>Warning:</strong> Changing settings on this page can have drastic effects if your server is not configured correctly. It is important that you <strong>consult the user manual</strong>, so that you may fully understand what is happening, before changing any settings on this page.</span></html>
-The **reason for the strong warning** is so you come to this page to learn what is needed to change certain settings on the page, specifically what you need to do before switching to //Option B//.  Don't let the warning scare you too much though, if you are familiar with setting up cron tasks for your hosting (or your hosting has good instructions for doing so), you should be fine with setting up the basic heartbeat to run once a minute, just use the example listed in your admin panel for doing so.  The main thing, is after you have set it up to use a manual cron task, after about a week or so, be sure to come back to the cron tasks page and look at the //Last Run// time for each of the cron tasks.  If none of them have been run recently you will need to double check to make sure you have it all set up correctly, or just switch it back to doing //Option A//.  It is a good idea to come back to the page periodically just to make sure everything is still running smoothly.
+The **reason for the strong warning** is so you come to this page to learn what is needed to change certain settings on the page, specifically what you need to do before switching to //Option B//.  Don't let the warning scare you too much though, if you are familiar with setting up cron tasks for your hosting (or your hosting has good instructions for doing so), you should be fine with setting up the basic heartbeat to run once a minute, just use the [[#Manually Run Heartbeat every minute]] example listed in your admin panel for doing so.  The main thing, is after you have set it up to use a manual cron task, after about a week or so, be sure to come back to the cron tasks page and look at the //Last Run// time for each of the cron tasks.  If none of them have been run recently you will need to double check to make sure you have it all set up correctly, or just switch it back to doing //Option A//.  It is a good idea to come back to the page periodically just to make sure everything is still running smoothly.
 ===== How cron tasks work...what a cron task is: =====
@@ Line 58: / Line 60: @@
 This section gives examples of cron jobs you may set up, with the site URL and cron key set to match your site.
-"Manually Run Heartbeat every minute":  This is an example of how you would use a cron job to call the heartbeat task, instead of loading the heartbeat task automatically on each page load.  If your server does not have the command line browser "lynx", you must substitute whatever command line browser your server does have.
+==== Manually Run Heartbeat every minute ====
+This is an example of how you would use a cron job to call the heartbeat task, instead of loading the heartbeat task automatically on each page load.  If your server does not have the command line browser "lynx", you must substitute whatever command line browser your server does have.  For example you might substitute "lynx" with "wget" or something similar.
+==== Run the made-up tasks task1 and task2 every Monday at 1AM ====
+This is an example of how to set it up to manually run certain tasks using a cron job, instead of relying on the heartbeat to run the tasks needed.  In the example, it uses **task1** and **task2**, which are **not real task names**, this is just an example.  The [[#Manually Run Heartbeat every minute|first example]] of running the heartbeat would actually work on servers that have lynx, where this example would do nothing since the tasks are not real.
+==== SSH Command Line Options ====
+Using "command line php" to run cron tasks:  In the first 2 examples, using lynx in the cron job will work as long as lynx is installed on your server, or if your server has another command line browser that can be used instead.
+If your server does not have a command line browser, it is also set up to be called using PHP to run it directly on the command line, however this is not guaranteed to work since server configurations can vary widely.  If you wish to test using PHP instead of lynx, wget, or another method, using SSH try the following command:
+  php /path/to/cron.php --help
+Replace "**/path/to/cron.php**" with the absolute path to the file cron.php on your server, which will be listed in your admin.  This will display information on how to use cron.php to be run on the command line, without using a browser.
-"Run the made-up tasks task1 and task2 every Monday at 1AM":  This is an example of how to set it up to manually run certain tasks using a cron job, instead of relying on the heartbeat to run the tasks needed.  In the example, it uses task1 and task2, which are not real task names, this is just an example.  The first example of running the heartbeat would actually work on servers that have lynx, where this example would do nothing since the tasks are not real.
+=====Are My Cron Routines Running?=====
-"SSH Command Line Options"
+To verify if a cron has been run correctly or not, in the admin to go to the following admin tool:
-Using "php" to run cron tasks:  In the first 2 examples, using lynx in the cron job will work as long as lynx is installed on your server, or if your server has another command line browser that can be used instead.
+  SITE SETUP > CRON JOBS
-If your server does not have a command line browser, it is also set up to be called using php to run it directly on the command line, however this is not guaranteed to work since server configurations can vary widely.  If you wish to test using PHP instead of lynx or another browser, using SSH try the following command:
+and look at the times for "last run" on the cron jobs.  Make sure that all the cron jobs listed have been run recently.  Note that how recently they run will depend on how often each cron job is set to run.
-php /path/to/cron.php --help
-Replace "/path/to/cron.php" with the absolute path to the file cron.php on your server.  This will display information on how to use cron.php to be run on the command line, without using a browser.

Geodesic Solutions Community Wiki

User Tools

Site Tools

Differences

Page Tools