Process Test method working alternatively
-
- Posts: 6
- Joined: Wed Oct 05, 2011 2:35 am
Process Test method working alternatively
Hello all,
I have problem with process test method on a remote domino server.
Process Test:
- Check process on \\[DOMINO SERVER]
- Alert when less than 1 nhttp are running
- Connect as [DOMINO SERVER]\[local admin account] good password
When the test is working it returns : 1
The problem is on many test refresh, this test have alternative status from "OK" reply "1" to "Unknown".
It sounds like timeout.
Anyone have some tips ?
Hostmonitor 8.86 on 2008 R2 server.
I have problem with process test method on a remote domino server.
Process Test:
- Check process on \\[DOMINO SERVER]
- Alert when less than 1 nhttp are running
- Connect as [DOMINO SERVER]\[local admin account] good password
When the test is working it returns : 1
The problem is on many test refresh, this test have alternative status from "OK" reply "1" to "Unknown".
It sounds like timeout.
Anyone have some tips ?
Hostmonitor 8.86 on 2008 R2 server.
There a lot of possible reasons for this: server is too busy to process RPC requests in time, some improperly working antivirus or firewall, and so on.
For begining try to setup CPU Usage test for the same server and check if it will work fine or not. If this test will return Unknown status, check Reply field value.
Do you have installed some antivirus monitors, personal firewall, content monitoring software? Non stanard winsock components?
HostMonitor and target server located in the same LAN and same domain?
Regards
Alex
For begining try to setup CPU Usage test for the same server and check if it will work fine or not. If this test will return Unknown status, check Reply field value.
Do you have installed some antivirus monitors, personal firewall, content monitoring software? Non stanard winsock components?
HostMonitor and target server located in the same LAN and same domain?
Regards
Alex
-
- Posts: 6
- Joined: Wed Oct 05, 2011 2:35 am
Hello,
Thanks for your reply.
I had installed antivirus (McAfee VirusScan Enterprise) on this server but On Access Scan and Access Protection are disabled.
This server is not in the same LAN than my Hostmonitor server (firewall applicance between them).
I will try CPU Usage test for this server and check if it works.
I will be back.
Thanks for your reply.
I had installed antivirus (McAfee VirusScan Enterprise) on this server but On Access Scan and Access Protection are disabled.
This server is not in the same LAN than my Hostmonitor server (firewall applicance between them).
I will try CPU Usage test for this server and check if it works.
I will be back.
-
- Posts: 6
- Joined: Wed Oct 05, 2011 2:35 am
Sorry for double post but I am back with some adds.
I created a CPU test.
It works like process test.
In good run it returns CPU usage in % > 28% OK
But when i use refresh button the test show alternatively the unknown status with reply:
Cannot conect to remote Registry. Code #1727
Remote registry service is started on Hostmonitor server and on remote server.
I created a CPU test.
It works like process test.
In good run it returns CPU usage in % > 28% OK
But when i use refresh button the test show alternatively the unknown status with reply:
Cannot conect to remote Registry. Code #1727
Remote registry service is started on Hostmonitor server and on remote server.
Probably this problem caused by firewall.
RPC dynamic port allocation (used for all RPC calls including Remote Registry calls) may use any random port above 1024.
You may check firewall settings or change RPC dynamic port allocation.
Please check the following article for details
http://support.microsoft.com/kb/154596
Regards
Alex
RPC dynamic port allocation (used for all RPC calls including Remote Registry calls) may use any random port above 1024.
You may check firewall settings or change RPC dynamic port allocation.
Please check the following article for details
http://support.microsoft.com/kb/154596
Regards
Alex
-
- Posts: 6
- Joined: Wed Oct 05, 2011 2:35 am
1) RCC does nothing, it does not perform tests and it cannot work without HostMonitor. It just remote console that shows you what HostMonitor does.
This means HostMonitor is still running.
2) If you closed HostMonitor application, I assume you have started HostMonitor service? Normally HostMonitor application checks for HostMonitor service, ask you for confirmation and stop service when you really need application instead. If you forced HostMonitor to run application and service at the same time, this may lead to some configuration problems (service will not "see" your changes made in application until restart, etc)
3) Some tests may work differently (e.g. return Unknown status) when you are running HostMonitor under different accounts due to some restrictions with one of your user accounts. E.g. you start service under admin account but run application using regular user with restricted rights.
However this cannot explain problem you have (as I understand the same test may retun "good" or "unknown" status without any changed on HostMonitor side, right?)
Regards
Alex
This means HostMonitor is still running.
2) If you closed HostMonitor application, I assume you have started HostMonitor service? Normally HostMonitor application checks for HostMonitor service, ask you for confirmation and stop service when you really need application instead. If you forced HostMonitor to run application and service at the same time, this may lead to some configuration problems (service will not "see" your changes made in application until restart, etc)
3) Some tests may work differently (e.g. return Unknown status) when you are running HostMonitor under different accounts due to some restrictions with one of your user accounts. E.g. you start service under admin account but run application using regular user with restricted rights.
However this cannot explain problem you have (as I understand the same test may retun "good" or "unknown" status without any changed on HostMonitor side, right?)
Regards
Alex
-
- Posts: 6
- Joined: Wed Oct 05, 2011 2:35 am
Hostmonitor is actually running as service with local system account.
I am loggued with the local administrator account.
The hostmonitor application was launched by choosing the "no" answer (create a second application instance?).
When I closed this application, the service is still running and I tried to run RCC in order to see the interface. No problem with process tests.
Hostmonitor is installed on a 2008 R2 server.
I am thinking about a conflict in the second instance of the application. Is it coorect?
I am loggued with the local administrator account.
The hostmonitor application was launched by choosing the "no" answer (create a second application instance?).
When I closed this application, the service is still running and I tried to run RCC in order to see the interface. No problem with process tests.
Hostmonitor is installed on a 2008 R2 server.
I am thinking about a conflict in the second instance of the application. Is it coorect?
Bad idea.The hostmonitor application was launched by choosing the "no" answer (create a second application instance?)
That's why HostMonitor displayed warning message
-----------------
We do not recommend to start several instances of HostMonitor using the same installation folder and configuration files unless you really understand consequences of such action
-----------------
Do you really understand consequences of such action?
As I said this may lead to configuration problems. But this should not lead to problem you had when your servers/firewall/network work properly.I am thinking about a conflict in the second instance of the application. Is it coorect?
Unless we misunderstand problem description.
Does "test have alternative status from OK reply 1 to Unknown" means
the same test item may retun "good" or "unknown" status without any changed on HostMonitor side (without changing test settings or restarting HostMonitor), right?
Regards
Alex
-
- Posts: 6
- Joined: Wed Oct 05, 2011 2:35 am