KS-Soft

Thanks so much for the reply! I'm going to switch over to text logs and see if that helps. If not, then I'll go with a daily rotation.

Thanks again!

Hi, I'm having an issue where my log is stopping at 2 GB. I am using .htm logs and rotating weekly. We just started hitting this limit in the last couple of weeks and didn't have any problems before then, but I run weekly reports off of the logs to provide to each client with statistics, so I need t...

I've been watching the handles a little more and they appear to fluctuate rather than rise and stay there. Do the handles rise sharply when a test is done? Each RMA runs between 8 and 10 tests every 5 minutes, so maybe the handles increase when the tests are done and then drop again when the tests a...

I looked into it a little more and only 2 of the servers that I use RMA on have the high handle counts - all of the other servers had handle counts of 250 or less. The two servers that do have high handle counts seem to stay in the mid 7000s, but I'm not really sure what would be causing it on these...

Yes, the handle count is that high on all of the servers and when I restart the RMA service the handles dip down really low (about 100), but slowly creep back up. I guess I could schedule daily/weekly service restarts, but that seems unnecessary at this point because the other fix eliminated the unn...

No ODBC requests. Here are the requests that are on each of these servers:

Disk space for each drive
CPU
Several service and process checks
Memory

We do have McAfee Enterprise installed on all of these servers, but we were actually having problems prior to the installation of it on them. Other than that, we are using typical Windows 2003 Server apps as well as Commerce and DB programs. The resource usage on these boxes is actually pretty low a...

I'm not sure how it could be the server since the same exact issue is happening on 6 different boxes. Maybe there is a bug in the RMA for Windows Server 2003 Enterprise SP1 and SP2? Anyways, I'm going to try to disable the "Warning=Bad" option and that should do the trick. Then all of the ...

I actually increased the test interval to 5 minutes yesterday and fewer alerts are coming in, but I still get them once in a while. I'm assuming that the monitor just isnt' catching them now since I upped the interval from 1 minute to 5 minutes. Where can I find the Treat Unknown as Bad" option...

Hi, again, Yes, I am only testing the local machine that the RMA agent is installed on and yes, I use <local computer> instead of a hostname or IP. Any ideas on a solution? Also, if I end up having to go with the Advanced profile method instead of the standard, right now I have it set that after 5 b...

Thanks so much again! I sent the files in with a pdf copy of the ticket so whoever gets it will have the history. If you could let me know what you think I would really appreciate it! Also, I'd like to save the use of the Advanced mode as a last resort, but I'll keep it in mind if we can't find anot...

All RMAs are 3.44 and Host Monitor is 6.82 (they should all be the most up to date versions). Also, all of the RMA configs have "Failure audit log to" checked and the log is "log2.txt" as you said. What about re-installing the agents or installing backup agents? Or any other poss...

Only one of the servers actually has the log file so I'm assuming that the other RMAs haven't needed to log any errors yet. The one log file that does exist one has 4 lines in it from back on august 29 (I believe when it was installed), but nothing recent and I have seen the issue once on each serve...

The few times that I have actually been able to get to the Host Monitor box while they were in error, each of the problem CPU monitors would only take 5-10 seconds to error out (not the full 120 seconds). Also, yes each RMA monitors the CPU locally on the box it is installed on and each of the CPU m...

Hi, again. The issue is still happening, so I was wondering if you have any further ideas? The timeout on the Host Monitor side in RMA Manager is 120 seconds for each agent and the timout on the agent side is the 1 minute I made it yesterday. I have several other Windows 2003 agents installed on oth...