Project

General

Profile

Actions

tickets #56951

closed

login redirection making page loading very slow for individual user(s)

Added by okurz over 4 years ago. Updated about 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Servers hosted in Provo
Target version:
-
Start date:
2019-09-17
Due date:
% Done:

0%

Estimated time:

Description

Observation

from #opensuse-admin

[15/09/2019 20:34:19] <a-865k> opensuse.org creepy crawley wait wait wait slow for past more than 12 hours
[15/09/2019 20:35:02] <a-865k> >60s wait for most page opens
[15/09/2019 20:35:35] <cboltz> which domains/pages exactly?
[15/09/2019 20:48:43] <a-865k> forums.o.o, bz.o.o are main use
[15/09/2019 20:49:28] <a-865k> maybe 24 days is too much uptime...
[15/09/2019 20:52:46] <cboltz> hmm, bugzilla response time looks normal for me (not super fast, but "as usual")
[15/09/2019 21:49:55] <a-865k> *.o.o seems normal since rebooting :p
[15/09/2019 22:32:15] <cboltz> interesting[tm]
[15/09/2019 22:32:58] <cboltz> I can only guess that you got new login cookies and, more important, ended up on another login server (AFAIK there are multiple login servers in Provo behind a load balancer)
[15/09/2019 22:34:34] <cboltz> the login cookies probably include a hint for the load balancer to which login server it should forward your requests
[15/09/2019 22:36:39] <cboltz> okurz: can you please forward this guess to the admins in Provo?
[15/09/2019 22:36:46] <cboltz> okurz: (For bonus points: having a way to force usage of a specific login server would be nice, and would make debugging much easier)
[16/09/2019 00:30:42] <a-865k> stalled looking up forums.opensuse.org again
[16/09/2019 00:31:03] <a-865k> okurz
[16/09/2019 00:31:21] <a-865k> The operation timed out when attempting to contact forums.opensuse.org
[16/09/2019 00:31:49] <a-865k> startpage.com and google.com are working normally
[16/09/2019 00:32:59] <a-865k> stalled looking up bugzilla.opensuse.org again
[16/09/2019 00:34:08] <a-865k> I had been reading a forum post, clicked reply to thread, and then the stall
Actions #1

Updated by okurz over 4 years ago

  • Description updated (diff)

tracked as RIO ticket FIX_302510

Actions #2

Updated by okurz over 4 years ago

  • Description updated (diff)
  • Private changed from Yes to No
Actions #3

Updated by okurz over 4 years ago

  • Tracker changed from communication to tickets
  • Status changed from Feedback to Blocked
Actions #4

Updated by okurz over 4 years ago

a-865k: regarding your network problems: I still have a MF-IT ticket open linked to here and there is sporadic communication but not really going forward in either way. I agree with kl_eisbaer aka. lrupp who had a good point in https://progress.opensuse.org/issues/52262#note-5 : We are merely acting as proxies and can not really help when there are either individual or sporadic network problems. The services are fine as most of the users at most of the time can interact just fine. I suggest to directly get in contact with someone at microfocus. There are also nice people there but going over multiple hops in communication tends to slow down transfer of information, loose information, loose the "personal touch" and not really reach a conclusion.

Actions #5

Updated by mrmazda over 4 years ago

From 52262 so I have a chance to find it when needed: Please contact forums@microfocus.com

Actions #6

Updated by okurz about 4 years ago

  • Status changed from Blocked to Resolved

In the MF-IT ticket "Chris Slade" answered with "There is no way to force a specific server for login.". The other questions were not answered. I guess moving forward like this won't work out so I will close the ticket with the notice to try to directly contact the support adress you mentioned already. Let's hope that after the planned move of the bugzilla and other instances to SUSE-only network we can help better or we will have these problems fixed.

Actions

Also available in: Atom PDF