Answers.Body: <p>It seems to be an issue with running php bin/cli.php. Can you try using wp-cli instead?</p>
  
  <pre><code>/path/to/wp --user=&lt;cron&gt; --url=&lt;http://example.com&gt; --path=&lt;/path/to/wp&gt; civicrm api job.execute auth=0
  </code></pre>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-02-16T10:40:13.747Z
Answers.LastActivityDate: 2016-02-16T10:40:13.747Z
Answers.UserDisplayName: Xavier
Answers.Body: <p>I noticed on all my sites that I upgraded, it also initially had an error that cron was not running.  But after the first automatic cron run triggered by my host cron job, this went away.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-02-09T15:50:07.063Z
Answers.Text: How are you triggering cron?  PHP call, cURL, wget, wp-cli?
Answers.UserDisplayName: G H
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-02-10T17:21:56.507Z
Answers.Text: PHP to call cli.php
  
  /usr/bin/php5 /home/xxxxxx/public_html/sites/all/modules/civicrm/bin/cli.php -u username -p password -e Job -a execute
Answers.UserDisplayName: Friendswood Tech
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-02-10T19:10:56.080Z
Answers.Text: So, you are using Drupal.  From what I've seen, this seems to be an issue with something being parsed in wp-content/plugins/civicrm/civicrm/CRM/Utils/System/WordPress.php and therefore is irrelevant to Drupal.  Sounds like Drupal might have a separate issue.
Answers.UserDisplayName: G H
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-03-02T13:34:32.360Z
Answers.Text: This is also happening in Joomla 3.4.8. Cronjob is running continuously without any errors in /var/log/cron
Answers.UserDisplayName: BruceW
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-03-02T13:43:52.000Z
Answers.Text: Using CLI, too:    nice -n19 /usr/bin/php-cli /home/account/public_html/administrator/components/com_civicrm/civicrm/bin/cli.php -j -s <site> -u <user> -p <password> -e Job -a execute >/dev/null 2>&1
Answers.UserDisplayName: BruceW
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-04-01T23:33:23.647Z
Answers.Text: It appears that cli.php is completely broken now. With an alternative, I find that wp-cli reports that the process-mail-queue command is successful, but no bulk emails are sent out. Go figure.
Answers.UserDisplayName: P a u l
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-02-09T00:58:59.467Z
Answers.LastActivityDate: 2016-02-09T00:58:59.467Z
Answers.UserDisplayName: Friendswood Tech
Answers.Body: <p>I reviewed the Civi instructions on cron. I performed an adjustment of the permissions of ../civicrm/bin/cli.php from 0754 to 0755 and the error message disappeared.</p>
  
  <p>See <a href="https://wiki.civicrm.org/confluence/display/CRMDOC/Managing+Scheduled+Jobs" rel="nofollow">Wrong permissions for cli.php</a></p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-03-02T14:31:06.867Z
Answers.Text: Unfortunately, despite the cronjob running and the error not appearing anymore, the scheduled jobs are not being fired either. When I try to send a bulk mailing, nothing happens even though the cronjob scrolls through /var/log/cron and no errors reported in any other log files. Bump!
Answers.UserDisplayName: BruceW
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-03-02T13:50:37.830Z
Answers.LastActivityDate: 2016-03-02T13:50:37.830Z
Answers.UserDisplayName: BruceW
Answers.Body: <p>Hrm ... That's very interesting.  I'm fighting the same error, though it is persisting far beyond the first run.  On mine it seems like it's failing to render the WP_Error correctly.  I thought it was a third party plugin, but I'm beginning to feel like it is deeper.  Perhaps related to the removal of the "htmlize" class?  Here's a bug I've opened.  <a href="https://issues.civicrm.org/jira/browse/CRM-17981" rel="nofollow">https://issues.civicrm.org/jira/browse/CRM-17981</a></p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-02-09T15:48:04.627Z
Answers.LastActivityDate: 2016-02-09T17:19:55.610Z
Answers.LastEditDate: 2016-02-09T17:19:55.610Z
Answers.UserDisplayName: G H
Body: <p>The detail is:
  "No cron runs have been recorded."</p>
  
  <p>Just updated from 4.6.10. This has never been a problem with other updates. What do I have to do to fix this? We need cron to send mailings as I recall.</p>
  
  <p>Edit: <strong>There are a lot of errors including "cron not running" on the civicrm wordpress demo site so it's not just me.</strong> I think something needs a tidy.
  Another error on the demo site:
  "Failed to make directory (extensionsDir) at "/srv/buildkit/build/wpmaster/wp-content/uploads/civicrm/ext/". Please update the settings or file permissions."</p>
  
Tags: <wordpress><upgrade><4.7>
Title: "Cron Not Running" system error after update to 4.7.1
ThreadText: # "Cron Not Running" system error after update to 4.7.1
  
  (Asked by: username_0 on 2016-02-08)
  
  The detail is:
  "No cron runs have been recorded."
  
  Just updated from 4.6.10. This has never been a problem with other updates. What do I have to do to fix this? We need cron to send mailings as I recall.
  
  Edit: **There are a lot of errors including "cron not running" on the civicrm wordpress demo site so it's not just me.** I think something needs a tidy.
  Another error on the demo site:
  "Failed to make directory (extensionsDir) at "/srv/buildkit/build/wpmaster/wp-content/uploads/civicrm/ext/". Please update the settings or file permissions."
  
  **Tags:** wordpress, upgrade, 4.7
  
  
  ---
  
  ## 4 answers
  
  ### Answer by username_1 on 2016-02-16. Score: 2
  
  It seems to be an issue with running php bin/cli.php. Can you try using wp-cli instead?
  
  ```
  /path/to/wp --user=<cron> --url=<http://example.com> --path=</path/to/wp> civicrm api job.execute auth=0
  
  ```
  
  
  ---
  
  ### Answer by username_2 on 2016-02-09. Score: 2
  
  I noticed on all my sites that I upgraded, it also initially had an error that cron was not running. But after the first automatic cron run triggered by my host cron job, this went away.
  
  > **Comments:**
  > **username_3**: How are you triggering cron?  PHP call, cURL, wget, wp-cli?  
  > **username_2**: PHP to call cli.php  /usr/bin/php5 /home/xxxxxx/public_html/sites/all/modules/civicrm/bin/cli.php -u username -p password -e Job -a execute  
  > **username_3**: So, you are using Drupal.  From what I've seen, this seems to be an issue with something being parsed in wp-content/plugins/civicrm/civicrm/CRM/Utils/System/WordPress.php and therefore is irrelevant to Drupal.  Sounds like Drupal might have a separate issue.  
  > **username_4**: This is also happening in Joomla 3.4.8. Cronjob is running continuously without any errors in /var/log/cron  
  > **username_4**: Using CLI, too:    nice -n19 /usr/bin/php-cli /home/account/public_html/administrator/components/com_civicrm/civicrm/bin/cli.php -j -s <site> -u <user> -p <password> -e Job -a execute >/dev/null 2>&1  
  > **username_0**: It appears that cli.php is completely broken now. With an alternative, I find that wp-cli reports that the process-mail-queue command is successful, but no bulk emails are sent out. Go figure.  
  
  ---
  
  ### Answer by username_4 on 2016-03-02. Score: 0
  
  I reviewed the Civi instructions on cron. I performed an adjustment of the permissions of ../civicrm/bin/cli.php from 0754 to 0755 and the error message disappeared.
  
  See [Wrong permissions for cli.php](https://wiki.civicrm.org/confluence/display/CRMDOC/Managing+Scheduled+Jobs)
  
  > **Comments:**
  > **username_4**: Unfortunately, despite the cronjob running and the error not appearing anymore, the scheduled jobs are not being fired either. When I try to send a bulk mailing, nothing happens even though the cronjob scrolls through /var/log/cron and no errors reported in any other log files. Bump!  
  
  ---
  
  ### Answer by username_3 on 2016-02-09. Score: 0
  
  Hrm ... That's very interesting. I'm fighting the same error, though it is persisting far beyond the first run. On mine it seems like it's failing to render the WP\_Error correctly. I thought it was a third party plugin, but I'm beginning to feel like it is deeper. Perhaps related to the removal of the "htmlize" class? Here's a bug I've opened. <https://issues.civicrm.org/jira/browse/CRM-17981>
  
  
  ---
  
  