Last modified: 2013-10-08 22:11:16 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T56876, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 54876 - Error 504 Gateway Time-out on Special:Log/INeverCry and others
Error 504 Gateway Time-out on Special:Log/INeverCry and others
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
Logging (Other open bugs)
1.22.0
All All
: High major (vote)
: ---
Assigned To: Nobody - You can work on this!
https://commons.wikimedia.org/wiki/Sp...
: performance, platformeng
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2013-10-02 15:10 UTC by Nemo
Modified: 2013-10-08 22:11 UTC (History)
8 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Nemo 2013-10-02 15:10:45 UTC 
Trijnstel reports that for users like INeverCry, Fastily, Túrelio and Herbythyme it's impossible to load Special:Log: it keeps loading and finally timeouts, Error 504 Gateway Time-out by nginx.
Setting a low limit doesn't help, while adding a type filter does, e.g. https://commons.wikimedia.org/w/index.php?title=Special%3ALog&type=block&user=INeverCry

Those are all users with tens of thousands log entries.
Comment 1 Gerrit Notification Bot 2013-10-02 18:30:35 UTC 
Change 87168 had a related patch set uploaded by Aaron Schulz:
Removed more FORCE INDEX clauses for logging

https://gerrit.wikimedia.org/r/87168
Comment 2 Gerrit Notification Bot 2013-10-03 06:34:04 UTC 
Change 87168 merged by jenkins-bot:
Removed more FORCE INDEX clauses for logging

https://gerrit.wikimedia.org/r/87168
Comment 3 Andre Klapper 2013-10-05 09:25:10 UTC 
Is more work needed or can this be closed after Aaron's patch got merged?
Comment 4 Trijnstel 2013-10-05 21:22:00 UTC 
(In reply to comment #3)
> Is more work needed or can this be closed after Aaron's patch got merged?

Don't know. I only know that I also see this happen on another wiki, nlwiki.
Comment 6 Trijnstel 2013-10-07 19:51:13 UTC 
Could someone please fix this? It's quite a major bug.
Comment 7 Nemo 2013-10-08 15:56:29 UTC 
(In reply to comment #6)
> Could someone please fix this? It's quite a major bug.

I'm confused, the fix was made live yesterday on Commons few minutes before you wrote this comments and the example URL works; marking fixed, please reopen if it's not.
In 2 days this will land on Wikipedias too.
Comment 8 Trijnstel 2013-10-08 20:32:27 UTC 
(In reply to comment #7)
> (In reply to comment #6)
> > Could someone please fix this? It's quite a major bug.
> 
> I'm confused, the fix was made live yesterday on Commons few minutes before
> you
> wrote this comments and the example URL works; marking fixed, please reopen
> if
> it's not.
> In 2 days this will land on Wikipedias too.

Ah, I guess that's why. I checked it on nlwiki when I replied here yesterday.
Comment 9 MZMcBride 2013-10-08 22:11:16 UTC 
I don't understand why a fix for this wasn't deployed immediately.
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links