Magically, my problem with issue #1001794: Another Fatal error: Out of memory has resolved itself and I am finally running Drush.

I have a multisite configured like:

  • sites/all
  • sites/site1.domain.com
  • sites/site2.domain.com

I ran drush up -l site1.domain.com and it updated Views (6.x-3.0-alpha3) and Core (from 6.19 -6.20). The last lines of the upgrade gave the impression that it ran update.php as well as clearing all the caches. Of course, right now all it shows is:

No code updates available.                                           [ok]
No database updates required                                         [success]
'all' cache was cleared                                              [success]
Finished performing updates.                                         [ok]

I noticed that if I run update.php from admin (Admin Menu), it runs and informs me that there is a views update to be made.

I confirmed this on site2.domain.com by running drush updatedb -l http://site2.domain.com. Drush returns:

> drush updatedb -l http://site2.domain.com
No database updates required                                         [success]
'all' cache was cleared                                              [success]
Finished performing updates.                                         [ok]

Yet if I run update.php from the browser (http://site2.domain.com/update.php), I still get a message that views tables need to be updated.

Am I using update incorrectly?

Comments

greg.1.anderson’s picture

greg.1.anderson commented
Status: Active » Postponed (maintainer needs more info)

The first thing that you experienced was expected. When you run drush up on site1, drush updates the code for all modules enabled in site1 and then runs updatedb on site1. Since site1 and site2 share some code, it is expected that you will still need to run updatedb on site2.

At the bottom of #0, I'm not sure why drush thinks that you don't need to updatedb, but the browser does, though.

waverate’s picture

waverate commented

What more info can I provide?

greg.1.anderson’s picture

greg.1.anderson commented

Read the top of the page here: http://drupal.org/node/add/project-issue/drush.

In this case, I don't know that that will be enough to solver your issue. Fortunately, you have a workaround. Experiment a bit and see if you can figure it out.

waverate’s picture

waverate commented

Upgraded to HEAD Drush

An update to the Image module was posted so I ran drush -l http://site1.domain.com up --debug

There was a lot of output however, there were errors like:

Warning: MySQL server has gone away
query: INSERT INTO watchdog
    (uid, type, message, variables, severity, link, location, referer, hostname, timestamp)
    VALUES
    (0, 'php', '%message in %file on line %line.', 'a:4:{s:6:\"%error\";s:12:\"user warning\";s:8:\"%message\";s:59:\"MySQL server has gone away\nquery: TRUNCATE TABLE cache_page\";s:5:\"%file\";s:63:\"/home/domain.com/public_html/drupal/includes/cache.inc\";s:5:\"%line\";i:172;}', 3, '', 'http://domain.com/index.php', '', '127.0.0.1', 1293116824) in /home/domain.com/public_html/drupal/includes/database.mysqli.inc on line 135
WD php: MySQL server has gone away                                   [error]
query: TRUNCATE TABLE cache_page in
/home/domain.com/public_html/drupal/includes/cache.inc on
line 172. [189.82 sec, 37.87 MB]

I followed this issue and added max_allowed_packet = 64M to php.ini

Afterwards, drush -l site2.domain.com updatedb --debug did not have any errors and there were no issues with update.php from the browser.

I am going to wait for a module to update its tables and try it one more time to be sure.

jhr’s picture

jhr commented
Status: Postponed (maintainer needs more info) » Closed (fixed)

Seems it's fixed... plus an unsupported version
novice triaged - feel free to reopen