From: Chuck Lever <chuck.lever@oracle.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: "Dr. J. Bruce Fields" <bfields@fieldses.org>,
linux-nfs@vger.kernel.org, nfsv4@linux-nfs.org,
pnfs@linux-nfs.org, labeled-nfs@linux-nfs.org,
keyrings@linux-nfs.org
Subject: Re: linux-nfs.org will be going down for an upgrade today...
Date: Mon, 17 May 2010 16:16:26 -0400 [thread overview]
Message-ID: <4BF1A41A.9010201@oracle.com> (raw)
In-Reply-To: <1274123725.4354.6.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
On 05/17/10 03:15 PM, Trond Myklebust wrote:
> On Mon, 2010-05-17 at 13:48 -0400, Chuck Lever wrote:
>> On 05/17/10 01:38 PM, Trond Myklebust wrote:
>>> On Mon, 2010-05-17 at 13:19 -0400, Chuck Lever wrote:
>>>> On 05/11/2010 03:12 PM, Trond Myklebust wrote:
>>>>> On Mon, 2010-05-10 at 13:07 -0400, Trond Myklebust wrote:
>>>>>> Hi,
>>>>>>
>>>>>> I'm planning on upgrading the Linux distribution on linux-nfs.org to a
>>>>>> newer release today. Unfortunately, this has to be done during working
>>>>>> hours since I no longer have physical access to the CITI machine room
>>>>>> (and so have to rely on Bruce being available should the remote access
>>>>>> fail).
>>>>>>
>>>>>> I expect to start at around 2pm EST (in 1 hour from now). Hopefully the
>>>>>> down time will be less than an hour or two.
>>>>>> During that time, expect no access to www.linux-nfs.org, the git daemon,
>>>>>> wiki.linux-nfs.org, bugzilla.linux-nfs.org or the linux-nfs.org mailing
>>>>>> lists.
>>>>>>
>>>>>> I'll send a mail once everything is up and running again...
>>>>>
>>>>> As feared it took a good deal more time than expected, however I believe
>>>>> that everything should be up and working again now.
>>>>
>>>> I've found two anomalies so far (and they may be on my end, fwiw).
>>>>
>>>> 1. Yesterday, I tried to update the IPv6 working document on the NFSv4
>>>> wiki, and the edit failed with a page that said an "internal error"
>>>> occurred.
>>>
>>> Not sure about this. Is it reproducible?
>>
>> Yes. I just tried it again.
>>
>> The error page says you can set $wgShowExceptionDetails = true; at the
>> bottom of LocalSettings.php to show detailed debugging information.
>
> OK. I think I've fixed it: we were hitting a bug in the SpamBlackList
> module. I've disabled that module for the time being...
Confirmed, it's working now. Thanks.
prev parent reply other threads:[~2010-05-17 20:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-10 17:07 linux-nfs.org will be going down for an upgrade today Trond Myklebust
2010-05-11 19:12 ` Trond Myklebust
[not found] ` <1273605127.2810.12.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2010-05-17 17:19 ` Chuck Lever
2010-05-17 17:38 ` Trond Myklebust
[not found] ` <1274117929.4354.3.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2010-05-17 17:48 ` Chuck Lever
[not found] ` <4BF18172.4040607@oracle.com>
2010-05-17 19:15 ` Trond Myklebust
[not found] ` <1274123725.4354.6.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2010-05-17 20:16 ` Chuck Lever [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4BF1A41A.9010201@oracle.com \
--to=chuck.lever@oracle.com \
--cc=bfields@fieldses.org \
--cc=keyrings@linux-nfs.org \
--cc=labeled-nfs@linux-nfs.org \
--cc=linux-nfs@vger.kernel.org \
--cc=nfsv4@linux-nfs.org \
--cc=pnfs@linux-nfs.org \
--cc=trond.myklebust@fys.uio.no \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.