identifying problems

Discussions about Internet service providers (ISPs), the Meetinghouse Firewall, wired and wireless networking, usage, management, and support of Meetinghouse Internet
jirp
Member
Posts: 174
Joined: Thu Feb 21, 2013 8:02 pm
Location: Greybull WY

identifying problems

Postby jirp » Sun Aug 12, 2018 1:03 pm

Yet again today there was a long stretch where the church websites were unavailable if a login was required. Go to log in for LCR, the seminary site, directory or maps and the login screen freezes and eventually the message website down for maintenance appears.

This problem usually happens roughly between about 10:30 AM mountain time and 2 PM with the worst of it being the hour just before lunch time.

Today our HC was trying to get youth seminary registrations done and an assignment for the youth on family search. It was nearly impossible. The seminary site logging in from the family history center computers(hardwired connection) was taking a couple of tries up through about 10 tries to get a successful login. I had to go to MLS to get the IOS sheets so the kids could do password recovery because I couldn't log onto LCR.

My belief is that the problem is on the server end at church headquarters but I need to verify before complaining so I know for sure who to complain to. There are a number of reasons to think this. 1. In May after stake conference I stopped at the church on the way home and was having that problem when I was the only one in the building and the only car in the parking lot at about 11:40 in the morning 2. All other websites I have access to seem to work fine even when doing semi data intensive things. 3. Back before we lost the usage statistics on technology manager we rarely flatlined at the peak rate. Attendance is down for the summer so it is unlikely we are suddenly needing more data.

The plan is to get the problem happening next Sun.(there are sundays it isn't a problem) Turn off the APs to see if that changes anything.(guessing it won't) That should verify if it is a building bandwidth problem. If that doesn't help try a laptop using a cell phone as a hotspot. That should let us check if it is an internet service provider bottleneck.

Is there anything else I need to do???

I am ward clerk, executive sectary and stake assistant technology specialist so I have access from both ends and I have physical access to all the hardware. After many months of this I am getting very frustrated with this. Mostly I can move my work load to other parts of the day but there are things I really need to do during block and just after the block at times.

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

Re: identifying problems

Postby russellhltn » Sun Aug 12, 2018 1:18 pm

jirp wrote:eventually the message website down for maintenance appears.

Assuming you're talking about the page with the church logo (and not a message from your browser), that page appears when the church network (at the data center) detects the servers are taking too long to respond. That points to problems at the head end, not the local network.

You might also want to test logging in using moble data. That would skip the local network entirely.

I'm not sure how data for lds.org is routed from the local building. It's possible it might be routed though the VPN and it's the VPN that's overloading. The expected syptom for that is moble data works fine, but the building network fails even when lightly loaded.

Something you might want to check is to make sure the system is assigning you a 192.168.x.x IP. 10.x.x.x IPs are for special things like Family History Centers.
Have you searched the Wiki?
Try using a Google search by adding "site:tech.lds.org/wiki" to the search criteria.

drepouille
Senior Member
Posts: 1698
Joined: Sun Jul 01, 2007 5:06 pm
Location: Plattsmouth, NE
Contact:

Re: identifying problems

Postby drepouille » Sun Aug 12, 2018 1:44 pm

I also could not access LCR during Sunday School today. I even unplugged the wireless adapters from the firewall, leaving only me connected to the firewall, and I still got the "down for maintenance" page. So I figured it was the church servers that were overloaded. I hope they get this fixed before we being trying to use LCR for deposits and checks.
Dana Repouille, Plattsmouth, Nebraska

lajackson
Community Moderators
Posts: 7755
Joined: Mon Mar 17, 2008 9:27 pm
Location: US

Re: identifying problems

Postby lajackson » Sun Aug 12, 2018 7:02 pm

drepouille wrote:I figured it was the church servers that were overloaded.


They were. Semiannual audits are in progress right now. Guess how many stake auditors hit the Church servers midday Sunday and called to ask me if they were really down for maintenance? Guess how many stake auditors are going back later this week to complete their audits? (Hint: the answer is the same to both questions.)

nmecantwin73
Member
Posts: 117
Joined: Thu Oct 11, 2007 8:36 am
Location: Utah

Re: identifying problems

Postby nmecantwin73 » Mon Aug 13, 2018 12:22 pm

jirp wrote:Is there anything else I need to do???

lds.org sites did go down yesterday starting around 10:30am Mountain Time. It is not a localized issue to your building(s), so you should not have to do anything.

RyanGard1977
New Member
Posts: 23
Joined: Sun Jul 19, 2015 9:26 pm

Re: identifying problems

Postby RyanGard1977 » Tue Aug 14, 2018 7:58 am

Yup, same issue- Many church sites & apps the past few Sundays have not been accessible during a good portion of the day (USA) :(


Return to “Meetinghouse Internet”

Who is online

Users browsing this forum: No registered users and 1 guest