[heroes] *.opensuse.org virtually unreachable when apache2 running
Last night I put a DVD .iso on my website and emailed a link to it to a bunch of friends. Since then, bugzilla.opensuse.org and forums.opensuse.org frequently are unreachable or timeout in the middle of using them, such as trying to reply to a forum post, or load a saved bug search. At best the waits before *.o.o page load are 10 times as long as other sites. Even on good days most b.o.o searches totally timeout eventually into a blank page[1]. Startpage, Google, their hits and other commonly used sites (e.g. eBay) are producing no such trouble. I found that by stopping apache2 that b.o.o and f.o.o will become reachable shortly following "systemctl stop apache2". Today is hardly the first time *.opensuse.org has been painful if not impossible to use. See e.g.: https://progress.opensuse.org/issues/53396 https://progress.opensuse.org/issues/52178 https://progress.opensuse.org/issues/56189 https://bugzilla.opensuse.org/show_bug.cgi?id=1133589 https://bugzilla.opensuse.org/show_bug.cgi?id=1084827 https://bugzilla.opensuse.org/show_bug.cgi?id=1065560 https://bugzilla.opensuse.org/show_bug.cgi?id=1051768 https://bugzilla.opensuse.org/show_bug.cgi?id=753203 (logs for irc://freenode/opensuse-admin) What has to be done, short of removing this .iso file from my website or keeping apache2 stopped, to stop this recurring pain and waste of time? [1] https://bugzilla.opensuse.org/show_bug.cgi?id=1100506 -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: heroes+unsubscribe@opensuse.org To contact the owner, e-mail: heroes+owner@opensuse.org
Felix Miata wrote:
Last night I put a DVD .iso on my website and emailed a link to it to a bunch of friends. Since then, bugzilla.opensuse.org and forums.opensuse.org frequently are unreachable or timeout in the middle of using them, such as trying to reply to a forum post, or load a saved bug search. At best the waits before *.o.o page load are 10 times as long as other sites. Even on good days most b.o.o searches totally timeout eventually into a blank page[1]. Startpage, Google, their hits and other commonly used sites (e.g. eBay) are producing no such trouble. I found that by stopping apache2 that b.o.o and f.o.o will become reachable shortly following "systemctl stop apache2".
Hi Felix I think this is really a support question. What you do with apache2 on your side can hardly have much affect on the openSUSE infrastructure. [snip]
What has to be done, short of removing this .iso file from my website or keeping apache2 stopped, to stop this recurring pain and waste of time?
I suggest you post your question on one of the support lists or fora, you will like get more traction there. -- Per Jessen, Zürich (19.6°C) Member, openSUSE Heroes -- To unsubscribe, e-mail: heroes+unsubscribe@opensuse.org To contact the owner, e-mail: heroes+owner@opensuse.org
Per Jessen composed on 2019-09-16 10:15 (UTC+0200):
Felix Miata wrote:
Last night I put a DVD .iso on my website and emailed a link to it to a bunch of friends. Since then, bugzilla.opensuse.org and forums.opensuse.org frequently are unreachable or timeout in the middle of using them, such as trying to reply to a forum post, or load a saved bug search. At best the waits before *.o.o page load are 10 times as long as other sites. Even on good days most b.o.o searches totally timeout eventually into a blank page[1]. Startpage, Google, their hits and other commonly used sites (e.g. eBay) are producing no such trouble. I found that by stopping apache2 that b.o.o and f.o.o will become reachable shortly following "systemctl stop apache2".
I think this is really a support question.
At first that's what I thought, but...
What you do with apache2 on your side can hardly have much affect on the openSUSE infrastructure.
It seems like it shouldn't but what's happening is the openSUSE infrastructure latency problem is obviously being magnified when on my end a big upload is slowing traffic going through my router and/or my ISP's speed throttling. Turning off the upload by halting apache2 returns the latency to its usually tolerable pain level. No one on broadband should have to spend so much time staring at seemingly stuck looking up/connecting/waiting for messages for suse.com/*.opensuse.org on a browser statusbar. DejaVu yester-century's dismal POTS connections. :~( -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: heroes+unsubscribe@opensuse.org To contact the owner, e-mail: heroes+owner@opensuse.org
Felix Miata wrote:
Per Jessen composed on 2019-09-16 10:15 (UTC+0200):
Felix Miata wrote:
Last night I put a DVD .iso on my website and emailed a link to it to a bunch of friends. Since then, bugzilla.opensuse.org and forums.opensuse.org frequently are unreachable or timeout in the middle of using them, such as trying to reply to a forum post, or load a saved bug search. At best the waits before *.o.o page load are 10 times as long as other sites. Even on good days most b.o.o searches totally timeout eventually into a blank page[1]. Startpage, Google, their hits and other commonly used sites (e.g. eBay) are producing no such trouble. I found that by stopping apache2 that b.o.o and f.o.o will become reachable shortly following "systemctl stop apache2".
I think this is really a support question.
At first that's what I thought, but...
What you do with apache2 on your side can hardly have much affect on the openSUSE infrastructure.
It seems like it shouldn't but what's happening is the openSUSE infrastructure latency problem is obviously being magnified when on my end a big upload is slowing traffic going through my router and/or my ISP's speed throttling. Turning off the upload by halting apache2 returns the latency to its usually tolerable pain level.
Which is not unexpected, I would think?
No one on broadband should have to spend so much time staring at seemingly stuck looking up/connecting/waiting for messages for suse.com/*.opensuse.org on a browser statusbar. DejaVu yester-century's dismal POTS connections. :~(
It is possible you have a particularly poor connection to our servers running in Nuernberg, and loading it up with other high-volume traffic onle exacerbates the problem. I just don't really see what we (openSUSE Heroes) can do about it? -- Per Jessen, Zürich (20.8°C) Member, openSUSE Heroes -- To unsubscribe, e-mail: heroes+unsubscribe@opensuse.org To contact the owner, e-mail: heroes+owner@opensuse.org
participants (2)
-
Felix Miata -
Per Jessen