Last modified: 2012-08-15 18:16:11 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 T40584, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 38584 - There was an error sending mail from 'bugzilla-daemon@wikimedia.org': Can't send data
There was an error sending mail from 'bugzilla-daemon@wikimedia.org': Can't s...
Status: RESOLVED FIXED
Product: Wikimedia
Classification: Unclassified
Bugzilla (Other open bugs)
unspecified
All All
: Unprioritized major (vote)
: ---
Assigned To: Nobody - You can work on this!
: ops
: 37762 (view as bug list)
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-07-22 19:51 UTC by matanya
Modified: 2012-08-15 18:16 UTC (History)
10 users (show)

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


Attachments
screenshot of the error (70.47 KB, image/png)
2012-07-22 19:51 UTC, matanya
Details

Description matanya 2012-07-22 19:51:15 UTC
Created attachment 10871 [details]
screenshot of the error

for the third time today:


Bugzilla has suffered an internal error. Please save this page and send it to noc@wikimedia.org with details of what you were doing at the time this message appeared.

URL: https://bugzilla.wikimedia.org/process_bug.cgi
There was an error sending mail from 'bugzilla-daemon@wikimedia.org' to 'tstarling@wikimedia.org':Can't send data

Traceback:


 at Bugzilla/Mailer.pm line 186
	Bugzilla::Mailer::MessageToMTA(...) called at Bugzilla/BugMail.pm line 594
	Bugzilla::BugMail::sendMail(...) called at Bugzilla/BugMail.pm line 434
	Bugzilla::BugMail::Send(...) called at Bugzilla/Bug.pm line 1201
	Bugzilla::Bug::_send_bugmail(...) called at Bugzilla/Bug.pm line 1150
	Bugzilla::Bug::send_changes(...) called at /srv/org/wikimedia/bugzilla/process_bug.cgi line 391
Comment 1 Andre Klapper 2012-08-06 11:28:08 UTC
Hi Matanya,
is this reproducible or did this just happen once?
Comment 2 matanya 2012-08-06 11:31:01 UTC
Happens every so often. Can't tell why or when.
Comment 3 Andre Klapper 2012-08-06 11:38:44 UTC
Would be great if you could try to find some pattern, like bug report numbers (e.g. belonging all to the same product) or if it is always the same specific email address (tstarling) that you get the error for.
Comment 4 Alex Monk 2012-08-06 14:49:07 UTC
I've got this for a couple of different addresses.
Comment 5 Niklas Laxström 2012-08-14 08:16:22 UTC
*** Bug 37762 has been marked as a duplicate of this bug. ***
Comment 6 Niklas Laxström 2012-08-14 08:17:04 UTC
Just got it twice in row.
Comment 7 matanya 2012-08-14 12:20:21 UTC
got one now. this time a mail to reedy.
Comment 8 jeremyb 2012-08-14 20:09:55 UTC
I've had this several times as well. (not yet today but all within the last 2 weeks I think)
Comment 9 Rob Lanphier 2012-08-15 01:29:24 UTC
filed as RT #3428
Comment 10 Daniel Zahn 2012-08-15 02:23:48 UTC
while i can confirm some temp. rejects from the mailserver for reedy's address i do not see the one for tstarling@ at all so far.. also commenting here trying to reproduce...
Comment 11 Daniel Zahn 2012-08-15 17:30:45 UTC
ok, i could find one occurence when tstarling@wm was temp. rejected due to DNS issues resolving the Google servers.. that was on August 6th:

August 6th... "temporarily rejected RCPT <tstarling@wikimedia.org>: host lookup for aspmx.l.google.com did not complete (DNS timeout?)".

Will look into ways to stop it from trying to send all mails immediately and use queuing instead, so if one address happens to fail temporary it should not give all users the error screen.
Comment 12 Daniel Zahn 2012-08-15 18:09:04 UTC
changed mail delivery method to sendmail (alias for local exim4). test
Comment 13 Daniel Zahn 2012-08-15 18:16:11 UTC
Since Bugzilla now does not deliver directly to mchenry anymore and local exim does not verify this should now be resolved.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links