| 2009-09-24 13:23:35 |
Tom Haddon |
bug |
|
|
added bug |
| 2009-09-24 13:23:51 |
Tom Haddon |
removed subscriber Tom Haddon |
|
|
|
| 2009-10-08 21:08:28 |
Diogo Matsubara |
affects |
launchpad |
launchpad-registry |
|
| 2009-10-08 21:27:41 |
Diogo Matsubara |
tags |
|
mailing-lists |
|
| 2009-10-08 21:28:44 |
Diogo Matsubara |
launchpad-registry: status |
New |
Incomplete |
|
| 2009-10-09 08:06:42 |
Tom Haddon |
launchpad-registry: status |
Incomplete |
New |
|
| 2009-10-16 02:19:27 |
Curtis Hovey |
launchpad-registry: importance |
Undecided |
Low |
|
| 2009-10-16 02:19:27 |
Curtis Hovey |
launchpad-registry: status |
New |
Triaged |
|
| 2010-05-28 15:36:11 |
Tom Haddon |
tags |
mailing-lists |
canonical-losa-lp mailing-lists |
|
| 2011-07-28 23:26:13 |
Robert Collins |
summary |
Need a way to monitor mailman via nagios |
nagios cannot be sure mailman is really working ok |
|
| 2011-07-28 23:27:36 |
Robert Collins |
description |
The extent of our monitoring for mailman at the moment is a process check for mailmanctl. We need a proper nagios check that confirms mailman is working correctly, as during the 3.0 rollout our nagios check was telling us everything was okay, but this wasn't the case. |
The extent of our monitoring for mailman at the moment is a process check for mailmanctl / a heartbeat in the log files.
This does not cover end to end operations and things like archiver backlogs will not trigger nagios alerts.
One way to solve this is a tiny process that continually sends and probes for email to be sure its working. There may even be a helper Out There for nagios to do this already. |
|
| 2011-11-16 19:53:38 |
Francis J. Lacoste |
launchpad: importance |
Low |
Critical |
|
| 2013-01-08 22:33:16 |
Curtis Hovey |
launchpad: importance |
Critical |
High |
|
| 2021-04-13 00:41:37 |
Colin Watson |
affects |
launchpad |
lp-mailman |
|
