[seqfan] Re: OEIS hosting service was in trouble today

[Alonso Del Arte]

The situation persists, but seems to affect only one side of the OEIS. The
OEIS Wiki seems to be unaffected. You can look at today's Sequence of the
Day, but as soon as you click on its A-number to look at the full entry, you
get the "service temp. unavailable" message.

Al

On Sat, Aug 13, 2011 at 12:10 AM, N. J. A. Sloane <njas at research.att.com>wrote:

>
> I am on vacation and can only read email at night.
>
> Today Slicehost sent me and Dave two emails, as follows:
>
> >From support at slicehost.com Fri Aug 12 20:39:01 2011
> Delivered-To: njas at research.att.com
> Date: Fri, 12 Aug 2011 19:38:54 -0500
> From: support at slicehost.com
> To: njas at research.att.com, david at research.att.com
> Subject: Slicehost Notice - Server Unresponsive | OEIS | <248784> [40269]
>
> Subject:  Slicehost Notice: server unresponsive
>
> Hi, this is a quick email to notify you that your server is not responding
> to our monitors. We are investigating now.
>
> Slicehost Support.
>
>
> [40269]
> ----
> Slicehost Support
> support at slicehost.com
>
>
>
> >From support at slicehost.com Fri Aug 12 20:41:48 2011
> Delivered-To: njas at research.att.com
> Date: Fri, 12 Aug 2011 19:41:38 -0500
> From: support at slicehost.com
> To: njas at research.att.com, david at research.att.com
> Subject: Slicehost Notice: Emergency Server Migration | OEIS | <248789>
> [40269]
>
> Subject:  Slicehost Notice: emergency slice migration
>
> We have determined that the server hosting your slice is showing signs of
> immediate hardware failure, and as a precautionary measure to protect your
> data we will be moving all slices off of this server immediately. You can
> track the state of your slice by looking at the "status" of your slice in
> the slicemanager. The move takes place in a few steps, much like our resize
> process:
>
> Step 1: Move request is queued (slice status will be "queue-move")
> The move request will be processed as resources permit. The queued period
> is usually quick, but can vary depending on other host machine activities.
> Due to the immediate nature of the problem on the host, all slices will be
> queued for move, and will be processed as quickly as possible.
>
> Step 2: Initial preparation of new slice home (slice status will be
> "prep-move")
> This is the longest part of the move, during this step the original slice
> remains up and running.
>
> Step 3: Current slice is shut down and migrated (slice status will be
> "move")
> You will experience a downtime varying in proportion to fullness of the
> filesystem.
>
> Step 4: Done! (slice status will be "verify-move")
> We will take care of the rest.
> We apologize for the unexpected downtime this will incur. Unfortunately,
> this is the best course of action to prevent future problems.
>
> Please contact us with any questions or concerns via a reply to this email,
> or come chat with us at https://chat.slicehost.com .
>
>
>
> [40269]
> ----
> Slicehost Support
> support at slicehost.com
>
>
> ---
>
> I can also see a bunch of emails from people about this, which
> I have not yet read
>
>
>  Best regards
>                         Neil
>
> _______________________________________________
>
> Seqfan Mailing list - http://list.seqfan.eu/
>