Bug 1661887 - Add monitoring of postgrey
Summary: Add monitoring of postgrey
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: project-infrastructure
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-12-24 09:07 UTC by M. Scherer
Modified: 2019-01-03 13:32 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-01-03 13:32:29 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

Description M. Scherer 2018-12-24 09:07:32 UTC 
Following the migration of the server, postgrey didn't restart and this wasn't managed by ansible, nor monitored. This did block mail delivery (no mail should have been lost however).

Postgrey should be monitored, and managed.
Comment 1 M. Scherer 2019-01-03 13:32:29 UTC 
So, notification was added, and I think it is also managed properly now.
Note You need to log in before you can comment on or make changes to this bug.