Donna, Applied the changes for mcelog also. The last issue I'm working so far with Mitch is the wrong system name is being picked up when multiple IP's are plumbed up on the same NIC. Mitch should have all the details but maybe I'll open up a new forum on this one also. Thanks for your support. dave ... View more

Looks like the sudo trick worked. Ready for another one? something is trying to open /dev/mcelog on 15 minute intervals and getting permission denied. Nov 10 20:28:27 usorl03p309 mcelog: Cannot open /dev/mcelog Nov 10 20:43:26 usorl03p309 mcelog: Cannot open /dev/mem for DMI decoding: Permission denied Nov 10 20:43:26 usorl03p309 mcelog: Cannot open /dev/mcelog Nov 10 20:58:27 usorl03p309 mcelog: Cannot open /dev/mem for DMI decoding: Permission denied dave ... View more

Thanks Donna. That's sorta what it was looking like since user root seem to work ok. It's tough doing root level tasks and at the same time maintain security. I'll give your suggestions a try and report back to you. dave ... View more

Output from /proc/mdstat usorl03p309 ~ -1277> cat /proc/mdstat Personalities : [raid1] md0 : active raid1 sdb1[1] sda1[0] 208704 blocks [2/2] [UU] md1 : active raid1 sdb2[1] sda2[0] 12586816 blocks [2/2] [UU] md2 : active raid1 sdb3[1] sda3[0] 49721088 blocks [2/2] [UU] unused devices: usorl03p309 ~ -1278> dave ... View more

The hardware installation is a BL495G5 blade that has two internal SSD 64GB disks. The OS is RHEL 5.4 and mirrored acrossed the two internal drives. mdadm.conf # mdadm.conf written out by anaconda DEVICE partitions MAILADDR root ARRAY /dev/md0 level=raid1 num-devices=2 uuid=aa4f5616:1f85a679:04e92872:8cb15fe7 ARRAY /dev/md1 level=raid1 num-devices=2 uuid=6787038e:e6c35d9c:fa5a0916:9729dd5f dave ARRAY /dev/md2 level=raid1 num-devices=2 uuid=c90d94d7:2f54ad8e:74248664:92872716 ~ ... View more

Ran the getMdadmEvents as both root and nagios. When ran as root no messages are generated in /var/log/messages. When ran as nagio, each time the command getMdadmEvents generates: Nov 6 13:45:53 usorl03p309 mdadm: DeviceDisappeared /dev/md1 Nov 6 13:45:53 usorl03p309 mdadm: DeviceDisappeared /dev/md0 Nov 6 13:45:59 usorl03p309 mdadm: DeviceDisappeared /dev/md2 Nov 6 13:45:59 usorl03p309 mdadm: DeviceDisappeared /dev/md1 Nov 6 13:45:59 usorl03p309 mdadm: DeviceDisappeared /dev/md0 I believe the messages are bogus and the devices are NOT disappearing. dave ... View more

The change did stop the alerts but /var/log/messages is still filling up with the bogus messages that start when mond sevice is started. every 15 minutes. mond -> /opt/hptc/supermon/etc/init.d/mond-setup with mond stopped there are no more messages generated in /var/log so there is something that ICE-Linus (supermon) is doing that is causing the message to occur in the first place. Need to find the root cause that is causing the messages. I can provide you a virtual room connection if it would help. ... View more

By chance should ther be a "|" between (SparesMissing) (DeviceDisappeared) ??? maybe shoudl be: (SparesMissing)|(DeviceDisappeared)/) ... View more

Thanks for the quick reply Donna. The HP case number for this issue is 4606099605. There is lots of logs and sysreports attached to the case if you can pull it up. The RHEL version on the node is RHEL 5.4 x86_64 on BL495G5 blades in C7000 chassis. Have been working with Mitch on other issues also but not this one. We are interested in seeing valid mdadm alerts, but these are not valid and start after mond is stared. I will make your suggested changes and report back. ... View more