Answers.Body: <p>How big is your database? It could be that Craft is failing to backup your database as part of the update process because it is running out of memory.</p>
  
  <p>Try setting the <a href="http://buildwithcraft.com/docs/config-settings#backupDbOnUpdate" rel="nofollow"><code>backupDbOnUpdate</code></a> config setting to <code>false</code> and running the update again.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-11-04T16:15:03.430Z
Answers.Text: That's likely it, though regardless of database size, the current `memory_limit` is `32M`, so I'd bump that up regardless. Once you start any image processing (transforms, etc.) you'll hit the same error.
Answers.UserDisplayName: Brad Bell
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-11-04T16:15:56.187Z
Answers.Text: Cheers @steverowling that worked a treat. Yes database is pretty large so obviously what was causing the issue.
Answers.UserDisplayName: Lettie
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-11-04T16:18:43.710Z
Answers.Text: @bradbell good point would do this with a non-shared server unfortunately hands are tied on this one. But it's only a play around test site so not an issue!
Answers.UserDisplayName: Lettie
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-11-04T16:19:52.150Z
Answers.Text: @Lettie Ahh, missed that part in your original post. My bad.
Answers.UserDisplayName: Brad Bell
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-11-04T16:10:35.287Z
Answers.LastActivityDate: 2015-11-04T16:10:35.287Z
Answers.UserDisplayName: Steve Rowling
Body: <p>Just tried updating craft from version 2.4.2669 to the latest version 2.4.2702 unfortunately it threw a fatal error with the following error message:</p>
  
  <blockquote>
    <p>Status: OK</p>
    
    <p>Response: <br /> <b>Fatal error</b>: Out of memory (allocated
    33030144) (tried to allocate 41 bytes) in
    <b>/homepages/3/d272256762/htdocs/crafttest/craft/app/framework/db/CDbCommand.php</b>
    on line <b>518</b><br /></p>
  </blockquote>
  
  <p>So I then tried to manually install it by uploading the app folder. Clicked through on the update databases it started working, but again threw the same error.</p>
  
  <p>The site is on a shared server so I can not do much regarding memory limits.</p>
  
  <p>So now I have no CMS and no frontend what can I do to rectify this problem to either rollback to the previous version or update to the newer one?</p>
  
Tags: <updating><auto-updates><updates><manual-updates>
Title: Updating Craft Produced Fatal Error.What now?
ThreadText: # Updating Craft Produced Fatal Error.What now?
  
  (Asked by: username_0 on 2015-11-04)
  
  Just tried updating craft from version 2.4.2669 to the latest version 2.4.2702 unfortunately it threw a fatal error with the following error message:
  
  > Status: OK
  >
  > Response:   
  >  **Fatal error**: Out of memory (allocated
  > 33030144) (tried to allocate 41 bytes) in
  > **/homepages/3/d272256762/htdocs/crafttest/craft/app/framework/db/CDbCommand.php**
  > on line **518**
  
  So I then tried to manually install it by uploading the app folder. Clicked through on the update databases it started working, but again threw the same error.
  
  The site is on a shared server so I can not do much regarding memory limits.
  
  So now I have no CMS and no frontend what can I do to rectify this problem to either rollback to the previous version or update to the newer one?
  
  **Tags:** updating, auto-updates, updates, manual-updates
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2015-11-04. Score: 2 | Accepted answer
  
  How big is your database? It could be that Craft is failing to backup your database as part of the update process because it is running out of memory.
  
  Try setting the [`backupDbOnUpdate`](http://buildwithcraft.com/docs/config-settings#backupDbOnUpdate) config setting to `false` and running the update again.
  
  > **Comments:**
  > **username_2**: That's likely it, though regardless of database size, the current `memory_limit` is `32M`, so I'd bump that up regardless. Once you start any image processing (transforms, etc.) you'll hit the same error.  
  > **username_0**: Cheers @username_1 that worked a treat. Yes database is pretty large so obviously what was causing the issue.  
  > **username_0**: @username_2 good point would do this with a non-shared server unfortunately hands are tied on this one. But it's only a play around test site so not an issue!  
  > **username_2**: @username_0 Ahh, missed that part in your original post. My bad.  
  
  ---
  
  