CiviCRM Community Forums (archive)

*

News:

Have a question about CiviCRM?
Get it answered quickly at the new
CiviCRM Stack Exchange Q+A site
This forum was archived on 25 November 2017. Learn more.
How to get involved.
What to do if you think you've found a bug.



  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Upgrading CiviCRM (Moderator: Deepak Srivastava) »
  • running time to upgrade 3.3.6 -> 3.4.0
Pages: [1]

Author Topic: running time to upgrade 3.3.6 -> 3.4.0  (Read 580 times)

mclyde

  • I post frequently
  • ***
  • Posts: 171
  • Karma: 3
    • International Society for Bayesian Analysis
  • CiviCRM version: 4.2.7
  • CMS version: Drupal 6.x
  • MySQL version: 5.136
  • PHP version: 5.2.16
running time to upgrade 3.3.6 -> 3.4.0
May 04, 2011, 12:34:54 pm
I am running the upgrade script on our development site to upgrade from 3..3.6 to 3.4.0 and it was running for over an hour before crashing. 

It just stopped with an error  DB Error: a515ac9c2796ca0e23adbe92c68fc9fc

My last upgrade (jump from 2.2.9 to 3.3.6 went pretty quickly)

Thoughts?

Quote
         
Database Error Code: Lost connection to MySQL server during query, 2013
Additional Details:

Array
(
    [callback] => Array
        (
           
  • => CRM_Core_Error
    • [1] => handle
            )

       
Code: [Select]
=> a515ac9c2796ca0e23adbe92c68fc9fc
    [message] => DB Error: a515ac9c2796ca0e23adbe92c68fc9fc
    [mode] => 16
    [debug_info] => UPDATE civicrm_membership_log cml INNER JOIN civicrm_membership cm
ON cml.membership_id=cm.id SET cml.membership_type_id=cm.membership_type_id [nativecode=2013 ** Lost connection to MySQL server during query]
    [type] => DB_Error
    [user_info] => UPDATE civicrm_membership_log cml INNER JOIN civicrm_membership cm
ON cml.membership_id=cm.id SET cml.membership_type_id=cm.membership_type_id [nativecode=2013 ** Lost connection to MySQL server during query]
    [to_string] => [db_error: message="DB Error: a515ac9c2796ca0e23adbe92c68fc9fc" code=0 mode=callback callback=CRM_Core_Error::handle prefix="" info="UPDATE civicrm_membership_log cml INNER JOIN civicrm_membership cm
ON cml.membership_id=cm.id SET cml.membership_type_id=cm.membership_type_id [nativecode=2013 ** Lost connection to MySQL server during query]"]
)

[/quote]


Merlise Clyde

myles

  • I post frequently
  • ***
  • Posts: 263
  • Karma: 11
Re: running time to upgrade 3.3.6 -> 3.4.0
May 04, 2011, 01:43:24 pm
Could the db error be a red herring - that appears to have failed because the connection was lost.

After an hour of nothing much I'd be getting lost too.

Why should it take an hour of run time before it lost the connection?

The only time that has happened to us was when we ran out of memory - when the allocation was increased by the VPS providor the script ran fine.

This thought may also be a red herring.
Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Upgrading CiviCRM (Moderator: Deepak Srivastava) »
  • running time to upgrade 3.3.6 -> 3.4.0

This forum was archived on 2017-11-26.