Bug 697867 - smartd prints "internal error in MailWarning(): cfg.mailwarn->emailfreq=0" when no mailaddress is specified
smartd prints "internal error in MailWarning(): cfg.mailwarn->emailfreq=0" wh...
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: smartmontools (Show other bugs)
6.0
All Linux
urgent Severity high
: rc
: 6.2
Assigned To: Michal Hlavinka
qe-baseos-tools
:
Depends On:
Blocks: GSS_6_2_PROPOSED
  Show dependency treegraph
 
Reported: 2011-04-19 09:53 EDT by Christian Horn
Modified: 2013-01-10 22:57 EST (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Prior to this update, when a system event relevant to smartd happened, the following spurious error message was output if no mail address was configured: "smartd: internal error in MailWarning(): cfg.mailwarn->emailfreq=0" This unintended behavior has been fixed in this update so that the spurious error message is no longer displayed.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2011-08-24 06:56:46 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)
the patch at currently used (6.80 KB, patch)
2011-05-06 06:15 EDT, Christian Horn
no flags Details | Diff
the patch as suggested/fixed version (6.49 KB, patch)
2011-05-06 06:16 EDT, Christian Horn
no flags Details | Diff

  None (edit)
Description Christian Horn 2011-04-19 09:53:32 EDT
Description of problem:
smartd not only outputs the relevant event notification but also message:
"smartd: internal error in MailWarning(): cfg.mailwarn->emailfreq=0"

Version-Release number of selected component (if applicable):
5.39.1-2.el6

How reproducible:
always

Steps to Reproduce:
1. # config example applies to ata/sata harddisc
   # the relevant part is that no -m mail@domain.tld is specified
   echo '/dev/sda -a -d sat' >/etc/smartd.conf
2. echo 'smartd_opts="-q never"' >/etc/sysconfig/smartmontools
3. service smartd restart
4. have a smartd relevant event happening, i.e. disc failure
  
Actual results:
output of event notification in syslog
smartd: internal error in MailWarning(): cfg.mailwarn->emailfreq=0

Expected results:
output of event notification in syslog

Additional info:
- the problem is not in unpatched smartmontools-5.39.1
- patch smartmontools-5.38-lowcap.patch removes a check which checks in
function MailWarning if mails are configured.
Removing lines 99-108 should solve the problem.
Comment 1 Michal Hlavinka 2011-04-19 10:55:22 EDT
> Removing lines 99-108 should solve the problem.

yes, this section of the patch should be removed
Comment 2 Christian Horn 2011-05-06 06:15:27 EDT
Created attachment 497319 [details]
the patch at currently used
Comment 3 Christian Horn 2011-05-06 06:16:14 EDT
Created attachment 497320 [details]
the patch as suggested/fixed version
Comment 4 Christian Horn 2011-05-06 06:17:03 EDT
Can we get the required ACKs once RHEL6.1 is GA?
Comment 14 Petr Kovar 2011-08-04 10:09:20 EDT
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Prior to this update, when a system event relevant to smartd happened, the following spurious error message was output if no mail address was configured: 

"smartd: internal error in MailWarning(): cfg.mailwarn->emailfreq=0" 

This unintended behavior has been fixed in this update so that the spurious error message is no longer displayed.
Comment 15 errata-xmlrpc 2011-08-24 06:56:46 EDT
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/RHBA-2011-1201.html

Note You need to log in before you can comment on or make changes to this bug.