False monitoring values caused a server crash
Hi,
I'm monitoring the free disc space in GB on a Windows 2003 Server using WMI (standard monitors). There are two drives which return values with 4GB (C:) and 32GB (D:). The OpManager table says that the disc space of both drives didn't change the last weeks. They always had the same value.
Drive C: should have the value of 5GB. The last weekend drive D: went to the size of 0 Bytes. OpManager didn't monitor this and kept on showing the value of 32GB (until today). I've tested this special monitor but also received the value of 32GB. SNMP and WMI tests had passed.
After removing and readding the two standard monitors the correct values have been shown. Now drive C: has 5GB and drive D: has 12GB (which is conform to the real values).
This is a very important server for us. These two monitors have a threshold alarm. If one is underrunning 3GB a notification has to be sent. Because OpManager didn't realize that the size of drive D: shrank to 0 Bytes we didn't receive any notification and had a server crash.
I hope you can find a solution for this bug so that this won't happen again.
Kind regards,
Mok
I'm monitoring the free disc space in GB on a Windows 2003 Server using WMI (standard monitors). There are two drives which return values with 4GB (C:) and 32GB (D:). The OpManager table says that the disc space of both drives didn't change the last weeks. They always had the same value.
Drive C: should have the value of 5GB. The last weekend drive D: went to the size of 0 Bytes. OpManager didn't monitor this and kept on showing the value of 32GB (until today). I've tested this special monitor but also received the value of 32GB. SNMP and WMI tests had passed.
After removing and readding the two standard monitors the correct values have been shown. Now drive C: has 5GB and drive D: has 12GB (which is conform to the real values).
This is a very important server for us. These two monitors have a threshold alarm. If one is underrunning 3GB a notification has to be sent. Because OpManager didn't realize that the size of drive D: shrank to 0 Bytes we didn't receive any notification and had a server crash.
I hope you can find a solution for this bug so that this won't happen again.
Kind regards,
Mok