Page MenuHomePhabricator
Create Task
Maniphest T61429

DRTRIGON-87 Bot ERROR mail cannot be sent sometimes
Closed, ResolvedPublic
Actions

Description

This issue was converted from https://jira.toolserver.org/browse/DRTRIGON-87.
Summary: Bot ERROR mail cannot be sent sometimes
Issue type: Bug - A problem which impairs or prevents the functions of the product.
Priority: Critical
Status: Closed
Assignee: drtrigon <dr.trigon@surfeu.ch>

From: drtrigon <dr.trigon@surfeu.ch>

Date: Sun, 20 Feb 2011 11:44:05

2011/02/20 12:06:49:: Sending mail "Bot ERROR" to "DrTrigon" as notification!

2011/02/20 12:06:49:: !!! WARNING: mail could not be sent!

Even though it was tested explicit it seams that it is very frequent for bot ERROR mails not to be sent to me. This is a critical issue since it may happen that I am not informed about such a crash. Another point is this error reporting has to be reliable ! This might be an issue with SGE too, thus look also at http://lists.wikimedia.org/pipermail/toolserver-l/2011-February/003901.html and its follow-ups.

Version: unspecified
Severity: critical

Details

Reference
bz59429

Event Timeline

• bzimport raised the priority of this task from to Needs Triage.Nov 22 2014, 2:30 AM
• bzimport added a project: Tool-DrTrigonBot---General.
• bzimport set Reference to bz59429.
JiraBugConverter created this task.Jan 3 2014, 4:06 PM
JiraBugConverter added a comment.Jan 3 2014, 4:06 PM

From: drtrigon <dr.trigon@surfeu.ch>

Date: Sun, 10 Jul 2011 21:17:06

First attempt to solve this issue is to add max. 3 retries for the mail sending. Additionally output of the error occurred was added to get more info.

Committed revision 124.

If this does not work try to add:

  • delay between attempts
  • re-create user object or do something else to retrieve new token
JiraBugConverter added a comment.Jan 3 2014, 4:06 PM

From: drtrigon <dr.trigon@surfeu.ch>

Date: Tue, 26 Jul 2011 08:28:53

Look at http://lists.wikimedia.org/pipermail/pywikipedia-l/2011-July/006885.html and follow-ups for a discussion about this issue.

JiraBugConverter added a comment.Jan 3 2014, 4:06 PM

From: drtrigon <dr.trigon@surfeu.ch>

Date: Thu, 25 Aug 2011 10:54:52

Solved by introducing a work-a-round in r149.
Bug report https://sourceforge.net/tracker/?func=detail&aid=3397944&group_id=93107&atid=603138 filed in order to solve this issue upstream. Then in fact the work-a-round would not be needed anymore, but does no harm also.

JiraBugConverter added a comment.Jan 3 2014, 4:06 PM

This bug was imported as RESOLVED. The original assignee has therefore not been
set, and the original reporters/responders have not been added as CC, to
prevent bugspam.

If you re-open this bug, please consider adding these people to the CC list:
Original assignee: dr.trigon@surfeu.ch
CC list: dr.trigon@surfeu.ch

Content licensed under Creative Commons Attribution-ShareAlike (CC BY-SA) 4.0 unless otherwise noted; code licensed under GNU General Public License (GPL) 2.0 or later and other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL