Hi All, One of our R720 servers raised following in OMSA-8.5.0 yesterday, Mon Dec 11 18:47:10 2017 System Peak Power detected new peak value Peak value (in Watts): 789 The power recorded by iDrac then was 128W. The max power measured during Prime95 stress test before deploying was 250W. So, it's highly unlikely the server could actually reach 789W. And syslog of the server says following, Dec 11 18:47:10 n01 Server_Administrator: 9551 1013 - Instrumentation Service System Peak Power detected new peak value #012Peak value (in Watts): 789 Dec 11 18:47:14 n01 setroubleshoot: SELinux is preventing /bin/hostname from read access on the chr_file /dev/megaraid_sas_ioctl_node. For complete SELinux messages. run sealert -l a585cd80-95e8-4055-9f83-1d1b6f450563 ... Dec 11 18:47:16 n01 setroubleshoot: SELinux is preventing /bin/mailx from read access on the chr_file /dev/megaraid_sas_ioctl_node. For complete SELinux messages. run sealert -l 82490d50-118d-4c04-ad3a-a6ac8bcbd622 ... Dec 11 18:47:20 n01 setroubleshoot: SELinux is preventing /bin/mailx from read access on the chr_file /dev/megaraid_sas_ioctl_node. For complete SELinux messages. run sealert -l 82490d50-118d-4c04-ad3a-a6ac8bcbd622
So, it's likely the SELinux triggered the alert. The OS involved is CentOS-6 x64 with latest patch. Is this expected behavior of the OMSA? If so, I can create a local SELinux policy to allow them. Or, should I worry system security breached? Thanks! Regards, Frank Wang _______________________________________________ Linux-PowerEdge mailing list [email protected] https://lists.us.dell.com/mailman/listinfo/linux-poweredge
