Body: <p>First time this has happened for me. Doing a periodic update, going from civicrm 5.74.4 to 5.78.0, the upgrade process seems to have hung on &quot;Upgrade DB to 5.78.beta1: SQL&quot;.</p>
  <p>Last few lines of the CiviCRM log:
  2024-10-06 08:56:42-0400  [info] Running task: Upgrade DB to 5.78.alpha1: SQL</p>
  <p>2024-10-06 08:56:43-0400  [info] Running task: Finish Upgrade DB to 5.78.alpha1</p>
  <p>2024-10-06 08:56:43-0400  [info] Running task: Begin Upgrade to 5.78.beta1</p>
  <p>2024-10-06 08:56:44-0400  [info] Running task: Upgrade DB to 5.78.beta1</p>
  <p>2024-10-06 08:56:45-0400  [info] Running task: Upgrade DB to 5.78.beta1: SQL</p>
  <p>It's been stuck there for over 10 minutes. Can't find any error message in any other logs.</p>
  <p>The site is working, for the few tests I've done on it... but... this is worrisome. Would rather not do a full rollback.</p>
  <p>Any suggestions?</p>
  <p>Thanks.</p>
  <p>Michael</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2024-10-06T14:28:10.770Z
Comments.Text: Based on the contents of .../civicrm/civicrm/CRM/Upgrade/Incremental/sql/5.78.beta1.mysql.tpl and the empty 5.78.alpha1.mysql.tpl file, at least assuming the comments on the columns were not that way before already, it looks like that part completed.
Comments.UserDisplayName: Michael Matthews
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2024-10-06T15:14:51.520Z
Comments.Text: The comments were like that before. What you'd want to compare is if the column specifies `not null`. You can also manually run each line and see where it hangs. The statements are re-runnable so you wouldn't need to restore.
Comments.UserDisplayName: Demerit
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2024-10-06T15:41:47.047Z
Comments.Text: Thanks. I ran all of the statements in that file and they all worked fine. Beginning to think the failure was the task failed to add / execute. And assuming this is the entire process and that was the last step, what else has to be done to mark the update as complete so I can do a future update?
Comments.UserDisplayName: Michael Matthews
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2024-10-06T16:24:31.757Z
Comments.Text: There are a few more steps where it does stuff with extensions and message templates. What I'd try is running `UPDATE civicrm_domain SET version='5.77.0'` and then re-run the upgrade.
Comments.UserDisplayName: Demerit
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2024-10-06T16:43:10.987Z
Comments.Text: That produced a successful update message. Thanks!
Comments.UserDisplayName: Michael Matthews
Tags: <upgrade><mysql><failure>
Title: WordPress/MySQL Upgrade from 5.74.4 to 5.78.0 hangs on Upgrade DB to 5.78.beta1: SQL
ThreadText: # WordPress/MySQL Upgrade from 5.74.4 to 5.78.0 hangs on Upgrade DB to 5.78.beta1: SQL
  
  (Asked by: username_0 on 2024-10-06)
  
  First time this has happened for me. Doing a periodic update, going from civicrm 5.74.4 to 5.78.0, the upgrade process seems to have hung on "Upgrade DB to 5.78.beta1: SQL".
  
  Last few lines of the CiviCRM log:
  2024-10-06 08:56:42-0400 [info] Running task: Upgrade DB to 5.78.alpha1: SQL
  
  2024-10-06 08:56:43-0400 [info] Running task: Finish Upgrade DB to 5.78.alpha1
  
  2024-10-06 08:56:43-0400 [info] Running task: Begin Upgrade to 5.78.beta1
  
  2024-10-06 08:56:44-0400 [info] Running task: Upgrade DB to 5.78.beta1
  
  2024-10-06 08:56:45-0400 [info] Running task: Upgrade DB to 5.78.beta1: SQL
  
  It's been stuck there for over 10 minutes. Can't find any error message in any other logs.
  
  The site is working, for the few tests I've done on it... but... this is worrisome. Would rather not do a full rollback.
  
  Any suggestions?
  
  Thanks.
  
  Michael
  
  **Tags:** upgrade, mysql, failure
  
  > **Comments:**
  > **username_0**: Based on the contents of .../civicrm/civicrm/CRM/Upgrade/Incremental/sql/5.78.beta1.mysql.tpl and the empty 5.78.alpha1.mysql.tpl file, at least assuming the comments on the columns were not that way before already, it looks like that part completed.  
  > **username_1**: The comments were like that before. What you'd want to compare is if the column specifies `not null`. You can also manually run each line and see where it hangs. The statements are re-runnable so you wouldn't need to restore.  
  > **username_0**: Thanks. I ran all of the statements in that file and they all worked fine. Beginning to think the failure was the task failed to add / execute. And assuming this is the entire process and that was the last step, what else has to be done to mark the update as complete so I can do a future update?  
  > **username_1**: There are a few more steps where it does stuff with extensions and message templates. What I'd try is running `UPDATE civicrm_domain SET version='5.77.0'` and then re-run the upgrade.  
  > **username_0**: That produced a successful update message. Thanks!  
  
  ---
  
  ## 0 answers
  
  