HM generates "Unknown Status" for all tests after unexpected

EdwardDuong · Post by **EdwardDuong** » Thu Nov 21, 2002 10:52 am

Once in a while, HM unexpectedly goes down. I use HM on my workstation to monitor the main HM on the server. When HM on the server goes down (I don't know the cause!), HM on my workstation will remotely restart the HM process via Remote Command Service. However, all tests on the server's HM show "Unknown status". Here is the external program "ReStartHMon.bat" that executes when HM on the server goes down:

@ECHO OFF

rcmd \cdmis1hb "C:Program FilesHostMonitor3HostMon.exe"

Do you know why HM generates "Unknown" status?

KS-Soft · Post by **KS-Soft** » Thu Nov 21, 2002 3:36 pm

"Unknown" status condition depends on test. There is table that explain when HostMonitor uses "Unknown" status http://www.ks-soft.net/hostmon.eng/mfra ... knownIsBad

Regards
Alex

EdwardDuong · Post by **EdwardDuong** » Thu Nov 21, 2002 3:46 pm

Thank you very much for your reponse, Alex. I know what "Unknown" status is. But please tell me why after HM restarts on the remote server via Remote Command Service, ALL tests show "Unknown". Is this a bug? or I have to configure something else to avoid false alarms. Your suggestion would be greately appreciated.

Best regards.

KS-Soft · Post by **KS-Soft** » Thu Nov 21, 2002 3:55 pm

I don't know why you have this problem. What kind of tests do you use? What version of HostMonitor? Could you send screen shot to our address line1@ks-soft.net?

Regards
Alex

KS-Soft · Post by **KS-Soft** » Thu Nov 21, 2002 3:57 pm

BTW if you restart HM manually (login to system locally and restart HM), does it work properly?

Regards
Alex

EdwardDuong · Post by **EdwardDuong** » Thu Nov 21, 2002 5:30 pm

It's fine if I manually shut down and restart HM. It happens only when HM unexpectely shuts down.

EdwardDuong · Post by **EdwardDuong** » Thu Nov 21, 2002 5:31 pm

By the way, my HM version is 3.44 (latest version).

KS-Soft · Post by **KS-Soft** » Thu Nov 21, 2002 9:02 pm

I think Remote Command Service does not work correctly. As far as I know it runs as service on remote system, and I think it starts HostMonitor under the same system account. In this case HostMonitor started as regular application but under local system account. So, some tests (I still don't know which tests do you use) those needs power user or administrator's acoount will not work.
Probably start Remote Command Service under administrators account will help.

Regards
Alex

Marcus · Post by **Marcus** » Fri Nov 22, 2002 6:41 am

The problem is that when started with rcmd (and thus as the 'system account'), your application runs in a different security AND user context.

The solution should be to run the rcmd command with the same user account as HM.