Answers.Body: <p>Our host helped resolve the issue. The cron job was failing silently by timing out. We had to lower the amount of emails triggered per run and updated the cron to have a longer period before timing out. Our host also increased the number of resources available for running cron jobs.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2022-02-08T19:47:35.937Z
Answers.LastActivityDate: 2022-02-08T19:47:35.937Z
Answers.UserDisplayName: LMK Web
Body: <p>We upgraded to CiviCRM 5.45.2 on Joomla 3.10.5 and everything was working fine until we attempted to send a mailing to about 1000 recipients. The cron job started failing silently after that, with no notification to us or a visible notification in the dashboard. I contacted our host and they are seeing a 500 error in the Apache access log, but no corresponding entry in the Apache error log, so they said it is coming from either Civi or Joomla.</p>
  <p>Example error below:</p>
  <pre><code>192.xxx.xxx.xx - - [31/Jan/2022:13:58:35 -0500] &quot;GET /administrator/components/com_civicrm/civicrm/bin/cron.php?name=[redacted]&amp;pass=[redacted] HTTP/1.1&quot; 200 5628 &quot;-&quot; &quot;lwp-request/6.36 libwww-perl/6.36&quot; 0 0 &quot;on:TLSv1.3:TLS_AES_256_GCM_SHA384&quot; 895 3404768 192.252.151.10 www.[redacted].com proxy:unix:/home/[redacted]/.config/php-fpm/.sockets/php-fpm-ZrxRl01wU0Jb5N0KjTcmWLbh8.sock|fcgi://ZrxRl01wU0Jb5N0KjTcmWLbh8 - 192.xxx.xxx.xx
  </code></pre>
  <p>We've never had a similar issue prior to the upgrade, and the only error notices I received were about updating system templates. Has anyone seen a similar issue?</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2022-02-07T13:25:27.137Z
Comments.Text: Can you send the mailing using 'Execute now' on the scheduled job? That would help figure out whether it is the cron side of things failing, or the mail sending.
Comments.UserDisplayName: Aidan
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2022-02-08T18:57:41.363Z
Comments.Text: I did try that and it did not work - but I did get a resolution from our host so I'll post that.
Comments.UserDisplayName: LMK Web
Tags: <joomla><upgrade><cron-job>
Title: Cron job failing silently after update to 5.45.2
ThreadText: # Cron job failing silently after update to 5.45.2
  
  (Asked by: username_0 on 2022-01-31)
  
  We upgraded to CiviCRM 5.45.2 on Joomla 3.10.5 and everything was working fine until we attempted to send a mailing to about 1000 recipients. The cron job started failing silently after that, with no notification to us or a visible notification in the dashboard. I contacted our host and they are seeing a 500 error in the Apache access log, but no corresponding entry in the Apache error log, so they said it is coming from either Civi or Joomla.
  Example error below:
  192.xxx.xxx.xx - - [31/Jan/2022:13:58:35 -0500] "GET /administrator/components/com_civicrm/civicrm/bin/cron.php?name=[redacted]&pass=[redacted] HTTP/1.1" 200 5628 "-" "lwp-request/6.36 libwww-perl/6.36" 0 0 "on:TLSv1.3:TLS_AES_256_GCM_SHA384" 895 3404768 192.252.151.10 www.[redacted].com proxy:unix:/home/[redacted]/.config/php-fpm/.sockets/php-fpm-ZrxRl01wU0Jb5N0KjTcmWLbh8.sock|fcgi://ZrxRl01wU0Jb5N0KjTcmWLbh8 - 192.xxx.xxx.xx
  
  We've never had a similar issue prior to the upgrade, and the only error notices I received were about updating system templates. Has anyone seen a similar issue?
  
  **Tags:** joomla, upgrade, cron-job
  
  > **Comments:**
  > **username_1**: Can you send the mailing using 'Execute now' on the scheduled job? That would help figure out whether it is the cron side of things failing, or the mail sending.  
  > **username_0**: I did try that and it did not work - but I did get a resolution from our host so I'll post that.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_0 on 2022-02-08. Score: 1 | Accepted answer
  
  Our host helped resolve the issue. The cron job was failing silently by timing out. We had to lower the amount of emails triggered per run and updated the cron to have a longer period before timing out. Our host also increased the number of resources available for running cron jobs.
  
  
  ---
  
  