Scheduled down time

Share discussions around the Classic Local Unit Website (LUWS).
russellhltn
Community Administrator
Posts: 20757
Joined: Sat Jan 20, 2007 2:53 pm
Location: U.S.

Scheduled down time

Postby russellhltn » Tue Aug 21, 2007 12:29 am

Would it be possible to get a schedule or some idea when LUWS is taken down? Often times, I'm not informed when I reach the login page, but when the whole thing goes ka-fooey on login.

For example, I logged into to look up some names so I can schedule somethings and after logging in I get "The requested object does not exist on this server. The link you followed is either outdated, inaccurate, or the server has been instructed not to let you have it." I have no idea when it will be back up again.

Also when scheduling, please keep in mind that the US is at least 6-7 time zones wide, not 4-5. What's good for CONUS isn't good for all users. :mad:

User avatar
WelchTC
Senior Member
Posts: 2088
Joined: Wed Sep 06, 2006 7:51 am
Location: Kaysville, UT, USA
Contact:

Postby WelchTC » Mon Aug 27, 2007 8:33 am

I think that is a great suggestion. I'll pass it along to the team to see if they want to post their downtimes somewhere online.

Tom

JamesAnderson
Senior Member
Posts: 748
Joined: Tue Jan 23, 2007 2:03 pm

Postby JamesAnderson » Mon Aug 27, 2007 9:15 am

Almost all major websies post something if they are going to be down more than a few minutes, such as overnight or whatever. That would be a good idea for a bloglike page off lds.org or any other Church property, that would be updated to show 'system status' or something, when they needed to take a site or part of it offline for maintenance.

Will be particularly needed as new FamilySearch rolls out, they have already done this with good results on the FamilySearch Indexing site after everyone swamped the servers right after the August Ensign came out.

User avatar
bhofmann-p40
Member
Posts: 272
Joined: Tue Feb 06, 2007 9:47 am
Location: Tulsa, OK
Contact:

Postby bhofmann-p40 » Mon Aug 27, 2007 10:45 am

JamesAnderson wrote:Almost all major websies post something if they are going to be down more than a few minutes, such as overnight or whatever. That would be a good idea for a bloglike page off lds.org or any other Church property, that would be updated to show 'system status' or something, when they needed to take a site or part of it offline for maintenance.


Sounds like a job for LDS Tech!

User avatar
ShirtsDre
Member
Posts: 109
Joined: Wed Jan 31, 2007 10:53 am
Location: Utah
Contact:

Default Error Message.

Postby ShirtsDre » Mon Aug 27, 2007 1:56 pm

RussellHltn wrote: "The requested object does not exist on this server. The link you followed is either outdated, inaccurate, or the server has been instructed not to let you have it."


This message is simply the default error message that gets displayed for a variety of reasons. As far as a scheduled outtage, the only regular occurrence will be a nightly run of several database updates. I don't know exactly when these occur, but they do cause this default message to occur.

We will not be implementing a scheduled outtage message as the current one (The default error message) "fits the bill". There are occasions where this default error page will display a specific error id number. If that occurs, please contact the Global Help Desk with as much background information as possible as to where you were in the site and what action you were attempting to accomplish. I can't tell you how helpful it is to provide us this error number and background information.
-- Learn from the past. Prepare for the future. Live in the present. -- President Thomas S. Monson

User avatar
ShirtsDre
Member
Posts: 109
Joined: Wed Jan 31, 2007 10:53 am
Location: Utah
Contact:

Postby ShirtsDre » Mon Aug 27, 2007 2:02 pm

BillyBoJimBob wrote:We will not be implementing a scheduled outtage message as the current one (The default error message) "fits the bill".


Normally, changes I make to the website happen so quickly that it doesn't warrant shutting the site down. The effect it will have, at most, is one or two users being interrupted. I only do these updates periodically ,two or three times a quarter, and can tell if it is interrupting normal usage of the site. If it does, the changes are usually rolled back immediately.

In the event that we will be taking the website down for an extended period of time, other than the daily database updates previously mentioned, a site lock out page would be provided, giving an estimated time for reopening the site. This has yet to happen with the Stake and Ward Websites site.
-- Learn from the past. Prepare for the future. Live in the present. -- President Thomas S. Monson

russellhltn
Community Administrator
Posts: 20757
Joined: Sat Jan 20, 2007 2:53 pm
Location: U.S.

Postby russellhltn » Mon Aug 27, 2007 2:07 pm

BillyBoJimBob wrote:We will not be implementing a scheduled outage message as the current one (The default error message) "fits the bill".


I beg to differ. The default message suggests that either the servers are totally hosed, or that your login is messed up. Nowhere does it suggest "we're down for maintenance" or "please try later" (or how much "later"). If nothing else, I think the default error message needs tweaking.

The current message, while it may be technically correct, doesn't give the user any useful information. (It reminds me of this joke)

User avatar
ShirtsDre
Member
Posts: 109
Joined: Wed Jan 31, 2007 10:53 am
Location: Utah
Contact:

"Glittering Generality"

Postby ShirtsDre » Mon Aug 27, 2007 5:08 pm

RussellHltn wrote:I beg to differ. The default message suggests that either the servers are totally hosed, or that your login is messed up. Nowhere does it suggest "we're down for maintenance" or "please try later" (or how much "later"). If nothing else, I think the default error message needs tweaking.

The current message, while it may be technically correct, doesn't give the user any useful information. (It reminds me of this joke)


This is a default message used by a multitude of sites within the same architecture. It is meant to be over-generalized. Specifics are sometimes added as an error ID number that the user can refer to the Global Service Desk for reporting purposes.

We are not the only site that offers only a generalized error screen when issues arise. This is in effect our "404 - Not Found" page, which we and other sites use for a host of different reasons.

If the issue happens again, please note if an error id number is displayed. Either way, please contact the Global Service Desk to report the issue so we can get working on it as soon as possible.
-- Learn from the past. Prepare for the future. Live in the present. -- President Thomas S. Monson

russellhltn
Community Administrator
Posts: 20757
Joined: Sat Jan 20, 2007 2:53 pm
Location: U.S.

Postby russellhltn » Mon Aug 27, 2007 6:19 pm

BillyBoJimBob wrote:This is in effect our "404 - Not Found" page.


Actually, "404" would be an improvement. At least I know what that is.


Return to “Classic Ward & Stake Sites (LUWS)”

Who is online

Users browsing this forum: No registered users and 1 guest