Zandronum Chat on our Discord Server Get the latest version: 3.2
Source Code

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0003529Site[All Projects] Bugpublic2018-10-01 04:442018-10-04 04:39
ReporterWubTheCaptain 
Assigned ToBlzut3 
PriorityimmediateSeveritymajorReproducibilitysometimes
StatusclosedResolutionno change required 
PlatformOSOS Version
Summary0003529: Issue tracker write operations take unreasonably long time and are blocking I/O for that account
DescriptionSince sometime today (possibly after 1000+ issues were closed), almost every write operation such as editing ticket details or adding a note takes around 3 minutes to finish, during which time the issue tracker is not usable except in incognito mode for read-only while not logged in.

Unbreak now.
Attached Filespng file icon 2018-10-01-045720_1267x868_scrot.png [^] (471,956 bytes) 2018-10-01 05:01

- Relationships

-  Notes
User avatar (0019853)
WubTheCaptain (reporter)
2018-10-01 04:56

I've been enduring this for few hours and thought to wait for it to go away, but a ticket is better than no ticket.

This issue is also visible in issue histories, such as 0003483's:

2018-10-01 06:56 	WubTheCaptain		Relationship deleted 	related to 0003479
2018-10-01 06:59 	WubTheCaptain		Relationship deleted 	related to 0003482
2018-10-01 07:01 	WubTheCaptain		Relationship deleted 	related to 0003505
User avatar (0019855)
WubTheCaptain (reporter)
2018-10-01 05:03

Also, the "last update" date is severely wrong but probably unrelated to this issue (as in attachment, which demonstrates this and the issue tracker being very slow to respond). Although, in browser incognito mode the notes and updates go live much faster, it still makes that account unusable for a good while.
User avatar (0019856)
Blzut3 (administrator)
2018-10-01 05:03

It should clear up in 24 hours. That said if you are going to make a ticket like this you should probably refrain from "unbreak now." :P
User avatar (0019857)
WubTheCaptain (reporter)
2018-10-01 05:05

Quote from Blzut3
you should probably refrain from "unbreak now." :P


It's a priority level at Wikimedia Foundation (in MediaWiki software development, for example). :P

'https://www.mediawiki.org/w/index.php?title=Phabricator/Project_management&oldid=2865675#Priority_levels [^]'
User avatar (0019879)
WubTheCaptain (reporter)
2018-10-02 05:35

Progress report? The outbound email server (my guess) is still clogged.
User avatar (0019896)
Blzut3 (administrator)
2018-10-03 23:09

Based on the emails I'm getting today, I think surprisingly it's working through the backlog. I thought it would just drop them.
User avatar (0019897)
Blzut3 (administrator)
2018-10-04 00:01

OK learned about Mantis's email que and cleared out the remaining 222 emails about tickets being closed.
User avatar (0019900)
Blzut3 (administrator)
2018-10-04 03:27

Seems to be clear now, if not it will definitely clear up very soon.
User avatar (0019901)
WubTheCaptain (reporter)
2018-10-04 04:33

I don't think this issue is seemingly resolved from what I can read from the notes. "No change required" is not the right solution here either, you've done something to have temporarily "fixed" it. Someday someone may inevitably run into this issue again, and the blame may be on MantisBT's code or the existing email infrastructure.

I've said "unbreak now" in the OP for a reason.

Quote from Blzut3
I think surprisingly it's working through the backlog. I thought it would just drop them.


MTAs never drop email, they must accept it for delivery or generate a bounce as designed. "It MUST NOT lose the message for frivolous reasons, such as because the host later crashes or because of a predictable resource shortage." This is hardly surprising to me. (RFC 5321, section 6.1)

Besides: Have you tried OpenSMTPD for a local MTA to relay messages (like an MSA)? Please do. What steps will the site administration take to prevent this issue from happening again?
User avatar (0019902)
Blzut3 (administrator)
2018-10-04 04:37
edited on: 2018-10-04 04:39

I put no change required since I did nothing but sit back and relax. (Well except flushing the queue, but lets be real here.)

The software is doing what it's supposed to do, we're just using free services and they have limits. There's nothing to do here.

Un-pedant now. :P

Edit: and at the typical volume of traffic that we have I have better things to do with my time then setup an SMTP server.


Issue Community Support
This issue is already marked as resolved.
If you feel that is not the case, please reopen it and explain why.
Supporters: No one explicitly supports this issue yet.
Opponents: No one explicitly opposes this issue yet.

- Issue History
Date Modified Username Field Change
2018-10-01 04:44 WubTheCaptain New Issue
2018-10-01 04:56 WubTheCaptain Note Added: 0019853
2018-10-01 05:01 WubTheCaptain File Added: 2018-10-01-045720_1267x868_scrot.png
2018-10-01 05:03 WubTheCaptain Note Added: 0019855
2018-10-01 05:03 Blzut3 Note Added: 0019856
2018-10-01 05:05 WubTheCaptain Note Added: 0019857
2018-10-02 05:35 WubTheCaptain Note Added: 0019879
2018-10-03 02:19 Blzut3 Assigned To => Blzut3
2018-10-03 02:19 Blzut3 Status new => assigned
2018-10-03 23:09 Blzut3 Note Added: 0019896
2018-10-04 00:01 Blzut3 Note Added: 0019897
2018-10-04 03:27 Blzut3 Note Added: 0019900
2018-10-04 03:27 Blzut3 Status assigned => closed
2018-10-04 03:27 Blzut3 Resolution open => no change required
2018-10-04 04:33 WubTheCaptain Note Added: 0019901
2018-10-04 04:33 WubTheCaptain Status closed => feedback
2018-10-04 04:33 WubTheCaptain Resolution no change required => reopened
2018-10-04 04:37 Blzut3 Note Added: 0019902
2018-10-04 04:37 Blzut3 Status feedback => closed
2018-10-04 04:37 Blzut3 Resolution reopened => no change required
2018-10-04 04:39 Blzut3 Note Edited: 0019902 View Revisions






Questions or other issues? Contact Us.

Links


Copyright © 2000 - 2025 MantisBT Team
Powered by Mantis Bugtracker