To disable triggering cron by page visits, adjust the value of Run cron on visitor's requests, every at /admin/config/system/cron/settings: Note: This will disable all cron jobs, including those handled by Elysia Cron and those invoked via Drush. Select Never from the "Run cron every" drop-down menu.ĭrupal sites using the Elysia Cron contrib module to extend the standard cron can disable it globally in the module's settings: Navigate to Configuration > System > Cron within the admin interface. This configuration disables cron execution in Drupal, but it does not affect Pantheon's cron execution at the platform level which runs every hour on all environments. The unique URL to kick off cron externally can be found at /admin/config/system/cron. You can set custom schedules, notifications, and logging through their web interface or through their Eas圜ron Module. If you have an external server executing cron tasks, you can invoke Drush commands remotely using Terminus, including Drush cron, to trigger scheduled operations.Īnother very effective solution is to leverage a service such as Eas圜ron. One advantage of this approach is that your site may already have a New Relic instance associated with it, saving you from having to setup another third-party service. You may still want to use Elysia Cron or Ultimate Cron to schedule different cron tasks at different frequencies though. This combination is not officially supported by Pantheon, but has worked for some of our customers.Ī single-part solution is to set up New Relic's Synthetics Ping Monitoring to hit Cron URLs. In conjunction, the use of Drupal modules like Elysia Cron or Ultimate Cron allows for granular control over cron scheduling and execution with both a user interface and API.īy having Pingdom visit the site once a minute like a visitor, the site stays active and the Cron module has an opportunity to act every minute (if it needs to). To keep the site active, some users have used Pingdom to automate access to their site as often as once a minute. Most work by keeping the site awake, then using a different mechanism for executing cron tasks. If the site has not been accessed through the web by a visitor for at least two hours, the platform suspends the associated services until it's accessed again and cron will not run. While Pantheon doesn't provide a mechanism for custom scheduling of cron tasks, the platform will automatically execute drush pantheon_cron 3600 once an hour, usually within 5 to 10 minutes of half past each hour (4:30pm, 5:30pm, 6:30pm, etc). You can also filter the log to only show cron entries: If cron has run recently, entries will appear in the log. To ensure that cron tasks have been run, check the reports via the Drupal Admin interface at Reports > Recent log messages.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |