#34174: Update majus errors recipient -------------------------------------------------+------------------------- Reporter: antonela | Owner: anarcat Type: defect | Status: closed Priority: Medium | Milestone: Component: Internal Services/Tor Sysadmin Team | Version: Severity: Normal | Resolution: fixed Keywords: | Actual Points: Parent ID: | Points: Reviewer: | Sponsor: -------------------------------------------------+-------------------------
Comment (by sysrqb): Replying to [comment:6 anarcat]: > done. i recommend you somehow simulate a failure to make sure you still receive notifications. I can also try to see if we can do that straight from nagios if you prefer. Thanks anarcat. Instead of simulating a failure we (accidentally) broke the system instead (and triggered alerts from nagios). Long(er) story, short, now we know the nagios alerts are reaching the new mailing list. {{{ Subject: [translation-admin] ** PROBLEM Service Alert: majus/translation cron - stuck is CRITICAL ** Subject: [translation-admin] ** RECOVERY Service Alert: majus/translation cron - stuck is OK ** }}} I think we are done here. -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/34174#comment:7> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online
_______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs