Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
litespeed_wiki:cache:litemage:troubleshooting:warmup [2019/06/20 14:51] Lisa Clarke [Magento system scheduler ''litemage_warmup_cache'' hangs] Copyediting |
litespeed_wiki:cache:litemage:troubleshooting:warmup [2019/06/25 19:54] Jackson Zhang [Magento System Scheduler ''litemage_warmup_cache'' Hangs] |
||
|---|---|---|---|
| Line 312: | Line 312: | ||
| fi | fi | ||
| fi | fi | ||
| - | ==== Magento System Scheduler ''litemage_warmup_cache'' Hangs ==== | + | ==== Magento AOE Scheduler doesn't mark completion of ''litemage_warmup_cache''==== |
| - | Sometimes the LiteMage warmup may hang in the Magento system scheduler. | + | [[https://github.com/AOEpeople/Aoe_Scheduler|Magento AOE Scheduler extension]] sits on top of Magento's default cron functionality allowing the users to manage the jobs and visualize the timeline. |
| + | |||
| + | LiteMage works with AOE scheduler most of the time. However, occasionally, Magento AOE scheduler sometimes believers the LiteMage warmup process is always running while it has stopped by the max execution time hence AOE scheduler doesn't start next ''litemage_warmup_cache'' at all. | ||
| 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. | 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. | ||
| Line 391: | Line 393: | ||
| }} | }} | ||
| - | 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. | + | Remove all duplicated cron commands and only keep the above two configurations. {{ :litespeed_wiki:cache:litemage:troubleshooting:781630-9-scheduler-litemage_warmup_cache_running.png?800 |}} |
| - | + | ||
| - | {{ :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 |}} | {{ :litespeed_wiki:cache:litemage:troubleshooting:781630-9-litespeed-warmup-stats-running.png?800 |}} | ||
| + | |||
| + | {{ :litespeed_wiki:cache:litemage:troubleshooting:781630-10-aoe-scheduler-stop-litemage_warmup_cache-3-highlight.png?|800}} | ||
| + | |||
| + | The above-scheduled tasks view show the AOE scheduler's problem. ''litemage_warmup_cache'' was scheduled for 17:02 and run for 5 mins. However, AOE scheduler did not mark the task as "completed" at 17:07 and treats it running all the time. Then 17:12, 17:22, 12:32 etc scheduled ''litemage_warmup_cache'' never run due to the incorrect status issue for 17:02 's job. It may need your Magento developer or AOE developer to fix such issue to make ''litemage_warmup_cache'' run without any problem until the completion. | ||
| ===== Warm Up for logged in users ===== | ===== 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. | 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. | ||