Bug 201887

Summary: Timeout if accessing bugzilla dashboard sub-link
Product: Services Reporter: Kurt Jaeger <pi>
Component: Bug TrackerAssignee: Oleksandr Tymoshenko <gonzo>
Status: Closed Overcome By Events    
Severity: Affects Only Me CC: dbn, gonzo, pi
Priority: ---    
Version: unspecified   
Hardware: Any   
OS: Any   

Description Kurt Jaeger freebsd_committer freebsd_triage 2015-07-26 09:05:48 UTC
If I access the dashboard of bugzilla:
     
https://bugs.freebsd.org/bugzilla/page.cgi?id=dashboard.html
     
this works, but if I access the link for
     
'Ports bugs, that do not have been looked at yet'
     
the following error appears:
     
504 Gateway Time-out
nginx/1.8.0

The problem has started somewhere around January 2015.
Comment 1 David Naylor freebsd_committer freebsd_triage 2015-10-19 18:49:41 UTC
I have been unable to reproduce this error (tried using Firefox, Chrome and Rekonq - for good measure).
Comment 2 Kurt Jaeger freebsd_committer freebsd_triage 2015-11-09 07:33:54 UTC
Works in bugzilla 5.0.
Comment 3 Kurt Jaeger freebsd_committer freebsd_triage 2015-11-17 17:31:44 UTC
(In reply to David Naylor from comment #1)

I can reproduce it via PPPoE/DSL and mtu 1500.

I can't reproduce it via some generic ethernet-link.
Comment 4 Marcus von Appen freebsd_committer freebsd_triage 2015-12-30 12:09:10 UTC
Kurt: can you give it another try and tell us, if it works for you after the upgrade?
Comment 5 Kurt Jaeger freebsd_committer freebsd_triage 2015-12-30 20:45:54 UTC
I can still reproduce the bug behind the DSL/PPPoE link, this time with MTU 1450.

Error is:

504 Gateway Time-out
nginx/1.8.0

I'll try to reproduce from the office in a few days.
Comment 7 Kurt Jaeger freebsd_committer freebsd_triage 2016-02-25 20:52:45 UTC
I tried to access the link with 10.2p7-amd64, and lower MTU (1440), problem
still persists. I can access the "Bugs waiting for feedback (flags) for more than 14 days" dashboard link, which returns a much larger result set.
Comment 8 Kurt Jaeger freebsd_committer freebsd_triage 2016-02-25 20:53:31 UTC
Browser is firefox 44.0.2. Happened with older ff browsers, too.
Comment 9 Kurt Jaeger freebsd_committer freebsd_triage 2016-03-17 21:14:56 UTC
I found a reproducable test-case.

If I query

https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=New&email1=freebsd-port
s-bugs%40FreeBSD.org&emailassigned_to1=1&emailtype1=exact&f1=longdescs.count&o1=
equals&product=Ports%20%26%20Packages

the timeout does not happen.

If I query

https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=New&email1=freebsd-port
s-bugs%40FreeBSD.org&emailassigned_to1=1&emailtype1=exact&f1=longdescs.count&o1=
equals&product=Ports%20%26%20Packages&v1=1

the timeout happens. The difference is the 'v1=1' at the end of the query. If it is missing, the query succeeds.
Comment 10 Oleksandr Tymoshenko freebsd_committer freebsd_triage 2018-02-13 07:52:25 UTC
Kurt, is this bug still reproducible? I can't reproduce it with the link your provided.

There were some fixes on nginx front-end regarding "502 Bad Gateway" error so they might have affected this issue to.

Thanks
Comment 11 Oleksandr Tymoshenko freebsd_committer freebsd_triage 2018-04-16 21:43:33 UTC
Closing as OBE since I can't reproduce the issue.