Install problem [#122118]

No one else has reported this, so I'm not sure yet if it's really a general issue, but I had a lot of trouble with the content module update 1003. I kept getting server 500 errors. I finally got it working only by commenting out all but one part of the update at a time, and re-running it until I had gotten through the whole thing.

That update does a lot of things (and in the last part you're pulling up the Views cache and the Views tables, which are huge), so I'm wondering if it needs to be broken into several updates instead of one huge one. Since we now have an update right after that which is taking up the next available update number, I'm not sure how we would handle the numbering to break it up without creating problems for anyone who has already run it.

Comments

Comment #1

yched CreditAttribution: yched commented 24 February 2007 at 00:34

The first part of the update_1003 (tables renaming) should be rather harmless. If there is a problem, it is probably more related to the views update part.

This part relies on the list of fields that have been updated in the first part. So we could put this list in a session variable at the end of _1003, and move the views part to a new _1005 function, which does nothing if it does not find the right session variable (that way, currently up-to-date installs starting the update in 1005 do nothing)

then this _1005 function could be made a progressive update function that gets executed in several passes (like content_update_5) and updates one view at a time. Only problem is this would need refactoring _content_views_rebuild_views.

I'm not exactly sure what is a 500 error to begin with ?

Comment #2

KarenS CreditAttribution: KarenS commented 24 February 2007 at 02:01

The server 500 error is something I get all the time since I have a lot of modules installed and am using as much memory as I am able to on my host. It almost always is an out of memory error from the server.

Yes, I'm pretty sure that it's just that last bit that is the real problem. I was able to get that part of the install to work OK as long as I wasn't trying to do anything else at the same time, so I think it's sufficient to pull the Views rebuild part out into a separate update. I don't think the rebuild itself needs to be broken up.

Comment #3

yched CreditAttribution: yched commented 24 February 2007 at 02:55

OK.
I'm about to commit a fix to http://drupal.org/node/108094 (MySQL5 error on text field creation) that includes an update function, so I'll fix this first, and add my new update as _1006