Re: [iola-conversion-tool] Knowing when the phase 2 server is supposed to be down?

Henrik Levkowetz <> Tue, 31 January 2012 21:34 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 9495B11E8080 for <>; Tue, 31 Jan 2012 13:34:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -102.557
X-Spam-Status: No, score=-102.557 tagged_above=-999 required=5 tests=[AWL=0.042, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 4wHp6j+cmYjA for <>; Tue, 31 Jan 2012 13:34:39 -0800 (PST)
Received: from ( [IPv6:2a01:3f0:1:2::30]) by (Postfix) with ESMTP id C9A6B11E8076 for <>; Tue, 31 Jan 2012 13:34:38 -0800 (PST)
Received: from localhost ([]:60826 helo=vigonier.lan ident=henrik) by with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.77) (envelope-from <>) id 1RsLLZ-0004Us-Df; Tue, 31 Jan 2012 22:34:37 +0100
Message-ID: <>
Date: Tue, 31 Jan 2012 22:34:36 +0100
From: Henrik Levkowetz <>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: Robert Sparks <>
References: <>
In-Reply-To: <>
X-Enigmail-Version: 1.3.5
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-SA-Exim-Scanned: No (on; SAEximRunCond expanded to false
Subject: Re: [iola-conversion-tool] Knowing when the phase 2 server is supposed to be down?
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Discussion of the IOLA / DB Schema Conversion Tool Project <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 31 Jan 2012 21:34:39 -0000

Hi Robert,

On 2012-01-31 20:26 Robert Sparks said the following:
> I've tried dropping in to test a couple of times and gotten either can't 
> connect or (what I have now),
> a 404 dressed in the top-level tools stylesheet.
> <> at the moment.

I see there's a problem with the https: server instance, will look at that
in a moment.  There's also a problem with the style sheet for the http:
instance, which may be a code update problem.  Will look at that too.

> I'm sure some of that is because of the data refresh.
> Is there some way we can predict when we shouldn't be expecting the 
> system to be available for testing?

Just before I left work, I updated the conversion script a bit to reduce
the amount of work it has to do; and I'm also close to having replication
in place.  I should be able to give much more precise timing on the updates
after that (hopefully later tonight).  But the issues I see when I connect
now aren't (I think) directly related to that, and I intend fix them now.

Best regards,