Bugzilla – Full Text Bug Listing
| Summary: | Bugzilla internal error sending change mails - no notifications sent | ||
|---|---|---|---|
| Product: | Community | Reporter: | Michael Keppler <michael.keppler> |
| Component: | Bugzilla | Assignee: | Eclipse Webmaster <webmaster> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | blocker | ||
| Priority: | P3 | CC: | christian.dietrich.opensource, daniel_megert, denis.roy, dev, frederic.gurr, jonah, loskutov, lshanmug, mikael.barbero, pierre-charles.david, walther |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 10 | ||
| Whiteboard: | |||
|
Description
Michael Keppler
In fact, even creating this bug led to the same issue: There was an error sending mail from 'bugzilla-daemon@eclipse.org' to 'denis.roy@eclipse-foundation.org': 4.1.8 <bugzilla-daemon@eclipse.org>: Sender address rejected: Domain not found Traceback: at /localsite/Bugzilla/Mailer.pm line 179. Bugzilla::Mailer::MessageToMTA(...) called at /localsite/Bugzilla/BugMail.pm line 381 Bugzilla::BugMail::sendMail(...) called at /localsite/Bugzilla/BugMail.pm line 269 Bugzilla::BugMail::Send(...) called at /localsite/post_bug.cgi line 208 ModPerl::ROOT::Bugzilla::ModPerl::ResponseHandler::localsite_post_bug_2ecgi::handler(...) called at /usr/lib/perl5/vendor_perl/5.18.2/x86_64-linux-thread-multi/ModPerl/RegistryCooker.pm line 206 eval {...} called at /usr/lib/perl5/vendor_perl/5.18.2/x86_64-linux-thread-multi/ModPerl/RegistryCooker.pm line 206 ModPerl::RegistryCooker::run(...) called at /usr/lib/perl5/vendor_perl/5.18.2/x86_64-linux-thread-multi/ModPerl/RegistryCooker.pm line 172 ModPerl::RegistryCooker::default_handler(...) called at /usr/lib/perl5/vendor_perl/5.18.2/x86_64-linux-thread-multi/ModPerl/Registry.pm line 31 ModPerl::Registry::handler(...) called at /localsite/mod_perl.pl line 137 Bugzilla::ModPerl::ResponseHandler::handler(...) called at -e line 0 eval {...} called at -e line 0 Notifications are no longer sent! *** Bug 542613 has been marked as a duplicate of this bug. *** Possibly related, I don’t seem to be getting any emails from Gerrit either. Another duplicate: bug 542608. I see some bugzilla notifications flowing now... ok thx (In reply to Denis Roy from comment #5) > I see some bugzilla notifications flowing now... I see some too, but only new ones. What about the "lost" ones? *** Bug 542608 has been marked as a duplicate of this bug. *** If bugzilla ended with a traceback, then the old ones never got sent :/ (In reply to Denis Roy from comment #9) > If bugzilla ended with a traceback, then the old ones never got sent :/ Do you know when it started to fail? That would allow us to do a search for bugs that changed since then. *** NOTE *** While changes to bug reports no longer give an error, I did not get any e-mail about the recent changes in this bug, e.g. for comment 9, made 20 minutes ago! (In reply to Dani Megert from comment #11) > *** NOTE *** > > While changes to bug reports no longer give an error, I did not get any > e-mail about the recent changes in this bug, e.g. for comment 9, made 20 > minutes ago! I did get Comment 9. I do see that emails going through Eclipse are very delayed. e.g. a gerrit comment had a 10 minute delay: Received: from mail.eclipse.org (mail.eclipse.org [198.41.30.200]) by pb-mx23.pobox.com (Postfix) with SMTP for <jonah@kichwacoders.com>; Mon, 10 Dec 2018 10:44:15 -0500 (EST) (envelope-from gerrit@eclipse.org) Received: from gerrit-vm1.eclipse.org (unknown [172.30.3.253]) by mail.eclipse.org (Postfix) with ESMTP id C1D202DD054; Mon, 10 Dec 2018 10:44:14 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by gerrit-vm1.eclipse.org (Postfix) with ESMTP id 7227718E8828; Mon, 10 Dec 2018 10:36:20 -0500 (EST) But the log for Comment 9 email shows no delay: Received: from mail.eclipse.org (mail.eclipse.org [198.41.30.200]) by pb-mx9.pobox.com (Postfix) with SMTP for <jonah@kichwacoders.com>; Mon, 10 Dec 2018 10:22:26 -0500 (EST) Received: from bugs-vm1.eclipse.org (unknown [172.30.3.253]) by mail.eclipse.org (Postfix) with ESMTP id 191C22DD134 for <jonah@kichwacoders.com>; Mon, 10 Dec 2018 10:22:26 -0500 (EST) Received: from bugs.eclipse.org (localhost [127.0.0.1]) by bugs-vm1.eclipse.org (Postfix) with ESMTP id 40E6661EFD for <jonah@kichwacoders.com>; Mon, 10 Dec 2018 10:22:26 -0500 (EST) (In reply to Jonah Graham from comment #12) So far I did not get any e-mail for your comment made at 2018-12-10 16:48:04 CET. Things are flushing out. We're making changes to our core gateways, and this is some of the dust. Apologies for the inconvenience. All Mail should be stabilizing and flushing itself out. These changes started Friday, around noon Ottawa time. (In reply to Denis Roy from comment #14) > Things are flushing out. We're making changes to our core gateways, and this > is some of the dust. > > Apologies for the inconvenience. All Mail should be stabilizing and flushing > itself out. > > These changes started Friday, around noon Ottawa time. I got this just now, but no notification for comment 12 so far. (In response to request on cross-project to resend lost emails) Hi Mikaël/webmasters, I think the emails may actually not be permanently lost. I think bugzilla knows what it hasn't sent out. However I don't know how to get bugzilla to send them. For example, I just made a comment on Bug 542613 - one of the bugs that emails didn't get sent out the other day for - and the one email contained all the comments/edits made. As this email was cc'ed to webmaster@eclipse.org perhaps you have just received that too. Thanks, Jonah Yeah, the problem is that it only does that if another comment is added to the bug (or something else is changed?) after it works again.
> I think the emails may actually not be permanently lost. I think bugzilla
> knows what it hasn't sent out. However I don't know how to get bugzilla to
> send them.
That is correct. I just discovered the "flush bugmail queue" tool.
586 bugs found with possibly unsent mail. Sending mail for bug 33184... 9 mails sent. Took 1 seconds. Sending mail for bug 68836... 13 mails sent. Took 2 seconds. Uh oh.... (In reply to Denis Roy from comment #19) > 586 bugs found with possibly unsent mail. > > Sending mail for bug 33184... > 9 mails sent. > Took 1 seconds. > > Sending mail for bug 68836... > 13 mails sent. > Took 2 seconds. > > > Uh oh.... Probably related to this, but since a few minutes ago I've started receiving bugzilla notification mail for changes dating back from 2013. 26 mails for now. Oops, make that 28 now :) > Uh oh....
*sigh*
I think there were a bunch of silently queued emails over the last, oh, decade.
I've stopped the process since the webmaster inbox is filling up with old, stale email notifications. (In reply to Denis Roy from comment #22) > I've stopped the process since the webmaster inbox is filling up with old, > stale email notifications. Thanks. This was really a bad move! I now have to sort out all those old miles out of over 50 notifications. And the bad thing is, that the messages does not contain the change(d) date, hence I have to look at every single one. Marking as FIXED, because I don't think more is going to happen here. |