Body: <p>I have an old drupal civiCRM site (4.7.. i know) that has recently started having issues completing this cron job:</p>
  <p>/sites/all/modules/civicrm/bin/cli.php -s SITEURL -u USER -p &quot;PASSWORD&quot; -e Job -a execute</p>
  <p>They can stack up in the process manager (whm) using a lot of CPU.</p>
  <p>I'm trying to work out what is causing it - I can manually &quot;run all scheduled jobs&quot; within civiCRM seemingly without issue - is my cron running stuff other than the listed jobs too?</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2022-11-17T15:34:36.963Z
Comments.Text: try running that command directly from the command line as the same user as the crontab file and watch it to see if you're getting any errors or it gets stuck somewhere. I'm guessing there is some kind of context issue.
Comments.UserDisplayName: kapn
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2022-11-17T15:41:25.320Z
Comments.Text: What about using cv instead. It's the recommended method in any event and has always worked well for me. https://docs.civicrm.org/sysadmin/en/latest/setup/jobs/#cv
Comments.UserDisplayName: kapn
Tags: <cron><cron-job>
Title: Does this cron command run anything other than scheduled jobs?
ThreadText: # Does this cron command run anything other than scheduled jobs?
  
  (Asked by: username_0 on 2022-11-13)
  
  I have an old drupal civiCRM site (4.7.. i know) that has recently started having issues completing this cron job:
  
  /sites/all/modules/civicrm/bin/cli.php -s SITEURL -u USER -p "PASSWORD" -e Job -a execute
  
  They can stack up in the process manager (whm) using a lot of CPU.
  
  I'm trying to work out what is causing it - I can manually "run all scheduled jobs" within civiCRM seemingly without issue - is my cron running stuff other than the listed jobs too?
  
  **Tags:** cron, cron-job
  
  > **Comments:**
  > **username_1**: try running that command directly from the command line as the same user as the crontab file and watch it to see if you're getting any errors or it gets stuck somewhere. I'm guessing there is some kind of context issue.  
  > **username_1**: What about using cv instead. It's the recommended method in any event and has always worked well for me. https://docs.civicrm.org/sysadmin/en/latest/setup/jobs/#cv  
  
  ---
  
  ## 0 answers
  
  