Differences

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

--- litespeed_wiki:cache:litemage:troubleshooting:warmup [2019/06/19 18:12]
Jackson Zhang
+++ litespeed_wiki:cache:litemage:troubleshooting:warmup [2019/06/20 14:51]
Lisa Clarke [Magento system scheduler ''litemage_warmup_cache'' hangs] Copyediting
@@ Line 312: / Line 312: @@
     fi
   fi
-==== Magento system scheduler ''litemage_warmup_cache'' hangs ====
+==== Magento System Scheduler ''litemage_warmup_cache'' Hangs ====
-There is one use case related to Magento system scheduler. The user does see litemage_warmup_cache scheduled but it actually hangs there.
+Sometimes the LiteMage warmup may hang in the Magento system scheduler.
-If you go to Magento Admin -> Scheduler -> Scheduler Timeline, you might see a long cross line for ''litemage_warmup_cache'' either in red or orange color, it actually means the cron hangs instead of running ok.
+If you navigate to **Magento Admin > Scheduler > Scheduler Timeline**, you might see ''litemage_warmup_cache'' highlighted either in red or orange. It means the cron is hanging and is not running propery.
 {{ :litespeed_wiki:cache:litemage:troubleshooting:781630-6-scheduler-stunck.png?800 |}}
-or
 {{ :litespeed_wiki:cache:litemage:troubleshooting:781630-6-scheduler-stunck-2.png?800 |}}
+Navigate to **Magento Admin > System > Scheduler > Job Configuration**, select ''litemage_warmup_cache'' then in the right top corner Actions, select ''Run now'', then press the **Submit** button.
+{{ :litespeed_wiki:cache:litemage:troubleshooting:781630-8-scheduler-runnow.png?800 |}}
+Check the LiteMage cron log, like so:
+  tail -f /home/jsmith/public_html/var/log/litemage_crawler.log
+-05-29T10:14:21+00:00 DEBUG (7): LiteMage [cron:jsmith:1559124843]  Generate url map for store1 url count=5320
+-05-29T10:14:21+00:00 DEBUG (7): LiteMage [cron:jsmith:1559124843]  litemage_runner crawling  store1 urls (cur_pos:0) with cookie
+  litemage_cron=store1; Array
+  LiteMage [cron:jsmith:1559124843]   (
+  LiteMage [cron:jsmith:1559124843]       [0] => https://www.example.com/
+  LiteMage [cron:jsmith:1559124843]       [1] => https://www.example.com/business-office-writing/
+  LiteMage [cron:jsmith:1559124843]       [2] => https://www.example.com/business-office-writing/conference-business/business-card-holders/
+  LiteMage [cron:jsmith:1559124843]       [3] => https://www.example.com/business-office-writing/paper/promotional-calendars-diaries/
+  LiteMage [cron:jsmith:1559124843]       [4] => https://www.example.com/business-office-writing/desk/promotional-calculators/
+  LiteMage [cron:jsmith:1559124843]       [5] => https://www.example.com/business-office-writing/paper/promotional-notebooks/
+  LiteMage [cron:jsmith:1559124843]   )
+  LiteMage [cron:jsmith:1559124843]
+-05-29T10:14:32+00:00 DEBUG (7): LiteMage [cron:jsmith:1559124843]  litemage_runner crawling  store1 urls (cur_pos:6) with cookie
+  litemage_cron=store1; Array
+  LiteMage [cron:jsmith:1559124843]   (
+  LiteMage [cron:jsmith:1559124843]       [0] => https://www.example.com/bags-and-travel/
+  LiteMage [cron:jsmith:1559124843]       [1] => https://www.example.com/clothing-accessories/
+  LiteMage [cron:jsmith:1559124843]       [2] => https://www.example.com/usb-technology/
+  LiteMage [cron:jsmith:1559124843]       [3] => https://www.example.com/food-and-drink/
+  LiteMage [cron:jsmith:1559124843]       [4] => https://www.example.com/health-personal-care/
+  LiteMage [cron:jsmith:1559124843]       [5] => https://www.example.com/bags-and-travel/travel/backpacks/
+  LiteMage [cron:jsmith:1559124843]   )
+These results mean that the warmup did begin to run, so we know it works when started manually. A ''Run now'' action won't fix the Magento system scheduler problem, however, and the initiated cron will be stopped due to exceeding the defined **Maximum Run Time** in the configuration.
+{{ :litespeed_wiki:cache:litemage:troubleshooting:781630-9-litespeed-warmup-stats-stopped-exceeding-defined-max-run-time.png?800 |}}
+Take a look at ''litemage_crawler.log'' and you will see something like the following:
+-06-19T16:17:05+00:00 DEBUG (7): LiteMage [cron:brandin1:1560960721]  Stopped due to exceeding defined Maximum Run Time. cron meta end = Array
+This is normal, since the cron was set to stop at 5 minutes before running again at the next scheduled time. If it had stopped there completely without further running, then there would be some Magento system scheduler issue which would need to be fixed.
+By taking a look at your crontab (assuming your userid is ''jsmith'') we see that you have too many of the same crons set up which may conflict with each other:
+  crontab -u jsmith -e
+  MAILTO=""
+  SHELL="/usr/local/cpanel/bin/jailshell"
+  * * * * * /usr/local/bin/php /home/jsmith/public_html/cron.php
+  SHELL="/usr/local/cpanel/bin/jailshell"
+  * * * * * /usr/local/bin/php /home/jsmith/public_html/cron.sh
+  SHELL="/usr/local/cpanel/bin/jailshell"
+  * * * * * /bin/bash /home/jsmith/public_html/scheduler_cron.sh --mode always
+  SHELL="/usr/local/cpanel/bin/jailshell"
+  * * * * * /bin/bash /home/jsmith/public_html/scheduler_cron.sh --mode default
+  SHELL="/usr/local/cpanel/bin/jailshell"
+  * * * * * /bin/bash /home/jsmith/public_html/cron.sh
+  SHELL="/usr/local/cpanel/bin/jailshell"
+  * * * * * /bin/sh /home/jsmith/public_html/cron.sh
+  * * * * * /bin/sh /home/jsmith/public_html/cron.sh cron.php
+**NOTE**: You may need ''SHELL="/usr/local/cpanel/bin/jailshell"'' on cPanel for jailshell.
+The latest 1.9.x.x version of Magento may prefer to run ''/home/jsmith/public_html/scheduler_cron.sh'' instead of ''/home/jsmith/public_html/cron.sh''. You can find this in **Magento Admin > System > Scheduler > Insctuctions**:
+  Run scheduler_cron.sh instead cron.sh (recommended)
+  Run every minute (recommended)
+  Edit your crontab:
+  sudo crontab -u jsmith -e
+  Add following configuration:
+  * * * * * /bin/bash /home/jsmith/public_html/scheduler_cron.sh --mode always
+  * * * * * /bin/bash /home/jsmith/public_html/scheduler_cron.sh --mode default
+{{ :litespeed_wiki:cache:litemage:troubleshooting:781630-7-scheduler-instruction2.png?600 |
+}}
+Remove all duplicated cron commands and only keep the above two configurations. The issue will be fixed, and ''litemage_crawler.log'' will look ok. The ''litemage_warmup_cache'' cron task will show that it is running in **Scheduler** and **LiteMage Crawler Warm-up Status** will show that it is running ok.
+{{ :litespeed_wiki:cache:litemage:troubleshooting:781630-9-scheduler-litemage_warmup_cache_running.png?800 |}}
+{{ :litespeed_wiki:cache:litemage:troubleshooting:781630-9-litespeed-warmup-stats-running.png?800 |}}
 ===== Warm Up for logged in users =====
 Normally logged in users and non-logged in users will share the same cache copies. However, when you enable **Separate Cache Copy per Customer Group** in LiteMage configuration, LiteMage will have different cache copies.