Bug 1100506 - some searches routinely timeout or otherwise fail to return a result page
Summary: some searches routinely timeout or otherwise fail to return a result page
Status: CONFIRMED
Alias: None
Product: openSUSE.org
Classification: openSUSE
Component: Bugzilla (show other bugs)
Version: unspecified
Hardware: Other Other
: P5 - None : Major (vote)
Target Milestone: ---
Assignee: Ryan Wilson
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-07-08 01:12 UTC by Felix Miata
Modified: 2020-02-16 12:24 UTC (History)
2 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Comment 1 Felix Miata 2019-02-08 00:56:58 UTC
This saved search:
https://bugzilla.opensuse.org/buglist.cgi?cmdtype=runnamed&namedcmd=all%20my%20bugs normally runs quickly but
when edited to add a check to checkbox CC in the first search by people list, which already has reporter checked, plus adding a search keyword in the comment box plymouth repeatedly either times out or returns the following:

Secure Connection Failed

The document contains no data.

The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.

    Please contact the website owners to inform them of this problem.

Clicking try again just creates another long delay followed by the same useless response.
Comment 2 Felix Miata 2019-08-07 08:08:00 UTC
The following is what happens when I try finding a comment from Stefan Dirsch about G200 video in Chromium on 15.1:

This site can’t be reached The connection was reset.
Try:

Checking the connection
Checking the proxy and the firewall
ERR_CONNECTION_RESET
Comment 3 Felix Miata 2019-08-31 20:40:36 UTC
This has become nearly standard behavior. Few searches fail to timeout with same message as comments 1 and 2, UNLESS I log out first, in which case behavior is normal. Logging out is a horrible workaround, because I'm constantly on the forums, and often elsewhere where I need to be logged in to see what needs seeing and can't be without being logged in. Also, logging in or out from BOO or forums is an obnoxiously slow process which is less so on the wiki and progress.o.o.

Most recent timing out search: https://bugzilla.opensuse.org/buglist.cgi?chfieldfrom=22m&chfieldto=Now&list_id=12265031&longdesc=amdgpu.dc%3D0&longdesc_type=substring&query_format=advanced
Comment 4 Felix Miata 2019-09-20 21:16:23 UTC
This has regressed to virtually always, except for saved searches. This includes simple searches.
Comment 5 Dave Howorth 2020-02-15 16:24:22 UTC
(In reply to Felix Miata from comment #3)
> This has become nearly standard behavior. Few searches fail to timeout with
> same message as comments 1 and 2, UNLESS I log out first, in which case
> behavior is normal. Logging out is a horrible workaround, because I'm
> constantly on the forums, and often elsewhere where I need to be logged in
> to see what needs seeing and can't be without being logged in. Also, logging
> in or out from BOO or forums is an obnoxiously slow process which is less so
> on the wiki and progress.o.o.
> 
> Most recent timing out search:
> https://bugzilla.opensuse.org/buglist.
> cgi?chfieldfrom=22m&chfieldto=Now&list_id=12265031&longdesc=amdgpu.
> dc%3D0&longdesc_type=substring&query_format=advanced

I just tried the search listed above. It's sitting there saying "Bugzilla is pondering ... (something) ..." and "Please stand by" and after a long time it has gone to:

"Secure Connection Failed

"An error occurred during a connection to bugzilla.opensuse.org.

    "The page you are trying to view cannot be shown because the authenticity of
    the received data could not be verified.
    Please contact the web site owners to inform them of this problem."
Comment 6 Mykola Krachkovsky 2020-02-16 12:24:58 UTC
This fails affects not only searches, but other actions also, like creating of report. E.g. you can see my duplicates [1]-[4] were created because each time I've got error, so I filed report again and again.

And after typing report topic "Possible duplicates" are often empty due to this search problem.

[1] https://bugzilla.opensuse.org/show_bug.cgi?id=1143136
[2] https://bugzilla.opensuse.org/show_bug.cgi?id=1143137
[3] https://bugzilla.opensuse.org/show_bug.cgi?id=1143138
[4] https://bugzilla.opensuse.org/show_bug.cgi?id=1143139