Answers.Body: <p>I was able to reproduce a similar symptom in a <a href="https://github.com/civicrm/civicrm-buildkit/tree/master/app/config/wp-demo" rel="nofollow noreferrer">wp-demo configuration</a>. Specifically, the upgrader activates the new, core-internal extension (<code>sequentialcreditnotes</code>), and the activation fired off a general system-flush, and the general system-flush raised an error while handling some data from another extension (<code>civivolunteer</code>). The problem only occurred with the web-based upgrade UI (and not with the CLI-based upgrader).</p>
  
  <p><a href="https://download.civicrm.org/about/5.24.1" rel="nofollow noreferrer">CiviCRM 5.24.1</a> has a fix for that case.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-04-05T04:33:42.813Z
Answers.LastActivityDate: 2020-04-05T04:33:42.813Z
Answers.UserDisplayName: Tim Otten
Answers.Body: <p>On WordPress version, tried to upgrade from 5.21.2 to 5.24.0 twice and had the same issue. Freezes on: Executed: Upgrade DB to 5.24.alpha1: SQL Had to restore previous day's back up to bring database back. No error messages, just the freezing.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-04-03T22:33:16.303Z
Answers.Text: I was able to reproduce this problem. The following fixed it for me: https://github.com/civicrm/civicrm-core/pull/16971
Answers.UserDisplayName: Tim Otten
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-04-04T14:39:27.173Z
Answers.Text: I saw the same under Joomla.  My test Joomla instance ran to completion, but the CiviCRM menu disappeared!
Answers.UserDisplayName: Stephen Palmstrom
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-04-04T21:07:03.357Z
Answers.Text: Glad you found a fix, Tim and thanks for letting us know . I'm surprised this didn't occur  in testing as it was such a solid error.
Answers.UserDisplayName: Andy Clark
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-04-03T10:51:12.473Z
Answers.LastActivityDate: 2020-04-03T10:51:12.473Z
Answers.UserDisplayName: Oli P
Body: <p>I tried upgrading to 5.24 and it hung half way through the upgrade - while upgrading to 5.24alpha1.  Here's all that was in the log - it then died. I've gone back to 5.23.4 (Drupal).  Ideas?
  <p>
  Apr 02 09:21:30  [info] Running task: Cleanup old files
  <br>
  Apr 02 09:21:31  [info] Running task: Checking extensions
  <br>
  Apr 02 09:21:31  [info] Running task: Begin Upgrade to 5.24.alpha1
  <br>
  Apr 02 09:21:32  [info] Running task: Upgrade DB to 5.24.alpha1
  <br>
  Apr 02 09:21:33  [info] Running task: Upgrade DB to 5.24.alpha1: SQL
  <br>
  Apr 02 09:21:34  [info] Running task: Install sequential creditnote extension</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2020-04-02T09:04:24.673Z
Comments.Text: Did it succeed in installing that extension?  Are there any errors in webserver logs, or CMS logs?
Comments.UserDisplayName: Aidan
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2020-04-02T09:11:57.090Z
Comments.Text: I restored the database, which is shared with Drupal, so the only thing I have is the above log.  I'll retry the upgrade and look further
Comments.UserDisplayName: Andy Clark
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2020-04-02T13:07:32.557Z
Comments.Text: I ran the upgrade again, nothing in civicrm_log or Drupal's log, nothing more in ConfigAndLog, and no extension installed. I can try again with some diagnostics.  Also I do have a lot of extensions, I could do some gradual disabling.  This is a test system, by the way!
Comments.UserDisplayName: Andy Clark
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2020-04-02T15:18:16.850Z
Comments.Text: Ok, since it's a test system would be interesting to try installing that extension manually after the upgrade has failed and see if you get more error messages that way.
Comments.UserDisplayName: Aidan
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2020-04-02T23:26:10.917Z
Comments.Text: (a) +1 for disabling some other ext's as debug tactic. (b) You might get better debug info with one of these patches: https://gist.github.com/totten/96aa7172faced3fde2225e145307f3b9 (c) You might also get more debug info with a CLI runner (eg `cv upgrade:db -vvv`).
Comments.UserDisplayName: Tim Otten
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2020-04-03T06:43:05.573Z
Comments.Text: I had a similar experience on Wordpress 5.4. I cleared cache and used the "Upgrade CiviCRM" option in Christian Wach's CiviCRM Admin Utilities plugin for Wordpress, which is my typical routine. My upgrade also stalled at the same spot that Andy showed. At the time, I didn't think to check on the status of the creditnote extension. I restored my database (mine is separate from Wordpress) and tried again with "cv -vvv upgrade:db". It upgraded with no complaints.
Comments.UserDisplayName: Mark Westergaard
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2020-04-03T08:04:53.013Z
Comments.Text: I don't do command line stuff (I'm strictly an implementer) so tried installing Tim's patches manually but failed. The creditnote extension can only be installed via the command line, it seems, so Aidan's suggestion is out. Since Mark also hit the same problem it doesn't sound like disabling extensions will fix. Any other ideas?
Comments.UserDisplayName: Andy Clark
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2020-04-03T21:26:01.200Z
Comments.Text: I uninstalled all extensions and tried again.  It stopped at the same place (5.24aplha1) for a bit, then continued and installed OK, and I now have the sequential creditnote extension installed. There were over 20 extensions disabled so no idea which was the culprit. Is see that three of us have had this upgrade fail now..
Comments.UserDisplayName: Andy Clark
Tags: <upgrade>
Title: Upgrade to 5.24 failed
ThreadText: # Upgrade to 5.24 failed
  
  (Asked by: username_0 on 2020-04-02)
  
  I tried upgrading to 5.24 and it hung half way through the upgrade - while upgrading to 5.24alpha1. Here's all that was in the log - it then died. I've gone back to 5.23.4 (Drupal). Ideas?
  
  Apr 02 09:21:30 [info] Running task: Cleanup old files
    
  Apr 02 09:21:31 [info] Running task: Checking extensions
    
  Apr 02 09:21:31 [info] Running task: Begin Upgrade to 5.24.alpha1
    
  Apr 02 09:21:32 [info] Running task: Upgrade DB to 5.24.alpha1
    
  Apr 02 09:21:33 [info] Running task: Upgrade DB to 5.24.alpha1: SQL
    
  Apr 02 09:21:34 [info] Running task: Install sequential creditnote extension
  
  **Tags:** upgrade
  
  > **Comments:**
  > **username_1**: Did it succeed in installing that extension?  Are there any errors in webserver logs, or CMS logs?  
  > **username_0**: I restored the database, which is shared with Drupal, so the only thing I have is the above log.  I'll retry the upgrade and look further  
  > **username_0**: I ran the upgrade again, nothing in civicrm_log or Drupal's log, nothing more in ConfigAndLog, and no extension installed. I can try again with some diagnostics.  Also I do have a lot of extensions, I could do some gradual disabling.  This is a test system, by the way!  
  > **username_1**: Ok, since it's a test system would be interesting to try installing that extension manually after the upgrade has failed and see if you get more error messages that way.  
  > **username_2**: (a) +1 for disabling some other ext's as debug tactic. (b) You might get better debug info with one of these patches: https://gist.github.com/totten/96aa7172faced3fde2225e145307f3b9 (c) You might also get more debug info with a CLI runner (eg `cv upgrade:db -vvv`).  
  > **username_3**: I had a similar experience on Wordpress 5.4. I cleared cache and used the "Upgrade CiviCRM" option in Christian Wach's CiviCRM Admin Utilities plugin for Wordpress, which is my typical routine. My upgrade also stalled at the same spot that username_0 showed. At the time, I didn't think to check on the status of the creditnote extension. I restored my database (mine is separate from Wordpress) and tried again with "cv -vvv upgrade:db". It upgraded with no complaints.  
  > **username_0**: I don't do command line stuff (I'm strictly an implementer) so tried installing Tim's patches manually but failed. The creditnote extension can only be installed via the command line, it seems, so username_1's suggestion is out. Since Mark also hit the same problem it doesn't sound like disabling extensions will fix. Any other ideas?  
  > **username_0**: I uninstalled all extensions and tried again.  It stopped at the same place (5.24aplha1) for a bit, then continued and installed OK, and I now have the sequential creditnote extension installed. There were over 20 extensions disabled so no idea which was the culprit. Is see that three of us have had this upgrade fail now..  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_2 on 2020-04-05. Score: 4
  
  I was able to reproduce a similar symptom in a [wp-demo configuration](https://github.com/civicrm/civicrm-buildkit/tree/master/app/config/wp-demo). Specifically, the upgrader activates the new, core-internal extension (`sequentialcreditnotes`), and the activation fired off a general system-flush, and the general system-flush raised an error while handling some data from another extension (`civivolunteer`). The problem only occurred with the web-based upgrade UI (and not with the CLI-based upgrader).
  
  [CiviCRM 5.24.1](https://download.civicrm.org/about/5.24.1) has a fix for that case.
  
  
  ---
  
  ### Answer by username_4 on 2020-04-03. Score: 0
  
  On WordPress version, tried to upgrade from 5.21.2 to 5.24.0 twice and had the same issue. Freezes on: Executed: Upgrade DB to 5.24.alpha1: SQL Had to restore previous day's back up to bring database back. No error messages, just the freezing.
  
  > **Comments:**
  > **username_2**: I was able to reproduce this problem. The following fixed it for me: https://github.com/civicrm/civicrm-core/pull/16971  
  > **username_5**: I saw the same under Joomla.  My test Joomla instance ran to completion, but the CiviCRM menu disappeared!  
  > **username_0**: Glad you found a fix, Tim and thanks for letting us know . I'm surprised this didn't occur  in testing as it was such a solid error.  
  
  ---
  
  