[theforum] [Fwd: Progress (at last! (Was: Re: weo migration))]

David Kaufman david at gigawatt.com
Sun Nov 29 23:48:35 CST 2009

[Resent with cc's since theforum is apparently experiencing some 
technical difficulties]

-------- Original Message --------
Subject: Progress (at last! (Was: Re: [theforum] weo migration))
Date: Mon, 30 Nov 2009 00:16:44 -0500
From: David Kaufman <david at gigawatt.com>
To: theforum at lists.evolt.org <theforum at lists.evolt.org>

Great news!

Thanks, Dean -- your upgrade access-variable tip got me over that last
hump, and I was able to resolve the session issue tonight by upgrading
drupal from 4.6.1 to 4.6.11 which was the last thing blocking us from
decommissioning tempest.

I now have scripts (in the tempest user home directory on tron, if you
care to peruse) that will rsync a fresh snapshot of the drupal htdocs
directory tree, dump the database from tempest to tron over ssh (into a
db called tempest_weo), and perform the upgrade, so I can redo this to
get WEO up on tron quickly, as soon as were we're ready to retire tempest.

If you'd like to test, you'll need a hosts file entry such as:      evolt.org  www.evolt.org

(and a "bowser reboot" (and maybe some cache-clearage)), but everything
looks fine to me...

You guys ready to do (er: re-do) LEO and BEO migrations, one last time?



PS: Just transferred another $100 bucks from paypal to the bank to cover
December hosting at $113 in the optimistic hope that we'll only need $45
for January and thereafter :-)

Dean Mah wrote:
> On Wed, Sep 9, 2009 at 7:28 AM, David Kaufman<david at gigawatt.com> wrote:
>> Dean wrote:
>>> David wrote:
>>>> Dean wrote:
>>>>> 1) Drupal 4.6.1 does not work out of the box on tron.  There is a
>>>>> session problem.
>>>> What was the specific issue, login problems?  Is it difficult to
>>>> reproduce?  I'm doing some testing now.
>>  > Login and then go to any page. Check to see if you are still logged
>>  > in.
>> Ok, so that was an easy bug to reproduce :-)
>> So I have the old weo and old drupal running (with the session bug in
>> full bloom) and I have a test environment of sorts (i created a tempest
>> user on tron -- is that confusing enough?) and scripts to
>> 1) pull fresh copies of htdocs and database from production, and
>> 2) revert my dev site to the latest copy of production (fixing up things
>> like permissions the db_url in settings.php and such)
>> and now I need to develop either:
>> a) a script that performs the steps to upgrade drupal to the latest 4.x
>> that works with php 5, or
>> b) compile custom apache 1.3x and php4 binaries and reconfigure the
>> virtual host to use them, so it is usable
>> If a is going to work, I have to get around this session bug first,
>> which you mentioned was frustrating.  Since I can't login I can't do the
>> recommended pre-upgrade steps such as disabling plugins and reverting to
>> the default theme first.
>> I wonder if I should try doing this upgrade step (from 1.6.1 to 1.7.11)
>> on a dev copy on tempest first (where drupal + php works) then sync that
>> over to tempest... I'll try that next.  Friday morning probably -- need
`>> at least one night of sleep this week :-)
> In my experience, you don't need to be able to login to do the
> upgrade.  There is a variable in the update.php file that you can set
> to remove the requirement to login.  If memory serves, you don't need
> to return to the default theme.  At least not when you are going from
> 4.6.3 -> 4.7.
> For the session bug, I had a similar problem with limesurvey.  I used
> LiveHTTPHeaders to see the cookies that were being sent back and forth
> and noticed an inconsistency after a session_regenerate_id in the code
> where the new session id was not being passed.  I was going to start
> looking there for the problem in the Drupal code.
> Dean
> --
> TheForum Archives: http://lists.evolt.org/theforumarchive/
> evolt.org wiki: http://wiki.evolt.org/
> teamwork site: http://evolt.teamworkpm.net/

More information about the theforum mailing list