Description of problem: smartmontools tried to send a message because a USB hard drive was powered off by the cleaners: Oct 23 18:50:36 mik-desktop smartd[810]: Device: /dev/sdc [USB JMicron], open() failed: No such device Oct 23 18:50:36 mik-desktop smartd[810]: Sending warning via /usr/libexec/smartmontools/smartdnotify to root ... Oct 23 18:50:36 mik-desktop smartd[810]: Warning via /usr/libexec/smartmontools/smartdnotify to root produced unexpected output (70 bytes) to STDOUT/STDERR: Oct 23 18:50:36 mik-desktop smartd[810]: /usr/sbin/sendmail: No such file or directory Oct 23 18:50:36 mik-desktop smartd[810]: . . . message not sent. Oct 23 18:50:36 mik-desktop smartd[810]: Warning via /usr/libexec/smartmontools/smartdnotify to root: successful SELinux is preventing /usr/bin/mailx from 'write' accesses on the directory /. ***** Plugin catchall (100. confidence) suggests *************************** If you believe that mailx should be allowed write access on the directory by default. Then you should report this as a bug. You can generate a local policy module to allow this access. Do allow this access for now by executing: # grep mail /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context system_u:system_r:system_mail_t:s0 Target Context system_u:object_r:root_t:s0 Target Objects / [ dir ] Source mail Source Path /usr/bin/mailx Port <Unknown> Host (removed) Source RPM Packages mailx-12.5-8.fc19.x86_64 Target RPM Packages filesystem-3.2-13.fc19.x86_64 Policy RPM selinux-policy-3.12.1-74.9.fc19.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 3.11.3-201.fc19.x86_64 #1 SMP Thu Oct 3 00:47:03 UTC 2013 x86_64 x86_64 Alert Count 2 First Seen 2013-10-23 18:50:36 EST Last Seen 2013-10-23 18:50:36 EST Local ID 240be1d2-be11-47b0-8255-977c92604c13 Raw Audit Messages type=AVC msg=audit(1382514636.180:239316): avc: denied { write } for pid=11343 comm="mail" name="/" dev="dm-1" ino=128 scontext=system_u:system_r:system_mail_t:s0 tcontext=system_u:object_r:root_t:s0 tclass=dir type=SYSCALL msg=audit(1382514636.180:239316): arch=x86_64 syscall=open success=no exit=EACCES a0=26fd6d0 a1=441 a2=1b6 a3=c items=0 ppid=1 pid=11343 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 ses=4294967295 tty=(none) comm=mail exe=/usr/bin/mailx subj=system_u:system_r:system_mail_t:s0 key=(null) Hash: mail,system_mail_t,root_t,dir,write Additional info: reporter: libreport-2.1.8 hashmarkername: setroubleshoot kernel: 3.11.3-201.fc19.x86_64 type: libreport Potential duplicate: bug 682577
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.