Bug 492170

Summary: bug to track monitoring email notifications
Product: Red Hat Satellite 5 Reporter: wes hayutin <whayutin>
Component: MonitoringAssignee: Miroslav Suchý <msuchy>
Status: CLOSED CURRENTRELEASE QA Contact: wes hayutin <whayutin>
Severity: medium Docs Contact:
Priority: low    
Version: 530CC: bperkins, tlestach
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
URL: na
Whiteboard:
Fixed In Version: sat530 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 492169 Environment:
Last Closed: 2009-09-10 18:49:20 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 285651, 463877    
Attachments:
Description Flags
ss of monitoring email none

Description wes hayutin 2009-03-25 18:12:41 UTC 
+++ This bug was initially created as a clone of Bug #492169 +++

Description of problem:

currently probes are not sending email notifications.
Unfortunately I dont have any details right now.

recreate:
1. setup monitoring in spacewalk
2. create a probe that you know will go critical
3. setup the probe to send email notifications
4. wait for the probe to go critical

check your inbox...

right now we are not getting notifications.
Comment 1 Miroslav Suchý 2009-03-26 08:50:10 UTC 
Root of the problems are probabaly the same as https://bugzilla.redhat.com/show_bug.cgi?id=490783#c4
Leaving to trace it, since it is serious symptom.
Comment 2 Miroslav Suchý 2009-06-03 14:41:40 UTC 
this should work now. passing to qa
Comment 3 Miroslav Suchý 2009-06-05 12:58:00 UTC 
Moving ON_QA
QA Build: 20090529
Comment 4 wes hayutin 2009-06-05 13:35:28 UTC 
Created attachment 346649 [details]
ss of monitoring email

I think we can easily make the emails a little more professional looking.. :)
Comment 5 wes hayutin 2009-06-05 13:37:18 UTC 
great!! emails are working but not quite well enough to pass QA

Sending back to dev to get their opinion on:
1. adding a subject to the emails.
2. chaning the sender email address from <rogerthat01> to a real user on the box like nocpulse, root or something.

thanks
Comment 6 Miroslav Suchý 2009-06-05 14:20:35 UTC 
err of course QA build 20090605
Comment 7 Miroslav Suchý 2009-06-05 14:49:30 UTC 
No it should be rogerthat01, according to documentation you may want to setup notification acknowledgement. Although it is currently not working. See Bug 493028
Comment 8 wes hayutin 2009-06-08 16:22:44 UTC 
nice.. working..

This is RHN Monitoring Satellite notification 01hkb0rd.

Time:      Mon Jun 08, 12:18:41 EDT
State:     CRITICAL
Host:      dhcp77-159.rhndev.redhat.com (10.10.77.159)
Check:     Linux: Load
Message:   CPU load 5-min ave 0.07 (above critical threshold of 0.01); CPU load 15-min ave 0.16 (above critical threshold of 0.01); CPU load 1-min ave 0.00

Run from:  RHN Satellite Monitoring Scout

6/05
Comment 9 Tomas Lestach 2009-09-09 15:29:02 UTC 
Receiving notifications ... f.e:
========================================================
This is RHN Monitoring Satellite notification 01jcrxxd.

Time:      Wed Sep 09, 10:17:38 EDT
State:     CRITICAL
Host:      dhcp77-134.rhndev.redhat.com (10.10.77.134)
Check:     General: TCP Check
Message:   TCP port 1: connect: Connection refused
Notification #16 for connect: Connection refused

Run from:  RHN Satellite Monitoring Scout
========================================================

Stage validated -> RELEASE_PENDING
Comment 10 Brandon Perkins 2009-09-10 18:49:20 UTC 
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHEA-2009-1434.html