Hoping you can help a few common intermittent errors we are seeing as we roll out Host Monitor across multiple datacenters.
HostMonitor v. 9.58
RMA (passive) v. 4.58.0.297
Windows Server 2008 R2 Standard Service Pack 1
First Error
Test Method: check NT Event Log
RMA: 301 - System Error. Code: 87
Second Error
Test Method: check NT Event Log
RMA: 301 - Cannot open event log. The RPC server is unavailable.
Third Error
Test Method: Perf Counter test
RMA: Cannot read data
Again with all of these they work and function as normal but occasionally/frequently throw these errors.
Intermittent RMA Errors
Increase timeout for this agent.Third Error
Test Method: Perf Counter test
RMA: Cannot read data
I don't think we can do anything in this case.Test Method: check NT Event Log
RMA: 301 - Cannot open event log. The RPC server is unavailable.
Again with all of these they work and function as normal but occasionally/frequently throw these errors.
That's network or target server problem. May be server too busy to respond, out of resources...
If some tests works unstable, setup alert profile to start actions after 2nd, 3rd consecutive failure. Also you may use "Repeat test" action after first "unknown" status.
Are you using Windows Vista mode for this test? or Windows NT mode?Test Method: check NT Event Log
RMA: 301 - System Error. Code: 87
Regards
Alex
We are using Windows Vista mode since they are 2008 R2 servers and they occasionally throw the RMA: 301 - System Error. Code: 87Are you using Windows Vista mode for this test? or Windows NT mode?
For some reason in one data center only, when we use Windows Vista mode we get 'RMA: 301 - Cannot open event log. The RPC server is unavailable' always without exception. As soon as we modify them to use Windows NT Mode they immediately work.
Target servers are fine on resources (CPU, RAM, Disk).
Thanks for your responses!
How many NT Event Log tests performed by agent?We are using Windows Vista mode since they are 2008 R2 servers and they occasionally throw the RMA: 301 - System Error. Code: 87
There are some bugs in new Windows API (Windows Vista API does not work well in multi-thread environment).
Could you add VistaEvLogMode=1 line into [Misc] section of rma.ini file and restart RMA to apply changes?
(note: test probes will require more time)
Sorry, we cannot explain this.For some reason in one data center only, when we use Windows Vista mode we get 'RMA: 301 - Cannot open event log. The RPC server is unavailable' always without exception. As soon as we modify them to use Windows NT Mode they immediately work.
Windows 2008 R2 as well?
Regards
Alex
What is "VistaEvLogMode"? Are you controlling the number of threads with this parameter?
Yes, all Win 2008 R2
Also, do you have documentation on all ini settings as well as documentation on all error codes?
We will try the settings you recommend and let you know our results. We currently have many of the perfmon tests disabled to see if it impacts the number of errors we are receiving across all other tests.
Yes, all Win 2008 R2
Also, do you have documentation on all ini settings as well as documentation on all error codes?
We will try the settings you recommend and let you know our results. We currently have many of the perfmon tests disabled to see if it impacts the number of errors we are receiving across all other tests.
-
- Posts: 2832
- Joined: Tue May 16, 2006 4:41 am
- Contact:
There are 3 possible values for VistaEvLogMode:What is "VistaEvLogMode"? Are you controlling the number of threads with this parameter?
VistaEvLogMode=0 normal multithread mode.
VistaEvLogMode=1 HostMonitor/RMA performs one test per server
VistaEvLogMode=2 HostMonitor/RMA performs one test only (one by one)
No. All standard ini settings should be changed using HostMontor/RMA GUI. Other undocumented settings should not be used, unless there are some real problem in particular environment.Also, do you have documentation on all ini settings
HostMonitor just displays errors, returned by Windows API. You may check MS KB atricles for specific errors.as well as documentation on all error codes?